If you want to reinitialize a particular transfer, the transfer
    definition must be associated with your UIC, or you must have
    the DBCTRL or ALTER transfer privilege, or the OpenVMS BYPASS
    privilege.

    You can reinitialize a transfer only when the transfer is in
    the suspended state. To suspend a transfer, first issue a STOP
    TRANSFER statement. You must execute the REINITIALIZE TRANSFER
    statement outside the scope of a transaction. If you issue this
    statement when a transaction is outstanding, Replication Option
    returns an error message.

    After you enter the REINITIALIZE statement, the transfer remains
    in the suspended state. You must then issue a START TRANSFER
    statement to restart the transfer.

    The REINITIALIZE TRANSFER statement has different effects
    depending on the type of replication transfer being reinitialized
    and whether the transfer is TO NEW or TO EXISTING:

    o  For a standard replication transfer created with SQL to an
       existing database, REINITIALIZE TRANSFER forces the next
       execution of the transfer to drop all target tables and create
       new target tables rather than update the tables with changed
       data.

    o  For a replication transfer created with the NO DELETE
       attribute using SQL, REINITIALIZE TRANSFER forces the next
       execution of the transfer to drop all rows in the target
       tables except those whose dbkey has been set to zero. Any row
       whose dbkey has not been set to zero is copied to the target
       database from the source database.

    o  For a replication transfer specifying TO NEW FILENAME
       target-file-spec created with SQL, or for any RDO transfer
       definition, new versions of the target database files are
       created and all tables specified in the transfer definition
       and their corresponding rows will be copied from the source
       database to the target database.