OSI/AS Programming Manual

APS_EXCEPTIONREQ_
APS Procedure Calls
056783 Tandem Computers Incorporated 3–73
APS_EXCEPTIONREQ_ This procedure allows you to send an exception report when an error has occurred on
a connection operating in half-duplex mode. All undelivered data will be lost.
You can issue an exception request only if the data token is available on the connection
and is held by the remote user, not by you. If the activity management service is
available on the connection, you can issue an exception request only if an activity is in
progress.
This procedure also allows you, optionally, to use basic concatenation to send a token
please request primitive along with the exception request primitive.
status := APS_EXCEPTIONREQ_ ( cepi ! I
, exception-reason ! I
,[ user-data ] ! I
,[ tag ] ! I
,[ please-tokens ] ); ! 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.
exception-reason input
INT:value
is the reason for the exception report request. For the possible values of this
parameter, see ZAPS-VAL-EXC-xxx in Appendix A.
user-data input
INT .EXT:ref:*
contains the user data you wish to send to the remote application; see
“Considerations” for the maximum amount of data you can send. 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.