If the t_open is successful, the value returned is a file descriptor that identifies the local transport endpoint. This document uses the variable spxFd to refer to this value.
If t_open returns an error, t_errno may be set to one of the following.
TSYSERR
A system error has occurred during execution of this function. Check errno for possible further information.
TBADFLAG
An invalid flag was specified.
Remarks
The t_open function creates a local transport endpoint and returns protocol-specific information associated with that endpoint as well as a file descriptor that serves as the local identifier of the endpoint. Both server and client applications can use this call to open a transport endpoint.
The path and name of the clonable SPXII device is /dev/nspx2 or /dev/nspx. The difference between opening nspx2 and nspx depends on the options that are allowed in other TLI calls:
Opening ``nspx2'' allows an expanded set of options associated with SPXII (see the t_optmgmt documentation).
Opening ``nspx'' allows a set of options compatible with SPX (see the t_optmgmt documentation).
A successful t_open call returns a TLI information structure. The t_info structure contains the following information about SPX/SPXII.
SPX/SPXII Information in the t_info Structure
Field
Value
Description
addr
12 (bytes)
This is the number of bytes required for an IPX address.
The address consists of three components: network address (4 bytes),
node address (6 bytes), socket number (2 bytes)
tsdu
-1
An unlimited amount of data can be sent during a connection
etsdu
-2
Not supported
connect
-2
Not supported
discon
-2
Not supported
servtype
T_COTS_ORD
The service type for SPXII is always T_COTS_ORD.
SPXII is a connection-oriented service with orderly release
(nspx) options
4
SPX supports 4 bytes of option data. For a description, see
t_optmgmt(3xti_spx)
(nspx2) options
52
SPXII supports 52 bytes of option data. For a description, see
t_optmgmt(3xti_spx)