OSI/AS Programming Manual

APS_ACTIVITY_INTERRUPTREQ_
APS Procedure Calls
056783 Tandem Computers Incorporated 3–17
user-data input
INT .EXT:ref:*
for session version 2 only, 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 in “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.
Considerations
The maximum amount of user data you can send with this primitive depends on
the layer of your connection, whether you are using session version 1 or session
version 2, and (for presentation and ACSE connections) whether your connection
is in normal mode or X.410-1984 mode. The maximum length of the user-data
parameter is as follows:
Session version 1 Session version 2
Session connection 0 bytes 10240 bytes
Presentation connection (normal mode) 0 bytes < 10240 bytes
ACSE connection (normal mode) 0 bytes < 10240 bytes
For a normal-mode presentation or ACSE connection using session version 2, you
can send as much data as will fit in a 10240-byte PPDU; the maximum length
depends on the encoding.
For a presentation or ACSE connection in X.410-1984 mode, the maximum amount
of data is the same as that for a session connection.
After calling APS_ACTIVITY_INTERRUPTREQ_ (and MFM_AWAITIOX_ if in
nowait mode), you should call APS_EVENT_RECEIVE_ to receive the confirm
primitive from the remote application. You cannot call any APS procedure that
invokes a primitive, except APS_ASSOC_ABORTREQ_ , until you have received
this confirm primitive.
After you receive the confirm, all available tokens are assigned to you.
After you receive the confirm, you can resume the same activity by calling
APS_ACTIVITY_RESUMEREQ_.