• Subject: RE: PTF question
  • From: "Allen, Stuart" <sallen@xxxxxxxxxxxx>
  • Date: Wed, 3 Nov 1999 06:34:30 -0600

I tend to put the cum on first, then the group ptf's, as the group ones are
usually more recent.  I stick them all on together *DELAYED, and then IPL at
the weekend as usual.  OS/400 sorts it all out!

As usual, it is prudent to read the PSP info first - just in case.

Stuart


> -----Original Message-----
> From: Matthias Oertli [SMTP:oertlim@s054.aone.net.au]
> Sent: Wednesday, November 03, 1999 10:24 AM
> To:   midrange-l@midrange.com
> Subject:      PTF question
> 
> I am looking at applying the latest CUM, database group and y2k group
> PTF's. Now I'm wondering if it would be a bad move to stick them on
> all at once via go PTF 8, apply all group CD's without IPL and the CUM
> last with IPL.
> Or would it be better to IPL after each group (3 IPL's)?
> How do you guys handle this?
> Regards,
> Matthias
> 
> ---------------------------------------------------------------------
> Matthias Oertli   <oertlim@s054.aone.net.au>
> +---
> | 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
+---

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].