Hello,

I am facing the situation when the SYSTEM.COMMAND.REPLY.xxx queue is not available after the QMGR restart even if the model queue is defined with DEFTYPE(PERMDYN).

There are all details:

MSTR output >>>

08.13.05 S0950641  CSQR001I !QDS2 RESTART INITIATED

08.13.06 S0950641  CSQR005I !QDS2 RESTART - FORWARD RECOVERY COMPLETE -  706

   706             IN COMMIT=0, INDOUBT=0                                   

08.13.06 S0950641  CSQR006I !QDS2 RESTART - BACKWARD RECOVERY COMPLETE -  711

   711             INFLIGHT=0, IN BACKOUT=0                                 

08.13.07 S0950641  CSQR002I !QDS2 RESTART COMPLETED

08.13.07 S0950641  CSQ3018I !QDS2 CSQ3RRSR RRS synchronization complete        

08.13.07 S0950641  S QDS2CHIN,JOBNAME=QDS2CHIN                                 

08.13.07 S0950641  CSQM138I !QDS2 CSQMSCHI CHANNEL INITIATOR STARTING          

08.13.08 S0950641  CSQ9022I !QDS2 CSQXCRPS ' START CHINIT' NORMAL COMPLETION   

08.13.26 S0950641  CSQN207I !QDS2 COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE 

08.13.26 S0950641  CSQN203I !QDS2 QUEUE  828                                   

   828             SYSTEM.COMMAND.REPLY.D72282E51C457957, MQCC=2 MQRC=2085      

   828             (MQRC_UNKNOWN_OBJECT_NAME)                                  

08.23.05 S0950641  CSQY220I !QDS2 CSQSCTL Queue manager storage usage:  350    

   350             local storage: used 613MB, free 898MB: above bar: used 236MB,

CHIN output >>>

In fact, I do not understand why the dynamic queue is not available when it is defined using PERMDYN model queue. Could you, please, help me to prevent this issue in the future?

Thank you!

Best regards,
Radek

------------------------------
Radek Vanek
IT Specialist for zSeries IBM MQ, DB2 & DBA
IBM Certified Specialist & Database Administrator
IBM Client Innovation Centre Brno Czech Republic
Email: Radek_Vanek@cz.ibm.com
------------------------------

Looking at the times:-

08.13.23 S0950652  +CSQX037E !QDS2 CSQXDPSC Unable to get message from  808    

   808              SYSTEM.COMMAND.REPLY.D72282E51C457957, MQCC=2 MQRC=2033    

   808              (MQRC_NO_MSG_AVAILABLE)         

vs

08.13.26 S0950641  CSQN207I !QDS2 COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE 

08.13.26 S0950641  CSQN203I !QDS2 QUEUE  828                                   

   828             SYSTEM.COMMAND.REPLY.D72282E51C457957, MQCC=2 MQRC=2085      

   828             (MQRC_UNKNOWN_OBJECT_NAME)                                  

it looks like the command that was issued using the SYSTEM.COMMAND.REPLY.D72282E51C457957 did not wait long enough for its reply. It reported that it did not get a reply message at 08.13.23, and then I assume deleted the temporary queue - which is why, even though it was a PERMDYN it is not there anymore. The 'application' using it (in this case some part of MQ) closed and deleted it when it was finished with it.

Then at 08.13.26, the command server finally got around to replying and found that the reply queue was no longer there. This suggests that the 'application' (some part of MQ) making the request did not align the expiry in it's request message with the length of time it was willing to wait for the reply.

The CSECT from the CSQX037E message shows 'CSQXDPSC' which indicates that the component in question was the Distributed Pub/Sub task in the CHINIT. Given that it is a component of MQ that is having this issue, I would suggest raising a support case with IBM.

If you don't use the Queued Pub/Sub Daemon, you could turn it off using:-

ALTER QMGR PSMODE(COMPAT)

Cheers,
Morag

------------------------------
Morag Hughson
MQ Technical Education Specialist
MQGem Software Limited
------------------------------