×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 20 Apr 2012 06:35, Tom Duncan wrote:
Is there any way to restore just the file structures of files in a
library without restoring the data too ? The only way that I know to
do that is to restore the files with the data then save them with
the STG(*FREE) option. That could require a lot more disk space than
is available. Surely there is a less painful way to do this.
The database restore capabilities include restoring just data into
existing member(s), member(s) with data, file(s) with member(s) with
data, or file(s) without members thus with no data; not that it applies
for this scenario, but there exists no option to restore member(s)
without data. This can be done on either the RSTOBJ, the SAVRSTOBJ
utility, and presumably the Restore a list of objects API.
The OPTION(), FILEMBR(), and MBROPT() parameters are used in
conjunction to control what of File, of File.Mbr.Data, or of Member.Data
that will be restored. When restoring just the database *FILE without
any members, the MBROPT(*ALL) must be specified [without understanding
the parameter, that may seem amiss at first glance] and either the
OPTION(*NEW) or OPTION(*ALL) must be specified.
Note that this type of restore is a /scratch/ restore, mimicking a DR
restore, such that private authorities would be lost if they were not
both saved and restored with the *FILE objects.
So given a SAVLIB MYLIB *SAVF SAVF(MYSAVF) /* no aut saved */, I
would issue the following request to get all database *FILE objects
restored from library MYLIB into library MYLIB [which was previously
cleared, or to a new system]:
rstobj *all MYLIB *savf *FILE savf(mysavf) option(*all)
mbropt(*all) /* must ask to include, to effect omit */
filembr((*ALL *NONE))
After the restore I might have to issue DLTF against all of the
non-DBF [because device files are included in OBJTYPE(*FILE)], and then
assign authorities as appropriate.
Regards, Chuck
midrange.com
