@Gil, which IBM? <g> This is a Dallas system, and it is set up the way IBM sets up Dallas systems, which might be a third case in addition to "defaults" and "recommendations." We have changed very little of that sort of thing.
@Ed, thanks, but now what? Using IEFJOBS to define started tasks Last Updated: 2023-03-29 If MSTJCLxx contains a DD named IEFJOBS, the source JCL for a started task can be placed in one of the data sets within the IEFJOBS concatenation. Doing so allows jobs and the procedures they invoke to have the same name. These jobs can contain the minimum set of JCL needed to define the job level characteristics (for example, JOB statements, JCLLIB, and JECL), and then either invoke an existing procedure or use the INCLUDE keyword to invoke the desired set of JCL. Why would I want to do that? How would that solve my problem? Is what you are alluding to perhaps that I do not want to change SYS1.PROCLIB because a PTF or new release might overlay it? If so, not a problem. It's a Dallas system. SYS1.PROCLIB is read-only. (The magic of VM!) I would create an edited copy of BPXAS in a "Dallas-standard" customer proclib that is concatenated ahead of SYS1.PROCLIB. Or is there something else I should be grokking about IEFJOBS? Charles On Mon, 10 Apr 2023 17:59:52 -0500, Paul Gilmartin <[email protected]> wrote: >On Mon, 10 Apr 2023 17:11:11 -0500, Charles Mills wrote: >> >>Okay, I confirmed that MSGCLASS=Z will make output magically disappear. >> >Had you been taking all IBM's defaults: SYSOUT class, disposition of that >class, etc.? > >If so, IBM's design is adverse. > >But, "IBM's defaults are not IBM's recommendations!" (source obscure) >(E.g. BLKSIZE=3120) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
