Customizing the TSO/E health checks

TSO/E provides several health checks that are registered with the Health Check facility during TSO/E initialization. These checks are programs or routines that identify potential problems before they impact your availability or cause an outage. The health checks supported by TSO/E take advantage of the IBM® Health Checker for z/OS® framework. For more detailed information, see .

TSO/E provides the following health checks:

TSOE_USERLOGS - This check determines if user logs have been implemented and issues an exception message if they are not in use. When user logs have not been implemented, job notifications and other messages sent to individual users are saved in the system broadcast data set, instead. Utilizing user logs reduces contention on the broadcast data set and reduces the risk of problems with the broadcast data set that could slow or prevent TSO/E logons.
TSOE_PARMLIB_ERROR - This check detects if serious errors occurred during PARMLIB initialization for TSO/E. An exception message is issued if an unrecognized operand was found in the IKJTSOxx member, a syntax error was encountered during the processing of a specific option, or the pointers to key TSO/E control blocks were left uninitialized. TSO/E processing might not work as desired due to the uninitialized or default settings used a result.

Each check includes a set of pre-defined values, such as:

Interval, or how often the check will run
Severity of the check, which influences how check output is issued
Routing and descriptor codes for the check

You can update or override some check values using either SDSF or statements in the HZSPRMxx parmlib member or the MODIFY command. These are called installation updates. You might do this if some check values are not suitable for your environment or configuration.

For example, to delete the TSOE_USERLOGS health check temporarily, issue the following command from the MVS™ console:

F         hzsproc,DELETE,CHECK=(IBMTSOE,TSOE_USERLOGS)
          A check that has been deleted can be undeleted later.

F         hzsproc,ADDNEW,CHECK=(IBMTSOE,TSOE_USERLOGS)

However, deleted health checks can also be reactivated if the Health Checker facility is restarted. To make permanent changes, a policy statement in the HZSPRMxx member is needed. For example, to delete the TSOE_USERLOGS health check permanently the following policy could be defined.

ADDREPLACE POLICY STMT(DEL1) DELETE Check(IBMTSOE,TSOE_USERLOGS)

Then issue F hzsproc,ADD,PARMLIB=xx to add the HZSPRMxx member containing the new policy statement to the list of members containing the IBM Health Checker for z/OS policy.

For more information on the TSO/E health checks, and the IBM Health Checker for z/OS facility, see .