| #### rpcentry export Transfers information to the specified entry in the name service. The syntax is: rpcentry export entry_name_list {[-object object_uuid_list] [-interface interface_id -binding string_binding_list]} Options -object object_uuid_list Declares the UUID of an object. Accepts a list of up to 32 object UUIDs. The UUID is a hexadecimal string. See Data Structures for the format of the object UUID. -interface interface_id Declares the interface identifier of one RPC interface. If you specify an interface identifier, you must specify at least one -binding option. See Data Structures for the format of the interface identifier. -binding string_binding_list Declares a list of one or more protocol sequences (RPC bindings). To use this option, you must also specify an interface identifier (using the -interface option). See Data Structures for the format of a protocol sequence. Description The rpcentry export operation transfers information to the specified entry in the name service. The argument is a list of one or more names of server entries to be exported to. If an entry does not exist, it is created. Uses the -interface, -binding, and -object options to specify what to export. This operation returns an empty string on success. Privileges Required To export an entry, you need both r (read) permission and w (write) permission to the CDS object entry (the target name service entry). If the entry does not exist, you also need i (insert) permission to the parent directory. Examples This example uses the dcecp string syntax to export an RPC entry to CDS: dcecp> rpcentry export /.:/subsys/applications/bbs_server \ > -interface {458ffcbe-98c1-11cd-bd93-0000c08adf56 1.0} \ > -binding {ncacn_ip_tcp 130.105.1.227} \ > -object {76030c42-98d5-11cd-88bc-0000c08adf56} dcecp> ####