Frank, Prasath, I did a search on www.ibm.com for the phrase MQFB_APPL_CANNOT_BE_STARTED. The first result returned is for the APAR reporting this problem. There are a number of PTF cover letters that include the fix for this APAR, depending on the platform you are on.
If you have a PMR open with IBM, I am sure they told you to ensure that the applicable PTFs are installed on your target systems; if not, install them and attempt to reproduce the problem. One situation I ran into that caused this problem was an attempt to start the triggered application a second time, with the same process name (OpenVMS, the target system, didn't allow for this) and so the application failed to start. I had to modify the trigger definition to trigger FIRST, not EVERY, and modified the code to handle multiple passes until it exhausted the input queue. The code I was given to install was written to handle a single message, on the expectation of low messages volume. Our implementation suddenly starting triggering LOTS of times, and so we were operating outside the design specs for the original appl. Mr. Murphy was then reassigned to his next assignment :-). ====================== David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY (516) 481-6440 [EMAIL PROTECTED] -----Original Message----- From: Bright, Frank [mailto:[EMAIL PROTECTED] Sent: Friday, July 02, 2004 9:35 AM To: [EMAIL PROTECTED] Subject: Re: MQ issues with dead letter queue I don't have the answer but we see it too. We having trouble reproducing the error on our test system to trace it as requested by IBM. It only occurs occasionally on some systems. X'109' or MQFB_APPL_CANNOT_BE_STARTED is the MQDLH reason code. Thanks Frank -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of BALAKRISHNAN, PRASATH (SBCSI) Sent: Thursday, July 01, 2004 6:13 PM To: [EMAIL PROTECTED] Subject: MQ issues with dead letter queue Hello, For the last several days we have been accumulating large numbers of trigger messages in the Dead Letter Queue. We added this in the .profile which was suggested in one of the forums as a possible solution # For Web Sphere MQ 5.3 SP 4 export AMQ_SIGCHLD_SIGACTION=YES export MQ_SIGCHLD_SIGACTION=YES Still it did not work. Can you help me in finding a possible solution Thanks Prasath Balakrishnan ===== David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY (516) 481-6440 [EMAIL PROTECTED] 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
