http://www.itjungle.com/ptf/DLB-PTF_063012_V14N26.html Cumulative PTFs are a package containing all the PTFs up to date.

HIPER PTFs are important updates for your system (not all PTFs). Cumulative PTFs are a package containing all the PTFs up to date. A cumulative (cume) PTF package doesnt contain all PTFs up to date. It contains probably the majority of them; but they only include ones IBM determines apply to most systems and they dont include PTFs that have been issued since the publication date of the cume package. A PTF might apply only to a very specific combination of hardware and software. A high-end tape drive, for example, might have a PTF that takes advantage of particular option that is not common. (A made-up example.) The PTF ay be be cataloged on the IBM PTF site as being part of cume level 1000 which means none. Theres no point in having it shipped to everyone. Then there are group PTF packages. These are sets of PTFs that all relate to an area such as DB2 or Java. Group packages are released much more often than cume packages. If you have an issue with a SQL function, it might be handled in the DB2 group that was released in the past two or three weeks while the latest cume package could be three, four or more months old and not have it. The latest PTFs in a group will probably not be on a cume yet. When you order the latest cume package, IBM also sends the latest DB2 group package for that reason. Many DB2 PTFs can be missed by not applying the DB2 group. HIPER PTF packages contain High Impact/PERvasive PTFs. These are PTFs that are likely to affect nearly everybody regardless of their hardware or software options or that may correct serious issues. A cume package order will also result in the current HIPER package being sent.

Four Simple Rules For IBM i PTF Management Talking with an IBM Business Partner this week, the conversation turned to PTF management and the best ways for managing cumulative PTFs. Inspired by this talk, I came up with these four simple rules for a good PTF management strategy. Rule 1: Don't Let Your PTFs Age A lot of shops only apply PTFs when they upgrade their hardware, but many (or most) shops are also frequently upgrading their application software. Frequent application changes can create new processing situations that test the limits of a partition's Licensed

Internal Code (LIC) and operating system fixes. In a rapidly changing applications environment, it's more important than ever to keep current with PTFs. I've seen two situations in the past year where an IBM i system went down during the production day and the fix was to apply more current PTFs. So while IBM i systems may be the most reliable computers on this or any other planet, operating system errors can also happen to these partitions if youre not current on fixes. So don't let your cumulative PTFs get too old. Rule 2: Don't Rush Cumulative PTFs. . . Maybe Conventional wisdom says don't rush to put cumulative PTFs (cumes) on your system as soon as they're released. The fear is that if IBM releases a bad PTF on a cume, it may take a month or so for them to realize it. So the thinking goes, if you wait a month or two after the cume is released, IBM will have time to correct any bad PTFs it may have released with the package. The jury is still out on this one. There are plenty of people who religiously put cume PTFs on their system without any problems. So Im not sure if waiting to apply cume PTFs is a valid action or not. If anyone from IBM who is knowledgeable about cume PTFs is reading this, please email me to let me know whether Big Blue corrects PTF package after they hit the system. I'd be curious to see how much truth there is to the conventional wisdom out there. Until I hear otherwise however, I'd stick with the common wisdom and wait a reasonable time (say a month after release) before ordering and applying cume PTFs on your system. Rule 3: Apply PTFs To Your Partitions In The Proper Sequence If you have several different partitions that serve different functions for your shop, there's a definite sequence you should follow to apply the same cumulative PTF package to each partition. IMHO, heres how I believe cumes should be applied across all your various partitions. 1. All new PTF packages go on the development partition first--Development partitions are made for testing software fixes and modifications. Put any new PTF packages on your development partitions first and let them run on the box for at least a week before you post the PTFs to another partition. That way you'll have some confidence that the act of applying these PTFs will not harm your production systems. And if there is a bad PTF on the partition, running it on development for a while gives you time to discover the issue before it goes to production. 2. High availability (HA) or backup partitions get new PTF packages second--HA and backup partitions should always get PTFs before your production box. Again, this provides some time for bad PTFs to show themselves without taking down your

