T_UNITDATA_REQ

Section: Transport Provider Interface (TPI) (7)
Updated: 2008-10-31
Index Return to Main Contents

NAME

T_UNITDATA_REQ - Unitdata Request

SYNOPSIS

This message consists of one M_PROTO message block followed by zero or more M_DATA message blocks where each M_DATA message block contains zero or more bytes of data. The format of the M_PROTO message block is as follows:

struct T_unitdata_req {
t_scalar_tPRIM_type;/*AlwaysT_UNITDATA_REQ*/
t_scalar_tDEST_length;
t_scalar_tDEST_offset;
t_scalar_tOPT_length;
t_scalar_tOPT_offset; };

DESCRIPTION

This primitive requests that the transport provider send the specified datagram to the specified destination.

PARAMETERS

PRIM_type: identifies the primitive type.
DEST_length: is the length of the destination address
DEST_offset: is the offset (from the beginning of the M_PROTO message block) where the destination address begins.
OPT_length: is the length of the requested options associated with the primitive.
OPT_offset: is the offset (from the beginning of the M_PROTO message block) of the requested options associated with the primitive.

The proper alignment of the destination address and options in the M_PROTO message block is not guaranteed. The destination address and options in the M_PROTO message block are, however, aligned the same as they were received from the transport user.

This primitive does not require any acknowledgment. If a non-fatal error occurs, it is the responsibility of the transport provider to report it via the T_UDERROR_IND(7) indication. Fatal errors are indicated via a M_ERROR message type which results in the failure of all operating system service routines on the stream.

ERRORS

The allowable fatal errors are as follows:

[EPROTO]: This indicates one of the following unrecoverable protocol conditions:
-: The transport service interface was found to be in an incorrect state.
-: The amount of transport user data associated with the primitive defines an transport service data unit larger than that allowed by the transport provider.

MODES

Only connectionless-mode.

ORIGINATOR

Transport user.

HISTORY

The Transport Provider Interface first appeared in SVR 4[1].

CONFORMANCE

This interface conforms to TPI Version 2, Draft 2[2].

REFERENCES

[1]: SVR 4, UNIX® System V Release 4 Programmer's Manual, 1990, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[2]: TPI Revision 2.0.0, Open Group CAE Specification: Transport Provider Interface (TPI) Specification, Revision 2.0.0, Draft 2, 1999, (Berkshire, UK), OpenGroup, Open Group Publication. <http://www.opengroup.org/onlinepubs/>
[3]: 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]
[4]: 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 XTI/TLI Networking: Package strxnet version 0.9.2.12 released 2008-10-31.

This document was created by man2html, using the manual pages.
Time: 15:53:03 GMT, May 19, 2013

Description: Manual Page

Keywords: ss7 ss7/ip ss7 over ip ss7 mtp ss7 sccp ss7 tcap sigtran mtp sccp tcap openss7 acb56 linux telephony pstn linux telephony linux nebs linux compactpci