Ruzi,
If your QM1 subsystem has been up for an extended period of time (i.e., more than a couple of weeks), it might be that SMF record processing (both end-of-STEP & end-of-JOB) could be the culprit. One caveat - I haven't seen this problem at the 5.3 level, only at previous levels. FWIW.
Regards,
Art
Arthur C. Schanz
Operating Systems Programmer I. - Specialist
Federal Reserve Information Technology
Distributed Systems Engineering
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified Solution Designer - WebSphere MQ V5.3
(804) 697-3889
[EMAIL PROTECTED]
| Ruzi R <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]> 12/16/2003 10:42 AM
|
To: [EMAIL PROTECTED] cc: Subject: Why cannot stop the queue manager??? |
Hi all,
QM1 is on OS/390 (MQ 5.3) is in a cluster. I could
not stop the queue manager even with the FORCE option
last night. There are only 4 programs (one batch that
was not running at the time, and 3 scheduled CICS
ones) that send datagram messages from QM1 to QM2
(both in the same cluster). No messages are sent to
QM1 from any queue manager at all. I checked these
programs and they use fail_if_quiescing appropriately.
The CHIN job came down but not the MSTR, which was
using 80% of the CPU after I had issued the STOP
command. Has anyone experienced this before? What
might have been holding up the queue manager?
Any ideas/suggestions would be much appreciated.
Best regards,
Ruzi
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
