Datacom XES signal paths (transport classes)


Article ID: 107526


Updated On:


CA-11 CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA 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.

Additional Information

Refer to IBM publications "MVS Programming Services, SYSPLEX Reference".