I'm running BC 3.3.13 on Windows. First of all, I should point out that this is not a big deal.
Background. I've written my own plug-in in Reginald Rexx for mainframe files created in a product called Mainframe Express (MFE). MFE creates "mainframe" files on the PC so you can run mainframe JCL and debug Cobol programs. I've been using this plug-in for some years now with great success. The other day, however, I was comparing 2 before-and-after files and was surprised to to see loads of data converted, but then being shown with "missing" hex values (you can see this in the new_vs_old screen capture (SC) at the bottom). The MFE_file_contents SC shows what's actually in the file (albeit, in EBCDIC) and the weirdest (?) thing is that the new_vs_new SC shows the contents of the file as I expected to see on the one side in the new_vs_old SC.
I was suprised enough that I mucked around with it at home and could confirm that my plug-in reads the relevant records and translates them from EBCDIC to ANSI correctly. Any thoughts on what might be happening?
Background. I've written my own plug-in in Reginald Rexx for mainframe files created in a product called Mainframe Express (MFE). MFE creates "mainframe" files on the PC so you can run mainframe JCL and debug Cobol programs. I've been using this plug-in for some years now with great success. The other day, however, I was comparing 2 before-and-after files and was surprised to to see loads of data converted, but then being shown with "missing" hex values (you can see this in the new_vs_old screen capture (SC) at the bottom). The MFE_file_contents SC shows what's actually in the file (albeit, in EBCDIC) and the weirdest (?) thing is that the new_vs_new SC shows the contents of the file as I expected to see on the one side in the new_vs_old SC.
I was suprised enough that I mucked around with it at home and could confirm that my plug-in reads the relevant records and translates them from EBCDIC to ANSI correctly. Any thoughts on what might be happening?
Comment