On 9/24/2013 12:31 PM, Frank Swarbrick wrote:
These discussions sure make me glad we implemented steps that allow us to use a single,
shared include member for our "load library concatenation".
We have the following member named 'PROD.APPLIB.INCLUDE(JOBLIB)':
//JOBLIB DD DSN=EMER.APPLIB.LOAD,DISP=SHR
// DD DSN=EMER.PEPLIB.LOAD,DISP=SHR
// DD DSN=PROD.APPLIB.LOAD,DISP=SHR
// DD DSN=PROD.PEPLIB.LOAD,DISP=SHR
// DD DSN=PROD.UTILLIB.LOAD,DISP=SHR
// DD DSN=SYS6.IMP1.SDFSRESL,DISP=SHR
// DD DSN=SYS6.IMP1.DYNLIB.BTCH,DISP=SHR
// DD DSN=SYS3.DSN910.SDSNEXIT,DISP=SHR
// DD DSN=SYS3.DSN910.SDSNLOAD,DISP=SHR
// DD DSN=SYS3.MBC.LOAD,DISP=SHR
// DD DSN=CICS.SDFHEXCI,DISP=SHR
// DD DSN=PROD.VISAEP4.RULES.LOAD,DISP=SHR
// DD DSN=PROD.VISAEP4.LOAD,DISP=SHR
In the JES2PARM member we have this:
JOBLIBing everything has performance implications. We were also bit by
this when they included an old SORT steplib in the concatenation and
then SORT bombed on us.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
