Making persistent changes to checks

You can make changes to checks that persist across check refreshes and restart of IBM® Health Checker for z/OS® using statements in the HZSPRMxx parmlib member. The HZSPRMxx parmlib member should include only the following kinds of statements:
  • POLICY statements to define your policy. The system applies POLICY statements every time IBM Health Checker for z/OS starts up, as well as when checks are added or refreshed. See Creating and maintaining IBM Health Checker for z/OS policies.
  • ADD | ADDREPLACE CHECK statement to define local installation-written check defaults to the system and add them to IBM Health Checker for z/OS. ADD | ADDREPLACE CHECK statements are applied every time IBM Health Checker for z/OS starts up. See Syntax and parameters for HZSPRMxx and MODIFY hzsproc.
  • WHEN statements containing other appropriate HZSPRMxx statements, mostly policy statements. The statements within a WHEN statement are applied conditionally, depending on the particular system configuration. Using the WHEN statement allows you to share HZSPRMxx members between many systems in a sysplex, even if you have need to specify particular conditions for some systems.

    The system interprets WHEN statements when it reads the HZSPRMxx parmlib member. If the WHEN statement meets the criteria, the system applies the statements as appropriate for the type of statement.

    See Using WHEN to apply statements conditionally and Syntax and parameters for HZSPRMxx and MODIFY hzsproc.
  • LOGGER statement to turning log stream support on or off for IBM Health Checker for z/OS. See LOGGER.
  • HZSPDATA statement to define the name of the HZSPDATA persistent data set. See HZSPDATA.

If you specify other statements, such as UPDATE, ADDNEW, or DISPLAY, the system applies them once and only to currently active checks. This means that including such non-policy statements in your HZSPRMxx member are ineffective. Start of changeFor example, a plain, non-POLICY UPDATE in HZSPRMxx typically does not affect any, or a few checks, when such an HZSPRMxx member is read in at Health Checker START time. This is because most checks are not added to Health Checker at that time. An indicator of this situation, an UPDATE not being applied as expected, is message HZS0410I  - CHECK(checkowner,checkname): UPDATE PROCESSING FOUND NO MATCH. Non-policy statements that you put in your HZSPRMxx member are not part of your IBM Health Checker for z/OS policy. Such statements cannot be applied to checks that are added to Health Checker later.End of change

Note that you can share HZSPRMxx parmlib members across different systems in a sysplex, even if those systems are at different levels, and even if a system at a lower level does not support the most current HZSPRMxx parameters you specify. See Sharing critical IBM Health Checker for z/OS information between systems at different levels.