Jousma, David wrote:
You are correct about HFS/ZFS, I mentioned that. Those do get cataloged
with the maintenance SYSRES as the second qualifier in the live
Mastercat. We have no SMS managed datasets provided by Serverpac(other
than HFS/ZFS). CPAC provided datasets get cataloged in the live
catalogs with a version/release qualifer. My SMPE targets eventually
become the same name as the live datasets, after they get loaded. Hence
my comments about removing the requirement for these datasets to be
cataloged at all.
I'm not there any more, but I really doubt ServerPac Development
would seriously entertain removing the requirement to catalog the
data sets during installation. It solves more problems than it
causes, and it's easy to discard the catalog later if you don't
want it.
This is the process:
1) configure serverpac for end state(including end-state dataset names)
2) modify and run ALLOCDS changing all created datasets to add unique
HLQ(want to stop doing this if the requirement to catalog them went
away)
This is *exactly* what SSAs are!
3) modify and run RESTORE making the same jobs as above (also stop doing
this if the job had VOL=SER references to the datasets created above).
4) rename all above datasets removing unique qualifier
This is exactly what the DELSSA job does...
I realize I could use the SSA to do this, I'm just not a fan of them,
and if the vol=ser references were put into the job, there would be no
need for the SSA either. Just a few less jobs to run, and stuff to mess
with.
I think it would be faster and considerably less error-prone if
you instead used the software upgrade installation path, which is
intended to get the end result you're after.
Optionally, you could use a ServerPac catalog through (at least)
the DELSSA job, ALTER its entries to use system symbols and
DEVT(0000), run a REPRO MERGECAT using it and your existing
catalog, and then delete the ServerPac catalog once the
installation process was complete. This would eliminate the
massive editing for ALLOCDS and RESTORE while getting the new
catalog entries into your existing catalog.
Note that both of these suggestions absolutely rely on the target
data sets that you use retaining their positions on the same
relative volumes in your set of target volumes. (For example, if
it was on the &SYSR1 on the old system, it has to also be on
&SYSR1 on the new system.)
I use a cloning procedure that copies the maintenance sysres to one of
several "Live" SYSRES volumes that we alternate through. The live
dataset are all cataloged indirectly with &SYSR1.
<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
