Re: Wisdom of just a SAVSYS after an upgrade

I agree with "Save Entire system". In an effort to limit the time that takes, if deemed necessary, I choose to perform two SAVSTG for a system that has a fast tape drive. That of course limits the recovery options to either a scratch to pre-upgrade, or /RSTSTG/ to post-upgrade. However Save Storage enables the quickest and easiest method to get back to the point in time just after the upgrade completion.

In Beta testing, to verify install & post-install, I also schedule Save Changed activity and two SAVSTG just before the upgrade, with the Save Entire System done as recent as possible before the upgrade as can be accommodated to limit the amount of Save Changed. That allows similar ease in reverting to pre-upgrade; i.e. not having to scratch install, just Restore Storage and Restore Changed to revert. If there were problems with the install, conversions, or some application, it is easy to go back -- and try/test it again later, after fixes for whatever error was causing the difficulty. That process obviously does not apply directly to the typical install scenario, but it sure is nice in those rare cases where an urgent situation dictates; if for example, the primary business application refuses to play nice on the new release, and the time to implement a circumvention or to get the fix requires an indefinite amount of time, as compared to a known amount of time required for a restore storage.

Regards, Chuck