CONSOLxx members of PARMLIB contain statements that can affect the routing and hardcopying of messages.

During WTO processing, the route codes defined by the DEFAULT statement are applied to unsolicited messages which have been issued without route codes, without descriptor codes, or without a console ID or console name.

If the ROUTCODE parameter is not supplied on the DEFAULT statement, route codes 1-16 are applied.

Message Flood Automation can affect the processing of messages whose route codes are defined by DEFAULT processing just like messages that have been issued with route codes, descriptor codes or console routing information.

Specifying the MSGFLD parameter on the CONSOLxx INIT statement allows a MSGFLDxx parmlib member to be automatically loaded and optionally enabled during system initialization. This eliminates the need for an operator or automation to enter a SET MSGFLD=xx command, followed by a SETMF ON command to initialize Message Flood Automation. For more details, see z/OS MVS Initialization and Tuning Reference.

The HARDCOPY statement defines the route codes of the messages that are subject to being hardcopied. Messages with route codes 1, 2, 3, 4, 7, 8, 10 and 42 are always hardcopied whether the ROUTCODE parameter is supplied on the HARDCOPY statement or not.

Message Flood Automation can affect the hardcopying of messages that have been forced to hardcopy by HARDCOPY processing just like messages that were explicitly issued to hardcopy.