Client applications can post events to Connection Manager
or to other clients by inserting event information into the sysrepstats pseudo
table. Client applications can register events using the sysmaster
pseudo table sysrepevtreg, and receive event data by issuing
select or fetch statements against the sysrepstats pseudo table.
By posting events to the sysrepstats, you can issue
control messages to Connection Manager without having to directly connect to Connection Manager
itself.
When Connection
Manager registers that it wishes to receive events, it passes a bitmap
of the event types that it wants to receive. As events are received,
they are posted to the thread that placed the request.
Event Classes
The following table lists
each event class, its bit value, and a description of the event class.
Table 1. Event Classes
| Event class name |
Bit value |
Description |
| REPEVT_CLUST_CHG |
0x1 |
Event class for High-Availability cluster
changes |
| REPEVT_CLUST_PERFSTAT |
0x2 |
Event class for workload statistics
for the server nodes in a High-Availability cluster |
| REPEVT_CLUST_LATSTAT |
0x4 |
Event class for replication latency
information for server nodes in a High-Availability cluster |
| REPEVT_CM_ADM |
0x8 |
Connection Manager administration commands |
| REPEVT_SRV_ADM |
0x10 |
Event class for server mode changes |
| REPEVT_ER_ADM |
0x20 |
Event class for events related to Enterprise
Replication (ER) |
| REPEVT_CLIENT |
0x40 |
User-defined client event |
Sub-events for the Event Class REPEVT_CLUST_CHG
The
following table lists sub-events for the event class REPEVT_CLUST_CHG:
Table 2. Sub-events for the Event Class REPEVT_CLUST_CHG
| Sub-event name |
Value |
Description |
Event available at: |
| REPEVT_SUB_CLUST_ADD |
1 |
Adding new node to a High-Availability cluster |
Only at primary server in a High-Availability cluster |
| REPEVT_SUB_CLUST_DROP |
2 |
Dropping a node from a High-Availability cluster |
Only at primary server in a High-Availability cluster |
| REPEVT_SUB_CLUST_CON |
3 |
High-Availability secondary node connected to primary
server |
Only at primary server in a High-Availability cluster |
| REPEVT_SUB_CLUST_DIS |
4 |
High-Availability secondary node disconnected from
primary server |
Only at primary server in a High-Availability cluster |
| REPEVT_SUB_CLUST_NEWPRIM |
5 |
High-Availability primary node changed |
Only at secondary servers in a High-Availability
cluster |
| REPEVT_SUB_CLUST_DROFF |
6 |
HDR secondary node disconnected from primary server |
HDR primary and secondary servers |
| REPEVT_SUB_CLUST_DRON |
7 |
HDR secondary node connected to primary server |
HDR primary and secondary servers |
Sub-events for the Event Class REPEVT_CLUST_PERFSTAT
The
following table lists sub-events for the event class REPEVT_CLUST_PERFSTAT:
Table 3. Sub-events for the Event Class REPEVT_CLUST_PERFSTAT
| Sub-event name |
Value |
Description |
Event available at: |
| REPEVT_ SUB_LOCAL_PERFSTAT |
1 |
Work load statistics for local server |
All servers in a High-Availability cluster |
| REPEVT_ SUB_REMOTE_PERFSTAT |
2 |
Work load statistics for High-Availability secondary
servers |
Only at the primary server in a High-Availability
cluster |
Sub-events for the Event Class REPEVT_CLUST_LATSTAT
The
following table lists sub-events for the event class REPEVT_CLUST_LATSTAT:
Table 4. Sub-events for the Event Class REPEVT_CLUST_LATSTAT
| Sub-event name |
Value |
Description |
Event available at: |
| REPEVT_SUB_LOCAL_LATSTAT |
1 |
Replication latency statistics for secondary servers
in a High-Availability cluster |
Only at the primary server in a High-Availability
cluster |
Sub-events for the Event Class REPEVT_CM_ADM
The
following table lists sub-events for the event class REPEVT_CM_ADM:
Table 5. Sub-events for the Event Class REPEVT_CM_ADM
| Sub-event name |
Value |
Description |
Event available at: |
| REPEVT_SUB_CM_ADM_REQ |
1 |
Command request |
All Informix® server
instances |
| REPEVT_SUB_CM_ADM_ACK |
2 |
Command response |
All Informix server
instances |
| REPEVT_SUB_CM_REG |
3 |
Connection Manager registered with server |
All Informix server
instances |
| REPEVT_SUB_CM_DEREG |
4 |
Connection Manager de-registered with server |
All Informix server
instances |
| REPEVT_SUB_CM_FATAL |
5 |
Connection Manager terminated without de-registering
with server |
All Informix server
instances |
Sub-events for the Event Class REPEVT_SRV_ADM
The
following table lists sub-events for the event class REPEVT_SRV_ADM:
Table 6. Sub-events for the Event Class REPEVT_SRV_ADM
| Sub-event name |
Value |
Description |
Event available at: |
| REPEVT_ SUB_SRV_BLK |
1 |
Server blocked due to DDRBLOCK |
All Informix server
instances |
| REPEVT_ SUB_SRV_UBLK |
2 |
Server unblocked; DDRBLOCK removed |
All Informix server
instances |
Sub-events for the Event Class REPEVT_ER_ADM
The
following table lists sub-events for the event class REPEVT_ER_ADM:
Table 7. Sub-events for the Event Class REPEVT_ER_ADM
| Sub-event name |
Value |
Description |
Event available at: |
| REPEVT_SUB_ER_SPOOL_FULL |
1 |
ER blocked while waiting for space to be added
in either the queue data sbspace or dbspace, or in the grouper paging
sbspace. |
Enterprise Replication server nodes |