Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rpc_register_mgr(3ncs) [ultrix man page]

rpc_register_mgr(3ncs)													    rpc_register_mgr(3ncs)

Name
       rpc_register_mgr - register a manager (server only)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$register_mgr(type, ifspec, sepv, mepv, status)
       uuid_$t *type;
       rpc_$if_spec_t *ifspec;
       rpc_$generic_epv_t sepv;
       rpc_$mgr_epv_t mepv;
       status_$t *status;

Arguments
       type		   The UUID of the type being registered.

       ifspec		   The interface being registered.

       sepv		   The generic EPV, a vector of pointers to server stub procedures.

       mepv		   The manager EPV, a vector of pointers to manager procedures.

       status		   The completion status.  If the completion status returned in is equal to status_$ok , then the routine that supplied it
			   was successful.

Description
       The routine registers the set of manager procedures that implement a specified interface for a specified type.

       Servers can invoke this routine several times with the same interface (ifspec) and generic EPV (sepv) but  with	a  different  object  type
       (type) and manager EPV (mepv) on each invocation.  This technique allows a server to export several implementations of the same interface.

       Servers	that  export several versions of the same interface (but not different implementations for different types) must also use not Such
       servers should supply uuid_$nil as the type to

       If a server uses to register a manager for a specific interface and a specific type that is not nil, the server must  use  to  register	an
       object.

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$op_rng_error   The requested operation does not correspond to a valid operation in the requested interface.

       rpc_$unk_if	   The	requested interface is not known.  It is not registered in the server, the version number of the registered inter-
			   face is different from the version number specified in the request, or the UUID in the request does not match the  UUID
			   of the registered interface.

       rpc_$too_many_ifs   The	maximum  number  of interfaces is already registered with the RPC runtime library; the server must unregister some
			   interface before it registers an additional interface.

       rpc_$not_in_call    An internal error.

       rpc_$you_crashed    This error can occur if a server has crashed and restarted.	A client RPC runtime library sends the error to the server
			   if  the  client  makes  a  remote  procedure  call before the server crashes, then receives a response after the server
			   restarts.

       rpc_$proto_error    An internal protocol error.

       rpc_$illegal_register
			   You are trying to register an interface that is already registered and you are using an EPV different from the one used
			   when  the  interface  was  first registered.  An interface can be multiply registered, but you must use the same EPV in
			   each routine.

Files
See Also
       intro(3ncs), rpc_register(3ncs), rpc_register_object(3ncs), rpc_unregister(3ncs)

															    rpc_register_mgr(3ncs)

Check Out this Related Man Page

rpc_clear_server_binding(3ncs)											    rpc_clear_server_binding(3ncs)

Name
       rpc_clear_server_binding - unset the binding of an RPC handle to a server (client only)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$clear_server_binding(handle, status)
       handle_t handle;
       status_$t *status;

Arguments
       handle		   The RPC handle whose binding is being cleared.

       status		   The completion status.  If the completion status returned in is equal to status_$ok , then the routine that supplied it
			   was successful.

Description
       The routine removes the association between an RPC handle and a particular server (that is, a particular port number), but does not  remove
       the associations with an object and with a host (that is, a network address).  This call replaces a fully bound handle with a bound-to-host
       handle.	A bound-to-host handle identifies an object located on a particular host but does not identify a server exporting an interface	to
       the object.

       If  a  client  uses  a bound-to-host handle to make a remote procedure call, the call is sent to the Local Location Broker (LLB) forwarding
       port at the host identified by the handle.  If the call's interface and the object identified by the handle are both  registered  with  the
       host's  LLB, the LLB forwards the request to the registering server.  When the client RPC runtime library receives a response, it binds the
       handle to the server.  Subsequent remote procedure calls that use this handle are then sent directly to the bound server's port.

       The routine is useful for client error recovery when a server dies.  The port that a server uses when it restarts is  not  necessarily  the
       same port that it used previously; therefore, the binding that the client was using may not be correct.	This routine enables the client to
       unbind from the dead server while retaining the binding to the host.  When the client sends a request, the binding is automatically set	to
       the server's new port.

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$not_in_call    An internal error.

       rpc_$proto_error    An internal protocol error.

Files
See Also
       intro(3ncs), rpc_bind(3ncs), rpc_clear_binding(3ncs), rpc_set_binding(3ncs)

														    rpc_clear_server_binding(3ncs)
Man Page