EXECRBP1 created some data sets under the userid qualifier

book

Article ID: 6174

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

After binding the product packages and plans on post-installation of CA Database Management Solution for DB2, the submitted JCL, EXECRBP1 created some data sets under the userid qualifier. Here are some examples: 

userID.PTDB.PTTSRTS7.DBX1.COPY 

userID.PTDB.PTTSRVL7.DBX1.COPY 

userID.PTDB.TID366.DBX1.DATA   

userID.PTDB.TID366.DBX1.DATA.D 

userID.PTDB.TID366.DBX1.DATA.E 

 

Why that JCL created these data sets and is it okay to delete them?

Environment

Release:
Component: GEN

Resolution

The .DATA datasets are purely work files required for the ssid0001 execution. Once this job completes normally, as it did, they can be safely deleted. The .COPY datasets are image copies of the respective tablespaces that can be used for recovery if required. I really do not see that you would need the .COPY datasets as well. You can likely scratch the .COPY datasets as well. You may have a production type job that takes image copies of database PTDB for recovery purposes.