Identifies
a message or group of messages to be processed. The msgid consists
of: - 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 non-blank character
of the message text and continues until the next blank.
Note: The
system might insert a character, such as a + or *, preceding the message
identifier. This character is not a part of the message identifier.
Do not add it to the msgid specification.
You
can specify only one msgid per record. If a msgid is repeated within
an MPFLSTxx member, the system uses the options 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
(see note below), 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.
Note: A msgid that
consists of only a single asterisk (‘*’) does not mean “all messages,”
but rather messages that have a single asterisk as their message identifier.
- ,AUTO(YES/NO/token)
- Specifies whether the message (msgid)
is eligible for processing by an automation subsystem, such as NetView®. AUTO(YES) makes the
message eligible for automation processing. AUTO(NO), which is the
system default, makes the message ineligible for automation processing.
If you specify msgid and do not specify
the AUTO option, the system defaults to NO. If, however, 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.
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. You may not use
a left parenthesis “(” as part of the token value. Imbedded 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.
Note: A
message might loop repetitively to an extended MCS console if all
of the following 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.
- ,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).
- YES
- all action messages are to be retained; this is the default
- I
- immediate action messages are to be retained
- E
- eventual action messages are to be retained
- CE
- critical eventual action messages are to be retained
- NO
- no action messages are to be retained
You can specify any combination of I, E,
or CE.
The system default is RETAIN(YES). You can use
the .DEFAULT statement followed by a msgids to change the system default
for the list of messages.
To view a retained message, use the
DISPLAY R command.
- ,SUP(YES/ALL/NO)
- Specifies whether
MPF is to suppress the message identified by msgid.
SUP(YES) is the default, and indicates that the system is to suppress
messages identified by
msgid, with the following
exceptions:
SUP(ALL) specifies that the system is to suppress all
messages identified by msgid, without exception.
SUP(NO)
specifies that the system should not suppress messages identified
by msgid.
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.
- ,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 message(s).
This routine can process the message(s); 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.
.DEFAULT
allows you to specify the defaults that you want for the message processing
records (msgids) that follow .DEFAULT. The options you specify on
the .DEFAULT statement override the system defaults for messages that
you list. On the .DEFAULT statement, you can specify that the message
is eligible for automation processing, retention, and/or suppression,
and the installation exit that is to process the message. Through
AUTO(token), you can also specify information to be passed to the
automation subsystem. .DEFAULT with no options, results in the message
being ineligible for automation processing, and indicates that the
system is to suppress and retain any listed action messages. IEAVMXIT,
if it exists, receives that message. 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 listed under one .DEFAULT
statement, the system uses the options for the first occurrence and
ignores the others.
If an MPFLSTxx member contains multiple
.DEFAULT statements, the system uses the values on the .DEFAULT statement
that precedes the first message record (msgid statement) in that group.
- ,AUTO(YES/NO/token)
- Specifies whether a message or a list of messages following the
.DEFAULT statement is eligible for processing by an automation subsystem,
such as NetView. AUTO(YES)
makes the message(s) eligible for automation processing. AUTO(NO)
(the system default for the .DEFAULT statement) makes the subsequent
message(s) ineligible for automation processing.
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. You may not use
a left parenthesis “(” as part of the token value. Imbedded blanks
are allowed in the token value. For example, if you code an ‘N,O,
and a blank’, AUTO(NO ), the system uses the “NO” as a token value.
Note: - If you specify a .DEFAULT and omit the AUTO option, the system
will not consider the message(s) eligible for automation processing.
If, however, you do not specify any message processing statements
for a message, the system considers the message eligible for automation
processing.
- A message might loop repetitively to an extended MCS console if
all of the following 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.
- ,RETAIN(YES/I,E,CE/NO)
- RETAIN specifies which
subsequent action messages are to be retained by the action message
retention facility (AMRF).
- YES
- all action messages are to be retained; this is the default
- I
- immediate action messages are to be retained
- E
- eventual action messages are to be retained
- CE
- critical eventual action messages are to be retained
- NO
- no action messages are to be retained
You can specify any combination of I, E, or CE.
To view a retained message, use the DISPLAY R command.
- ,SUP(YES/ALL/NO)
- Specifies whether
MPF is to suppress subsequent messages.
SUP(YES) is the default,
and indicates that the system is to suppress subsequent messages,
with the following exceptions:
SUP(ALL) specifies that the system is to suppress all
subsequent messages, without exception.
SUP(NO) specifies that
the system should not suppress subsequent messages.
If you
specify a .DEFAULT statement without SUP, the system uses the default,
SUP(YES), and suppresses subsequent messages.
If you specify
a .DEFAULT statement with one of the SUP options, and then specify
SUP on a subsequent message record, the system uses the SUP value
specified on that particular message record.
If you do not
specify any message processing statements for a message, the system
displays the message, regardless of any SUP value that might have
been specified on a preceding .DEFAULT statement.
- ,USEREXIT(exitname)
- Specifies
the name of an installation-supplied WTO/WTOR installation exit routine
that is to get control each time the system issues one of the indicated
messages. This routine then processes the message(s). 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) or national characters
(@, $, *). The first character must be alphabetic or numeric. If you
do not specify an exitname the system defaults
to IEAVMXIT, if it exists.
For more information about the WTO/WTOR
installation exits, see the CONSOLxx member of SYS1.PARMLIB in this information,
and z/OS MVS Installation Exits.
.NO_ENTRY
specifies the message processing options for all messages that are NOT specified
in MPFLSTxx members. The options you specify on the .NO_ENTRY statement
override the system defaults for messages that are not specified in
this member. On the .NO_ENTRY statement, you can specify whether all
messages not specified in the MPFLSTxx member are to be considered
eligible for automation processing, retained, and suppressed. .NO_ENTRY
is a very powerful statement and should be used with care.
Note: .NO_ENTRY
requires the underscore (_) in the syntax. You might not, however,
be able to print the underscore character on your printer.
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.
Specify only one .NO_ENTRY
statement in an MPFLSTxx member. If there is more than one occurrence
of a .NO_ENTRY statement in an MPFLSTxx member, the system checks
the syntax of the duplicate and uses the options on the first .NO_ENTRY
statement. If there is more than one occurrence of a .NO_ENTRY statement
in a concatenation of MPFLSTxx members, the system uses the options
on the first valid .NO_ENTRY statement in the concatenation.
- ,AUTO(YES/NO/token)
- For messages that are not identified in MPFLSTxx, AUTO indicates
whether the message is eligible for processing by an automation subsystem,
such as NetView. AUTO(YES),
the system default, makes the messages eligible for automation processing.
AUTO(NO) makes the messages ineligible for automation processing.
(Specifying AUTO without either YES or NO results in a syntax error.)
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. You may not use a left parenthesis “(” as part of the
token value. Imbedded blanks are allowed in the token value. For example,
if you code an ‘N,O, and a blank’, AUTO(NO ), the system uses the
“NO” as a token value.
Note: - IEAVMXIT, if it exists, gets control for all messages whose message
ids are not specified in the MPFLSTxx member.
- A message might loop repetitively to an extended MCS console if
all of the following 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.
- ,RETAIN(YES/I,E,CE/NO)
- For all action
messages (immediate, eventual, or critical eventual) not identified
in MPFLSTxx, RETAIN specifies
which messages are to be retained by the action message retention
facility (AMRF).
- YES indicates that all action messages are to be retained. The
default is RETAIN(YES).
- I indicates that immediate action messages are to be retained.
- E indicates that eventual action messages are to be retained.
- CE indicates that critical eventual action messages are to be
retained.
- NO indicates that no action messages are to be retained.
You can specify any combination of I, E, or CE. To view a
retained message, use the DISPLAY R command.
- ,SUP(YES/ALL/NO)
- Specifies whether
MPF is to suppress messages that are not specified in MPFLSTxx members.
SUP(YES) indicates that the system is to suppress messages, with
the following exceptions:
SUP(ALL) specifies that the system is to suppress all
messages, without exception. SUP(NO) specifies that the system should
not suppress messages.
: SUP(ALL)
causes the system to suppress all messages that are not identified
in the active MPFLSTxx member. This setting might result in most
or all messages being suppressed from the MCS console. Suppression
of all messages is useful in certain situations, such as a remote
system, but it can be detrimental if an operator is expecting these
messages.