Global DSM Messages - mfx - 3.1

Syncsort™ MFX Installation

Product type
Software
Portfolio
Integrate
Product family
Syncsort™ Software
Product
Syncsort™ MFX > MFX
Version
3.1
Language
English
Product name
Syncsort™ MFX
Title
Syncsort™ MFX Installation
Copyright
2024
First publish date
2010
Last updated
2024-08-27
Published on
2024-08-27T07:49:46.255035
Message Codes Descriptions
WER600I

SYNCSORT DSM SUBSYSTEM - UNSUPPORTED SYSTEM COMMAND. REQUEST IGNORED   

EXPLANATION: Global DSM does not support the system command that was issued. The request has been ignored, and global DSM will continue normal operation.

WER605I

SYNCSORT DSM SUBSYSTEM INITIALIZATION COMPLETE   

EXPLANATION: Global DSM has been successfully started.

WER606I

SYNCSORT DSM SUBSYSTEM TERMINATION COMPLETE 

EXPLANATION: Global DSM has been terminated by a STOP com­mand or an internally detected critical error. If a STOP command was not issued, refer to previous WERxxxy messages for additional infor­mation.

WER607I

SYNCSORT DSM SUBSYSTEM TERMINATION IN PROGRESS   

EXPLANATION: Global DSM has received a STOP command and has initiated termination processing. WER606I will be issued when termination processing is complete.

WER610A

SYNCSORT DSM SUBSYSTEM TERMINATED DUE TO CRITICAL ERROR 

EXPLANATION: One or more supporting functions in global DSM have ended with a critical error or abend. Global DSM will try to write a diagnostic dump to a SYS1.DUMPxx data set.

WER612A

SYNCSORT DSM SUBSYSTEM xxxxxxxx LOAD FAILURE, CODE=yyy, RC=zzz   

EXPLANATION: The module xxxxxxxx cannot be successfully loaded. For an explanation of the codes yyy and zzz, see the appropriate IBM Message Library: System Codes manual for your system. Global DSM is terminated.

WER614A

SYNCSORT DSM SUBSYSTEM ALREADY ACTIVE. REQUEST IGNORED   

EXPLANATION: Two global DSM subsystem interfaces with the same name may not be active on one system simultaneously. 

WER615A

SYNCSORT DSM SUBSYSTEM LIBRARY MUST BE APF AUTHORIZED   

EXPLANATION: The global DSM modules must reside in an APF authorized library. 

WER616A

SYNCSORT DSM SUBSYSTEM - UNSUPPORTED OPERATING SYSTEM   

EXPLANATION: Global DSM requires a z/OS operating system.

WER617A

SYNCSORT DSM SUBSYSTEM - DSMHIST DD NOT DEFINED   

EXPLANATION: Global DSM requires a DSMHIST DD statement be defined in the SYNCDSM1 JCL procedure. 

WER618A

SYNCSORT DSM SUBSYSTEM - HISTORY DATA SET UNINITIALIZED   

EXPLANATION: Global DSM’s history data set must be initialized prior to the execution of the START command for the SYNCG100 JCL procedure. For more details, see STEP 15: Initialize Global DSM’s History Data Set in Installation Procedure section above in this guide.

WER619A

SYNCSORT DSM SUBSYSTEM - INCORRECT HISTORY DATA SET FOR THIS SYSTEM ID  

EXPLANATION: A history data set in global DSM cannot be shared by different systems. You must allocate a separate history data set for each system, and activate it. For more details, see STEP 14: Allocate Global DSM’s History Data Set in Installation Procedure section above in this guide.

WER620A SYNCSORT DSM SUBSYSTEM - UNEQUAL MAINTENANCE LEVELS: xxxxxxxx, yyyyy, zzzzz   

EXPLANATION: The load module xxxxxxxx of global DSM (GDSM) and the GDSM root module maintenance levels do not cor­respond. yyyyy represents the maintenance level of the xxxxxxxx module; zzzzz represents the maintenance level of the root module.