DL_XID_REQ(7dlpi) DL_XID_REQ(7dlpi)
NAME
DL_XID_REQ - Message Type
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 {
ulong dl_primitive;
ulong dl_flag;
ulong dl_dest_addr_length;
ulong dl_dest_addr_offset;
} dl_xid_req_t;
DESCRIPTION
Conveys one XID DLSDU from the DLS User to the DLS Provider
for transmission to a peer DLS User.
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.
Copyright 1994 Novell, Inc. Page 1
DL_XID_REQ(7dlpi) DL_XID_REQ(7dlpi)
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.
Reasons for Failure
DL_BADDATA The amount of data in the current DLSDU exceeded
the DLS Provider's DLSDU limit.
DL_XIDAUTO Previous bind request specified Provider would
handle XID.
DL_OUTSTATE The primitive was issued from an invalid state
DL_BADADDR The DLSAP address information was invalid or was
in an incorrect format.
DL_SYSERR A System error has occurred and the UNIX System
error is indicated in the DL_ERROR_ACK.
DL_NOTSUPPORTED
Primitive is known but not supported by the DLS
Provider
Category
XID.
Copyright 1994 Novell, Inc. Page 2