There was an efix for CSD3 on AIX - efix IY39939 - don't know whether it got included in CSD4 or not - the 265s were going to the DLQ even though the triggered app was exiting with rc 0 - the same APAR may exist on the Windows codebase as well.
After the APAR was applied I think you then had 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 -0500
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 queue defined for the local queue. Thanks Bill C.
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
_________________________________________________________________ Find a cheaper internet access deal - choose one to suit you. http://www.msn.co.uk/internetaccess
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
