Manpage of N_PVC_ATTACH

N_PVC_ATTACH

Section: Network Layer Interface (NLI) (7)
Updated: 2008-10-31
Index Return to Main Contents

NAME

N_PVC_ATTACH - PVC Attach

INTERFACE

Network Layer Interface (NLI)[1], nli(7).

SYNOPSIS

#include <netx25/x25_proto.h>
struct xcallf {
    unsigned char xl_type;
    unsigned char xl_command;
    unsigned short lci;
    union {
        uint32_t link_id;
        uint32_t sn_id;
    };
    unsigned char reqackservice;
    unsigned char reqnsdulimit;
    int nsdulimit;
    int result_code;
};

DESCRIPTION

The PVC Attach message primitive is used by the NS user when requesting an attachment of the Stream to a PVC. The NS provider uses the PVC Attach message primitive to acknolwedge a previous PVC Attach message primitive issued by the NS user. The control part of the message consists of one M_PROTO(9) message block containing the pvcattf structure. There is no data part (M_DATA(9) message blocks) associated with this message primitive.

FORMAT

The PVC Attach uses the pvcattf structure. The control part of the message consists of one M_PROTO(9) message block containing the pvcattf structure. There is no data part (M_DATA(9) message blocks) associated with this message primitive.

MEMBERS

The pvcattf structure contains the following members:

xl_type

Always XL_CTL.

xl_command

Always N_PVC_ATTACH, for PVC Attach.

lci

Conveys the logical channel identifier (LCI) of the PVC.

link_id

Conveys the link identifier for the PVC. This is a Solstice X.25 specific field.

: The link_id and sn_id fields are equivalent, with a slightly different name and format for Solstice X.25.

sn_id

Conveys the subnetwork identifier for the PVC. This is the non-Solstice X.25 specific field.

: This field is sometimes specified as a unsigned long. It has been declared as an uint32_t to support compatibility of 32-bit applications running over a 64-bit kernel.

reqackservice

When non-zero, conveys that the receipt confirmation service is requested by the use of the D-bit. This field can have one of the following values:

Constant	Value	Description

-	0	No receipt confirmation.
RC_CONF_DTE	1	Confirmation by the remote terminal.
RC_CONF_APP	2	Confirmation by the remote application.

In the case of receipt confirmation by the remote station, no acknowledgements are expected or given over the X.25 NLI service interface. For receipt confirmation by the remote application, there is a one-to-one correspondence between D-bit data and acknolwedgements passing in opposite directions. One data acknowledgement is received or sent for each D-bit data packet sent or received over the X.25 NLI service interface.

reqnsdulimit

When non-zero, conveys that an NSDU concantenation limit is asserted and the nsdulimit field is valid.

nsdulimit

When non-zero, conveys the packet concatenation limit for NSDUs when the reqnsdulimit field is also non-zero.

result_code

When the PVC Attach message primitive is used by the NS provider to acknowledge a previous PVC Attach message primitive issued by the NS user, this field is non-zero when an error has been encountered that prevents the attachment of the PVC.

This field can have one of the following values:

Constant	Value	Description

PVC_SUCCESS	0	Operation was successful.
PVC_NOSUCHSUBNET	1	Subnetwork not configured.
PVC_CFGERROR	2	LCI not in range, no PVCs.
PVC_NODBELEMENTS	3	No database available.
PVC_PARERROR	4	Error in request parameters.
PVC_BUSY	6	PVC in non-attach state.
PVC_CONGESTION	7	Resources unavailable.
PVC_WRONGSTATE	8	State wrong for function.
PVC_NOPERMISSION	9	Inadequate permissions.
PVC_LINKDOWN	10	The link has gone down.
PVC_RMTERROR	11	No reponse from remote.
PVC_USRERROR	12	User interface error detected.
PVC_INTERROR	13	Internal error.
PVC_NOATTACH	14	Not attached yet.
PVC_WAIT	15	Wait code, not to user.

