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.
But JES2 does not have an enqueue on the dataset after it is read into memory Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Mitch > Sent: Monday, December 09, 2013 9:10 AM > To: [email protected] > Subject: Re: JES2 Proclibs > > Matt, > > I may be wrong, but I think it can be as simple as what you are suggesting, but, you > would have to be 100% sure there would be no access of any kind against the > library while you are doing this. > > Regards, > > Mitch McCluhan > > > > -----Original Message----- > From: Dazzo, Matt <[email protected]> > To: IBM-MAIN <[email protected]> > Sent: Mon, Dec 9, 2013 8:02 am > Subject: JES2 Proclibs > > > We are running zos1.13, jes2. I have a production proclib in the jes2 proclib earch > string. This proclib is a pds that is running out of directory blocks. > here are no enque's on the proclib except for when someone is working in it. > inally the question, can I just create a new larger proclib, copy of the embers over > and then rename the pds's or will JES2 become very unhappy? IPL equired? > Thanks Matt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
