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

System Functions (s and S) socket_transport_name_get(2)
The value returned in the buffer pointed to by the buffer parameter is always an uppercase name.
NOTES
This function requires that the feature-test macro _XOPEN_SOURCE_EXTENDED be specified
when you compile the module.
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-specific 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 DEFINE =_AFUNIX_PROCESS_NAME to $ZAFN2. This define 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. For systems running the AF_UNIX Release 2 software, you can change the transport-
provider name using either the socket_transport_name_set() function or the Guardian DEFINE
=_AFUNIX_PROCESS_NAME. This define must be a MAP DEFINE with a FILE attribute
string of the desired AF_UNIX transport-provider name.
For more information about AF_UNIX Release 2, see the Open System Services Programmer’s
Guide.
Changing the AF_INET or AF_INET6 transport-provider name is meaningful when a node is
configured with multiple TCP/IP processes as part of the AF_INET or AF_INET6 socket
environment.
The transport-provider name is a convention and does not guarantee use of a specific TCP/IP
stack. For example, on older systems, $ZTC0 provided only Internet Protocol version 4 address-
ing for an AF_INET stack and could be used to distinguish the stack to use for sockets that do
not use AF_INET6 features. On current systems, $ZTC0 might identify an AF_INET6 pr
otocol
527186-023 Hewlett-Packard Company 7−125