Issuing messages for your check - message table checks versus DIRECTMSG checks

The messages that your check issues are the most important part of your check, because they report the results found by the check. For all of the check types, there are two ways to issue check messages:

Create a separate message table module that defines the check output messages issued by the check routine. A message table has the advantage of allowing you to create much more complete messages. Using a message table also makes it easier to create consistent and maintainable messages and includes formatting support. See Issuing messages in your local check routine with the HZSFMSG macro for additional information on planning check messages in a message table.
Issue messages directly from the check routine. You define the message text right in the message request, as follows:
- For local or remote checks, use HZSFMSG REQUEST=DIRECTMSG, providing the message text in the HZSLFMSG REQUEST=DIRECTMSG request. See HZSFMSG macro — Issue a formatted check message.
- For REXX checks, use HZSLFMSG_REQUEST='DIRECTMSG', providing the message text right in the HZSLFMSG_REQUEST='DIRECTMSG' input variables. See Input variables for HZSLFMSG_REQUEST='DIRECTMSG'.
When it is time to define a DIRECTMSG check to the system, you must do so using the MESSAGETABLE=*NONE subparameter on the MODIFY hzsproc command or in an HZSPRMxx parmlib member on the ADD | ADDREPLACE parameter. See Using HZSPRMxx and MODIFY hzsproc command.