Message PXM1135 seen when XMANAGER restart fails after a hardware failure.

Products

• Detector for DB2 for z/OS

Issue/Introduction

A 3-way production xmanager group is running on two z15s on 3 LPARs.  Two of the LPARs were lost when one machine underwent an emergency power down.  On subsequent LPAR IPLs after recovery, the xmanagers would not restart on that machine.  Workaround was to change XSYS from Y to N to get them up and running. 

The other xmanager that survived the event went on to be restarted during a cleanup IPL with XSYS=Y with no issues.   

Environment

DB2 for z/OS

Cause

The specified Xmanager cannot start because the coupling facility (CF) list structure changed state after other active Xmanagers in the group were started.

Resolution

Review of the Xmanager logs show that both Xmanagers reported message PXM1135 .

PXM1135 XMANAGER CF LIST STRUCTURE WAS ALLOCATED WHEN OTHER ACTIVE XMANAGERS IN GROUP PXM2000 WERE STARTED XMID=2000  

PXM1135 indicates that "The specified Xmanager cannot start because the coupling facility (CF) list structure changed state after other active Xmanagers in the group were started. "  

Follow the action steps for PXM1135 message and verify the Coupling Facility List Structure is defined in the active CFRM policy.

See the message page for the details on PXM1135 message:  

 

This page discusses defining the Coupling facility List structure. 

 

A workaround is to change XSYS from Y to N to get them up and running till the ACTION steps in  PXM1135  can be implemented.