production system. And once you apply PTFs to both your development and your HA partitions without incident, you'll have a much higher confidence level that your PTFs wont damage your production system. 3. Special purpose partitions receive PTFs next--If you have a partition that's devoted to a certain function, that partition should be the next one to get your PTF package. For example, if you have an isolated IBM i partition that runs credit card processing in its own secured network for PCI compliance, apply your PTFs to that partition before applying them to your general production partition. Again, this is part of the vetting process to ensure that all PTFs go on smoothly before going to production. 4. Main production partitions receive PTFs last--If you apply PTFs in this methodical style, you'll have pretty good confidence that you won't have any problems applying PTFs to production. Rule 4: Pick Your Poison For A Production System PTF IPL When you IPL your system to apply PTFs is almost as important as how you apply your PTFs. With most partitions running 24x7x365, finding a time when you can take your system down for an IPL can be a delicate maneuver. For PTF applications, you always have to find a time when the system is relatively quiet for IPLing. But that time can depend on a number of situations, including:

End of month or end of year closing where the system needs to be up to balance the books. Physical inventory or weekend warehouse work where workers using scanners need to access and update inventory. Busy season where the company imposes a moratorium on making any system changes that would affect availability (think Black Friday through New Year's for a retailer). Busy times of the week when customers may be entering orders.

It's wise to know your company's processing pain points and to schedule PTF IPLs around those events. For most partitions, an IPL isn't a long enough event to trigger a switch-over to a Capacity BackUp (CBU) system. So until you migrate to a high availability solution that can perform an immediate switch-over, you will still have to deal with your companys processing schedule. Not The Only Rules, But A Start Take these PTF rules as just a starter guide for your own PTF strategy. Great PTF reference available It's also worth noting that IT Jungle publishes the System i PTF Guide, a complete listing of all PTF group levels and the last dates each PTF group was changed (including

HiPERs and Cumulative PTFs). This site is worth checking on a regular basis when you're looking for fixes. Admin Alert: Readers Check in on Four Simple Rules for PTFs Q: When does IBM refresh a Cume PTF package? A: Never Reader Richard Shearwood wrote in with this piece of information about whether IBM corrects cumulative PTF packages containing bad PTFs after the package is released. IBM never refreshed a cume PTF package with new content as far as I can tell. But they can and do replace cumulative PTFs pretty quickly if they need to. I haven't seen it for a while but back in 2006, a cume PTF had a major defective PTF that could require a reload of the Licensed Internal Code (LIC) to remove. So the next cume PTF after that was released just 41 days later. Full details are inSF98088 (V5R3 defective PTFs) for the morbidly curious. Speaking of defective PTF packs, you might have come across a bug in the latest i 7.1 cumulative pack--or, indeed, several bugs. One or two key PTFs have incorrect CoReq/PreReq specifications and the pack will not apply if the previous pack is too old. In this case, you need to apply PTF 5770999 MF54291 as a *TEMP PTF with all its PreReq PTFs and then do the same for PTF 5770SS1 SI45000. Change your IPL attributes to IPL into restricted state with the following Change IPL Attributes (CHGIPLA) command:
CHGIPLA STRSTD(*YES)

IPL your machine and once the machine comes up in restricted state, carry on to reapply the pack. Thanks, Richard. That's good information on the bug in the i 7.1 cume package. It's things like Richard's 2006 story where a defective PTF has an adverse effect on your system, that led me to adopt rule #2 in my PTF Management article, Don't Rush Cumulative PTFs. Wait a reasonable time before applying a cumulative PTF package after it's released, at least a month. And be sure to check IBM's Preventive Service Planning (PSP) Defective PTFs page for the latest on bad PTFs for each release and what to do about them. Here are the links to the PSP Defective PTFs pages for each of the currently supported releases.

i5/OS V5R4 i 6.1 i 7.1

Simple Rules Five, Six, and Seven for PTF Management?

The following general PTF management suggestions came from an IBMer who wrote in. Some of these ideas might be considered extensions to my four rules of PTF management. 1. Take a snapshot of the following key system information prior to loading or applying PTFs. This gives you a baseline in case of post-PTF issues.

The Work with System Status screen (WRKSYSSTS) Work with PTF Groups screen (WRKPTFGRP) All system values with the Work with System Values (WRKSYSVAL) command The Display IPL Attributes (DSPIPLA) command

2. Capture or save pre-PTF performance baseline information so if issues arise after the PTF apply, you have data to compare your performance to. 3. Develop a test plan to thoroughly exercise system functions and application code so that the post-PTF testing done on the development system will really test the PTFs. There are good suggestions for everyone to minimize any adverse effects a cume PTF package might have on your system. In particular, these steps may serve you well if you're in a Sarbanes-Oxley (SOX) environment, where there may be a greater requirement to document PTF testing before and after PTF application. I run a Data Center for two different companies, one of which falls under Sarbanes-Oxley. I can tell you that the requirements for the SOX environment are much more stringent for doing things like applying PTFs. Following these steps might help when the auditors come around. Don't Waste Time Before Installing Hiper PTFs And then there was this suggestion from Luis Rodriguez about the need to rush Hiper PTFs on to your system. To Rule #2: Don't Rush Cumulative PTFsMaybe, I would add: Rule 2b: RUSH with Hiper PTFs. . . (After carefully considerations, of course)\r\nHiper PTFs are High Impact/Pervasive for a good reason. If you check the Hiper PTF list and it looks as if one of them could apply to your system, don't waste too much time installing them. Regarding cume PTFs, I belong to one of those lucky souls that never (AFAIK) had a problem with them. The one month rule [before applying cumulative PTFs after the cume package is released] is always good, though. I've had the same experience as Luis, where I've been lucky and have never had a problem with bad cume PTFs on my machine (hope this doesn't curse it). That said, I still think I'd go with waiting a month to see what happens before applying the package.

Which Came First, The Group PTF or the Cume? Similar to the common question about the chicken or the egg, Ed Evers wrote in with this puzzling query. I have heard (quite a while ago) that a faster way to apply PTFs was: For existing systems: Apply group PTFs prior to applying the new cume. For new installs: Apply cume first, then apply groups. Any truth to that? I have never tried to apply group PTFs before the cume package. I always apply the cumulative PTFs first. I have to confess that I don't know the answer to this. However, if anyone reading this has any information on this topic, please email me through the IT Jungle Team Web site However, I'm not sure why there would be a difference in your PTF load/apply sequence between existing systems and new systems. My gut feeling is that in all instances, the cume should be loaded first before the group PTFs. I usually load both the cume and the group PTFs at the same time through option 8 (Install program temporary fix package) on the Program Temporary Fix (GO PTF) menu. If I change the Prompt for Media parameter to 2=Mulltiple PTF volume sets, Option 8 will prompt me for additional PTF sets after I finish loading the cumulative package. After I load both PTF packages, I then apply them at the same time with an IPL. This load sequence makes sense to me because I'm much more likely to have any PreReqs and CoReqs for the group PTFs loaded before the group package is loaded. Again, I'm not sure why loading one set of PTFs before the other would make a difference but like you, I started doing it this way a long time ago and I never broke the habit.

PTFs: FAQs / Question and Answers

Q1: What is a PTF? What is a Cumulative package? A1: A PTF is a temporary solution to or bypass of a problem diagnosed by IBM as resulting from a defect in a current, unaltered release of a licensed program. A cumulative

(Cumulative) PTF package contains PTFs that affect the general system population for a specific release. Q 2: If I have two different Cumulative PTF packages, do I have to install both of them? A2: Because Cumulative PTFs are cumulative, only the most current cumulative package must be installed. Q 3: What is the difference between the A side and the B side? A3: A and B side concepts are relative to LIC and not to the operating system or LPP PTFs. When a new system is shipped or when the operating system is upgraded to a new release, the A side and B side match. When LIC PTFs are temporarily applied, they are applied to the B side. If you have temporarily applied LIC PTFs and you are running on the A side, you will not be running with the PTFs. Previous to V3R1M0, you had to be running on the A side to apply PTFs to the B side. When GO PTF , Option 8 is used to apply LIC PTFs, the system determines if you are running on the A side or the B side. If you are running on the A side, the LIC PTFs are applied immediately. The system is IPLed to the B side to apply the rest of the PTFs. If you are running on the B side, the system does a partial IPL to the A side to apply the LIC PTFs. The system is IPLed back to the B side to apply the rest of the PTFs. Starting at V3R1M0, immediate LIC PTFs can be applied to the B side while you are running on the B side. If you are on the B side and you use GO PTF Option 8, Automatic IPL Y to apply immediate LIC PTFs, the system IPLs to the B side to apply the PTFs. The system does not IPL to the A side. Delayed LIC PTFs in V3R1 and beyond function the same way all LIC PTFs functioned before V3R1M0. Permanently applying LIC PTFs puts the PTF on the A side. Once the PTF is permanently applied, it cannot be removed. Q 4: I forgot to do CHGMSGQ QSYSOPR *BREAK SEV(70) . Now I have a message that needs a reply. How do I respond? A4: A system request is required to reply to the message(s). Once the system request menu is up, Option 6 allows the ability to respond to the messages requiring a response. Q 5 : My Cumulative package did not install. How do I determine what is wrong? A5: First, determine if the failure occurred during the load or apply phase of the cumulative package installation. If the system did not IPL, the failure may have occurred during the load phase. Do a help on the failure message. Then, press PF10 from the message details panel to view the messages in the joblog. Look for all escape messages that indicate what the problem is. Fix these errors, and try the request again. If the system IPLed and the PTFs did not apply, start by looking at the history log. On the

operating system command line, type GO LICPGM , and select Option 50 to display the log for messages. o Look for a message indicating if the IPL was normal or abnormal. PTFs are not always applied during an abnormal IPL. o If Perform Automatic IPL was not selected on the Installation options for the PTFs panel, verify that the power down system command (PWRDWNSYS ) was done with RESTART(*YES) and the keylock position was at normal. If RESTART(*NO) was used, the system does not automatically IPL to the A side to apply LIC PTFs. o Look for any messages that indicate that there was a failure during the IPL. If failure messages are found, go to the SCPF joblog to find the detailed messages indicating the cause of the problem. To find the SCPF joblog, use the WRKJOB SCPF command. You may get a list of jobs. If you just did the IPL, choose the first one that is not active. Look at the spooled file for that job. The detailed error messages can be found in this joblog. Find the error messages, and try to determine what caused the error. If you can, fix the problem, and then re-IPL the system to apply the remaining PTFs. If you cannot fix the problem, have the information in the joblog available when you call the Rochester Support Center. Q6: I was trying to load a PTF, and I got message CPA3576 indicating that my Master Program Temporary Fix Index (MPTFI) may be damaged. What should I do? A6: Message CPA3576 is issued as a general error message and does not necessarily mean that the MPTFI has been damaged. Do not answer D to this message. Always answer with C unless directed otherwise by service support. Display your joblog to see what other errors are in the joblog. This is your clue as to what really went wrong. Correct any errors, and try your request again. If this does not solve the problem, have the information in the joblog available when you call the IBM Rochester Support Center. Q7: I want to send multiple PTFs to another system. How can I load them all with one command instead of having to specify each PTF save file on the LODPTF command? A7: One option is to use the Send Network File (SNDNETF ) command to send the PTF save files to the other system. On the remote system, use the QPZGENNM API to generate a valid save file name for the PTF save file. Create a save file in QGPL by that name and receive the PTF into that save file. Use the QPZLOGFX API to log the PTF into *SERVICE. Once this has been done, the PTF is recognized by the system for any PTF functions like LODPTF DEV(*SERVICE) . Refer to the iSeries Information Center for further information on these APIs. Note: At R540 and above, if all *SAVFs get send to the target system, the UPDPTFINF command can be used to get the serviceable attributes recognized by the system A second option is the Send PTF (SNDPTF ) command to send the PTF save files. The SNDPTF command sends the PTFs, loads them, and sets them for apply with a single command on the remote system. The command is available with the System

Manager/400 Licensed Program Product (LPP). A third option is to use FTP to send the *SAVFs among the systems. Then, as with the SNDNETF command above, the APIs are required to get the PTFs put back into *SERVICE. A fourth option is when using Virtual Image Catalog to load/apply PTFs, all .bin file images will reside in a single Integrated File System directory. That Integrated File System directory can be saved into a *SAVF and then moved over to the other systems using FTP or the SNDNETF command and then restored into the target Integrated File System. Once restored on the target a new image catalog can be built off of that directory to load and apply PTFs. Lastly, iSeries Navigator can be used. To use Management Central, refer to Rochester Support Center knowledgebase document 30390328, Management Central PTF/Fix Send Function , for more information. To link to document 30390328 immediately, click here . Within iSeries Navigator, a user can drag and drop the .bin file images between the Integrated File System on the source system and the Integrated File System on the target system. Once the .bin files reside on the target, the Virtual Image Catalog can be used to load or apply PTFs. Q8: What does it mean when a PTF has an action required? A8: This was a new concept in V3R1M0. Some PTFs that were previously delayed PTFs can now be applied immediately, However, some additional steps are required to make them active. These additional steps are described in the cover letter. The following types of action required PTFs exist: updateable and non-updateable. Updateable action required PTFs are shipped with an action exit program to verify the actions required to make the PTF active have been done. The action exit program is called by the Display PTF (DSPPTF ) command to list the actions that are necessary to make the PTF active and to verify if the actions have been completed. The exit program is called when the details for the PTF are displayed using Option 5 on the Display PTF Status panel or when you select *ACTRQD PTFs on the DSPPTF command. At this time, the status of the PTF is updated if the actions are complete. The status of the PTF changes from Temporarily applied - PND to Temporarily applied after all required actions have been completed. Non-updateable action required PTFs do not have an exit program to verify the actions have been done. These PTFs remain in a status of Temporarily applied - ACN until the next IPL. During the IPL, the status of the PTF changes to Temporarily applied. It is important to note that any dependent PTFs cannot be applied until the pre-requisite PTF indicates that its actions are complete. Q9: What is iSeries 400 ALERT?

A9: iSeries 400 ALERT is a service that proactively notifies customers of critical software and hardware problems and PTFs that may help avoid system interruptions and expensive down time. Notices tailored to the user's release and cumulative PTF level are sent by facsimile or mail to the user's site. Weekly reports include notification of: Contact you marketing representative for more information on this service offering. For a free type of alert service, go to Subscription Service for System i5 at thie website: https://www947.ibm.com/systems/support/myview/subscription/css.wss/subscriptions? methodName=listAvailableSubscriptions Q10: How do I generate a listing of my PTFs? A10: To generate a list of the PTFs applied to your system, on the operating system command line type in the following: DSPPTF LICPGM(*ALL) SELECT(*ALL) RLS(*ALL) OUTPUT(*PRINT) Press the Enter key. Then, type the following: WRKSPLF Press the Enter key. You can then display or print as needed. Q11: What is the command used to order PTFs electronically? A11: To order individual PTFs, on the operating system command line type the following: SNDPTFORD PTFID(nnnnnnn) where nnnnnnn is the number of the PTF you want to order. Press the Enter key. You can order up to 20 PTFs simultaneously. Q12: How do I order cumulative PTF packages electronically? A12: To order cumulative PTF packages, on the operating system command line type the following: SNDPTFORD PTFID(SF99VRM) press the Enter key. The last three digits indicate the version, release, and modification level of the operating system. Q13: What is PSP information?

A13: PSP stands for Preventive Service Planning. It is a collection of information used when installing a licensed program, cumulative PTF package, or hardware. PSP information should be reviewed before installing a licensed program, a cumulative PTF package, or hardware. Q14: How do I order the PSP information for the current cumulative PTF package? A14: To order the PSP information for the current cumulative PTF package, on the operating system command line type the following: SNDPTFORD PTFID(SF98VRM) Press the Enter key. The last 3 digits indicate the version, release, and modification level of the operating system. Q15: How can I determine what the current Cumulative PTF is and when the next one is scheduled for release? A15: SF98VRM gives the current Cumulative PTF number and also mentions the target date for the next scheduled Cumulative PTF. Q16: Can I order a new Cumulative PTF before it is actually available? A16: The Cumulative PTF must be available before it can be ordered. Q 17 : How can I tell what PTFs I have installed on my system? A17: Use the Display PTF (DSPPTF ) command, and specify the product ID. If you do not know the product ID, on the operating system command line type DSPPTF , and press the Enter key. This brings up the first product. Every time you press the Enter key, it takes you to the next product installed on your system. Q18: How can I tell what Cumulative PTF Package is on my system? A18: On the operating system command line, type DSPPTF LICPGM(57xx999) and verify what the first TLnXXXX number is. Or, type DSPPTF LICPGM(57xxSS1) , and verify that the first TCnXXXX or TAnXXXX number is. XXXX represents the first 4 numbers of the Cumulative tape package identifier. The TL number stands for the HIPER VLIC PTFs on the Cumulative package, TC represents the operating system PTFs on the Cumulative package, and TA represents the HIPER operating system PTFs on the Cumulative package. The n represents some number based on the current year. For example, Cumulative PTF C7002540 Breaks down to TL07002, TC07002, and TA07002. Q19: How can I find out what PTFs are on the Cumulative PTF that I received?

A19: Load the Cumulative package into the optical drive (OPTXX). Then, do the following: 1. On the operating system command line type the following command, and press the Enter key: WRKOPTVOL 2. Select Option 11 to Work with object links. 3. Locate the README file. 4. Type 5 to display. 5. Locate the PKGLIST.TXT. 6. Type 5 to display. This provides a summary listing of the PTFs contained within the package. While this is a listing of the PTFs contained within the package, it is not a complete listing. Pre-req and Co-req PTFs are not included in the PTF listing. Q20: How do I print PSP information that I have downloaded? A20: On the operating system command line, type the following: CPYF FROMFILE(QGPL/QAPZCOVER) TOFILE(QGPL/QPRINT) FRMMBR(QSF98XXX) Press the Enter key. Q21: How can I print a cover letter for the PTF I have downloaded? A21: On the operating system command line, type the following: DSPPTF LICPGM(57xxYYY) SELECT(SIXXXXX) COVERONLY(*YES) OUTPUT(*PRINT) Then, run the WRKSPLF command. You can display or print the cover letter. Q22: Where are the cover letters for PTFs stored on my system? A22: They are stored in a file called QAPZCOVER in QGPL. Q23: How can I get QAPZCOVER back on my system if I accidentally deleted it. A23: You can run the RSTOBJ command from a previous backup or you can re-create it. To re-create QAPZCOVER, On the operating system command LINE, type the following: CRTPF FILE(QGPL/QAPZCOVER) RCDLEN(80) FILETYPE(*DATA) + LVLCHK(*NO) MBR(*NONE) MAXMBRS(*NOMAX) AUT(*USE) + TEXT('PTF COVER LETTERS')

Press the Enter key. Then, on the operating system command line type the following: CHGOBJOWN OBJ(QGPL/QAPZCOVER) OBJTYPE(*FILE) NEWOWN(QSYS) Press the Enter key. Then, on the operating system command line type the following: GRTOBJAUT OBJ(QGPL/QAPZCOVER) OBJTYPE(*FILE) + USER(QSYS QSRVBAS) AUT(*ALL) Press the Enter key. Q24: What is the difference between an immediate PTF and a delayed PTF? A24: An immediate PTF can be applied without doing an IPL if the licensed program it affects is not in use. An IPL is required to apply delayed PTFs. In some cases, there may be an action pending status until a special instruction is done or an IPL. In some cases, MF PTFs can be applied immediately while on the B side of the operating system. Q25: Do I have to load the PTF before I can apply it? A25: The PTF must be loaded or the apply does not work. Q26: I just received some PTFs via the ECS line. How do I apply them? A26: To apply the PTFs, do the following: 1. On the operating system command line type the following: GO PTF 2. Select Option 8 from the menu to install fix package. 3. Specify *SERVICE for the device. 4. Specify Y or N for the IPL depending if you can IPL at the time. 5. Specify 1 for all PTFs. 6. Specify N for other options unless you do not want to load all that have been downloaded electronically. This ensures all pre-req and co-req checking is done for the successful load and apply of the PTFs. However, if N is specified for the IPL, PTFs do not get applied until the IPL has been issued. The IPL should be done with the following command: PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B) Q27: How do I remove a PTF that is temporarily applied to my system? A27: If it is an immediate MF PTF, an IPL to the system might need to be performed. Then, on the operating system command line, type the following: RMVPTF LICPGM(57xx999) SELECT(MFXXXXX) RMV(*PERM) Then, we must IPL back to the B side of the system. If it is an immediate SF PTF, on the

