Hex 41 character in mainframe
Hi, I am getting a mainframe file from client which contains many spaces, but one of the space is showing as 41 when I looked at it in hex on mode. Even client is not sure how he got this. Could you please help me what could be the reason behind this issue.
Software/Hardware used:
os390
Software/Hardware used:
os390
ASKED:
July 5, 2011 11:18 PM
UPDATED:
March 31, 2012 10:15 PM
Approved Answer - Chosen by Prakashpcs (Question Asker)
'Required space' is an extremely useful Wp control, and it's handy when you need an inserted character, but one which doesn't display.
Accepting the premise that 'he who gets the data, translates the data' then scan the record for any non-print value. That would be, you leave A-Z a-z 0-9, maybe some punctuation £$%"1@+- etc, and discard the rest.
At least, when you have established the 'rules' yourself, you know what is entering your system, and therefore you have some assurance that your system will handle it.
The surprise appearance of a decimal point in a value field has been known to be , well, a surprise.
Other Answers:
Latest Answer Wiki Contributors:
To see other answers submitted to the Answer Wiki: View Answer History.
Generally, an EBCDIC x’41′ character is a non-breaking space.
But I don’t know of any way to determine how it got in to the file from your client without knowing all about the process used by your client to prepare the data.
Tom
…scan the record for any non-print value.
Always being careful with binary/packed data (as mainframe files often have) as well as CCSID issues.
Tom