to set an env variable for
the user that
the trigger monitor was running under - AMQ_SIGCHILD_ACTION=YES I believe.
Regards
Darren
From: Conklin, William [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: DLQ reason code = 265
Date: Wed, 24 Sep 2003 13:19:36
Hi There,
I've seen threads discussing the reason code of 265 in the dead letter
header but I can't seem to find them now. I can't find this reason code in
any of the documentation either. Suggestions? The put application name in
the DLH is runmqtrm and the destination queue is the initiation
Bill,
I just entered your subject line into a google search: DLQ reason code = 265 and found
this.
Cheers,
Darry
DESCRIPTION OF PROBLEM FIXED FOR APAR SA92087 :
---
The MQSeries trigger monitor program (QMQM/RUNMQTRM) places
trigger messages
Bill,
Here is another item on this subject.
-Original Message-
From: Conklin, William [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 1:20 PM
To: [EMAIL PROTECTED]
Subject: DLQ reason code = 265
Hi There,
I've seen threads discussing the reason code of 265 in the dead
by: Subject: Re: DLQ reason code = 265
MQSeries List
[EMAIL PROTECTED]
en.AC.AT
09/24/2003 02:31
PM
Please respond
to MQSeries List
cmqc.h
I'm running MQSeries 5.3, CSD03 on Windows 2k.
-Original Message-
From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 2:02 PM
To: [EMAIL PROTECTED]
Subject: Re: DLQ reason code = 265
Scott,
What Version and CSD level are you running at, and what platform
PM
To: [EMAIL PROTECTED]
Subject: Re: DLQ reason code = 265
Bill,
I just entered your subject line into a google search: DLQ reason code = 265
and found this.
Cheers,
Darry
DESCRIPTION OF PROBLEM FIXED FOR APAR SA92087 :
---
The MQSeries trigger
