Re: Os/400 System Reload - PTF Problems.

Nick,

 SHould the thing go completely south I would recommend to re-load SLIC from the
CD.  (Boot up with Option D M on the panel and the CD Loaded), when the menu
show up take the option to ReLoad the SLIC and wipe out the config entirely. DO
NOT take the option to recover the disk configuration. Even though this will
cost some time, the machine will have a completely clean OS load.

 Of course you should avoid this option if you are not comfortable rebuilding
your disk configuration including RAID and MIRROR setup.

 - Larry


Nick Arnold wrote:
> 
> Thanks Larry,
> 
> basically, I have this machine with 4.2 loaded, but, I have to reload with
> an earlier version of 4.2 and earlier Cum PTF Pack this is for millennium
> purposes !.
> 
> Both the data and Licpgms remain untouched, the idea is to just reload the
> OS and slic, this has worked on previous machines.
> 
> I agree that the PTF index table must be corrupt (apparently this machine
> has a rough history when it comes to upgrades!), it looks as if the slic is
> not clearing down all of the previously installed PTF's.
> 
> I have been in contact with the support guys, but he has no real idea on
> this, I am planning to push forward, omitting the PTF's that are giving me
> the problems, I had exactly the same problem on this box last November when
> going from 3.7 to 4.2, IBM thought it was due to an old PTF Cum against new
> OS software !!!.
> 
> thanks for your help, nice to know that I am not on my own !.
> 
> Thanks
> Nick
> -----Original Message-----
> From: Larry Bolhuis <lbolhui@ibm.net>
> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
> Date: 03 April 1999 22:36
> Subject: Re: Os/400 System Reload - PTF Problems.
> 
> >Nick,
> >  Are you doing a complete scratch reload of the system or an upgrade from
> a
> >previous OS verision?  If you reloaded microcode (SLIC) and had to add all
> disks
> >in that process then there is NO prior version of OS/400 or it's PTFs to
> worry
> >about.  If you are doing an upgrade then the pre-existing PTFs are removed
> as
> >the programs are replaced with newer versions.  If you are just re-loading
> >OS/400 and your programs and data (with SLIC still in place) then the MF
> ptfs
> >from before should all still be there.
> >
> >  What this sounds like is a corrupted table of some sort as to what PTFs
> exist
> >and what status they are in.  If you haven't already taken this rash step I
> >would call supportline on this one.
> >
> > - Larry
> >
> >Nick Arnold wrote:
> >>
> >> Hi All,
> >>
> >> I am in the middle of a V4.2 system reload.
> >>
> >> I have hit a really strange problem when trying to load my Cum PTF
> Package,
> >> I have a question that I hope you could answer for me.
> >>
> >>         ==>    When you load the SLIC & OS does it effectively remove the
> >> existing OS ?, i.e. all PTF's that may be loaded are removed.
> >>
> >> My problem is, I have loaded the Slic & OS, but when I attempt to load my
> >> Cum PTF package I get the following message.
> >>
> >> MESSAGE:        PTF 5769SS1-SF47572 V4R2M0 not applied.
> >>
> >> CAUSE:               Licensed internal code fix 5769999-MF19309 V4R2M0 is
> >>                                 required for PGM Temporary fix (PTF)
> >> 5769SS1-SF47572 V4R2Mo and must be permanently applied.
> >>
> >> The recovery for this is to permanently applied the MF PTF, the problem
> is I
> >> have MF19309 Permanently applied already, I am getting this on 5/6 of
> this
> >> PTF's. The problem is if I try to omit the said PTF's  I then get a whole
> >> host of PTF's that are dependent on the one I already have.
> >>
> >> Does anybody have any ideas ???.
> >>
> >> Many Thanks in advance.
> >>
> >> Nick
> >>
> >> ==============================================
> >> Nick Arnold
> >> Production Services Manager,
> >> IBM Certified Specialist, Novell Certified Administrator,
> >> Channel Islands, & Gibraltar.
> >>
> >> Coutts NatWest Group IT Limited.
> >>
> >> +---
> >> | 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
> >> +---
> >
> >--
> >Larry Bolhuis         |
> >Arbor Solutions, Inc  | Two rules to success in life:
> >(616) 451-2500        | 1. Never tell people everything you know.
> >lbolhui@ibm.net       |
> >+---
> >| 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
> +---

-- 
Larry Bolhuis         |
Arbor Solutions, Inc  | Two rules to success in life:
(616) 451-2500        | 1. Never tell people everything you know.
lbolhui@ibm.net       |
+---
| 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
+---