On Thu, 16 Jun 2022 14:50:18 +0000, Seymour J Metz wrote:
>Only from the perspective of the submitter, not from the perspective of the
>installation.
>
Which of my two paragraphs are you addrressinig?
In either case, the submitter is the one who cares.
Since (I believe) the system symbol facility antedates the
JCL SET statement, the rule should have been that system
symbols be honored unconditionally in SET with no
compatibility impact. The programmer could then have used:
// SET jcl-symbol='&system-symbol'
and used &jcl-symbol freely subsequently.
________________________________________
>From: Paul Gilmartin
>Sent: Thursday, June 16, 2022 9:27 AM
>
>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
