1  DISPLAY_AREA_HEADER
   Displays the current storage area file or storage area snapshot
   file header Unique Identifier value for the storage area with the
   specified name or number.

   To execute the DISPLAY AREA_HEADER command, the user must be
   attached to the database which the root and areas belong to,
   either by specifying the database name when issuing the RMU/ALTER
   command or by executing the "ATTACH" command from the "RdbALTER>"
   prompt.
 

2  Format

 (B)0qwqqqqqq>qqqqqwq> AREA_HEADER qwq> area-id qqqwqwqqqqqqq>qqqqqwqqqk
  mq> DISPLAY qj                mq> area-name qj mq> SNAPSHOT qj   x
     lqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
     mqq> UNIQUE_IDENTIFIER

 

2  Arguments
 

3  area_or_id

   Specifies the name or number of the storage area for which you
   want to display the Unique Identifier value.
 

3  SNAPSHOT

   Displays the Unique Identifier value for the .snp file.
 

3  Unique_Identifier

   Specifies that you are displaying the Unique Identifier value for
   the storage area file or storage area snapshot file.
 

2  Examples
   Example 1


   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 root file. He then executes the
   "deposit" commands to designate that the Unique Identifer value
   in the root file is to be moved to the DEPARTMENTS area storage
   and the DEPARTMENTS area snapshot files, displays the Unique
   Identifier value that is to be moved to the DEPARTMENTS area
   storage and the DEPARTMENTS area snapshot files, and finally
   specifies "commit" to actually write the root unique identifier
   value to the DEPARTMENTS area storage and the DEPARTMENTS area
   snapshot files. The display messages designate the pending
   Unique Identifier value as "(marked)" until the user either
   executes "commit" to write out the Unique Identifier value or
   "rollback" to restore the original Unique Identifier value. The
   user then verifies the database changes. The example shows that
   the user can use either the storage area name or the storage area
   identifier number in the root to designate the target storage
   area.

   $ RMU/ALTER MF_PESONNEL
   %RMU-I-ATTACH, now altering database "DEVICE:[DIRECTORY]MF_PERSONNEL.RDB;1"
     DISPLAY ROOT UNIQUE_IDENTIFIER
              Root file unique identifier is: "22-OCT-2010 13:49:28.34"
    (00AA557868CC9F7A)

     DEPOSIT AREA_HEADER DEPARTMENTS UNIQUE_IDENTIFIER
   Area DEPARTMENTS:
   (marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
    (00AA557868CC9F7A)

     DEPOSIT AREA_HEADER 2 SNAPSHOT UNIQUE_IDENTIFIER
   Area DEPARTMENTS:
   (marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
    (00AA557868CC9F7A)

     DISPLAY AREA_HEADER DEPARTMENTS UNIQUE_IDENTIFIER
   Area DEPARTMENTS:
   (marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
    (00AA557868CC9F7A)

     DISPLAY AREA_HEADER 2 SNAPSHOT UNIQUE_IDENTIFIER
   Area DEPARTMENTS:
   (marked) Root file unique identifier is: "22-OCT-2010 13:49:28.34"
    (00AA557868CC9F7A)

     COMMIT
     EXIT
   $ RMU/VERIFY/ALL/NOLOG MF_PERSONNEL