CRE Programmer's Guide

CRE Service Functions
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
6-32
CRE_Receive_Open_Close_
Return Value
CRE_Receive_Open_Close_ returns one of the following:
•
0 if the input operation is successful
•
A positive number, which is a file system error number
•
A negative number, which is the negation of a CRE error number from the following
table:
Specifying the Receive File Open Attributes
This subsection describes the fields of the structure that the attributes parameter
references.
The format of the
attributes structure is defined by the following TAL STRUCT:
STRUCT CRE^RFOA^model(*); ! $RECEIVE open attributes
BEGIN
INT Maximum^requesters; ! Max requesters supported
INT Maximum^syncdepth; ! Max saved / requester
INT Maximum^reply; ! Max bytes in saved reply
INT Receive^depth; ! Max server queue depth
INT Report^flags[0:3]; ! Report system msg flags
FILLER 2; ! Reserved (must be 0)
END; -- CRE^RFOA^model
The structure CRE^RFOA^model is in the CREDECS file. Refer to Section 3,
Compiling and Binding Programs for the TNS CRE, for information on the CREDECS
file.
Figure 6-4
on page 6-34 shows how each of the fields in CRE^RFOA^model affects
how the CRE allocates memory for requester processes:
Error Code Cause
17 Cannot obtain control space
55 Missing or invalid parameter
57 Parameter value not accepted
65 Invalid attribute value
71 Inconsistent attribute value
RFOA field Effect
Maximum^requesters
(value 3)
The server can support three simultaneous requester processes
because it has allocated space for three sets of server replies:
Requester 1 Replies, Requester 2 Replies, and Requester 3
Replies. Therefore, the server can support all three requesters:
Requester A, Requester B, and Requester C.