• z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference
  • Macro API (EZASMI) for assembler programs
  • CALL instruction API (EZASOKET) supporting COBOL, PL/I, and System/370 assembler languages
  • REXX socket API
• z/OS Communications Server: IP CICS Sockets Guide
  • CICS® C socket calls (EZACIC07 or EZACIC17, which calls EZASOKET with entry in EZACICAL)
  • CICS CALL instruction API (EZASOKET with entry in EZACICAL) supporting COBOL, PL/I, and System/370 assembler languages
• z/OS Communications Server: IP IMS Sockets Guide
  • IMS™ CALL instruction API (EZASOKET) supporting COBOL, PL/I, and System/370 assembler languages
• z/OS XL C/C++ Runtime Library Reference
  • z/OS® IBM® C/C++ sockets API within the z/OS Language Environment®
• z/OS UNIX System Services Programming: Assembler Callable Services Reference
  • Assembler Callable Services (BPX1IOC or BPX4IOC)

Each programming language has its own control block structure mapping. All mappings and header files are stored in SEZANMAC and the C language headers are also installed in file system directory /usr/include. The following programming languages are supported:

Assembler

Include EZBZTLSP mapping. See z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference for coding an ioctl call in assembler or coding an ioctl call for a callable API.

See z/OS UNIX System Services Programming: Assembler Callable Services Reference for coding BPX1IOC or BPX4IOC.

PL/I

Include EZBZTLS1 mapping. See z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference, z/OS Communications Server: IP CICS Sockets Guide, or z/OS Communications Server: IP IMS Sockets Guide for coding an ioctl in PL/I.

COBOL

Include EZBZTLSB mapping. See z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference, z/OS Communications Server: IP CICS Sockets Guide, or z/OS Communications Server: IP IMS Sockets Guide for coding an ioctl call in COBOL.

REXX

No mapping or header file used. See z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference for coding an ioctl call in REXX.

C

Include EZBZTLSC header file, which is installed in SEZANMAC and in the file system directory /usr/include. See z/OS XL C/C++ Runtime Library Reference or z/OS Communications Server: IP CICS Sockets Guide for coding an ioctl call in C.

See the control block structures in SEZANMAC and in the /usr/include directory for variable names and locations and their enumerated values.

• All ioctl calls must set the Version field. See the control block structures in SEZANMAC for constants declared for these variables.
  Guideline: The TTLS_CURRENT_VERSION constant in EZBZTLSC.h is being deprecated and will remain defined as 1. Use a specific TTLS version level constant, such TTLS_VERSION2, to set the TTLSi_Ver level when coding SIOCTTLSCTL Ioctl requests.
• Any field not used must be set to 0.
• If the additional buffer is required for the SIOCTTLSCTL ioctl, the buffer pointer is specified in TTLSi_BufferPtr and must point to the beginning of the buffer. The length of the buffer area is specified in TTLSi_BufferLen. Obtain enough buffer storage to hold the returned data. The buffer area can be part of the storage obtained for the base ioctl or it can be stand-alone storage. If the buffer is not large enough, the variable errno indicates the value ENOBUFS with the required buffer size specified in TTLSi_Cert_Len.