Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
$HASP787 z/OS JES2 Messages SA32-0989-01 |
|
$HASP787 Explanation>>-FAILURE DURING THE XCF JOIN-- BECAUSE A DUPLICATE------------> >--JES2 XCF MEMBER IS ACTIVE – --MEMBER=--nodename--$--memb-----> >--GROUP=--xcfgrpnm-------------------------------------------->< MAS member memb is attempting to join the JES2 XCF group but cannot because a member with an identical name already belongs to the group. Each MAS should have a unique XCF group name. However, if there is more than one MAS with the same node name, sharing the same JES2 XCF group, and at least one member in each shares the same name, this failure can occur. In the message
text:
System actionJES2 initialization ends. Operator responseDecide which JES2 MAS member should be joined to the XCF group and stop the JES2 member that doesn't belong in the JES2 XCF group. In addition, notify the system programmer. System programmer responseIf more than one MAS should happen to exist in a sysplex environment, each MAS should define a unique XCF group for JES2 to join. This can be done by specifying a unique name in the XCFGRPNM parameter on the MASDEF initialization statement for all MAS's in the sysplex. See z/OS JES2 Initialization and Tuning Guide and z/OS JES2 Initialization and Tuning Reference for information on the XCFGRPNM parameter. ModuleHASPXCF Routing Code: 1,2,10 Descriptor Code: 4 |
Copyright IBM Corporation 1990, 2014
|