Re: How can I copy only certain file types to tape and/or

Vern,

Thanks for the ideas.   Yeah, I am aware of a solution using the
DSPOBJD.    

But before we thought of using DSPOBJD...,  Let me lay out in a little
more detail what I'm trying to do and what we've run into using the SAV
technique.   I think you're talking about the SAVOBJ command.    

At least from what I can figure out, SAVOBJ only allows a gross backup
of a particular library, that is to say PF and LF and allows you to save
them as a SAVF.  Yes, I know you can use some wildcards in the command
to narrow what your backing up, but if I want to back up all the PF in a
library I can not say particular attributes like PF, I have to back up
both (unless I use the DSPOBJD technique first).   So, using the
"native" technique my systems programmer was stuck with backing up both
PF and LF as they are of type FILE.   So, he'd save the following:

All FILES of library CXLIB, CRLIB, WFLIB and LXLIB.  These are the
production libraries.   We need to restore ONLY THE DATA to the same
named files but to different library names, such as, CXLIBTEST,
CRLIBTEST, etc.   What we found was, the restore went OK but the folks
using the TEST environment after the restore were seeing the latest
transactions of the PRODUCTION libraries on an ongoing basis!!!   My
assumption of the cause... because the LFs were forced to be restored
from the RSTOBJ command( because there is a TYPE of FILE but there are
no attribute choices), you get LFs pointing to the PRODUCTION
libraries.

So, we'll try the DSPOBJD technique.   

Now comes the second part...  Let's assume DSPOBJD works and we only
get the PFs and we restore them as outlined above.   What about the LFs
and/or access paths in the TEST environmnet(the target)... they are now
pointing to data of which some may be new and much expanded in numbers
of records since the last refresh?     What about access paths...Will I
have to run something to keep the users from suffering massive rebuilds
of the access paths when they first access the applications or what?   I
know there is a command.    Is it necessary to prevent the first access
problem?  I assume so.    

If the DSPOBJD technique works, we'll SAVOBJ to tape to save DASD space
during the backup.

Hope this makes sense.    Any gotchas you can see?

Thanks,

Dave