Set_Tsn=(Tsn=n, Csn=m)
    Noset_Tsn

    The Set_Tsn qualifier sets the database transaction sequence
    number (TSN) and commit sequence number (CSN) to the specified
    values. The correct value can be extracted from the original .rdb
    file if it is still accessible, or from the last .aij file if one
    is available. If that fails, you can use a TSN value larger than
    the maximum number of transactions applied to the database since
    it was created, or since TSNs were last initialized.

    The TSN and CSN values do not have to be the same value. However,
    you need to choose new values that are greater than the last
    values assigned to a transaction. Set_Tsn values are expected
    to be multiples of eight. If you specify a value that is not a
    multiple of eight, RMU Restore Only_Root assigns the next highest
    value that is a multiple of eight. (For example, if you specify
    Set_Tsn=(Tsn=90, Csn=90), RMU Restore Only_Root assigns the Next
    TSN a value of 96.)

    The default value for the Set_Tsn qualifier is the TSN and CSN
    values stored in the backup file plus 1,000,000 when TSNs are not
    being initialized. The new TSN and CSN values for most database
    applications should be larger than the number of transactions
    committed since the database was last backed up. Set the TSN
    and CSN values higher than this default increment value plus
    the value in the backup file when needed. You can determine
    the next TSN and CSN values by dumping the .rdb file, using the
    Option=Debug qualifier.

    The TSN and CSN values are each contained in a quadword with the
    following decimal format:

    high longword : low longword

    The high longword can hold a maximum user value of 32768
    (215) and the low longword can hold a maximum user value of

    4,294,967,295 (232). A portion of the high longword is used by

    Oracle Rdb for overhead.

    When you specify a TSN or CSN, you can omit the high longword and
    the colon if the TSN fits in the low longword. For example 0:444
    and 444 are both valid TSN input values.

    The Noset_Tsn qualifier specifies that the root will be restored
    with the same TSN state as was recorded in the backup file.

    When you use the Noset_Tsn qualifier in conjunction with the
    Noupdate_Files qualifier, you can use a backup strategy that uses
    recent by-area full backup files in place of a recent full and
    complete backup file of the entire database. See Example 6 in the
    Examples help entry under this command.

    Note that you cannot use the Initialize_Tsns with the Set_Tsn
    or Noset_Tsn qualifier in the same command. This restriction is
    required because Initialize_Tsns directs RMU Restore Only_Root
    to reset the TSN value to zero, while Set_Tsn directs RMU Restore
    Only_Root to reset the TSN to the value you have indicated, and
    Noset_Tsn leaves the TSN value unchanged.