Dazzo, Matt wrote:
Software upgrade, the previous install was not used as a model.
Software Upgrade is really intended to be used only when you will keep
things on the same relative target volumes. That is, the same data sets
that are on the first volume on your existing system will still be on
the first volume built by ServerPac, and the same is true for subsequent
volumes in the target volume set. It is also mostly intended for use
with indirect cataloging, though I will admit the documentation could be
clearer about that.
As it says on the panel where you select SU vs. FSR:
"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."
SU will generate a job to update your existing master catalog to reflect
the placement of the data sets in your order. If they are not in the
same relative places as the ones you are IPLed from, havoc might (well,
probably will) ensue either quickly or at the next (attempted) IPL. The
chances of them winding up on the same relative volumes are a lot less
than 100% unless both the old and new volumes are so large that all the
data sets for each order fit on one volume.
As you did not model after the prior installation, where things will
wind up depends on order content, volume size, and any changes to data
set size in the new order vs. the old one.
If you still have the old ServerPac order's data sets around, you can
probably go into the dialog and save the configuration for that older
order. Then, select it for merge when you create the work configuration
for the new order. That will carry forward all the stuff you did the
last time for anything that existed in the old order, which is generally
less work overall. If everything fits on the "same" volumes, the SU
path will create a job that basically only adds new entries to your
master catalog, which ought to be harmless.
You can also fool Mother Nature by creating a temporary catalog, but
that will still leave you the task of reconciling catalog entries with
actual data set placement later.
HTH...
--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
