| Author |
Message
|
| sboucher |
 Posted: Wed Nov 27, 2002 5:33 am Post subject: ASCII to EBCDIC using WMQSI |
 |
|
Acolyte
Joined: 27 Oct 2002
Posts: 52
|
I have the following set in a compute node just prior to outputting to our VSE System
SET OutputRoot.MQMD.CodedCharSetID = 037;
SET OutputRoot.MQMD.Encoding = 785;
The VSE Code Page is set to 037 and the messages arrive to the Q however the data is unintelligible. My hunch is the ASCII to EBCDIC conversion is not working. Any Ideas.
Thanks
Scott
_________________
Scott A. Boucher
Database Administartor |
|
| Back to top |
|
 |
| leongor |
| Posted: Wed Nov 27, 2002 5:55 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
Why to change CCSID on MQPUT (Output Node) ?
You need that your message will be in its original CCSID.
MQGET on VSE must convert it to EBCDIC.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Nov 27, 2002 7:28 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Scott,
Use this instead,
| Code: |
SET OutputRoot.Propertis.CodedCharSetID = 037;
SET OutputRoot.Propertis.Encoding = 785;
|
_________________
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 |
|
|
| PeterPotkay |
| Posted: Wed Nov 27, 2002 4:44 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
Kirani,
I'm not an WMQI expert, but is that going to do anything? If the message coming into WMQI is ASCII, the output will be in ASCII as well, regardless of what the MQMD is set to on the PUT. I am not aware of any conversion happening on the MQPUT.
In the above case, unless I am wrong, I would expect WMQI would still put out an ASCII message, but just be calling it EBCIDIC. In fact, it is still ASCII, and the recieving convert is going to try to convert to its local CCSID a message it assume is coming in as EBCIDIC, producing garbage.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Nov 27, 2002 9:08 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi Peter,
With above two statements, WMQI will do the data conversion.
When WMQI reads an input message from the queue, it first converts it into UCS2 (Unicode) format internally. It then convert the message to CCSID and Encoding Values set into Properties folder while writing out the message using MQOutput node. This is one of the main feature of WMQI!
_________________
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 |
|
|
| sboucher |
| Posted: Sat Nov 30, 2002 12:42 pm Post subject: |
|
|
Acolyte
Joined: 27 Oct 2002
Posts: 52
|
I'm still not getting the convert to take place with the suggestions made here.
Thanks anyway
Scott
_________________
Scott A. Boucher
Database Administartor |
|
| Back to top |
|
|
| kirani |
| Posted: Sat Nov 30, 2002 6:11 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi Scott,
What is code you are using now in your Compute node to do the Data Conversion? What is your output message format/domain set to?
I think I mistyped the code in my earlier post, It should be
| Code: |
SET OutputRoot.Properties.CodedCharSetId = 037;
SET OutputRoot.Properties.Encoding = 785;
|
Add a Trace node before the MQOutput node and capture ${Root} in it, make sure it's showing the new CCSID and Encoding values in Properties folder.
_________________
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 |
|
|
|
|
