Group PTFs by Release

V5R3M0

V5R4M0

V6R1M0

V7R1M0

CPF3810 during PTF Installation

Some users are seeing message CPF3810 authority error being received during PTF install processing.

Problem

Message CPF3810:

Message . . . . : Save file &1 not restored to library &3. (One of the typical libraries we see in this message is QSRV)

Cause . . . . . : You do not have sufficient authority to restore a save file that does not exist on the system.

Recovery . . . : Do one of the following:

1) Obtain authority to the CRTSAVF command from your security officer and use the RSTOBJ command to restore the save file.

2) Have your security officer restore the save file.

Resolution

To resolve the problem, do the following:

1 Sign in as the actual QSECOFR profile.
2 Verify that QSYS library is at the top of the system library list using the DSPLIBL command. If not, consider temporarily removing the library above QSYS with the following command:
CHGSYSLIBL LIB(xxxxxx) OPTION(*REMOVE)
3 Install the PTFs.
4 If you removed a library from the system library list during Step 2, add the library back in the system library list using the following command:
ADDLIBLE LIB(xxxxxx)

Fix Central Download Order Options

The first part of the download options screen for IBM i, i5/OS, and OS/400 allow the user to change the Order name to something more meaningful and whether to customize the order.

 
 
 
 
 
 
 
 
 
Note: If the option to Customize your order is not selected, the order will contain all PTFs related to the Cumulative, Groups, or individual PTFs selected. See the text beginning with To customize your order... in the Select download options screen above to see what will be removed from the order if customize is selected.

The second half of the screen allows the user to download individual fixes directly to the system, download virtual images using Download Director, download virtual images using FTP, or to order the fixes on media.

 
 
 
 
 
 
 
 
 
 
 
 
 
What will each option do? Download individual fixes directly to my system. Download individual fixes directly to my system. This option will allow the user to download fixes as save files directly down to the system. Selecting this option will lead next to the Download fixes to my system screen. The user will see a status bar noting the progress of the order.

If the order is not needed on the system, the user will get a summary similar to the following:

 
 
 
 

If the order is successful, the Order summary screen will note that the PTFs were successfully downloaded to the system.

Download virtual images using Download Director

This option allows the user to submit an order for virtual images. This will not result in an e-mail. When the order is ready, the user will need to utilize the Resume pending orders option.

After the order is submitted, the summary screen will note an approximate time when the order will be ready. When the order is ready, the user will need to select the Resume my pending orders from the order summary screen or from the panel on the right of the screen. The first section of the order shows Your order is being constructed.

Download virtual images using FTP

This option allows the user to submit an order for virtual images. This will result in two e-mails. The first e-mail will note that the order has been received. The second e-mail will not the link to the FTP site to download the order. The download summary will note Your order will be sent to the FTP server followed by the order details.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Order fixes on physical media (requires Software Maintenance Agreement)

This option takes you directly to the Order Fixes on Media site. If the user has a valid Software Maintenance Agreement with IBM, the option to mail the media rather than download the order can be selected.

If no Software Maintenance Agreement is available, the following screen will come up:

If Software Maintenance is found, the summary screen will note that the order will be mailed.

Note: For more on the download options, click on the appropriate link above.

Registering to Use Fix Central and Other IBM Web Sites

Before a user can access Fix Central and other IBM sites, registration must be completed. This document provides some information to assist users in obtaining a Web ID. If there are any problems with the registration process or with updating the Web ID, once created, please go to the Worldwide IBM Registration Helpdesk
When your registration is complete, this registration is part or all that is needed for access to the following sites:

1. Fix Central
2. Support for IBM System i5 
3. Entitled Software Support  
4. Software Service Request

Follow the steps for registering to have IBM id.
Open Software Service Request Link & Select the Register Now option at the right of any Sign in screen









Select the IBM Service Request option on the next screen to continue with the registration:

On the My IBM registration page, complete the general information that is noted with a red asterisk (*)

Click Continue
Complete the personal and business information that is marked by the red asterisk (*) on this page:

Note: At a minimum, fill in the preferred language, First name, Last name, daytime phone, company name,
Country/Region, Street address, City, State or Providence, and postal code (where appropriate)

Click Submit.

The next screen is a Thank you screen. Select Continue to complete the registration. (This step must be completed.)
Note: If Continue is not selected here, Fix orders will not complete using Fix Central nor will a user be able to submit electronic service requests or PMRs.

