t_rcvrel(3nsl)

1t_rcvrel(3NSL)       Networking Services Library Functions      t_rcvrel(3NSL)
2
3
4

NAME

6       t_rcvrel - acknowledge receipt of an orderly release indication
7

SYNOPSIS

9       #include <xti.h>
10
11
12
13       int t_rcvrel(int fd);
14
15

DESCRIPTION

17       This  routine  is part of the XTI interfaces which evolved from the TLI
18       interfaces. XTI represents the future evolution  of  these  interfaces.
19       However,  TLI  interfaces are supported for compatibility. When using a
20       TLI routine that has the same name as an  XTI  routine,  the   tiuser.h
21       header  file must be used.  Refer to the  TLI COMPATIBILITY section for
22       a description of differences between the two interfaces.
23
24
25       This function is used to receive an orderly release indication for  the
26       incoming  direction  of  data  transfer. The argument fd identifies the
27       local transport endpoint where the connection exists. After receipt  of
28       this indication, the user may not attempt to receive more data by means
29       of  t_rcv(3NSL) or  t_rcvv(). Such an attempt will fail  with   t_error
30       set  to TOUTSTATE. However, the user may continue to send data over the
31       connection if t_sndrel(3NSL) has not been  called  by  the  user.  This
32       function  is an optional service of the transport provider, and is only
33       supported if the transport provider returned service type T_COTS_ORD on
34       t_open(3NSL)  or  t_getinfo(3NSL). Any user data that may be associated
35       with the orderly release indication is discarded  when   t_rcvrel()  is
36       called.
37

RETURN VALUES

39       Upon  successful  completion,  a value of  0 is returned.  Otherwise, a
40       value of  -1 is returned and t_errno is set to indicate an error.
41

VALID STATES

43       T_DATAXFER, T_OUTREL.
44

ERRORS

46       On failure, t_errno is set to one of the following:
47
48       TBADF          The specified file descriptor does not refer to a trans‐
49                      port endpoint.
50
51
52       TLOOK          An  asynchronous  event  has  occurred on this transport
53                      endpoint and requires immediate attention.
54
55
56       TNOREL         No orderly release indication currently  exists  on  the
57                      specified transport endpoint.
58
59
60       TNOTSUPPORT    This  function is not supported by the underlying trans‐
61                      port provider.
62
63
64       TOUTSTATE      The communications endpoint referenced by  fd is not  in
65                      one  of  the  states in which a call to this function is
66                      valid.
67
68
69       TPROTO         This error indicates that a  communication  problem  has
70                      been detected between XTI and the transport provider for
71                      which there is no other suitable XTI error (t_errno).
72
73
74       TSYSERR        A system error has occurred  during  execution  of  this
75                      function.
76
77

TLI COMPATIBILITY

79       The XTI and TLI interface definitions have common names but use differ‐
80       ent header files. This, and other semantic differences between the  two
81       interfaces are described in the subsections below.
82
83   Interface Header
84       The  XTI  interfaces  use the header file, xti.h. TLI interfaces should
85       not use this header.  They should use the header:
86         #include<tiuser.h>
87
88   Error Description Values
89       The t_errno values that can be set by the XTI interface and  cannot  be
90       set by the TLI interface are:
91         TPROTO
92         TOUTSTATE
93

ATTRIBUTES

95       See attributes(5)  for descriptions of the following attributes:
96
97
98
99
100       ┌─────────────────────────────┬─────────────────────────────┐
101       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
102       ├─────────────────────────────┼─────────────────────────────┤
103       │MT Level                     │Safe                         │
104       └─────────────────────────────┴─────────────────────────────┘
105