|
Nah... just a question of logistics - thank goodness that we're outside of SOX concerns (although auditors seem to treating everyone worse because of SOX, anyway...) The 800 is our production WAS/Domino box and to get it to V5R4 would (normally) require doing the backup WAS/Domino 520 box first, and that box is also the Mimix'ed backup to our 520 production DB2 apps, so it would trigger that upgrade to V5R4 also. It just depends how big of a snowball we want to start pushing on... The few months timeframe has to do with when the 800's lease is up. We may have a good need for the V5R4 virtual tape features, but that's the only real interest in V5R4 at this point. The impact of the 2 additional upgrades and program testing and such won't be a good fit along with some other projects that are ratcheting up in the near future. We'll be upgrading/replacing the current 520s mentioned above the following year, so V5R4 will probably fit better then. I've always been able to avoid a manual install, so i'll have to get familiar with it again if we think we're going to do the V5R3M5 install on the new box. We're very early in the planning stages... rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 02/28/2006 02:20 cc PM Subject RE: 'On order only' PTFs Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> The newer 520's require 535 or 540. The older 520's will work on 530 and above. Basically you go through the same steps to go to 535 that you go to 540 - IPL either from CD or image catalog to replace your lic. But you'd probably use "Manual" installation instead of "Automatic" installation. That way you stop after the LIC. There is no 535 for SS1, etc. Then you apply the latest cume, group's, etc just like you'd do with 540. You said "in a few months...". So assuming that's enough time to shake out a few more bugs from 540, (if that's your big concern), why wouldn't you go to 540? Is there some weird SOX thing that says you have to have the Pope bless a new version of OS prior to using it (but lic doesn't count)? Is there something in the "Memo to Users" or at the planning site at http://www-03.ibm.com/servers/eserver/support/iseries/planning/upgrade/index.html that has you concerned about 540? I'm still turning in service requests on 530 and I'd bet that if I still had a machine running 520 I'd be turning service requests on that also, so it's not like waiting 2 years makes those infallible. And, here's the part most germane to this thread: More times than not, any new service request was fixed by downloading a ptf that was already created for someone else. Very, very few of any service requests I've submitted have had to do because of a bad ptf. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com ChadB@xxxxxxxxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 02/28/2006 01:47 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: 'On order only' PTFs Best practices are a wonderful thing from a tech perspective, but from a management perspective instead it might look like: So what problem were we fixing by adding these? None? But they caused us a problem? I don't understand... ;) Luckily, I probably wouldn't hear that at this job. I'm still not sure sometimes which path is better. One part of the problem is that at times there are too many other irons in the fire (i.e. Windows, Network, etc.) to be more proactive and responsive to loading recent PTFs. By the time the project load clears up 3-6 months later and everything is still running A-OK on the iSeries side, it's somewhat hard to justify knocking a piece of the puzzle out of place while trying to stay completely current with PTFs. With that being said, what i'm working on right now is doing just that... trying to get our 3 boxes more current and matched up PTF-wise... we're looking at moving our 800 to a 520 in a few months. I'm not sure yet if we'll stick with V5R3 on the new box or look at V5R4. If we stay at V5R3 on the new 520+, is it necessary to go to V5R3M5? If so, what's involved with doing so? rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 02/28/2006 01:14 cc PM Subject RE: 'On order only' PTFs Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> I tend to agree with you Scott. Their counter argument is "if they can run for a month or so without any problems, why couldn't they run for all perpetuity without any problems. Wouldn't the ptf's then potentially introduce new problems?" Granted, a new MCH#### error after a ptf install is not a happy day. But there is the potential that you are experiencing problems, and may not be aware of it. Like some of the "Integrity Problem" ptf's. Or, let's say a ptf that will help you actually recover if you have a disk failure, but failure to have this ptf, prior to the recovery, may be catastrophic. Or the ptf's that will better handle temporary space. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 02/28/2006 12:33 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: 'On order only' PTFs Why wouldn't you just apply these PTFs for your installed products? I understand that out of the 1000's of PTFs released in the last 10 years or so there have been at least two that have had undesirable effects, but do you really want to wait until a problem occurs and then spend valuable time trying to determine what the problem actually is before installing PTFs or would you rather be ahead of the game and solve these problems proactively? In my mind there is nothing worse than having to do two IPLs to get up to snuff on PTFs before support will even help diagnose a problem. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Tue, 28 Feb 2006 10:38:15 -0500 from: ChadB@xxxxxxxxxxxxxxxxxxxx subject: 'On order only' PTFs I've got a number of PTFs in 'On order only' status for various LICPGMs on my systems. For the most part, these came from Service Director automatic PTF orders that resulted in shipments on CD media and I have no intention of loading these unless a specific need comes up. I periodically review and load the PTFs that Service Director pulls down automatically in electronic format, but these CDs are packed with them and I have no desire to review/load them unless a specific need arises. The volume is just too great... Are there any benefits/drawbacks to leaving them in that state or cleaning them up? I'd like to clean them up (with DLTPTF i'm guessing, haven't tried yet), but i'm wondering if there's a good reason to keep them in that state? DISCLAIMER: This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. ?? 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ForwardSourceID:NT0003D966 _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ForwardSourceID:NT0003D9AE _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.