Query Tuner packages are missing

Follow these steps when an error message requires you to bind missing Query Tuner packages.

To follow these steps, you must be using InfoSphere® Optim™ Query Workload Tuner for DB2® for z/OS®, Version 4.1.

To bind missing packages by using the IBM® Data Studio client:
  1. In the Data Source Explorer, expand the connection to the subsystem.
  2. Right-click the subsystem and select Analyze and Tune > Configure for Tuning > Advanced Configuration and Privilege Management.
  3. In the Query Tuner section, click Bind.

To bind missing packages by running a JCL job:

  1. Find out which packages are missing.
    1. In the Data Source Explorer, expand the connection to the subsystem.
    2. Right-click the subsystem and select Analyze and Tune > Configure for Tuning > Advanced Configuration and Privilege Management.
    3. Click Detailed Report.
  2. Locate the JCL job file for the version of DB2 for z/OS that you are running.

    The JCL files are located in 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.
    Table 1. JCL and DBRMs for Version 9.1, Version 10 conversion mode from Version 8, Version 10 conversion mode from Version 9.1, and Version 10 new function mode of DB2 for z/OS
    Name of subfolder V9 V10CM8 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:
    AOCDDLX8

    DBRMs:
    AOC5OADM
    AOC5OAPC
    AOC5OEPL
    AOC5OEXJ
    AOC5OFMM
    AOC5OIA1
    AOC5OIA2
    AOC5OIA3
    AOC5OIA4
    AOC5OIA5
    AOC5OIA7
    AOC5OIA8
    AOC5OIAA
    AOC5OIAK
    AOC5OIAL
    AOC5ONPT
    AOC5OPKG
    AOC5OQA
    AOC5OQIA
    AOC5OSA
    AOC5OWCC
    AOC5OWCJ
    AOC5OWSA
    AOC5OWSJ
    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
  3. Upload the JCL job file and the DBRMS that correspond to the missing packages to the subsystem from the client. Upload the job file in ASCII format and the DBRMS in binary format.
  4. On the subsystem, modify the corresponding AOCDDL JCL job file to conform to your environment, then submit the job.

Feedback