Re: CPYLIB - file locks?

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

Hi, Ryan:*
*
You could try something like this:

1. create a save file:
 CRTSAVF   yourlib/yoursavf

2. save the contents of the library, using "save while active":
    SAVLIB  LIB(datalib) DEV(*SAVF) SAVF(yourlib/yoursavf) SAVACT(*LIB) +
           SAVACTWAIT(600) UPDHST(*NO)

3. create a new (empty) library to restore into:
 CRTLIB   LIB(newdatalib) TYPE(*TEST) TEXT('description')
  
4. restore the data saved above into this new library:
 RSTOBJ OBJ(*ALL) SAVLIB(datalib) DEV(*SAVF) SAVF(yourlib/yoursavf) 
RSTLIB(newdatalib)

All the best,

Mark S. Waterbury

> Ryan Hunt wrote:
> I need to copy our production data to dev data. We've segmented this data by
> library.  So, when I need to copy I typically just run a CPYLIB command and
> let it run over night.  I have a need to do this during the day and need to
> know if my production data (the source) will experience any locks that could
> impact production?
>
> Anyone know?
>
> Thanks. RH
>
>
>
>