Db2 Mirror exit points
Exit points for Db2® Mirror actions provide application developers with a programmatic solution for important changes in Db2 Mirror.
The preclone and postclone exit points provide a mechanism for application providers to automate actions that need to occur before or after a Db2 Mirror clone operation.
The software reclone exit point is called when synchronization is complete for a Db2 Mirror software reclone for SYSBAS or any database IASP.
The role change exit point is called when a node changes from primary to secondary or vice versa. It can also be used to indicate the source of the role change.
The replication state change exit point is called whenever the replication state changes between ACTIVE and TRACKING or ACTIVE and BLOCKED.
The replication detail change exit point is called whenever the replication state changes and also whenever the replication detail changes, for example between SYNCHRONIZING and REPLICATING.
The generic versioning exit point is called when a user supplied active version within the Mirror Version List (MVL) is changed. This exit point allows for the version entries to be refreshed with the most recent versions available.
| Exit point | Exit point format | Description |
|---|---|---|
| QIBM_QMRDB_PRECLONE | PREC0100 | Db2 Mirror ASP preclone |
| QIBM_QMRDB_POSTCLONE | PSTC0100 | Db2 Mirror ASP post-clone |
| QIBM_QMRDB_ROLE_CHG | RCHG0100 | Db2 Mirror replication role change |
| RCHG0200 | ||
| QIBM_QMRDB_SOFTCLONE | SFTC0100 | Db2 Mirror ASP post software reclone |
| QIBM_QMRDB_STATE_CHG | SCHG0100 | Db2 Mirror replication state change |
| SCHG0200 | ||
| QIBM_QMRDB_VERSION | VERI0100 | Db2 Mirror generic versioning |
For complete details on these exit points, view Monitoring by using exit points.