| Author |
Message
|
| c22manas |
 Posted: Wed May 02, 2007 12:42 am Post subject: Problem with Mq triggering |
 |
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
OS - AS/400
Mq version - 5.2
Problem - The initiation queue GET option is getting changed to inhibit/no . Messages are getting piled up in application queue. Only after manually changing the GET property of initq to yes and starting the trigger monitor manually by strmqmtrm the messages are flowing . But the messages are not picked up automatically . Is there any suggestion for this ? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 02, 2007 1:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ugrade? If the numbering is the same for AS/400 (and I don't know that it is) v5.2 is out of support.
Moving to your problem - if you're saying that having restarted the trigger monitor the application to read messages was not triggered, I suspect the trigger type was set to FIRST. If there are messages already in the queue the trigger will not fire.
Once the queue's been read to empty, the next message should cause a trigger to be raised.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| c22manas |
| Posted: Wed May 02, 2007 1:58 am Post subject: Problem with Mq triggering |
|
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
The trigger type is FIRST.
If the trigger fail to initiate at the time of first message put in the appl Q will not it not trigger automatically when the message depth > 1 ? Is there any log where the failure of triggering failure reason is mentioned ?
Why the MQGET option in initiation queue is being inhibited by the WMQ ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 02, 2007 2:08 am Post subject: Re: Problem with Mq triggering |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| contact admin wrote: |
The trigger type is FIRST.
If the trigger fail to initiate at the time of first message put in the appl Q will not it not trigger automatically when the message depth > 1 ? |
No - FIRST only fires when queue depth goes from 0 -> 1
| contact admin wrote: |
Is there any log where the failure of triggering failure reason is mentioned ?
Why the MQGET option in initiation queue is being inhibited by the WMQ ? |
I'd guess these are linked - the triggered program failed, rolled back and the queue was inhibited to prevent further messages.
Triggering is not failing, it's that the conditions are not being met. You'll find these in the application programming guide.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| c22manas |
| Posted: Wed May 02, 2007 2:53 am Post subject: Problem with Mq triggering |
|
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
Good suggestion.
In our case the triggered process is an mqm process which internally calls as follows:
JOB(<job name>) USER(MQWCDC) JOBD(< job desc>) JO
BQ(<some value>) CURLIB(*CURRENT) INLLIBL(*JOBD) LOGCLPGM(*YES) LOG(3 *JOBD *MSG)
Hence the failure information should be avaialble with the Job log - right ?
Or in the Queue manager error log ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 02, 2007 2:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
As I indicated above, I'm not too familiar with AS/400 but on other platforms I'd look in the application logging rather than the queue manager one.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| c22manas |
| Posted: Wed May 02, 2007 10:25 pm Post subject: Problem with Mq triggering |
|
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
Strangely enough, the triggered job log shows no error. After the initiation queue is manually made ON for MQGET, it shows message with MQTrig format.
Is there any other reason for the failure ? in the Queue manager error log only following message
==============================================
05/03/07 00:26:25
AMQ8612: Waiting for a trigger message
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor is waiting for a message to
arrive on the initiation queue.
Recovery . . . : None.
Technical Description . . . . . . . . : None.
-------------------------------------------------------------------------------
05/03/07 00:26:33
AMQ8614: Initiation queue not enabled for input.
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor cannot read from the
initiation queue because input is not enabled.
Recovery . . . : Ask your systems administrator to enable the queue for
input.
Technical Description . . . . . . . . : None.
-------------------------------------------------------------------------------
05/03/07 00:26:33
AMQ8602: MQSeries trigger monitor ended.
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor has ended.
Recovery . . . : None.
Technical Description . . . . . . . . : None.
===============================================
Any suggestions ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 03, 2007 12:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I think you need someone more familiar with the nuts & bolts of triggering on AS/400 than me.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 03, 2007 11:44 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I would have thought that if the initq is get disabled your trigger monitor would recognized the fact and quit???
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu May 03, 2007 5:00 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| fjb_saper wrote: |
| I would have thought that if the initq is get disabled your trigger monitor would recognized the fact and quit??? |
It did didn't it?
| Code: |
05/03/07 00:26:33
AMQ8614: Initiation queue not enabled for input.
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor cannot read from the
initiation queue because input is not enabled.
Recovery . . . : Ask your systems administrator to enable the queue for
input.
Technical Description . . . . . . . . : None.
-------------------------------------------------------------------------------
05/03/07 00:26:33
AMQ8602: MQSeries [b]trigger monitor ended[/b].
EXPLANATION:
Cause . . . . . : The MQSeries trigger monitor has ended.
Recovery . . . : None.
Technical Description . . . . . . . . : None. |
|
|
| Back to top |
|
|
| c22manas |
| Posted: Sun May 06, 2007 9:16 pm Post subject: |
|
|
Novice
Joined: 02 Jan 2007
Posts: 20
|
| In As/400 is there any separate log for Runmqmtrm ? if yes, what is the path for that ? |
|
| Back to top |
|
|
| skopparapu |
| Posted: Thu Dec 24, 2015 9:28 pm Post subject: |
|
|
Novice
Joined: 04 Mar 2014
Posts: 19
|
We do have something called as spool files which store the runmqtrm logs. Type in WRKSPLF and press F4. Give the user as "QMQM" and press ENTER.
It gives you all the spool files with time stamp.  |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Dec 25, 2015 12:10 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| skopparapu wrote: |
We do have something called as spool files which store the runmqtrm logs. Type in WRKSPLF and press F4. Give the user as "QMQM" and press ENTER.
It gives you all the spool files with time stamp. |
Why did you think re-opening an EIGHT year old post would add anything to the disussion that took place in 2007?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
