Step 4: Verify fix installation
You should develop the habit of verifying whether 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 installation.
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.
- Type GO LICPGM from any command line.
- Type option 50 (Display log for messages).
- 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.
- 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:
- Go to the start-control-program-function (SCPF) job log (WRKJOB SCPF).
- If you performed an IPL, choose the first job that's not active and look at the spooled file for that job.
- Find the error messages, and determine what caused the error
- 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:
- On any command line, type GO LICPGM and press Enter. The Work with Licensed Programs display appears.
- Select Option 50 (Display log for messages). The Display Install History display appears.
- 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 the temporary IPL source (T-side) to activate the changes to the server firmware. On systems running V5R4M0 Licensed Internal Code, use the DSPPTF SELECT(*ACTRQD) command to determine which PTFs require a server IPL. On systems running V5R4M5 Licensed Internal Code, use the Display Firmware Status (DSPFMWSTS) command to determine the PTF that requires a server IPL. See Installing 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.
Parent topic:
Installing fixesRelated concepts
Single fixes Causes of abnormal IPLs