RE: Wisdom of just a SAVSYS after an upgrade

["Evan Harris" <spanner@xxxxxxxxxx>]

Hi Rob

A SAVSYS wouldn't even get the licensed programs so by itself a SAVSYS after
an upgrade would be next to useless. Seems to me like using this as part of
the recovery would see you doing a install from previous release migration.
Madness in my opinion.

As others have said I like the safety of a full save following an upgrade
but quite often opt for doing an option 22 off the SAVE menu where there are
time constraints or the customer doesn't want to do the extra hours. That
allows us to recover the IBM components as required and the data can be
gathered from other tapes.

The day after the upgrade the data is in a new save cycle anyway so I don't
generally get to bothered by not repeating the full system save. 

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, 30 November 2007 7:22 a.m.
To: midrange-l@xxxxxxxxxxxx
Subject: Wisdom of just a SAVSYS after an upgrade

Skipping a lot of details but our basic steps to doing a release upgrade 
is:
Save entire system
apply ptfs perm, IPL
do the upgrade
Do a full system save.

The boss is wondering if we could just do a SAVSYS at the end.  My 
argument is that this isn't a S/36, or even an old AS/400.  That a release 
upgrade puts stuff into all sorts of libraries, directories, etc that a 
SAVSYS just doesn't begin to cover.  Including, but not limited to data 
conversions in QUSRSYS.  Then, there's the little things like object 
conversions, etc that sometimes happen with release upgrades.

If the goal is to be able to recover, do the full system save.  Otherwise 
you're stuck with the save PRIOR to the OS upgrade.

So who passes the whizz quiz:  the boss or I?

Rob Berendt