Re: PTFs, again

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

Thank you for your insight, Rob.

Earlier this morning, I did a DSPPTF to an outfile.  A query on that file
shows:

Cover letter only                 1
On order only                     2
Permanently applied     3,760
Save file only                      1
Superseded                 5,043

Value of QABNORMSW  = 0
hows
A DSPPTF with no parameters shows Server IPL required.  Pressing help shows
CPD35F8.  Causw states reason code 1, Program temporary fixes have been
applied for the server firmware portion of the Licensed Internal Code.


DSPPTF LICPGM(5722999) SELECT(*ACTRQD) shows eight PTFs.  And, I remember
some of these.  All state Permanently applied - IPL.  They are all MH
PTFs.  And they are 1076, 1073, 1070, 1053, 1007, 1004, 1001, 997

Maybe just another IPL with restart type *FULL clears this all up?  But, I
don't recognize any CHGIPLA attributes that might need to be changed, other
than retsart type.

Vast majority of the save files are for v5r4m0.  I found some ancient
v1r2m0 save files with ANZOBJCNV.  Wanted to let PTF process delete the
v5r4m0 save files so I would not accidentally confuse things by deleting
wrong save file manually.

Maybe I can find out when PTFs were perm applied.

John McKee


On Mon, Dec 2, 2013 at 3:09 PM, <rob@xxxxxxxxx> wrote:

> Where, exactly, are you seeing "server IPL required"?
> On an individual PTF when looking at 1. General information?
> On the list of ptf's when looking at the column "IPL Action"?
>
> Try this:
> DSPPTF OUTPUT(*OUTFILE) OUTFILE(QTEMP/DSPPTF)
> sql that and delete the ones which are permanently applied.  Then start
> your analysis from there.
>
>
> Other things which will affect PTF application include if your IPL was
> 'abnormal'.  WRKSYSVAL QABNORMSW.
> Sometimes you may have PTF's that are missing coreqs or prereqs.  See GO
> LICPGM, 50. Display log for messages.  You may have to delve into the
> joblogs for SCPF, active and past.  If it's been too long since your last
> IPL you may be missing this history.  GO CLEANUP will clear it out after
> the number of days you tell it to.
>
> Also, look closely at those PTF save files.  Are some PRIOR to V5R4?  If
> so, and you failed to apply them permanently before upgrading to V5R4 they
> will remain there for all eternity.  Years ago I started applying all PTFs
> permanently (along with an extra IPL or two) before upgrading my OS.  This
> helped prevent new ones from being left over.  The older ones I had to
> manually delete.  I think I even discovered some V2 PTFs.
>
> Oops look at the time.  This may be chopped - gotta go.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   John McKee <jmmckee@xxxxxxxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:   12/02/2013 03:52 PM
> Subject:        PTFs, again
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> I know I asked this before.  Just tried to search, but didn't find it.
> Maybe wrong terms.  What I used, with Google, was:
>
> perm applied ptfs savf file remains
>
>
> I know there were a large number of temporary applied PTFs.  Just looked,
> and they are all permanent applied now.
>
> DSPPTF still shows "Server IPL required".  IPL source is ##MACH#B ##SERV#P
>
> And, all the PTF save files are still in QGPL.
>
> I don't know when PTFs were permanently applied.  I thought I read that
> the
> save files were removed when PTFs were permanently applied.
>
> I do remember changing the IPL attribute for restart type.  It is
> currently
> set to *SYS, and I know I changed it per the suggestion of another user.
> Been a while, but I am wondering if the SERV value stated T at the time.
>
> This is v5r4m0
>
> I am confused, and it is getting more routine.
>
> John McKee
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.