Use the RESTORE command to copy portions of the  directory  hierarchy
 and their related data definitions from a backup file into the CDD.

 You specify where to restore the information  in  the  CDD.   If  the
 backup  file  contains  history lists, access control lists, or both,
 DMU restores them also.   With  the  RESTORE  command  you  have  the
 following options:

  o  To generate  history  list  entries  in  the  CDD  to  audit  the
     restoration

  o  To  generate  a  log  of  the  restored  dictionary  directories,
     subdictionaries, and objects

  o  To restore files for subdictionaries


 Command Syntax:

 RESTORE [qualifiers] file-specification [path-name]

Additional information available:

parametersprivilegesqualifiers

 file-specification

 Names the backup file.  Use the standard VMS file specification.  The
 default file extension is .BAK.

 path-name

 Specifies the dictionary directory or subdictionary  into  which  you
 are  restoring  the  information.  If you are using a terminal of the
 VT200 family, you can use 8-bit characters in path names.  You cannot
 use any wildcards in the path name.

 If you omit the path name, the information is added to  your  current
 default directory.

 Type "HELP specify path-name" for further information.

  o  You need PASS_THRU and EXTEND at each  dictionary  directory  and
     subdictionary as it is restored.

  o  You need PASS_THRU and UPDATE at each dictionary object as it  is
     restored.

  o  You need HISTORY at each dictionary directory, subdictionary,  or
     object for which you specify /AUDIT.

  o  To restore access control lists included in the backup file,  you
     need    CONTROL    at   each   restored   dictionary   directory,
     subdictionary, or object.

Additional information available:

/AUDIT/LOG/STAGE/SUBDICTIONARY/VERSION

 Syntax:

     /AUDIT [= (quoted-string [, quoted-string]...)]
     /AUDIT=file-specification
     /NOAUDIT

 Use /AUDIT to create history list entries auditing the restoration of
 a  portion  of  the CDD directory hierarchy.  Entries are made in the
 history lists of each restored dictionary  directory,  subdictionary,
 and object.

 You can include explanatory text in history  list  entries  in  three
 ways:

  o  By specifying the /AUDIT qualifier.  If  you  include  no  quoted
     string or file-specification, DMU provides a default history list
     entry describing your operation.

  o  By including quoted  strings.   Enclose  each  quoted  string  in
     double  quotation  marks,  and  enclose  the series of strings in
     parentheses.  The parentheses are optional if  you  specify  only
     one quoted string.

  o  By specifying a file whose contents are to  be  included  in  the
     history  list  entry.   The  file specification is a standard VMS
     file specification, and the default file type is .DAT.   You  can
     include  no  more  than 64 input strings in a history list entry.
     DMU ignores any excess.

 With /NOAUDIT, no history list entries are created.  The  default  is
 /NOAUDIT.

 Syntax:

     /LOG [= file-specification]
     /NOLOG

 Use /LOG to create  a  list  of  the  given  names  of  all  restored
 dictionary directories, subdictionaries, and objects.

 The file specification is a standard VMS  file  specification  naming
 the  file  into  which  the log is written.  The default file type is
 .LOG.  If you use /LOG without specifying a file, DMU writes the  log
 to SYS$OUTPUT.  With /NOLOG, no list is created.

 The default is /NOLOG.

 Syntax:

     /[NO]STAGE

 Use /STAGE to withhold committing changes in the CDD until the entire
 restoration is completed.  Use /NOSTAGE to make changes in the CDD as
 each dictionary directory,  subdictionary,  or  object  is  restored.
 /NOSTAGE is the default.

 Using /STAGE assures that no changes remain in the  dictionary  if  a
 command   is  interrupted.   However,  with  /STAGE,  execution  time
 increases   exponentially   with   the   number    of    directories,
 subdictionaries, and objects restored.

 With /NOSTAGE, execution time increases linearly with the  number  of
 directories,  subdictionaries,  or objects restored.  However, if you
 interrupt an unstaged RESTORE command, some of the changes remain  in
 the dictionary.

 Syntax:

     /[NO]SUBDICTIONARY

 Use /SUBDICTIONARY to restore subdictionaries as subdictionaries with
 their   original   file   names.   Use  /NOSUBDICTIONARY  to  restore
 subdictionaries as directories.

 /NOSUBDICTIONARY is the default.

 Syntax:

     /[NO]VERSION

 Use /VERSION to restore an object to a directory in which there is an
 object with the same name.  If you do not use the /VERSION qualifier,
 DMU will not restore an object whose name is the same as the name  of
 an already existing object.

 Use /NOVERSION to guarantee that you are not creating  an  additional
 version  of an object when you do not intend to do so.  /NOVERSION is
 the default.

 The results of using the /VERSION qualifier  vary  depending  on  the
 existing children of the destination directory.

  o  RESTORE/VERSION restores an object to a destination directory  if
     the destination directory does not already contain an object with
     the same name and same version number as the object in the backup
     file.   The  restored  object  has the same version number as the
     object in the backup file.

  o  RESTORE/VERSION restores an object to a destination directory and
     issues an informational message if the destination directory does
     not already contain an object with the same name and same version
     number  as  the object in the backup file, but it does contain an
     object with the same name  and  a  higher  version  number.   For
     example,  the backup file contains TEST_REC;2 and the destination
     directory contains only TEST_REC;3.   DMU  restores  the  object,
     giving  it  the same name and version number as the object in the
     backup file, and issues an informational message.

  o  RESTORE/VERSION does not restore an  object  if  the  destination
     directory  contains  an  object  with  the  same name and version
     number as an object in the backup file.  For  example,  DMU  does
     not  restore  TEST_REC;2  if  the  destination  directory already
     contains an object named TEST_REC;2.


 By default, a restored version of  an  object  has  the  same  access
 control  list and history list as the highest existing version of the
 object in the destination directory.  If the access control  list  is
 included  in  the backup file, it will be restored with the object if
 you have CONTROL privilege at the highest  existing  version  of  the
 object in the destination directory.