Bind makes  a  VMS  or  ULTRIX  file  system  (logical_filesystem)
  available to UCX software clients.  Once a logical filesystem  has
  been bound, the entire filesystem or  any  of  its  subdirectories
  may be exportable to NFS clients.  Refer to the ADD EXPORT command
  for information on specifying exportable files.

  An NFS client can mount a UCX File System or a subdirectory  of  a
  UCX  File  System  into  his  local file system.  The  target  UCX
  File System must first be bound by the VMS system manager via  the
  BIND command.

  Format:
    BIND logical_filesystem  "UCX_Filesystem_name"

  where:

  logical_filesystem
        is one of the following:
           o  a VMS device  name  representing  a  VMS  volume,  for
              example: MYHOST$DUA1:

           o  a device and directory containing an ULTRIX filesystem
              (CFS container file), for example:
              HOST$DUA0:[ULT_FILESYS]

  UCX_Filesystem_name
        is the name to  be  given to the  logical  filesystem.  This
        file system name is the reference name which will be used by
        an ULTRIX client accessing files  within  the  file  system.

  NOTE: If the file system is to be available on all hosts of a  VMS
        VAXcluster, then the file system must be bound on each  host.

Additional information available:

Examples

  A.  BIND MYHOST$DUA1:  "/DISK@VMS"

      Declares MYHOST$DUA1:, a VMS device, to be  a  VMS-style  UCX
      file system known as 'DISK@VMS'.  File operations on any file
      within this file system  will  adhere  to  the  VAX/VMS  file
      system rules.

  B.  BIND HOST$DUA0:[ULT_FILES]  "/ruser"

      Declares  HOST$DUA0:[ULT_FILES]ULT_FILES.CONTAINER,   a   CFS
      container file, to be an ULTRIX-style UCX file  system  known
      as  'ruser'.  File  operations  on  any  file   within   this
      filesystem will adhere to the ULTRIX file system rules.