I will take a contrary due here. I never did trust SMPE with DDDEFS I always coded the JCL and I always know what libraries were being used/updated. Its too easy to make mistakes with DDEF’s (IMO). JCL is easy and straight forward in my opinion. Especially when you have too many fingers in the pipes (i.e. trainee’s but I have seen seniors screw up as well.
Ed > On May 5, 2016, at 6:16 PM, Andrew Rowley <[email protected]> > wrote: > > On 6/05/2016 8:11, Mark Zelden wrote: >> 1) There is a DDDEF called AAAA. It points to a DSN defined with DISP=SHR >> (no volser / unit). >> 2) The SYSLIB concatenation includes DDNAME AAAA (last in the concatenation, >> I didn't >> test a different order). >> 3) At execution time DD AAAA is overridden in the JCL to point to a >> different VOLSER than >> the cataloged version. >> 4) The data set used in the SYSLIB concatenation is the cataloged version, >> not the override. > > I think it is the behaviour I would expect. > I think the SYSLIB concatenation includes DDDEFs which specify datasets, not > DDNAMEs. > > Overriding SMP/E DDDEFs via JCL always seemed to me like it was a bad thing > to do... I always felt that the SMP/E zones should contain all the > definitions for the installation. Overriding DDs seemed like a recipe for an > inconsistent installation if e.g. some people did the override and others > didn't, or if some overrides became out of date. > > -- > Andrew Rowley > Black Hill Software > +61 413 302 386 > > ---------------------------------------------------------------------- > 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
