RC 25 (01) during CATALOG Dynamic System Tables - job DBACTDYN

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

RC 25 (01) during CATALOG Dynamic System Tables - Upgrade job DBACTDYN

 

RC 25(01) INVALID DIRECTORY MAINTENANCE TO BASE DEFINED AS VIRTUAL

An attempt is being made to do Directory maintenance to a database defined as virtual. This is not allowed. This includes the ALTER option of the CXXMAINT function of DBUTLTY and SQL Data Definition Language (DDL) statements.

Astion: Perform the maintenance in a Multi-User Facility where this database is not virtual.

Environment

z/os 2.1; CA Datacom/DB 14.0 upgrading to 15.1

Cause

Customer using in Multi-User startup cards:

SYSTEMDBID 1000

and 

VIRTUAL 1000,500K

 

Starting CA Datacom/DB 12.0 

startup card VIRTUAL 1000 has been replaced by SYSTEMDBID 1000.

So using both is redundant and may confuse the Multi-User. 

 

Resolution

Startup Card VIRTUAL 1000,500K  should be removed.

Additional Information

From CA Datacom/DB System and Administration Guide:

SYSTEMDBID

(Optional) Specifies the database ID (the DATACOM-ID attribute-value of the database definition in Datadictionary) which contains any dynamic system tables used to obtain real-time information as the MUF is running.

Note: You must specify the SYSTEMDBID MUF startup option in order to activate Dynamic System Table access from the MUF.

If you do not specify the SYSTEMDBID option, attempts to access any of the dynamic tables receives a no record found condition.

The database specified in SYSTEMDBID is never opened to DASD and should not be defined as virtual.    <===