RE: Duplicating a library.

[Joe Giusto <JGiusto@xxxxxxxxxxxx>]

Actually, the access paths of the logical will be rebuilt, but one record at
a time (if I understand it correctly).  Does this take more or less time
over all?  I will leave that answer to someone more enlightened.  However,
what about changing the logicals in the test environment to *DELAY or
*REBUILD the access paths so that they only get rebuilt if they are needed
for testing on that day.  A little longer on the first test run but the copy
should go faster.  Also, I usually CPYF with FROMRCD(1) so that the system
does not have to read the physical by key for the copy.

Joe Giusto II
Patuxent Publishing Company
10750 Little Patuxent Parkway
Columbia, MD 21044
mailto:JGiusto@patuxent.com <mailto:jgiusto@patuxent.com> 
http://www.lifegoeson.com <http://lifegoeson.com> 




-----Original Message-----
From:   Denis Robitaille [SMTP:DRobitaille@cascades.com]
Sent:   Wednesday, June 28, 2000 9:48 AM
To:     MIDRANGE-L@midrange.com
Subject:        RE: Duplicating a library.

Assuming that the library is stable (the sources of the PF and LF do not
change much), you could do the following:

Instead of the save/restore, create a CL that do a CPYF of all the PF form
the production to the test library. This way, you avoid all the file
creation and all the access path rebuild.


Denis Robitaille
Directeur services techniques
Cascades Inc
819 363 5187
fax 819 363 5177





+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---