Re: SAVSECDTA from v5r2, restore on v6r1

[CRPence <CRPbottle@xxxxxxxxx>]

  The _restore_ is supported, even from the S/38.  However do *not* 
restore any of the pseudo-user libraries QUSRSYS, QGPL, or QSYS2, 
because _install_ is not supported beyond N+2.  Restore into those 
new libraries could be done with RSTLIB OPTION(*NEW) MBROPT(*ALL) 
ALWOBJDIF(whatever).  Even ALWOBJDIF(*ALL) is OK for these libraries 
_when using the option to restore only new objects_, but definitely 
*not* OK when using other OPTION() specifications; restoring new 
objects may cause obsolete objects to remain even after reinstall of 
those features, because there is no requirement to keep obsolescence 
processing beyond N+2.  Using OBJTYPE(*FILE) OPTION(*OLD) 
MBROPT(*NEW) would effect similar to the object restore, but 
restoring only new members; same caveat about obsolescing.

Regards, Chuck

Terry Richardson wrote:
> Is it possible and/or advisable to save security data from a
> v5r2 box and restore to v6r1? If this is possible, what are
> the potential gotchas? We have a client doing a box swap from
> an old 825 running v5r2 onto a new 8203-E4A running v6r1.