|
> >I see a couple of problems with your formula: >TimeForEachPtfOnCpw1Sys - PTF sizes are so different that PTF application >time is wildly different. Did you mean average time across all known PTFs ? cpw1 time used to apply the avg ptf on the cume. >Besides you make an assumption that PTF load/temp apply time and PTF perm >apply/supercede time are the same. Actually it's much faster to perm >apply/supercede PTF already on system than to load and temp apply a new >one. This is why the more PTFs already on system, the faster cume apply. did not know that. so formula would have include an avg cpw1 time to load the avg size ptf and a 2nd cpw1 time to perm apply/supercede the avg ptf. alexie, are you saying that a cume may contain ptf's that are already on the system and the ptf load will effectively skip those already present ptf's? if so, the formula would need to account for ptf on the cume that already exist on the system, which might be difficult to est ahead of time. also, is a ptf a new, corrected copy of a pgm? or is it a patch to a pgm? thanks, Steve Richter +--- | 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 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.