Mike Wojtukiewicz wrote:
This post is most likely directed towards John Eells as he's the master of
the ServerPac domain, but ANYONE with prior experience would be appreciated.
I'm no longer in ServerPac design, but I might be able to
remember bits here and there (smile).
I am looking into doing a software upgrade using ServerPac. I've been doing
SPs since they started coming out and I've never used it nor have I come
across anyone who's done it, yet I'm told it's pretty popular. My question
specifically is.
How does it restore the target and distlibs? Does it OVERLAY the current
libraries, which means the target system in question is not running or does
it use new DASD and load the datasets down. That being said must the
datasets be indirectly catalogued or not. If not then how does it know what
the "true" running datasets are. If it is required then I can fully
understand how it works and it can be done on the target system while it's
running.
Don't feel alone. Though clear to us, the wording of these
options has historically created an enormous amount of confusion.
If I could go back in time and rename these options from
"Software Upgrade" and "Full-System Replacement" to something
like "load new software into new data sets" and "load new
software into new data sets and create operational data sets,"
you can be sure I would!
Anyway, the target and distribution libraries are loaded exactly
the same way in SU as they are in FSR. That is, new data sets
are allocated and loaded with IEBCOPY/IDCAMS/IEBGENER, etc.
Read and _understand_ the section in Installing Your Order about
how the SU catalog update jobs work before using them. Once you
understand them, you might also find them useful as you migrate
to production systems (or not).
Indirect cataloging is supported, but the generated jobs will
update your existing catalogs, so do this with your eyes open.
The jobs are designed to work with existing indirect catalog
configurations when *no* data sets that matter to *you* are moved
between target volumes. (In other words, if SYS1.ABC was on
target volume two on the old system and you need it to IPL, it
had better be on target volume two on the new system. On the
other hand, if you don't use data set SYS1.XYZ at all, then it
doesn't really matter whether the catalog entry winds up pointing
to the wrong place when the old system is in use.)
If you're ever in doubt, you can *always*:
(0. Tailor the work configuration the way you want it.)
1. Save the configuration. (You do this anyway, right? If not,
you should!)
2. Generate the jobs to see what they would do if they were run.
3. Change your mind after (2).
4. Re-create the work configuration by selecting the one you
saved in (1).
This is easy and fast, preserves your work, and can remove all
doubts created by those "what if I were to...?" kinds of
questions. 15-20 minutes spent this way can sometimes save you
hours (even days) later.
The net is that if you (a) use indirect cataloging and (b) do not
move data sets you use on your system between volumes from one
release to the next, then SU can save you some work and will
require less DASD than FSR. (b) is most easily achieved when you
saved your configuration after installing every order so that it
can be used to model the new one when the new work configuration
is created. (Don't panic if you forgot. Just select the order
and save it when you get the new one.)
I have to say the online help and the printed documentation is poor, to be
kind, on this topic and poking around the CPPC screens doesn't give me any
inkling how it would works. Thanx all
I'm not sure what you find unclear about:
"F - Full System Replacement installs a complete new IPL-able
standalone system including all
SMP/E-maintained libraries, SMP/E environment,
operational data sets, and CustomPac sample data sets. The
supplied operational data sets must be merged with or replaced by
production operational data sets before the new system is used in
production.
"S - Software Upgrade installs only the SMP/E-maintained
libraries, SMP/E zones, and CustomPac sample data sets.
Operational data sets, including system control files (like
LOGREC and VTAMLST), a security system database, and a master
catalog must already exist. These existing operational data sets
must be updated as required for new products and product changes
before the first IPL."
...on panel CPPP6015, or its documentation in ServerPac: Using
the Installation Dialog at:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CPP2UD80/5.1?SHELF=EZ2ZO10H&DT=20060710040225
But if you would take a few minutes to send a note to
[EMAIL PROTECTED], perhaps we can improve on them both.
<snip>
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
[EMAIL PROTECTED]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
