OSI/AS Programming Manual

APS_ASSOC_CONNECTREQ_
APS Procedure Calls
056783 Tandem Computers Incorporated 3–37
Table 3-1 shows the five functional units that each use a token. If you select a
functional unit from this list, you must give a value to the corresponding token.
Table 3-2 shows the values you can give and how the token is assigned as a result.
If a token is not applicable because you have not selected the corresponding
functional unit, give it the value ZAPS-VAL-TOKEN-NOVALUE.
Table 3-1. Functional Units and Corresponding Tokens
For This Functional Unit Assign This Token
Activity management Major/activity token
Half-duplex Data token
Minor synchronize Synchronize-minor token
Major synchronize Major/activity token
Negotiated release Release token
Table 3-2. Assigning Tokens during Connect Request
Give This Value To Assign the Token
ZAPS-VAL-TOKEN-ACCEPTOR-CHOICE As the remote application decides
ZAPS-VAL-TOKEN-NOTOWNED To the remote application
ZAPS-VAL-TOKEN-NOVALUE Not applicable
ZAPS-VAL-TOKEN-OWNED To your application
subdevice-name enables you either to explicitly name a subdevice that is being
created or to reuse an existing static subdevice from a previous connect request.
The following restrictions apply:
It must be reused with the same PSAP address, AP title, and AE qualifier that
created it.
It can be reused only for a connect request.
It can be reused only on the same OSI service layer that it was used on
previously. For example, if a static subdevice is used for a session connect
request, it cannot be reused for a presentation connect request.
If the specified subdevice is currently in use or if you are trying to reuse it in the
wrong context, the APS_ASSOC_CONNECTREQ_ procedure returns a ZAPS-
ERROR-PARAMETER error indication with a ZAPS-ERR-PARAM-L5-
SUBDEVICE error subcode.