OSI/AS Programming Manual

Sending and Retrieving User Data
APS Procedures Programming Concepts
056783 Tandem Computers Incorporated 2–47
2. To send the data, call APS_DATA_REQ_.
3. If the connection is in nowait mode, call MFM_AWAITIOX_ to wait for the
completion of the procedure. MFM_AWAITIOX_ gives you the status code for the
completed procedure call. If the status is not ZAPS-VAL-STATUS-OK, call
APS_STATUS_.
4. If you are using APS_DATA_REQ_ or APS_TYPEDDATA_REQ_ , you can repeat
steps 2 and 3 until you have sent all the data.
You can use a similar set of steps with APS_TYPEDDATA_REQ_ or
APS_CAPDATA_REQ_. Note the following differences:
You do not need the data token to call APS_TYPEDDATA_REQ_.
APS_CAPDATA_REQ_ is subject to several restrictions related to tokens and
functional units, as described in Section 3.
With APS_CAPDATA_REQ_ , you can send only a limited amount of data, and
you cannot repeat steps 2 and 3 (that is, you cannot use multiple calls per
primitive).
For details, refer to the descriptions of APS_TYPEDDATA_REQ_ and
APS_CAPDATA_REQ_ in Section 3.
Retrieving User Data The incoming primitives listed in Table 2-17 can contain user data sent by the remote
application.
Table 2-17. Primitives That Can Contain Incoming User Data
Activity discard confirm* Release confirm
Activity discard indication* Release indication
Activity end confirm Resynchronize confirm
Activity end indication Resynchronize indication
Activity interrupt confirm* Synchronize major confirm
Activity interrupt indication* Synchronize major indication
Activity start indication Synchronize minor confirm
Capability data confirm Synchronize minor indication
Capability data indication Token give indication*
Connect confirm Token please indication
Connect indication Typed data indication
Control give indication* User abort indication
Data indication User exception report indication
* These procedures can contain incoming user data for session version 2 only.