There are three types of shutdown:
In the procedures that follow, we use a sample queue manager name of QMgr1 and a sample subsystem name of SUBX. Replace these with your own.
RCDMQMIMG OBJ(*ALL) OBJTYPE(*ALL) MQMNAME(QMgr1) DSPJRNDTA(*YES)
ENDMQM MQMNAME(QMgr1) OPTION(*CNTRLD)If QMgr1 does not end, the channel or applications are probably busy.
ENDMQM MQMNAME(QMgr1) OPTION(*IMMED) ENDCCTJOB(*YES) TIMEOUT(15)
ENDMQM MQMNAME(QMgr1) OPTION(*IMMED)If QMgr1 does not end, the channel or applications are probably busy.
ENDMQM MQMNAME(QMgr1) OPTION(*IMMED) ENDCCTJOB(*YES) TIMEOUT(15)
ENDMQM MQMNAME(QMgr1) OPTION(*IMMED)If QMgr1 does not end, continue with step 3 providing that:
ENDSBS SUBX *IMMEDIf this command fails to complete, shut down all queue managers, using the unplanned shutdown procedure, and IPL your machine.
Do not use ENDJOBABN for MQSeries(R) or WebSphere(R) MQ jobs that fail to end as result of ENDJOB or ENDSBS, unless you are prepared to IPL your machine immediately after.
STRSBS SUBX
ENDMQM MQMNAME(QMgr1) OPTION(*IMMED) ENDCCTJOB(*YES) TIMEOUT(10)
STRMQM MQMNAME(QMgr1)
If this fails, and you:
Tidy up MQSeries or WebSphere MQ shared memory by executing:
ENDMQM MQMNAME(*ALL) OPTION(*IMMED) ENDCCTJOB(*YES) TIMEOUT(15)
before repeating step 5.
If the queue manager restart takes more than a few seconds, WebSphere MQ will add status messages intermittently to the job log detailing the start up progress. For more information on these messages see WebSphere MQ Messages.
If you still have problems restarting your queue manager, contact IBM(R) support. Any further action you might take could damage the queue manager, leaving MQSeries or WebSphere MQ unable to recover.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
quiesone |