Re: RE: RE: RE: Rebuild Access Paths

That's just it -- I'm not using CPYF, I'm using RSTLIB to a different
(empty) library. Since the original save doesn't save access paths, the
restore doesn't restore them (?? I think it's that simple). Several people
have told me I _should_ save access paths, and I'm not going to argue with
them; instead, I'll just mention that this is not my decision.

I've considered CPYF with *REPLACE, but that has its own set of problems
-- principally, that the production files have ever-changing members that
get created and deleted on a daily basis. I know how to get around that,
but we also have occasional level differences between the test and
production systems -- again, much as I might wish to control this
situation I'm just the guy picking up the pieces.

Still, I appreciate all the suggestions -- they've all been very helpful.
Thanks!

MIDRANGE-L@midrange.com writes:
>If all the files are set to *IMMED, then you shouldn't have to open them.
>Copying the data into the physical file using *REPLACE should invalidate
>all
>indexes then rebuild them when the copy completes.  If you have to open
>them
>before they rebuild then they aren't set to *IMMED or you are doing
>something else clever that is preventing the ordinary stuff from working.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com


+---
| 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
+---