OSI/AS Programming Manual

APS_DATA_GETPARAM_
APS Procedure Calls
3–64 056783 Tandem Computers Incorporated
more-data output
INT(32) .EXT:ref:1
gives you the size, in bytes, of the user data you have not yet received. To obtain
the remaining data, call APS_DATA_GETPARAM_ again.
A value of 0 indicates that no more user data remains.
next-position output
INT(32) .EXT:ref:1
gives you the offset, in bytes, of the next byte of user data available in the API. In
other words, it gives you the position of the first byte not yet retrieved. Use this
value as the start-position of the next APS_DATA_GETPARAM_ call.
start-position input
INT(32):value
specifies the offset, in bytes, of the first data byte to be returned by this procedure.
If this parameter is omitted, the API assumes a value of 0.
Note that start-position refers only to actual user data, excluding ZAPS-
DDL-DATA-HDR and ZAPS-DDL-DATA-ELEMENT-HDR.
For further information about the use of this parameter, see “Considerations.”
Considerations
APS_EVENT_RECEIVE_ enables the movement of user data from the TAPS
process to the API, so that when you call APS_DATA_GETPARAM_ , the data to
be returned is already in the API’s extended segment. Because this procedure
does not perform any file-system I/O operations, the request is always completed
immediately after the procedure call. Do not call MFM_AWAITIOX_ to complete
this procedure.
On return from a call to this procedure, the user data buffer has the following
structure if it contains only one data element:
ZAPS-DDL-DATA-HDR
ZAPS-DDL-DATA-ELEMENT-HDR
data
085