Re: Copyng a library

On 04-May-2016 04:57 -0500, Paul Bailey wrote:

I need to create an infrequently used copy of our live data every
month. It has to be a complete copy, so originally we were using
CPYLIB. But CPYLIB takes an extraordinarily long time to do the job
and interferes with the day-to-day processing if (when) it runs into
the work day.

Recently we decided to use RSTLIB instead which would restore the
nightly backup from the tape and even if the job did run slowly it
would not affect the users. However, both DLTLIB and CLRLIB take even
longer to clear the backup library before we can restore to it.

After some investigation I discovered that the backup library is
journaling to the same journal as the live data after a RSTLIB but no
objects are journaled after a CPYLIB. I'm guessing that the
journaling is causing the CLRLIB to take an exceptionally long time,
and no journaling is required on the backup copy, so can anyone
advise how I can use RSTLIB but prevent the journaling from starting
on any of the objects restored?

I expect the "guess" is incorrect. Easily enough tested; prepend the Clear Library [or Delete Library] with the required End Journal request(s) to ensure none are journaled. Then compare that scenario to the time taken in scenarios without having first ended journaling.

In the following post, see my comments at\since "QDFTJRN feature":
[http://archive.midrange.com/midrange-l/201111/msg00130.html]

See essentially the same information given here; but more current information as well:
[http://www.shieldadvanced.com/Blog/disaster-recovery/ignore-journaling-when-restoring-objects/]