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 » WebSphere Message Broker (ACE) Support » DFDL Parsing issue

Post new topic  Reply to topic
 DFDL Parsing issue « View previous topic :: View next topic » 
Author Message
mindspace
PostPosted: Thu May 10, 2018 3:04 pm    Post subject: DFDL Parsing issue Reply with quote

Apprentice

Joined: 22 Jan 2013
Posts: 26
I am creating new DFDL model from scratch and facing below issue.
I have a incoming field with 2 bytes field length in prefix(prefix length not inc. in field) in hex form.
For example:
Incoming Field is : 0BF4F3F04040404040404040
Prefix length = 0B (Hex format, is equal to decimal -11)

On the input node the parser is selected as BLOB.
So after Input node the same field is represented as HEX(ASCII form)
304246344633463034303430343034303430343034303430
Prefix length = 3042(0B)

Next, in compute node I am doing conversion of this field to original hex form -3042F4F3F04040404040404040 leaving the prefix length as is i.e 3042.

Later using DFDL model, I can successfully parse this prefix length field using number representation (number base 16) and also the field as string with encoding as ebcdic so output is '430 '

Here comes the issue..when the output from last step is again assigned to blob (using ASBITSTREAM ) what I see is 3062f4f3f04040404040404040

Prefix length is getting changed to 3062 ... I understand its because of ASCII character 'b' instead of 'B'.
How to handle this? how to achieve correct BLOB value for prefix which is '3042'?
Back to top
View user's profile Send private message
timber
PostPosted: Fri May 11, 2018 2:53 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280
Quote:
Incoming Field is : 0BF4F3F04040404040404040
Is that 12 bytes or 24 ASCII characters?
Back to top
View user's profile Send private message
mindspace
PostPosted: Fri May 11, 2018 5:53 am    Post subject: Reply with quote

Apprentice

Joined: 22 Jan 2013
Posts: 26
its 24 ASCII character, prefix being in HEX and actual field value is being encoded in ebcdic
Back to top
View user's profile Send private message
timber
PostPosted: Mon May 14, 2018 4:46 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280
Quote:
how to achieve correct BLOB value for prefix which is '3042'?
I think both are 'correct' but I assume that the downstream application only handles 'B' and not 'b'. You will probably have to post-process the DFDL BLOB to achieve what you need.
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 » WebSphere Message Broker (ACE) Support » DFDL Parsing 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.