How PFA uses the ini file

PFA processing uses the ini file from the check directory if one exists otherwise, it uses the ini file from /etc/PFA.

Note: The system creates /etc/PFA during the installation of z/OS®. If your installation takes steps to delete the /etc/PFA directory that is created during installation, ensure you retain it to take advantage of the new PFA function. If the system does not find the /etc/PFA directory when running the install script, AIRSHREP, the ini file is copied to each check directory (for both new and migrate option). For more information, see the topic on Migrate /etc and /var system control files in z/OS Migration.

PFA can use the single ini file for all checks in the /etc/PFA directory, which means you only have to update and maintain one ini file. If you prefer a specific check uses a different level of Java™ than what is specified in the /etc/PFA/ini directory, provide an ini file in the check directory for the check. For example, create an ini file in the pfa/PFA_MESSAGE_ARRIVAL_RATE/ directory if you want to use a different level of Java for the PFA_MESSAGE_ARRIVAL_RATE check.

If the path to the JDK for your installation is not the same as the path in the ini file in /etc/PFA/ and in the checks’ directories (if they exist) or if you installed the PFA Java code in a location other than the default path, you must update each ini file after running the install script for PFA. For more information, see Updating the Java path.