On 14-Aug-2015 10:38 -0600, Jim Franz wrote:
I did a DSPTAP *SAVRST to print of a SAV of /EKDVIRTUAL (our
directory of virtual optical) and subtree=*ALL. This is not ptfs or
software, but real images. We are using the IBM PRPQ to handle
library mode=Yes on these.
We see the primary and second directory in the *SAVRST, but not the
Checked and have ALWSAV attribute set to *NO - but we don't know how
they changed from *Yes to *NO.
Likely Load Image Catalog (LODIMGCLG); see below.
When we test the unload, the attribute changes from *NO to *YES, and[
we do an unload just before SAV.
Do not have BRMS. V7R1
_Performing a save operations_
To save files to virtual optical storage, see Consider using virtual
optical storage in the Back up your system topic.
Note: When the image catalog is in ready status, all images in the
catalog have a *ALWSAV attribute value of *NO. This does not allow the
images to be saved by the Save Object (SAV) command or the QsrSave API.
When the image catalog is not in ready status, all images in the catalog
have a *ALWSAV attribute value of *YES. This allows the images to be saved.
3. If you want to exclude virtual images from a full-system save, use one
of the following strategies. Virtual images can significantly increase the
time it takes to complete an Option 21 save operation, even if the image
catalog entries do not contain data:
• Use the Change Attribute (CHGATR) command to mark the image catalog
directory as nonsavable. For example:
CHGATR OBJ('/MYINFO') ATR(*ALWSAV) VALUE(*NO)
• Use the Load Image Catalog (LODIMGCLG) command to make the image
catalog ready. Image catalogs with a ready status are omitted from the save
• In an attended save, you can specify to omit the image catalog
directories on the Save Object (SAV) command.
This trying to figure out what in IFS has ALWSAV = NO or YES (I
don't see anything on SAV that tracks this for verification). WhatThere should be the msg CPD3775 as an indication after-the-fact; I made
are others doing to be sure your backing up what you think your
several comments in the following thread [in English]:
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives