On Wed, 8 Jul 2020 21:51:11 -0700, Charles Mills wrote: >> 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. > Are the code pages used for that default translation documented?
I know, rather, there is documentation for using Assembler and Binder to create private translation tables painstakingly by typing hex constants, but no supported simple way to create such tables in terms of given CCSIDs. On Thu, 9 Jul 2020 13:23:16 +0000, DAL POS Raphael wrote: > >Wilbur source is not that "trashed". >After uploading it to USS I can access the code in a perfectly readable way >using ISPF Edit : > >EDIT /u/sys56/WYLORV/Mainframe/GG.PUB/WINGS.COMMANDS Columns 00001 00 >Command ===> Scroll ===> C >****** ***************************** Top of Data ************************** >000001 ; >000002 ; Wings - ALLOCATE command >000003 ; > Yes, but perhaps you're one of those eccentric programmers who doesn't reflexively copy any zFS files to a PDS ASAP! >I use ISPF 3.17 to access the directory. Edit the member on the displayed >list. >Just that you must specify ASCII on the Edit Entry panel: > >Data Encoding >1 1. ASCII > 2. UTF-8 > If you tag the files with the proper CCSID, that's automatic subsequently. It's marvelous! I've even displayed UTF-8 files containing a mix of Latin and Cyrillic characters on x3270 set to CP880. Hex display of UTF-8 is shabby; not vertically aligned. (Are there DBCS terminals? Does ISPF support them?) >Furthermore you can use CUT and PASTE to copy it to a regular PDS. > Do SAVE and COPY to PDS(E) work likewise? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
