On a DDL or HDDL command in RC/Query why Is the SET CURRENT SQLID not the creator of the object?

book

Article ID: 49397

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 Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

Description:

When using the DDL or HDDL command on an object the user is expecting the SET CURRENT SQLID to be the CREATOR of the object. Instead it is the ID of the person using the tool.

Solution:

The intent of the DDL/HDDL command is for the user to create their own version of the object, therefore the SQLID is set to the ID of the person using the tool. DDL generated using a Quick Migrate will pick up the CREATOR of the object for the SET CURRENT SQLID since the objective is to migrate the object to another subsystem.

Environment

Release:
Component: RCQ