OSI/AS Programming Manual

APS_TYPEDDATA_REQ_
APS Procedure Calls
056783 Tandem Computers Incorporated 3–105
APS_TYPEDDATA_REQ_ This procedure allows you to send typed data to the remote application. Typed data
transfers are subject to the same service restrictions as normal data transfers, except
that typed data transfers are not subject to token restrictions. On each call to this
procedure, you can send as much data as your program can handle; in addition, you
can send an unlimited amount of data in a single typed data request primitive by
using multiple calls. See “Sending and Retrieving User Data” in Section 2.
status := APS_TYPEDDATA_REQ_
( cepi ! I
, user-data ! I
,[ tag ] ! I
,[ data-operation ] ! I
,[ block-size ] ); ! I
status returned value
INT
indicates the outcome of the call. For the possible values of ZAPS-VAL-STATUS-
xxx, see “Status Codes” in Appendix B.
cepi input
INT:value
is the connection endpoint identifier (CEPI) for this connection.
user-data input
INT .EXT:ref:*
contains the user data you wish to send to the remote application. You can send
as much data and as many data elements as your program can handle. You must
send at least one byte. You must define the structure of the data buffer, as
described under “Defining User Data Buffers” in Section 2. For a normal-mode
presentation or ACSE connection, you must also encode the data, as described in
“Encoding ACSE and Presentation User Data” in Section 2.
tag input
INT(32):value
is for use in nowait mode only. Specify a unique value to identify this instance of
the procedure call. When the operation is complete, the MFM_AWAITIOX_
procedure returns the tag value, allowing you to match the completion with the
correct instance of the procedure call.