Thanks Tim. That was the answer I was hoping for. As for why we've always 
done FSR: until 2.1, we've been an 'MVS' ESP customer as long as ServerPac 
has existed. ESP customers have to hit the road several months before GA. 
In the beginning, ServerPac was not even available to ESP customers. Once 
it became available, FSR was the only path. So by the time SU became 
available for ESP customers, our procedures were pretty well entrenched.

We migrate a z/OS image from (non-IPLable) SMP/E environment to 7 running 
sysplexes. The release-level HLQ is a cornerstone of these processes. I 
will give SU a shot. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]



From:   Tim Deller <[email protected]>
To:     [email protected], 
Date:   05/28/2014 06:18 AM
Subject:        Re: ServerPac: Upgrade or Full Replace?
Sent by:        IBM Mainframe Discussion List <[email protected]>



Service upgrade does create a catalog specifically for the install and 
ongoing maintenance of the zOS release.
I think of it as one of the SMP datasets because that is the only thing 
that needs it.
It has an alias for the SMP support datasets (ex. SMP21) and an alias for 
the target and dlib datasets (ex. ZOS21). 
DDDEFs point to alias names such as ZOS21.SYS1.LINKLIB 
ZOS21 is an alias in the driving master cat pointing to the release 
specific catalog on the SMP volume.
The ZOS21.SYS1.LINKLIB dataset alias points to SYS1.LINKLIB on volser 
Z21RES 
I used full replace a couple of times in the beginning but found that I 
didn't need the support datasets.
I use Mark Zeldan's one pack JCL to build on a borrowed volume for the IVP 
IPL. (xcflocal)
Then apply usermods and clone a normal RES volume (we rotate 3) and IPL it 
in the TECH lpar. (multisystem)
That way; the serverpack datasets never get IPL'd; we only run from 
copies.
Thanks,
Tim Deller


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to