The REPCMD command line utility is a program that can be used to pause and resume the replications, get replication status, and start intial states on replications.

The REPCMD utility is in the replication\consumer folder and must be run from the machine where the replication controller is installed. The REPCMD program is tied to the local replication controller. To use the commands with a different controller, you must use the REPCMD program local to the other controller.

This lists all deployed replications and their current state.

This pauses all replications. A success return means that the message is sent to the controller. After the command is sent, you can do a status call to see the state of the controller.

This starts all paused replications. A success return means that the message is sent to the controller. After the command is sent, you can do a status call to see the state of the controller.

This starts an initial state on the selected replication(s). After the initial state request is sent, you can send a status command to see the progress of the initial states.

When running an initial state request with Windows PowerShell, you might need to use quotes around the command statement. For example:

or

The command to start an initial state uses the Replication ID found in the CONNX Replication Administrator. If an Adabas to Adabas replication is added through the Adabas commands and not with the Replication Administrator, it will not have a Replication ID to perform an initial state. On such replications, you can return Status, but not start initial state. To get a replication ID for the new Adabas to Adabas replication, open the Replication Administrator, and go to the Server Status tab to sync up the Replications. Then perform a deploy to send the new Replication ID to the controller. When this is done, a repcmd /status command will show the Replication ID for the Adabas to Adabas replication and you can use the initial state command.