Event classes and attributes

The body of an event contains an event class and the attributes that define the event class.

An event class defines a specific type of Event Integration Facility (EIF) event that a Classic data server sends to an event server.

Event classes

The Classic data server emits EIF events to an event server based on the subscription state, the subscription apply latency, and the heartbeat event. The following table lists each event class, a description of the event class, and the event attributes that define the event class.

Table 1. Event classes
Event class name	Description	Attributes
AA_replication_max_latency_exceeded AA_replication_max_average_latency_exceeded	Emitted when the value of the averaged or non-averaged end-to-end apply latency of a subscription exceeds the specified maximum apply latency threshold time.	adapter host apply_latency_time averaging_time cac_eventmsg cac_eventmsg_id consistency_group consistency_group_total credibility data_source job_name latency_state max_latency_time msg node origin point_in_time_consistency reserved01 - reserved05 severity source_system_id status sysplex_name system_name taskno time_stamp version workload_name workload_type
AA_replication_constrained_latency_exceeded AA_replication_constrained_average_ latency_exceeded	Emitted when the value of the averaged or non-averaged end-to-end apply latency of a subscription exceeds the constrained apply latency threshold time.	adapter_host apply_latency_time averaging_time cac_eventmsg cac_eventmsg_id consistency_group consistency_group_total constrained_latency_time credibility data_source job_name latency_state msg node origin point_in_time_consistency reserved01 - reserved05 severity source_system_id status sysplex_name system_name taskno time_stamp version workload_name workload_type
AA_replication_critical_latency_exceeded AA_replication_critical_average_latency_exceeded	Emitted when the value of the averaged or non-averaged end-to-end apply latency of a subscription exceeds the critical apply latency threshold time.	adapter_host apply_latency_time averaging_time cac_eventmsg cac_eventmsg_id consistency_group consistency_group_total credibility critical_latency_time data_source job_name latency_state msg node origin point_in_time_consistency reserved01 - reserved05 severity source_system_id status sysplex_name system_name taskno time_stamp version workload_name workload_type
AA_replication_discrete_latency_exceeded	Emitted when the value of the non-averaged end-to-end apply latency of a subscription exceeds the discrete apply latency threshold time.	adapter_host apply_latency_time cac_eventmsg cac_eventmsg_id consistency_group consistency_group_total credibility data_source discrete_latency_time job_name latency_state msg node origin point_in_time_consistency reserved01 - reserved05 severity source_system_id status sysplex_name system_name taskno time_stamp version workload_name workload_type
AA_replication_heartbeat	Emitted at the frequency established by the value of the heartbeat apply latency threshold time.	adapter_host apply_latency_time averaging_time cac_eventmsg cac_eventmsg_id commits consistency_group consistency_group_total credibility data_source heart_beat_time job_name latency_state max_latency_time msg node origin point_in_time_consistency reserved01 - reserved05 severity source_system_id status subscription_name sysplex_name system_name taskno time_stamp version workload_name workload_type
AA_replication_reset_latency_met AA_replication_reset_average_latency_met	Emitted when the value of the averaged or non-averaged end-to-end apply latency of a subscription falls below the reset apply latency threshold time, after previously exceeding the maximum apply latency threshold time.	adapter host apply_latency_time cac_eventmsg cac_eventmsg_id consistency_group consistency_group_total credibility data_source job_name latency_state msg node origin point_in_time_consistency reserved01 - reserved05 reset_latency_time severity source_system_id status sysplex_name system_name taskno time_stamp version workload_name workload_type
AA_replication_workload_down	Emitted by the target server when a subscription transitions to the state SUB_STATE_REPL_INACTIVE	adapter host apply_latency_time cac_eventmsg cac_eventmsg_id consistency_group consistency_group_total credibility data_source job_name latency_state msg node origin point_in_time_consistency reserved01 - reserved05 severity source_system_id status subscription_state sysplex_name system_name taskno time_stamp version workload_down_method workload_name workload_type
AA_replication_workload_up	Emitted by the target server when a subscription transitions to the state SUB_STATE_CONTINUOUS.	adapter host apply_latency_time cac_eventmsg cac_eventmsg_id consistency_group consistency_group_total credibility data_source job_name latency_state msg node origin point_in_time_consistency reserved01 - reserved05 severity source_system_id status subscription_state sysplex_name system_name taskno time_stamp version workload_name workload_up_method workload_type

Event attributes

The following tables list the event attributes, a description of the attributes, and examples of attribute values.

