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. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Wednesday, July 8, 2020 4:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SuperWylbur Users 1. I would be willing to bet that if Gerhard gave up on it then it was well and truly hosed. 2. The web site mentions IEBCOPY unload. If they translated that to ASCII then you're in for interesting times. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
