An obscure question but just the kind I know SU users might be able to help with.
I've got a file from an iSeries that's encoded as CCSID 65535 (binary) which basically means that it's hex encoded (in EBCDIC). I'd like to understand how that format works as it seem to arbitrarily skip in and out of the hex encoding. For example:
4040404040404040404040F3F040404040404040404040F1 0 04040404040404040404040F8F0F0F3F54040404040F3F4F0404040F3F0F3F8F1F1F7F1F0F8404040404040404040404040404040404040 2009E2D5F9F6F0F0F0F0F0F7 0 04040404040404040404040404040404040404040
The 40 are EBCDIC spaces, this I know but you'll see that there are literal spaces in the text as well. The transitions happen on odd and even byte boundaries and looking that the first section with literal spaces "F1 0 040" you'll see a hex encoded '1' ("F1"), several literal spaces, a literal '0', some more spaces, a literal '0' again and then a hex encoded space. Tearing my hair out here, there seems to be no logic to it.
I suspect that the 'knowledge' for the format may be held in the iSeries in a separate definition but I can't find any definitive documentation on the web so I'm hoping that a guru here may know how this all fits together. Any guidance gratefully received!