CONSOLE statement

The CONSOLE statement specifies the forwarding of z/OS console messages to a syslog server. CONSOLE statements might be used to define one or more message sets–types of messages that are related in some way.

Example

They might all have a message prefix of IGH, or they might all be WTORs, or they might all have a particular route code or some combination of these attributes. Then CONSOLE statements might be used to select one or more message sets for forwarding to the syslog server, the fields of the messages to be forwarded, and optionally filtering to be applied to the messages.

The effect of multiple CONSOLE statements is cumulative. If you code,

CONSOLE SET(A ...)
CONSOLE SET(B ...)
CONSOLE SET(C ...)
CONSOLE SELECT(A)
CONSOLE SELECT(C)
CONSOLE FIELDS(...)

the effect is the same as if you had coded,

CONSOLE SET(A ...) SET(B ...) SET(C ...) +
  SELECT(A C) FIELDS(...)

CONSOLE is ignored by CZASEND.

The former restriction that the SET and SELECT operands of CONSOLE were ignored during the processing of the console command MODIFY CZAGENT,PARMS has been lifted. In other words, CONSOLE is fully supported during MODIFY processing.

Note

Like all BMC AMI Defender features, CONSOLE only forwards messages produced on the LPAR on which BMC AMI Defender is actually running. Due to the effects of JES2 multi access spool (MAS) and sysplex command scope, you might see a particular message on SDSF on a particular LPAR; however, unless that message was actually written on that LPAR it is not seen or processed by BMC AMI Defender on that LPAR.

This section provides information about the following topics:

Related topic

Parameter-file-statements

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*