The program runs in the background (asynchronously). My understanding is
that once MQ forks the process, it has no idea what rc is returned by the
application.
Marc Verhiel
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
NDLE.COM> cc:
Sent by: Subject: Re: DLQ problem
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
07/24/2003 04:36
PM
Please respond
to MQSeries List
>>>
I have a strange one here. I run a triggered program, which runs without
any problems. But, I still get a DLQ message:
00000000: 444C 4820 0000 0001 0000 0109 5359 5354 'DLH ........SYST'
00000010: 454D 2E44 4546 4155 4C54 2E49 4E49 5449 'EM.DEFAULT.INITI'
00000020: 4154 494F 4E2E 5155 4555 4520 2020 2020 'ATION.QUEUE '
As per the DLQ reason code, MQ had a problem starting the application. The
application is started asynchronously in the background, so the application
does not pass back a return code. It's almost as if the MQ is getting a
bad rc when it forks the process, which runs perfectly fine in the
background. Anyone experience this?
OS: HP-UX11
MQ: 5.3
CSD: 4
<<<
Ensure the triggered app ends with a return code of 0. If is ends with a
non zero return code then the trigger monitor will place the trigger
message on the DLQ with a reason of MQFB_APPL_CANNOT_BE_STARTED x'109'.
Marc Verhiel
O:604 904 9979
C:604 351 9096
F:604 904 9978
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
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
