Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
$HASP554 z/OS JES2 Messages SA32-0989-01 |
|
$HASP554 Explanation>>-MEMBER--member_name – – --A MISMATCH EXISTS-----------------> >--BETWEEN WHAT JES2 WAS EXPECTING ON---------------------------> >--CKPTn AND WHAT WAS PROVIDED BY THE---------------------------> >--COUPLING FACILITY RC=--rsnc--------------------------------->< MEMBER member_name – – A MISMATCH EXISTS
BETWEEN WHAT JES2 WAS EXPECTING ON JES2 finds that the information on the in-storage copy of the checkpoint data set and the copy of the checkpoint data set that resides on a coupling facility structure do not match. It is possible that you are
attempting to start a JES2 member with initialization parameters that
are incompatible with the initialization parameters that are either:
a. Currently in effect in the MAS Under these circumstances, the format of the checkpoint data set already in effect can be very different from the one expected on the member you are attempting to start. This discrepancy can cause various errors to occur, including the display of this message. This is an example of conditions that can cause these errors to occur: You have attempted to change a cold start initialization parameter during a warm start (for example, JOBNUM= on the JOBDEF initialization statement). See the z/OS JES2 Initialization and Tuning Reference for a description of initialization parameters that require a cold start. See the JES2 Migration Notebook applicable for the highest JES2 release running in the MAS for more details on checkpoint compatibility. In the message text:
System actionJES2 enters the checkpoint reconfiguration dialog. Operator responseNotify system programmer System programmer responseCorrect the initialization parameters so that they are compatible with the with the cold start initialization parameters currently in effect. ModuleHASPCFLE Routing Code: 1,2,10 Descriptor Code: 4 |
Copyright IBM Corporation 1990, 2014
|