rpc_sm_enable_allocate, rpc_ss_enable


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| Reference \| Topic List \| Previous \| Next \| Contents

BEA Tuxedo C Function Reference

rpc_sm_enable_allocate, rpc_ss_enable_allocate(3c)

Name

rpc_sm_enable_allocate(), rpc_ss_enable_allocate() - enables the stub memory management environment

Synopsis

#include <rpc/rpc.h> 
void rpc_sm_enable_allocate(unsigned32 *status) 
void rpc_ss_enable_allocate(void)

Description

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 service code called from the server stub, the stub memory management environment is normally established by the stub itself. Code that is called from other contexts needs to call rpc_sm_enable_allocate() before calling rpc_sm_allocate() (for example, if the service code is called directly instead of from the stub).

The output parameter, status, returns the status code from this routine. This status code indicates whether the routine completed successfully or, if not, why not. Possible status codes and their meanings include:

rpc_s_ok: Success.
rpc_s_no_memory: Insufficient memory available to set up necessary data structures.

rpc_ss_enable_allocate() is the exception-returning version of this function and has no status output parameter. The following exceptions are raised by this routine.

rpc_x_no_memory: Insufficient memory available to set up necessary data structures.

A thread in a multithreaded application may issue a call to rpc_sm_enable_allocate() or rpc_ss_enable_allocate() while running in any context state, including TPINVALIDCONTEXT.

Return Values

None.