Re: PEER REVIEW please of V5R2 to V5R3 plan

["Roger Vicker, CCP" <rv-lists@xxxxxxxxxx>]

Pete,

I got in a hurry and copied the second PWRDWNSYS instead of a GO PTF 
before it.

I will have to check the CDs tomorrow. They were ordered around 
Christmas. I ran through everything in the hard copy that came with it 
but didn't see anything other than when they PTF'd the first ability to 
install from images. The V5R2 is latest on the CUME but do you have a 
link on the PTFs just to be safe.

Roger

On 1/19/2005 8:07 AM, Pete Massiello wrote:

> A couple of problems with this.
>
>    1) You don't do a PWRDWNSYS to apply PTFs.  You can use the image 
> catalogue when you do a GO PTF option 8 for the device if you wish. 
> Make sure you load the catalogue to the virtual optical device.
>
>    2)    You can now with V5R3, apply multiple "sets" of PTFs in one 
> iteration of loading your PTFs, which makes the initial load of the 
> PTFs quicker as you don't have to do 2 IPLs.
>
>    3)    If your CDs (look at I_BASE) has RSCD on it, which means its 
> the latest, you also need to have some PTFs on for using the Image 
> Catalogue.  Even the previous copies of V5R3 required some PTFs.
>
>    I would also do a SAVSYS at the end of the upgrade, so you now have 
> one for V5R3.
>
>    Pete Massiello
>
> Roger Vicker, CCP wrote:
>
> > Hello,
> >
> > I am getting ready to take a Model 800 from V5R2 to V5R3 using 
> > *IMGCLG as the source. I would appreciate a second (or more) set of 
> > eyes to review my plan.
> >
> > The standard weekly backup on the night before the upgrade is:
> >
> > SAVSECDTA
> > SAVLIB *ALLUSR
> > SAVDLO
> > End DHCP, Domino, HTTP, and WASe
> > SAV -- the Domino IFS files, HTTP config/logs, WASe config/logs, and 
> > the web pages using a SAVF
> > Start DHCP, Domino, HTTP, and WASe
> > SAVSAVFDTA
> > ENDTCPSVR *NETSVR
> > SAV /* -- Omit the Domino IFS files, HTTP config/logs, WASe 
> > config/logs, the web pages, /QSYS.LIB, /QDLS, /QNTC, /TMP and the 
> > *IMGCLG directory.
> > STRTCPSVR *NETSVR
> > SAVCFG
> > SAVLIB *IBM
> >
> > FYI. The first separate SAV to SAVF is to minimize the WEB downtime 
> > to less then 10 minutes. The second SAV takes 2 hours itself and the 
> > SAVCFG & SAVLIB *IBM take only 40 minutes. Everything before the 
> > second SAV only takes an hour.
> >
> > Will another copy of it and a couple of SAVSYS before the upgrade 
> > serve the place of GO SAVE 21? If so my weekend can be:
> >
> > ENDSBS *ALL
> > SAVSYS (twice)
> > PWRDWNSYS RESTART(*YES) IPLSRC(*IMGCLG) IMGCLG(V5R3)
> > Go home for 8 hours according to the install manual
> > Come back
> > ENDSBS *ALL
> > PWRDWNSYS RESTART(*YES) IPLSRC(*IMGCLG) IMGCLG(V5R3CUME)
> > PWRDWNSYS RESTART(*YES) IPLSRC(*IMGCLG) IMGCLG(V5R3GROUPS)
> >
> > If I perform a SAVE 21 it will take another 4 hours as well as two 
> > tapes each. The above weekly just fits on one tape now but if it 
> > includes the *IMGCLG directory (which a SAVE 21 would) it will span 2 
> > tapes.
> >
> > Not sure yet if I can schedule for this weekend or the next.
> >
> > Thanks for the "PEER REVIEW."
> >
> > Roger Vicker, CCP

--
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com 
***
With people, reach should exceed grasp. Try for heaven.