You can issue DEFINE REPOSITORY on a local (host) machine, but
    not on a remote (client) machine.

    To make your repository available to remote users, perform the
    following steps:

    1. Ask your system manager to make the ALTERNATE_ROOT directory
       a DFS access point. This action makes the directory and
       subdirectories known to a DFS server.

    2. Issue the DEFINE REPOSITORY command, including an ALTERNATE_
       ROOT parameter. This action permanently associates the
       file directories with the anchor directory. You should not
       explicitly refer to the file directories again. For example:

       DEFINE REPOSITORY DEV1:[PROJECT.CDD]
         ALTERNATE_ROOT DEV2:[PROJECT.FILES]

       For backup purposes, you can choose to move your anchor
       directory to the DFS disk where you store your file
       directories. In this case, you specify the same logical name
       for both anchor and ALTERNATE_ROOT directories. For example:

       DEFINE REPOSITORY DEV1:[PROJECT.CDD]
         ALTERNATE_ROOT DEV1:[PROJECT.FILES]

    To access a repository from a host machine, perform the following
    steps:

    1. Ask your system manager to make the DFS access point available
       on your system. During the DFS mount, the manager identifies
       the access point by the ALTERNATE_ROOT logical name. For
       example, if the DEFINE REPOSITORY command issued at the host
       machine referred to ALTERNATE_ROOT DEV1:[PROJECT.FILES], the
       manager refers to DEV1.

    2. Issue a SET DEFAULT command that includes the full node name
       of the anchor directory. For example:

       SET DEFAULT A_NODE::DEV1:[PROJECT.CDD]

    3. Review the default protection you receive on file directories.
       DFS does not support remote specification of file ACLs. You
       must make any modifications on the host system.