operating system command line type the following: RMVPTF LICPGM(57xxYYY) SELECT(SIXXXXX) RMV(*TEMP) which puts it in a Not Applied Status. We can then issue it again with RMV(*PERM) so it does not show up on the system. If it is a delayed PTF, specify DELAYED(*YES) so it is removed on the next IPL. Q28: Does the system have to be restricted to load PTFs? A28: We can load a PTF and mark it to be applied on the next IPL unless it is an immediate PTF which we can apply if no one is using that product. Q29: What is the procedure to get PTFs on my system? A29: On the operating system command line, type GO PTF . Select Option 8 to load any PTFs you have to be applied. Or, you can do a LODPTF and APYPTF for each PTF. This must be done for each product. Q30: If I order one PTF, why do I sometimes receive more than the one that I order? A30: The prereq and coreq PTFs are sent along also to make sure we have everything we need to get the full effect of the PTF. The cover letter mentions these PTF numbers. Q31: How do I remove a damaged PTF from my system? A31: Because nothing can be done with the PTF while in a damaged status, the PTF must be reloaded with the LODPTF . Then, a RMVPTF can be done to remove it or a LODPTF can be done to apply it again. Q32: I have just loaded PTFs on my system. How can I verify if they are set to be applied on the next IPL? A32: Use the DSPPTF command, and verify the IPL action. If it is N, the PTF has not been marked to be applied. If you look at the general information of the PTF the unattended IPL action should say apply temporarily. Q33: How should I issue my IPL to apply my PTFs? A33: On the operating system command line, type the following: PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B) Q34: I have loaded my PTF and have to apply it delayed. What command do I use? A34: On the operating system command line, type the following:

