Datacom XES signal paths (transport classes)

Products

• CA-11
• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Does Datacom require dedicated XES signal paths (transport classes)?

Environment

z/OS

Resolution

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".