DL_ATTACH_REQ(7dlpi) DL_ATTACH_REQ(7dlpi)
NAME
DL_ATTACH_REQ - Message Type
SYNOPSIS
The message consists of one M_PROTO message block, which
contains the following structure.
typedef struct {
ulong dl_primitive;
ulong dl_ppa;
} dl_attach_req_t;
DESCRIPTION
Requests the DLS provider associate a physical point of
attachment (PPA) with a stream. DL_ATTACH_REQ is needed for
style 2 DLS providers to identify the physical medium over
which communication will occur. The request may not be issued
to a style 1 DLS provider; doing so may cause errors.
The DLS provider may initialize the physical line on receipt
of this primitive or the DL_BIND_REQ. Otherwise, the line
must be initialized through some management mechanism before
this request is issued by the DLS user.
Either way, the physical link must be initialized and ready
for use on successful completion of the DL_BIND_REQ.
Parameters
dl_primitive
conveys DL_ATTACH_REQ.
dl_ppa conveys the identifier of the physical point of
attachment to be associated with the stream. The
format of the identifier is provider-specific, and
it must contain sufficient information to
distinguish the desired PPA from all possible PPAs
on a system.
At a minimum, this must include identification of
the physical medium over which communication will
occur. For media that multiplex multiple channels
over a single physical medium, this identifier
should also specify a specific channel to be used
for communication (where each channel on a
physical medium is associated with a separate
PPA).
Copyright 1994 Novell, Inc. Page 1
DL_ATTACH_REQ(7dlpi) DL_ATTACH_REQ(7dlpi)
Because of the provider-specific nature of this
value, DLS user software that is to be protocol
independent should avoid hard-coding the PPA
identifier. The DLS user should retrieve the
necessary PPA identifier from some other entity
(such as a management entity) and insert it
without inspection into the DL_ATTACH_REQ.
State
The message is valid in state DL_UNATTACHED.
New State
The resulting state is DL_ATTACH_PENDING.
Response
If the attach request is successful, DL_OK_ACK is sent to the
DLS user resulting in state DL_UNBOUND.
If the request fails, message DL_ERROR_ACK is returned and the
resulting state is unchanged.
Reasons for Failure
DL_BADPPA The specified PPA is invalid.
DL_ACCESS The DLS user did not have proper permission to use
the requested PPA.
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.
Category
Local Management.
Copyright 1994 Novell, Inc. Page 2