Xmanager tasks stopped with several abends S222 due to automation cancel
Article ID: 195339
Updated On:
Products
Issue/Introduction
Suddenly the Database Management for Db2 for z/OS Xmanager started task stopped with several abends S222 related to
the UPM and Health Checker tasks:
CSLOG004I Closing UPMLOG - WRITEs(6) Lines(6) Switch(0)
PXM0810 CA/XMANAGER RECOVERY IN PROGRESS (TCB 00AC8178)
PXM0811 PSW: 478D0000 96D01A34 LMOD: PXMINICC OFFSET: 00001A34 ABEND: S222
GEN0907 CA-DB2 Tools Health Checker recovery in progress
GEN0913 CA-DB2 Tools Health Checker interface termination in progress
GEN0909 CA-DB2 Tools Health Checker active health check stop in progress
GEN0910 CA-DB2 Tools Health Checker active health check stop complete
GEN0914 CA-DB2 Tools Health Checker interface termination complete
GEN0908 CA-DB2 Tools Health Checker recovery actions complete
PXM0810 CA/XMANAGER RECOVERY IN PROGRESS (TCB 00AC8310)
PXM0811 PSW: 478D0000 96D01A34 LMOD: PXMINICC OFFSET: 00001A34 ABEND: S222
Resolution
Problem was with the implementation of the Automation product.
First there was a Stop command for the Xmanager started task: P <xmanager>
After 30 seconds interval there was a Cancel command: C <xmanager>
Unfortunately Xmanager did not stop within 30 seconds so the Cancel command was issued with the abends S222.
Xmanager has several Subtasks attached to communicate with other systems, one of the systems is IBM Health Checker or Db2 Tools with UPM Task.
GEN0901 CA-DB2 Tools Health Checker task attached
GEN0935 CA-DB2 Tools UPM manager attached
...
GEN0937 CA-DB2 Tools UPM manager initialization in progress
GEN0938 CA-DB2 Tools UPM manager initialization complete
...
GEN0911 CA-DB2 Tools Health Checker interface initialization in progress
GEN0912 CA-DB2 Tools Health Checker interface initialization complete
At the Stop command these Subtasks have to be stopped correctly to clean up all the storage and finish Xmanager started task
gracefully. If you issue the Cancel command while the Health Checker Subtasks or the UPM Subtask have not finished yet then
the storage is not cleaned up correctly and results in next Xmanager start up are unpredictable.
The interval was increased to 90 seconds and hopefully with the new window Xmanager will be able to stop all the Subtasks
correctly and you will not find these S222 abends anymore.
Feedback
