Re: Trigger Messages to DLQ

[Bright, Frank]

Title: Message

This is what I have within my environments.  If you use crontab scripts to perform a start of your trigger monitors, then you must export the same variable within the crontab script.

 

# Defect 72854 - APAR IY39949 - trigger mesg X109 - MQFB_APPL_CANNON_BE_STARTED
        export AMQ_SIGCHLD_SIGACTION=YES

-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Driscoll Tom - Princeton
Sent: Monday, November 29, 2004 11:53 AM
To: [EMAIL PROTECTED]
Subject: Re: Trigger Messages to DLQ

Thanks !

---

From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Mike Krueger
Sent: Monday, November 29, 2004 9:24 AM
To: [EMAIL PROTECTED]
Subject: Re: Trigger Messages to DLQ

Had a similar problem, try exporting the following environment variables before starting your trigger monitor.

 

#                                                                     

# set variables in attempt to resolve MQFB_APPL_CANNOT_BE_STARTED error

#                                                                     

export AMQ_SIGCHLD_SIGACTION=YES                                      

export MQ_SIGCHLD_SIGACTION=YES                                       

 

-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Driscoll Tom - Princeton
Sent: Monday, November 29, 2004 8:40 AM
To: [EMAIL PROTECTED]
Subject: Trigger Messages to DLQ

 

This is a Microfocus COBOL program on HP-UX 11.11 MQSeries v5.3.
I have a triggered application with the triggertype set to EVERY. The triggered program is written to process one message and then end (it's a very low volume application). Everything runs fine, but periodically a trigger message gets written to the Dead Letter Queue with the associated initiation queue as the intended destination, and RUNMQTRM as the application. The reason code in the DLQ message header appears to be a hex 00000109 (??). I can't find a reason code that matches this.

There are no associated error messages written to the AMQERR01.LOG or FDC entries. From a user perspective, everything is processing fine.

Any ideas ?

---

This e-mail message and any attachments contain confidential information from Medco. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.