z/OS messages must have a match in the message filter table to be forwarded to the OMi management server. The message table holds up to 2,000 message IDs by default. If a successful match is found for a message ID, the job name and/or job ID of the job which generated the message can also be checked, and the message will only pass if it also matches the given job name or job ID. If a REXX script is specified and the RMA subtask is running, the named script will be called.
Parameters
Parameters |
Description |
|---|---|
msgid |
The message ID of the message to pass to OM server. Typically, this is the first token of the message (up to the first space). msgid can contain the special period placeholder character (.) to indicate that any character in that position should match. If the msgid is terminated with an asterisk (*), matching will occur only on characters preceding the asterisk. Multi-line MVS messages will be forwarded to the OM browser as one continuous message unless a plus sign “+” is placed in front of msgid, in which case the multiple lines will be sent as separate messages, each with prepended to the message text, or a minus sign “-” in front of msgid, in which case the multiple lines will be sent as separate messages, but without the msgid prepended to the message text. A msgid can be up to 15 characters in length. |
jobname |
The job name of the job that issued the message. The same wildcarding rules used in msgid may be applied to this parameter. A jobname may be up to 8 characters in length. |
jobid |
The job ID of the job that issued the message. The same wildcarding rules used in msgid may be applied to this parameter. A jobid may be up to 8 characters in length. |
script |
A REXX program to be called if this message is encountered. The program will be called with one parameter: the message text, the job name, and the job ID, separated by carriage return characters (x'0A'). (If there is no job name or job ID, these fields are filled in with "N/A"). See the sample programs JOBSUB, PARSEMSG, and SMFDUMP in the Ironstream SAMP dataset for examples on how to set up automation programs. The REXX program must be available in the dataset specified by the DD card named on the RMA subtask card (see the RMA Parameter Card definition). |