Qualifiers

/ALLOCATION
      /ALLOCATION=n

   Specifies the initial number of blocks to be allocated to each of
   the specified directories. The default allocation is 1 block.

   This qualifier is useful for creating large directories, for
   example MAIL.DIR;1. It can improve performance by avoiding the
   need for later dynamic expansion of the directory.

   This qualifier does not apply to Files-11 ODS-1, ODS-3, or ODS-4
   volumes.


/LOG
      /LOG
      /NOLOG (default)

   Controls whether the CREATE/DIRECTORY command displays the
   directory specification of each directory after creating it.


/OWNER_UIC
      /OWNER_UIC=option

   Requires SYSPRV (system privilege) privilege for a user
   identification code (UIC) other than your own.

   Specifies the owner UIC for the directory. The default is your
   UIC. You can specify the keyword PARENT in place of a UIC to mean
   the UIC of the parent (next-higher-level) directory. If a user
   with privileges creates a subdirectory, by default, the owner
   of the subdirectory will be the owner of the parent directory
   (or the owner of the MFD, if creating a main level directory).
   If you do not specify the /OWNER_UIC qualifier when creating a
   directory, the command assigns ownership as follows: (1)  if you
   specify the directory name in either alphanumeric or subdirectory
   format, the default is your UIC (unless you are privileged, in
   which case the UIC defaults to the parent directory); (2)  if you
   specify the directory in UIC format, the default is the specified
   UIC.

   Specify the UIC by using standard UIC format as described in the
   OpenVMS User's Manual.


/PROTECTION
      /PROTECTION=(ownership[:access][,...])

   Specifies protection for the directory.

   o  Specify the ownership parameter as system (S),  owner (O),
      group (G),  or world (W).

   o  Specify the access parameter as read (R),  write (W), execute
      (E),  or delete (D).

   The default protection is the protection of the parent directory
   (the next-higher level directory, or the master directory for
   top-level directories) minus any delete (D) access.

   If you are creating a first-level directory, then the next-
   higher-level directory is the MFD. (The protection of the MFD
   is established by the INITIALIZE command.)

   For more information on specifying protection code, see the VSI
   OpenVMS Guide to System Security.


/VERSION_LIMIT
      /VERSION_LIMIT[=n]

   Sets the maximum number of versions that files in the directory
   can have. If you do not set a version limit, a value of 0 is used,
   indicating that the number of file versions is limited only to the
   Files-11 architectural limit of 32,767.

   If you change the version limit for a directory, the new version
   limit applies only to files created after the change has been made.
   When creating a file, if the total number of versions of that file
   name exceeds the specified version limit, then the file with the
   lowest version number is deleted from the directory without
   notification to the user.

   The version limit set on a directory has no effect on the version
   limit set on a particular file in that directory. To set a
   version limit on a particular file in a directory, use the
   SET FILE/VERSION_LIMIT[=n] command.

   To view the version limit on a directory, use the DIRECTORY/FULL
   command on a directory file and look at the File Attributes
   field of the output.


/VOLUME
      /VOLUME=n

   Requests that the directory file be placed on the specified
   relative volume of a multivolume set. By default, the file is
   placed arbitrarily within the multivolume set.