IMS/ESA Shared Queues: A Planning Guide

/S IMA2CQS

*138 CQS0031A CONFIRM CQS RESTART FOR STRUCTURE IMA0MSGQ CMA2CQS

*139 CQS0031A CONFIRM CQS RESTART FOR STRUCTURE IMA0EMHQ CMA2CQS

R 138,CONFIRM

CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0MSGQ

R 139,CONFIRM

CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0EMHQ

CQS0020I CQS READY CMA2CQS

CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0MSGQ

CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0EMHQ

IMS and CQS resynchronized through DFS0226A.

An MPR was started on IMA2 and it processed all the messages on the

shared-queue. Transaction IVTNO was the MSC transaction defined to process

as local on IMA2. In fact the output to the previously entered transactions

reached the related terminals and no more replies were present on the

shared-queue. These commands

/DISPLAY QCNT TRAN MSGAGE 0

/DISPLAY QCNT LTERM MSGAGE 0

both showed there were no transactions or output messages on the

shared-queues.

QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW

*98218/092451*

8.2.3 CQS Abend with Transactions on SQ, Checkpoint Data Sets and SRDS

Deleted

During this test, we followed the same path as for 8.2.2, “CQS Cancelled with

Transactions in SQ and Checkpoint Data Sets Deleted” on page 71 with the

difference that we deleted all the checkpoint data sets and the SRDSs. We got

exactly the same results. Deleting the SRDSs does not impact normal operation

unless it is required to use them during recovery.

8.3 CQS Cold Start

A series of tests was performed after cold-starting CQS:

•

8.3.1, CQS Cold Start with Transactions in Flight (IMS Running)

•

8.3.2, CQS Cold Start with IMS Emergency Restart and Transactions In-flight

•

8.3.3, Test Begun after Replying to WTOR (Output in Flight)

8.3.1 CQS Cold Start with Transactions in Flight (IMS Running)

A transaction was entered from IMA1CTL/IMA1CQS without any MPR in the IMS

sysplex. The transaction was:

/FORMAT IVTNV

TADD (valerio oldest 11 22)

This was done with the intention of having a WTOR pending and, therefore, the

transaction waiting in the queue before a commit:

Chapter 8. IMS and CQS Normal and Abnormal End 73

/DISPLAY QCNT TRAN MSGAGE 0

QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW

IVTNV 1 1 98218/125526 98218/125526

*98218/125620*

Following that, IMA1CQS was cancelled with the C IMA1CQS command.

The following command was entered on IMA1CTL, and produced the message

shown:

/CQCHKPT

DFS1973I CQCHKPT SHAREDQ REQUEST REJECTED FOR REASON CODE= 2

Code 2 means no CQS address space is available.

From IMA2CTL, more than two structure checkpoints were taken, causing the

CQS log records older than the last two structure checkpoints to be deleted.

The following sequence of messages was received for each structure checkpoint:

•

From the IMS side:

/CQCHKPT SHAREDQ STRUCTURE ALL

DFS058I 14:14:37 CQCHKPT COMMAND IN PROGRESS IMA2

DFS1972I CQCHKPT SHAREDQ COMMAND COMPLETE FOR STRUCTURE=IMA0MSGQ

DFS1972I CQCHKPT SHAREDQ COMMAND COMPLETE FOR STRUCTURE=IMA0EMHQ

•

From the CQS side:

CQS0220I CQS CMA2CQS STARTED STRUCTURE CHECKPOINT FOR STRUCTURE IMA0EMHQ

CQS0220I CQS CMA2CQS STARTED STRUCTURE CHECKPOINT FOR STRUCTURE IMA0MSGQ

CQS0200I STRUCTURE IMA0MSGQ QUIESCED FOR STRUCTURE CHECKPOINT CMA2CQS

CQS0200I STRUCTURE IMA0EMHQ QUIESCED FOR STRUCTURE CHECKPOINT CMA2CQS

CQS0201I STRUCTURE IMA0MSGQ RESUMED AFTER STRUCTURE CHECKPOINT CMA2CQS

CQS0201I STRUCTURE IMA0EMHQ RESUMED AFTER STRUCTURE CHECKPOINT CMA2CQS

CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0EMHQ, LOGTOKEN ...

CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0MSGQ, LOGTOKEN ...

CQS0221I CQS CMA2CQS COMPLETED STRUCTURE CHECKPOINT FOR STRUCTURE IMA0EMHQ

CQS0221I CQS CMA2CQS COMPLETED STRUCTURE CHECKPOINT FOR STRUCTURE IMA0MSGQ

IMA1CQS was then restarted and a reply cold was given to CQS0032A. The cold

reply was returned because the CQS log records were deleted from the MVS log

stream by the two structure checkpoints.

Transaction IVTNV was still in the shared-queue:

74 IMS/ESA Shared Queues Planning Guide