Use the REPAIR command to change the state of transactions.

                                 CAUTION

       The REPAIR command can corrupt data. Use it only if none
       of the resource managers participating in the transaction
       provides a means of changing transaction states.

    Use this command only if none of the resource managers
    participating in the transaction provides a means of changing
    the transaction state. For example, if Rdb is a participant in
    the transaction, do not use REPAIR; use the Rdb Management (RMU)
    utility commands instead. Similarly, if DBMS is a participant,
    use the Database Operator (DBO) utility commands.

    Change the transaction state only when you already know the
    outcome of the transaction and need to manually update the
    transaction log immediately. You might want to do this because,
    for example, you have lost the network link to a remote node.

    When you use the REPAIR command you use qualifiers to specify
    which transactions you want to change. By default, the REPAIR
    command selects all transactions.

    Once you have selected the transactions to change, you enter the
    REPAIR subcommand mode. Within this mode, the prompt changes to
    REPAIR> and you have a set of additional subcommands described
    in Subcommands of the REPAIR Command. You use these commands
    either to manually change the state of the transaction, or
    to select the next transaction that matches your selection
    criteria.  The subcommands are as follows:

    Subcommand  Action

    ABORT       Specifies that a Prepared transaction is to be
                aborted by removing its record from the transaction
                log. This writes a record of type Forgotten for the
                transaction.
                Note that DECdtm services use the presumed abort
                logging protocol.
    COMMIT      Specifies that a Prepared transaction is to be
                committed. This writes a record of type Committed
                for the transaction.
    EXIT        Returns to the LMCP> prompt.
    FORGET      Specifies that a Committed transaction can be removed
                from the transaction log. This writes a record of
                type Forgotten for the transaction.
    NEXT        Displays the next transaction that matches your
                selection criteria.

    LMCP displays each of the selected transactions in turn, so that
    you can change them. For each selected transaction, you can
    either use the ABORT, COMMIT, and FORGET subcommands to change
    the state of the transaction, or use the NEXT subcommand to
    select the next transaction.

    To exit from the REPAIR subcommand mode, enter the EXIT
    subcommand or press Ctrl/Z.