Author |
Message
|
LH33 |
Posted: Sun Mar 16, 2003 8:14 am Post subject: BLOB Error in trace node |
|
|
Master
Joined: 21 Nov 2002 Posts: 200
|
HI! I am getting an error in my trace node Can someone help me understand what it is and what I need to do to correct it? Thanks!! LisaB
Here is the contents of the Trace Node:
Root
(
(0x1000000)Properties = (
(0x3000000)MessageSet = ''
(0x3000000)MessageType = ''
(0x3000000)MessageFormat = ''
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = FALSE
(0x3000000)CreationTime = GMTTIMESTAMP '2003-03-16 16:09:22.890'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x3000000)ReplyProtocol = 'MQ'
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'DISTR_ATLAS_COORD_REPLY'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Format = 'MQSTR '
(0x3000000)Version = 2
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 0
(0x3000000)Persistence = 0
(0x3000000)MsgId = X'414d51204745544d5131202020202020bbde633e1220e80d'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'
(0x3000000)BackoutCount = 0
(0x3000000)ReplyToQ = ' '
(0x3000000)ReplyToQMgr = 'GETMQ1 '
(0x3000000)UserIdentifier = 'MTSRUN_MQ '
(0x3000000)AccountingToken = X'1601051500000008691451fa547e13c811bf7b421f000000000000000000000b'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 11
(0x3000000)PutApplName = ':\WINNT\System32\dllhost.exe'
(0x3000000)PutDate = DATE '2003-03-16'
(0x3000000)PutTime = GMTTIME '16:09:22.890'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'000000000000000000000000000000000000000000000000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
)
(0x1000000)BLOB = (
(0x3000000)UnknownParserName = 'MQSTR'
(0x3000000)BLOB = X'3c41544c41535f58595f51554552593e3c4170706c69636174696f6e417265613e3c53656e6465723e3c436f6d706f6e656e743e41746c61733c2f436f6d706f6e656e743e3c436f6e6669726d6174696f6e3e3c2f436f6e6669726d6174696f6e3e3c417574686f72697a6174696f6e49643e3c2f417574686f72697a6174696f6e49643e3c2f53656e6465723e3c4372656174696f6e4461746554696d653e434359592d4d4d2d44445468683a6d6d3a73733c2f4372656174696f6e4461746554696d653e3c424f4449643e47554944202d20476c6f62616c6c7920556e69717565204964656e7469666965723c2f424f4449643e3c2f4170706c69636174696f6e417265613e3c44617461417265613e3c5245515f545950453e5052454d4953453c2f5245515f545950453e0d0a09093c5245515f434f44453e31323334353c2f5245515f434f44453e3c585f434f4f5244494e4154453e35363734363c2f585f434f4f5244494e4154453e3c595f434f4f5244494e4154453e39343536373c2f595f434f4f5244494e4154453e3c5354415455533e5355434345535346554c3c2f5354415455533e3c5245434f52445f444154413e3c45585445524e414c5f4f4e453e313233343536373839303132333435363c2f45585445524e414c5f4f4e453e3c2f5245434f52445f444154413e3c2f44617461417265613e3c2f41544c41535f58595f51554552593e0d0a'
)
)
-------
ExceptionList |
|
Back to top |
|
 |
kirani |
Posted: Sun Mar 16, 2003 10:27 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
I don't see the ExceptionList here. Pls make sure you have added ${ExceptionList} in your Trace node in catch path. _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
janhl |
Posted: Wed Mar 24, 2004 1:48 am Post subject: |
|
|
Newbie
Joined: 05 Nov 2003 Posts: 4
|
I've got the same error and the ExceptionList is NOT filled.
Running WMQI 2.1 CSD4 on z/OS(USS).
Input node setting Msg Domain=BLOB
My trace:
(
(0x1000000)Properties = (
(0x3000000)MessageSet = ''
(0x3000000)MessageType = ''
(0x3000000)MessageFormat = ''
(0x3000000)Encoding = 785
(0x3000000)CodedCharSetId = 500
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = FALSE
(0x3000000)CreationTime = GMTTIMESTAMP '2004-03-24 09:12:55.150'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x3000000)ReplyProtocol = 'MQ'
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'ODBATCH.BIBU_TO_EWMS.001.QL'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 785
(0x3000000)CodedCharSetId = 500
(0x3000000)Format = 'MQSTR '
(0x3000000)Version = 1
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 0
(0x3000000)Persistence = 0
(0x3000000)MsgId = X'414d51204b4c44414f4e442020202020403d01cf0181b012'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'
(0x3000000)BackoutCount = 1
(0x3000000)ReplyToQ = ' '
(0x3000000)ReplyToQMgr = 'KLDAOND '
(0x3000000)UserIdentifier = 'MTUSER01 '
(0x3000000)AccountingToken = X'0335303300000000000000000000000000000000000000000000000000000006'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 6
(0x3000000)PutApplName = 'mqput '
(0x3000000)PutDate = DATE '2004-03-24'
(0x3000000)PutTime = GMTTIME '09:12:55.150'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'000000000000000000000000000000000000000000000000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
(0x3000000)Flags = 0
)
(0x1000000)BLOB = (
(0x3000000)UnknownParserName = 'MQSTR'
(0x3000000)BLOB = X'f2f4d4c1d9f0f4f1f0f1f2f3f4f4f0f0f0f0f0f1f5d2d340f1f6f9f3f0f5e2c5d7f0f4f14040f0f1 etc
Jan-Hein |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Mar 24, 2004 4:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You don't get an exception list populated at the Failure terminal of the MQInput node. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
janhl |
Posted: Wed Mar 24, 2004 4:33 am Post subject: |
|
|
Newbie
Joined: 05 Nov 2003 Posts: 4
|
OK, but what about the problem itself? |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Mar 24, 2004 5:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Well, your message flow failed somewhere.
Where did it hit the tracenode? At the failure terminal? Did it hit any other tracenodes before this one?
If not, then change the tracenode to be connected to the catch terminal, and try again. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Missam |
Posted: Wed Mar 24, 2004 6:05 am Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003 Posts: 424
|
Did u guys check the Error Log for any reported errors...? |
|
Back to top |
|
 |
janhl |
Posted: Tue Mar 30, 2004 5:50 am Post subject: |
|
|
Newbie
Joined: 05 Nov 2003 Posts: 4
|
An update:
The problem occurs with various "shared" queues on z/OS (using coupling facility, part of our parallel sysplex environment) and has been reported to IBM as PMR 28415. |
|
Back to top |
|
 |
|