I think that a better subject/question (accompanying that with information
about what you tried) would have been:
In IPCS, how do you access 64-bit storage? I tried using ADPLSACC and that
didn't seem to work with the options that I used which were
Some code I have seen uses BLSRESSY with
On 9/20/2023 8:23 AM, Farley, Peter wrote:
I believe that statement in the JCL Reference is in error and needs to be deleted
or at the very least completely rewritten. My quite substantial experience using
this technique over the last 10-15 years is that using JCL symbols as part of the
defin
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
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
I’ll admit I have NOT used symbol substitution in the “name” part (left of the
“=”) at all, only on the right (value) side, so the true answer is “I don’t
know”. Never had a reason to use substitution in the “name” part.
I personally haven’t had reason to use dynamic system symbols that could c
To be honest I consider date-related variables as pooor when
compared to batch scheduler features, especially ControlM (it is not
advertisement, just opinion).
Justification:
More possibilities of when the date should be resolved. For example it
can be "accounting date" - job should prepare
