Paul--
If I follow your statements correctly, you're backing up the complete
system because you're about to apply permanently all of the PTFs
currently installed on your system. I assume you've been running
with these PTFs active (ie IPL from Side "B").
Also assuming that you've been running on these PTFs for several
weeks (or months), I feel there's little risk in just applying them
*PERM. Until now, IPLing from the "A" side would revert to the state
the system was in before the currently un-applied PTFs were applied
*TEMP.
Here's the sequence of events that we usually follow (If I haven't
left anything out)--
- Decide its time to load new set of PTFs
- Apply all existing PTFs *PERM - most likely setting them to apply
during the next unattended IPL (scheduled monthly)
- Download new Cume, Groups, and 'stray' PTFs we think we need
-- These will get loaded into one or more Image Catalogs
- IPL the system
- Load the new Cume, Groups, etc. and set to apply at the next IPL
- IPL the system (this will probably be 1 month after we apply the
prior PTFs *PERM - just because that's our IPL Schedule)
We make a SAVSYS backup (ie Option 22 - OS, IBM products) every month
after our IPL-- so we have several copies of the 'working' OS to pick
from if we have problems.
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
At 1:20 PM +1300 3/29/10, PaultinNZ wrote (in part):
I had decided to do the SAVE prior to permanently applying all V5R4 PTF's so
I could restore to a 'known' stable state in need.
Okay about to apply the 'not permanently applied' fixes, load the images
etc.
As an Amazon Associate we earn from qualifying purchases.