Posted: Mon Aug 31, 2009 12:52 am Post subject: 0D in the data area considered as Carriage return
Apprentice
Joined: 07 Sep 2004 Posts: 39
When -20.00 get converted in EBCIDIC format with signed over punch the resultant binary data is 0000000200D. there is a 0D in the data area.Data is written to a file using Fileoutput node.When target application parse the file, even records are getting splited into peaces when application see record delimted hexa value in the data.Even when i open the file on the broker server i can see records been splitted into two lines due to oD.
How to make broker not to consider 0d as Carriage return if it comes as part of data. How to view data as one record when 0d appare.
Sounds like the application in question is not expecting a signed decimal field there and is reading it as character data ....
Quote:
How to make broker not to consider 0d as Carriage return if it comes as part of data
Well, don't try and parse it as character data when it isn't. You need to use MRM domain to parse the data so that these signed fields get interpreted correctly.
Even when i open the file on the broker server i can see records been splitted into two lines due to oD.
Seems to me your file viewer simply interprets the 0D, use another one that does not or a hex viewer. Same for the application which probably also interprets the 0D for some reason.
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