On Thu, 24 Aug 2023 17:02:48 -0400, Phil Smith III wrote: > >>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). > I'm ignorant, or at best outdated. I haven't known of use of symbols by SMP/E. But are there instances where the same &symbol would need to appear in one instream data set where it should be evaluated and in another where it must not, regardless of //name DD DATA,SYMBOLS=...? Cite detailed example, please.
There are ways. however cumbersome, to escape symbol evaluation in instream data sets. >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. > Better, to just change stuff in ONE JCLLIB member included in ALL relevant jobs. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
