ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » CCSID500 Double Byte?

Post new topic  Reply to topic
 CCSID500 Double Byte? « View previous topic :: View next topic » 
Author Message
atheek
PostPosted: Mon Oct 20, 2008 9:55 pm    Post subject: CCSID500 Double Byte? Reply with quote

Partisan

Joined: 01 Jun 2006
Posts: 327
Location: Sydney

Hi All,

We are getting a message from a TPF system to a unix queue manager. We are facing issues in conversion of certain characters:

The byte sequence in unconverted format is:
156C D8D2 40E2 ( Message had a CCSID 500)

which when converted gets

0A25 514B 2053 ( Message has a CCSID 819) and in character form this is as: .%QK SY


15 is the ebcdic new line character which is getting to ascii line feed charcater 0A. 6C is ebcidic % charcter which is getting correctly transformed to % symbol. So the receiving application is interpreting that there is a % symbol in the message.

Now the TPF guys tell that 156C is a special combination and has its own meaning in the TPF world. 156C converts to a new line for them.
So I suspect the message is a mix of double byte and single byte characters which I think MQ is unable to convert correctly in its original form. The charcter conversion needs to be handled either at the receiver side or at sender side. Preference should be to use sender since the mainframe may be able to understand ebcdic better

I would like to know if you guys have faced any similar issue.

A few basic questions:
1. Does CCSID500 support both single byte and double byte characters?
2. What will be the best way to handle such a situation?

There are quite a few other combinations like this eg 5E5E, 005E etc

Thanks,
Atheek
Back to top
View user's profile Send private message
zboy
PostPosted: Mon Oct 20, 2008 11:12 pm    Post subject: Reply with quote

Novice

Joined: 01 Oct 2008
Posts: 13

Quote:
1. Does CCSID500 support both single byte and double byte characters?


No, 500 is single byte only

this is nothing to do with WMQ. the problem is caused by the msg not being described properly by the TPF side, i.e. they are not using 500 properly

Quote:
2. What will be the best way to handle such a situation?


tell TPF to write msgs properly.
if they are not going to do so, then they should use a user defined code page or msg format, and convert it at their end
Back to top
View user's profile Send private message
atheek
PostPosted: Mon Oct 20, 2008 11:46 pm    Post subject: Reply with quote

Partisan

Joined: 01 Jun 2006
Posts: 327
Location: Sydney

Thanks Zboy.. We were suspecting that TPF is not setting the message as per the 500 encoding.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » CCSID500 Double Byte?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.