STATE

This message primitive is valid in the disconnected phase.

RESPONSE

When an NS user issues a PVC Attach, the NS user expects a PVC Attach message primitive from the NS provider in response.

USAGE

The PVC Attach message primitive is equivalent to the N_CONN_REQ(7) and N_CONN_CON(7) of the Network Provider Interface (NPI)[2], npi(7).

NOTICES

The Network Layer Interface (NLI) is a proprietary interface without a formal standard. Either the Network Provider Interface (NPI)[2], npi(7), or the XTI-X25 interface[3], xti_x25(3), should be used in its stead.

FILES

N_PVC_ATTACH is defined in the <netx25/x25_proto.h> file.

COMPATIBILITY

N_PVC_ATTACH is compatible with NLI, and implementations based on NLI such as Solaris Solstice® X.25 9.2[4], IRIX SX.25[5], HP-UX X.25/9000, PT X.25[6], with the following considerations:

---: Solaris Solstice® X.25 9.2[4], IRIX SX.25[5], PT X.25[6], are consistent in their documentation of N_PVC_ATTACH.
---: NLI is an inherently low level and non-portable interface and should not be used by portable programs. Portable programs should use the NPI or XX25 interfaces in its stead.
---: Binary compatibility is not attempted: only a rough source compatibility. Any binary compatibility exhibited is a bug and is scheduled to be removed in the next release.

See NLI(7), STREAMS(4), for additional compatiblity considerations.

CONFORMANCE

The NLI is not a formal standard. The OpenSS7tm implementation of NLI conforms to documentation for Version 3 of the NLI.

HISTORY

The NLI is an interface originally developed by Spider Systems, Ltd. (now a division of Emmerson Power). The NLI interface found its way into may mainstream UNIX implementations and UNIX-like RTOS sporting STREAMS such as Windriver's VxWorks. The NLI was never standardized and remains an inherently non-portable interface.

VERSIONS

This manual page was written for the OpenSS7tm implementation of X.25.

REFERENCES

[1]: NLI, OpenSS7 CAE Specification: Network Layer Interface (NLI) Specification, Revision 0.9.2, Draft 1, July 15, 2008, (Edmonton, Canada), B. Bidulock, OpenSS7 Corporation. Distributed with package strx25-0.9.2. <http://www.openss7.org/specs/nli.pdf>
[2]: NPI, Open Group CAE Specification: Network Provider Interface (NPI) Specification, Revision 2.0.0, Draft 2, August 17, 1992, (Parsippany, New Jersey), UNIXInternational,Inc., UNIX International Press. <http://www.openss7.org/docs/npi.pdf>
[3]: C411 (XX25), X/Open CAE Specification: X.25 Programming Interface using XTI (XX25), November 1995, (Berkshire, UK), X/Open, Open Group Publication. [ISBN: 1-85912-136-5] <http://www.opengroup.org/onlinepubs/>
[4]: 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/>
[5]: IRIX® SX.25, SX.25 NLI Programming's Guide, 1994, (Mountainview, California), Silicon Graphics, Inc., SGI Technical Publications. [Doc. No: 007-2268-002] <http://techpubs.sgi.com/>
[6]: PT X.25, X.25 Protocol User's Manual, 2007, (Rochester, New York), Performance Technologies Inc., PT.

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 X.25 Networking: Package strx25 version 0.9.2.1 released 2008-10-31.

Index

NAME
INTERFACE
SYNOPSIS
DESCRIPTION
FORMAT
MEMBERS
STATE
RESPONSE
USAGE
NOTICES
FILES
SEE ALSO
COMPATIBILITY
CONFORMANCE
HISTORY
VERSIONS
REFERENCES
TRADEMARKS
IDENTIFICATION

This document was created by man2html, using the manual pages.
Time: 23:09:38 GMT, May 19, 2013