I wish that IBM had (or would) support the SYMBOLS= keyword on JOB statements to allow system symbols in the JCL. The current jobclass spec would still be the default; and SYMBOLS=JCLONLY would still be the default default.
sas On Thu, Jun 16, 2022 at 9:27 AM Paul Gilmartin < [email protected]> wrote: > On Thu, 16 Jun 2022 13:09:53 +0000, Seymour J Metz wrote: > > >This has been discussed here many times. The issue is that the results > vary depending on ehrn and where you evaluate them. > > > Doesn't SYMBOLS=({JCLONLY|EXECSYS|CNVTSYS} suffice to resolve that? > > There remains the phobia concerning the antiquated use of "&" in temp DSNs. > > -- > gil > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
