Initialization › Initialization Parameter Statement Descriptions › MESSAGE

MESSAGE

Syntax

MESSAGE

message number,
TYPE=NORMAL | SEVERE, 
WTO=YES | NO | NOLOG,
ESFLOG=YES | NO, 
SCREEN=YES | NO,
CID=YES | NO, 
EXIT=YES | NO, 
SDIREQ=YES | NO, 
ROUTCDE=(x,x,x,x......)

Description

The MESSAGE statement is used to specify the way the message is to be processed.

You only have to code a MESSAGE statement for the messages you want to change. You can specify more than one MESSAGE statement. If several MESSAGE statements are valid for the same message number, the statements are processed in the order in which they are specified.

Any parameter specified is valid until explicitly changed by another similar parameter.

MESSAGE Parameters

This section describes the MESSAGE parameters.

message number

This parameter defines the number of the message to be processed. This number can be specified in one of two ways; as a 4-digit number specifying that only one message must be processed, or as two 4-digit numbers separated by a hyphen to specify a range of messages. For example, 123 to indicate message ESF123 or 123-200 to indicate messages ESF123 through ESF200.

The lower limit is 0 and the upper limit is 9999. There is no default value.

TYPE=NORMAL | SEVERE

This parameter defines the form in which the message is presented.

Valid values are:

• NORMAL—The message is presented in normal intensity.
• SEVERE—The message is presented in highlighted intensity.

There is no default value.

WTO=YES | NO | NOLOG

This parameter defines whether the message is to be sent to the MVS console (YES) or (NO).

• YES—Send the message to the MVS console and system log.
• NO—Do not send the message to the MVS console or system log.
• NOLOG—The message is sent to the MVS console but is not to be logged on the hardcopy log (that is, SYSLOG).

There is no default value.

Note: The WTO statement overrides this parameter.

ESFLOG=YES | NO

This parameter defines whether the message must be logged on the ESFLOG.

• YES—Log the message on the ESFLOG.
• NO—Do not log the message on the ESFLOG.

This parameter has no meaning if the NOLOG option has been specified. This parameter can be overridden by the LOGMENU parameter. There is no default value.

When considering the NOLOG startup option or when combining ESFLOG=NO with WTO=NO or NOLOG (the default), be aware it is possible that messages necessary to debug a problem condition will not be available.

SCREEN=YES | NO

This parameter defines whether the message must be broadcast to active display nodes.

• YES—Broadcast the message to active display nodes.
• NO—Do not broadcast the message to active display nodes.

If you specify YES, the message is sent to all active display nodes with AUTH=2.

If the message concerns a specific node, it is also sent to all active display nodes in the same network group as the specific node.

There is no default value.

CID=YES | NO

This parameter defines whether the message must be broadcast to active communication channels.

• YES—Broadcast the message to active communication channels.
• NO—Do not broadcast the message to active communication channels.

If you specify YES, the message is sent to all active channels with AUTH=2. If the message concerns a specific node, it is also sent to all active channels in the same network group as the node. Messages are not broadcast to channels with USMR=NO.

There is no default value.

EXIT=YES | NO

Defines whether the message processing exit (ESFMSG0) must be called for this message.

• YES—Call ESFMSGO for this message.
• NO—Do not call ESFMSGO for this message.

If you specify YES, the exit ESFMSG0 must be present in the ESFMAIN load-module.

There is no default value.

SDIREQ = YES | NO

This parameter defines whether a Service Plus Help desk issue must be opened when this message is issued.

• Yes—Open a Service Plus HelpDesk issue.
• No—Do not open a Service Plus HelpDesk issue.

This parameter has no meaning if SDI=NO has been specified or is taken as a default.

ROUTCDE=(x,x,x,x......)

This parameter defines which routing codes are to be assigned to the message. You can assign up to 16 routing codes to each message. If more than one code is to be assigned, they must be in parenthesis and separated by commas.

The lower limit is 1 and the upper limit is 16. The default value is the value specified by statement ROUTCDE.