On Wed, 30 Aug 2023 15:59:02 -0500, Mike Schwab wrote: >On Wed, Aug 30, 2023 at 3:32 PM Paul Gilmartin wrote: > >> And I've seen no good explanation for "&&TEMPDSN" >> As s test, I posted that, not via WWW but by Mail, which I rarely do. The paired ampersands were properly decoded.
>S/360 started with &tempdsn. >Later (S/360-370), // SET VAR=value was added. >Created &&tempdsn is always &tempdsn. >&var picks up the SET value and if none is specified it uses the name >of the var. > But it fails to clarify what happens if: o a value *is* specified o the specified value begins with one ampersand o the specified value begins with two ampersands The JCL Ref. misleads readers to believe that the paired ampersands are special in the case of temporary DSNs. I believe otherwise. The pleonastic discussion of paired ampersands vis-a-vis temporary DSNs is anachronistic and phobic. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
