| Author |
Message
|
| jillsam |
 Posted: Thu Jun 27, 2002 3:53 pm Post subject: EBCDIC to ASCII using MQSI |
 |
|
Newbie
Joined: 27 Jun 2002
Posts: 7
|
Is it appropriate to use the following for converting EBCDIC to ASCII?
Computer Node:
Set OutputRoot.MQMD.Encoding = 273;
Set OutputRoot.MQMD.CodedCharSetId= 819;
However the output were non-readable characters. Anyone has an answer to it? Thanks.
Also what's the difference between EBCDIC from mainfram & EBCDIC from AS/400?
_________________
http://www.materialsforum.net
Last edited by jillsam on Thu Jun 17, 2004 7:02 am; edited 1 time in total |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Jun 27, 2002 4:00 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What is your input message type? Do you have any binary fields in the message?
_________________
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 |
|
|
| jillsam |
| Posted: Thu Jun 27, 2002 5:03 pm Post subject: |
|
|
Newbie
Joined: 27 Jun 2002
Posts: 7
|
Not sure if it has binary data. The encoding is 273 and the CCSID is 37.
Thanks for your help.
_________________
http://www.materialsforum.net
Last edited by jillsam on Thu Jun 17, 2004 7:03 am; edited 1 time in total |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Fri Jun 28, 2002 5:58 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
Assuming you have a logically message tree which will be output as either MQMD format MQSTR (eg: generic XML) or according to an MRM message definition, then when the message is written, the correct CCSID will be applied.
However, the MQMD follows what's in the properties folder/tree, so rather than set the values in the MQMD, do:
Set OutputRoot.Properties.CodedCharSetId = 819;
Set OutputRoot.Properties.Encoding = 273;
Also double check the case of "Id" (or "ID") in the manual, I can't remember which it should be but getting it wrong will have you spend ages looking for the reason the conversion doesn't work ...
For any given CCSID there is no difference between EBCDIC on AS/400 v. OS/390 or other mainframe platforms, although do not that there are multiple EBCDIC CCSIDs, include SBCS, MBCS and DBCS. You are unlikely to encounter MBCS or DBCS unless you are taking part in exchanges with Japan/Korea/etc system. |
|
| Back to top |
|
|
| jdouch |
| Posted: Fri Jun 28, 2002 7:28 am Post subject: |
|
|
Apprentice
Joined: 31 May 2002
Posts: 32
Location: London, UK
|
the work i have just done required taking ebcidic messages from mainframe and sending them to a unix environment.
i just clicked the convert option on the mqinput node. in a fully functional environment the message should then assume the correct ccsid of the destination qmgr, and appears to be working fine.
if you're just testing the flows directly with input messages using rfhutil or something you need to specify MQSTR in the MQMD message format field.
rgds
J
_________________
Julian Douch
E-business Solutions Consultant
WMQ/WMQI Specialist |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Fri Jun 28, 2002 8:19 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
| Are you sure the MQInput node "convert" option has an impact here? I thought that was for doing an MQ Convert when the mqget call was made, which would (if my MQ is correct) involve having either a know message format (to MQ), or an exit available to convert the message. |
|
| Back to top |
|
|
| dhaksr |
| Posted: Fri Jun 28, 2002 10:27 am Post subject: |
|
|
Apprentice
Joined: 20 Feb 2002
Posts: 37
|
Setting Convert to Yes will invoke MQ Series conversion (either exit or standard conversion for known formats)
If you have mixed data (binary and Alpha) then you have to set
output root properties and do individual field assignments to
invoke WMQI conversion.
As an aside,
| Quote: |
Also double check the case of "Id" (or "ID") in the manual, I can't remember which it should be but getting it wrong will have you spend ages looking for the reason the conversion doesn't work ...
|
we spent ages debuging "Id" Vs "ID"  .
Shouldnt we ask IBM to have atleast the Standard Properties as Case Insensitive? |
|
| Back to top |
|
|
| kwelch |
| Posted: Fri Jun 28, 2002 10:44 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
checking the convert option will work. Normally we just let the getting app. do the convert and things pass through WMQI. In this case though I was creating from Mainframe, EBCDIC code to XML for a UNIX environment. I needed to look at the XML with another tool before passing it on and the convert option worked quite nicely for that.
If you do have comp fields though it will cause problems.
Karen |
|
| Back to top |
|
|
|
|
