|
http://www-912.ibm.com/a_dir/as4ptf.nsf/PTFBYNUMORDER2/SF99510?OpenDocum ent&ptfnumber=SF99510 3147 has been superceded by 3175. That's less than a month apart. Anyone know why the CUM was updated so quickly? I haven't heard of any problems with 3147. BTW, the next V5R1 CUM is still slated for 12/29/2003. - John -----Original Message----- From: Jeffry Kennedy [mailto:jkennedy@xxxxxxxxxxxxx] Sent: Tuesday, June 24, 2003 1:05 PM To: Midrange Systems Technical Discussion Subject: Re: V5R1 CUM3147 .. Anyone applied this yet? I just finished it on my test LPAR yesterday. I also did the Hiper, DB, WEbSp, BRMS, JAVA and performance tools. I did SI03120 & SI03125 for the Image Catalog for installing V5R2. It took about 90 minutes to IPL and 60 minutes to apply the PTF's (LPAR has 10% of 820) I haven't had any problem with the fixes. "Jones, John (US)" wrote: > I normally defer updates for a few months but I've got to install > DB2/SMP on one of our systems, which means reapplying 3007/db/HIPER to > make sure SMP matches the rest of the system. Since I've got to load > those CDs anyway, I may as well get current so I'm considering > applying 3147 (along with the current db & HIPER groups). Has anyone > already applied the update and if so, would you mind sharing your > experience? Any 'gotchas'? When I loaded 3007/db/HIPER, I loaded the > CUM, db, HIPER and did a single IPL; any problems keeping it simple > like that? > > Main OS components we use include HTTP server, Net.Data, Developer > Toolset (RPG, C, C++), Netserver, Java, Performance Tools, Query > Manager, Client Access Express, Windows Integration (IPCS). We also > just switched to Ops Console. > > I do have a current SAVSYS. > > Thanks, > > John A. Jones > Americas Security Administrator > Jones Lang LaSalle, Inc. This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.
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.