Re: Rebuilding PTF indexes (was RE: V3R2 LIC)

[rob@xxxxxxxxx]

Dan,

This is not meant as a slam.  But, with all of these old releases of OS/400
your company doesn't really sound 'bleeding edge' to me.  I am only
mentioning this because certain versions of 'beta' OS/400 have been known
to put marker ptf's similar to this.  Might you have beta'ed V4R3?

Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    "Bale, Dan"
                    <D.Bale@handleman.c       To:     <midrange-l@midrange.com>
                    om>                       cc:     <neilp@dpslink.com>
                    Sent by:                  Subject:     Rebuilding PTF 
indexes (was RE: V3R2 LIC)
                    midrange-l-admin@mi
                    drange.com


                    08/14/2001 01:04 PM
                    Please respond to
                    midrange-l






Neil, where is this documented?  What releases is this available for?  I've
got a similar situation with a V4R3 box whose DSPPTF 5769999 screen starts
out with the following column of PTF IDs:


RE98316
RE98273
RE98144
RE98143
RE98142
QLL2924
MF20589
MF20583
MF20515


Nobody's ever been able to tell me what the RE entries are, but there are
no TL entries and I find it hard to believe that we've been running this
thing in production since who knows when without any cumes installed.
FWIW, everything is either permanently installed or superseded.


Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)


-------------------------- Original Message --------------------------


     -----Original Message-----
     From:   neilp@dpslink.com [SMTP:neilp@dpslink.com]
     Sent:   Tuesday, August 14, 2001 11:41 AM
     To:     midrange-l@midrange.com
     Subject:        Re: V3R2 LIC


     More likely the PTF index has somehow been destroyed.
     Try this (in a restricted state):
      DLTF       FILE(QUSRSYS/QAPZPTF4)
      DLTF       FILE(QUSRSYS/QAPZPTF3)
      DLTF       FILE(QUSRSYS/QAPZPTF2)
      DLTF       FILE(QUSRSYS/QAPZPTF)
      CALL       PGM(QPZSYNC) PARM(C)


     ...Neil








     Douglas Handy <dhandy1@bellsouth.net>
     Sent by: midrange-l-admin@midrange.com
     2001/08/14 11:09
     Please respond to midrange-l



             To:     midrange-l@midrange.com
             cc:
             Subject:        Re: V3R2 LIC





     Pete,


     >when I did a  DSPPTF 5763999, it came up with no PTFs


     I just checked a 200-2031 machine at V3R2, and 5763-999 definately
     showed
     a long
     list of PTF's.  The highest numbers on that particular box were
     TL98139
     and
     MF18809.  I don't know if MF18809 was part of the CUME or not.


     The highest number for 5763-SS1 was TC98139.  All of these were
     permanently
     applied.  There were numerous superceded TL's and TC's before them.


     I believe 98139 was the last CUME issued for V3R2.


     Did the account never load a CUME?  That's scary.  At least they
     aren't on
     V3R1
     without a CUME...


     Doug







     _______________________________________________
     This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
     list
     To post a message email: MIDRANGE-L@midrange.com
     To subscribe, unsubscribe, or change list options,
     visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
     or email: MIDRANGE-L-request@midrange.com