| ### Object Entries An object is any real resource - like a disk, application, or node - that is given a CDS name. When an object name is created, client applications and the CDS software supply attributes to be stored with the name. An attribute, consisting of an attribute name and value(s), describes a particular operational property of an object. The name and its attributes make up the object entry. When a client application requests a lookup of the name, CDS returns the value of the relevant attribute or attributes. Object entries are typically created and managed through a client application interface. For example, the DCE control program and the Name Service Interface (NSI) of the RPC runtime let users create entries that represent RPC servers, groups, and profiles. These are special kinds of entries that enable an RPC application to locate and select servers. (See the OSF DCE Application Development Guide for details on how RPC uses CDS for this purpose.) You can also create object entries through the DCE control program (dcecp). (See the OSF DCE Command Reference for information on the commands that allow you to create and manage object entries using the dcecp program. Every object can have a defined class, which is an optional attribute of the object entry. DCE components that use the Directory Service can define their own object classes and supply class-specific attributes for the Directory Service to store on their behalf. Class-specific attributes have meaning only to the particular class of objects with which they are associated. The clearinghouse object entry represents a special class of object that is predefined by CDS. A clearinghouse object entry serves as a pointer to the location of a clearinghouse in the network. CDS needs this pointer so that it can look up and update data in a clearinghouse. When you create a clearinghouse, CDS creates its clearinghouse object entry automatically. The clearinghouse object entry acquires the same name as the clearinghouse. The clearinghouse object entry is like any other object entry in that it describes an actual resource, but it is different because it is solely for internal use by CDS. Clearinghouses can only be created in the cell root directory. Therefore, all clearinghouse object entries are stored in the cell root directory. CDS itself updates and manages clearinghouse object entries when necessary. They do not require any external management except in rare problem-solving situations. (See your vendor for help in these situations.) ###