Re: Wisdom of just a SAVSYS after an upgrade

Other than the obvious goal of protecting the work (and possible downtime)
spent on the upgrade, in my mind a system is at increased risk just after
an upgrade for a time period. I wouldn't consider skipping the after
upgrade save... it's just of too much potential value. Let's say you have
some strange data/application/integrity problem discovered a day after the
upgrade that needs fixed quick and will require a restore... how bad would
it be to have to restore, then perform a 6 or 8 hour upgrade before getting
things back in order (without having the downtime set aside, activities
planned out, detailed checklists, etc.).

I'm pretty sure you're on the same wavelength here, Rob - you'll get some
good ideas to help convince your boss, hopefully.





rob@xxxxxxxxx
Sent by:
midrange-l-bounce To
s@xxxxxxxxxxxx midrange-l@xxxxxxxxxxxx
cc

11/29/2007 01:20 Subject
PM Wisdom of just a SAVSYS after an
upgrade

Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






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
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.