Example 1

    The following example shows how to enter a new unique_identifier
    value using RMU/ALTER.

    $ RMU/ALTER MF_PERSONNEL
    %RMU-I-ATTACH, now altering database
     "DEVICE:[DIRECTORY]MF_PERSONNEL.RDB;1"
      DEPOSIT ROOT UNIQUE_IDENTIFIER = NEW
    (marked) Root file unique identifier is: "22-OCT-2010 13:49:31.72"
     (00AA55786ACFB115)
      COMMIT
      EXIT

    Example 2

    The following example shows that RMU/ALTER is invoked specifying
    the database MF_PERSONNEL.RDB. The user then displays the current
    Unique Identifier value in the database root, creates a new
    Unique Identifier value in the database root, displays the new
    Unique Identifier in the root, and finally specifies "commit"
    to write the new Unique Identifier value to the database root
    file and ALL database storage area files. The display messages
    designate the pending new Unique Identifier value as "(marked)"
    until the user either executes "commit" to write out the new
    Unique Identifier value or "rollback" to restore the original
    Unique Identifier value. The user then verifies the database
    changes.

    $ RMU/ALTER MF_PERSONNEL
    %RMU-I-ATTACH, now altering database "DISK:[DIRECTORY]MF_PERSONNEL.RDB;1"
      DISPLAY ROOT UNIQUE_IDENTIFIER
             Root file unique identifier is: "22-OCT-2010 13:49:27.87"
     (00AA5578688428BB)
      DEPOSIT ROOT UNIQUE_IDENTIFIER = NEW
    (marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
     (00AA557868CC9F7A)
      DISPLAY ROOT UNIQUE_IDENTIFIER
    (marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
     (00AA557868CC9F7A)
      COMMIT
      EXIT
    $ RMU/VERIFY/ALL/NOLOG MF_PERSONNEL