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

    You must terminate any outstanding transactions before you issue
    a STOP TRANSFER statement.

    If you want to stop a particular transfer, the transfer
    definition must be associated with your UIC.

    A transfer cannot occur until you remove it from the suspended
    state using the START TRANSFER statement. If the transfer is in
    the active state, the STOP TRANSFER statement also stops the copy
    process associated with that transfer. After you stop a currently
    executing extraction, extraction rollup, or initial replication
    transfer, you cannot access the partially created target database
    unless you restart the transfer.

    If a replication update transfer is executing and you stop the
    transfer, users of the target database can continue their work
    unaffected. Furthermore, stopping the transfer does not stop
    the capture of the changes in the source database (written to
    RDB$CHANGES). The changes are transferred to the target database
    when the transfer is restarted. No updates to the target database
    are missed as a result of stopping a replication transfer for
    which the target relations have already been created. However,
    since stopping a transfer does not stop the capture of record
    changes, changes continue to be written to RDB$CHANGES regardless
    of a transfer's state. Records are added to RDB$CHANGES even
    for transfers that are suspended for a long time. The number of
    records in RDB$CHANGES and the overall size of the database both
    continue to grow.