Syntax and parameters of the MSG statement

MSG statements define up to 1024 specific messages for which specific actions are to be taken if the message is involved in a message flooding situation. The MSG statement has the following syntax form.

MSG msgid [action][,action]

The MSG statement applies to the previously specified SPECIFIC msgtype statement. One to 1024 MSG statements should follow the SPECIFIC msgtype statement.

msgid: A 1-to-10 character message identifier. Up to the first 10 characters of the first blank-delimited token in the message is treated as the message identifier.
Message flood automation treats everything in the message up to the first blank as the message ID. If the message ID in the message is followed immediately by a special character before the first blank, the special character is treated as part of the message ID and must be specified for a match to occur. Also, message flood automation can handle message IDs with embedded special characters without problem, for example, message IDs that include embedded "-" characters.

Note: The msgid identifier does not support wildcard specifications.
action: If specified, is one or more of the actions as defined for the DEFAULT statement. CMD is not supported. If an action is not specified, the DEFAULT or built-in actions are taken for the message. You can use a MSG statement to override the DEFAULT or built-in actions to be taken for a specific message. If IGNORE is specified, the message is ignored by message flood automation and no action is taken for the message even if the message threshold is exceeded and other actions are specified.

Syntax rules:

The MSG specification must begin in column 1 and must be separated from the msgid by a single blank character.
The msgid is separated from the first action, if specified, by a single blank character. More than one blank character causes any following string to be treated as comment text.
action specifications are separated by a comma. There must be no blank characters on either size of the comma.
Comment text may follow the last action. There must be at least one blank character between the action and the beginning of the comment text. If action is not specified, there must be at least two blank characters. There is no need to preface the comment text with either an asterisk (*) or open comment specification (/*).

Example:

MSG IAT1001
MSG IAT1002   comment: note >1 blank required before comment
MSG IAT1003 LOG,NOAUTO
MSG IAT1004 LOG,NOAUTO comment: note only 1 blank required
MSG IOS000I NOLOG,NODISPLAY
MSG DSI064A NOLOG,NODISPLAY,NORETAIN

Suggested MSG specifications to handle specific conditions:

Provide MSG specifications for the following messages that can be produced if an ESCON® Director or FICON® switch fails:

IOS001E
IOS050I
IOS051I
IOS071I
IOS251I
IOS444I
IOS450E

Provide MSG specifications for the following messages which can be produced if a device fails:

IOS003A

Provide MSG specifications for the following messages if you perform HyperSwaps or are in a GDPS® environment:

IOS000I NOLOG,NOAUTO,NODISPLAY
IOS002A NOLOG,NOAUTO,NODISPLAY
IOS017I NOLOG,NOAUTO,NODISPLAY
IOS107I NOLOG,NOAUTO,NODISPLAY
IOS109E NOLOG,NOAUTO,NODISPLAY
IOS251I NOLOG,NOAUTO,NODISPLAY
IOS291I NOLOG,NOAUTO,NODISPLAY
IOS444I NOLOG,NOAUTO,NODISPLAY
IOS450E NOLOG,NOAUTO,NODISPLAY
IEA476E NOLOG,NOAUTO,NODISPLAY
IEA491E NOLOG,NOAUTO,NODISPLAY
IEA494I NOLOG,NOAUTO,NODISPLAY
IEA497I NOLOG,NOAUTO,NODISPLAY

Note:

Specifying NOLOG, NOAUTO and NODISPLAY together causes the message to be completely deleted.
While NOAUTO was chosen as the default for the above list of messages to prevent message floods from overwhelming automation, if your automation has dependencies on any of these messages during a HyperSwap® (including HyperSwaps in a GDPS environment), you might consider specifying AUTO for the message so that it can be detected by your automation. Refer to the GDPS documentation for further suggestions on use of Message Flood Automation in that environment.
If your automation has dependencies on any of these messages during a HyperSwap, you should specify AUTO for the message so that it can seen by your automation.