Using HZS exception messages for automation

A check exception message WTO consists of an HZS header message, followed by the check-specific exception message text, as shown in the system console example below:

 HZS0001I CHECK(IBMUSS,USS_MAXSOCKETS_MAXFILEPROC)
 BPXH033E MAXSOCKETS value for AF_INET is too low.

The HZS header messages issued with exceptions are:

HZS0001I: Exception information message: low severity or WTOTYPE(INFORMATIONAL). Indicates that the check found a problem that will not impact the system immediately, but that should be investigated.
HZS0002E: Exception eventual action message: medium severity or WTOTYPE(EVENTUAL). Indicates that the check found a medium severity problem in an installation.
HZS0003E: Exception critical eventual action message: high severity or WTOTYPE(CRITICAL). Indicates that the check routine found a high-severity problem in an installation.
HZS0004I: Exception hardcopy message: hardcopy only informational severity or WTOTYPE(HARDCOPY).

See z/OS MVS System Messages, Vol 6 (GOS-IEA) for a complete list of IBM Health Checker for z/OS HZS messages.

To find the documentation for the check-specific messages (which are on the second line of the WTO), such as BPXH033E shown above, look in either:

Using LookAt - see Finding check message documentation with LookAt.
The check owner product or element documentation. For a list of documents where you can find the messages documented for each check, see IBM Health Checker for z/OS checks.