If you're wondering why I'm suddenly adding stuff to this ECI v2 discussion thread, it's because we're researching ECI "v2" for Java ( >32K). I'm getting my notes organized and thought you might find it helpful grouped in this discussion thread.
So here's another nugget of info about ECI v2 for Gen C clients:
Be sure to get a defect fix:
PTF SO16152. The problem was that with ECI V2 configured for COMMAREA it was possible to send a response (from Server to Client) larger than 32K of data and that caused a storage violation.
------------------------------
Kim Peelman
Product Owner, CA Gen
Broadcom
Plano,TX
------------------------------
Original Message:
Sent: 04-06-2020 09:07 PM
From: Kim Peelman
Subject: Now Available: ECI v2 for CA Gen 8.6
We are pleased to announce that CA Gen 8.6 now supports ECI v2 as one of the middleware choices for Gen C clients (GUI, COM Proxy and C Proxy) to communicate with Gen COBOL servers on CICS.
ECI v2 provides the ability to send more than 32K of data on each cooperative flow by utilizing Containers. ECI v2 also allows the CICS Transaction Gateway (CTG) to be located on a different machine than the client applications. This allows for a smaller client footprint and for the configuration/administration of the CTG to be centralized.
CA Gen will continue to support ECI v1 for backward compatibility.
You can find the solution at the following links:
Additional documentation is available on Tech Docs:
If you have any questions, please feel free to reach out to me.
-Kim
P.S. CA Gen has moved to a continuous delivery model. To learn more about Broadcom's approach to continuous delivery and maintenance best practices, read HERE https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/traditional-management/mainframe-common-maintenance-procedures/1-0/continuous-delivery/maintenance-best-practices.html
------------------------------
Kim Peelman
Product Owner, CA Gen
Broadcom
Plano,TX
------------------------------