Informs the local data link service (DLS) user that a remote (calling) DLS user is attempting to establish a data link connection.
The primitive consists of one
M_PROTO message block, which contains the following
structure.
typedef struct
{
ulong dl_primitive;
ulong dl_correlation;
ulong dl_called_addr_length;
ulong dl_called_addr_offset;
ulong dl_calling_addr_length;
ulong dl_calling_addr_offset;
ulong dl_qos_length;
ulong dl_qos_offset;
ulong dl_growth;
} dl_connect_req_t;
The DL_CONNECT_IND primitive informs the local DLS user that a remote (calling) DLS user is attempting to establish a data link connection. The primitive contains the data link service access point (DLSAP) addresses of the calling and called DLS user.
The DL_CONNECT_IND primitive also contains a number that allows the DLS user to correlate the primitive with a subsequent DL_CONNECT_RES, DL_DISCONNECT_REQ, or DL_DISCONNECT_IND primitive.
The number of outstanding DL_CONNECT_IND primitives issued by the DLS provider must not exceed the value of the dl_max_conind parameter specified by the DL_BIND_ACK primitive. If this limit is reached and an additional connect request arrives, the DLS provider does not pass the corresponding connect indication to the DLS user until a response is received for an outstanding request.
Note: This primitive applies to connection mode.
The DLS user must send either the DL_CONNECT_RES primitive to accept the connect request or the DL_DISCONNECT_REQ primitive to reject the connect request. In either case, the responding message must convey the correlation number received from the DL_CONNECT_IND primitive. The DLS provider uses the correlation number to identify the connect request to which the DLS user is responding.
This primitive is part of Base Operating System (BOS) Runtime.
The DL_BIND_ACK primitive, DL_CONNECT_RES primitive, DL_DISCONNECT_IND primitive, DL_DISCONNECT_REQ primitive.