Modify the UPDATE statement for the PFA date change

Description

Before z/OS V2R2, Predictive Failure Analysis (PFA) checks had a DATE value that reflected the current parameters and values.

Beginning with z/OS V2R2, the DATE value in each PFA check changed because new parameters are added to all checks. The existing UPDATE statements in HZSPRMxx parmlib members fail unless the DATE parameter is set to use ('20140313') or later.

New parameters are added to all PFA checks. If you want to use the new PFA enhancements, or you want to use a value other than the default, you must create an HZSPRMxx parmlib member or modify the existing one.

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 you have updated PFA checks in HZSPRMxx.
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

Follow these steps:

Determine whether you are using an HZSPRMxx parmlib member that contains the UPDATE statements for one or more PFA checks.
If you have an UPDATE statement for any PFA check, the DATE parameter must be changed to DATE('20140313') or later, or the UPDATE fails.
Determine whether you want to change the value of any of the new parameters. If you want to change the values, add the parameters and new values to the UPDATE command.
If you do not want to change any of the other parameter values, PFA uses the value that was last set. When a value is never set, PFA uses the default.
If you specify WTOTYPE for the PFA_COMMON_STORAGE_USAGE check and want to use the new enhancement for dynamic severity for that check, remove WTOTYPE from the UPDATE statement.

For example, the following UPDATE statement changes for the PFA_JES_SPOOL_USAGE check changes:

DATE to ('20140313').
EXCDIRDAYS to 30 days.
FORCEMODEL time to 5:00 A.M.
COLLUPTIME to 3 hours.

UPDATE CHECK(IBMPFA,PFA_JES_SPOOL_USAGE)
ACTIVE
SEVERITY(MEDIUM)
INTERVAL(ONETIME)
PARMS=(’COLLECTINT(5)’,’MODELINT(720)’,’STDDEV(3)’,’DEBUG(0)’,’COLLECTINACTIVE(1)’
,’EXCEPTIONMIN(10)’,'EXCDIRDAYS(30)','FORCEMODEL(5:00)','COLLUPTIME(180)')
DATE(20140313)
REASON(’To detect a damaged address space by comparing the amount of
change in the size of the JES spool to the expected value.’)

Reference information

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