rpc_sm_enable_allocate-enables the stub memory management environment
#include <rpc.h>
void rpc_sm_enable_allocate(
unsigned32 *status);
Output
- status
- 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:
- rpc_s_ok
- Success.
Applications can call rpc_sm_enable_allocate() to establish a stub memory management environment in cases where one is not established by the stub itself. A stub memory management environment must be established before any calls are made to rpc_sm_allocate(). For server manager code called from the stub, the stub memory management environment is normally established by the stub itself. (SeeIntroduction to the RPC API for a description of stub memory management and an explanation of the conditions under which the stub establishes the necessary memory management environment.) Code that is called from other contexts needs to call rpc_sm_enable_allocate() before calling rpc_sm_allocate().
- Note:
- For a discussion of how spawned threads acquire a stub memory management environment, see
tagmref_rpc_sm_get_thread_handle .
None.
rpc_sm_allocate()
rpc_sm_disable_allocate().
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.
Contents | Next section | Index |