On Tue, 28 Jul 2020 10:07:50 +1000, Andrew Rowley wrote: >On 28/07/2020 4:48 am, Lionel B Dyck wrote: >> Created several ISPF panels from DTL. The result is an ISPF panel with >> attribute characters that are binary (hex) with examples being x'01' , >> x'02', x'05, x'0D', and more. >> ... >> The problem/anomaly is copying the files from OMVS into z/OS dataset members >> results in these members being corrupted with the single record being >> broken into one, or more, records. ... > >Copying binary data as text is not guaranteed to give the correct result >after a round-trip. ... > >Options: >- ... >- Copy as binary. The best-simplest option, however it would also cause >merge etc. problems >- Use an escape character scheme for binary characters e.g. quoted >printable. This adds a processing step - you can't use regular cp >command - but it gives you data in git that is mergable and mostly >readable as text. > Doesn't ISPF support panel definitions coded in Rexx? Rexx would allow representing those nondisplayable characters as hexadecimal strings.
It would be wonderful if ISPF supported UNIX directories in the ISPPLIB (and other) concatenations as described in Using Data Sets, eliminating the need for the back-and-forth copying. RFE? There are workstation ISPF lookalikes. How portable are panel definitions to those? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
