> 4. Source code EBCDIC-ASCII translation. Example: I hate REXX > translation. REXX use || characters while in CP852 it should be !!.
Rubbish. It is not the fault of CP852, C or REXX. CP852 has | and ! at the same code points as CP437. The issue is the EBCDIC code page and translation that you're using. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Radoslaw Skorupka [r.skoru...@hotmail.com] Sent: Friday, January 29, 2021 6:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Inspecting and extracting from /OS transportable files on other platforms? I did it. There is no simple solution, not "one size fit all". Few remarks: 1. EBCDIC-ASCII conversion. It is crucial for text file, however sometimes record contain binary fields which should not be translated or the translation is quite different. 2. Programs. There is no big reason to migrate PDS libraries (program objects or load modules). 3. Source code. Why? It's not so obvoius. 4. Source code EBCDIC-ASCII translation. Example: I hate REXX translation. REXX use || characters while in CP852 it should be !!. Simple translation corrupts REXX code. C code is corrupted as well. 5. PDS/PDSE data. It is simple to download XMI files or just convert PDS(E) to directory of members. Why? 6. "Archival purposes" can be EASILY fulfilled with ADRDSSU DUMP "all files" and then XMIT and download. It is good archive, but it is readable under z/OS. Bad? This is the only 100% exact copy. And let's imagine, you can use two (or more) ways - one for "exact, but unreadable copy", other for more readable copies, but not necessarily exact. -- Radoslaw Skorupka (currently unemployed) Lodz, Poland W dniu 28.01.2021 o 23:31, Gibney, Dave pisze: > Isn't that a long winder subject? > In preparation for shutting down my z/OS 2.3 system, sometime this year, > I am looking at options for unloading/storing both my z/OS files as well as > my application data and infrastructure files. > I thought of experimenting with GIMZIP. Which, for a PDS/E uses IEBCOPY > to create a sequential unload and then uses pax to create a > Snnnn.dsname.pax.Z file containing the unload and a GIMFAF.XML descriptive > file. > I can download the .pax.Z file, and using 7zip decompress it. > I looked on CBTTAPE.org and found the Xmit tools, and some terse/unterse > options. And tools for .aws files. > I didn't find anything to process ot look at IEBCOPY unloaded files. Does > such a tool exist out there. > > I can of course TRANSMIT (and even AMATERSE it) before GIMZIP, or run pax > outside GIMZIP. But, I'd kind of like the GIMFAF.XML file... > > Dave Gibney > Information Technology Services > Washington State University > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
