I'll be honest, I *don't* like JCLLIB's. Operationally, they are fine, but problem is JCL can now be scattered to the corners of the datacenter and possibly to generally unknown locations. When one wants to facilitate mass JCL changes due to some change in the environment, it is very hard to quantify the scope of the change.
We do use SEA JCLPLUS which you do just give it the library where the Job control lives, and it will chain down and expand all the procs wherever they may be. Now its identified, but could be in 100's of different proclibs. Again, not insurmountable, but just makes life harder. Used to be you a finite(small) set of PROCLIB's that you *knew* contained all JCL and could easily react to changes. _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Services [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
