Does the CA Datacom version 15.x CUSLIB need to be PDSE?

Products

• 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

When installing and configuring the CA Datacom version 15.0 environment, both the main software loadlib (CAAXLOAD or CABDLOAD) and the custom loadlib (CUSLIB) are defined as PDS Extended format. 

Is it required that the CUSLIB defined for CA Datacom version 15.0 be a PDSE (Library), or can I use a standard PDS?

Environment

Release:
Component: DB

Resolution

There are a number of Format 3 modules delivered with CA Datacom 15.x - primarily those that are a part of the SQL component. The binder for format 3 requires PDSE formatted datasets.  Using a regular PDS for these modules (now called Program Objects) will cause the binder to fail.

However, there is no requirement at this time to create Format 3 custom modules, so the CUSLIB can still use a standard PDS. We would recommend that all loadlibs be formatted as PDSE usage for consistency, and to allow for the possibility of a future solution that might require a Format 3 module.

Additional Information

As always, please contact CA Technologies support for CA Datacom if you have further questions.