1)Create a windows based EXE file that converts EBCDIC Fields into ASCII and also unpacks packed fields as per the attached layout of 840byte per record length. 2)The program will put a carriage return and line feed after each record. ## Deliverables Need a fully functional EXE file that will have ask for the input data and create output data in the same folder with a carriage return and line feed after each record of 840 bytes as per layout. ## Platform Windows 98SE, ME, 2000 & XP Skills:,,,,,,, See more:,,,,,,,,,,,,,,,,,,,,,,.

So you pack the sequences '15' and '25' into the bytes 21 and 37. Which are x'15' and x'25' respectively. That part is correct. But converting those bytes to a using CP037 converts them both in the the character whose Unicode value is 10. (This isn't all that surprising because both of them represent line-ending characters in EBCDIC and you are actually saying 'These bytes represent a string in EBCDIC, so convert them to a Unicode string'.) It's possible that there are other situations besides this one where the conversion maps two bytes to the same character, but I haven't done that.

I assume you're doing this EBCDIC-to-Unicode conversion because sending the result string to the database does a Unicode-to-EBCDIC conversion automatically for text data, and you're attempting to do the inverse so the end result is the original bytes you packed. But here it doesn't work because the bytes you produce aren't actually EBCDIC characters. So it's a cheap hack which turns out not to work. Movavi Video Converter 12 Keygen more. I vaguely remember thinking this sort of thing was a good idea several years ago, but I quickly found it wasn't.

It was just a pain in the behind. I found that making the fields on the mainframe NOT be packed decimal (but zoned decimal instead) was much easier to deal with. Or using to access well-structured records, that worked well too. Creativemarket Angelline Script 214094 Down there.