CA-11CA Datacom - DBCA DatacomCA Datacom - ADCA Datacom - ServerCA CISCA Common Services for z/OSCA 90s ServicesCA Database Management Solutions for DB2 for z/OSCA Common Product Services ComponentCA Common ServicesCA Datacom/ADCA ecoMeter Server Component FOCCA Easytrieve Report Generator for Common ServicesCA Infocai MaintenanceCA IPCUnicenter CA-JCLCheck Common ComponentCA Mainframe VM Product ManagerCA Chorus Software ManagerCA On Demand PortalCA Service Desk Manager - Unified Self ServiceCA PAM Client for Linux for zSeriesCA Mainframe Connector for Linux on System zCA Graphical Management InterfaceCA Web Administrator for Top SecretCA CA- Xpertware
Does Datacom require dedicated XES signal paths (transport classes)?
While we recommend that dedicated transport classes for Datacom are kept, this is not a requirement.
Datacom does recommend a class buffer size of at least 1280 (instead of the default 956) if the transport class is for CA Workload Automation Restart Option for z/OS Schedulers - 11.0 (aka "CA-11") communicating with the Datacom MUF via XCF. Size of 1280 would cover all messages between CA-11 and Datacom.
Generally speaking, sharing transport classes with other XCF groups will also increase the probability of "no buffer available" conditions.
The crucial point for optimization in transport class assignments is the size of buffers.
Refer to IBM publications "MVS Programming Services, SYSPLEX Reference".