DB, another hint. You wrote "The MQDLH reason code was 2052". 2052 means "MQRC_Q_DELETED".
Hubert > -----Ursprüngliche Nachricht----- > Von: MQSeries List <[email protected]> > Gesendet: 16.03.06 15:07:59 > An: [email protected] > Betreff: Re: cmdserver to dlq ? > It could be that the queue exists but the QMgr attribute for the dlq is not > set (thus the command server doesn't know what dlq to use). > > Either way, you need to specify the dlq in the QMgr attributes *and* make > sure it exists. > > When I use admin tools and they crash every now and then (or I exit MO71 too > quick, just after doing a refresh), then we get alarms for messages going > onto the SYSTEM.DEAD.LETTER.QUEUE. > > When you create a queue manager you need to specify it to use the SDLQ which > is created by default, but not referenced. You can ALTER QMGR to set the > DEADQ correctly once it is created however. > > HTH > > Regards > > John Scott > IBM Certified Specialist - MQSeries > ARG Infrastructure Services - Middleware > > > > -----Original Message----- > From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Hubert Kleinmanns > Sent: 16 March 2006 13:53 > To: [email protected] > Subject: Re: cmdserver to dlq ? > > > DB, > > your first question: A command server may put a msg to a DLQ, when a remote > admin tool (e. g. MQ-Explorer, MO71 ...) has been started a request (e. g. a > queue list) but ends, before the command server could process this request. > Generally the admin tool creates a temporary reply queue and deletes it, when > the admin tool ends. So the command server tries to put a msg to a > non-existing queue. > > Your second question: It seems, that you specified a DLQ in the QMgr > attribute DEADQ, but did not create this queue itself. > > Regards > Hubert > > > > -----Ursprüngliche Nachricht----- > > Von: MQSeries List <[email protected]> > > Gesendet: 15.03.06 18:12:48 > > An: [email protected] > > Betreff: Re: cmdserver to dlq ? > > > > Hi all, > > > > New problem, never seen before ...anyone else run into this ? > > > > 3/15/2006 11:04:30 > > AMQ6184: An internal WebSphere MQ error has occurred on queue manager > > W2KLAB4D. > > > > EXPLANATION: > > An error has been detected, and the WebSphere MQ error recording routine has > > been called. The failing process is process 2368. > > ----------------------------------------- > > I found that 2368 is amqzlaa0.exe > > > > That particular Qmgrs AMQ log shows: > > > > 03/15/2006 10:36:31 > > AMQ8507: Command server MQPUT1 request for an undelivered message failed > > with reason code 2085. > > > > EXPLANATION: > > An attempt by the command server to put a message to the dead-letter queue, > > using MQPUT1, > > failed with reason code 2085. The MQDLH reason code was 2052. > > ACTION: > > None. > > ----------------------------------------- > > > > There are no messages on the DLQ ... why would a Command server be trying to > > PUT1 on the DLQ ? > > > > Meanwhile, MQ Explorer can't access queues on this Qmgr. The cmdline works > > just fine though. > > > > Any help is appreciated, > > > > /DB > > > > Instructions for managing your mailing list subscription are provided in > > the Listserv General Users Guide available at http://www.lsoft.com > > Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html > > -- > Hubert Kleinmanns > Beratung / Schulung / Projektleitung > > Tel.: +49 (0) 60 78 / 7 12 21 > Fax: +49 (0) 60 78 / 7 12 25 > Mobil: +48 (0) 178 / 6 97 22 54 > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html > > - -------------------------------------------------------------- > > Check our latest prices and full range at http://www.argos.co.uk > > The information contained in this message or any of its attachments may be > privileged and/or confidential, and is intended exclusively for the > addressee. Unauthorised disclosure, copying or distribution of the contents > is strictly prohibited. > > The views expressed may not be official policy, but the personal views of the > originator. > > If you have received this message in error, please advise the sender by using > the reply facility in your e-mail software. > > All messages sent and received by Argos Ltd are monitored for viruses, > high-risk file extensions, and inappropriate content. > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +48 (0) 178 / 6 97 22 54 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
