It turned out that for whatever reason, we had a problem triggering a exe
on a mapped network drive.
So, we created a shortcut on a local drive that pointed to the exe on the
mapped drive and triggering
started to work. Not sure why MQ could not start the process on the
networked mapped drive. We are using
a W2k domain controller and thats new to us.
Benjamin Zhou
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: MQSeries cc:
List Subject: Re: W2K Trigger monitor
triggers going to DLQ
<MQSERIES@AKH-WIE
N.AC.AT>
02/18/03 10:04 AM
Please respond to
MQSeries List
I'm having similar problem, just no msg to the DLQ. When I run the trigger
monitor in the foreground, it triggered without any problem. But if I start
the trigger monitor as MQ Service, simply nothing happened, although it did
try to trigger.
Benjamin Zhou
State Street
-----Original Message-----
From: Matt Gurney [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 11:39 AM
To: [EMAIL PROTECTED]
Subject: Re: W2K Trigger monitor triggers going to DLQ
Another tip is to run the trigger monitor in the foreground, rather
than as an MQSeries service. You start it up with :
Usage: runmqtrm [-m QMgrName] [-q InitQ]
Remember to disable the MQSeries service trigger monitor to ensure
your foreground trigger monitor does the work.
This way you see the trigger messages being processed which can
assist with debugging.
Matt Gurney
|-+-+-------------------------------+-+-----------------------------------|
| | | | | |
| | | "Stephan C. Moen" | | |
| | | <[EMAIL PROTECTED]> | | |
| | | TPSGI.COM | | To: |
| | | Sent by: MQSeries List | | [EMAIL PROTECTED] |
| | | <[EMAIL PROTECTED]> | | cc: |
| | | | | |
| | | | | |
| | | 17/02/2003 16:14 | | |
| | | Please respond to MQSeries | | |
| | | List | | |
| | | | | Subject: |
| | | | | Re: W2K Trigger monitor |
| | | | | triggers going to DLQ |
| | | | | |
|-+-+-------------------------------+-+-----------------------------------|
What I have done in the past is dump the contents of the message
using one
of the sample programs provided when you install MQM on the platform
in
question. On a Windows system, this would be something like <Drive
Letter>:\Program Files\IBM\MQSeries\Tools\C\Samples\Bin\amqsbcg.
This
utility will view or browse the message on the DLQ, dumping the
contents of
that message to your console. It will NOT read the message off the
queue.
In the body of the message dumped, review the 6th word (11th and 12th
bytes). Since the error code is in hexadecimal, if you have a UNIX
machine
around, simply do the following at the command line:
bc
ibase=16
07EE
CNTRL-D
BC is a binary calculator. ibase means BC will read its input in
base 16
vs. base 10. All input values need to be in UPPERCASE. The decimal
equivalent of 07EE is 2030. Now take that value and look it up
either in
MQSeries Information Center or use the following command on UNIX
systems -
grep 2030 /usr/include/cmqc.h. The returned string of the last
example will
give you why the message got redirected to the DLQ. Other codes you
may
find in the DLQ are as follows:
HEX DECIMAL ERROR DESCRIPTION
07EE 2030 Message Too Big for Queue
07EF 2031 Message Too Big for Queue Manager
0805 2053 Queue Full
0835 2101 MQ Object Damaged
08AA 2218 Message Too Big for Channel
Stephan C. Moen
[EMAIL PROTECTED]
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of
Wesley Shaw
Sent: Monday, February 17, 2003 7:16 AM
To: [EMAIL PROTECTED]
Subject: W2K Trigger monitor triggers going to DLQ
I have a triggered process where the trigger message is going to the
DLQ.
Below is the message header.
I am trying to figure out the reason code. Anybody decode that for
me
quicker than I ?
(Embedded image moved to file: pic04664.pcx)
Wesley Shaw
OJRP 10th Floor
Work: 804 771 3589 (736-3589)
Pager: 888 436 2805 Mobile 804 512 5260
_________________________________________________________________
For your protection, this e-mail has been scanned for known
viruses and damaging content by http://GATEWAYDEFENDER.com
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
