Guardian Programming Reference Summary for pTAL and TAL

Procedure Calls Summary (R-Z)
Guardian Programming Reference Summary for pTAL and TAL—522631-001
8-7
REFPARAM_BOUNDSCHECK_
Checks the validity of parameter addresses passed to the procedure that calls it. Bounds
checking performed by the system is enough for most applications. This procedure,
however, provides additional checks for those few applications that might need it.
Primarily, REFPARAM_BOUNDSCHECK_ verifies that a specified memory area is
valid for a specified type of access (read only or read/write). Optionally, it also verifies
that the specified memory area does not overlap the part of the process stack occupied
by the calling procedure and any of the procedures it calls.
0 Not a data message
1 Sender called WRITE
2 Sender called READ
3 Sender called WRITEREAD
< (CCL) $RECEIVE is not open.
= (CCE) RECEIVEINFO is successful.
Note. This procedure is declared only in the EXTDECS0 file.
error := REFPARAM_BOUNDSCHECK_ ( start-address
,area-length
,framestart
,flags );
error, INT returned value
0 No error. The procedure successfully executed; the specified memory area is in bounds.
See “Considerations” for a discussion of what it means to be in bounds.
1 The specified memory area is out of bounds. Accessing the area might cause an
addressing trap or system-generated nondeferrable signal.
2 The address is in a read-only area and the check was made for read/write access. The
effect of attempting to write to the area depends on whether your process is a TNS/R
native process or a TNS process: For a TNS/R native process, the system might deliver a
nondeferrable signal to the process; for a TNS process, the write operation might not
take effect.