rpccp_add_mapping man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

add mapping(1m)						       add mapping(1m)

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 annota‐
       tion-string] [-o object-uuid] [-N]

OPTIONS
       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 RPC	 string	 binding,  without  an	object
       UUID, for 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  an  escape  symbol  (\)  or
       placed  within  quotation  marks (' ' or `` ''). Requirements vary from
       system to system, and you must conform to the usage rules of a  system.
       Specifies  an  interface identifier to register with the local endpoint
       map.  An interface identifier is required.  Only one interface  can  be
       added  (i.e., registered) in a single operation.	 The interface identi‐
       fier has the following form: interface-uuid,major-version.minor-version

       The UUID is a hexadecimal string and the version	 numbers  are  decimal
       strings, for example: -i ec1eeb60-5943-11c9-a309-08002b102989,1.1

       Leading	zeros  in  version numbers are ignored.	 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.
       Defines	an  object  UUID that further determines the endpoint map ele‐
       ments that are removed (optional). Each add mapping command accepts  up
       to 32 -o options.

       The    UUID    is    a	 hexadecimal	string,	   for	 example:   -o
       3c6b8f60-5945-11c9-a236-08002b102989 Specifies 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,  replaces,  or	 adds  server  address
       information to the local endpoint map.

       Each  element  in the local endpoint map logically contains the follow‐
       ing: Interface ID, consisting of an interface UUID and versions	(major
       and  minor)  Binding  information  Object  UUID	(optional)  Annotation
       (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 Dae‐
       mon (RPCD) will identify these obsolete elements and remove them.  How‐
       ever,  during  the interval between these removals, the presence of the
       obsolete elements increases the chance that clients will	 receive  end‐
       points 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 end‐
       point, 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.

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 operates from the system prompt to add a map ele‐
       ment 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' $

       The     previous	    command	adds	 the	following    elements:
       ec1eeb60-5943-1169-a309-08002b102989,1.1	  ncadg_ip_udp:63.0.2.17[5347]
       005077d8-8022-1acb-9375-10005a4f533a		   001bc29a-8041-1acb-
       b377-10005a4f533a Calendar version 1.1

RELATED INFORMATION
       Commands:  export(1m),  remove  mapping(1m),  show  mapping(1m),	  show
       server(1m)

       Subroutines: rpc_ep_register, rpc_ep_register_no_replace

							       add mapping(1m)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net