Where to next? A road map for developing your check

To create a IBM Health Checker for z/OS check for your component or product, you must do the following:

Write a check routine that gathers information, compares current values with suggested settings or looks for configuration problems, and issues messages with the results of the check.
- For a local check, see Writing local check routines.
- For a remote check, see Writing remote check routines.
- If you are writing a REXX check, see Writing REXX checks.
Create messages for the check. You can do this in two ways:
- Create a separate message table module that defines the check output messages issued by the check routine. See Issuing messages in your local check routine with the HZSFMSG macro.
- Create DIRECTMSG messages right in the check routine in one of the following ways:
  - For local or remote checks, use HZSFMSG REQUEST=DIRECTMSG. See HZSFMSG macro — Issue a formatted check message.
  - For REXX checks, use HZSLFMSG_DIRECTMSG_. See Input variables for HZSLFMSG_REQUEST='DIRECTMSG'.
Provide documentation about check-specific installation overrides to allow the installation to override the default check values defined when the check was added. See IBM Health Checker for z/OS checks.