Running JCL to configure a DB2 for z/OS subsystem

You can create EXPLAIN tables, create Query Tuner tables, and activate the full set of tuning features by customizing and submitting JCL jobs.

Before you begin

Carry out steps 1 through 9 in Checklist for configuring DB2® for z/OS® for use with InfoSphere® Optim™ Query Workload Tuner.

About this task

If your subsystem was configured for InfoSphere Optim Query Workload Tuner, Version 3.1 or 3.1.1, then you do not need to follow the steps in this procedure.

Procedure

To create EXPLAIN tables, create Query Tuner tables, and activate the full set of tuning features:

  1. Upload the required JCL job files and DBRMs to the subsystem from the client system.
    The JCL files and DBRMs are located inside the installation directory for the IBM® Data Studio client.
    • If you installed the IBM Data Studio client on a Windows system, the JCL is in the installation_directory\QueryTunerServerConfig\all_features\ZOS\version_number_and_mode directory.
    • If you installed the IBM Data Studio client on a Linux system, the JCL is in the .installation_directory/QueryTunerServerConfig/all_features/ZOS/version_number_and_mode directory.

    Upload the JCL files in ASCII format and the DBRMs in binary format.

    Table 1. JCL and DBRMs for Version 9.1, Version 10 conversion mode from Version 9.1, and Version 10 new function mode of DB2 for z/OS
    Name of subfolder V9 V10CM9 V10
    List of files JCL:
    AOCDDL9

    DBRMs:
    AOC5OADM
    AOC5OAPC
    AOC5OEPK
    AOC5OEXK
    AOC5OFMJ
    AOC5OIA1
    AOC5OIA2
    AOC5OIA3
    AOC5OIA4
    AOC5OIA5
    AOC5OIA6
    AOC5OIA7
    AOC5OIA8
    AOC5OIA9
    AOC5OIAA
    AOC5OIAK
    AOC5OIAL
    AOC5ONPT
    AOC5OPKG
    AOC5OQA
    AOC5OQIA
    AOC5OSA
    AOC5OWCK
    AOC5OWQA
    AOC5OWSA
    AOC5OWSK
    JCL:
    AOCDDLX9

    DBRMs:
    AOC5OADM
    AOC5OAPC
    AOC5OEPK
    AOC5OEXK
    AOC5OFMM
    AOC5OIA1
    AOC5OIA2
    AOC5OIA3
    AOC5OIA4
    AOC5OIA5
    AOC5OIA6
    AOC5OIA7
    AOC5OIA8
    AOC5OIA9
    AOC5OIAA
    AOC5OIAK
    AOC5OIAL
    AOC5ONPT
    AOC5OPKG
    AOC5OQA
    AOC5OQIA
    AOC5OSA
    AOC5OWCK
    AOC5OWQA
    AOC5OWSA
    AOC5OWSK
    JCL:
    AOCDDL10

    DBRMs:
    AOC5OADM
    AOC5OAPC
    AOC5OEPK
    AOC5OEXM
    AOC5OFMM
    AOC5OIA1
    AOC5OIA2
    AOC5OIA3
    AOC5OIA4
    AOC5OIA5
    AOC5OIA6
    AOC5OIA7
    AOC5OIA8
    AOC5OIA9
    AOC5OIAA
    AOC5OIAK
    AOC5OIAL
    AOC5ONPT
    AOC5OPKG
    AOC5OQA
    AOC5OQIA
    AOC5OSA
    AOC5OWCM
    AOC5OWQA
    AOC5OWSA
    AOC5OWSM
  2. Create the tables for Version 4.1.
    1. Modify the corresponding AOCDDL JCL job file to conform to your environment. The following table lists the AOCDDL JCL job files for each environment.
      Version of DB2 for z/OS on the subsystem JCL job Version 4.1
      DB2 Version 10 for z/OS new-function mode AOCDDL10
      DB2 Version 10 for z/OS conversion mode from Version 9 AOCDDLX9
      DB2 Version 9 for z/OS AOCDDL9
    2. Optional: Uncomment the job step AOCGRT2 if you do not want to create RACF® groups for InfoSphere Optim Query Workload Tuner to use a secondary authorization IDs. The product can use the RACF IDs to explain tables and perform other tasks. If you uncomment this job step, you must supply authorization IDs to use in place of RACF IDs. These authorization IDs must be the same IDs with which users of the product will connect to the subsystem from the Data Studio client.

      Also, if you uncomment this job step, individual users in the Data Studio client must unselect an option in the Data Studio client before attempting to tune SQL that runs on the subsystem. After starting the Data Studio client, each users must select Window > Preferences. Then, expand Data Management and select Query Tuner. The preference to deselect is labelled Allow internal processes to use the RACF IDs DB2OE and DB2OSCA.

    3. Submit the job.
  3. If you did not comment the job step AOCGRT2 before running the AOCDDL job, create the following two RACF groups and link your users to them.
    • DB2OSCA
    • DB2OE
  4. Activate the full set of tuning features for InfoSphere Optim Query Workload Tuner on the subsystem.
    1. Ensure that the authorization ID that you are using to connect to the subsystem has one of the following authorities or privileges that are required for activating the full set of tuning features.
      • DB2 Version 9.1 for z/OS:
        • CREATEIN privilege on the schema DB2OE (if you created the DB2OE RACF group in step 3)
        • SYSADM or SYSCTRL authority
      • DB2 10 for z/OS and later:
        • CREATEIN privilege on the schema DB2OE (if you created the DB2OE RACF group in step 3)
        • SYSADM, SYSCTRL, or DBADM authority
    2. Upload the following file to the subsystem: qwt_license.jcl This file is in the QueryTunerServerConfig\all_features\ZOS\License\ folder in the installation directory for the IBM Data Studio client.
    3. Replace the variables $$DSN and $$USER with values for your system environment and submit the job.

What to do next

Return to Checklist for configuring DB2 for z/OS for use with InfoSphere Optim Query Workload Tuner and continue at step 12.

Feedback