RE: Joe's V5R1 upgrade (was totally unrelated topic)

[neilp@xxxxxxxxxxx]

Joe,

Sorry I've been a little busy for the last week and just saw this, but for 
future reference an IPL isn't necessary.  Just go to restricted state and 
run:

DLTF       FILE(QUSRSYS/QAPZPTF4)
DLTF       FILE(QUSRSYS/QAPZPTF3)
DLTF       FILE(QUSRSYS/QAPZPTF2)
DLTF       FILE(QUSRSYS/QAPZPTF) 
CALL       PGM(QPZSYNC) PARM(C) 

...Neil





"Joe Pluta" <joepluta@PlutaBrothers.com>
Sent by: midrange-l-bounces@midrange.com
2003/01/25 23:06
Please respond to Midrange Systems Technical Discussion

 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@midrange.com>
        cc: 
        Subject:        RE: Joe's V5R1 upgrade (was totally unrelated topic)


> From: Joe Pluta
>
> The cume has a problem; MF27247 is superseded by MF28114, and so cannot
> load.  However, MF28114 is not on my machine, so I don't know
> what to do.  I just IPLed and left it at that for now.

This is indeed a problem, everyone.  I get:

CPD35D2
Message: Licensed Internal Code fix MF27247 is superseded.
Cause: Licensed Internal Code fix MF27247 could not be applied because
superseding Licensed Internal Code fix MF28144 is already installed.

When I try to display MF28144, I get:

CPF6602
PTF 5722999-MF28144 *ALL not found.

So, MF27427 thinks MF28144 is loaded even when it is not.  Any 
suggestions?

Joe

P.S. Rooting atround the bowels of the archives found an old note that 
Neil
Palmer had from back in the mid-90's about this whole PTF database thing.
It seems it (the database) can indeed get out of sync, and if a PTF gets
mistakenly flagged as superseded, there's no way to unflag it.  A 
suggestion
was to remove the PTF database (files QAPZPTF* in QUSRSYS) and re-IPL.  I 
am
giving that a shot as I type this.  The worse that could happen is I need 
to
do a scratch install, which is basically where I was this morning anyway
<smile>.