CA DB2 tools Post Install Compare job, ssid0000, fails within step CREATETS with SQLCODE -601 during the CREATE of tablespace PTITLOG2.

Products

• RC Compare for DB2 for z/OS
• Database Analyzer for DB2 for z/OS
• Fast Unload for DB2 for z/OS
• Fast Check for DB2 for z/OS
• Fast Index for DB2 for z/OS
• Rapid Reorg for DB2 for z/OS

Issue/Introduction

Problem:

The CA Database Management Solutions for DB2 for z/OS Post Install Compare job, ssid0000, is failing within step CREATETS.

It appears that the Compare Object job should skip step CREATETS as the stogroup, database, and tablespace PTITLOG2 already exist.  Step SGDBCHK ends with a COND CODE 04 which indicates the following:

IF BOTH THE STOGROUP AND THE DATABASE DO AND PTITLOG2
DOES NOT EXIST. RC=4

Symptoms:

CREATE TABLESPACE PTITLOG2
IN PTDB
BUFFERPOOL BP0
LOCKSIZE ANY
SEGSIZE 64
CLOSE NO
USING STOGROUP PTSG
PRIQTY -1
SECQTY -1
ERASE NO
FREEPAGE 0
PCTFREE 005

AN SQL ERROR OCCURRED DURING SQL STATEMENT EXECUTION

DSNT408I SQLCODE = -601, ERROR: THE NAME (VERSION OR VOLUME SERIAL
NUMBER) OF THE OBJECT TO BE DEFINED OR THE TARGET OF A RENAME
STATEMENT IS IDENTICAL TO THE EXISTING NAME (VERSION OR VOLUM
SERIAL NUMBER)
PTDB.PTITLOG2 OF THE OBJECT TYPE TABLESPACE

 

Cause:

The following message was noted in the ssid0000 Compare execution related to this problem:

BIND PLAN(INPOBJCK) PKLIST(INAOBJCK_PKG.*)
DSNT241I >DB2M BIND AUTHORIZATION WARNING ON PLAN INPOBJCK
AUTHORIZATION-ID xxxxxxxx NOT AUTHORIZED TO EXECUTE
PACKAGE INAOBJCK_PKG.*

 

Resolution:

The PLANOWN parameter in hlq.CDBAPARM member SETUPxx was modified to an ID with SYSADM authority.  Post install jobs regenerated and jobs completed successfully.

Environment

Release:
Component: INS