Recently we have encountered an issue with Hex value 41, which also looks like SPACE in normal view.
We have received a file which had this value in between spaces. Say example “MINNI IS HERE”. The space that you see between MINNI and IS actually had a HEX value of 41 instead of 40 (SPACE).
This value is one time updated into ADMIN table, and then compared against the same column available in other tables. So here the issue is that ADMIN table had the issue character X’41’ and all other tables had valid data X’40’.
For naked eye, both the data looked similar, so it was not sure, whey there is no match found against the ADMIN table.
Identification and Resolution:
So SPUFI was run to get the data into a file, then its HEX value was compared between ADMIN table and other tables. Now issue char X’41’ was identified and it was updated with SPACE(X’40’) in the ADMIN table and NOW other tables were able to find the match in the ADMIN table.
Note:
If the issue char X’41’ needs to be replaced in multiple records in a file, the SORT options ALTSEQ, FINDREP can be used as shown in below posts.
——————————————————————————————————–
In United States, If you would like to Earn Free Stocks, Credit card Points and Bank account Bonuses, Please visit My Finance Blog
——————————————————————————————————–
You may also like to look at:
F1 for Mainframe 