HEARTBEATTIMEOUT

Specifies whether or not heartbeat is enabled. If heartbeat is enabled, this keyword also specifies the heartbeat timeout period.

When heartbeat is enabled, InfoSphere® CDC automatically detects failure between a source environment and target environment and performs a graceful shutdown so that you do not have to terminate replication on the server that did not fail.

The source environment and target environment exchange heartbeat request messages. Either the source environment or target environment must respond within a specified timeout period by sending any message (heartbeat or any other type of message). If the source environment or target environment does not receive a message within the specified timeout period, then a communication or server failure is declared, and replication ends in a controlled manner.

HEARTBEATTIMEOUT=0 disables heartbeat. Any positive integer assigned to HEARTBEATTIMEOUT that is within the acceptable range enables heartbeat and specifies the heartbeat timeout period in minutes. To automatically detect failure, heartbeat must be enabled on both the source environment and target environment. For non-z/OS servers, consult the appropriate InfoSphere CDC documentation for information about supported heartbeat settings and whether it is necessary to enable heartbeat explicitly.

This keyword is optional.

Default Setting—15 minutes

Minimum (Non-Zero) Setting—3 minutes

Maximum Setting—999 minutes