Statements and parameters for MPFLSTxx

• A complete message identifier of one to ten characters. This is known as a specific message identifier.
• A message prefix, which is a portion of the message identifier, followed by an asterisk (*). This is known as a generic message identifier.
• A single quotation mark (') is not a valid character in a message identifier.

A message identifier begins with the first nonblank character of the message text and continues until the next blank.

You can specify only one msgid per record. If a msgid is repeated within an MPFLSTxx member, the system uses the options that are specified on the first record and ignores the duplicates.

If you want MPF to process a specific message, you must specify the complete message ID, for example, IEF124I.

If you want MPF to process all messages that begin with a specific prefix, you can specify the prefix and an asterisk, for example, IEF24*. Use the message prefix with an asterisk carefully. Too wide a suppression, such as IEF*, could suppress many messages that you need for effective system operation.

With one exception, specific message definitions take precedence over generic message definitions. For example, if you specify both a specific entry for IEF638I, and a generic entry that includes IEF638I (such as IEF63*), the system uses the specific entry to process IEF638I.

In situations where a message is included by more than one generic message definition, such as IEF6* and IEF63*, the most specific definition takes precedence. In this example, the system uses the entry for IEF63* for message IEF638I, if no specific entry exists.

,AUTO(YES|NO|token)

Specifies whether the message (msgid) is eligible for processing by an automation subsystem, such as NetView®.

NO

Makes the message ineligible for automation processing.

YES

Makes the message eligible for automation processing.

token

The token value is available for MPF installation exit processing and for processing by an automation subsystem. Specifying a token indicates that the message is eligible for processing by the automation subsystem. The token value must be 1 to 8 alphanumeric characters. Do not use a left parenthesis as part of the token value. Embedded blanks are allowed in the token value. For example, if you code an ‘N,O, and a blank’, AUTO(NO ), the system takes the “NO” as a token value.

If you specify msgid and do not specify the AUTO option, the system defaults to NO. If you do not specify any message processing statements for a message, the system considers the message eligible for automation processing AUTO(YES). To change the system default, use the .DEFAULT or the .NO_ENTRY statement.

Note: A message might loop repetitively to an extended MCS console if all of the following conditions are true:

• AUTO(YES) is specified, and
• The RACF® OPERPARM segment specifies AUTO YES for the extended MCS console, and
• The console profile, as defined through TSO/E CONSPROF, specifies YES for the UNSOLDISP parameter or for the SOLDISP parameter or for both.

Default: NO

,RETAIN(YES|I,E,CE|NO)

If the message identified by the msgid is an action message (immediate, eventual, or critical eventual), RETAIN specifies whether the message is to be retained by the action message retention facility (AMRF). AMRF retains action messages only (not WTORs).

CE

Critical eventual action messages are retained.

E

Eventual action messages are retained.

I

Immediate action messages are retained.

NO

No action messages are retained.

YES

All action messages are retained. YES is the default.

You can specify any combination of I, E, or CE.

To view a retained message, use the DISPLAY R command.

Default: YES. You can use the .DEFAULT statement followed by a msgids to change the system default for the list of messages.

,SUP(YES|ALL|NO)

Specifies whether MPF is to suppress the message that is identified by msgid.

ALL

Suppresses all messages that are identified by msgid, without exception.

NO

Messages that are identified by msgid are not suppressed.

YES

Suppresses messages that are identified by msgid, with the following exceptions:

• Command responses where MCSFLAG=RESP was specified on the WTO or WTOR macro.
• Command responses with descriptor code 5 (immediate command response).
  Note: This exception does not apply to command responses with descriptor code 5 that are generated in response to the MONITOR command. SUP(YES) suppresses such responses.

If you specify a msgid without SUP, the system uses the default, SUP(YES), and does not display the message. If, however, you do not specify any message processing statements for a message, the system displays the message. To change the system defaults, use the .DEFAULT or the .NO_ENTRY statement.

Default: YES

,USEREXIT(exitname)

Specifies the name of an installation-supplied WTO/WTOR installation exit routine that is to get control each time the system issues the messages. This routine can process the messages; it can suppress, retain, or respond to a message. It can make the message eligible for automation processing, and take other actions on the message. The exit should be link-edited into an APF-authorized library that is part of the LNKLST concatenation.

The exitname can be from one to eight alphanumeric (A-Z, 0-9) and national characters (&, *, $). The first character must be alphabetic or numeric. If you do not specify an exitname, the system uses IEAVMXIT, if it exists. To change the system default, use the .DEFAULT statement.

For more information about the WTO/WTOR installation exits, see CONSOLxx (console configuration definition) and z/OS MVS Installation Exits.

You can use the .DEFAULT statement multiple times within an MPFLSTxx member. Each group of messages following a .DEFAULT statement should have common option values. This allows you to control attributes assigned by default to each message ID without having to change every message processing record.

On a particular message record (msgid statement) that follows a .DEFAULT statement, you can specify specific operand values that override, for that message, the .DEFAULT values.

If there are multiple occurrences of a message ID that is listed under one .DEFAULT statement, the system uses the options for the first occurrence and ignores the others.

NOCHANGE

.MSGIDS NOCHANGE specifies that the message identifiers are to be the same as those specified in the previously used concatenation of MPFLSTxx members (the one the system was previously using). Use this statement with the .MSGCOLR statement.

The .MSGIDS NOCHANGE statement should not be specified in an MPFLSTxx member or a concatenation of MPFLSTxx members that includes message identifiers. If syntactically correct message identifiers (msgid statements) precede the .MSGIDS NOCHANGE statement, the system ignores the statement, issues an IEF760I error message, and continues processing the remaining statements. If a valid .MSGIDS NOCHANGE statement precedes message identifiers, the system ignores the message identifiers, issues an IEF760I error message, and continues processing the remaining statements.

If multiple .MSGIDS NOCHANGE statements occur in one MPFLSTxx member, or a concatenation of MPFLSTxx members, the system processes each statement as though it were the first statement.

.NO_ENTRY is a very powerful statement and should be used with care.

If you specify a .NO_ENTRY statement with no options, the system considers the messages that are not specified in the MPFLSTxx member to be eligible for automation processing, it retains action and WTOR messages, and it displays all messages (AUTO(YES) RETAIN(YES) SUP(NO)). These options are the same defaults that the system uses when no message processing record is specified in an MPFLSTxx member for a particular message.

.NO_ENTRY checks the syntax and then ignores the USEREXIT(exitname) statement. IEAVMXIT receives control, if it exists.