|
At 08:48 02/09/2000 , Debbie Gallagher wrote: >It seems to me that LODPTF is transferring the info from the CD to the >AS/400. According to the documentation, the PTFs are applied at IPL. Is this >much right? LODPTF makes a list of PTFs that are eligible for installation. It makes sure that all co and pre requisites are either installed or available for installation, and (it can) permanently apply superceded PTFs so that they will be out of the way. APYPTF processes the PTFs that have been previously loaded. It can apply PTFs right now (if the PTF allows it), a mixture of right now and during the next unattended IPL, or during the next unattended IPL only. Some PTFs (usually microcode PTFs) are "delayed" and can only be applied during IPL. You can't rotate your tires while you're driving down the highway either. >What I am still missing is - how is APYPTF different from Install PTF >package? What is being done at these steps? During the early days of OS400, the PTF process consisted of permanently applying existing PTFs, then loading and applying all PTFs for each program product on the system. The instruction pamphlet was about the same size it is now, but it consisted mostly of commands that you had to key at the console. Even then, the PTF process (usually) had enough intelligence to handle the pre and co requisites. Sometimes multiple IPLs were required, but usually one was enough to handle the delayed PTFs. This process has been streamlined, but the basic steps are still required. When you install a PTF package, you are running a program that examines your system and loads the required PTFs, then applies them and initiates an unattended IPL during which the delayed applies are actually processed. Pete Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.