OSI/AS Programming Manual

APS_ASSOC_CONNECTREQ_
APS Procedure Calls
056783 Tandem Computers Incorporated 3–35
Considerations
A valid CEPI (one with a value other than -1) remains allocated until you call
APS_DISCARD_. If, however, the APS_ASSOC_CONNECTREQ_ procedure
returns a cepi value of -1, APS_DISCARD_ is unnecessary.
To obtain error information when a cepi value of -1 is returned, call
APS_STATUS_ with the cepi parameter set to -1.
The local-appl and remote-appl parameters each consist of the application
name and the corresponding OSI address. If you specify only the application
name, OSI/AS supplies the OSI address. If you specify the OSI address, OSI/AS
ignores any application name you specify. The local-appl and remote-appl
structures used, including the corresponding OSI address (if any) filled in by
OSI/AS, are 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 connect request procedure has
completed.
Because an application entity title can have many associated OSI addresses, an OSI
address can be identified only by a presentation service access point (PSAP)
address or by a locally defined application name. If you specify an application
name to identify an OSI address, you can retrieve the PSAP address and/or the
application entity title if it is present. If you specify the PSAP address to identify
an OSI address, you cannot retrieve the application entity title or the application
name. When the OSI manager process looks up an application name, it checks in
the management information base (MIB) to retrieve the PSAP address and the
application entity title if it is present.
If you want to reuse a static subdevice, both local-appl and remote-appl
must be either omitted or set to null values (all ZLEN fields of the ZAPS-DDL-
APPL-ADDR structure set to 0).
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:
Type of Connection 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.