Only if you can place the PROCLIB data set completely on the original TTRs. I do not believe this has changed.
You can use dynamic Proclibs (see $TPROCLIB) which are not bothered by the same issues as the ones in the JCL of JES2 or Master JCL If the Proclib is in the JES2 startup JCL then JES2 reads all of the members and places the TTRs in storage. If you move the proclib dataset, JES2 tries to read the TTR location of the member of proclib and if it is not there you get the JES2 I/O ERROR ON PROCLIB message. You can refresh the proclib TTRs by opening and closing a different PROCxx jcl statement in the JES2 Startup proc. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of R.S. > Sent: Monday, December 09, 2013 12:48 PM > To: [email protected] > Subject: Re: JES2 Proclibs > > W dniu 2013-12-09 17:14, Lizette Koehler pisze: > > Once JES2 is up, it has read the TTR information about the members in > > PROCLIB and will not be bothered by the removal, compress or move of a > > PROCLIB dataset. However, doing this could produce JES2 I/O ERROR > > message reading the PROCLIB members. > I dare to disagree. > You can add/change/remove proclib members anytime you want. Proclib is read at > submit time. > > > But JES2 does not have an enqueue on the dataset after it is read into > > memory > No enqueue - that's true. > > I'm not sure about OP's question, but my faulty memory tells me it's just matter of > PDS delete/rename and creation. > > > -- > Radoslaw Skorupka > Lodz, Poland > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
