Some examples showing how to compile and link typical ECI,
EPI, and ESI applications in a Windows environment.
For local C applications
- The compiler options /DWIN32, /D_WIN32, and /D_X86_=1 are used
to select the correct Windows function and are standard Win32 options. These options are not specific
to the CICS Transaction Gateway.
- The compiler option /DCICS_W32 must be used to define the symbol
CICS_W32 to the compiler to ensure that the CICS® header files are processed correctly.
- The application must be linked with the cclwin32.lib library in
addition to the standard C runtime and Windows libraries.
- Callback functions must be declared using the CICSEXIT calling
convention—see samples for details.
- 32-bit applications are supported
For remote C applications (ECI V2 and ESI V2)
- The compiler option /DWIN32 is used to select the correct Windows function and is a standard
Win32 option. This options is not specific to the CICS Transaction Gateway.
- The compiler option /DCICS_W32 must be used to define the symbol
CICS_W32 to the compiler to ensure that the CICS header files are processed correctly.
- The application must be linked with the ctgclient.lib library
in addition to the standard C runtime and Windows libraries.
- 32-bit and 64-bit applications are supported.
For statistics applications
- The compiler option /DCICS_W32 must be used to define the symbol
CICS_W32 to the compiler to ensure that the CICS header files are
processed correctly.
- The application must be linked with the ctgstats.lib library in
addition to the standard C runtime and Windows libraries.
- 32-bit applications are supported
For local COBOL programs
- It is important to use the correct calling convention when invoking
the ECI or EPI from COBOL. The sample programs use the "SPECIAL-NAMES.
CALL CONVENTION 8 IS CICS."
statements to achieve this.
- The application must be linked with the CCLWIN32.LIB library,
in addition to the standard COBOL libraries, because a 32-bit Windows application is being
generated.
- ECI or EPI callback functions are not supported in COBOL applications.