Which API can be used for container?

This table shows which APIs are supported over the IPIC and TCP/IP in local and remote mode.

To determine which scenarios are supported by CICS® Transaction Gateway, you should use this table in conjunction with the preceding table Which protocol can be used?
Table 1. APIs are supported over the IPIC and TCP/IP in local and remote mode
Linux on Intel Container, Linux on z Systems Container
API IPIC TCP/IP SNA
32 bit (Local mode) 64 bit (local mode) 32 bit (Remote mode) 64 bit (remote mode) 32 bit (Local mode) 64 bit (local mode) 32 bit (Remote mode) 64 bit (remote mode) 32 bit (Local mode) 64 bit (local mode) 32 bit (Remote mode) 64 bit (remote mode)
Java ECI x 1 1 x x
Java ESI x x x x x x
Java EPI x x x x x x
JEE non-XA x 1 1 x x
JEE XA x x x x x x x x x x x
JSON web services x x 1 1 x x x x
C/C++/COBOL ECI V1 x x x x x2 x x x x x
C/C++/COBOL ESI V1 x x x x x x x x x2 x x
C/C++/COBOL EPI x x x x x2 x x x x x
C ECI V2 x x x x x x
C ESI V2 x x 1 1 x x x x x x
.NE✓ Framework ECI x x x x x x
.NE✓ Framework ESI x x 1 1 x x x x x x
.NE✓ Core ECI x x 1 1 x x x x
.NE✓ Core ESI x x x x x x x x
Note:
  • 1 Includes channel application support. All ECI APIs and protocols support COMMAREA based applications.
  • 2 Recompilation with 64-bit compiler directives (-m64 or -q64) is needed for running 32-bit applications in local mode.
  • If you need to run a 32-bit local mode application instead of a 64-bit local mode application, then ctgsymlinks-add32 can be used to convert a 64-bit CICS TG client daemon to a 32-bit CICS TG client daemon.
  • For containers, only the remote mode API is supported for SNA configuration.