|
You bring up a good point. Many times when I've opened up a pmr IBM has responded put on group ptf such-and-such. However they could never tell me which particular ptf fixed the issue. Sometimes I swear it's just a convenient way to get me to reboot my iSeries and see if the problem goes away. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Mark Phippard" <MarkP@softlanding.com> Sent by: midrange-l-bounces@midrange.com 01/29/2003 08:35 PM Please respond to Midrange Systems Technical Discussion To: Midrange Systems Technical Discussion <midrange-l@midrange.com> cc: Fax to: Subject: RE: Joe's V5R1 upgrade Joe, You raise a valid point in favor of IBM in that they do offer quality support and as long as you contact them soon enough the general architecture of the hardware and software allow most any problem to be resolved. That being said, IMHO, the whole PTF process has become a nightmare on the iSeries. Does anyone understand it anymore? Do apply Group PTF's before or after CUME's? Do the CUME's include fixes for things like Java and WebSphere? The larger problem is the downtime. Too many fixes require IPL's. Look at WebSphere. To get its PTF's applied, you also have to apply all of the PTF's for the database, Java and HTTP server. Somewhere in there will always be at least one fix that requires an IPL. However, how many of those fixes did WebSphere actually need? Was an IPL absolutely necessary? This does not even get into the fact that often times these fixes inevitably break something else. As Walden and others have pointed out, with a cluster of Linux or Windows systems you can take a system out of the cluster to apply fixes without bringing down the cluster and your application. I think the iSeries really needs to improve in this area. As it stands, I would have a real hard time recommending the iSeries for someone with high availability needs in a "connected world". The iSeries rocks when it comes to unscheduled downtime, but it is not so great in the area of planned downtime. Mark _______________________________________________ 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/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.