OSF DCE Application Development Guide--Core Components

RPC and Other DCE Components

Step 3: Proﬁle attribute

If the binding and group attributes do not lead to compatible binding

information, the search continues by reading the proﬁle attribute, if present;

if the directory service entry lacks a proﬁle attribute, the search fails.

The search operation identiﬁes all the proﬁle elements containing the

requested interface identiﬁer and searches them in the order of their priority,

beginning with the 0 (zero) priority elements. Proﬁle elements of a given

priority are searched in random order. For the selected proﬁle element, the

search reads the member name and goes to the corresponding directory

service entry. There, the search resumes at step 1. Unless a proﬁle element

leads the search to compatible binding information, the search eventually

looks at all the proﬁle elements with the requested interface identiﬁer, one by

one, until none remain.

If the starting entry does not contain NSI attributes, or if none of the steps satisﬁes the

search, the search operation returns the status code rpc_s_no_more_bindings to the

client.

Note: The inquire next (inq_next) operations for objects, groups, or proﬁles

look at only the entry speciﬁed in its corresponding inquire begin

(inq_begin) operation. The search ignores nested groups or nested

proﬁles.

Figure 14-12 illustrates the three steps of the import_next and lookup_next search

operations.

124245 Tandem Computers Incorporated 14− 29