Dynamic symbols (date/time) can be evaluated at different points in
time during conversion, so if used multiple time in the JCL, they can
resolve to different values. My ROT was to never use a dynamic
symbol more that once in coding and where it was needed multiple
time, set it to my own date/time variable and then use that in the
multiple instances it was needed.
Michael
At 12:45 PM 10/7/2023, Paul Gilmartin wrote:
On Sat, 7 Oct 2023 09:41:56 -0700, Ed Jaffe wrote:
>On 9/20/2023 8:23 AM, Farley, Peter wrote:
>> ... JCL symbols as part of the definition of other JCL symbols
works flawlessly every time.
>
Is this true alike for substitution both in the name (left of the "=")
and in the value (right of the "=")?
In
<https://www.ibm.com/docs/en/zos/3.1.0?topic=symbols-determining-equivalent-jcl>
Substitute all symbols.
...
Symbols on JCL records are treated as if they resolved simultaneously.
Peter Relson (IIRC) answered my question hers that near midnight &DATE
and &TIME might be resolved at a time when their values are inconsistent.
This requires some explanation of "simultaneously". There ought to be
a lock to prevent this. (REXX does it right.)
And some explanation of the effect of resolving a symbol changing the
content of column 72 from blank to non-blank or vice-versa.
>Agreed 100%. We use that feature all the time for in-house JCL and also
>for distributed product JCL.
>
>This seems like a golden opportunity to test the IBM Documentation
>Feedback process.
>
>Give it a try and let us know if you actually get a response...
>
Yes.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
