RE: A worried New comer with a CUM install.

USUALLY (there are always exceptions) a PTF cum package, after following
all the instructions, basically comes down to GO PTF, run #8.
The exceptions are when there are some pre-requisite PTF's that must be
installed separately before you apply the rest of the package, or if
there are PTF's that affect the PTF process itself.  Usually, once
you've installed a new release and applied the first cum package - which
may include a few special steps - subsequent packages are usually just
GO PTF, #8.

Now, with that said, I am NOT suggesting you just do GO PTF, #8 - just
saying that all the other steps in the instructions may basically boil
down to just that.
The instructions may appear long, but keep in mind they are covering
every possible situation (ie. any previous cum package level applied to
the system), plus there are instructions at the end for SSP PTF's (if
you are running an Advanced/36, or a S/36 Virtual SSP Machine under
OS/400, that most people never need to read.

Also, there will be a decision to be made about how to apply the PTF's.
When you hit the step where you do GO PTF, #8 there will be a decision.
Do you want to IPL the machine immediately after the PTF's are loaded,
or do you want to wait until you manually issue a
PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(B)
command for the PTF's to be applied ?
If you're going to start the application in the evening, when there are
no other runs needed on the system afterward, you may want to take the
option to automatically IPL.  You can then usually go home as soon as
the PTF's start loading.
If you create a line description for a standard SDLC line for your ECS
modem - with ONLINE(*YES) specified, and make sure it is varied off
before you start the PTF install, you can always disl the modem from
home several hours later and if the modem answers and screams in your
ear you know the system is back up.  Of course if you have remote access
capability you can use that instead to see if the system is back up, but
the first method lets you check from your cell phone while driving off
to the cottage for the weekend !   :-)
Note that when you select to automatically IPL after the PTF's are
installed, if you don't first do an ENDSYS *IMMED the system will do
that automatically when it's ready to IPL.  I would suggest you do an
ENDSYS *IMMED before the 
GO PTF, #8 step so no one starts any other jobs up while you're loading
the PTF's.

NOW, the other option is to NOT automatically IPL.  I use this option
when I'm at a customer site and want to get the PTF's loaded and take my
tape/CD home with me.  You may want to do it to make sure the PTF load
process completes normally, and you can then schedule an IPL later at
night to apply the PTF's.  Note that if you do this I would suggest you
do a CHGJOB RUNPTY(35)   -  well, any number higher than 20 - so the
LODPTF process doesn't impact other interactive users too heavily.  If
you don't want to impact batch jobs too much during PTF load you may
want to change the run priority of the screen you're loading PTF's at to
55 or higher.

Whenever the system comes back up, you can use GO LICPGM, #50 to check
for messages to make sure the apply was successful, and/or use DSPPTF to
make sure all PTF's are either Temporarily Applied, Permanently Applied,
or Superseded (and you may have some PSP - cover letter only PTF's that
show status of Cover Letter Only).
You can also do DSPLOG QHST and display from the time you start the IPL
to apply the PTF's.


Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: SROACH@MANUS.COM [SMTP:SROACH@MANUS.COM]
> Sent: Friday, May 22, 1998 1:46 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      A worried New comer with a CUM install.
> 
> Hello all:
> 
>     I am new to the list.  Our company uses a 53S model AS400 running
> V3R7M0.  I've been reviewing messages from the last couple of days and
> I am glad
> I joined.  There are a great many knowledgeable individuals here and I
> will be
> glad to contribute in any way I can.  However, I am fairly new at
> operating
> myself and my knowledge is limited.
>     My job description is really laser Setup for a Xerox Laser
> Printer, but
> my title is Software Specialist (sort of a joke).
> I have been handling CA/400, PAE and Group1 software upgrades for our
> AS400 for
> a while, but I still know very little about how much of the system
> works. Anyway, I have been given the task of installing the latest CUM
> upgrade and it
> is an unsettling prospect.  I have heard horror stories of installs
> that went
> wrong and I was wondering if anyone has any tips regarding this
> process.  I have
> read the install instructions a couple of times as well as the PSP
> info, but it
> is somewhat daunting, and I'm not sure I'm not missing something.
> 
> I know this is a newbie request and I do not wish to waste anyone's
> time, but If
> you have any pointers, I would really appreciate them.
> 
> Thanks for listening.
> 
> Steve Roach
> Manus Direct
> Seattle
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---