Manpage of DL_ERROR_ACK

DL_ERROR_ACK

Section: Data Link Provider Interface (DLPI) (7)
Updated: 2008-10-31
Index Return to Main Contents

NAME

DL_ERROR_ACK (dl_error_ack_t) - informs the DLS user that a previously issued request or response was invalid.

INTERFACE

Data Link Provider Interface, DLPI[1].

SYNOPSIS

The message consists of one M_PCPROTO(9) message block, which contains the following structure.

#include <sys/dlpi.h>
typedef struct {
    t_uscalar_t  dl_primitive;
    t_uscalar_t  dl_error_primitive;
    t_uscalar_t  dl_errno;
    t_uscalar_t  dl_unix_errno;
} dl_error_ack_t;

DESCRIPTION

DL_ERROR_ACK informs the DLS user that a previously issued request or response was invalid. It conveys the identity of the primitive in error, a DLPI error code, and if appropriate, a Linux system error code. Whenever this primitive is generated, it indicates that the DLPI state is identical to what it was before the erroneous request or response.

PARAMETERS

The dl_error_ack_t structure contains the following members:

dl_primitive

conveys DL_ERROR_ACK.

dl_error_prim

identifies the primitive in error.

dl_errno

conveys the DLPI error code associated with the failure. See the individual request or response for the error codes that are applicable. In addition to those errors, the following errors may be reported:

DL_BADPRIM: An unrecognized primitive was issued by the DLS user.
DL_NOTSUPPORTED: A recognized but unsupported primitive was issued by the DLS user.

dl_unix_errno

conveys the Linux system error code associated with the failure. This value should be non-zero only when dl_errno is set to DL_SYSERR. It is used to report Linux system failures that prevent the processing of a given request or response. See the individual request or response reference page for the error codes that are applicable. In addition to those errors, the following errors may be reported:

[EPERM]: Fine-grained permission for the request or response is incorrect. That is, the primitive is recognized and supported by the DLS Provider but the requesting DLS User Stream does not have sufficient permissions for the DLS Provider to satisfy the request.
[ENOMEM]: Insufficient memory was available to satisfy the request. The request or response may be successful if the DLS User reissues the request or response primitive at a later time when resources become available.
[ENOBUFS]: Insufficient buffers were available to satisfy the request. The request or response may be successful if the DLS User reissues the request or response primitive at a later time when resources become available.
[ENOSR]: Insufficient STREAMS resources were available to satisfy the request. The request or response may be successful if the DLS User reissues the request or response primitive at a later time when resources become available.
[EAGAIN]: A temporary failure occurred and the DLS user should reissue the request or response.
[EBUSY]: The control information in the request or response primitive has already been subjected to the control request or response, or the driver is unabled to handle the request due to some other transient condition.
[EINVAL]: One of the parameters of the request for which there is no prescribed DLPI error code has an invalid value.
[ENOTSUP]: Unsupported request, event or call. The DLS provider recognizes and supportes the request or response primitive, however, the specific request or response is not supported by the DLS provider or data link protocol.
[ENOLINK]: The interface (Physical Point of Attachment (PPA) or underlying driver or device) is not connected and no prescribed DLPI error code is applicable.
[ENXIO]: Invalid device. The interface (Phsyical Point of Attachment (PPA) or underlying driver or device) is no longer installed on the system.

MODE

This primitive is valid in any mode.

STATE

The message is valid in every state where an acknowledgement or confirmation of a previous request or response is pending.

NEW STATE

The resulting state is that from which the acknowledged request or response was generated.

COMPATIBILITY

The DL_ERROR_ACK primitive is compatible with implementations based on DLPI Revision 2[1], such as AIX®[2], HP-UX®[3], Solaris®[4], Solstice®[5], and UnixWare®[6], with the following portability considerations:

---: The DLPI standard does not proscribe the use of specific Linux error codes. OpenSS7 XNS Networking details the use of Linux error codes with regard to DLPI primitives for the purpose of clarification of the implementation. OpenSS7 XNS Networking is largely compatible with HP-UX®[3] in this regard.

See dlpi(7), dlpi_ioctl(4), STREAMS(9), for additional compatibility information.

CONFORMANCE

This interface conforms to DLPI Revision 2[1].

HISTORY

The Data Link Provider Interface first appeared in SVR 4[7].

REFERENCES

[1]: DLPI, Data Link Provider Interface (DLPI) Specification, Revision 2.0.0, Draft 2, August 20, 1991, (Parsippany, New Jersey), UNIX. International,Inc., UNIX International Press. <http://www.openss7.org/doc/dlpi.pdf>
[2]: AIX Version 6.1, AIX Version 6.1 Technical Reference: Communications, Volume 1, First Edition, November 2007, (Boulder, Colorado), Internatonal Business Machines Corp., IBM. [SC23-6610-00] <http://publib.boulder.ibm.com/>
[3]: HP-UX DLPI, HP DLPI Programmer's Guide -- HP-UX 11i v3, February 2007, (Palo Alto, California), Hewlett-Packard Development Company L.P., HP. [Part No: 5991-7498] <http://docs.hp.com/>
[4]: Solaris® 11, Solaris 11 Docmentation, 2008, (Santa Clara, California), Sun Microsystems, Inc., Sun. <http://docs.sun.com/>
[5]: Solstice® X.25, Solstice® X.25 9.2 Programming Guide, October 1999, (Palo Alto, California), Sun Microsystems, Inc., Sun. [Part No: 806-1235-10] <http://docs-pdf.sun.com/>
[6]: UnixWare® 7.1.3, UnixWare 7.1.3 (OpenUnix 8) Documentation, 2002, (Lindon, Utah), Caldera International, Inc., Caldera. <http://uw713doc.sco.com/>
[7]: SVR 4, UNIX® System V Release 4 Programmer's Manual, 1990, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[8]: Magic Garden, The Magic Garden Explained: The Internals of UNIX® System V Release 4 / An Open Systems Design, 1994, (Australia), B. Goodheart, J. Cox, Prentice Hall. [ISBN 0-13-098138-9]
[9]: Advanced Programming in the UNIX®Environment, 15th edition, December 1997, (Reading, Massachusetts), W. R. Stevens, Addison Wesley. [ISBN 0-201-56317-7]

TRADEMARKS

OpenSS7tm: is a trademark of OpenSS7 Corporation.
Linux®: is a registered trademark of Linus Torvalds.
UNIX®: is a registered trademark of The Open Group.
Solaris®: is a registered trademark of Sun Microsystems.

Other trademarks are the property of their respective owners.

IDENTIFICATION

OpenSS7 XNS Networking: Package strxns version 0.9.2.7 released 2008-10-31.

This document was created by man2html, using the manual pages.
Time: 14:11:20 GMT, May 23, 2013