On Wed, 9 Aug 2023 17:12:41 +0000, Seymour J Metz wrote:
>"The system treats double ampersands as a single character. "
>
I see that. Also, elsewhere:
Determining equivalent JCL
• Does not compress double ampersands within symbols that are enclosed in
apostrophes.
ObEmerson: Grrr! And later:
• Symbols on JCL records are treated as if they were resolved
simultaneously.
I take " simultaneously"to mean (not clearly stated) that it does not
subsequently
resolve the apparent symbol introduced by the resulting ampersand. IOW,
doubling the ampersand serves to prevent symbol resolution.
So &&SYSUID should not be resolved as a JCL symbol.
________________________________________
From: Paul Gilmartin
Sent: Wednesday, August 9, 2023 12:01 PM
On Wed, 9 Aug 2023 13:57:21 +0000, Seymour J Metz wrote:
>The form DSN=&&&SYSUID may not be explicitly documented, but its
>expansion is a direct consequence of the documented rules.
>
I trust Hayim's explanation. DSN=&&&SYSUID should not be the same as
DSN=&&userid
if the two differ. What documented rules do you mean.
>________________________________________
>From: Hayim Sokolsky
>Sent: Wednesday, August 9, 2023 9:47 AM
> ...
> * As an undocumented trick, DSN=&&SYSUID can be used to cause
> substitution as if DSN=&&userid was specified.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