The user will be asked to sign in with the newly created user ID.



 
 
 
 
 
 
 
 
 
 
 
 
 

 

On the Request Access page, select the appropriate option and then complete the system information. This information includes the Customer number, Branch number, Machine type, and Machine serial number.

Note: If the customer number is not known, the user must talk to their Business Partner or IBM Marketing Representative.
For IBM System i products functions, only the iSeries profile section must be completed. However, the other sections can be completed if the data exists.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Select to search by Customer number or Serial number and fill in the Justification
 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Step 3 in the request access steps is to verify the platform and IBM profile information:

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Choose to continue to finalize/complete the registration or update the IBM profile. The final screen indicates the registration is complete:

 
 
 
 
 
 
 
 
As indicated in the screen shot above, the registration takes approximately 5 minutes to complete for Fix Central use. However, if using this registration to work with PMRs on line, the wait is longer.

How to Find a PTF Downloaded by ESA

When a WRKPRB entry is reported to IBM using the Electronic Service Agent application, a comparison is made in the APAR database to the symptom string found in the WRKPRB entry. This comparison process can result in ordering and downloading PTFs for the system.
To see what PTFs have been downloaded, issue the WRKPRB command and select option 5 beside the problem log entry to be reviewed. Press F9 to see the PTF list.

PTFs downloaded in this scenario are downloaded as save files to library QGPL. To view the PTFs, issue the WRKOBJ command.

Command examples are as follows:

WRKOBJ OBJ(QGPL/QSI*) OBJTYPE(*FILE)

WRKOBJ OBJ(QGPL/QSF*) OBJTYPE(*FILE)
WRKOBJ OBJ(QGPL/QMF*) OBJTYPE(*FILE)

 There are PTF download size limits for Electronic Customer Service (ECS); this is dependent upon how your ECS is configured.

Installing PTFs from an Image File Ordered through the SNDPTFORD FTP Option

If the default directory was used in SNDPTFORD on the Image Directory parameter, the PTF image(s) will be found in /QIBM/UserData/OS/Service/ECS.

