Compiling and linking ECI, EPI, and ESI applications in
an Solaris environment.
For local C applications
- The constant CICS_SOL must be defined to the compiler using the
-DCICS_SOL option.
- The application must be linked with the standard Solaris libpthread.so
and libc.so libraries, as well as the libcclsol.so library.
- 32-bit applications are supported
For remote C applications (ECI V2 and ESI V2)
- The constant CICS_SOL must be defined to the compiler using the
-DCICS_SOL option.
- The application must be linked with the standard Solaris libpthread.so
and libc.so libraries, as well as the libctgclient.so library.
- 32-bit and 64-bit applications are supported
For statistics applications
- The constant CICS_SOL must be defined to the compiler using the
-DCICS_SOL option.
- The application must be linked with the standard Solaris libpthread.so
and libc.so libraries, as well as the libctgstats.so library.
- 32-bit applications are supported
For local COBOL applications
- It is important to use the correct calling convention when calling
the ECI or EPI from COBOL. When you are using MicroFocus COBOL the
sample programs use the "SPECIAL-NAMES CALL CONVENTION 8 IS CICS®" statements to achieve
the correct calling convention.
- To build an application object files must be linked with the libcclsol.so
library file. Only 32-bit applications are supported by the API.
- ECI or EPI callback functions are not supported in COBOL applications.
Solaris is supported exclusively on SPARC.