OSI/AS Programming Manual

APS_ACTIVITY_ENDREQ_
APS Procedure Calls
056783 Tandem Computers Incorporated 3–11
give-tokens input
INT .EXT:ref:(ZAPS-DDL-TOKENS)
specifies the tokens you are giving to the remote application in the token give
request primitive to be concatenated with the activity end request primitive. To
give tokens to the remote application, set the field values for the tokens you are
giving to ZAPS-VAL-TOKEN-GIVE, and set the field values for all other tokens to
ZAPS-VAL-TOKEN-NOVALUE.
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 512 bytes 10240 bytes
Presentation connection (normal mode) < 512 bytes < 10240 bytes
ACSE connection (normal mode) <512 bytes < 10240 bytes
For a normal-mode presentation or ACSE connection, you can send as much data
as will fit in a 512-byte PPDU (for session version 1) or a 10240-byte PPDU (for
session version 2); 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.
This procedure causes a new synchronization point serial number to be used on
the connection. To obtain the new serial number, call
APS_ACTIVITY_GETPARAM_ with the sync parameter after the
APS_ACTIVITY_ENDREQ_ operation has completed.
After issuing this request, until you receive the activity end confirm, you cannot
call any APS procedure that invokes a primitive, except for the following
procedures:
APS_ABORTREQ_
APS_ACTIVITY_DISCARDREQ_
APS_ACTIVITY_INTERRUPTREQ_
APS_TOKEN_GIVE_
After calling APS_ACTIVITY_ENDREQ_ , you must call APS_EVENT_RECEIVE_
to be able to receive the confirm from the remote application.