On Sat, 9 Jun 2018 14:25:56 -0700, Tom Brennan wrote: >And I'm one of the perpetrators! For a long time I thought the single >asterisk was proper and whenever I saw the double I assumed it was a >mistake that just happened to work. > No, conventional behavior nowadays. JCL collapses a double ampersand to a single, but supprsses symbol substitution.
>>> On 6/6/2018 8:51 AM, Steve Smith wrote: >>> >>>> This has been previously discussed. The main issue (as usual) is >>>> incompatibility with an ancient bug (or feature). Specifically, temporary >>>> dataset names such as DSN=&TMP. That's supposed to be DSN=&&TMP, but >>>> for >>>> whatever reason, the single-& version works, unless &TMP is a symbol. >>> Aboriginal behavior: On Wed, 6 Jun 2018 18:02:13 +0000, Seymour J Metz wrote: >>Except, does support of DSN=&TMP antedate any support of symbols in JCL, >> not only by SET but also as PROC parameters? > >Yes. Bitsavers is your friend. ><http://bitsavers.org/pdf/ibm/360/os/R01-08/C28-6539-4_OS_JCL_Mar67.pdf> > (See Page 23. There were *no* symbols in JCL then!) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
