Required HZSLFMSG_REQUEST='DIRECTMSG' variables

CHECKEXCEPTION specifies that you want to issue an exception message to notify the installation that action is required because a check routine found an exception to a setting. The message text, intended for the operator, is issued in a WTO. The message text and full explanation are issued to the message buffer, mainly for the system programmer.

CHECKINFO specifies that you want to issue a general non-exception informational message, such as a message about the completion of the check without exceptions or the first line of a report. The message number and text are issued to the message buffer.

CHECKREPORT specifies that you want to issue a report message. A report message consists of a single line of report data issued to the message buffer without a message number (except in debug mode). The report message type gives you the most control over the formatted output. A single report line can be up to 65535 characters of formatted output.

REASON='CHECKREPORT' requires the HZSLFMSG_DIRECTMSG_TEXT variable. There are no optional variables for use with CHECKREPORT.

You can specify HZSLFMSG_DIRECTMSG_ID on a REASON=CHECKEXCEPTION or a REASON=CHECKINFO request.

The recommended message identifier format is ccccHmmmms:

• cccc is the component identifier, such as ISG for global resource serialization.
• the required H represents IBM Health Checker for z/OS.
• mmmm is the message number. For example, in message identifier ISGH101E, 101 is the message number.
• s is the severity code for the message: E for exception messages and I for information messages

You can specify HZSLFMSG_DIRECTMSG_TEXT on a REASON=CHECKEXCEPTION, CHECKINFO or CHECKREPORT request.

For information on how message text is formatted in the message buffer, see How messages are formatted in the message buffer.