Orthogonality is conspicuous by its absence. It were ever thus.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [0000000433f07816-dmarc-requ...@listserv.ua.edu] Sent: Monday, December 14, 2020 12:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL PARM issue On Mon, 14 Dec 2020 11:56:53 +0000, Seymour J Metz wrote: >Yes - you only have one level of expansion. > And doubled ampersands in the PARMDD file are not collapsed. This is documented. I have found that there is a circumvention for the convention that prohibits using JCL symbols in quoted strings in the SET statment. Something like: // SET Q='''',X='Middle' // SET TRIAD=&QLEFT&X.&RIGHT&Q Of course that is covered by the rule: • Do not specify JCL symbols within other JCL symbols. The results can be unpredictable, especially if the imbedded JCL symbol is not previously defined. "unpredictable" is feckless engineering. IBM simply doesn't care to document the behavior lest IBM be subject to SRs when the system transgresses such rules. The JCL Ref. has 18 pages describing the behavior of symbols, mostly exceptions. This is a symptom of design inconsistency -- Conway's Law. >________________________________________ >From: Paul Gilmartin >Sent: Sunday, December 13, 2020 3:43 PM >> >It's time for an RFE for the equivalent of HLASM's DOUBLE BIF. No "Maybe". > >Does PARMDD handle this better? -- gil ---------------------------------------------------------------------- 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