IBM Power Systems

IBM Power Systems

About This Blog

Warm wishes and welcome to all AS400 Administrators and Operators.



This is exclusive blog for iSeries system Administrators working anywhere in the world. Also a place for guys and gals who want to share knowledge pertaining to iSeries. This blog has been designed for exchanging knowledge on AS400 or iSeries server administration and operations.



Friday, February 5, 2010

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.

No comments:

Post a Comment