| Author |
Message
|
| harnesshg |
 Posted: Fri Mar 17, 2006 7:06 am Post subject: MQFB_APPL_CANNOT_BE_STARTED--> more info reqd refer last |
 |
|
Newbie
Joined: 07 Mar 2006
Posts: 7
|
I am new to MQ.
What are the various typical conditions under which this message 'MQFB_APPL_CANNOT_BE_STARTED' gets put into DEADLETTER queue?
Last edited by harnesshg on Sat Mar 18, 2006 1:43 am; edited 1 time in total |
|
| Back to top |
|
 |
| wschutz |
| Posted: Fri Mar 17, 2006 7:10 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Usually when a trigger monitor cannot start an application, like the appl name is wrong .... from the "InfoCenter" :
| Quote: |
MQFB_APPL_CANNOT_BE_STARTED
An application processing a trigger message cannot start the application named in the ApplId field of the trigger message (see MQTM - Trigger message).
On z/OS, the CKTI CICS transaction is an example of an application that processes trigger messages
|
_________________
-wayne |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Fri Mar 17, 2006 7:10 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
Well, this is rather self explaining.
This occures whenever the application that is supposed to be started cannot be started.
Possible causes could be:
- permission issues
- wrong filepath
- the application does not exist
and many more. Read the documentation to get more information on this.
cheers
Sebastian |
|
| Back to top |
|
|
| harnesshg |
| Posted: Sat Mar 18, 2006 1:43 am Post subject: |
|
|
Newbie
Joined: 07 Mar 2006
Posts: 7
|
| say the application has been triggered by the MQ and the application does not respond inspite of everything being proper(we faced this sort of a situation) what will be the message put on the SYSTEM.DEAD.LETTER.QUEUE or any other message indicating this condition. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Mar 18, 2006 6:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the application starts, but goes into an infinite loop and does not ever quit... then nothing will ever show up in MQ to indicate this - other than that the dequeue rate on the queue is zero and (perhaps) that the queue has a positive open input count.
Depending on how your process is defined in MQ, this could in theory also cause your trigger monitor to sit forever waiting for the application to finish before it will start another program.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 18, 2006 9:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And if you use Java you have to have set the right environment parameters before starting the trigger monitor or your VM might just hang...
Check out the triggering java url I put in the java thread. It covers pretty much everything...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jsware |
| Posted: Mon Mar 20, 2006 5:07 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
If you search IBM's site for the MQFB code, you'll see that depending upon the platform and version of MQ you are using, if you get the trigger monitor to start an application in the "foreground" (so the trigger monitor waits for the program to end) then if that program exits with a non-zero return code, the trigger monitor thinks that application has failed and records the trigger message on the DLQ.
I guess the moral is to always start the program in the background by using an & suffix on the Unix platforms and the "start " prefix on Windows.
The notes on IBM's site indicate that it has been fixed in various releases/fixpacks, but I have still observed this happening. I did a quick search of the manuals but couldn't find anything that indicates whether the trigger monitor should catch and log the return code from a process it starts.
HTH
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
|
|
