Last year we implemented ECI v2 in CA Gen 8.6 as a middleware choice for Gen C clients: GUI, COM Proxy, and C Proxy. (Details Here) A few customers have asked if we’ll be implementing similar changes for Java. We recently started investigating this and are pleased to inform you that it already works! It’s an unexpected benefit from last year’s work.
The Gen Java ECI runtimes were already coded to handle >32K in preparation for when the Gen z/OS runtimes could handle that much data. Last year's work to add support for Channels and Containers to the Gen z/OS runtimes allows Gen Java clients to take advantage of those changes as well. You’ll need to apply PTFs SO12045, SO12046, and SO16152 to your z/OS environment in order to pick up the changes.
To pass >32K from Gen Java clients via ECI, configure a CICS Server in your CICS Transaction Gateway to use the IPIC network protocol and then specify that CICS Server in your commcfg.properties file. The TCP/IP network protocol always uses the CommArea, which is limited to <32K. When configured to use IPIC, the Gen Java ECI runtimes will automatically choose to send <32K through the CommArea and >32K via Containers.
The CA Gen product team still plans to do a certification testing and create additional documentation for customers. We should have capacity within the next year. However, we want you to be able to take advantage of this functionality right away, and we will support ECI “v2” for Java using IPIC.
Have a great day!
------------------------------
Kim Peelman
Product Owner, CA Gen
Broadcom
Plano,TX
------------------------------