> Why is a utility targeted for IBM mainframes (other than Linux for z) > translated into "ASCII"?
My guess is there was no "why." They just downloaded it and the default was ASCII translation. It's bitten me more times than I care to admit. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, July 8, 2020 8:58 PM To: [email protected] Subject: Re: SuperWylbur Users On Wed, 8 Jul 2020 17:28:17 -0700, Charles Mills wrote: >Regarding 2: *if* it was a "round trip" translate table and *if* one could >get a copy of the table then the IEBCOPY data could be reconstructed >programmatically. > >Even if not, I suspect that if one defined the problem not as "do a 100% job >of recovering *any* IEBCOPY unload that has been translated to ASCII" but >rather as "do a 95% job of recovering FB/80 source code" that one might have >a manageable task. Not trying to "undo" the translate but just looping >through the unload data and pulling out the actual source records. > One of the worst possibilities is that they used the "dd" utility: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/dd.html#tag_20_31_18 ... which converts between no two identifiable code pages. Why is a utility targeted for IBM mainframes (other than Linux for z) translated into "ASCII"? That makes about as much sense as translating the Zohar into Sanskrit. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
