NAME

DL_XID_REQ (dl_xid_req_t) - conveys one XID DLSDU from the DLS User to the DLS Provider for transmission to a peer DLS User.

SYNOPSIS

The message consists of one M_PROTO message block, followed by zero or more M_DATA blocks containing zero or more bytes of data. The message structure is as follows:

typedef struct {
    t_uscalar_t  dl_primitive;
    t_uscalar_t  dl_flag;
    t_uscalar_t  dl_dest_addr_length;
    t_uscalar_t  dl_dest_addr_offset;
} dl_xid_req_t;

PARAMETERS

dl_primitive

conveys DL_XID_REQ

dl_flag

indicates the flag values for the response as follows:

DL_POLL_FINAL

indicates status of the poll/final bit in the xid frame.

dl_dest_addr_length

conveys the length of the DLSAP address of the destination DLS User. If the destination user is implemented using DLPI, this address is the full DLSAP address returned on the DL_BIND_ACK.

dl_dest_addr_offset

conveys the offset from the beginning of the M_PROTO message block where the destination DLSAP address begins.

STATE

The message is valid in state DL_IDLE and DL_DATAXFER.

NEW STATE

The resulting state is unchanged.

RESPONSE

On an invalid XID request, a DL_ERROR_ACK is issued to the user. If the remote side responds to the XID request, a DL_XID_CON will be sent to the User. It is recommended that the DLS User use a timeout procedure on an XID_REQ. The timeout may be used if the remote side does not respond to the XID request.

ERRORS

DL_BADADDR

The DLSAP address information was invalid or was in an incorrect format.

DL_BADDATA

The amount of data in the current DLSDU exceeded the DLS Provider's DLSDU limit.

DL_NOTSUPPORTED

Primitive is known but not supported by the DLS Provider

DL_OUTSTATE

The primitive was issued from an invalid state

DL_SYSERR

A System error has occurred and the UNIX System error is indicated in the DL_ERROR_ACK.

DL_XIDAUTO

Previous bind request specified Provider would handle XID.