COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

Topics:
• Receive-Control Table
• Reply Table
• ERROR CODE Phrase
• MESSAGE SOURCE Phrase
• REPORT Phrase
Receive-Control Table
The receive-control table, an internal table, is required for $RECEIVE operation. Its purpose is to
identify, by the PROCESS-ID, which requesting processes have opened the server process.
Table 27 Receive-Control Table Example
Requesting ProcessEntry Number
REQUESTER PROCESS 11
REQUESTER PROCESS 22
REQUESTER PROCESS 33
……
REQUESTER PROCESS 100100*
* The number of entries in the receive-control table is defined by table-length.
The compiler allocates only one receive-control table because only one file assigned to $RECEIVE
can be open for input or input-output at a time. When more than one program unit defines a
receive-control table, the compiler reserves space for the largest table.
In the Pathway environment, the value of table-length for a server must be greater than or
equal to the value of the MAXLINKS parameter in the server-class definition for the server.
When the number of active requesters fills the receive-control table, OPEN messages from new
requesters are refused with a run-time error message and are not reported to your program. OPEN
messages received from backup processes of active requesters are still accepted and reported.
Reply Table
When reply messages are sent back to the requesting processes, the COBOL compiler constructs
a second internal table in which to save the replies. The reply message includes the sync-id
and the contents of the reply.
If the reply table exceeds an internal threshold value, the reply table is in the Extended-Storage
Section.
NOTE: You do not need a reply table if the requester is not a fault-tolerant process.
Input-Output Section 147