MIGRATOR CDBAPARM member ignored determine where the parameter values are being picked up from for RC/Migrator
search cancel

MIGRATOR CDBAPARM member ignored determine where the parameter values are being picked up from for RC/Migrator

book

Article ID: 54779

calendar_today

Updated On:

Products

RC/Migrator for DB2 for z/OS

Issue/Introduction

Want to amend the PDSSHR parameter in the hlq.CDBAPARM(MIGRATOR) member from YES to NO, so that ddname DDLFILET is not dynamically allocated.

With the hlq.CDBAPARM(MIGRATOR) member updated, setting PDSSHR to NO, the change is ignored and ddname DDLFILET is still dynamically allocated.

PDSSHR  (NO)                       /* OUTPUT PDS USAGE.  SPECIFY    */
                                   /* YES IF THE ANALYSIS PDS WILL  */
                                   /* BE SHARED BY MULTIPLE USERS.  */

There is nowhere in the job output to determine where the PDSSHR parameter default is being picked up from.

Resolution

Check to see if an alternate hlq.CDBAPARM member exists for RC/Migrator, called RCMIGnn. This can be verified by entering the STATUS command on the Database
Management for Db2 for z/OS,  Product Main Menu. This will display the status of each hlq.CDBAPARM member processed.

If an hlq.CDBAPARM(RCMIGnn) member exists for this environment then it is read as the default. The normal default, MIGRATOR member, is ignored.

In this case, amend the PDSSHR parameter in the hlq.CDBAPARM(RCMIGnn) member, to set the default to NO and then rerun the job.

Another circumvention is If the output is changed to use Managed Output the PDSSHR setting is ignored.

Additional Information

MIGRATOR Parmlib Options

Product Parmlib Members