rpc_ns_entry_object_inq_next- returns one object at a time from an entry in the name service database
void rpc_ns_entry_object_inq_next( rpc_ns_handle_t inquiry_context, uuid_t *obj_uuid, unsigned32 *status);
- Specifies an inquiry context. The application obtains the inquiry context by calling the rpc_ns_entry_object_inq_begin() routine.
- Returns an exported object UUID.
- Returns the status code from this routine. The status code indicates whether the routine completed successfully, or if not, why not.
Possible status codes and their meanings include:
Name service entry not found.
Not an RPC entry.
Name service entry has incompatible RPC class version.
Name service unavailable.
No more members.
No permission for name service operation.
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 specifies 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 returned in unspecified order.
The application supplies the memory for the object UUID returned in obj_uuid.
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.
The application needs read permission for the target name service entry.
Please note that the html version of this specification may contain formatting aberrations. The definitive version is available as an electronic publication on CD-ROM from The Open Group.