APYPTF LICPGM(57xxYYY) SELECT(SIXXXXX) DELAYED(*YES) Q35: How do I know which side I am running on? A35: On the operating system command line, type the following: DSPPTF Verify what the IPL source at the top of the screen is. The control panel does not say what side you are on but what the next IPL will be. Q36: What is a superseded PTF? A36: A superseded PTF is one that has never been installed on the system, however, it is shown as superseded because the changes from this PTF have been included in a new PTF that has been installed on the system. If the PTF had been temporarily applied and we install the new PTF, it automatically permanently applies the old PTF so the code from the new PTF is used, and the new PTF is now in a temporarily applied status. Q37: I was doing a SAVSYS, and I received message CPI35C3 MPTFI for licensed internal code not saved due to error in the QSYSOPR message queue. What does that mean, and what do I need to do to recover? A37: This message is sent whenever the information about LIC PTFs is not saved during a SAVSYS . If the system is restored using these SAVSYS tapes, the information about the LIC PTFs installed on the system is missing. This could cause installation errors when future cumulative PTF packages are installed. The typical error that occurs is a CPF7206 Service function ended abnormally. Completion code 'FFFF'x qualifier 000000000000000B'X. This indicates an attempt was made to apply a PTF to a module that already has a PTF temporarily applied to it. You can determine why the CPI35C5 was issued and correct the error. Then, redo the SAVSYS . Or, when you reinstall the system, you can re-slip LIC from PID media and reapply the PTFs that were previously applied to the system. Q38: Where can I find more information on PTFs? A38: PTF information can be found on the iSeries Information Center under the topics: OS/400 and related software, Maintain and manage OS/400 and related software, Use software fixes. Additional PTF information can also be found at the following Web site: http://www.ibm.com/servers/eserver/support/iseries/fixes/guide/index.html Q39: What is the command WRKPTFGRP for? A3 9: The Work with PTF Groups display shows you a list of PTF groups on the system.

A PTF group consists of a list of program temporary fixes (PTFs) defined for the purpose of managing those PTFs as one entity. A PTF group can identify other PTF groups, called related PTF groups. The PTFs in the PTF group as well as the PTFs in all related PTF groups are used to determine the overall status of the PTF group. Starting at V6R1M0, this command can be formatted to show what previous levels of the groups have been installed on the system. The number of levels displayed is controlled by the CHGSRVA command's 'PTF group levels' parameter. Q40: What is the function of the UPDPTFINF command? A40: The Update Program Temporary Fix Information (UPDPTFINF ) command updates PTF information for all PTF save files in library QGPL. It was first introduced at V5R4M0. By running this command, the *SERVICE flag is turned on for those PTFs and from there you can run the GO PTF Option 8 menu selection and specify *SERVICE for the device to load and mark the associated PTFs. You can also run the DLTPTF command and safely remove the save files and cover letters for those PTFs. This is very useful when Fix Central brings down a number of save files for PTFs that are for different releases than what the system is at. Q41: What is DSPFMWSTS used for? A41: The Display Firmware Status (DSPFMWSTS ) command displays information for the current server firmware.