rpc_ns_binding_lookup_begin(3) — Subroutines

NAME

rpc_ns_binding_lookup_begin - Creates a lookup context for an interface and an object in the name service database

Used by client applications.

SYNOPSIS

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

unsigned32 entry_name_syntax ,
unsigned_char_t ∗entry_name ,
rpc_if_handle_t if_handle ,
uuid_t ∗object_uuid ,
unsigned32 binding_max_count ,
rpc_ns_handle_t ∗lookup_context ,
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 value rpc_c_ns_syntax_default.

entry_nameSpecifies the entry name at which the search for compatible binding handles begins. This can be either the global or cell-relative name. To use the entry name found in the RPC_DEFAULT_ENTRY environment variable, supply NULL or a null string (\0) for this argument. When this entry name is used, the RPC runtime automatically uses the default name syntax specified in the RPC_DEFAULT_ENTRY_SYNTAX environment variable.

if_handleA stub-generated data structure specifying the interface to look up. If the interface specification has not been exported or is of no concern to the caller, specify NULL for this argument. In this case the bindings returned are only guaranteed to be of a compatible and supported protocol sequence and contain the specified object UUID. The desired interface might not be supported by the contacted server.

object_uuidSpecifies an optional object UUID. If you specify NULL or a nil UUID for this argument, the returned binding handles contain one of the object UUIDs exported by the compatible server. If the server did not export any object UUIDs, the returned compatible binding handles contain a nil object UUID. For a non-nil UUID, compatible binding handles are returned from an entry only if the server has exported the specified object UUID. Each returned binding handle contains the specified non-nil object UUID.

binding_max_countSets the maximum number of bindings to return in the binding_vector argument of the rpc_ns_binding_lookup_next routine. To use the default count, specify rpc_c_binding_max_count.

Output

lookup_contextReturns the name service handle for use with the rpc_ns_binding_lookup_next and rpc_ns_binding_lookup_done routines.

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_incomplete_nameIncomplete name.

rpc_s_invalid_if_handleInvalid interface handle.

rpc_s_invalid_name_syntax
Invalid name syntax.

rpc_s_invalid_objectInvalid object.

rpc_s_no_env_setupEnvironment variable not setup.

rpc_s_not_rpc_entryNot an RPC entry.

rpc_s_unsupported_name_syntax
Unsupported name syntax.

DESCRIPTION

The rpc_ns_binding_lookup_begin routine creates a lookup context for locating compatible server binding handles for servers. These servers offer the specified interface and object UUID in the respective if_handle and object_uuid arguments.

Before calling the rpc_ns_binding_lookup_next routine, the client application must first create a lookup context by calling the rpc_ns_binding_lookup_begin routine. The arguments to this routine control the operation of the rpc_ns_binding_lookup_next routine.

When finished locating binding handles, the client application calls the rpc_ns_binding_lookup_done routine to delete the lookup context.

Permissions Required

None.

NOTE:

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

RETURN VALUES