/S IMA1CQS
IXL014I IXLCONN REQUEST FOR STRUCTURE IMA0EMHQ WAS SUCCESSFUL.
IXL014I IXLCONN REQUEST FOR STRUCTURE IMA0MSGQ WAS SUCCESSFUL.
IXL014I IXLCONN REQUEST FOR STRUCTURE IMA0EMHQOV WAS SUCCESSFUL.
IXL014I IXLCONN REQUEST FOR STRUCTURE IMA0MSGQOV WAS SUCCESSFUL.
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0EMHQ , LOGTOKEN ...
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0MSGQ , LOGTOKEN ...
CQS0020I CQS READY CMA1CQS
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0MSGQ , LOGTOKEN ...
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0EMHQ , LOGTOKEN ...
During the CQS restart phase, IMA1 resynchronized with CQS1:
DFS0226A CTL REGION WAITING FOR CQS (IMA1CQS ), RESPONSE TO CONNECT REQUEST -
The output for the transactions entered from IMA1 (ima1ctl/ima1CQS) were able
to reach their final destinations. The results of these commands:
/DISPLAY QCNT TRAN MSGAGE 0
/DISPLAY QCNT LTERM MSGAGE 0
both showed
QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW
*98218/084131*
8.2.2 CQS Cancelled with Transactions in SQ and Checkpoint Data Sets
Deleted
We investigated what happens when we have transactions on the shared queue
and the CQS address space is restarted after deleting the CQS checkpoint data
set.
Some transactions (response-mode, non-response-mode, conversational, and
MSC) were entered on each IMS. The queues contained the transactions shown
below:
/DISPLAY QCNT TRAN MSGAGE 0
QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW
IVTCV 1 1 98218/085911 98218/085911
IVTNO 1 1 98218/085931 98218/085931
IVTNV 1 1 98218/085945 98218/085945
PART 2 2 98218/090101 98218/090112
*98218/090205*
Both CQSs were abended with the MVS cancel command:
/C IMA1CQS
CQS0105I INTF CLEANUP SUCCESSFUL:CLIENT=IMA1
CQS0105I INTF CLEANUP SUCCESSFUL:CLIENT=IMA2
After the CQSs went down, new logons were rejected but it was possible to enter
IMS commands such as
/DISPLAY TRANSACTION xx
Chapter 8. IMS and CQS Normal and Abnormal End 71
/DISPLAY A
/DISPLAY LTERM xxx
Shared queue commands were not available:
/DISPLAY QCNT TRAN MSGAGE 0
DFS1975 09:04:19 COMMAND REJECTED AS CQS IS NOT AVAILABLE
Trying to enter new transactions we got:
DFS070 09:06:44 UNABLE TO ROUTE MESSAGE
All the checkpoint data sets were deleted for the CQS address spaces. During
IMA1CQS and IMA2CQS restart, message CQS0031A was received and we
confirmed the use of the log token found by CQS in the shared-queue structures.
Confirmation was indicated by these messages:
/S IMA1CQS
*133 CQS0031A CONFIRM CQS RESTART FOR STRUCTURE IMA0MSGQ CMA1CQS
*134 CQS0031A CONFIRM CQS RESTART FOR STRUCTURE IMA0EMHQ CMA1CQS
R 133,CONFIRM
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0MSGQ
R 134,CONFIRM
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0EMHQ
CQS0020I CQS READY CMA1CQS
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0MSGQ
CQS0030I SYSTEM CHECKPOINT COMPLETE, STRUCTURE IMA0EMHQ
IMS and CQS resynchronized through DFS0226A.
After IMA1CQS was started, it was possible to inquire on the shared-queue from
IMA1, as follows:
/DISPLAY QCNT TRAN MSGAGE 0
QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW
IVTCV 1 1 98218/085911 98218/085911
IVTNO 1 1 98218/085931 98218/085931
IVTNV 1 1 98218/085945 98218/085945
PART 2 2 98218/090101 98218/090112
*98218/091205*
The same procedure was used to restart CQS2:
72 IMS/ESA Shared Queues Planning Guide

Get IMS/ESA Shared Queues: A Planning Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.