Why is a DB RC 79(87) returned after a CXXCLONE?

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

Issue:

A CXX dataset has been correctly initialized using DBUTLTY INIT function. Then a DBUTLTY CXXCLONE is successfully executed using as input a CXX backup file from a previous release; but after that all the Datacom requests (in MUF or by DBUTLTY) fail due to DB RC 79(87) (CXX IS WRONG VERSION).

 

Cause:  

If DBID=1-5000 parameter is not used, CXXCLONE assumes that not only it has to restore all the DBIDs but it has also to switch the release to the one of the BACKUP CXX. 

 

Resolution:

When using a backup file from a previous release and all the databases must be cloned, CXXCLONE function must be executed with a DBID=1-5000 parameter:

 

 CXXCLONE DDNAME=..,STATUS=...,OPTION=..,DBID=1-5000 

Environment

Release: DATABB00200-14-Datacom/AD
Component: