CA-11DatacomDATACOM - ADCISCOMMON SERVICES FOR Z/OS90S SERVICESDATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesCA ECOMETER SERVER COMPONENT FOCEASYTRIEVE REPORT GENERATOR FOR COMMON SERVICESINFOCAI MAINTENANCEIPCUNICENTER JCLCHECK COMMON COMPONENTMainframe VM Product ManagerCHORUS SOFTWARE MANAGERCA ON DEMAND PORTALCA Service Desk Manager - Unified Self ServicePAM CLIENT FOR LINUX ON MAINFRAMEMAINFRAME CONNECTOR FOR LINUX ON MAINFRAMEGRAPHICAL MANAGEMENT INTERFACEWEB ADMINISTRATOR FOR TOP SECRETXpertware
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".