Re: Wisdom of just a SAVSYS after an upgrade

Le: 29 nov. 2007, vous écriviez dans:
gmane.comp.hardware.ibm.midrange:

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?

We do the following when there are no user data conversion after a
release upgrade:

SAVSYS
SAVLIB *IBM
SAVLIB QGPL, QUSR*
SAV '/QIBM/ProdData' or something like that (I do not remember exactly,
if you have BRMS there is an appropriate link list)

This backup covers all updated objects when a release upgrade occurs.

If there are user data conversions (like V5R4 or .... V6R1), we perform
a full backup. Because, all objects are potentially (is this an english
word ?) updated.

Rob Berendt