Once you've written the check routine and the HZSADDCHECK exit routine r for your checks, you must then add the checks to IBM Health Checker for z/OS so that the system can run the check. To do this, you must add the HZSADDCHECK exit routine r to the HZSADDCHECK exit and then have the system call the exit to run the exit routine. There are two approaches to this step:

• When your check is ready for production, you will add the code to your product or component to activate your checks when your product starts. See Creating product code that automatically registers checks at initialization.
• For testing purposes, you can add the HZSADDCHECK exit routine to the system dynamically with either operator commands or in a program, as we will show in this section. See:
  • Using operator commands to add checks to the system dynamically
  • Using a routine to add checks to the system dynamically

  You can also simply define the check defaults and values directly in an HZSPRMxx parmlib member and bypass the HZSADDCHECK exit routine entirely. See the ADD or ADDREPLACE CHECK parameters in Syntax and parameters for HZSPRMxx and MODIFY hzsproc.

Once you have added your check to the system using one of these methods, you can use a command such as the following to verify that it is there:

F hzsproc,DISPLAY CHECK(checkowner,checkname),DETAIL

Once a check has been added to the system, it will remain active and will run at the specified interval until:

• A user explicitly deactivates or deletes the check, issuing a MODIFY command for example. See Making dynamic, temporary changes to checks.
• IBM Health Checker for z/OS disables a check because of check routine or environmental problems. See IBM Health Checker for z/OS controlled states.