Wait
    Nowait

    Indicates whether or not the Replicate command should wait for
    activation of the replication server processes before returning
    control to the user.

    Applicable to:              Master and standby databases
    Required or Optional:       Optional
    Default Value:              Wait

    The Wait qualifier has the following effects:

    o  On the master database node-replication waits for activation
       of the server processes on the master database node

    o  On the standby database node-replication waits for activation
       of the server processes on the standby database node

    The following list describes the [No]Wait qualifier:

    o  Wait (default)

       The Replicate command does not return to the user until the
       respective server process has successfully initiated the
       database replication operation. Replication waits indefinitely
       for the activation of the server process, even though
       activation might take substantial time. However, the server
       process might not actually start the replication operation.

    o  Nowait

       Control should be returned to the user as soon as the LCS or
       LRS server process has been invoked by the database monitor.

    You can use the Connect_Timeout qualifier with the Wait qualifier
    to limit the amount of time replication waits for the server
    process to become active.

                                   NOTE

       You must wait for commands that include the Nowait qualifier
       to complete before you enter another command. This is
       because if the first command fails before the subsequent
       command executes, the second command might receive the
       HOTCMDPEND error. For example:

       $ RMU/REPLICATE AFTER_JOURNAL START/NOWAIT mf_personnel
       $ RMU/REPLICATE AFTER_JOURNAL STOP/WAIT mf_personnel

       If the first command to start replication fails, the startup
       error might be returned to the waiting Replicate After_
       Journal Stop command.