Choosing the correct data capture agent for your installation depends on your environment and data capture latency properties (near-real-time vs asynchronous) as shown in the following table.
Note: Even though the capture latency is near-real-time, applying the changed data to target datastores is dependent on network latency, target datastore performance and if required, external schedulers controlling the Publisher and/or Engines. It is highly recommended that continuous stream processing whenever possible to minimize the impact on source system logging and transient data storage.
| Data Capture Agent | Module Name | Near Real Time | Async |
| Db2 Log Reader Capture | SQDDB2C | Y | Y |
| IMS Capture | |||
| IMS Log Reader Capture | SQDIMSC | Y | Y |
| IMS TM EXIT Capture | SQDICDCL | Y | Y |
| UDB (Db2/LUW) Log Reader Capture | SQDUDBC | Y | Y |
| Oracle LogMiner Capture | SQDLOGM | Y | Y |
| VSAM Log Capture | SQDAREQC | Y | Y |
| Keyed File Compare Capture | SQDDFCDC | N | Y |
Note: The IMS TM Exit Capture agent is a Database Exit and consequently adds NO overhead to IMS Logging. This exit provides the highest level of performance for demanding applications delivering microsecond performance levels in the Real World. It is the only viable solution for IMS FastPath databases involved in Active/Active Replication, where a Log based capture would quadruple the size of the IMS Log.