If the procs/jobs etc were to include the joblibs/steplibs via the JCL INCLUDE statement, instead of explicit coding, there would be only 1 item to change (per application silo), the included member containing the joblib/steplib concatenation.
'Sorry for the confusion. <<snip>> Not sure what your question is. Converting the libraries in place won't affect JCL includes. _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: Tuesday, September 24, 2013 9:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PDS/E, Shared Dasd, and COBOL V5 JCL includes? <snip> For us there will be no Step1 or Step2. We will Convert existing loadlibs from PDS to PDSE. There is way too much application JCL to change to think about changing the concatenation. </snip> <</snip>> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
