Will ISPF correctly process a panel contianing 0A, 0D and 15 if it has FILEDATA=RECORD?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Tuesday, July 28, 2020 3:03 PM To: [email protected] Subject: Re: OMVS CP command anomaly On Tue, 28 Jul 2020 11:33:18 -0500, Lionel B Dyck wrote: >The problem is the x'0D' and x'15' characters which were generated from DTL. >They copy (cp) fine from z/OS to OMVS but the copy back causes the data after >either of those characters to go to a new record. > I'm inclined to regard the output of a language translator or generator such as DTL as a binary object akin to SYSPUNCH/SYSLIN, subject to editing only at the user's own risk. For storing binary objects (other than program objects) in zFS is FILEDATA=RECORD. That is transparent to and supported by utilities such as IEBGENER. ISPF Edit seems savvy to RECORD, but I've made only a cursory try. I don't know that ISPF with RECORD preserves trailing blanks. I doubt that OCOPY, OGET, OPUT, or /bin/cp supports FILEDATA=RECORD. How does git/zigi deal with executables/program objects? >The solution is for the DTL developers to use the ISRDTLCV after they generate >the panel. > ... subject to its own limitations. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
