And, if that isn't SAD enough, at 16:58 today, the AIX tar file for 4.2.2.5 got updated! (Who knows what they just changed, if anything!?!)
-----Original Message----- From: Don France [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:53 PM To: 'ADSM: Dist Stor Manager' Cc: '[EMAIL PROTECTED]' Subject: RE: NSM Upgrade Experience Ooops... we just advised a customer to install 4.2.2.5 --- for SumTab fix, didn't know there is a (yet) new bug for expiration (introduced by 4.2.2.4???) Are you sure that 4.2.2.6 is needed for EXPIRE INVENTORY to work, again ?!? (There is nothing about expiration in the .4 or .5 APAR abstracts... Were you/they referring to the "conflict lock" issue? Geesh, .5 just came out...sigh:() Don France Technical Architect -- Tivoli Certified Consultant San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jolliff, Dale Sent: Thursday, June 20, 2002 2:57 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience I got my 5100-02 patch when someone at 800-IBM-SERV was playing phone tag between myself and the CE when he was out investigating our PMH on duplicate IP addresses. I was told by level 2 this afternoon to avoid expiration on 4.2.2.4 until 4.2.2.6 is available Real Soon Now. -----Original Message----- From: Talafous, John G. [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 2:25 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience As I understand, support for TSM 4.1 expires June 30, 2002. So if you want to be supported, you have no choice but to upgrade to TSM 4.2. We too have been trying to implement EC017 on our NSM, and have had two failed attempts at the upgrade. The upgrade to AIX 5 and TSM 4.2.1.9 requires an AIX load from 4mm tape. We got a bad 4mm tape. You know, WORN technology (Write Once, Read Never). About 10% of the way into the upgrade to AIX 5 we couldn't read the tape. Tried and tried and tried. But it was bad. We had to recover from the MKSYSB we did that morning. That's why we take MKSYSB's. The second time we tried the EC script failed because \dbaa1dk31\db has on HDISK2. Huh? How did that happen. It turned out that when the recover was done from the MKSYSB all the HDISKS were renumbered by AIX. It took us a couple days with Level II support to get that straightened around. Took Level II about 4 hours dialed in running AIX commands to re-do things and put \dbaa1dk31\db back on HDISK31. We have scheduled our third attempt at EC017 for Sunday, June 30. I've also been told by Level II that anyone preparing to install EC017 should open a PMR prior to the upgrade so support can track the activity. I was also told that not very many NSM sites have done this upgrade, so many will be out of support. And what's this about OS patch 5100-02. Where do I get it and where do I find these kinds of patches? Is there some piece of documentation I've missed or did I just not catch something? Good luck to all!!! John G. Talafous Information Systems Technical Principal Global Software Support - Data Management telephone: (330)-471-3390 e-mail: [EMAIL PROTECTED] http://www.ctnvm.inside.tkr/~talafous/ http://www.cis.corp.inside.tkr/networkstorage/