Table 2. Event attributes
Attribute name	Description	Value
adapter_host	The host on which the adapter, the Classic source or target data server, is running.	`Adapter host`
averaging_time	The time across which apply latency times are averaged. When the averaging time is zero, no averaging is performed and the event is emitted if a single instance exceeds a threshold. When the averaging time is greater than zero, apply latency times are averaged across that time span. The apply latency times are then compared against the thresholds to determine whether or not to emit an event.	`Averaging time`
apply_latency_time	The end-to-end apply latency time.	`Apply latency time`
cac_eventmsg_id	The ID of the event message that the Classic data server emits from which the EIF event was adapted.	Event message ID. For example: 0x0101008C
commits	The number of transactions in the averaged end-to-end apply latency sample set.	`Number of committed transactions`
consistency_group	The name of the subscription. Same as the subscription_name attribute.	`Consistency group name`
consistency_group_total	When a value is supplied for the GDPSWORKLOADNAME configuration parameter, the consistency_group_total identifies the number of subscriptions that are defined in the target server. By default, the value is 1.	`1 or the number of subscriptions that are defined in the CECSUB file.`
constrained_latency_time	The latency threshold to which the apply latency time is compared to determine if a constrained latency exceeded event should be emitted..	`Constrained latency threshold time`
credibility	The credibility indicates how the adapter sends the event. The value 0 indicates that the event is sent from a non-Tivoli® Management Environment (TME) adapter.	0
critical_latency_time	The apply latency threshold time to which the apply latency time is compared to determine if a critical latency exceeded event should be emitted.	`Critical latency threshold time`
data_source	Indicates the type of data being replicated.	VSAM
discrete_latency_time	The apply latency threshold time to which the apply latency time is compared to determine if a discrete latency exceeded event should be emitted.	`Discrete latency threshold time`
heart_beat_time	The apply latency threshold heartbeat time.	`Heartbeat time`
job_name	The job name of the Classic data server where the event originated.	Job name
latency_state	Based on where the apply latency time falls in relation to the setting of the apply latency threshold values, the latency state can be one of the following: Normal Constrained Critical Acute	`Latency state`
max_latency_time	The apply latency threshold time to which the apply latency time is compared.	`Maximum latency threshold time`
msg	A message that describes the event in text format.	This message varies depending on the event. Possible values: The replication workload is up. The replication workload is down. The replication workload’s end-to-end apply latency has exceeded its maximum apply latency threshold. The replication workload’s average end-to-end apply latency has exceeded its maximum apply latency threshold. The replication workload’s end-to-end apply latency has fallen below its reset apply latency threshold. The replication workload’s average end-to-end apply latency has fallen below its reset apply latency threshold. The replication workload’s end-to-end apply latency has exceeded its critical apply latency threshold. The replication workload’s average end-to-end apply latency has exceeded its critical apply latency threshold. The replication workload’s end-to-end apply latency has exceeded its constrained apply latency threshold. The replication workload’s average end-to-end apply latency has exceeded its constrained apply latency threshold. The replication workload’s apply latency heartbeat. The replication workload’s end-to-end apply latency has exceeded its discrete apply latency threshold.
node	The ASID of the Classic data server.	ASID. For example: 1300
origin	The IP address or host name of the source system.	IP address. For example: 10.1.1.2
point_in_time_consistency	The current point-in-time of the data source.	The absolute bookmark of the subscription in the format: yyyy-mm-dd-hh.mm.ss.uuuuuu. For example: 2012-02-28-13.42.53.969000.
reserved01	Reserved
reserved02	Reserved
reserved03	Reserved
reserver04	Reserved
reserved05	Reserved
reset_latency_time	The apply latency threshold time to which the apply latency time is compared to determine if a reset latency met event should be emitted.	`Reset latency threshold time`
severity	The severity of the event. The value INFO indicates that the severity of the event is informational.	INFO
source	The source of the event that defines the adapter type.	Replication engine adapter.
source_system_id	The ID that the source server assigns to the subscription.	`Source system ID`
status	The severity of the event. The value OPEN indicates that the severity of the event is open.	OPEN
subscription_name	The name of the subscription.	Subscription name. For example: PAYROLL
subscription_state	The state of the subscription.	SUB_STATE_REPL_CONTINUOUS or SUB_STATE_INACTIVE
sysplex_name	The name of the sysplex on which the event occurred.	`Sysplex name`
system_name	The name of the system on which the event occurred.	`System name`
taskno	The task number indicates the TCB address of the service task where the event originated.	Task number. For example: 9001272
time_stamp	The time at which the replication engine generated the event.	Timestamp, in the format: yyyy-mm-dd-hh.mm.ss.uuuuuu. For example: 2012-02-28-13.42.53.969000
transaction_id	The identification of the transaction whose end-to-end apply latency time exceeded the discrete latency threshold.	Transaction ID. For example: '000000000001D730IM1A 54bc6d3f'
version	The version of the EIF event.	Version. For example: 1.
workload_down_method	Identifies why the AA_replication_workload_down was entered.	Operator or Failed.
workload_name	When no value is supplied for the GDPSWORKLOADNAME configuration parameter, the workload_name is set to the subscription name. Otherwise, it contains the value supplied for the GDPSWORKLOADNAME configuration parameter.	`Workload name`
workload_type	The type of workload.	Possible values: Active/Standby Active/Query

For additional information about event classes and attributes, see the product information for Tivoli Enterprise Console.