RC/Migrator for DB2 for Z/OS : Do not generate 'SET CURRENT SQLID' statements?
search cancel

RC/Migrator for DB2 for Z/OS : Do not generate 'SET CURRENT SQLID' statements?

book

Article ID: 54709

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS RC/Migrator for DB2 for z/OS

Issue/Introduction

By default, the 'SET CURRENT SQLID' statements are generated automatically in the DDL that RC/Migrator for DB2 for z/OS (RCM) generates.

'SET CURRENT SQLID' statements are issued to ensure that correct CREATOR and CREATED BY authorization IDs are used when creating objects.

However, sometimes users may not want to have these statements generated. Is there a way that they can be suppressed?

 

Environment

Release: R20
Component: RCM

Resolution

If you do not want RC/Migrator to generate 'SET CURRENT SQLID' statements, set the 'NO SET CURRENT SQLID' in the RC/Migrator's profile settings to Y.

From the RC/Migrator main menu, select option:
0 - Profile, then
2 - RC/Migrator Profile Variables, then
Set "NO SET CURRENT SQLID ===> Y"

                                                                                                                        

Indicate whether you want a SET CURRENT SQLID statement generated.

Values:  Y   The analysis output file will not contain SET CURRENT SQLID statements.

             .AUTH will contain the SQLID of the CREATOR ID of the object, rather than the CREATEDBY ID.

             N   (Default) Generate SET CURRENT SQLID = sqlid statements to set the SQLID as the CREATOR.

             Use the .AUTH command to preserve the CREATEDBY of an object.

 

Additional Information

For more information, please refer to "Manage Profile Options" of the RC/Migrator for DB2 for z/OS User Guide.