Open System Services System Calls Reference Manual (G06.29+, H06.08+, J06.03+)

ManualsBrandsHP ManualsServerHP NonStop G-Series

801

802

803

804

805

806

807

808

809

810

socket_transport_name_set(2) OSS System Calls Reference Manual

For more information about AF_UNIX Release 2, see the Open System Services Programmer’s

Guide.

NOTES

This function is equivalent to the socket_set_inet_name() function in the Guardian sockets

library.

This function requires that the feature-test macro _XOPEN_SOURCE_EXTENDED be speciﬁed

when you compile the module.

The process name speciﬁed in the socket_transport_name_set() function call is validated dur-

ing each call to the socket(), socketpair(),orsocket_transport_name_get() function. Process

names are not validated during calls to the socket_transport_name_set() function.

Choosing the Transport-Provider Process

Each socket declared by a user process is supported by:

• An OSS transport agent process (one per processor)

• A domain-speciﬁc transport-provider process (one or more per node)

Each user process has a current transport-provider name for each domain that is used when creat-

ing a socket in that domain.

The default AF_INET or AF_INET6 transport-provider name is $ZTC0, unless overridden by

an existing Guardian DEFINE =TCPIPˆPROCESSˆNAME. If =TCPIPˆPROCESSˆNAME exists,

it must be a MAP DEFINE with a FILE attribute string of the desired AF_INET or AF_INET6

transport-provider name.

For systems running AF_UNIX Release 1 software, $ZPLS is the only supported AF_UNIX

transport-provider name and this name cannot be changed.

For systems running AF_UNIX Release 2 software:

• The default AF_UNIX transport-provider name is $ZPLS, unless it has been overridden

by the setting the Guardian DEFINE =_AFUNIX_PROCESS_NAME to $ZAFN2. This

deﬁne must be a MAP DEFINE with a FILE attribute string of the desired AF_UNIX

transport-provider name.

• To create a socket in portability mode, choose transport-provider name $ZAFN2. Sock-

ets created in portability mode can communicate with each other but cannot communi-

cate with sockets created in compatibility mode.

• To create a socket in compatibility mode, choose transport-provider name $ZPLS. Sock-

ets created in compatibility mode can communicate with each other but cannot commun-

icate with sockets created in portability mode.

For more information about AF_UNIX Release 2, see the Open System Services Programmer’s

Guide.

Each user process can change its AF_INET, AF_INET6,orAF_UNIX transport-provider name

with the socket_transport_name_set() function and can retrieve its current AF_INET,

AF_INET6, and AF_UNIX transport-provider names with the socket_transport_name_get()

function.

Changing the AF_INET or AF_INET6 transport-provider name is meaningful when a node is

conﬁgured with multiple TCP/IP processes as part of the AF_INET or AF_INET6 socket

environment or the Cluster I/O Protocols (CIP) networking environment. When using the CIP

networking environment, you must choose a transport provider that is a CIPSAM process. The

default transport-provider name is $ZTC0. The default program name is CIPSAM. For more

7−128 Hewlett-Packard Company 527186-023