t_connect.3

7号信令功能代码,为开源代码

'\" rtp
.\" -*- nroff -*- vim: ft=nroff
.\"
.\" @(#) t_connect.3,v 1.1.4.1 2004/01/12 23:32:49 brian Exp
.\"
.\" =========================================================================
.\"
.\" Copyright (C) 2001-2004  OpenSS7 Corporation <www.openss7.com>
.\"
.\" All Rights Reserved.
.\"
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\"
.\" Permission is granted to copy and distribute modified versions of this
.\" manual under the conditions for verbatim copying, provided that the
.\" entire resulting derived work is distributed under the terms of a
.\" permission notice identical to this one
.\" 
.\" Since the Linux kernel and libraries are constantly changing, this
.\" manual page may be incorrect or out-of-date.  The author(s) assume no
.\" responsibility for errors or omissions, or for damages resulting from
.\" the use of the information contained herein.  The author(s) may not
.\" have taken the same level of care in the production of this manual,
.\" which is licensed free of charge, as they might when working
.\" professionally.
.\" 
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.\" -------------------------------------------------------------------------
.\"
.\" U.S. GOVERNMENT RESTRICTED RIGHTS.  If you are licensing this Software
.\" on behalf of the U.S. Government ("Government"), the following
.\" provisions apply to you.  If the Software is supplied by the Department
.\" of Defense ("DoD"), it is classified as "Commercial Computer Software"
.\" under paragraph 252.227-7014 of the DoD Supplement to the Federal
.\" Acquisition Regulations ("DFARS") (or any successor regulations) and the
.\" Government is acquiring only the license rights granted herein (the
.\" license rights customarily provided to non-Government users).  If the
.\" Software is supplied to any unit or agency of the Government other than
.\" DoD, it is classified as "Restricted Computer Software" and the
.\" Government's rights in the Software are defined in paragraph 52.227-19
.\" of the Federal Acquisition Regulations ("FAR") (or any success
.\" regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the
.\" NASA Supplement to the FAR (or any successor regulations).
.\"
.\" =========================================================================
.\" 
.\" Commercial licensing and support of this software is available from
.\" OpenSS7 Corporation at a fee.  See http://www.openss7.com/
.\" 
.\" =========================================================================
.\"
.\" Last Modified 2004/01/12 23:32:49 by brian
.\"
.\" =========================================================================
.so lis.macros
.R1
bracket-label "\fR[\fB" "\fR]" "\fR, \fB"
no-default-database
database lis.refs
accumulate
move-punctuation
abbreviate A
join-authors ", " ", " " and "
et-al " et al" 2 3
abbreviate-label-ranges ".."
sort-adjacent-labels
.R2
.\"
.\"
.\"
.\"
.TH T_CONNECT 3 "2004/01/12 23:32:49" "LiS-2_16_18-8" "Linux Fast-STREAMS XTI Library"
.\"
.\"
.SH NAME
.B t_connect
\- establish a transport connection
.\"
.\"
.SH SYNOPSIS
.PP
.B #include <xti.h>
.HP 8
.BI "int t_connect(int " fd ", struct t_call *" sndcall ", struct t_call *" rcvcall );
.\"
.\"
.SH ARGUMENTS
.PP
.TP 12
.I fd
the transport endpoint to connect.
.TP
.I sndcall
a pointer to a
.B t_call
structure specifying the peer address, options and data.
.TP
.I rcvcall
a pointer to a
.B t_call
structure returning the responding address, options and data.
.\"
.\"
.SH DESCRIPTION
.PP
.I fd
is the file descriptor of the local transport endpoint.
.PP
.I sndcall
is a
.B t_call
structure that specifies the address of the peer and the options and
connection data to send to the peer.
.PP
.I rcvcall
is a
.B t_call
structure that specifies the responding address, response options and
connection data received from the peer.
.PP
The
.IR sndcall " and " rcvcall
are
.B t_call
structures that specify the called and responding addresses.  The
.B t_call
structure is formated as follows:
.sp
.nf
\fC\s-1\
struct t_call {
        struct netbuf addr;             /* address */
        struct netbuf opt;              /* options */
        struct netbuf udata;            /* user data */
        int sequence;                   /* sequence number */
};
\fR\s+1
.fi
.TP 12
.I addr
is a
.BR netbuf (3)
structure specifying the area and length of the protocol address.
.I sndcall->addr
passes in on call the called address for the connection, if any.
.I sndcall->addr.len
is significant and
.I sndcall->addr.maxlen
is not.
.I rcvcall->addr
returns the responding address for the connection, if any.
.I rcvcall->addr.maxlen
is significant on call and
.I rcvcall->addr.len
is significant on return.
.TP 12
.I opt
is a
.BR netbuf (3)
structure specifying the area and length of the connection options.
.I sndcall->opt
passes in on call the local connection options.
.I sndcall->opt.len
is significant and
.I sndcall->opt.maxlen
is not.
.I rcvcall->opt
returns the remote connection options.
.I rcvcall->opt.maxlen
is significant on call and
.I rcvcall->opt.len
is significant on return.
.TP 12
.I udata
is a
.BR netbuf (3)
structure specifying the area and length of the connection data.
.I sndcall->udata
passes in on call the local connection data.
.I sndcall->udata.len
is significant and
.I sndcall->udata.maxlen
is not.
.I rcvcall->udata
returns the remote connection data.
.I rcvcall->udata.maxlen
is significant on call and
.I rcvcall->udata.len
is significant on return.
.TP 12
.I sequence
is not significant in the
.BR t_connect ()
call.
.\"
.\"
.SH CAVEATS
.PP
.BR t_connect ()
is only valid in state
.BR T_IDLE .
.PP
In syncrhonous mode,
.BR t_connect ()
blocks until it successfully receives a connection confirmation.
In asynchronous mode (i.e.
.BR O_NONBLOCK " or " O_NDELAY
is set with
.BR t_open "(3) or " fcntl (2)),
.BR t_connect ()
will return immediately after failing to read a connection confirmation
with a a return value of -1 and
.IR t_errno (3)
set to
.BR T_NODATA .
.\"
.\"
.SH "RETURN VALUE"
.PP
Upon success,
.BR t_connect ()
returns zero (0), confirms the connection request and provides the responding
address, options and connection data in the
.I rcvcall
.B t_call
structure.
Upon failure,
.BR t_connect ()
returns -1 and sets
.IR t_errno (3)
to an appropriate error number.
.\"
.\"
.SH ERRORS
.PP
When
.BR t_connect ()
fails, it returns -1 and sets
.IR t_errno (3)
to an appropriate error number as follows:
.TP 12
.RB [ TACCES ]
The caller did not have sufficient permissions to use the address or options specified in
.IR sndcall->addr " or " sndcall->opt .
.TP 12
.RB [ TADDRBUSY ]
The
.I sndcall->addr
specificed was already in use by another transport endpoint.
.TP 12
.RB [ TBADADDR ]
The
.I sndcall->addr
specified was of an invalid format or contained invalid information.
.TP 12
.RB [ TBADDATA ]
The amount of data specified for the call
.I sndcall->udata.len
provider was invalid for the underlying transport service (i.e. was outside
the protocol limits).  See
.BR t_getinfo "(3) and " t_open (3)
for more information.
.TP 12
.RB [ TBADF ]
.I fd
is invalid.
.TP 12
.RB [ TBADOPT ]
The options specified were of an invalid format or contained invalid information.
See
.BR t_optmgmt (3)
for more information on option formats.
.TP 12
.RB [ TBUFOVFLW ]
The
.I maxlen
field of a
.BR netbuf (3)
structure,
.IR rcvcall->addr.maxlen ", " rcvcall->opt.maxlen " or " rcvcall->udata.maxlen ,
passed to the call was non-zero, but insufficient to hold the available opaque
information.  See,
.BR netbuf (3)
for more information.
.TP 12
.RB [ TLOOK ]
An asynchronous event occured before the call could complete.  See
.BR t_look (3)
for more information.
.TP 12
.RB [ TNODATA ]
An attempt was made to read a connection confirmation but
.I fd
was set for non-blocking operation with
.BR O_NONBLOCK " or " O_NDELAY
and no connection confirmation was available.
The connection confirmation can be retrieved later with
.BR t_rcvconnect (3).
.TP 12
.RB [ TNOTSUPPORT ]
The call requires the use of a TLI primitive not supported by the underlying transport provider.
.TP 12
.RB [ TOUTSTATE ]
The call was issued with the interface in an incorrect state.
.TP 12
.RB [ TPROTO ]
A protocol error occured between the XTI library and the underlying transport provider.
.TP 12
.RB [ TSYSERR ]
A
.B Linux
system error occured and the
.B Linux
error number is set in
.IR errno (3).
.\"
.\"
.SH "SEE ALSO"
.PP
.BR fcntl (2),
.BR netbuf (3),
.BR t_errno (3),
.BR t_getinfo (3),
.BR t_look (3),
.BR t_open (3),
.BR t_rcvconnect (3).
.PP
.\"
.\"
.SH "BUGS"
.PP
.BR t_connect ()
has no known bugs.
.BR t_connect ()
has been tested for the described behavior using the
.I /usr/bin/test-xnet
conformance test program.
.\"
.\"
.SH "CONFORMING TO"
.PP
XTI/TLI,
.[
XTI
.]
TPI,
.[
TPI Revision 2.0.0
.]
XPG5,
XNS 5.2,
.[
xns
.]
SUSv2.
.[
susv2
.]
.\"
.\"
.[
$LIST$
.]
.TI