| Author |
Message
|
| c22manas |
 Posted: Tue Jun 05, 2007 5:34 am Post subject: Problem with inititation queue |
 |
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
Mq series is in AS/400 . in the queue manager log it is showing Initian queue is in use . But not sure which process is accessing it. The AS/400 Runmqtrm job is also ended previously . Any idea how to check which process was accessing it ?
The QMgr log :
AMQ8601: MQSeries trigger monitor started.
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor has been started with
initiation queue <init q name>.
Recovery . . . : None.
Technical Description . . . . . . . . : None.
-------------------------------------------------------------------------------
AMQ8610: Initiation queue in use
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor could not open the
initiation queue because the queue is open for exclusive use by another
application.
Recovery . . . : Wait until the queue is no longer in use, and try the
command again.
Technical Description . . . . . . . . : None.
-------------------------------------------------------------------------------
AMQ8602: MQSeries trigger monitor ended.
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor has ended.
Recovery . . . : None.
Technical Description . . . . . . . . : None. |
|
| Back to top |
|
 |
| rparti |
| Posted: Tue Jun 05, 2007 6:43 am Post subject: |
|
|
Voyager
Joined: 05 Oct 2005
Posts: 86
Location: U.S.A.
|
| What type of triggering are you using? Can you post the definations you are using? |
|
| Back to top |
|
|
| c22manas |
| Posted: Wed Jun 06, 2007 8:29 pm Post subject: |
|
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
Please find the triggering property of application queue.
Display MQM Queue
Message delivery sequence . . : *PTY
Harden backout count . . . . . : *YES
Trigger type . . . . . . . . . : *FIRST
Trigger depth . . . . . . . . : 1
Trigger message priority . . . : 0
Trigger data . . . . . . . . . :
I have one more query, is there any other process within MQseries who access initiation queue ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 07, 2007 2:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
An initiation queue is just a qlocal.
If some process is accessing it, it's because you've started some process to access it. The queue manager won't do any such on an initq just because it's an initq.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| c22manas |
| Posted: Thu Jun 07, 2007 2:58 am Post subject: |
|
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
| My question is whether any process internal to Mq series (i.e trigger monitor) reads or writes to initiation q ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 07, 2007 3:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| contact admin wrote: |
| My question is whether any process internal to Mq series (i.e trigger monitor) reads or writes to initiation q ? |
Strictly speaking, the trigger monitor is not an internal process but a process configured and run manually by the administrator. Things like the logging process is internal.
There's no reason why anything other than a trigger monitor would be running against an init q, but no reason why multiple jobs couldn't accidently be set to run against it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dgolding |
| Posted: Thu Jun 07, 2007 3:31 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| Even more strictly speaking and almost to point of pedantry, the INITQ is written to internally by the queue manager - when the trigger conditions on the application queue are met on a PUT, then MQ will put a message on the INITQ |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 07, 2007 3:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dgolding wrote: |
| Even more strictly speaking and almost to point of pedantry, the INITQ is written to internally by the queue manager - when the trigger conditions on the application queue are met on a PUT, then MQ will put a message on the INITQ |
Granted (and well pedanted!) but that still doesn't make the trigger monitor an internal process. Though continuing in the pedantic vein, I suppose it counts in that you don't get a message unless a monitor's got the queue open.
Moving back onto topic, I would hesitate to believe that the queue manager has the init q open for exclusive use to put init messages on it, and is causing the symptoms described. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 07, 2007 4:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd lay pints to shots that the qmgr uses either an MQPUT1, or the internal function equivalent.
I.E., it only ever has the initq open for put for exactly as long as is necessary to complete the put.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jun 07, 2007 6:20 am Post subject: |
|
|
Guest
|
"The MQSeries trigger monitor could not open the
initiation queue because the queue is open for exclusive use by another application."
Perhaps another instance of a trigger monitor already has the initq open for input-exclusive. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 07, 2007 6:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Perhaps another instance of a trigger monitor already has the initq open for input-exclusive. |
This certainly appears to be the prevaling theory.
Though the errant job need not be a trigger monitor, just a job which incorrectly references the init q.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
