PTF » Current News Trends Dec 9, 2009   11:45 AM GMT

[...] PTF [...]

0 pointsBadges:

Manish15 Jun 19, 2010   11:32 AM GMT

Types of fixes Many different kinds of fixes exist, and each fix has its own purpose. This topic introduces you to the different kinds of fixes and discusses when each type is available. Single fixes Single PTFs are applied to correct specific reported problems. A high-impact pervasive (HIPER) PTF is an example of a single PTF that resolves a problem that may have a high impact on the operations of your server or a low-impact pervasive problem that affects most iSeries(TM) servers. Cumulative PTF packages Cumulative PTF packages contain fixes for a given release of the i5/OS(TM) operating system and associated licensed programs. You should install the entire cumulative PTF package after you first load or reload the operating system and periodically throughout the release as defined in your maintenance strategy. Fix groups A PTF group or fix group is a name that is used to order and manage a group of logically related PTFs. Service packs Service packs are different from group PTFs. A service pack is a collection of code fixes (not PTFs) for iSeries Access for Windows(R) products that is contained in a single OS/400(R) PTF. Single fixes Single fixes are applied to correct specific reported problems. Single fixes are available on media, or are capable of being downloaded with electronic customer support or from the Internet. Examples of single fixes are: High-impact pervasive (HIPER) PTF A HIPER PTF resolves a problem that may have a high impact on OS/400(R) operations or a low-impact pervasive problem that affects most iSeries(TM) servers. Prerequisite fix A prerequisite fix is a fix that must be installed on your server before or at the same time as the fix that you want to install. Corequisite fix A corequisite fix must be installed at the same time as the fix that you are requesting to install. Distribution requisite fix A distribution requisite fix is required for distribution purposes only. Delayed and immediate fixes Some fixes can be applied without requiring an IPL, and some fixes can be applied only during an IPL. Find out about delayed and immediate fixes. HIPER PTFs HIPER PTFs correct severe problems that occur on your system. HIPER PTFs represent two types of problems, high impact or pervasive and high impact and pervasive. Examples of these situations are the following: • Your system may crash or hang and requires a restart or IPL (initial program load) to recover. • Your system may be stuck in a looping condition. • Your system's data integrity may be threatened. • Your system may experience a severe performance degradation, or the problem involves usability of a product's major function. If any of the fixes are needed to address these situations for your system, you should order and install the HIPER fixes. For a complete listing of HIPER fixes, see the preventive service planning information at the Support for System i Web site. Prerequisite fix A prerequisite fix is a fix that must be installed on your server before or at the same time as the fix that you want to install. The system will prevent you from installing your fixes if you do not have the prerequisite fixes. Your fix cover letter or PSP information can identify other fixes that must be installed before or at the same time as the fix that you want to install Corequisite fix A corequisite fix must be installed at the same time as the fix that you are requesting to install. Your fix cover letter or PSP information can identify other fixes that must be installed before or at the same time as the fix that you want to install. In addition, system error messages can notify you that the fix that you are attempting to install has requisite fixes. The system checks that the corequisite fixes are installed at the same time. In this case, you need to verify that your fixes installed successfully. Distribution requisite fix A distribution requisite fix is required for distribution purposes only. A distribution requisite fix is sent and installed only if it is named by a fix listed in a fix group and you are using that fix group to send or install fixes. If you are sending only a fix, then the distribution requisite fix is not sent and installed. The system does not require you to apply distribution requisites Delayed and immediate fixes Some fixes can be applied without requiring an IPL. There fixes are called immediate PTFs. Some fixes can be applied only during an IPL. These are called delayed PTFs. Immediate PTFs can also be applied during an IPL. The cover letter tells you if the PTF is immediate or delayed. Delayed Some fixes cannot be applied immediately because the licensed programs they affect are active. These fixes are called delayed fixes and can be applied only at the next IPL. Delayed fixes that affect the Licensed Internal Code can be applied immediately when running on the A storage area. Immediate Immediate fixes can be applied without doing an IPL if the objects that they affect are not in use, or may be applied when you do the next IPL Cumulative PTF packages Cumulative PTF packages contain fixes for a given release of the i5/OS(TM) operating system. The fixes contained in a cumulative PTF package are for the Licensed Internal Code and most licensed programs that can be installed on that operating system release. As the name implies, each package is cumulative, that is, it contains all of the fixes from the previous package plus additional fixes released since the previous package. Many, but not all, new fixes are included in cumulative packages. The fixes that are not included are typically applicable only to a specific user's situation or application. These fixes are not included for general availability to avoid introducing unwanted change and potential programming errors into a cumulative package where code quality has the highest priority. When you order the cumulative PTF package, you also receive the most recent Database PTF group and the HIPER PTF group. How often a cumulative package is available depends on the stage of the i5/OS release life cycle. During the first six months or so of general availability for a new release, a cumulative package can be available as often as every four to six weeks. After that time, cumulative packages are scheduled on a quarterly basis. After the i5/OS release has been available for a period of time, the frequency may decrease again. The frequency of availability depends on the number of new fixes to be added to the package. You should install cumulative PTF packages quarterly in dynamic environments and less frequently in stable ones. You should also consider installing cumulative fix packages prior to making major hardware or software changes to your environment. Fix groups A PTF group (or fix group) is a name that is used to order and manage a group of logically related PTFs. A PTF group or fix group consists of a list of PTFs defined for the purpose of managing those PTFs as one entity. A PTF group can identify other PTF groups called related PTF groups. A related fix group is a fix group that is listed in another fix group. The fixes in the fix group as well as the fixes in all related fix groups are used to determine the overall status of the fix group. IBM creates and maintains a set of PTF groups for certain functions on the system. PTF groups are available for each supported i5/OS(TM) release and are updated periodically. For a complete listing of PTF groups, see the preventive service planning information at the Support for System i Web site. In iSeries(TM) Navigator, you can perform these tasks for fix groups: send, send and install, or install. When you select a fix group to send and install, the fixes from all related fix groups are also sent and installed. The cumulative PTF package is shown as a PTF group on the Work with PTF Groups (WRKPTFGRP) display and in the Management Central fix group inventory. The cumulative PTF package is identified as a PTF group named in the format SF99vrm where vrm stands for version, release, and modification of the operating system. However, the Management Central functions of sending fixes, sending and installing fixes, and installing fixes are not supported for the cumulative fix group. Note: Even though the Compare and Update wizard (described in the topic Compare and update fixes) does not prevent you from comparing and updating fixes on systems at different cumulative levels, the wizard does not handle fix groups. It is recommended that your systems be at the same level of the cumulative PTF package before using the Compare and Update function. Order the latest level of the cumulative PTF package for the release of the operating system that is installed on the system by using Fix Central or SNDPTFORD *CUMPKG from each endpoint system. Select GO PTF option 8 (Install program temporary fix package) or the Install PTF (INSPTF) command to install the cumulative PTF package and maintain the correct PTF group information for the cumulative PTF package. Then use the Compare and Update wizard to work with a smaller number of differences. By following this recommendation, you ensure that the special instructions that accompany the cumulative PTF package are followed. For information about the tasks that you can perform with PTF groups, see the following items: Order PTF groups Use the Send PTF Order (SNDPTFORD) command to order your PTF groups. Manage PTF groups Manage your PTF groups with the Work with PTF Groups (WRKPTFGRP) command, the Copy PTF Group (CPYPTFGRP) command, or the fix group function that is available from iSeries Navigator. Display properties for fix groups Use iSeries Navigator to Display properties for fixes and fix groups. Create PTF groups Create your own fix group with the Create PTF Group (QpzCreatePtfGroup) API. Service packs A service pack is a collection of code fixes for iSeries(TM) Access for Windows(R). For specific service pack information, see the following: iSeries Access Web site The Web site tells you what service packs are available, how you can be notified when a new service pack is available, and how to order and download a service pack. Install service packs Find out how to check the service level, how to obtain the latest service pack, and how to install it. Order fixes Before you begin ordering fixes, you should order and apply the latest cumulative PTF package. When you apply cumulative PTF packages, you reduce the number of fixes that you need to order and distribute later. Some fix orders require special handling when received at an i5/OS(TM) service provider from a service requester. The following list identifies these special fix packages and indicates what they are: • MF98vrm: Hardware Service Planning package • SF98vrm: Preventive Service Planning package • SF99vrm: Cumulative PTF package • SF99xxx: PTF group • SF97vrm: PTF Summary package The vrm identifier stands for the version, release, and modification level of the operating system for which you are ordering the PTF package. You can order these PTF packages individually or as a part of a list. You can order most PTFs as part of a mixed list. A mixed list PTF order can contain operating system fixes, most licensed program fixes, and Licensed Internal Code fixes. Only fixes that begin with the prefix SH are not included in the mixed list. Order these fixes separately. Information APARs are coded with the II prefix and are not considered fixes. You must order those separately. Several methods exist that allow you to order your fixes, such as, voice support, Fax, 1-800 number, Fix Central, and SNDPTFORD command. More details are provided for Fix Central and the SNDPTFORD command. You can find more information about the other methods from Ordering PTFs for your iSeries family system Web site. Order fixes using the Internet Fix Central from IBM(R) allows you to select, order, and download PTFs over the Internet. To use this facility, you must have an IBM userid and password. Order fixes using SNDPTFORD If you prefer the command interface, you can use the Send PTF Order (SNDPTFORD) command to order individual fixes, multiple fixes, PTF groups, PTF summary, or cover letters. In some special circumstances, you may want to create your own custom fix package for sending, loading, and applying fixes on servers in your network. Order fixes using the Internet The quickest method to receive PTFs is through the Internet. To receive PTFs from the Internet, connect at least one workstation to the iSeries(TM) server that is set up to use the Internet. Do not wait until an emergency occurs and you need to request a PTF quickly, only to find you need to register and set up this function. Be prepared: register, set up, and request a PTF to test the process. IBM(R) offers many ways for you to download or order PTFs for your iSeries server or AS/400(R) system. The various methods are listed here, but you should go to the Fix Central Web site for details. For information on the Send PTF Order command, see Order fixes using the OS/400(TM) command SNDPTFORD. Order fixes using the SNDPTFORD command The Send PTF Order (SNDPTFORD) command is used primarily to order and receive IBM(R)-supplied fixes (or Program Temporary Fixes, PTFs) for the iSeries server and IBM-supplied applications. You can use this command over the electronic customer support configuration that uses either an SNA connection or TCP/IP connectivity through universal connection. Note: To use universal connection, the Remote control point parameter must be set to *IBMSRV. To learn more about the Universal Connection, see Universal Connection. Fixes and information you can order with the SNDPTFORD command You can use the SNDPTFORD command to order a variety of fixes and related information. The table below shows how to use the SNDPTFORD command to order the different types of fixes and fix information. You may want to print and use this table as a reference when you order fixes. • Separate or accompanying cover letters • Individual fixes • Multiple fixes • Cumulative PTF packages • PTF groups • PTF Summary • Cross-reference summary list • Preventive service planning tips Fix Information Command Specific fixes and cover letters SNDPTFORD nnnnnnn1 Fix cover letter only SNDPTFORD nnnnnnn1 PTFPART(*CVRLTR) Cumulative PTF packages SNDPTFORD SF99vrm2 PTF group SNDPTFORD SF99nnn3 PTF summary list SNDPTFORD SF97vrm2 Fix cross-reference summary list Operating System VRM510 to VRM520 Operating System VRM510 to VRM530 Operating System VRM520 to VRM530 Licensed Internal Code V5R3M0 to Licensed Internal Code V5R3M54 - SNDPTFORD SF97071 SNDPTFORD SF97072 SNDPTFORD SF97081 SNDPTFORD SF9706 PSP information for licensed programs SNDPTFORD SF98vrm2 PSP information for Licensed Internal Code and hardware devices SNDPTFORD MF98vrm2 Notes: 1nnnnnnn is the fix identifier. You can order up to 20 fixes at a time. 2v is the version, r is the release, and m is the modification level of the OS/400(R)operating system (5722SS1) . For Version 5 Release 3 Modification 0, type 530. 3nnn is the fix identifier, which can be any number. 4This fix cross-reference summary lists contains only PTFs for Licensed Internal Code. For operating system and Licensed product PTFs, you should refer to the operating system cross-reference summary list that corresponds to the release of your operating system. Using the SNDPTFORD command When you use the SNDPTFORD command, the following process takes place: 1. From the iSeries server command interface, enter the SNDPTFORD nnnnnnn command, where nnnnnnn is the number of the individual fix you want to order. If you are using Management Central to manage your fixes, you may want to use the SNDPTFORD command from the system that you will use as your source system when you compare and update fix levels. 2. To process your PTF order in batch, use the Submit Job (SBMJOB) command. For example, you can specify the SNDPTFORD command for the CMD parameter. 3. Your order is then sent to IBM where the decision is made whether to distribute the fixes electronically or on media. If the fix files are too large to be delivered electronically, they are delivered on media. 4. The PTFs are sent electronically or put on media. If the fixes are placed on media, the media is packaged and the order is sent to the user. 5. When you receive fixes electronically on your service support communications line, they are placed in a save file in library QGPL. In most cases, the save file name is the fix identifier prefixed with a Q. For example, the save file for fix identifier SInnnnn is QSInnnnn. To order a cumulative PTF package with the SNDPTFORD command, do the following: 1. Identify your licensed program release level: a. On any command line, type GO LICPGM. b. Press Enter. c. Select option 10 (Display installed licensed programs) on the Work with Licensed Programs display. d. Press F11. The current version, release, and modification level is shown in the Installed Release column where V is the version, R is the release, and M is the modification level. 2. Type SNDPTFORD SF99VRM, where VRM is the version, release, and modification level you found in step 1. For example, for Version 5 Release 3 Modification 0, type SNDPTFORD SF99530. 3. Verify the shipping information on the Verify Contact Information display. If any of the information is incorrect, change it and press Enter. 4. Select option 1 (Send service request now) on the Select Reporting Option display. This places the fix order. Specifying media for shipping a fix You can specify the media for any fixes that will be shipped instead of delivered electronically by doing the following: 1. On any command line, type WRKCNTINF. 2. Press Enter. The Work with Support Contact Information display appears. 3. Select Option 2. 4. Press Enter. The Work with Local Service Information display appears. 5. Select Option 2. 6. Press Enter. The Change service contact information display appears. 7. Page down to the next display. 8. Specify the fix medium type by entering the corresponding number. 9. Press Enter. The WRKCNTINF command is used in conjunction with the DELIVERY parameter on the SNDPTFORD command. If you specify DELIVERY(*ANY), fixes are sent by any available method. If you specify DELIVERY(*LINKONLY), you may not receive your order if the size of your fixes exceeds the transmit limit of the service link. Additional considerations Keep the following points in mind when using the SNDPTFORD command: • When you order a fix that has been replaced (superseded) with another fix, you receive the ordered fix, not the replacement fix. To identify fixes that have been replaced (superseded), consult the fix summary list. • When you order a fix for a product that is installed on your system, you will receive a fix package that contains the ordered fix and its requisites. • If you order a fix for a product that is not installed on your system, you will receive only the fix that you ordered. If you use the Display Program Temporary fix (DSPPTF) command on the fix you just ordered, you will receive the following message: PTF 5722xxx-SIxxxxx is not found. This message means that the fix is for a release of the product that is not installed on your system. Contact your service provider for the correct fix number. To avoid this situation, you can add support for a product. Install fixes This topic provides an overview of the tasks that you need to perform to ensure you install your fixes successfully. Each of the following tasks describes a specific part of the process for installing fixes. This topic is based on the use of the Install PTF (INSPTF) command or option 8 from the GO PTF menu. Step 1: Review fix cover letters Determine if there are any special instructions that you should be aware of before you install your fixes. Step 2: Prepare your server to install fixes An overview of the preparation tasks that you can perform on your servers to ensure a successful install, which includes determining if there are any special instructions. Step 3: Choose your installation scenario Find key considerations and tasks for unique fix installation scenarios, including local systems, remote systems, and systems with logical partitions. You can install many kinds of fixes including cumulative PTF packages, HIPER fixes, OS/400(R) and other licensed program fixes, and fixes for the iSeries(TM) Licensed Internal Code. Step 4: Verify installation After you have installed your fixes, you should verify that the install was successful. Advanced procedures for fix installation Find information that relates to loading and applying PTFs. You will also learn how to create your own fix package from CD-ROM and how to create a fix package to a virtual image. Step 1: Review fix cover letters prior to fix installation You should always review your cover letters to determine if there are any special instructions. If you are installing a cumulative PTF package, you should read the instructions that come with that package. If it is not a cumulative package, you should display and print your fix cover letters because they can contain special instructions. If you read your cover letters, you can avoid problems that could result in time-consuming recovery. If there are any pre-installation special instructions in any of the cover letters, follow those instructions first. Your next step Step 2: Prepare your server to install fixes Determine how to install your fixes. Some fixes can be applied without requiring an IPL. There fixes are called immediate fixes. Some fixes can be applied only during an IPL. These are called delayed fixes. Immediate fixes can also be applied during an IPL. You need to determine if you are installing any delayed fixes and when it is convenient for you to IPL your system to apply the fixes. The cover letter tells you if the fix is immediate or delayed. Before you begin to install fixes, complete these tasks: • Have a current backup of your user data, operating system, and licensed programs. If you have backed up the operating system and licensed programs since the last time you applied fixes, that backup is acceptable. • Have all users sign off the system only if you are doing an IPL when you install the fix. • For 8xx models, before applying a fix to the primary partition of a system with logical partitions, power down the secondary partitions. See install fixes on systems with logical partitions for further information. For eServer(TM) 5xx models, see the eServer troubleshooting and hardware service information and the install fixes from a server managed by the HMC topics. • Be sure you have security officer (*SECOFR) user class authority. You need it to do the rest of the install steps. • Verify that your system is running on the B storage area. See the Determine the storage area topic for more information. Your server maintains two copies of all Licensed Internal Code: a permanent copy and a temporary copy. Read this topic to learn about the available storage areas. Your next step Step 3: Choose your fix installation scenario You can install fixes in many ways. Some factors that influence the method you choose include your environment (logical partitions), how you received your fixes (electronically or on media), or the type of device that you want to use (image catalog). If you want information on advanced install topics, see applying PTFs or loading PTFs. The topics that follow provide information for the different ways that you can install fixes. Install cumulative PTF package Find out how to use the GO PTF menu to install a cumulative PTF package. You can also omit fixes when you install a cumulative PTF package. Install fixes received electronically Find out how to use Management Central or the GO PTF menu to install the fixes that you received electronically. Install fixes from media Find out how to use Management Central or the GO PTF menu to install the fixes that you received on media. Distribute fixes to multiple servers If you have a network of iSeries(TM) servers that you want to keep at the same fix level, find out how simple your servers are to manage when you use the Compare and Update wizard. Find out how to install your fixes on remote systems with iSeries Navigator. Install fixes on systems with logical partitions Even though the basic steps of installing a fix on a system with logical partitions are the same as on a system without logical partitions, there are some items that you need to be aware of before you begin to install your fixes. This topic provides information for your 8xx models. For information regarding eServer(TM) 5xx models, see the eServer troubleshooting and hardware service information and the install fixes from a server managed by the HMC topics. Install fixes from a server managed by Hardware Management Console Find out how to install OS/400(R) fixes when your system is managed by the the Hardware Management Console. For information regarding iSeries 8xx models, see the install fixes on systems with logical partitions. Install fixes from an image catalog Find out how to use an image catalog to install your fixes. Install cumulative PTF packages This topic describes the steps for installing a cumulative PTF package. You should order and install the current cumulative PTF package to keep your server at the most current fix level. You should do this on a periodic basis according to your fix maintenance strategy or when you install a new release of a licensed program. Notes: 1. The cumulative PTF package automatically includes the most recent Database PTF group and HIPER PTF group. 2. In an effort to simplify the process for installing a cumulative PTF package, some special instructions may be automated during installation when possible. However, you should continue to thoroughly read the cumulative PTF package installation instructions. It is important that you read the fix shipping information letter thoroughly. The letter provides any special instructions that you should be aware of before you install your cumulative PTF package. The steps that follow step 1 are part of the letter also; they are provided here as an overview of some of the steps you need to do. To install cumulative PTF packages: 1. Read the fix shipping information letter thoroughly and follow the instructions contained in it. 2. Select the storage area if you have not already done so. You should be running on the B storage area (B side) when installing the cumulative PTF packages. 3. Type GO PTF from any command line. 4. Type option 8 (Install program temporary fix package) and press Enter. The Install Options for Program Temporary Fixes display is shown. o Type optyy, where yy is the name of the CD-ROM drive unit (for example, opt01) where you loaded the fix CD-ROM. o If you want to automatically IPL your system after loading the fixes, type a Y (Yes) in the Automatic IPL field. o If you have additional fixes to install at this time, type a 2 (Multiple PTF volume sets) in the Prompt for media field, and install the additional fixes. o Type Y for Other options. The Other Install Options display is shown. o Type 1 for Apply Type. o Type 1 for the PTF type. Note: To prevent someone from unintentionally performing an IPL on your system when using the GO PTF option 7 or option 8, use the Change Server Attributes (CHGSRVA) command. Specify *DLYALL for the PTFINSTYPE parameter to override the Automatic IPL field and the Apply type field on the GO PTF option 7 and option 8. Omitting individual fixes when you install a cumulative PTF package The omit function allows you to specify individual fixes that you do not want to install from the cumulative package. A situation could exist where you received the latest cumulative package from IBM(R), and the Preventive Service Planning (PSP) information indicates that the package contains two defective PTFs. In this situation you do not want to install the defective PTFs. To omit any PTFs, do the following: 1. Type GO PTF from any command line. 2. Type option 8 (Install Program Temporary Fix package) and press Enter. 3. On the Install Options for Program Temporary Fixes display, specify Y for the Other options field, and press Enter. The Other Install Options display is shown. 4. Specify Y for the Omit PTFs field, and a value for the Apply Type field, and then press Enter. The Omit Program Temporary Fixes display is shown. 5. In the Opt Column, type a 1 next to each product and release for which you want to omit specific fixes from being installed, and press Enter. The PTFs to Omit display is shown for each product that was selected on the previous display. This display shows the list of fixes that are to be omitted from being loaded for the specified product and release. 6. To add fixes to the list on the PTFs to Omit display, type a 1 on the first line of the Opt column and specify the fix ID in the PTF ID column. Press Enter. 7. Repeat step 6 until you have specified all of the fixes you want to omit from being installed for the product and release. Press Enter again and repeat the procedure for the next product and release you selected on the Omit Program Temporary Fixes display. When you are done with the last product and release you have selected, the Omit Program Temporary Fixes display is shown again. The > symbol next to the product and release indicates that you have specified fixes to be omitted. Press Enter. The Confirm to Omit PTFs display is shown. 8. The Confirm to Omit PTFs display lists each of the fixes that have been specified to be omitted from being installed. If the list is correct, press Enter. Normal fix installation process continues from this point. Remember, you can install fixes using the power on and power off schedules. Your next step Install fixes received electronically Fixes are either sent to your server over the electronic customer support service link or received on distribution media such as CD-ROM, depending on the size and number of fixes that you ordered. If they are sent over the electronic customer support service link, you receive them as save files, and they are stored in library QGPL. You can use either Management Central or the GO PTF menu to install fixes that you received electronically. Note: If you receive fixes by any other method, you can use the Log Program Temporary Fix Information (QPZLOGFX) API to log the fix information. The fix information must be logged to install the fix or distribute it to remote systems. Remember, because Management Central uses inventory for many of its tasks, the inventory will become out of date after actions are performed on endpoint systems that change the state of an item in the inventory. That is why you should ensure that your inventory is current before you perform the install fixes task with Management Central. Install fixes with Management Central 1. In iSeries(TM) Navigator, expand Management Central. 2. Expand Endpoint Systems or System Groups. 3. Expand Configuration and Service. 4. Expand Fixes Inventory. 5. Select All Fixes, Fix Groups, or a specific product to choose which fix or fix group you want to install. The status of the fix or fix group must be Available, which means that the fix is ready to install. Install fixes with GO PTF menu 1. Type GO PTF from any command line. 2. Select option 8 (Install program temporary fix package) on the Program Temporary Fix (PTF) display. The Install Options for Program Temporary Fixes display is shown. o Type *SERVICE for the device. o If you do not want to install certain fixes, you can omit them by using the procedure identified in the Installing cumulative PTF packages topic. Notes when using the GO PTF menu: • You must be running on the B storage area to use any temporarily applied Licensed Internal Code fixes. Temporarily applied Licensed Internal Code fixes can be applied permanently (copied to the A storage area). To permanently apply delayed or immediate Licensed Internal Code fixes, you must be running from the B storage area. These fixes can be permanently applied without an IPL. • When running on the A storage area, the system will automatically apply the Licensed Internal Code fixes immediately. For Licensed Internal Code fixes that will be applied immediately without an IPL, you can find more information in the Applying fixes topic. • For immediate OS/400(R) fixes that will be applied immediately without an IPL (initial program load), see the instructions in Applying Immediate Licensed Program or OS/400 PTFs Temporarily or Permanently without an IPL. • To prevent someone from unintentionally performing an IPL on your system when using the GO PTF option 7 or option 8, use the Change Server Attributes (CHGSRVA) command. Specify *DLYALL for the PTFINSTYPE parameter to override the Automatic IPL field and the Apply type field on the GO PTF option 7 and option 8. Your next step Install fixes from media Fixes are either sent to your server over the electronic customer support service link or received on distribution media such as CD-ROM, depending on the size and number of fixes that you ordered. If they are sent over the electronic customer support service link, you receive them as save files, and they are stored in library QGPL. If the fixes are received on media and you want to distribute the fixes, you need to use the iSeries(TM)Navigator Copy from Media function to transfer the fixes into save files and store them in library QGPL. When you receive the fixes and transfer them to save files in library QGPL with the Copy from Media function, all the fix identification information and problem symptom data is stored in the PTF database. Note: If you receive fixes by any other method, you can use the Log Program Temporary Fix Information (QPZLOGFX) API to log the fix information. The fix information must be logged to install the fix or distribute it to remote systems. Install fixes with Management Central 1. In iSeries Navigator, expand Management Central. 2. Expand Endpoint Systems or System Groups. 3. Expand Configuration and Service. 4. Expand Fixes Inventory. 5. Select All Fixes or a specific product to choose which fix's save file you want to copy from media. The Copy from Media dialog allows you to copy the save file for a fix from a tape or optical device onto the system. Fix groups are automatically copied from media when you select All products or All supported products for Fixes to copy. 6. Collect your fixes inventory again. 7. Select All Fixes, Fix Groups, or a specific product to choose which fix or fix group you want to install. The status of the fix or fix group must be Available, which means that the fix is ready to install. You can install the fixes if the corresponding products are installed on the system. Install fixes with GO PTF menu 1. Type GO PTF from any command line. 2. Type option 8 (Install program temporary fix package) and press Enter. The Install Options for Program Temporary Fixes display is shown. o Type optyy, where yy is the name of the CD-ROM drive unit (for example, opt01) where you loaded the fix CD-ROM. o If you do not want to install certain fixes, you can omit them by using the procedure identified in the Installing cumulative PTF packages topic. Notes when using the GO PTF menu: • You must be running on the B storage area to use any temporarily applied Licensed Internal Code fixes. Temporarily applied Licensed Internal Code fixes can be applied permanently (copied to the A storage area). To permanently apply delayed or immediate Licensed Internal Code fixes, you must be running from the B storage area. These fixes can be permanently applied without an IPL. • When running on the A storage area, the system will automatically apply the Licensed Internal Code fixes immediately. For Licensed Internal Code fixes that will be applied immediately without an IPL, you can find more information in the Applying fixes topic. • For immediate OS/400(R) fixes that will be applied immediately without an IPL (initial program load), see the instructions in Applying Immediate Licensed Program or OS/400 PTFs Temporarily or Permanently without an IPL. • To prevent someone from unintentionally performing an IPL on your system when using the GO PTF option 7 or option 8, use the Change Server Attributes (CHGSRVA) command. Specify *DLYALL for the PTFINSTYPE parameter to override the Automatic IPL field and the Apply type field on the GO PTF option 7 and option 8. Your next step Distribute fixes to multiple servers with iSeries Navigator After you have received your fixes, you can use iSeries Navigator to distribute your fixes to other servers in your network. In the past, object distribution and Systems Network Architecture distribution services (SNADS) were the choices when you wanted to send objects. If you are in a TCP/IP environment, you can now use the iSeries Navigator's graphical interface function of Management Central to send and distribute your fixes. To understand how a network is set up, see the following list for a description of the different roles. A single system can assume more than one role. For example, the same system can be the central system, the source system, and a model system. Central system Central system directs and tracks activity in your environment. It has an active iSeries Access connection from your graphical client, and it is currently selected as the central system. Its server and inventory provide your view of the Management Central tasks and endpoints. Endpoint systems Endpoint systems are the systems that you are managing in your environment. The endpoint systems are controlled by the central system. The endpoint systems were discovered or created on your central system. Source system This is the system from which items are sent when performing a task. The source system is the source of the item that is sent. This is the system that you have selected to be the repository for the save files for the fixes that you will distribute to your other servers. Target system This is the system to which items are sent when performing a task. The target system is the destination of the item that is sent. Model system This is the system that is set up exactly the way you want it with regard to installed fixes. It has the fixes installed that you decided should be installed. You want the other systems that you are managing to have the same fixes installed as the model system. When you use the Compare and Update wizard, you make managing your fixes a lot easier. You can distribute fixes to remote systems with the following methods: Send and install fixes Use iSeries Navigator to send your fixes to remote systems and install them. Compare and update fixes Use iSeries Navigator to compare fixes across your systems or networks of systems. You then have the choice to update your systems with the missing fixes. Find out how the Compare and Update wizard works. Install fixes on systems with logical partitions For 8xx models, the basic steps of installing a fix or PTF are the same on a system with logical partitions as on a system without logical partitions. For information regarding 5xx models, see the eServer(TM) troubleshooting and hardware service information. However, you should take the following precautions: • When you load fixes to a primary partition, power down all secondary partitions before you restart the primary partition. • When you use the GO PTF command on the primary partition, change the automatic IPL parameter from the default (*YES) to (*NO). You do not have to do this if you first power down the secondary partitions. Installing partition-sensitive fixes There are certain partition-sensitive fixes that apply specifically to the lowest level code that controls logical partitions. Partition specific fixes will have special instructions referring to how to apply these fixes to your server. Attention: Failure to follow these steps exactly could result in a lengthy recovery process. For partition-sensitive fixes you should follow these steps exactly: 1. Permanently apply any fixes superseded by the new fixes. 2. Perform an initial program load (IPL) of all partitions from source A. 3. Load the fixes on all logical partitions with the Load PTF (LODPTF) command. Do not use the GO PTF command. 4. Apply the fixes temporarily on all logical partitions with the Apply PTF (APYPTF) command. 5. Power down all secondary partitions. 6. Perform a power down and IPL of the primary partition from source B in normal mode. 7. Perform normal mode IPLs of all secondary partitions from source B. 8. Apply all of the fixes permanently with the APYPTF command. If you want information on advanced install topics, see applying PTFs or loading PTFs Install fixes on systems managed by Hardware Management Console As the system administrator or system operator who manages the software level on your systems or partitions, you have two choices for performing this task for systems that are managed by the Hardware Management Console (HMC): • You control the software level of the hypervisor through the i5/OS(TM) service partition. This method requires a server IPL for the updates to take effect. A server IPL requires you to power down all the partitions at the same time. • You allow the HMC to control the level of the hypervisor. On systems that have an HMC attached, this is the default action. This method requires you to install fixes by using the HMC. With this method, the i5/OS service partition is disabled from applying updates to the hypervisor. When the DSPPTF display for licensed product 5722999 is shown, message CPD35FA is displayed. This message indicates that updates are not allowed from the i5/OS service partition, and the hypervisor that is currently active is at a different level than the hypervisor partition of the Licensed Internal Code that is installed on the system. To allow updates through HMC only, see the eServer(TM) troubleshooting and hardware service information. You can perform a server IPL from two different sources, the T side or the P side. The T side is considered the temporary side, which is the equivalent of the B IPL source on the iSeries(TM) server. The P side is considered the permanent side, which is the equivalent of the A IPL source on the iSeries server. These IPL sources do not have to synchronized. Normally, the service partition is running on the B IPL source, and the code for the hypervisor is running from the T side. The DSPPTF command shows the copy of the hypervisor that was used on the previous server IPL in the IPL source header field (##SERV#T or ##SERV#P). When fixes are applied to or removed from the hypervisor portion of the Licensed Internal Code, a message is sent that indicates if any of the PTFs require a server IPL. You can use the DSPPTF command to determine which PTFs require a server IPL to activate the changes. The Server IPL required field is set to None; ##SERV#T or ##SERV#P indicates which IPL source to use when performing the server IPL. It is not sufficient to perform an IPL on only the service partition to activate the code; you must power down all the partitions at the same time. Install fixes from an image catalog This topic discusses how you can use an image catalog to install PTFs that you receive on physical media or that you received using FTP when you downloaded fixes from Fix Central. Notes: 1. You cannot install PTFs directly from an image catalog with Management Central, but you can use the Copy from Media function to copy PTFs into save files from an image catalog associated with a virtual optical device. 2. Your user profile must have *ALLOBJ and *SECADM authority to use the image catalog commands. To install your fixes from an image catalog, do the following steps: 1. Create a virtual optical device It is possible that you used an image catalog that is associated with a virtual optical device to perform a software upgrade. If you did, you do not have to perform this step. If you do not have a virtual optical device, you must create one. o To create a device description, type the following on any command line: CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(*VRT) ONLINE(*YES) TEXT(text-description) o To determine whether or not a virtual optical device exists, type the following: WRKDEVD DEVD(*OPT) A virtual optical device is indicated by a device type of 632B. To ensure that the device is active, press F14 (Work with configuration status). If the device is not active, type 1 to vary it on. You can have only one virtual optical device active at a time. 2. Create an image catalog Create an image catalog for the set of PTFs that you want to install. The Create Image Catalog (CRTIMGCLG) command associates an image catalog with a target directory where the pre-loaded images are loaded. CRTIMGCLG IMGCLG(ptfcatalog) DIR('/MYCATALOGDIRECTORY') CRTDIR(*YES) TEXT(text-description) Note: A directory can be associated with only one image catalog. 3. Add an image catalog entry You can add an image catalog entry for each physical media that you have. You can also add an image catalog entry for fixes that you received using FTP, for example, you downloaded fixes from Fix Central. o Add an image catalog entry for each physical media that you have. You need to repeat this step for each volume of media. You should add the images in the same order as if you were going to install from them. ADDIMGCLGE IMGCLG(ptfcatalog) FROMDEV(OPT01) TEXT(text-description) o Add an image catalog entry for fixes that you downloaded from Fix Central into an IFS directory. You can add the directory into an image catalog in either of the following ways:  Into the same directory that is associated with the image catalog directory.  ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE(iptfxxx_x.bin) TOFILE(iptfxxx_x.bin)  Into a different directory.  ADDIMGCLGE IMGCLG(PTFCATALOG)  FROMFILE('/differentdirectory/iptfxxxx_x.bin') TOFILE(iptfxxx_x.bin) 4. Load the image catalog This step associates the virtual optical device to the image catalog. Only one image catalog can be associated with a specific virtual optical device. Type the following command to load the image catalog: LODIMGCLG IMGCLG(ptfcatalog) DEV(OPTVRT01) OPTION(*LOAD) 5. Verify that the images are in the correct order VFYIMGCLG IMGCLG(ptfcatalog) TYPE(*PTF) SORT(*YES) The system puts the images in the correct order. By default, the volume with the lowest index is mounted; all the other volumes are loaded. Use the Work with Catalog Entries (WRKIMGCLGE) command to see the order of the images. Note: If you are attempting to load individual PTFs with the Load PTF (LODPTF) command, only the PTFs on the volume set that is mounted can be loaded. 6. Install PTFs from virtual optical device To install PTFs from an image catalog associated with a virtual optical device, see Install fixes from media or Install cumulative PTF package. For the device name, enter the name of the virtual optical device that is associated with your image catalog. All the PTFs from the images that are either mounted or loaded will be installed. 7. Delete images from image catalog Once you have successfully installed the fixes, you should remove the images from the catalog with the Remove Image Catalog Entries (RMVIMGCLGE) command. If you continue to add new images to the same image catalog without removing the old images, PTF install processing will attempt to install the fixes from from all of the loaded images in the catalog Step 4: Verify fix installation You should develop the habit of verifying whether or not you were successful in installing your fixes. In general, if your fixes did not install, you need to determine whether the failure occurred during the load or apply phase of the install. If the system did not IPL, then possibly the failure occurred during the load phase. Press Help on the failure message, and then press F10 (Display messages in the job log). Look for all escape messages that might identify what the problem is. You should fix these errors, and then try your request again. If the system did IPL, but the PTFs did not apply, look at the history log. 1. Type GO LICPGM from any command line. 2. Type option 50 (Display log for messages). 3. Look for any messages that indicate any PTF activity during the previous IPL. Normal PTF processing occurs only during an unattended IPL (initial program load) that immediately follows a normal system end. If you did not specify Y for Perform Automatic IPL on the Install Options for PTFs display, verify that the Power Down System (PWRDWNSYS) command was run with RESTART(*YES) and that the key lock position was at normal. If an abnormal IPL occurs, some Licensed Internal Code fixes might be installed, but no other operating system or licensed program PTFs are applied. You can look at the previous end of system status system value (QABNORMSW) to view whether the previous end of system was normal or abnormal. 4. Look for any messages that indicate that there was a failure during the IPL or that indicate that a server IPL is required. If you find any failure messages, do the following: a. Go to the start-control-program-function (SCPF) job log (WRKJOB SCPF). b. If you performed an IPL, choose the first job that's not active and look at the spooled file for that job. c. Find the error messages, and determine what caused the error d. Fix the errors and re-IPL the system to apply the rest of the PTFs. Additionally, you can do the following to verify that your fixes have been installed correctly: 1. On any command line, type GO LICPGM and press Enter. The Work with Licensed Programs display appears. 2. Select Option 50 (Display log for messages). The Display Install History display appears. 3. Fill in the start date and start time on the Display Install History display and press Enter. The messages about fix installation are shown. If the fixes were installed successfully, you see messages like the following: PTF installation process started. Loading of PTFs completed successfully. Marking of PTFs for delayed application started. Marking of PTFs for delayed application completed successfully. Apply PTF started. Applying of PTFs for product 5722xxx completed successfully. Applying of PTFs for product 5722xxx completed successfully. Applying of PTFs for product 5722xxx completed successfully. . . . Applying of PTFs completed. If the PTFs were installed successfully, but require a server IPL to activate the changes, you see messages like the following: PTF installation process started. PTFs installed successfully, but actions pending. Server IPL required. You must perform a server IPL to activate the changes to the hypervisor. Use the DSPPTF SELECT(*ACTRQD) command to determine which PTFs require a server IPL and which IPL source (##SERV#T or ##SERV#P) to use when performing the server IPL. See Install fixes on systems managed by Hardware Management Console for information on performing a server IPL. If the cumulative PTF package was not installed successfully, you see error messages like the following: PTF installation process started. Loading of PTFs failed. Marking of PTFs for delayed application started. Marking of PTFs for delayed application failed. Apply PTF started. . . . Applying of PTFs failed for product 5722xxx. . . . Applying PTFs failed. Your next step Advanced fix installation procedures This topic introduces the advanced topics of loading and applying PTFs and creating your own fix package. In general, you should use option 8 from the Go PTF menu to install your fixes. Option 8 loads and applies fixes in one step. However, you can encounter some situations where you need to perform the separate steps of loading and then applying fixes. In addition to these two topics, you will learn how to customize a PTF package from CD-ROM and how to customize a PTF package to a virtual image. Build a custom fix package Find out how to create your own fix package that can be used in the same way as a fix package that is supplied by IBM(R) service support. Build virtual image fix packages Find out how to create how you can create your own virtual image for fix packages that you want to install at a later time. Load fixes Find out how to load one, some, or all of your fixes with the Load Program Temporary Fix (LODPTF) command. Apply fixes Find out how to apply one, some, or all of your fixes with the Apply Program Temporary Fix (APYPTF) command. Advanced fix installation: Build a custom fix package You can encounter situations where you, as the service provider, do not want to distribute the same fixes to your service requesters. In those situations, you will want to build your own fix package from CD-ROM that can be used the same way as a fix package supplied by IBM(R) service support. This example combines a fix package with individual fixes into a custom fix package for distribution to other iSeries servers in your network. Note: If you build a custom fix package and save it to virtual optical media, you cannot span virtual volumes. Your custom fix package must fit on one volume. The order of a cumulative PTF package is: • High-impact pervasive (HIPER) Licensed Internal Code fixes • HIPER OS/400(R) fixes • HIPER licensed program fixes • A delimiter that divides the HIPER fixes from the non-HIPER fixes • Non-HIPER Licensed Internal Code fixes • Non-HIPER OS/400 fixes • OS/400 Online information fixes, if any • Non-HIPER licensed program fixes Customizing a PTF package from CD-ROM For the following example, assume that you want a tape that contains all but one (SF00600) of the PTFs from the most recent PTF package received from IBM service support, including the HIPER PTFs. In addition, you want to include four individual PTFs received electronically from service support. These PTFs are MF00050, SF00480, SF00500, and SF00800. Because the four individual PTFs were received from IBM service support, they already exist in save files in library QGPL. They exist in the library as object type *file, as shown below: • QMF00050: *FILE • QSF00480: *FILE • QSF00500: *FILE • QSF00800: *FILE 1. Find out the path identifier for the fix file you want to copy from the cumulative PTF package: Note: A path identifier is a 1 to 6-digit number that identifies each fix file on the CD-ROM. Each release of a licensed product on the CD-ROM has its own unique set of identifiers. Each set of path identifiers for the product begins with the number 1 indicating the first fix file for the product and release. This first fix file may or may not contain HIPER fixes for the product. To get the path identifier for each fix file you want to copy from the cumulative PTF package for your product, use the Copy Program Temporary Fix (CPYPTF) command, and specify PATHID(*SELECT). The Select PTF CD-ROM File display is shown. Select PTF CD-ROM File display +--------------------------------------------------------------------------------+ | Select PTF CD-ROM File | | System: SYSNAMXX | |Product . . . . . . . . : 5722SS1 | | | |Type option, press Enter. | |1=Select | | | | National | | Feature Language Path Hiper | |Opt Release Type Version Identifier PTFs | | V5R3M0 *CODE 1 Yes | | V5R3M0 *CODE 2 No | | V5R3M0 *LNG 2924 2 No | +--------------------------------------------------------------------------------+ 2. Use the CPYPTF command to bring the HIPER fixes from the cumulative PTF package into library QGPL. Two licensed programs are being used in this example (MF and SF PTFs). You can identify the HIPER fix files on the Select PTF CD-ROM File display by a Yes in the Hiper PTFs column. 3. CPYPTF LICPGM(5722999) 4. FROMDEV(OPT01) 5. TODEV(*SAVF) 6. FROMPATHID(1) 7. TOSAVF(QGPL/PCUMH999) 8. 9. CPYPTF LICPGM(5722SS1) 10. FROMDEV(OPT01) 11. TODEV(*SAVF) 12. FROMPATHID(1) 13. TOSAVF(QGPL/PCUMHSS1) 14. Copy the product delimiter into a save file. 15. CPYPTF LICPGM(5722111) 16. FROMDEV(OPT01) 17. TODEV(*SAVF) 18. SELECT(*ALL) 19. FROMPATHID(1) 20. TOSAVF(QGPL/PCUMH111) 21. Copy the non-HIPER fixes from the cumulative package into a save file omitting the unwanted fixes. 22. CPYPTF LICPGM(5722999) 23. FROMDEV(OPT01) 24. TODEV(*SAVF) 25. FROMPATHID(2) 26. TOSAVF(QGPL/PCUMP999) 27. 28. CPYPTF LICPGM(5722SS1) 29. FROMDEV(OPT01) 30. TODEV(*SAVF) 31. OMIT(SF00600) 32. FROMPATHID(2) 33. TOSAVF(QGPL/PCUMPSS1) Creating the custom package Repeat the command for each licensed program with non-HIPER fixes. The OMIT parameter was used to identify the fix not included in the tailored package. The TOSAVF name must be 8 characters in length and must start with the letter P. You can choose the remaining seven characters. The library on the TOSAVF parameter must be QGPL. Library QGPL now contains: File Name Object Type QMF00050 *FILE QSF00480 *FILE QSF00500 *FILE QSF00800 *FILE PCUMH999 *FILE PCUMHSS1 *FILE (plus more for HIPERs of licensed programs) PCUMH111 *FILE PCUMH999 *FILE PCUMPSS1 *FILE (plus more for non-HIPERs of licensed programs) 1. Initialize the tape for the tailored cumulative package. 2. INZTAP DEV(TAP01) 3. NEWVOL(CUMPKG) 4. Copy the Licensed Internal Code HIPER fixes into one file and place it first on the tape. 5. CPYPTF LICPGM(5722999) 6. FROMDEV(*SERVICE) 7. TODEV(TAP01) 8. SELECT(CUMH999) 9. TOENDOPT(*LEAVE) The TOENDOPT(*LEAVE) parameter is used to maintain the tape position. 10. Copy the OS/400 HIPER fixes onto the CD-ROM. 11. CPYPTF LICPGM(5722SS1) 12. FROMDEV(*SERVICE) 13. TODEV(TAP01) 14. SELECT(CUMHSS1) 15. TOENDOPT(*LEAVE) Repeat for each licensed program with HIPER fixes. 16. Copy the delimiter to the tape. 17. CPYPTF LICPGM(5722111) 18. FROMDEV(*SERVICE) 19. TODEV(TAP01) 20. SELECT(CUMH111) 21. TOENDOPT(*LEAVE) 22. Copy the non-HIPER Licensed Internal Code fixes into one file and place on the tape. 23. CPYPTF LICPGM(5722999) 24. FROMDEV(*SERVICE) 25. TODEV(TAP01) 26. SELECT(CUMP999 MF00050) 27. TOENDOPT(*LEAVE) 28. Copy the non-HIPER OS/400 fixes into one file and place on the tape. 29. CPYPTF LICPGM(5722SS1) 30. FROMDEV(*SERVICE) 31. TODEV(TAP01) 32. SELECT(CUMPSS1 SF00480 SF00500 SF00800) 33. TOENDOPT(*LEAVE) Repeat for each licensed program with non-HIPER fixes. The tape now contains the tailored fix package. It can be used in the same way that your service support fix packages are used. Fixes can now be loaded on, applied to, or removed from a system. Advanced fix installation: Build virtual image fix packages This topic discusses how you can create your own virtual image for fix packages that you want to install at a later time. Notes: 1. You cannot install PTFs from an image catalog with Management Central, but you can use the Copy from Media function to copy PTFs into save files from an image catalog associated with a virtual optical device. 2. Your user profile must have *ALLOBJ and *SECADM authority to use the image catalog commands. 3. If you do not have a virtual optical device, you must create one. See Install fixes from an image catalog to create one. 4. If you build a custom fix package and save it to virtual optical media, you cannot span virtual volumes. Your custom fix package must fit on one volume. To create your own virtual image in an image catalog, do the following steps: 1. Create an image catalog Create an image catalog for the set of PTFs that you want to install. The Create Image Catalog (CRTIMGCLG) command associates an image catalog with a target directory where the pre-loaded images are loaded. CRTIMGCLG IMGCLG(ptfcatalog) DIR('/MYCATALOGDIRECTORY') CRTDIR(*YES) TEXT(text-description) Note: A directory can be associated with only one image catalog. 2. Add an image catalog entry Add an image catalog entry for each physical media that you have. You need to repeat this step for each volume of media. You should add the images in the same order as if you were going to install from them. 3. ADDIMGCLGE IMGCLG(ptfcatalog) FROMFILE(*NEW) TOFILE(NEWIMAGEFILE) IMGSIZ(xxxxx) TEXT(text-description) The size of the image should be large enough to contain the size of the fixes that you want to distribute. 4. Load the image catalog This step associates the virtual optical device to the image catalog. Only one image catalog can be associated with a specific virtual optical device. Type the following command to load the image catalog: LODIMGCLG IMGCLG(ptfcatalog) DEV(OPTVRT01) OPTION(*LOAD) 5. Initialize the virtual image 6. INZOPT NEWVOL(MYVOLUMEID) DEV(OPTVRT01) CHECK(*NO) TEXT(MYTEXTDESCRIPTION) The system initializes the virtual image. 7. Copy PTFs to virtual media Copy any PTFs and PTF groups to virtual optical device. You cannot span virtual optical volumes; all PTFs and PTF groups must fit on a single volume. If you exceed the capacity of the volume, either create a new volume or initialize the volume to a larger size. Use the Copy PTF Groups (CPYPTFGRP) command to copy the PTF groups to the media. You can optionally specify CPYPTF(*YES) on the command to copy the PTFs in the group. CPYPTFGRP PTFGRP(xxxxxxx) FROMDEV(*SERVICE) TODEV(OPTVRT01) CPYPTF(*YES) Use the Copy PTF (CPYPTF) command to copy PTFs to the media. Repeat the command for each product that you have. CPYPTF LICPGM(xxxxxxx) FROMDEV(*SERVICE) TODEV(OPTVRT01) SELECT(xxxxxxx) For additional information about optical storage and virtual optical storage on the iSeries(TM) server, see the following topics: Create actual Create actual media from a virtual image Use these instructions to copy a virtual image to an optical disk. Create actual Transport virtual images Use these instructions to move virtual images among different servers. Advanced fix installation: Load fixes Typically, you should use option 8 from the GO PTF menu to install your fixes. However, you can encounter some situations where you need to perform the separate steps of loading and then applying the fixes. The fix packages on CD-ROM or in a save file can contain many fixes. You can load one, some, or all of them using the Load Program Temporary Fix (LODPTF) command. As fixes are loaded, the system verifies that the release of the product is correct. Fix status is not applied after the fix has been loaded on the system. Use the Apply Program Temporary Fix (APYPTF) command to apply the fix. For some of the applied fixes, the status is Temporarily applied - ACN. There are also some temporarily applied fixes that show a status of Temporarily applied - PND. For these fixes, you need additional actions to make them active. Loading individual fixes from a cumulative PTF package To load one fix from a cumulative package, do the following steps: 1. Type LODPTF and press F4 (Prompt). 2. Specify the parameter values according to the fix you are loading. 3. Specify the fix identifier you want to load in the fix numbers to select (SELECT) parameter and press Enter. 4. Repeat LODPTF command for each fix you want loaded from the cumulative package. For fixes on a CD-ROM, the system will automatically find the fix file in the cumulative package that contains the selected individual fixes when you specify PATHID(*FIRST). All fixes to be loaded must exist in the same path identifier. Otherwise, you need to load the fixes separately. For fixes on an image catalog, only the images that are part of the volume set for the image that is mounted are searched. Loading fixes that supersede other fixes If the fix being loaded replaces (supersedes) existing fixes (identified in the fix cover letter) the following considerations apply: • If the fix to be replaced is not applied to the system, the

55 pointsBadges:

ToddN2000 Sep 11, 2017   1:54 PM GMT

You can use the DSPPTF command to see what PTF's are on you system and how they have been applied (Temporarily or Permanently) some may even show superseded. Then you can see the details by using the 5 option.

117,490 pointsBadges:

Gayathri123 Nov 15, 2017   6:30 AM GMT

Hi Salil,

925 pointsBadges:

ToddN2000 Nov 16, 2017   12:39 AM GMT

Also the number of PTF's will vary based on the OS release.

117,490 pointsBadges: