Instead of a save file you can use SAVRSTOBJ or SAVRSTLIB to concurrently
save and restore it to a different library on the same box. You get all the
benefits of the save while active and use less storage and time into the
bargain. Might get some hit on disk arm activity though :)

Be aware the CPYLIB does not get every object in a library; it will only
copy objects supported by CRTDUPOBJ.

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S. Waterbury
Sent: Tuesday, 29 September 2009 9:01 a.m.
To: Midrange Systems Technical Discussion
Subject: Re: CPYLIB - file locks?

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






Return to Archive home page | Return to MIDRANGE.COM home page