rpc_ns_entry_object_inq_next(3) — Subroutines
NAME
rpc_ns_entry_object_inq_next - Returns one object at a time from an entry in the name service database
Used by client, server, or management applications.
SYNOPSIS
#include <dce/rpc.h>
void rpc_ns_entry_object_inq_next(
rpc_ns_handle_t inquiry_context ,
uuid_t ∗obj_uuid ,
unsigned32 ∗status );
PARAMETERS
Input
inquiry_contextSpecifies a name service handle. This handle is returned from the rpc_ns_entry_object_inq_begin routine.
Output
obj_uuidReturns an exported object UUID.
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_ns_handleInvalid name service handle.
rpc_s_name_service_unavailable
Name service unavailable.
rpc_s_no_more_membersNo more members.
rpc_s_no_ns_permissionNo permission for name service operation.
DESCRIPTION
The rpc_ns_entry_object_inq_next routine returns one of the object UUIDs exported to an entry in the name service database. The entry_name argument in the rpc_ns_entry_object_inq_begin routine specified the entry.
An application can view all of the exported object UUIDs by repeatedly calling the rpc_ns_entry_object_inq_next routine. When all the object UUIDs are viewed, this routine returns an rpc_s_no_more_members status. The returned object UUIDs are unordered.
The application supplies the memory for the object UUID returned in the obj_uuid argument.
After viewing the object UUIDs, the application must call the rpc_ns_entry_object_inq_done routine to delete the inquiry context.
The order in which routine rpc_ns_entry_object_inq_next returns object UUIDs can be different for each viewing of an entry. This means that the order in which an application receives object UUIDs can be different each time the application is run.
Permissions Required
You need read permission to the CDS object entry (the target name service entry).
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_binding_export(3), rpc_ns_entry_object_inq_begin(3), rpc_ns_entry_object_inq_done(3)