I am not too sure about ZOS, so my thinking may be completely wrong, but... Based on Unix mechanisms...
The original program that crashed, was was the timeout value for the MQGET when it crashed? If you set this to unlimited, then the Queue Manager agent waiting for a message on the application's behalf will not realise that the app has crashed until either the MQGET times out (never happens if unlimited expiry), or a message arrives. In this situation, you then started another copy of the application, making the queue open twice. When a message arrives, say the first (now crashed application) gets the message. The Queue Manager agent then realises that your application has gone away and rolls back the transaction, putting the message back on the queue. The agent then exits (closing handles as it goes) and the second copy of the application gets the messages, processes it and then terminates cleanly (closing handles as it goes). Thus the open input counts to your queues drop to 0 and it "appears" that the second application grabs the handle of the first when it doesn't. Could this explain your observations or am I clsoe but no cigar... Regards John. -----Original Message----- From: Gary P. Klos [mailto:[EMAIL PROTECTED] Sent: 14 August 2003 16:00 To: [EMAIL PROTECTED] Subject: MQ Connection Handle Assignment? We are running MQ version 5.3 on ZOS. We had a situation where a queue was left open for input because of a program crash. The program never got to do a disconnect. This program was a Natural program running under COM-PLETE. So basically that queue was left open for input for two days. Today someone ran a Natural program and put a message to a queue. The message on the queue had the userid of the person who's program crashed on the user identifier. Also the queue that was left open for input was no longer open. I think what happened was when the person ran a program today, he picked up the handle that was left connected from the previous program crash and ended up using that userid and then when he disconected it closed both queues. How is it possible that MQ grabbed the same handle, when one was open? The program running runs as a server program to the queue manager and connects with MQCONN, which defaults to a nonshared handle. Thanks, Gary 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 ********************************************************************** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using your reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed. ********************************************************************** 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
