OSI/AS Programming Manual

APS_RESYNCRSP_
APS Procedure Calls
3–82 056783 Tandem Computers Incorporated
Considerations
After you have received a resynchronize indication, you cannot call any APS
procedure that invokes a primitive, except the following procedures:
APS_ASSOC_ABORTREQ_
APS_ACTIVITY_DISCARDREQ_
APS_ACTIVITY_INTERRUPTREQ_
APS_RESYNCREQ_
APS_RESYNCRSP_
Note also that APS_ACTIVITY_DISCARDREQ_ ,
APS_ACTIVITY_INTERRUPTREQ_ , and APS_RESYNCREQ_ cause a collision of
resynchronize requests, and you can issue these requests only if you will win the
collision. (See ISO 8326 for details about collisions.)
If there is an unacknowledged major synchronization point at the time of the
resynchronize indication, this point remains unacknowledged. In any case, you
should not call APS_RESYNCRSP_ until the resynchronization is complete and
until you have received new indications for synchronization points.
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.