Do the SMP/E DDDEFs external datasets CAVQLOAD, CAW0LINK and SDFHLOAD in installation job DCM3CSI need to be defined with real dataset names for the SMP/E APPLY?

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

Question: 

CA DATACOM/DB installation job DCM3CSI has numerous SMP/E DDDEFs for external datasets such as:

ADD DDDEF(CAVQLOAD)

ADD DDDEF(CAW0LINK)

ADD DDDEF(SDFHLOAD)

Do these DDDEFs need to be defined with real dataset names for the SMP/E APPLY?

Will they be updated by the APPLY operation?

 

Answer: 

The 3 files are required during the SMP/E APPLY so you do need to specify a real dataset name for these.

The files are not updated but we include modules from them during some of the linkedits during the APPLY. 

SDFHLOAD is the IBM CICS/TS target load library. 

CAW0LINK is the CA Common Services CAICICS target load library. 

CAVQLOAD is the CA IPC target load library. 

 

Environment

Release:
Component: DB