NAME

rpc_ns_mgmt_entry_delete - Deletes an entry from the name service database

Used by management applications. 

SYNOPSIS

#include <dce/rpc.h>
void rpc_ns_mgmt_entry_delete(

unsigned32 entry_name_syntax ,
unsigned_char_t ∗entry_name ,
unsigned32 ∗status );

PARAMETERS

Input

entry_name_syntaxAn integer value that specifies the syntax of argument entry_name.  To use the syntax specified in the RPC_DEFAULT_ENTRY_SYNTAX environment variable, provide the integer value rpc_c_ns_syntax_default. 

entry_nameSpecifies the name of the entry to delete.  This can be either the global or cell-relative name. 

Output

statusReturns the status code from this routine.  This status code indicates whether the routine completed successfully or, if not, why not.  The possible status codes and their meanings are as follows:

rpc_s_okSuccess. 

rpc_s_entry_not_foundName service entry not found. 

rpc_s_incomplete_nameIncomplete name. 

rpc_s_invalid_name_syntaxInvalid name syntax. 

rpc_s_name_service_unavailable
Name service unavailable.

rpc_s_no_ns_permissionNo permission for name service operation. 

rpc_s_not_rpc_entryNot an RPC entry. 

rpc_s_unsupported_name_syntax
Unsupported name syntax.

DESCRIPTION

The rpc_ns_mgmt_entry_delete routine removes an RPC entry from the name service database. 

Management applications use this routine only when an entry is no longer needed, such as when a server is permanently removed from service.  If the entry is a member of a group or profile, it must also be deleted from the group or profile. 

Use this routine cautiously.  Since name service databases are designed to be relatively stable, the frequent use of the rpc_ns_mgmt_entry_delete routine can result in the following difficulties:

       •Performance problems Creating and deleting entries in client or server applications causes the name service to repeatedly remove and replace the same entry in the name service database. This can lead to performance problems in replicated name service databases.

       •Lost entry updates When multiple applications access a single entry through different replicas of a name service database, updates to the entry can be lost. In this situation, if one application deletes the entry and another application updates the entry before the replicas are synchronized, the delete operation takes precedence over the update operation. When the replicas are synchronized, the update is lost because the entry is deleted from all replicas.

Permissions Required

You need read permission to the CDS object entry (the target name service entry).  You also need delete permission to the CDS object entry or to the parent directory. 

NOTE:

For this release, the RPC naming service (rpc_ns) routines are not implemented, nor is an independent naming service provided. 

RETURN VALUES

None. 

RELATED INFORMATION

Functions: rpc_ns_mgmt_entry_create(3)