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 IndexWebSphere Message Broker SupportReadding seqeunce ID from DTCC message

Post new topicReply to topic
Readding seqeunce ID from DTCC message View previous topic :: View next topic
Author Message
akashsthakkar
PostPosted: Fri Jul 17, 2020 11:31 am Post subject: Readding seqeunce ID from DTCC message Reply with quote

Newbie

Joined: 17 Jul 2020
Posts: 5

Hi,

Does anyone have any experience in consuming RAD (Receiver Authorized delivery) messages from DTCC.
We are working on one of such message but one of the field in the message RAD sequence Id comes with invalid characters in the message that we get.
This is probably because of some compression applied by DTCC.
We need this field as we need to send it back to DTCC on approval or rejection.
Any help in this regard would be highly appreciated.
Back to top
View user's profile Send private message
timber
PostPosted: Sat Jul 18, 2020 2:39 pm Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1127

Not much experience with RAD/DTCC but I should be able to help.
Quote:
RAD sequence Id comes with invalid characters in the message that we get. This is probably because of some compression applied by DTCC.

You may be correct, but I would like to understand your reasoning. We get a lot of questions about 'invalid' characters where the message flow is using the wrong CCSID (character set).
Back to top
View user's profile Send private message
akashsthakkar
PostPosted: Mon Jul 20, 2020 5:21 am Post subject: Reply with quote

Newbie

Joined: 17 Jul 2020
Posts: 5

timber wrote:
Not much experience with RAD/DTCC but I should be able to help.
Quote:
RAD sequence Id comes with invalid characters in the message that we get. This is probably because of some compression applied by DTCC.

You may be correct, but I would like to understand your reasoning. We get a lot of questions about 'invalid' characters where the message flow is using the wrong CCSID (character set).


Hi,

We use IBM XMS API and I believe the CSSID that we use would be 1208.
Anything that you recommend I should try.
Of the entire message , we are just unable to identify the 8 bytes that correspond to RAD sequence ID.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Jul 20, 2020 5:25 am Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20341
Location: LI,NY

akashsthakkar wrote:
timber wrote:
Not much experience with RAD/DTCC but I should be able to help.
Quote:
RAD sequence Id comes with invalid characters in the message that we get. This is probably because of some compression applied by DTCC.

You may be correct, but I would like to understand your reasoning. We get a lot of questions about 'invalid' characters where the message flow is using the wrong CCSID (character set).


Hi,

We use IBM XMS API and I believe the CSSID that we use would be 1208.
Anything that you recommend I should try.
Of the entire message , we are just unable to identify the 8 bytes that correspond to RAD sequence ID.


What is the format (as in MQMD.MQ_FORMAT) or the message they send?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
akashsthakkar
PostPosted: Mon Jul 20, 2020 5:37 am Post subject: Reply with quote

Newbie

Joined: 17 Jul 2020
Posts: 5

fjb_saper wrote:
akashsthakkar wrote:
timber wrote:
Not much experience with RAD/DTCC but I should be able to help.
Quote:
RAD sequence Id comes with invalid characters in the message that we get. This is probably because of some compression applied by DTCC.

You may be correct, but I would like to understand your reasoning. We get a lot of questions about 'invalid' characters where the message flow is using the wrong CCSID (character set).


Hi,

We use IBM XMS API and I believe the CSSID that we use would be 1208.
Anything that you recommend I should try.
Of the entire message , we are just unable to identify the 8 bytes that correspond to RAD sequence ID.


What is the format (as in MQMD.MQ_FORMAT) or the message they send?



The format is MQSTR
DTCC sends the message in EBCDIC format
Back to top
View user's profile Send private message
timber
PostPosted: Mon Jul 20, 2020 10:52 am Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1127

Mainframes often encode numbers using 'Packed Decimal' or 'Extended Decimal' formats. Both can include 'characters' (byte values, actually) with unusual bit patterns that do not decode safely.

This might be your problem, or it might not. I would need to see a couple of 'problem' field values to be sure.
Back to top
View user's profile Send private message
akashsthakkar
PostPosted: Mon Jul 20, 2020 1:37 pm Post subject: Reply with quote

Newbie

Joined: 17 Jul 2020
Posts: 5

timber wrote:
Mainframes often encode numbers using 'Packed Decimal' or 'Extended Decimal' formats. Both can include 'characters' (byte values, actually) with unusual bit patterns that do not decode safely.

This might be your problem, or it might not. I would need to see a couple of 'problem' field values to be sure.


Below is what we see on one of the messages. Just to be clear only 8 out of 370 bytes corresponding to this particular field appear this way.

Q\u009b\u001dU\"N

Below are the EBCDIC bytes.

EBDCIC Byte Mapping value from IBM Docs
216 Q
59 CUB
29 IGS
228 U
204 non displayable
127 "
213 N
86 Blank
Back to top
View user's profile Send private message
akashsthakkar
PostPosted: Tue Jul 21, 2020 7:12 am Post subject: Reply with quote

Newbie

Joined: 17 Jul 2020
Posts: 5

akashsthakkar wrote:
timber wrote:
Mainframes often encode numbers using 'Packed Decimal' or 'Extended Decimal' formats. Both can include 'characters' (byte values, actually) with unusual bit patterns that do not decode safely.

This might be your problem, or it might not. I would need to see a couple of 'problem' field values to be sure.


Below is what we see on one of the messages. Just to be clear only 8 out of 370 bytes corresponding to this particular field appear this way.

Q\u009b\u001dU\"N

Below are the EBCDIC bytes.

EBDCIC Byte Mapping value from IBM Docs
216 Q
59 CUB
29 IGS
228 U
204 non displayable
127 "
213 N
86 Blank


@timber
Does this ring any bell.
Let me know if you can share your contact so that I can work with you on this.
Thanks
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jul 21, 2020 7:52 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26015
Location: Texas, USA

akashsthakkar wrote:
Let me know if you can share your contact so that I can work with you on this.


It would be better if you kept this in the public forum for the benefit of other, future, readers.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
timber
PostPosted: Wed Jul 22, 2020 12:57 am Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1127

That data does not look like either Packed Decimal or External Decimal. I suggest that you contact the sender and ask for a format description.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportReadding seqeunce ID from DTCC message
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.