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

book

Article ID: 8050

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server 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

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.

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. 

 

Environment

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

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