Using HZSPRMxx and MODIFY hzsproc command

The syntax for both the HZSPRMxx parmlib members and the MODIFY hzsproc,parameters command (F hzsproc,parameters) follows. You can use the same parameters and syntax for both the HZSPRMxx parmlib member and the F hzsproc,parameters command. However, if you want to be consistent with the way commands and parmlib members are specified:

• Command syntax: Issue the F hzsproc,parameters command as shown in our syntax diagram.
• HZSPRMxx syntax: To specify parameters in an HZSPRMxx member:
  • Use parentheses where we show an equal sign. For example:
    • X=Y should be X(Y)
    • X=(Y) should be X(Y)
  • Separate parameters with blanks instead of commas. For example, command

    UPDATE,CHECK=(IBMAAA,CHECKA)

    should be as follows in HZSPRMxx:

    UPDATE CHECK(IBMAAA,CHECKA)

    See Guidelines for HZSPRMxx parmlib members for more information.

Parameters take effect for different durations:

• The following parameters are one time actions which are applied immediately. We recommend that you use the MODIFY command for these:
  • ADDNEW
  • DELETE
  • DISPLAY
  • REFRESH
  • RUN
  • STOP
  • ADD, or REPLACE,PARMLIB - Note that you can only specify these parameters on the MODIFY command. They are not valid in a HZSPRMxx member.
• The following parameters are applied immediately and remain in effect until the check is refreshed. For any changes you wish to keep, we recommend that you use policy statements in an HZSPRMxx parmlib member for these parameters.
  • UPDATE
  • ACTIVATE
  • DEACTIVATE

  If you just want to experiment with temporary check changes, you can use UPDATE, ACTIVATE, and DEACTIVATE in the MODIFY command. However, if you want to keep the changes you make with UPDATE, ACTIVATE, and DEACTIVATE past the next refresh, we recommend that you use these parameters in policy statements in an HZSPRMxx parmlib member so that they take affect whenever the affected check is added.

  Note that if you put these parameters into HZSPRMxx member(s) but not on policy statements, they act only on checks that have been added at the time that the parmlib member is processed. Particularly during initialization of IBM® Health Checker for z/OS®, no order is guaranteed among adding of checks and processing of the parmlib member.

• The ADD, ADDREPLACE, or REMOVE POLICY parameters are applied immediately, and are applied again whenever a check is added or refreshed. We recommend that you use policy statements in an HZSPRMxx parmlib member for these parameters. See Creating and maintaining IBM Health Checker for z/OS policies.
• The ADD and ADDREPLACE CHECK parameters are applied immediately and remain in effect as long as the parmlib member in which they are defined is in use. See Syntax and parameters for HZSPRMxx and MODIFY hzsproc.

Using wildcard characters in MODIFY hzsproc and HZSPRMxx: When you have many checks, you can simplify management by using wildcards. You can use wildcard characters * and ?. An asterisk (*) represents any string having a length of zero or more characters. A question mark (?) represents a position which may contain any single character. For example, the following command specifies that all checks with an owner that is 6 characters long beginning with IBM be run:

F hzsproc,RUN,CHECK=(ibm???,*)

The following HZSPRMxx POLICY statement specifies that a new policy be added that will update all IBMUSS owned checks to a severity of HIGH.

ADD POLICY STMT(POL5) UPDATE CHECK(IBMUSS,*) SEVERITY(HIGH)