Previous Topic: How You Filter Messages

Next Topic: Sysplex Considerations

How You Make Messages Eligible for External Routing

Typically, CA MIC does not allow local messages destined only for the system log to be routed externally. Hardcopy-only messages are recorded to the local SYSLOG, but are not displayed at local consoles. To make these messages eligible for external routing, specify the command SETOPTION CAPTURELOG=YES on the system where the messages are generated. When you use CAPTURELOG=YES, local messages that are marked as system log messages (also known as hardcopy-only) can be routed externally. When you use CAPTURELOG=NO, no hardcopy-only messages are routed externally from this system.

When NOLOG is specified on a collection set, hardcopy-only messages are not collected, even if CAPTURELOG=YES is specified on the system where the messages originate.

You can specify that you want to collect hardcopy-only messages that do not match any other criteria, by using the LOGONLY parameter on the COLLECT command. If you specify LOGONLY, and no other COLLECT criteria, then every hardcopy-only message generated on the systems from which you are collecting messages is sent to that collection set, provided those systems have CAPTURELOG=YES set.

NOLOG and LOGONLY are collection set selection criteria, like MSGID. The inclusion parameters, ANY and ALL, affect NOLOG and LOGONLY the way they affect MSGID. NOLOG and LOGONLY are not opposites of each other, but are mutually exclusive, meaning that you cannot specify both on the same COLLECT command. The following examples show you how to specify collection sets for routing hardcopy-only messages:

Note: Routing hardcopy-only messages to external systems significantly increases the number of messages processed by CA MIC. This results in an increase in overhead and storage used by the CA MIC address space.