The control program supports logical names.  Using logical names
   facilitates interactive use of the control program.

   To distinguish logical names, rpccp* reference pages follow the
   convention of using all uppercase letters for examples of logical
   names.  Note that OpenVMS logical names are NOT case sensitive.

   User-defined logical names

        You can set a logical name to represent values to rpccp.
        Using a logical name is helpful for specifying a long string
        such as the following:

          + A string representation of binding information (binding
            string)

          + A string representation of an object or interface UUID
            (string UUID)

          + An interface identifier (the interface UUID and version
            numbers)

          + The name of a name service entry

          For example, in the following example, the logical name
          JANE_CAL represents an object UUID; the target name service
          entry, /.:/LandS/anthro/Cal_host_2, is in the local cell:

               $ DEFINE JANE_CAL 47f40d10-e2e0-11c9-bb29-08002b0f4528

               $ rpccp
               rpccp> export  -o JANE_CAL /.:/LandS/anthro/Cal_host_2

   DCE RPC logical names

          The dce name syntax is the only syntax currently supported
          by the DCE Cell Directory Service (CDS). However, the Name
          Service Interface (NSI) is independent of any specific name
          service and, in the future, may support name services that
          use other name syntaxes.  When alternative name syntaxes are
          supported, you can override the standard default with a
          process-specific default by setting the
          RPC_DEFAULT_ENTRY_SYNTAX logical name. When this variable is
          set for a process, the control program uses it to find out the
          default syntax for the process. You can override this default
          in any NSI command of the control program by using the -s
          option to specify an alternative entry syntax.  Setting
          RPC_DEFAULT_ENTRY_SYNTAX requires specifying the integer 3 to
          indicate the dce syntax.  To set RPC_DEFAULT_ENTRY_SYNTAX, use
          the name=value command to define a logical name.  The following
          command specifies dce as the default name syntax in a login
          command file:

                       # .login command file
                       # setting dce as default name syntax,
                       RPC_DEFAULT_ENTRY_SYNTAX=3

        RPC_DEFAULT_ENTRY
              For the import command, you can use this environment
              variable to indicate the entry where the search operation
              starts.  Usually, the starting entry is a profile.