MsgId and CorrelId Conversion
Greetings All, We are in the process of rehosting OS/390 to AIX and I am looking for some thoughts on a problem we have run into. To provide test data on AIX I have a channel message exit on our gateway/hub.OS/390 channel that copies all mainframe-bound messages to the AIX qmgr, however initial testing has highlighted a problem with the format of the MsgId and CorrelId fields. Some of the applications, reading messages off some of the queues, all from the same source qmgr need to use the MsgId/CorrelId values but they are currently being sent in EBCDIC format and are not 'readable' on AIX. At the moment I am looking at either selectively translating the fields in the message exit or setting up a translation routine on AIX, if possible, that can be called by those applications that need it. Do any of you have any experience/thoughts/gotchas/samples/alternatives that you could share to help me in my decision? TIA, Kerry Swemmer T-Systems South Africa (Pty) Ltd Database Administrator Computing and Desktop Services Address: DaimlerChrysler, 7 Settlers Way, East London, South Africa Postal Address: PO Box 671, East London, 5200 Phone: +27 (43) 706 2549 Fax:+27 (43) 706 2085 Mobile: +27 (83) 657 4151 E-mail: [EMAIL PROTECTED] Internet: www.t-systems.co.za Any views expressed in this message are those of the individual sender, and T-Systems South Africa (Pty) Ltd accepts no liability therefore, except where the sender specifically states them to be those of T-Systems South Africa (Pty) Ltd. Although this message has been scanned for the possible presence of computer viruses prior to despatch, T-Systems South Africa (Pty) Ltd cannot be held responsible for any viruses or other material transmitted with, or as part of, this message. 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: MsgId and CorrelId Conversion
Message Id and Correlation Id are defined to be BINARY data, not character data. MQ will never convert these, and IMHO, neither should you. If the application developer is assuming that they will be converted they are mistaken. Dave 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: MsgId and CorrelId Conversion
Hi, MQ treats MsgID, CorrelID and GroupID fields as binary data and these fields are NOT converted when messages hope between queue managers. Over the years, I have learnt to never store application related data in any of these fields because you never know when you will get burnt by the EBCDIC-ASCII thing. You should always store application data in the message data area rather than in MQMD fields. The MsgID and CorrelID should be primary used in the request / reply scenario. i.e. Send a request message and save the MsgID field then do a 'Get by CorrelID' by copying the saved MsgID value into the CorrelID field. The application should not care what the value of the MsgID was and if you care then print it out as a hex representation of the binary field. i.e. 414D512043... Hope that helps. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting Kerry Swemmer [EMAIL PROTECTED]: Greetings All, We are in the process of rehosting OS/390 to AIX and I am looking for some thoughts on a problem we have run into. To provide test data on AIX I have a channel message exit on our gateway/hub.OS/390 channel that copies all mainframe-bound messages to the AIX qmgr, however initial testing has highlighted a problem with the format of the MsgId and CorrelId fields. Some of the applications, reading messages off some of the queues, all from the same source qmgr need to use the MsgId/CorrelId values but they are currently being sent in EBCDIC format and are not 'readable' on AIX. At the moment I am looking at either selectively translating the fields in the message exit or setting up a translation routine on AIX, if possible, that can be called by those applications that need it. Do any of you have any experience/thoughts/gotchas/samples/alternatives that you could share to help me in my decision? TIA, Kerry Swemmer T-Systems South Africa (Pty) Ltd Database Administrator Computing and Desktop Services Address: DaimlerChrysler, 7 Settlers Way, East London, South Africa Postal Address: PO Box 671, East London, 5200 Phone: +27 (43) 706 2549 Fax:+27 (43) 706 2085 Mobile: +27 (83) 657 4151 E-mail: [EMAIL PROTECTED] Internet: www.t-systems.co.za Any views expressed in this message are those of the individual sender, and T-Systems South Africa (Pty) Ltd accepts no liability therefore, except where the sender specifically states them to be those of T-Systems South Africa (Pty) Ltd. Although this message has been scanned for the possible presence of computer viruses prior to despatch, T-Systems South Africa (Pty) Ltd cannot be held responsible for any viruses or other material transmitted with, or as part of, this message. 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: MsgId and CorrelId Conversion
Kerry, No, no, no...You cannot put EBCDIC in msgid/correlid. MQ never translates them and neither should you; they ARE readable on AIX and will contain exactly what was sent. All by design. Passing application data in those fields is a boo-boo. You may be able to overcome it with some creative coding, but it begins to look like a snarly mess, no? My first suggestion, of course, is to fix the underlying problem. Yeah, I know. My first recourse would be for the exit to insert the EBCDIC msgid/correlid into the application part of the message where it belongs. Then it will get translated along with everything else consistent with the principal of receiver makes right. Regards, Dennis -Original Message- From: Kerry Swemmer [mailto:[EMAIL PROTECTED] Sent: Monday, April 26, 2004 6:55 AM To: [EMAIL PROTECTED] Subject: MsgId and CorrelId Conversion Greetings All, We are in the process of rehosting OS/390 to AIX and I am looking for some thoughts on a problem we have run into. To provide test data on AIX I have a channel message exit on our gateway/hub.OS/390 channel that copies all mainframe-bound messages to the AIX qmgr, however initial testing has highlighted a problem with the format of the MsgId and CorrelId fields. Some of the applications, reading messages off some of the queues, all from the same source qmgr need to use the MsgId/CorrelId values but they are currently being sent in EBCDIC format and are not 'readable' on AIX. At the moment I am looking at either selectively translating the fields in the message exit or setting up a translation routine on AIX, if possible, that can be called by those applications that need it. Do any of you have any experience/thoughts/gotchas/samples/alternatives that you could share to help me in my decision? TIA, Kerry Swemmer T-Systems South Africa (Pty) Ltd Database Administrator Computing and Desktop Services Address: DaimlerChrysler, 7 Settlers Way, East London, South Africa Postal Address: PO Box 671, East London, 5200 Phone: +27 (43) 706 2549 Fax:+27 (43) 706 2085 Mobile: +27 (83) 657 4151 E-mail: [EMAIL PROTECTED] Internet: www.t-systems.co.za Any views expressed in this message are those of the individual sender, and T-Systems South Africa (Pty) Ltd accepts no liability therefore, except where the sender specifically states them to be those of T-Systems South Africa (Pty) Ltd. Although this message has been scanned for the possible presence of computer viruses prior to despatch, T-Systems South Africa (Pty) Ltd cannot be held responsible for any viruses or other material transmitted with, or as part of, this message. 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
