According to V9.6 release notes ATTACH SERVICES component of the kernel in zOS EntireX Broker will be retired in the future (sometime after 9.6). So what upgrade path do customers have that are using this now, in particular to startup ACI servers. Do they now have to write their own?
Here is the snippet:
Features to be Dropped in Future Versions
The following features and platforms are not planned to be supported in future versions.
Broker Services have been partially retired since EntireX version 8.0. They will be fully retired with the next version of EntireX. This affects in particular the following components:
Broker Services WebSphere MQ Support
Retired since version 8.0. There will be no direct replacement for the Broker Services WebSphere MQ support. However, WebSphere MQ is supported with the EntireX WebSphere MQ RPC Server and the EntireX WebSphere MQ Listener. For scenarios using the Broker Services WebSphere MQ support, both of these might be a more modern and easier-to-use alternative.
Broker Services APPC Adapter
Retired since version 8.0. There was no replacement for the Broker Services APPC Adapter. We recommend using the standard EntireX functionality in the future. Possible migration paths can vary and should be determined based on your projects.
Broker Services Attach Service
There will be no replacement for the Broker Services Attach Service. Most of the RPC server implementations support multiple worker models for load balancing purposes. See for example Scenario Worker Models under CICS | Batch. For Natural RPC servers, the Natural RPC Server front-end provides similar functionality.