| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Coverting EBCDIC to ASCII |
« View previous topic :: View next topic » |
| Author |
Message
|
| sebastian |
 Posted: Wed Jul 28, 2004 12:14 pm Post subject: Coverting EBCDIC to ASCII |
 |
|
Centurion
Joined: 12 Nov 2003
Posts: 110
Location: Philadelphia
|
EBCDIC (MF) to ASCII (Unix)
MQSI v2.1
Control center = windows, base level CSD
Configuration Manger = windows, base level CSD
Broker server = HP/UX, CSD03
We have a mainframe application that is sending an MQSeries message in EBCDIC with an RFH header. We would like to output this message to another application in ASCII format.
I have defined input and output message sets that both have a default CCSID of 500. I am able to move fields from input to output message sets and create an output message, but the output in the message queue is still in EBCDIC with a coded character set of 1051.
How do we get this conversion to occur if the message set already has the CCSID default set?
Any help is appreciated,
Seb 
_________________
sebastian signature |
|
| Back to top |
|
 |
| Lisa |
| Posted: Wed Jul 28, 2004 12:20 pm Post subject: Convert |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
You can use something like this
SET "OutputRoot"."MRM"."e_PIILOGCHeader"."PIIDLOGC_FILLER" =
CAST("InputRoot"."BLOB"."BLOB" AS CHAR CCSID InputRoot.MQMD.CodedCharSetId);
In this example, I receive data from the mainframe and the message flow on HP will process the message and put to MQqueue.
Hope this helps.
By the way, Control center, Configuration Manger and broker should be at the same CSD level.
Lisa |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jul 28, 2004 1:05 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hmmm.... WMQI can do the data conversion for you in this case. All you need to do set the proper CCSID and Encoding in Properties folder.
After you mapping, in a compute node put code similar to this,
| Code: |
SET OutputRoot.Properties.CodedCharSetId = 500;
SET OutputRoot.Properties.Encoding = 785;
|
This code will transform the message to NT codepage.
_________________
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 |
|
|
| EddieA |
| Posted: Wed Jul 28, 2004 1:39 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Errr. Aren't those the values for the Mainframe. 
I think you need CCSID: 437 and Encoding: 546 for Windows.
But, if everything is set correctly, and the message is all character, there should never be a need to set an explicit value. You should always use MQCCSI_Q_MGR and MQENC_NATIVE when PUTting messages and then GET with Convert.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jul 28, 2004 2:04 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Yes. My mistake!
Those values were for OS/390.
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
