z/OS Communications Server: IP CICS Sockets Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


C socket library

z/OS Communications Server: IP CICS Sockets Guide
SC27-3649-00

To use the socket routines described in this topic, you must include these header files:
bsdtime.h
bsdtypes.h
cmanifes.h (reentrant programs only)
errno.h    (reentrant programs only)
ezacichd.h (non-reentrant programs only)
ezbpinfc.h (if using the SIOCGPARTNERINFO or SIOCSPARTNERINFO IOCTL calls)
ezbztlsc.h (if using IOCTL calls related to AT-TLS)
fcntl.h 
if.h
in.h   
inet.h 
ioctl.h
manifest.h (non-reentrant programs only)
netdb.h
rtrouteh.h
socket.h
uio.h

The files are in the SEZACMAC, SEZAINST, and SEZANMAC data sets, which must be concatenated to the SYSLIB DD in the compilation JCL (as described in Step 1 of Changes to DFHYITDL). These files contain a .h extension in this text to distinguish them as header files.

In the IBM® implementation, you must include either manifest.h (if the program is non-reentrant) or cmanifes.h (if the program is reentrant) to remap function long names to 8-character names. To reference manifest.h or cmanifes.h, you need to include one of the following statements as the first #include at the beginning of each program:

Non-reentrant programs:
#include <manifest.h>

Reentrant programs:
#include <cmanifes.h>
Include the following definition to expose the required IPv6 structures, macros, and definitions in the header files in C socket library:
#define __CICS_IPV6
Include the following definition to expose structures, macros and definitions in the TCP C header files previously listed:
#define __CICS_SOCKETS

Include the in.h header before the socket.h header because the socket.h header needs structure types that are defined by in.h.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014