Re: Unidentifiable reason code in DLH
Thanks all for your reply, Stefan did the right deal ! I could find the message: --- CSQ2001I ?MQP2 CSQ2QCP0 OTMA REJECTED MESSAGE - APPLICATION ERROR, SENSE CODE=001A0019, XCFGNAME=IMSXCF XCFMNAME=IMPA TPIPE=CSQ00034 --- My colleage administrating IMS showed me, that the IMS-application SD341P had an error and therefore OTMA rejected the message. So the batch program did not recognize that. Stefan, thanks for your help, it was great ! Norbert Pfister IT DB/DC-Systemtechnik ITELLIUM Systems Services GmbH N - Bau V, Zi. 113 Fürther Strasse 205 D-90429 Nürnberg, Germany Tel.: (+49) 0911/14-26548 Fax: (+49) 0911/14-23390 Mobil: (+49) 0151/14265011 mailto:norbert.pfister;itellium.com -Ursprüngliche Nachricht- Von: Stefan Sievert [mailto:stefansievert;HOTMAIL.COM] Gesendet: Donnerstag, 17. Oktober 2002 19:12 An: [EMAIL PROTECTED] Betreff: Re: Unidentifiable reason code in DLH Hi Norbert, DLH reasoncodes in the range between 300 and 399 are actually feedback codes generated by OTMA. You have to subtract MQFB_ERROR from that value (300), which gives you the OTMA sense code. In your case that would be 26(dec); converted to Hex that is 1A. Now, chapter 4 of the OTMA Guide and reference available at http://www-3.ibm.com/software/data/ims/shelf/v6pdf2/OTMA_V6.pdf contains a list of OTMA sense codes and their cause. You should also see a message CSQ2001I in the SYSOUT of your MSTR started task that gives you additional information. The format of this message is as follows: CSQ2001I csect-name OTMA REJECTED MESSAGE - APPLICATION ERROR, SENSE CODE=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipename Hope that gets you on the right track. Cheers, Stefan From: Pfister Norbert [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Unidentifiable reason code in DLH Date: Thu, 17 Oct 2002 16:34:47 +0200 Hi all, we have a batch assembler program on our OS/390 , which is preparing messages coming from outer space, ... uuppss ... , sorry, from distributed platforms, to go to the IMS bridge . In detail it transforms the first bytes of the message data, a IMS lenth field from character to hex. Sometimes messages go to the DLQ. I surely want to stop this awful behaviour, but since the reason code is 326(decimal), I can't interpret it ! Below an example message header: --- - -- [ 364 bytes] Message Descriptor (MQMD) StrucId :'MD ' Version :1 Report :0 Message Type :8 Expiry :-1 Feedback :0 MQEncoding :0x'311' CCSID:273 Format :'MQDEAD ' Priority :0 Persistence :1 (Persistent) Message Id :35333434344533303334333135302020202020202020 Correl. Id :35333434344533303334333135302020202020202020 Backout Cnt. :0 ReplyToQ :'QM.SD.SD341.REPLY.LOCAL ' ReplyToQMgr :'MQP2' UserId :'YTU0002 ' AccountingTkn:0 0 00 ApplIndentity:'' PutApplType :0 PutApplName :'' Put Date :'' Put Time :'' ApplOriginDat:'' [ 272 bytes] Dead Letter Queue Header (MQDLH) StrucId :'DLH ' Version :1 Reason :326 (Unrecognised) Dest. Queue :'IMPA.IMSQ ' Dest. QMgr :'MQP2' MQEncoding :0x'311' CCSID:273 Format :'MQSTR ' PutApplType :19 PutApplName :'MQP2' Put Date :'20020905' Put Time :'13200550' --- - -- Can anyone help ? Norbert Pfister IT DB/DC-Systemtechnik ITELLIUM Systems Services GmbH N - Bau V, Zi. 113 F|rther Strasse 205 D-90429 N|rnberg, Germany Tel.: (+49) 0911/14-26548 Fax: (+49) 0911/14-23390 Mobil: (+49) 0151/14265011 mailto:norbert.pfister;itellium.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 _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 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
Unidentifiable reason code in DLH
Hi all, we have a batch assembler program on our OS/390 , which is preparing messages coming from outer space, ... uuppss ... , sorry, from distributed platforms, to go to the IMS bridge . In detail it transforms the first bytes of the message data, a IMS lenth field from character to hex. Sometimes messages go to the DLQ. I surely want to stop this awful behaviour, but since the reason code is 326(decimal), I can't interpret it ! Below an example message header: -- [ 364 bytes] Message Descriptor (MQMD) StrucId :'MD ' Version :1 Report :0 Message Type :8 Expiry :-1 Feedback :0 MQEncoding :0x'311' CCSID:273 Format :'MQDEAD ' Priority :0 Persistence :1 (Persistent) Message Id :35333434344533303334333135302020202020202020 Correl. Id :35333434344533303334333135302020202020202020 Backout Cnt. :0 ReplyToQ :'QM.SD.SD341.REPLY.LOCAL ' ReplyToQMgr :'MQP2' UserId :'YTU0002 ' AccountingTkn:00 00 ApplIndentity:'' PutApplType :0 PutApplName :'' Put Date :'' Put Time :'' ApplOriginDat:'' [ 272 bytes] Dead Letter Queue Header (MQDLH) StrucId :'DLH ' Version :1 Reason :326 (Unrecognised) Dest. Queue :'IMPA.IMSQ ' Dest. QMgr :'MQP2' MQEncoding :0x'311' CCSID:273 Format :'MQSTR ' PutApplType :19 PutApplName :'MQP2' Put Date :'20020905' Put Time :'13200550' -- Can anyone help ? Norbert Pfister IT DB/DC-Systemtechnik ITELLIUM Systems Services GmbH N - Bau V, Zi. 113 Fürther Strasse 205 D-90429 Nürnberg, Germany Tel.: (+49) 0911/14-26548 Fax: (+49) 0911/14-23390 Mobil: (+49) 0151/14265011 mailto:norbert.pfister;itellium.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: Unidentifiable reason code in DLH
Hi Norbert, DLH reasoncodes in the range between 300 and 399 are actually feedback codes generated by OTMA. You have to subtract MQFB_ERROR from that value (300), which gives you the OTMA sense code. In your case that would be 26(dec); converted to Hex that is 1A. Now, chapter 4 of the OTMA Guide and reference available at http://www-3.ibm.com/software/data/ims/shelf/v6pdf2/OTMA_V6.pdf contains a list of OTMA sense codes and their cause. You should also see a message CSQ2001I in the SYSOUT of your MSTR started task that gives you additional information. The format of this message is as follows: CSQ2001I csect-name OTMA REJECTED MESSAGE - APPLICATION ERROR, SENSE CODE=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipename Hope that gets you on the right track. Cheers, Stefan From: Pfister Norbert [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Unidentifiable reason code in DLH Date: Thu, 17 Oct 2002 16:34:47 +0200 Hi all, we have a batch assembler program on our OS/390 , which is preparing messages coming from outer space, ... uuppss ... , sorry, from distributed platforms, to go to the IMS bridge . In detail it transforms the first bytes of the message data, a IMS lenth field from character to hex. Sometimes messages go to the DLQ. I surely want to stop this awful behaviour, but since the reason code is 326(decimal), I can't interpret it ! Below an example message header: -- [ 364 bytes] Message Descriptor (MQMD) StrucId :'MD ' Version :1 Report :0 Message Type :8 Expiry :-1 Feedback :0 MQEncoding :0x'311' CCSID:273 Format :'MQDEAD ' Priority :0 Persistence :1 (Persistent) Message Id :35333434344533303334333135302020202020202020 Correl. Id :35333434344533303334333135302020202020202020 Backout Cnt. :0 ReplyToQ :'QM.SD.SD341.REPLY.LOCAL ' ReplyToQMgr :'MQP2' UserId :'YTU0002 ' AccountingTkn:00 00 ApplIndentity:'' PutApplType :0 PutApplName :'' Put Date :'' Put Time :'' ApplOriginDat:'' [ 272 bytes] Dead Letter Queue Header (MQDLH) StrucId :'DLH ' Version :1 Reason :326 (Unrecognised) Dest. Queue :'IMPA.IMSQ ' Dest. QMgr :'MQP2' MQEncoding :0x'311' CCSID:273 Format :'MQSTR ' PutApplType :19 PutApplName :'MQP2' Put Date :'20020905' Put Time :'13200550' -- Can anyone help ? Norbert Pfister IT DB/DC-Systemtechnik ITELLIUM Systems Services GmbH N - Bau V, Zi. 113 F|rther Strasse 205 D-90429 N|rnberg, Germany Tel.: (+49) 0911/14-26548 Fax: (+49) 0911/14-23390 Mobil: (+49) 0151/14265011 mailto:norbert.pfister;itellium.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 _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 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: Unidentifiable reason code in DLH
Hi Norbert, The MQDLH Reason code can be a reason code or a feedback code.In the Application Programming Reference, under the description of Reason for the MQDLH, it says, If the value is in the range MQFB_IMS_FIRST through MQFB_IMS_LAST, the actual IMS error code can be determined by subtracting MQFB_IMS_ERROR from the value of the Reason field. The constants for Feedback are in the same manual in the appendix for MQ Constants. IMS_FIRST is 301, IMS_LAST is 399, and IMS_ERROR is 300. Regards, Tom == Tom Schneider / IBM Global Services (513) 533-3644 [EMAIL PROTECTED] == Pfister Norbert [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 10/17/2002 10:34 AM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject:Unidentifiable reason code in DLH Hi all, we have a batch assembler program on our OS/390 , which is preparing messages coming from outer space, ... uuppss ... , sorry, from distributed platforms, to go to the IMS bridge . In detail it transforms the first bytes of the message data, a IMS lenth field from character to hex. Sometimes messages go to the DLQ. I surely want to stop this awful behaviour, but since the reason code is 326(decimal), I can't interpret it ! Below an example message header: -- [ 364 bytes] Message Descriptor (MQMD) StrucId :'MD ' Version :1 Report :0 Message Type :8 Expiry :-1 Feedback :0 MQEncoding :0x'311' CCSID:273 Format :'MQDEAD ' Priority :0 Persistence :1 (Persistent) Message Id :35333434344533303334333135302020202020202020 Correl. Id :35333434344533303334333135302020202020202020 Backout Cnt. :0 ReplyToQ :'QM.SD.SD341.REPLY.LOCAL ' ReplyToQMgr :'MQP2' UserId :'YTU0002 ' AccountingTkn:00 00 ApplIndentity:'' PutApplType :0 PutApplName :'' Put Date :'' Put Time :'' ApplOriginDat:'' [ 272 bytes] Dead Letter Queue Header (MQDLH) StrucId :'DLH ' Version :1 Reason :326 (Unrecognised) Dest. Queue :'IMPA.IMSQ ' Dest. QMgr :'MQP2' MQEncoding :0x'311' CCSID:273 Format :'MQSTR ' PutApplType :19 PutApplName :'MQP2' Put Date :'20020905' Put Time :'13200550' -- Can anyone help ? Norbert Pfister IT DB/DC-Systemtechnik ITELLIUM Systems Services GmbH N - Bau V, Zi. 113 Fürther Strasse 205 D-90429 Nürnberg, Germany Tel.: (+49) 0911/14-26548 Fax: (+49) 0911/14-23390 Mobil: (+49) 0151/14265011 mailto:norbert.pfister;itellium.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
