IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

PIPE COREVENT
Syntax
COREVENT:
COREVENT event_type
timer retry_interval
Command Description
The COREVENT stage takes a message or MSU from the primary input stream and
takes information from it that can be used for state correlation. A correlation event
is built from the message or MSU and sent from the pipe stage to the DSICORSV
subtask for correlation processing. The original message or MSU is passed onto the
primary output stage of the pipe. In most cases, the pipe discards the original
message or MSU after it has been sent off for correlation processing. If the event
cannot be sent to the DSICORSV task, error message BNH785I is generated and
placed on the secondary output stream.
Streams
Stream Type Number Supported
Input 1
Output 2
Termination Conditions
COREVENT terminates when the primary input stream or output stream is
disconnected.
Operand Descriptions
Usage Notes
PIPE COREVENT
event_type:
Indicates a name that is used to describe the resulting correlation event. This
name is used in the correlation rule base to indicate that a rule applies to this
event.
timer
Indicates (in seconds) how long to wait for a correlation reply before
discarding the event. This parameter overrides the PURGETIMER value in the
CNMSTYLE member.
retry_interval
Indicates (in seconds) how long the DSICORSV task keeps retrying to send the
event to the correlation engine in UNIX System Services if there are
communication problems with the correlation engine. This parameter overrides
the RETRYTIMER value in the CNMSTYLE member.
v The following information from messages is used by default when building an
event:
– The date of the message
– The message ID
Chapter 2. Pipeline Stages and Syntax 47