Writing remote check routines
A remote check runs as a task in the caller's address space. To learn about the differences between local and remote checks and deciding which type you want to write, see Remote checks.
A IBM Health Checker for z/OS check gathers information about the system environment and parameters, compares them to suggested settings or looks for configuration problems, and then informs customers of the results through detailed messages. Because remote checks run in the caller's address space (rather than the IBM® Health Checker for z/OS® address space) you must ensure communication between the remote check routine and IBM Health Checker for z/OS.
To learn about the differences between local and remote checks and deciding which type you want to write, see Remote checks.
- Metal C or assembler?
- Sample checks
- Remote check routine basics
- Programming considerations
- Preparing for check definition - making sure IBM Health Checker for z/OS is up and running
- Allocate a pause element token using IEAVAPE
- Issue the HZSADDCK macro to define a remote check to IBM Health Checker for z/OS
- Pause the remote check routine with IEAVPSE
- Using HZSCHECK REQUEST=OPSTART and REQUEST=OPCOMPLETE to communicate check start and stop to IBM Health Checker for z/OS
- Using the check parameter parsing service (HZSCPARS)
- Using the HZSPQE data area in your remote check routine
- Release codes for remote check routines
- Creating and using data saved between restarts
- Issuing messages in your remote check routine with the HZSFMSG macro
- Writing a check with dynamic severity levels
- Controlling check exception message WTOs and their automation consequences
- Defining the variables for your messages
- Recommendations and recovery considerations for remote checks
- Building Metal C checks
- Debugging checks