NAME
   add element - Adds an element to a profile in a name service entry;
                 if the specified entry does not exist, creates the
                 entry.

 SYNOPSIS

   rpccp add element   profile-entry-name -m member {-d | -i if-id
                       [-p  priority]} [-a annotation] [-s  syntax ]

 OPTIONS

   -m        Defines a member name for the profile element to be added
             (required).

   -d        Performs the add element operation on the default profile
             element. With the -d option, the -i and -p options are
             ignored.

   -i        Defines an interface identifier for the profile element to
             be added.  Only one interface can be added in a single
             operation.  An interface identifier is required, unless
 	    the default profile element is being added.  With the -d
  	    option, the -i option is ignored.  The value has the
             following form:

                  interface-uuid,major-version.minor-version

             The UUID is a hexadecimal string and the version numbers
             are a decimal string, for example:

                  -i ec1eeb60-5943-11c9-a309-08002b102989,3.11

             Leading zeros in version numbers are ignored.

   -p        Defines a search priority for the new profile element. The
             priority value is in the range 0 to 7, with zero having
             the highest priority. When a default element is added
             (with the -d option), the -p option is ignored.By default,
             a nondefault element is assigned a priority value of zero.

   -a        Defines an annotation string for the profile element.
             Note that the shell supports quotation marks around the
             annotation field of profile elements, which allows you to
             include internal spaces in an annotation; the control
             program does not.  To specify or refer to annotations from
             within the control program, limit each annotation to an
             unbroken alphanumeric string; for example, CalendarGroup.
             To refer to annotations from the system prompt, do not
             incorporate quotation marks into any annotation.

   -s        Indicates the name syntax of the entry name (optional).
             The only value for this option is the dce name syntax,
             which is the default name syntax. Until an alternative
             name syntax becomes available, specifying the -s option
             is unnecessary.

 ARGUMENTS

   profile-entry-name
         Specifies the entry name of the target profile.  For an entry
         in the local cell, you can omit the cell name and specify only
         the cell-relative name.

 DESCRIPTION

   The add element command adds an element to a profile in a name
   service entry.  The name of the entry containing the profile and
   the entry name of the profile member in the new element are
   required. The entry of a profile may have been created previously
   (by either the add entry or add element command).  But, if the
   specified entry does not exist, the add element command tries to
   create the entry.

   A profile element is a database record containing the following
   fields:

   Interface identifier
         This is the primary search key.  The interface identifier
         consists of the interface UUID and the interface version
         numbers.

   Member name
         The entry name of one of the following kinds of name service
         entries:

           + A server entry for a server offering the requested RPC
             interface and object

           + A group corresponding to the requested RPC interface

           + A profile

   Priority value
         The priority value (0 (zero) is the highest priority; 7 is the
         lowest) is designated by the creator of a profile element to
         help determine the order for using the element. NSI search
         operations select among like priority elements at random.  For
         the rpccp add element command, the default is 0.

   Annotation string
         The annotation string enables you to identify the purpose of
         the profile element. The annotation can be any textual
         information, for example, an interface name associated with
         the interface identifier or a description of a service or
         resource associated with a group.  The annotation string is
         not a search key for the import or lookup operations.

   Privilege Required

   You need both read permission and write permission to the CDS object
   entry (the target profile entry).  If the entry does not exist, you
   also need insert permission to the parent directory.

 NOTE
   This command is replaced at Revision 1.1 by the dcecp command and
   may not be provided in future releases of DCE.

 EXAMPLES
   The following command adds an element to the cell profile,
   /cell-profile, in the local cell:

        $ rpccp
        rpccp> add element  \
        > -i ec1eeb60-5943-11c9-a309-08002b102989,1.1  \
        > -m /.:/Calendar_profile  \
        > -a RefersToCalendarGroups  \
        > /.:/cell-profile

   The following control program commands start the control program,
   set up a user profile associated with the cell profile as its
   default element, and add a user-specific element for the Calendar
   V1.1 interface, as follows:

        $ rpccp
        rpccp>  add element  /.:/LandS/anthro/molly_o_profile  \
        > -d   -m  /.:/cell-profile
        rpccp>
        rpccp>  add element  /.:/LandS/anthro/molly_o_profile  \
        > -m  /.:/LandS/anthro/Calendar_group  \
        > -i  ec1eeb60-5943-11c9-a309-08002b102989,1.1  \
        > -a  Calendar_Version 1.1_Interface
        rpccp>

   The added profile element contains the global name of the member
   (specified using its cell-relative name,
   /.:/LandS/anthro/Calendar_group) and the RPC interface identifier
   for the Calendar Version 1.1 interface.

 RELATED INFORMATION
   Commands: remove element
             remove profile
             show profile