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 » General IBM MQ Support » JSON Message conversion issue

Post new topic  Reply to topic Goto page Previous  1, 2
 JSON Message conversion issue « View previous topic :: View next topic » 
Author Message
gbaddeley
PostPosted: Mon Aug 16, 2021 3:58 pm    Post subject: Reply with quote

Jedi

Joined: 25 Mar 2003
Posts: 2492
Location: Melbourne, Australia

anveshita wrote:
gbaddeley wrote:
Given that CONVERT(YES) on the channel is successfully converting the message, and you have confirmed the message ccsid is 37, and the square bracket is the correct hex code BA, it appears the issue is with conversion on DP.

Can you dump a message using amqsbcg? This will show all the MQMD fields and the raw unconverted RFH and data. There could be a lurking ccsid issue that is upsetting DP.


We ran the amqscbcg. For this test, the convert flag is YES st on cluster receiver channel is on. I am unable to share the data part but can share the header with some info masked.
Code:

****Message descriptor****

  StrucId  : 'MD  '  Version : 2
  Report   : 0  MsgType : 8
  Expiry   : -1  Feedback : 0
 Encoding : 546  CodedCharSetId : 819
  Format : 'MQHRF2  '
  Priority : 0  Persistence : 0
  MsgId : X'F1F8F2F2F8F0F0F0F0F0F2F5F6F0F8404040404040404040'
  CorrelId : X'000000000000000000000000000000000000000000000000'
  BackoutCount : 0
  ReplyToQ       : 'xxx.xxx.xxxx.xxxx                     '
  ReplyToQMgr    : 'xxxx                                            '
  ** Identity Context
  UserIdentifier : 'xxxxx    '
  AccountingToken :
   X'0000000000000000000000000000000000000000000000000000000000000000'
  ApplIdentityData : '                                '
  ** Origin Context
  PutApplType    : '2'
  PutApplName    : 'xxxxxxx                   '
  PutDate  : '2021xxxx'    PutTime  : 'xxxxxx'
  ApplOriginData : '    '

  GroupId : X'000000000000000000000000000000000000000000000000'
  MsgSeqNumber   : '1'
  Offset         : '0'
  MsgFlags       : '0'
  OriginalLength : '-1'


Please see Encoding : 546 CodedCharSetId : 819 from the amqsbcg program output. The Z/os is using "037" though. We ran both with channel conversion ON and OFF on the request cluster channel. But did not see any difference in the amqsbcg output of the encoding. So I am bit confused.


After changing the value of CONVERT, did you restart the channel? (ie. this is not a dynamic setting for channels that are running at the time)

Based on the MsgId, it appears the message is from z/OS. It is has been converted from and EBCDIC ccsid (eg. 37, 500) to 819. It is MQHRF2 format, so there will be a sequence of one or more MQRFH structures in the Message Data, followed by a payload data string. Each of the MQRFH contains a CCSID field. Can you provide the message data, with some indicative characters in the MQRFH strings so that we can check if they are ASCII or EBCDIC.

I suspect that MQ is converting everything correctly, but it pays to check.
_________________
Glenn
Back to top
View user's profile Send private message
anveshita
PostPosted: Tue Aug 17, 2021 5:46 am    Post subject: Reply with quote

Master

Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam

Quote:
After changing the value of CONVERT, did you restart the channel? (ie. this is not a dynamic setting for channels that are running at the time


Yes, We did.

Quote:
It is MQHRF2 format, so there will be a sequence of one or more MQRFH structures in the Message Data, followed by a payload data string. Each of the MQRFH contains a CCSID field. Can you provide the message data, with some indicative characters in the MQRFH strings so that we can check if they are ASCII or EBCDIC.


Is there any way I can PM you? Not sure the data can be shared here.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Tue Aug 17, 2021 3:33 pm    Post subject: Reply with quote

Jedi

Joined: 25 Mar 2003
Posts: 2492
Location: Melbourne, Australia

anveshita wrote:
Is there any way I can PM you? Not sure the data can be shared here.

You can redact the data to share here, or you can follow my suggestion of checking the CCSID and data in each of the MQRFH structures.
_________________
Glenn
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » JSON Message conversion issue
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.