OSI/AS Programming Manual

APS_ASSOC_ATTACH_
APS Procedure Calls
3–30 056783 Tandem Computers Incorporated
If you are ready to accept more than one connect request, call
APS_ASSOC_ATTACH_ as many times as necessary. Note, however, that some
connect requests might be rejected because you may have failed to issue an attach
for that particular local application in time.
The first event following a successful attach may be a provider abort rather than a
connect indication, because the connect indication may have failed at some layer.
If that happens, reissue the attach. OSI/AS issues a provider abort indication
when a session, presentation, or ACSE connect indication fails.
Until a connection is established for this CEPI, the only other APS procedures
that you can call are APS_STATUS_ , APS_ASSOC_ABORTREQ_ ,
APS_ASSOC_GETPARAM_ , and APS_DISCARD_. Any other APS
procedures you call at this stage are rejected. If you no longer wish to wait
for a connect indication, call APS_DISCARD_.
If the specified subdevice is currently in use or if you are trying to reuse
it in the wrong context, the APS_ASSOC_ATTACH_ procedure returns a
ZAPS-ERROR-PARAMETER error indication with a ZAPS-ERR-PARAM-
L5-SUBDEVICE error subcode.
If you want to reuse a static subdevice, the address you supply as the local-
appl parameter must be either omitted or null (all ZLEN fields of the ZAPS-DDL-
APPL-ADDR structure set to 0).