>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> -- 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: Wednesday, June 6, 2018 1:26 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Use of dynamic system symbols in JCL On Wed, 6 Jun 2018 11:51:30 -0400, 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. > Bug? Feature? I call it a primeval bad design. Any use of an undefined symbol should always have resulted in a JCL error. Except, does support of DSN=&TMP antedate any support of symbols in JCL, not only by SET but also as PROC parameters? When to double ampersands and apostrophes get resolved? I believe that regardless of MSGLEVEL, when I code: //EXEC PGM=IEFBR14,PARM='O''Reilly &&SYSUID &SYUID' //SET RFM=FB //SYSUT2 DD DISP=(,PASS),DSN=&&TMP,RECFM=&RFM, ... I still see double ampersands and double apostrophes in the JCL substitution messages, but they are collapsed by the time the program inspects its PARM. -- 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
