I resemble that example. But point taken. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Friday, June 5, 2020 8:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Gratuitous EXECIO Documentation CAUTION EXTERNAL EMAIL In: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/dup0037.htm I see the verbiage: When you use EXECIO, you must ensure that you use quotation marks around any operands, such as DISKW, STEM, FINIS, or LIFO. Using quotation marks prevents the possibility of the operands being substituted as variables. For example, if you assign the variable stem to a value in the exec and then issue EXECIO with the STEM option, if STEM is not enclosed in quotation marks, it is substituted with its assigned value. Sheesh! A similar caution might be included for any command in the Ref., but it doesn't belong. "must ensure"? Well, not always. I infer the etiology: A troublesome user once coded: STEM=SKIP /* perhaps */ EXECIO ... ... got astonishing results; went to SR; got fully proper "REJ; RTFM"; vindictively submitted RCF. A feckless tech writer acceded and added the paragraph. I strongly suspect the matter is covered properly earlier (citation needed) in the Ref., which shouldn't be cluttered with such errant rubbish. (I was reading that Ref. to see whether EXECIO assembles segments of V[B]S records. Didn't find it.) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
