HP 9000 Networking XTI Programmer's Guide

XTI over OSI Networks

Addressing

Before a transport endpoint can be used in an XTI application, a transport

selector (t-selector) must be assigned (or bound) to it.

With XTI, the application process can bind to either the t-selector only or the

t-address (includes t-selector and NSAP) as the source address in t_bind(3).

For an XTI server application requiring a combination of CONS, CLNS, or

RFC 1006, support for incoming and outgoing connections, use the t-

selector only format.

The source address used in the t_bind(3) call must be speciﬁed as a buffer of

concatenated bytes. The two supported formats are as follows:

• T-selector only:

• Complete t-address:

T-selectors need not be conﬁgured in OTS/9000 but must be unique across

all of your OSI applications.

The maximum lengths for the components of the t-address are as follows: t-

selector -- 32 bytes; n-selector (NSAP) -- 20 bytes.

Once a transport endpoint has been created by calling t_open(3), the t-

address is bound to this transport endpoint by calling t_bind(3) with the t-

address included in the t_bind(3) call. Note that if you have created a

listening and responding transport endpoint for one process, both endpoints

can be bound to the same t-address.

In order to communicate with another process, you must obtain the

conﬁgured network service access point (NSAP) and t-selector addresses for

each system on which the remote application or process resides. NSAPs and

t-selectors are used in the connection establishment phase of the program

t_sel_len transport selector

t_sel_len transport

selector

nsel_len network

selector(NSAP)