Just for kicks, I did try Go ptf option 8 and then option 4 on a test box. It seems to work. Thanks for the PTF info! We don't plan on doing this on production systems, don't worry. Jeff Carey Technical Specialist "Ingvaldson, Scott" <SIngvaldson@guideon To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx> e.com> cc: Sent by: Subject: RE: Determining and refreshing build of LIC midrange-l-bounces@m idrange.com 03/30/2004 04:33 PM Please respond to "Midrange Systems Technical Discussion" I don't think that you should ever need to refresh the LIC unless you migrate to new hardware (specifically the processor, I think I/O cards are handled with PTF's.) The LIC build is identifiable by looking at marker PTF's, see Info APAR II13365 at: http://www-912.ibm.com/n_dir/NAS4APAR.NSF/5fafac98aa8265b1862564c00079d111/9 4a6a270552366b286256c01003c9105?OpenDocument To "refresh" the LIC you would need to do a slip upgrade, not much different than a full upgrade. It's probably better just to stay current on cumulative and group PTF's. Regards, Scott Ingvaldson AS/400 System Administrator GuideOne Insurance Group -----Original Message----- date: Tue, 30 Mar 2004 14:45:41 -0600 from: jeff_carey@xxxxxxxxxx subject: Determining and refreshing build of LIC Is there a way to see what build of the LIC was used to install a system? Is it a good idea to refresh this? I think that is done via GO PTF option 8, correct? Jeff Carey Technical Specialist iSeries Technology 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. The information transmitted is intended only for the person(s)or entity to which it is addressed and may contain confidential and/or legally privileged material. Delivery of this message to any person other than the intended recipient(s) is not intended in any way to waive privilege or confidentiality. Any review, retransmission, dissemination or other use of , or taking of any action in reliance upon, this information by entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer. For Translation: http://www.baxter.com/email_disclaimer
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.