Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
What is a check? IBM Health Checker for z/OS User's Guide SC23-6843-02 |
|
A check is actually a program or routine that identifies potential
problems before they impact your availability or, in worst cases,
cause outages. A check is owned, delivered, and supported by the component,
element, or product that writes it. Checks are separate from the IBM Health Checker for z/OS framework.
A check might analyze a configuration in the following ways:
Check owner and check name: Each check has a
check owner and check name.
For the most up-to-date list of IBM-owned check owners
and names, see the following Web site:
Check values: Each check includes a set of pre-defined values,
such as:
Check output: A check issues its output as messages, which you can view using SDSF, the HZSPRINT utility, or a log stream that collects a history of check output. If a check finds a potential problem, it issues a WTO message. We will call these messages exceptions. The check exception messages are issued both as WTOs and also to the message buffer. The WTO version contains only the message text, while the exception message in the message buffer includes both the text and explanation of the potential problem found, including the severity, as well as information on what to do to fix the potential problem. Resolving check exceptions: To get the best results from IBM Health Checker for z/OS, you should let it run continuously on your system so that you will know when your system has changed. When you get an exception, you should resolve it using the information in the check exception message or overriding check values, so that you do not receive the same exceptions over and over. Managing checks: You can use either SDSF, the HZSPRMxx parmlib
member, or the IBM Health Checker for z/OS MODIFY
(F hzsproc) command to manage checks. Managing
checks includes:
|
Copyright IBM Corporation 1990, 2014
|