NAME

export - Exports binding information for interface identifiers or object UUIDs to a server entry

SYNOPSIS

rpccp export entry-name {{[-i if-id] | [-o object-uuid] ...} -b string-binding ...}
[-s syntax]

OPTIONS

-i if-idDeclares the interface identifier of a remote procedure call (RPC) interface.  The export command operates on only one ­-i option; if you enter more than one, the command ignores all but the last interface identifier.  If you specify an interface identifier, you must specify at least one -b option.  The ­-i and ­-o options can occur together or separately, but one of them is necessary. 

The interface identifier takes the following form:

interface-uuid,major-version.minor-version

The version numbers are optional, but if you omit a version number, the value defaults to 0.  The Universal Unique Identifier (UUID) is a hexadecimal string and the version numbers are decimal strings, as in the following example:

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

Leading zeros in version numbers are ignored. 

-o object-uuidDeclares the UUID of an object.  Each export command accepts up to 32 ­-o options.  The -i and ­-o options can occur together or separately, but one of them is necessary. 

The UUID is a hexadecimal string, as in the following example:

-o 3c6b8f60-5945-11c9-a236-08002b102989

-b  string-binding
Declares a string binding (optional). To use this option, you must also specify an interface identifier (using the ­-i option).  Each command accepts up to 32 ­-b options. 

The value has the form of an RPC string binding, without an object UUID.  The binding information contains an RPC protocol sequence, a network address, and sometimes an endpoint within brackets, as follows:

rpc-prot-seq:network-addr[endpoint]

For a well-known endpoint, include the endpoint in the string binding, as in the following example:

-b ncadg_ip_udp:63.0.2.17[5347]

For a dynamic endpoint, omit the endpoint from the string binding, for example:

-b ncacn_ip_tcp:16.20.15.25

Note that depending on your system, string binding delimiters such as [ ] (brackets) may need to be preceded by a \ (backslash) or placed within ’ ’ or " " (single or double quotation marks).  Requirements vary from system to system, and you must conform to the usage rules of a system. 

-s syntaxIndicates 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

entry-nameSpecifies the name of the target name service entry.  Usually, the target is a server entry.  However, objects also can be exported (without an interface identifier or any binding information) to a group or a profile. 

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

DESCRIPTION

The export command places binding information and an interface identifier, object UUIDs, or both into a server entry, or the command object UUIDs into a group’s entry.  The export command searches the name service database for the entry with the specified entry name.  If the entry exists, the command uses it; otherwise, the command tries to create a new name service entry using the specified entry name. 

Minimally, the command requires the name of the entry and either an identifier and binding string or an object. 

If the specified entry does not exist, the export command tries to create the entry. 

Privileges Required

You need both r (read) and w (write) permission to the Cell Directory Service (CDS) object entry (the target name service entry).  If the entry does not exist, you also need i (insert) permission to the parent directory. 

NOTES

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

EXAMPLES

     1.The following  example shows  a control  program export command  that is stored in a file for later execution from the system prompt.  The command exports two objects and an interface with two string bindings to the server entry /.:/LandS/anthro/Cal_host_3 in the local cell. 

# file to export Calendar 1.1 at installation time
rpccp export  \
  -i ec1eeb60-5943-11c9-a309-08002b102989,1.1  \
  -b ncacn_ip_tcp:16.20.15.25  \
  -b ncadg_ip_udp:63.0.2.17  \
  -o 30dbeea0-fb6c-11c9-8eea-08002b0f4528  \
  -o 16977538-e257-11c9-8dc0-08002b0f4528  \
  /.:/LandS/anthro/Cal_host_3

     2.The  following  example  shows the  use  of  a  user-defined  environment variable as an interface identifier, to facilitate entering an export command interactively (in this case, from inside the control program).  The two initial shell commands set up an environment variable Calendar_1_1, which represents the interface identifier of an RPC interface.  The rpccp command then starts the control program, and the export command exports the Calendar interface and two string bindings to the server entry /.:/LandS/anthro/Cal_host_2 in the local cell. 

Calendar_1_1=ec1eeb60-5943-11c9-a309-08002b102989,1.1
export Calendar_1_1
rpccp
rpccp> export  -i Calendar_1_1 -b ncacn_ip_tcp:16.20.15.25  \
       -b ncadg_ip_udp:63.0.2.17 /.:/LandS/anthro/Cal_host_2

     3.The  following  example   shows  the   use  of  user-defined environment variables for object UUIDs to facilitate entering an export command interactively (in this case, from inside the control program).  The initial shell commands set up the environment variables LUKE_CAL and JOSH_CAL, which represent personal calendars that are accessible as objects to an RPC server.  The rpccp command then starts the control program, and the export command exports the two objects to the server’s entry /.:/LandS/anthro/Cal_host_2 in the local cell. 

LUKE_CAL=30dbeea0-fb6c-11c9-8eea-08002b0f4528
export LUKE_CAL
JOSH_CAL=16977538-e257-11c9-8dc0-08002b0f4528
export JOSH_CAL
rpccp
rpccp> export  -o LUKE_CAL -o JOSH_CAL /.:/LandS/anthro/Cal_host_2

RELATED INFORMATION

Commands:

rpccp_import(8rpc), rpccp_show_server(8rpc), rpccp_unexport(8rpc).