RE: Joe's V5R1 upgrade -- MIDRANGE-L

Joe -

When we talked on the phone I gave you a bad parameter, to change the IPLAPY
setting on your PTF's you need to use the command APYPTF LICPGM(5722SS1)
DELAYED(*YES) IPLAPY(*NO).

That said your key issue is the link/loader error.  This implies that you
have one or more damaged PTF's that need to be reloaded and re-applied
before you can continue the PTF apply process.  The damaged PTF will show up
in the LIC Log in Service Tools as a 0C00 FFFF entry, it will probably be in
the top SCPF joblog in OUTQ status, or try DSPPTF LICPGM(5722999)
OUTPUT(*PRINT) and search for the word "Damaged".

The culprit is most likely an MF PTF that is a pre or co-req to the first
PTF that would not apply (in the SCPF joblog.)

You are right on in your understanding of the A and B sides, be sure to
verify that C2134510 is successfully applied to the O/S(5722SS1) as well as
the LIC.

Good Luck!

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
Date: Tue, 28 Jan 2003 11:43:52 -0600
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
Subject: RE: Joe's V5R1 upgrade

Wow.

This is getting to be quite the saga.

I can IPL to side A.  Side A says I'm up to C2134510, which is a pretty good
release.  But side B will not boot, I consistently get a SRCB6000910.  On
Al's advice, I've been trying to enter an incident, but we're having
problems there (I've been directed to use the Internet to purchase my
incident, but the IBM web catalog store is not working).

Basically, I just want to de-spin the B side.  Scott Ingvaldson says it can
be done by just going through and "unapplying" PTFs:

  APYPTF LICPGM(5722SS1) DELAYED(*NO) IPLAPY(*NO) APYREQ(*NO)

Doing that for every licensed program may force the B-side to relink
himself.  The problem is whether or not this will work when IPL'd to the A
side.  Foer a short period I was beginning to understand which parts of the
A side and B side were physical, and which were virtual, but now I'm not so
sure.

My current belief is that there is a copy of the SLIC on both sides.  It is
also my belief that PTFs for 5722999 apply to the SLIC.  It is further my
belief that the SLIC on the A side has only permanently applied PTFs and the
one on the B side includes also temporarily applied PTFs.

My other current belief is that temporary PTFs for the operating system and
licensed programs are "virtual", in that they or either enabled or not based
on which side you IPL from.  So, there aren't two physical copies of the
operating system; there is a base with permanent PTFs applied which is
loaded when you start the machine, and then the temporary PTFs are somehow
incorporated in at load time if you're running from the B side.

If that's the case, I may be able to remove the PTFs (using the APYPTF
command above) even though I'm on the A side, and then MAYBE that will force
the B side to attempt to rerun the link/loader.

Unfortunately, that's a WHOLE LOT of assumptions.  If the A side weren't
working, I might be tempted to try it, but since the A side is active, I am
very reluctant to run ANY command that has the word "PTF" in it.  Instead
I'm putting in a call to IBM.

Of course, that means buying an incident, and that's a whole DIFFERENT
story.  The web catalog store is broken right now (evidently all the virtual
employees are on virtual break) and so instead I have to go through the
manual procedure of receiving a contract, signing it, faxing it back, and
then finally hopefully getting to talk to a technical person.

I will say this; the IBM personnel are being very helpful.  I have found
over the last several weeks that (unlike certain times in IBM's past) it's
definitely not the personnel, it's the processes.  Any issues in service or
support are primarily due to management, not the folks in the trenches.

Joe