Migrating data objects when upgrading DB2 for z/OS

If you upgrade your DB2® for z/OS® subsystem to a higher version, and the subsystem is already configured for tuning with InfoSphere® Optim™ Query Workload Tuner, Version 3.1.1, you must migrate the data objects in that configuration.

About this task

To migrate, modify and submit the corresponding AOCTIJ JCL job. The following table lists the AOCTIJ JCL job files for each environment.

Upgrading from Upgrading to JCL job for migrating data objects for query tuning
DB2 for z/OS Version 8 new-function mode DB2 Version 10 for z/OS conversion mode from DB2 for z/OS Version 8 AOCTIJC8
DB2 Version 10 for z/OS conversion mode from DB2 for z/OS Version 8 DB2 Version 10 for z/OS new-function mode AOCTIJ8X
DB2 Version 9 for z/OS DB2 Version 10 for z/OS conversion mode from DB2 Version 9 for z/OS AOCTIJC9
DB2 Version 10 for z/OS conversion mode from DB2 Version 9 for z/OS DB2 Version 10 for z/OS new-function mode AOCTIJ9X

Procedure

To migrate data objects when upgrading DB2 for z/OS:

  1. Upload to your subsystem the JCL file that corresponds to the upgrade of your DB2 for z/OS subsystem. The JCL files are in the directory installation_directory_for_the_IBM_Data_Studio_client\QueryTunerServerConfig\all_features\ZOS\migration. Upload the file as an ASCII file.
  2. Follow the instructions in the Notes® section of the comments to customize the JCL for your environment, and then submit the job. For example, here are the instructions from the file AOCTIJ9X.
    //*  Notes =
    //*    PRIOR TO RUNNING THIS JOB, customize it for your system:
    //*    (1) Add a valid job card
    //*    (2) Locate and change all occurrences of the following strings
    //*        as indicated:
    //*        (A) '!DSN!'      to the subsystem name of your DB2
    //*        (B) 'DSNTIA!!'   to the plan name for DSNTIAD on your DB2
    //*        (C) 'DSN!!0'     to the prefix of the target library for DB2
    //*        (D) '!AOCDBRM!' to the prefix of target library for QT
    //*                          DBRMs
    //*        (E) 'USER!!'     user id for individual explain tables
    //*        (F) '!GRANTEE!   to one or more authorization IDs that
    //*                          need to use stored procedures
    //*                           SYSPROC.OPT_RUNSQL and
    //*                           SYSPROC.OPT_EXECUTE_TASK
    //*        (G) '!USERID!'    to the USER ID which will have execute
    //*                           authority on packages
    //*        (H) 'PKGOWNER!'   to the owner of the QT packages
    //*        (I) '!SQLID!'     CURRENT SQLID which is set before execute
    //*                           DDLs
    //*        (J) '!WLMENV4!'   WLM environment name for SYSPROC.OPT_RUNSQL
    //*        (K) '!WLMENVJU!'  WLM environment name for
    //*                           SYSPROC.OPT_EXECUTE_TASK
    //*                           and want to capture SQL from cache.
    Attention: Step AOCSP is required only if you created the OPT_RUNSQL and OPT_EXECUTE_TASK stored procedures in the configuration that you are migrating. Creating these stored procedures when configuring a subsystem for tuning is optional.

Feedback