(c) Digital Equipment Corporation. 1994. All rights reserved.

Name

ds_intro − This reference page introduces the X/OPEN Directory Services (XDS) functions. 
 
 
 

Syntax

#include <xom.h>
 
#include <xds.h>
 
 
 

Description

 
This reference page lists the XDS interface functions supported in this product.  XDS provides a C language binding.

Function@Description  
 
 
ds_abandon@T{ Abandons an outstanding asynchronous operation.  T} ds_add_entry@T{ Adds a leaf entry to the Directory Information Tree (DIT).  T} ds_bind@T{ Opens a session with a directory user agent.  T} ds_compare@T{ Compares a purported attribute value with the attribute value stored in the directory for a particular entry.  T} ds_initialize@T{ Initializes the interface.  T} ds_list@T{ Enumerates the immediate subordinates of a particular directory entry.  T} ds_modify_entry@T{ Performs an atomic modification of a directory entry.  T} ds_modify_rdn@T{ Changes the Relative Distinguished Name (RDN) of a leaf entry.  T} ds_read@T{ Queries information on a directory entry by name T} ds_receive_result@T{ Retrieves the result of an asynchronously executed operation T} ds_remove_entry@T{ Removes a leaf entry from the DIT T} ds_search@T{ Finds entries of interest in a portion of the DIT T} ds_shutdown@T{ Shuts down the interface T} ds_unbind@T{ Unbinds from a directory session T} ds_version@T{ Negotiates features of the interface and service T} dsX_trace_object@T{ Displays an explanation of the content of an object T}

DCE Notes

 
 
 
The DEC X.500 Directory Service supports asynchronous operations, which the Distributed Computing Environment (DCE) XDS interface does not. Thus, the Abandon and Receive Result functions are included in the Digital product.
 

 
The differences between the X.500 Directory Service and the Cell Directory Service (CDS) are as follows:
 
 
 

•All functions operate on the X.500 name space. 
 

•CDS does not support the Modify RDN or Search functions.  The Service-Error unwilling-to-perform is returned if either function is attempted on CDS. 
 

•
 CDS does not support the X.500 schema.  Therefore, CDS does not have:
 
 
 

•The concept of an object class
 

•Mandatory attributes for a given object
 

•A set of attributes expressly permitted for a given object
 

•A predefined definition of single and multivalued attributes
 
 

 The absence of the schema means that the usual errors, which are returned by X.500 for breach of the rules, are not returned by CDS. 
 
 

•
 The CDS naming Directory Information Tree (DIT) is modeled on a typical file system architecture, in which directories are used to store objects and can contain subdirectories.  Leaf objects in the CDS DIT are similar to X.500 naming objects.  However, subtree objects are called directories as in a file system directory.  All new objects must be added to an existing directory.  CDS directory objects cannot be added, removed, modified, or compared using the XDS programming interface.
 
 

•
 In CDS, the naming attribute of an object is not stored in the object.  Consequently, in CDS the Read operation never returns this attribute, and the Compare operation applied to this attribute returns with the Attribute-Error  constraint-violation. 
 
 

 
See the notes in the relevant reference page for function-specific differences.