/DISPLAY Q BALGRP
BALGRP NO.RGNS MSG CT ENQ COUNT DEQ COUNT
DFSIVP4 1 5 6 1
*98212/083622*
/DISPLAY QCNT BALGRP MSGAGE 0
QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW
*98212/083635*
/CQQUERY STATISTICS STRUCTURE ALL
STRUCTURE NAME LEALLOC LEINUSE ELMALLOC ELMINUSE LE/EL
IMA0MSGQ 126 12 127 12 0001/0001
IMA0MSGQOV N/A N/A N/A N/A N/A
IMA0EMHQ 126 4 127 4 0001/0001
IMA0EMHQOV N/A N/A N/A N/A N/A
*98212/083646*
Once replied to the TADD WTOR, all the transactions on the IMA1 local
balancing group were processed:
/DISPLAY Q BALGRP
BALGRP NO.RGNS MSG CT ENQ COUNT DEQ COUNT
DFSIVP4 1 0 6 6
*98212/084247*
/DISPLAY QCNT BALGRP MSGAGE 0
QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW
*98212/084329*
/CQQUERY STATISTICS STRUCTURE ALL
STRUCTURE NAME LEALLOC LEINUSE ELMALLOC ELMINUSE LE/EL
IMA0MSGQ 126 12 127 12 0001/0001
IMA0MSGQOV N/A N/A N/A N/A N/A
IMA0EMHQ 126 4 127 4 0001/0001
IMA0EMHQOV N/A N/A N/A N/A N/A
*98212/084349*
11.4 On the Full-Function Shared Queue Initial Program Load of an MVS with
Messages
During our test cases we tried to determine CQS and IMS behavior after a whole
system outage. For this reason we did three IPL tests:
•
The first test was done after cancelling the address spaces (CQS1 and IMA1)
belonging to the MVS that was about to receive the IPL.
•
The second test was run after cancelling only CQS1, with IMA1, still up at IPL
time.
•
The third test was executed by an IPL of the MVS while leaving both CQS
and IMS up.
Chapter 11. Miscellaneous Shared-Queue Tests 107
We report only the CQS messages; IMS was emergency restarted as usual. Ten
messages were queued to the full-function shared queue (IMA0MSGQ). The
CQS message is
/DISPLAY QCNT TRANSACTION MSGAGE 0
QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW
IVTNO 10 10 98216/072521 98216/072533
*98216/072612*
Both CQS1 and IMA1 were MVS cancelled and an IPL performed.
These messages were issued by CQS1 upon restart:
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 ...
Operation was as expected: a system checkpoint was taken at CQS startup and
IMS synchronization was performed. The full-function shared-queue still
contains the ten messages that were previously queued.
The test was repeated, each time with ten messages on the full-function shared
queue (IMA0MSGQ). CQS1 was cancelled and a repeat IPL of MVS was
performed while IMA1 was still up and running.
This is what we saw when CQS1 restarted:
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 ...
We performed a repeat IPL of the system with both CQS1 and IMA1 up and
running and we got the same CQS results.
Operation was as expected: a system checkpoint was taken at CQS startup and
IMS synchronization was performed with the full-function shared-queue still
containing the ten messages.
/DISPLAY QCNT TRANSACTION MSGAGE 0
QUEUENAME QCNT-TOTAL QCNT-AGED TSTMP-OLD TSTMP-NEW
IVTNO 10 10 98216/072521 98216/072533
*98216/092113*
108 IMS/ESA Shared Queues Planning Guide
Get IMS/ESA Shared Queues: A Planning Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
