Ensure that PFA finds the configuration file

Description

Before z/OS V2R2, Predictive Failure Analysis (PFA) required that you run the install script, AIRSHREP.sh, to create the new directory structure, copy the ini file, and create the default EXCLUDED_JOBS file. Beginning with z/OS V2R2, there is no need to run the install script. Everything previously done by the install script is now done when PFA starts. Also, the only ini file that PFA uses is the /etc/PFA/ini file. The install of PFA requires that any values in the /etc/PFA/ini file are correct.

Table 1 provides more details about this migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature: BCP.
When change was introduced: z/OS V2R2.
Applies to migration from: z/OS V2R1 and z/OS V1R13.
Timing: Before the first IPL of z/OS V2R2.
Is the migration action required? Yes, if the /etc/PFA/ini file does not exist or if the values for JAVAPATH, PATH, and LIBPATH are not correct.
Target system hardware requirements: None.
Target system software requirements: None.
Other system (coexistence or fallback) requirements: None.
Restrictions: None.
System impacts: None.
Related IBM® Health Checker for z/OS® check: None.

Steps to take

Before you begin, ensure that the PFA user has READ access to the /etc/PFA/ini file. Also, the operator must have proper authority to read or update the files, as needed.

When PFA is started, PFA attempts to use the values in the /etc/PFA/ini file.

Follow these steps:
  1. If the /etc/PFA/ini file already exists, PFA uses the existing JAVAPATH, PATH, and LIBPATH that are in the file. Update the values as necessary.
  2. If the /etc/PFA/ini file file does not exist, PFA attempts to create the /etc/PFA/ini file file from an existing check, or it uses the values defined in the /usr/lpp/bcp/samples/PFA/ini file. To ensure that the JAVAPATH, PATH, and LIBPATH values are correct for your installation before PFA starts, copy /usr/lpp/bcp/samples/PFA/ini into /etc/PFA/ini and update the values as necessary.
For example, check the values for the JAVAPATH, PATH, and LIBPATH to be certain they are at the correct level for PFA. In z/OS V2R2, PFA uses a minimum level of Java 7.1 (31-bit) as in the following examples for the PATH and LIBPATH:
PATH= /usr/lpp/java/J7.1/lib/s390/classic:/usr/lpp/java/J7.1/lib/s390

LIBPATH=/usr/lpp/java/J7.1/lib/s390:/usr/lpp/java/J7.1/lib/s390/classic:/lib:/usr/lib:

If the values are not correct, PFA either fails to start or can have processing errors.

Reference information

For information about installing PFA, see z/OS V2R2 Problem Management.