Hi Phil,
I beg to differ.
You can use SET at the top of every Job to set ALL variables (as my
previous email said).
Can you please give me an example of what you're saying.
Another thing ... Do you remember IPOUPDTE? (It was a batch "editor" to
change all of the HLQ from ABC to DEF. This could be used instead of the
SET.)
Regards,
David
On 2023-08-24 17:02, Phil Smith III wrote:
Gil wrote:
I introduced "symbols". Shmuel may have reintroduced it. Are we thinking of
the same
JCL SET? Where is its behavior inconsistent?
It's not SET that's inconsistent, it's support for it in SMP/E. There are
places in SMP/E jobs that can't use symbols. So you can't just have a chunk at
the top that job where you fill in values-you have to tour the job and fix it
27 times (OK, not 27, that's just a number I made up).
When I deliver the product to the customers, I'd like them to be able to just
change stuff in ONE place per job. Otherwise they can (AND DO) miss a few,
leading to hilarity.
----------------------------------------------------------------------
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
