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

    You can use the START TRANSFER statement without any qualifiers
    to change the state of a suspended transfer. Issuing the START
    TRANSFER statement places the transfer in the scheduled state
    if a schedule definition exists for the transfer. Execution then
    occurs at the next scheduled time. If a schedule definition does
    not exist, the transfer is placed in the unscheduled state and
    will execute only when you issue a START TRANSFER statement using
    the NOW qualifier or you define a schedule for the transfer.

    If you specify both the NOW and WAIT arguments and your transfer
    has an epilogue procedure, Replication Option waits for the
    epilogue procedure to finish before resuming execution.

    You cannot enter the START TRANSFER statement when a transaction
    is outstanding. You must terminate any outstanding transactions
    before issuing the START TRANSFER statement.

    You can use the START TRANSFER statement to initiate a transfer
    on demand by including the NOW option. The NOW option immediately
    places the transfer in the active state. This execute-on-demand
    feature is useful in batch processing environments when you
    want to initiate the transfer after another job has completed
    successfully, regardless of the transfer's schedule.

    When you define a one-time-only transfer schedule and specify
    a transfer time that has already passed, issuing a START
    TRANSFER statement changes the transfer status from suspended
    to scheduled. However, when you issue a SHOW TRANSFER STATUS
    statement, the "next transfer to be executed" phrase is not
    included. To avoid this problem and cause the transfer to
    execute, use the START TRANSFER NOW statement.

    Do not issue a START TRANSFER NOW WAIT statement when RDO is
    attached to a source database and the transfer is either a
    replication transfer that has not finished or a replication
    initialization transfer. Instead, issue a FINISH statement to
    detach from the database, and then enter the START TRANSFER NOW
    WAIT statement. Otherwise, the copy process waits indefinitely
    for you to release the source database. Because you specified
    that you want to wait for the copy process to complete, the
    transfer operation will never complete.