Compiling and linking C and COBOL applications

This section gives some examples showing how to compile and link typical ECI, EPI, and ESI applications in the various client environments. These are examples only, and may refer to specific compilers and linkers.

Refer to the samples supplied with your environment (see Sample programs) for more information about compiling and linking programs.

For details of supported compilers, see the CICS Transaction Gateway: Administration book for your operating system.

Table 1 shows the header files for C required for your programs:
Table 1. C header files
Use File
ECI cics_eci.h
EPI cics_epi.h
ESI cics_esi.h
Type definitions cicstype.h
Table 2 shows the copybook files for COBOL required for your programs:
Table 2. COBOL copybooks
Use File
ECI cicseci.cbl
EPI cicsepi.cbl
ESI cicsesi.cbl

The files contain the entry points, type definitions, data structures, and constants needed for writing programs using the ECI, EPI, and ESI interfaces.

When compiling C programs, you might need to pass structures to the external CICS® interfaces in packed format. If this is the case, the C header files will contain the #pragma pack directive, which should not be changed.

For Micro Focus COBOL, you must use call-convention 8 for every program call, or use the default call-convention 0 and compile using the LITLINK compiler directive.