OSI/AS Programming Manual
APS_ASSOC_ATTACH_
APS Procedure Calls
056783 Tandem Computers Incorporated 3–29
Considerations
Note that the completion of APS_ASSOC_ATTACH_ (even in wait mode) does not
mean a connection has been established. You must call APS_EVENT_RECEIVE_
in order to be notified when you have received a connect indication. For full
details on how to establish a connection, see “Establishing a Connection” in
Section 2.
A valid CEPI (one with a value other than -1) remains allocated until you call the
APS_DISCARD_ procedure. If, however, the APS_ASSOC_ATTACH_ procedure
returns a
cepi
value of -1, the procedure has failed and APS_DISCARD_ is
unnecessary.
To obtain error information when a
cepi
value of -1 has been returned, call
APS_STATUS_ with the
cepi
parameter set to -1.
The
local-appl
parameter consists of the application name and the
corresponding OSI address. If you specify only the application name, OSI/AS
supplies the corresponding OSI address. If you specify the OSI address, OSI/AS
ignores any application name you specify. The
local-appl
structure used,
including the corresponding OSI address (if any) filled in by OSI/AS, is returned
when you call APS_ASSOC_GETPARAM_ after the request has completed. If you
are in nowait mode, do not call APS_ASSOC_GETPARAM_ until
MFM_AWAITIOX_ indicates that the attach procedure has completed.
Note that ACSE does not filter incoming calls based on the application entity title
(AE title) associated with the application name in
local-appl
. This means, for
instance, that you could issue an attach for AE title “B” and PSAP “xyz” and
receive a connect indication for AE title “P” and PSAP “xyz”. It is your
responsibility either to assign a different PSAP to each AE title or to provide
provide a method of resolving AE title conflicts.
subdevice-name
enables you to explicitly name a subdevice or to reuse a static
subdevice from a previous attach. 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 an attach.
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 attach, it
cannot be reused for a presentation attach.