Open System Services Porting Guide (G06.24+, H06.03+)

Open System Services Porting Guide—520573-006
11-1
11
Porting or Migrating Sockets
Applications
This section discusses the following topics:
•
Porting UNIX Sockets Applications to the OSS Environment on page 11-1
•
Porting Guardian Sockets Applications to the OSS Environment on page 11-4
•
Interoperability of OSS and Guardian Sockets in an OSS Application on page 11-8
Porting UNIX Sockets Applications to the OSS
Environment
The following topics are discussed in this subsection:
•
General Considerations on page 11-1
•
Differences Between OSS Sockets and Berkeley Software Distribution Sockets on
page 11-2
•
Porting Situations on page 11-3
Additional considerations and sample programs can be found in the Open System
Services Programmer’s Guide.
General Considerations
The following is a list of general considerations for porting a sockets program from a
UNIX system to the OSS environment:
•
Errors with the same names are compatible from UNIX to OSS sockets routines.
UNIX and OSS sockets routine error numbers are not the same. UNIX programs
that refer to errors by number must be converted to refer to errors by name.
•
The socketpair() function cannot be used with the AF_INET or AF_INET6
domain.
•
OSS sockets programs cannot currently receive SIGIO signals.
•
OSS supports multiple transport provider processes on one node for AF_INET and
AF_INET6 sockets. If a processor has multiple IP addresses, you can specify
which transport provider process to use by setting the DEFINE
=TCPIP^PROCESS^NAME or by calling the socket_transport_name_set()
function within the application.
A specified AF_INET or AF_INET6 transport provider process must be a TCP/IP
process running on the same node as the application. The default AF_INET
transport provider process is $ZTC0. An alternate transport provider process can