Steps to create another directory, if the default is not wanted (needs to be noted in the SNDPTFORD command, once created).
Steps to create another directory, if the default is not wanted (needs to be noted in the SNDPTFORD command, once created). Steps to create another directory, if the default is not wanted (needs to be noted in the SNDPTFORD command, once created.)
However, if another directory is wanted, the following can be used to create one:
a Open iSeries Navigator.
b Expand My Connections.
c Expand the system.
d Expand File Systems.
e Expand Integrated File System.
f Right-click on the Root and create a new folder called Fixes.
g Right-click on Fixes and select Sharing > New share.
h Select Read/Write Access and click OK.
2 Create a virtual optical device. On the operating system command line, type the following:
CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(*VRT) ONLINE(*YES) TEXT('text-description')
Press the Enter key.
3 Ensure that only one virtual optical device, type 632B, is active. On the operating system command line, type the following:
WRKDEVD DEVD(*OPT)
Press the Enter key and press F14.
4 Create an image catalog. On the operating system command line, type the following:
CRTIMGCLG IMGCLG(ptfcatalog) DIR(/QIBM/UserData/OS/Service/ECS) CRTDIR(*YES) TEXT('text-description')
Press the Enter key.
Notes:
a) A directory can be associated with only one image catalog.
b) ptfcatalog is the example image catalog used in this document. This name can be changed.
5 Add an image catalog entry for fixes that you downloaded from Fix Central into an Integrated File System directory. Add the directory into an image catalog by using one of the following methods:
Method 1: From the same directory that is associated with the image catalog directory, type the following commands:
ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE(SI#####_1.bin) TOFILE(*FROMFILE)
ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE(SI#####_2.bin) TOFILE(*FROMFILE)
and repeat the commands until all image files are added.
Method 2: From a different directory, type the following commands:
ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE('/differentdirectory/SI#####_1.bin') TOFILE(*FROMFILE)
ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE('/differentdirectory/SI#####_2.bin') TOFILE(*FROMFILE)   and repeat until all image files are added.
6 Make the virtual device OPTVRT01 available for use. On the operating system command line, type the following:
WRKCFGSTS CFGTYPE(*DEV)
Press the Enter key. Then select Option 1, Make Available, for OPTVRT01.
7 Load the image catalog. On the operating system command line, type the following:
LODIMGCLG IMGCLG(ptfcatalog) DEV(OPTVRT01) OPTION(*LOAD)
Press the Enter key.
8 Verify the images are in the correct order. On the operating system command line, type the following:
VFYIMGCLG IMGCLG(ptfcatalog) TYPE(*PTF) SORT(*YES)
Press the Enter key.
9 Install the PTFs from the image catalog as you would if you were using a physical CD-ROM. The only difference is that the device you will be applying the PTFs from is OPTVRT01 rather than OPT01.
Note: Use GO PTF Option 1 and 2 or GO PTF Option 8 to install PTFs from this image catalog.
10 Unload the image catalog. On the operating system command line type the following:
LODIMGCLG IMGCLG(ptfcatalog) DEV(OPTVRT01) OPTION(*UNLOAD)
Press the Enter key.
11 Delete the images from the image catalog. On the operating system command line, type the following:
WRKIMGCLGE IMGCLG(ptfcatalog)
Press the Enter key. Select Option 9 to unload the image catalog entry. Then select Option 4 to remove the image catalog entry.
Note: This option will also remove the bin file from the Fixes directory. If you want to keep the files, use the RMVIMGCLGE command.

Locating PTFs Downloaded by SNDPTFORD Command

The DSPJOBLOG command can be used, in this case, to find the SNDPTFORD SF98540 e.g. command last used. The joblog was reviewed to find a message (assuming the SNDPTFORD xxxxxxx command was successful) as follows:

Cover letter has been copied to file QAPZCOVER member QSF98540.

Placing your cursor on the above message in the joblog and pressing F1 will yield the following message description:

Message ID . . . . . . : CPI35F1

 

Message . . . . : Cover letter has been copied to file QAPZCOVER member QSF98540.

 

Cause . . . . . : The cover letter has been copied to file QAPZCOVER in library GPL with member name of QSF98540 from file *N member *N.

 

Recovery . . . : Use the Display Program Temporary Fix (DSPPTF) command to display the cover letter. Specify product 5722SS1, PTF SF98540, release V5R4M0 and request cover letter only.

When using the default parameters for the SNDPTFORD command for PTF ordering, the SAVFs are downloaded by default to QGPL.
Other options would be to use:

1. WRKOBJ OBJ(QGPL/QSI*) OBJTYPE(*FILE)
2. WRKOBJ OBJ(QGPL/QSF*) OBJTYPE(*FILE)
3. WRKOBJ OBJ(QGPL/QMF*) OBJTYPE(*FILE)
4. WRKOBJ OBJ(QGPL/SI*) OBJTYPE(*FILE)
5. WRKOBJ OBJ(QGPL/SF*) OBJTYPE(*FILE)
6. WRKOBJ OBJ(QGPL/MF*) OBJTYPE(*FILE)

A message can usually be identified in the interactive joblog containing similar information about where the PTFs were downloaded after the request was successful.
Note: The PTFs will be found in the IFS, if the *IMAGE format was used, instead of the default *SAVF format.

 

Latest PTFs Index

Requesting PTFs and Cover Letters Using the Internet

Internet access is an alternative connection method between the AS/400 system and the RETAIN system that houses PTF information. On the Internet, users can:

• Browse PTF information

• Request shipment of a CUM package

• Request shipment of selected PTFs

Enabling Internet access over using ECS to request delivery has an advantage for many customers in the U.S. due to the cost, availability of modems, and higher speed transfer. Internet access provides a graphical interface and has the potential for faster access and download of PTF information. This is a result of higher speed modems that are available through some Internet service providers and the possible use of T1 lines. ECS PTF delivery is limited to a SDLC 19.2 kbps synchronous connection. For some customers, ECS remains the preferred method to request PTFs. In other cases where ECS is not available, Internet access provides a faster and more efficient solution than delivery of the PTF information through the “mail.”

Internet delivery does not replace or affect the traditional PTF order process. If you do not have access to the internet, continue using the ECS PTF order function with the SNDPTFORD command. To print cover letters for PTFs for a product installed on your system, enter the command:

DSPPTF LICPGM(57nnxxx) SELECT(yyyyyyy) COVERONLY(*YES) OUTPUT(*PRINT)

In the command, xxx is the licensed program number, and yyyyyyy is the PTF ID. The output can be viewed in the spooled file named QSYSPRT. To print a cover letter of a PTF for a product not installed on your system, enter the following command:

CPYF FROMFILE(QGPL/QAPZCOVER) TOFILE(QGPL/QPRINT) FROMMBR(Qxxxxxxxyy)

In this command, xxxxxxx is the PTF ID, and yy is the language ID. English PTFs do not have a language ID.

Applying CUM Packages

Cumulative packages can be applied at the same time as individual PTFs.
If you receive the individual PTFs on tape, follow these steps:
1. Place the tape containing the individual PTFs in the tape drive.
2. Enter GO PTF and select option 8 (Install program temporary fix package).
3. Specify Automatic IPL N on the Install Options for Program Temporary Fixes display.

If you receive the individual PTFs through ECS, perform these steps:
1. Enter GO PTF and select option 8 (Install program temporary fix package).
2. Specify *SERVICE for the device parameter, and select N for Automatic IPL.

When the GO PTF command is used to install PTFs from *SERVICE, all PTFs in *SERVICE not already installed are installed.
*SERVICE means that the PTF exists in a save file in the QGPL library and that the system checks for these PTFs during the installation process.

Cumulative PTF Package

Not all PTFs produced are included in a cumulative PTF package. The following criteria help determine if a given PTF is incorporated into a subsequent cumulative package:

· The number of customer orders for a particular PTF

· The severity of the associated APAR

· Whether the PTF is designed as HIPER

· Problems that crash a system and require an IPL

· High availability options (mirroring or checksum, for example)

· Problems that require a reinstall or restore

· Save and restore problems that prevent data recovery

· Problems affecting installability of a product or feature

· Problems affecting a product¢s major useability function

· Problems requiring an unnecessary replacement of hardware parts

· Pervasive customer satisfaction problems

· Data integrity and security problems

· If the PTF has a corresponding PTF in a previous release package (to minimize the rediscovery)

PTFs that have special instructions, which might break the system if they are not followed, are not usually incorporated into the cumulative package.

Applying PTFs without an IPL

Beginning in V3R1, PTFs are built to produce PTFs without requiring IPLs to apply them whenever possible. PTFs that can be applied immediately have additional activation steps, which are described in the cover letter. Updateable and non-updateable actions exist.

Updateable action PTFs are shipped with an action-exit program to verify the actions required to activate the PTF. The action-exit program is called by the DSPPTF command to list the actions necessary and verify whether the actions are completed. The exit program is called when the details for the PTF are shown using option 5 on the DSPPTF status panel or when you specify SELECT(*ACTRQD) on the DSPPTF command. The status of the PTF is updated if the actions are complete. The status changes from Temporarily applied—PND to Temporarily applied after the required actions are complete.Non-updateable action required PTFs do not have exit programs to verify that the actions have been done. These PTFs remain in a Temporarily applied—ACN status until the next IPL when the status changes to Temporarily applied.

LIC PTF Apply and System Availability

To apply LIC PTFs, the system must be able to access the A-side. If the system IPLs from the B-side, a message appears indicating the wrong copy of LIC is in use. To apply LIC PTFs, we recommend that you use the following command:

PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B)

This command performs an IPL to the A side to apply the LIC PTFs and then to the B side to apply the rest of the PTFs. Since the Job Scheduler can only perform IPLs on the B-side, LIC PTFs are not applied. If these LIC PTFs are the prerequisite of any OS/400 licensed program PTFs, the latter is not applied.

To increase the number of immediate PTFs for LIC, the apply procedure for nucleus modules was changed to fixes for nucleus modules beginning with V4R2.

Space usage allows more PTFs to be built for an immediate apply. Changing the apply process for nucleus modules and minimizing the space usage enable the building of more PTFs as immediate, thus shortening or completely removing downtime caused by IPLs required to apply fixes.

Applying and Removing PTFs and IPLs

To progress toward 24 x 365 system availability, it is necessary to reduce or eliminate maintenance operations that cause the system to be off-line. These days, a primary cause of downtime is the application of PTFs, especially fixes that are applied to the Licensed Internal Code (LIC). More and more PTFs need to be, and are, built to apply immediately to help reduce downtime. When applying a microcode PTF on systems prior to V4R1, the system performs an IPL from the A-side to the apply PTF stage. That includes up to the C6nn nnnn set of System Reference Codes (SRCs). Microcode PTFs are applied. Before OS/400 is started, the system powers down and perform IPL again using the B-side. The IPL is selected using the control panel or the defaults of the PWRDWNSYS command. This process is fairly lengthy, and requires the LIC to be loaded for each IPL. On V4R1 and later systems, if the microcodes PTFs do not affect the MFIOP microcode, the system does not reload the MFIOP when applying the PTFs. This process avoids the need for a second IPL.

For example, a user may apply a delayed microcode PTF while on the B-side, and issue a PWRDWNSYS with a RESTART(*YES) and TYPE(*SYS). The system powers down and performs a mini-IPL without reloading the code into the MFIOP. The microcode PTF subsequently is applied during the SLIC part of the IPL. After the PTF is applied, the system IPLs again without reloading the MFIOP code. If the PTF affects the MFIOP code, the MFIOP code is reloaded during the IPL. The advantage of this approach is that the system does not have to IPL all the way up to OS/400 on the A-side, before coming down and performing IPL again on the B-side. This way, the IPL time is considerably reduced, and the PTF application is faster than it was prior to V4R1. This process is pictured below:

PTF Terminoloy

PTF

A PTF is a set of program modules meant to replace an earlier version of a program module. PTFs are first loaded onto the AS/400 system as save files.

Superseded PTF

A superseded PTF has its program modules replaced by a PTF that was released at a later time. The superseded PTF is not installed on the system. The superseded PTF is included in a PTF that was produced later and is installed on the system.

Prerequisite & Co-requisite PTFs

Prerequisite PTFs must be applied before or at the same time as the PTF, which requires them, is applied. Co-requisite PTFs must be applied at the same time as the named co-requisite PTF that needs them.

PTF Cover Letter

Each PTF consists of program modules and a text file that describes both the problem fix and any activation instructions to affect the installation of the PTF. The cover letter also documents co-requisite PTFs, prerequisite PTFs, superseded PTFs, and PTFs that are distributed together.

RETAIN

RETAIN is the worldwide database for IBM problem management and the central repository of PTF files. You access this database with any and all PTF orders, no matter which ordering method is used.

Preventive Service Planning (PSP)

Preventive service planning (PSP) is a collection of information regarding PTFs applicable to AS/400 hardware and software problems. PSP information should be investigated on a regular basis by using ECS or the Internet.

High Impact or Pervasive (HIPER) PTF

High impact or pervasive (HIPER) PTFs correct serious system problems. These problems usually relate to data integrity, system, and communication processing problems that the IBM AS/400 engineers suspect all or almost all customers experience. These PTFs should be proactively applied. You can find them by reviewing the PSP package or using the ALERT/400 service offering.

Cumulative (CUM) PTF package

Cumulative (CUM) PTF packages are a regularly released set of PTFs that contain all the HIPER PTFs and selected non-HIPER PTFs. The selection criteria changes over time, but generally the PTFs that have had a certain number of download through ECS are selected for the next CUM package.

Electronic Customer Support (ECS)

Electronic customer support (ECS) is an integrated set of functions designed to help service and support the AS/400 system. ECS provides:

1. Hardware & Software Problem Analysis,reporting and Management
2. Copy screen image
3. Question & Answer Support
4. IBM Technical and product information access

Immediate versus Delayed PTF

Some program modules cannot be replaced while in use. Immediate PTFs are those that can be activated while the system is up and performing normal work, where delayed PTFs are activated during a normal IPL. Delayed PTFs can be loaded in groups during a single apply function. Some immediate PTFs do not require an IPL but do require that the product they affect is not in use. Some require a restart of the IOP or a vary off and on of a network description.

A-side and B-side of Licensed Internal Code (LIC)

On the AS/400 system there are two copies of Licensed Internal Code (LIC) known as the A-side and B-side. When a LIC PTF is temporarily installed, it is only installed on the B-side. When a LIC PTF is applied permanently, it is applied to both the A-side and B-side copies of the LIC. If all the LIC PTFs are applied permanently, the system can only be IPLed on the A-side.

Note: Most AS/400 systems should use the B-side copy of the LIC unless otherwise directed by IBM support representatives.

Temporary versus Permanent PTF

When a PTF is temporarily applied, the original program module is renamed and the new module replaces the original one. If the new module proves to be defective, the original module can be reactivated simply by removing the new PTF containing the program module with the Remove PTF (RMVPTF) command. When a PTF is permanently applied, the original module is destroyed. There is no easy way to go back and use the old module. Nonetheless, there are two reasons for applying a PTF permanently:

1.  To Save Disk space
2. A New PTF require the older one to be permanently applied.