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

book

Article ID: 32834

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

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: