Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ rpccp_add_mapping(8rpc) — DCE 3.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

add mapping(8rpc)  —  Maintenance

NAME

add mapping - Adds or replaces server address information in the local endpoint map

SYNOPSIS

rpccp add mapping -b string-binding -i interface-identifier [-a annotation-string]
[-o object-uuid] ... [-N]

OPTIONS

-b string-binding
Specifies a string representation of a binding over which the server can receive remote procedure calls.  At least one binding is required.

The value has the form of an remote procedure call (RPC) string binding, without an object Universal Unique Identifier (UUID), as in the following example:

-b ncadg_ip_udp:63.0.2.17[5347]

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. 

-i interface-identifier
Specifies an interface identifier to register with the local endpoint map. An interface identifier is required. Only one interface can be added (that is, registered) in a single operation. The interface identifier has the following form:

interface-uuid,major-version.minor-version

The UUID is a hexadecimal string and the version numbers are decimal strings, as in the following example:

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

Leading zeros in version numbers are ignored. 

-a annotation-string
Specifies a character string comment to be applied to each cross product element that is added to the local endpoint map.  The string can be up to 64 characters long, including the NULL terminating character.

The string is used by applications for informational purposes only.  The RPC runtime does not use this string to determine which server instance a client communicates with, or for enumerating endpoint map elements. 

-o object-uuid
Defines an object UUID that further determines the endpoint map elements that are removed (optional). Each add mapping command accepts up to 32 ­-o options. 

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

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

-NSpecifies that existing elements in the local host’s endpoint map should not be replaced when the new information is added. 

DESCRIPTION

The add mapping command adds to or replaces server address information in the local endpoint map. 

Each element in the local endpoint map logically contains the following:

       •An interface ID, consisting of an interface UUID and versions (major and minor)

       •Binding information

       •An object UUID (optional)

       •An annotation string (optional)

This command should be used without the ­-N option when only a single instance of the server in question runs on the server’s host.  Do not use the ­-N option if no more than one server instance on the host ever offers the same interface UUID, object UUID, and protocol sequence. 

When local endpoint map elements are not replaced, obsolete elements accumulate each time a server instance stops running without explicitly unregistering its endpoint map information.  Periodically, the RPC daemon rpcd will identify these obsolete elements and remove them.  However, during the interval between these removals, the presence of the obsolete elements increases the chance that clients will receive endpoints to nonexistent servers.  The clients will then waste time trying to communicate with these servers before giving up and obtaining another endpoint. 

Allowing rpcd to replace any existing local endpoint map elements (by not specifying -N) reduces the chance of this happening. 

For example, suppose an existing element in the local endpoint map matches the interface UUID, binding information exclusive of the endpoint, and object UUID of an element this routine provides.  The routine changes the endpoint map according to the elements’ interface major and minor version numbers. 

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

The following command adds a map element to the local endpoint map.  The command adds the map element that contains the specified interface identifier, server address (specified as a string binding), and object UUIDs. 

rpccp add mapping -i ec1eeb60-5943-11c9-a309-08002b102989,1.1 \
  -b ncadg_ip_udp:63.0.2.17[5347] -o 005077d8-8022-1acb-9375-10005a4f533a \
  -o 001bc29a-8041-1acb-b377-10005a4f533a -a ’Calendar version 1.1’

This command adds the following elements:

interface IDec1eeb60-5943-1169-a309-08002b102989,1.1

string bindingncadg_ip_udp:63.0.2.17[5347]

objects005077d8-8022-1acb-9375-10005a4f533a
001bc29a-8041-1acb-b377-10005a4f533a

annotationCalendar version 1.1

RELATED INFORMATION

Commands:

rpccp_export(8rpc), rpccpremove_mapping(8rpc), rpccpshow_mapping(8rpc), rpccpshow_server(8rpc)

Subroutines: rpc_ep_register(3rpc), rpc_ep_register_no_replace(3rpc)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026