rpc_mgmt_ep_unregister(3rpc)
Removes server address information from an endpoint map
Used by management applications.
Synopsis
#include <dce/rpc.h>
void rpc_mgmt_ep_unregister(
rpc_binding_handle_t ep_binding,
rpc_if_id_t *if_id,
rpc_binding_handle_t binding,
uuid_t *object_uuid,
unsigned32 *status);
Parameters
Input
ep_binding
Specifies the host whose local endpoint map elements you unregister (that is, remove). To remove elements from the same host as the calling application, specify
NULL.
To remove local endpoint map elements from another host, specify a server binding handle for that host. You can specify the same binding handle you are using to make other remote procedure calls. The object UUID associated with this parameter must be a nil UUID. If you specify a non-nil UUID, the routine fails with the status code ept_s_cant_perform_op. Other than the host information and object UUID, all information in this parameter is ignored.
if_id
Specifies the interface identifier to remove from the local endpoint map.
binding
Specifies the binding handle to remove.
object_uuid
Specifies an optional object UUID to remove.
The value NULL indicates there is no object UUID to consider in the removal.
Output
status
Returns the status code from this routine. This status code indicates whether the routine completed successfully or, if not, why not.
Description
The rpc_mgmt_ep_unregister( ) routine unregisters (that is, removes) an element from a local endpoint map. A management program calls this routine to
remove addresses of servers that are no longer available, or to remove addresses of servers that support objects that are no longer offered.
Use this routine cautiously; removing elements from the local endpoint map may make servers unavailable to client applications that do not already have a fully bound binding handle to the server.
A management application calls the rpc_mgmt_ep_inq_next( ) routine to view local endpoint map elements. The application can then remove the elements using the rpc_mgmt_ep_unregister( ) routine.
Return Values
No value is returned.
Errors
The following describes a partial list of errors that might be returned. Refer to the OSF DCE Problem Determination Guide for complete descriptions of all error messages.
rpc_s_ok
Success.
ept_s_cant_access
Error reading the endpoint database.
ept_s_cant_perform_op
Cannot perform the requested operation.
rpc_s_comm_failure
Communications failure.
ept_s_database_invalid
Endpoint map database is invalid.
ept_s_invalid_entry
Invalid database entry.
ept_s_not_registered
No entries found.
ept_s_update_failed
Update failed.
rpc_s_invalid_binding
Invalid binding handle.
rpc_s_no_interfaces
No interfaces registered.
rpc_s_wrong_kind_of_binding
Wrong kind of binding for operation.
Related Information
Functions: rpc_ep_register(3rpc)
rpc_ep_register_no_replace(3rpc)
rpc_mgmt_ep_elt_inq_begin(3rpc)
rpc_mgmt_ep_elt_inq_done(3rpc)
rpc_mgmt_ep_elt_inq_next(3rpc)