CQS checkpoint problems

CQS checkpoint messages

Most problems are of structure checkpoint type because it is a sysplex-wide operation with shared resources (SRDS data set, structures on the CF), and it needs cooperation through z/OS® IXLUSYNC between all CQSs within the sysplex. Sometimes, another CQS process (initialization, termination, rebuild, overflow threshold, or overflow scan) can interfere with the checkpoint process and cause it to fail.

CQS System Checkpoint Messages

1. CQS0030I for a successful CQS system checkpoint.
2. CQS0035E for a failed CQS system checkpoint. If the CQS system checkpoint failed with CQS0035E, refer to CQS messages in IMS Version 15.6 Messages and Codes, Volume 2: Non-DFS Messages for the details of the failure and the recommended system programmer action.

CQS Structure Checkpoint Messages

The syslog of a successful CQS structure checkpoint will contain five CQS messages in the following order:

CQS0220I CQS cqsname START STRUCTURE CHECKPOINT FOR STRUCTURE strname
CQS0200I STRUCTURE strname QUIESCED FOR STRUCTURE CHECKPOINT
CQS0201I STRUCTURE strname RESUME AFTER STRUCTURE CHECKPOINT
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE strname LOGTOKEN logtoken
CQS0221I CQS COMPLETE STRUCTURE CHECKPOINT FOR STRUCTURE strname

If the CQS structure checkpoint failed with a CQS0222E message, refer to the CQS messages section in IMS Version 15.6 Messages and Codes, Volume 2: Non-DFS Messages for the details of the failure and the recommended system programmer action.

If message CQS0222E is not displayed and all five of the normal structure checkpoint messages did not appear on the console, CQS probably has encountered a serious WAIT/HANG problem.

The CQS log records, the structure dump of the related structure, and the SRDSs (structure recovery data sets) are helpful in diagnosing the problem. After collecting all the documents, you can stop the CQS in error and restart it to resolve the WAIT/HANG problem.