The life-cycle of a check - check terminology

We'll use the following terms throughout this document:

Check iteration: An instance of a check routine that does the check processing and clean up phases of a check routine. Only one iteration of a particular check, identified by the check and owner name, can run at a time. During refresh processing, a check is reset to its first iteration.
Check life-cycle: The life-cycle of a check is one full cycle of a check, from initialization through delete. Then, when a check is added to the system as part of refresh processing, the life of the check starts all over again.
Installation updates: The installation can update or override some of the default check values you define in the check definition using:
- SDSF
- The MODIFY command
- Policy statements in the HZSPRMxx parmlib member
The installation might update some check values to make the check more suitable for their environment or configuration. See Managing checks.
Refresh process: Refresh processing first deletes one or more checks from the IBM Health Checker for z/OS and then add the same checks back to the system. The system does the following for each refreshed check:
- Applies any installation updates to the default values for the check.
- Clears the 2K work area (PQEChkWork)
- Resets the check's iteration count to one.
- Starts the initialization phase for the check, if the check is defined as active.
For a local check , you can have multiple checks in a single check routine. When you refresh some, but not all, of the checks in a check routine, the system does refresh processing only for the specified checks.
Refresh processing is kicked off in response to:
- Refresh request (E action character) from the SDSF CK panel. See Using SDSF to manage checks.
- The MODIFY (F) hcproc,REFRESH operator command. See Using HZSPRMxx and MODIFY hzsproc command.