Re: BRMS recovery report - recovery includes objects which were not saved - preparing for a P7 to P9 mibration

<snip>
How do others in the group handle IFS items "not saved" when preparing for
a P7 to P9 migration?
</snip>

I read the report. As you did, I would have noticed the
CPD37C3 - Cannot save /QFPNWSSTG.
And then I would have realized that I just saved my hosting lpar. And I
generally do not restore all my guests when I restore my hosting lpar so
this is all right.
If, however, you really wanted to restore the guests also then before the
save I would have ran
CHGATR OBJ('/QFPNWSSTG') ATR(*ALWSAV) VALUE(*YES) SUBTREE(*ALL)
I have done this, on RARE occasions.
Actually I have a
CHGATR OBJ('/QFPNWSSTG') ATR(*ALWSAV) VALUE(*NO) SUBTREE(*ALL)
right before my save in my documentation. This reminds me to change it to
*NO in case I ever changed it in the past. It also reminds me that if
this is one of those rare occasions that I really want to save it then I
should probably change this.
I also do a
CHGATR OBJ('/fixes') ATR(*ALWSAV) VALUE(*NO) SUBTREE(*ALL)
because /fixes is where my PTF and OS image catalogs reside. Again, there
are some rare exceptions where I want to save those also.

This is totally different than using Omit lists in BRMS. Omit lists are
easy to flag to ignore by simply using a parameter
STRBKUBRM CTLGRP(...) OMITS(*IGNORE)...
But this still will not save any directory with *ALWSAV turned off.


Rob Berendt