Re: W2K Trigger monitor triggers going to DLQ
Title: RE: W2K Trigger monitor triggers going to DLQ Hi Glen I did tried the same approach. it didn't work as well. I'm pursuing this with IBM, will let you know the result if I get the solution from IBM. regards, Benjamin Zhou State Street. -Original Message- From: Glen Larson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 18, 2003 2:13 PM To: [EMAIL PROTECTED] Subject: Re: W2K Trigger monitor triggers going to DLQ Benjamin, I saw a problem like that on NT, (this was 5.2, csd04), using the SYSTEM.DEFAULT.INITIATION.QUEUE. I created a new INITQ, and it worked fine. I got side-tracked because of some higher priority work, and have not gone back to pursue it further. glen larson zurich north america Benjamin Zhou <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 02/18/2003 09:04:32 AM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: W2K Trigger monitor triggers going to DLQ 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 || MQSERIES@AKH-Wi| ||| <[EMAIL PROTECTED]|| en.AC.AT | ||| > || 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 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 deco
Re: W2K Trigger monitor triggers going to DLQ
Benjamin, I saw a problem like that on NT, (this was 5.2, csd04), using the SYSTEM.DEFAULT.INITIATION.QUEUE. I created a new INITQ, and it worked fine. I got side-tracked because of some higher priority work, and have not gone back to pursue it further. glen larson zurich north america Benjamin Zhou <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 02/18/2003 09:04:32 AM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: W2K Trigger monitor triggers going to DLQ 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 || MQSERIES@AKH-Wi| ||| <[EMAIL PROTECTED]|| en.AC.AT | ||| > || 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 :\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:/
Re: W2K Trigger monitor triggers going to DLQ
I believe you also can get that reason code if the application does start, but returns a non-zero result code, reflecting an error condition back to the trigger monitor. > -Original Message- > From: Wesley Shaw [SMTP:[EMAIL PROTECTED]] > Sent: Monday, February 17, 2003 5: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 << File: pic04664.pcx >> 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
Re: W2K Trigger monitor triggers going to DLQ
I had a the same problem. It was a security issue. -Original Message- From: Wesley Shaw [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 18, 2003 9:37 AM To: [EMAIL PROTECTED] Subject: Re: W2K Trigger monitor triggers going to DLQ 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: MQSeriescc: List Subject: Re: W2K Trigger monitor triggers going to DLQ 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 :\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: HEXDECIMAL ERROR DESCRIPTION 07EE 2030Message Too Big for Queue 07EF 2031Message Too Big for Queue Manager 0805 2053Queue Full 0835 2101MQ Object Damaged 08AA 2218Message Too Big for Channel Stephan C. Moen [EMAIL PROTECTED]
Re: W2K Trigger monitor triggers going to DLQ
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: MQSeriescc: List Subject: Re: W2K Trigger monitor triggers going to DLQ 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 :\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: HEXDECIMAL ERROR DESCRIPTION 07EE 2030Message Too Big for Queue 07EF 2031Message Too Big for Queue Manager 0805 2053Queue Full 0835 2101MQ Object Damaged 08AA 2218Message 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
Re: W2K Trigger monitor triggers going to DLQ
This was copied from an earlier reply
bobbee
Dead Letter Header (DLH)
/usr/mqm/samp/bin/amqsbcg SYSTEM.DEAD.LETTER.QUEUE YOURQMGR > dlq.browse
the dlq.browse then looks like this:
AMQSBCG0 - starts here
**
MQOPEN - 'SYSTEM.DEAD.LETTER.QUEUE'
MQGET of message number 1
Message descriptor
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D51204D5141444D494E3420202020C713033E12F0'
CorrelId : X''
BackoutCount : 0
ReplyToQ : ''
ReplyToQMgr: ''
** Identity Context
UserIdentifier : '*** '
AccountingToken :
X'16010515009F3C2D05AC5FFA16ED7C36243D3C0B'
ApplIdentityData : ''
** Origin Context
PutApplType: '11'
PutApplName: 'MQSeries\pgm\bin\amqsput.exe'
PutDate : '20030109'PutTime : '08580248'
ApplOriginData : ''
GroupId : X''
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
Message
length - 184 bytes
: 444C 4820 0001 0825 4153 4446 'DLH ...%ASDF'
0010: 3220 2020 2020 2020 2020 2020 2020 2020 '2 '
0020: 2020 2020 2020 2020 2020 2020 2020 2020 ''
0030: 2020 2020 2020 2020 2020 2020 ''
0040: 2020 2020 2020 2020 2020 2020 '*** '
0050: 2020 2020 2020 2020 2020 2020 2020 2020 ''
0060: 2020 2020 2020 2020 2020 2020 0222 '..."'
0070: 0352 4D51 5354 5220 2020 0006 '...RMQSTR '
0080: 616D 7163 7273 7461 5F6E 6420 2020 2020 'amqcrsta_nd '
0090: 2020 2020 2020 2020 2020 2020 3230 3033 '2003'
00A0: 3031 3039 3038 3536 3236 3937 6173 6466 '010908562697asdf'
00B0: 6173 6466 6173 6466 'asdfasdf'
in the message dump you can see the "DLH" identifying the dead letter
header, now check from byte 9 to 12 - the value is 0825 (hex) which is
2085 dezimal
Now you can check API Return and Reason Codes in the "messages and Codes"
manual or use "mqrc 2085" which should return
2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME
In this case you also see the Object name that is missing (ASDF). Because of
our security policies i had to wipe out some fields like user ids and
queuemanager names.
From: Wesley Shaw <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: W2K Trigger monitor triggers going to DLQ
Date: Mon, 17 Feb 2003 08:15:41 -0500
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
<< pic04664.pcx >>
_
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
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
Re: W2K Trigger monitor triggers going to DLQ
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 AMTo: [EMAIL PROTECTED]Subject: Re: W2K
Trigger monitor triggers going to DLQAnother 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 Sent by:
MQSeries List <[EMAIL PROTECTED]>
17/02/2003 16:14 Please respond to MQSeries List
To:
[EMAIL PROTECTED]
cc:
Subject:
Re: W2K Trigger monitor triggers
going to DLQ What
I have done in the past is dump the contents of the message using oneof
the sample programs provided when you install MQM on the platform
inquestion. On a Windows system, this would be something like
Letter>:\Program
Files\IBM\MQSeries\Tools\C\Samples\Bin\amqsbcg. Thisutility will
view or browse the message on the DLQ, dumping the contents ofthat 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 12thbytes).
Since the error code is in hexadecimal, if you have a UNIX
machinearound, simply do the following at the command
line:bcibase=1607EECNTRL-DBC is a binary
calculator. ibase means BC will read its input in base 16vs. base
10. All input values need to be in UPPERCASE. The
decimalequivalent of 07EE is 2030. Now take that value and look it
up either inMQSeries Information Center or use the following command on
UNIX systems -grep 2030 /usr/include/cmqc.h. The returned string of
the last example willgive you why the message got redirected to the DLQ.
Other codes you mayfind in the DLQ are as follows:HEX
DECIMAL
ERROR DESCRIPTION07EE 2030
Message Too Big for
Queue07EF 2031
Message Too Big for Queue Manager0805
2053
Queue Full0835 2101
MQ Object
Damaged08AA 2218
Message Too Big for
ChannelStephan C. Moen[EMAIL PROTECTED]-Original
Message-From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf
Of Wesley ShawSent: Monday, February 17, 2003 7:16 AMTo:
[EMAIL PROTECTED]Subject: W2K Trigger monitor triggers going to
DLQI 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 mequicker than I
?(Embedded image moved to file: pic04664.pcx)Wesley
ShawOJRP 10th FloorWork: 804 771 3589 (736-3589)Pager: 888 436
2805 Mobile 804 512
5260_For
your protection, this e-mail has been scanned for knownviruses and
damaging content by http://GATEWAYDEFENDER.comInstructions for
managing your mailing list subscription are provided inthe Listserv
General Users Guide available at http://www.lsoft.comArchive:
http://vm.akh-wien.ac.at/MQSeries.archive
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 Sent by: MQSeries List <[EMAIL PROTECTED]> 17/02/2003 16:14 Please respond to MQSeries List To: [EMAIL PROTECTED] cc: 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 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
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 :\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: HEXDECIMAL ERROR DESCRIPTION 07EE 2030Message Too Big for Queue 07EF 2031Message Too Big for Queue Manager 0805 2053Queue Full 0835 2101MQ Object Damaged 08AA 2218Message 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
Re: W2K Trigger monitor triggers going to DLQ
Bridgette,
Bytes 9-12 of the DLH - which may require reversing for the 'Endianness' of
the machine.
Peter
"Beardsley, Bridgette"
To: MQSERIES
Sent by: "MQSeries List"
<[EMAIL PROTECTED]> cc:
Subject: Re: W2K
Trigger monitor triggers going to DLQ
17-Feb-2003 14:46
Please respond to "MQSeries
List" <[EMAIL PROTECTED]>
Mark & Peter,
Where are you finding your codes in that screen shot?
-Bridgette Beardsley
-Original Message-
From: Marc Verhiel [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 8:32 AM
To: [EMAIL PROTECTED]
Subject: Re: 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 ?<<<
Reason X'109' 265 since it's less than 2000 look it up under MQFB_*...this
is MQFB_APPL_CANNOT_BE_STARTED
Marc Verhiel
Candle Corp.
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
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
Re: W2K Trigger monitor triggers going to DLQ
Mark & Peter, Where are you finding your codes in that screen shot? -Bridgette Beardsley -Original Message- From: Marc Verhiel [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 8:32 AM To: [EMAIL PROTECTED] Subject: Re: 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 ?<<< Reason X'109' 265 since it's less than 2000 look it up under MQFB_*...this is MQFB_APPL_CANNOT_BE_STARTED Marc Verhiel Candle Corp. 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
Re: 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 ?<<< Reason X'109' 265 since it's less than 2000 look it up under MQFB_*...this is MQFB_APPL_CANNOT_BE_STARTED Marc Verhiel Candle Corp. 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
