× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: why cum ptf apply faster than predicted?
  • From: bvining@xxxxxxxxxxxx
  • Date: Wed, 16 May 01 09:38:12 CDT

The estimate is simply that, an estimate.  Factors that can influence
your time spent on the cum are the size/capacity of your system, how
many LPs you have installed, how many PTFs/Cums you may have previously
installed, etc.

The 4 to 8 hour estimate you saw was derived from testing in the lab
(using a very old and small system that actually took 9 hours to run
and was reduced to 4 to 8 to reflect what most users would likely see)
on a system that had every LP you can think of installed.  The letter
hopefully also indicated a 2 to 4 hour estimate if previous cums had
already been applied.

The 4 to 8 is hopefully a meaningful compromise to lead most users to
some appropriate estimate of their downtime.  To estimate from 1/2 hour
to 10 hours (or longer?) would most likely be such a wide range that
it would be worthless for most planning purposes (though you may feel
that the current estimate is about as worthy).

As others have mentioned, I would favor the over estimating rather than
under estimating of required time in this area.

Bruce

>
>Did a cummulative ptf load after a v4r4 install.
>
>The cummulative ptf's were on 3 cd's. The system is a very fast, non geared
>down 720.
>
>The cover letter said the ptf process would take from 4 to 8 hours.
>
>But it actually took 1 hour to load, apply and complete the auto ipl.  (
>17:57:31 to 18:47:50 )
>
>The history log msgs ( listed below ) show no indication of error.
>
>What does ibm base its time estimates on?
>
>This is not a trivial question.  Misstating the estimate results in much
>wasted time double and triple checking to make sure that nothing was missed,
>that the system is running ok.
>


+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.