System and SQL Performance products and solutions when you migrate to a new Db2 version

Use this procedure to maintain the System and SQL Performance products when you migrate to a new version of IBM Db2.

Before you begin

• To maintain the product when you create a new Db2 catalog for a new version of Db2, use Deployment Ready JCL to perform a new product installation. Then you will be operating in exploitation mode.
• Perform this procedure only after you migrate to the new version of Db2 in compatibility mode or NFM mode.

To migrate between versions of Db2

1. Before you migrate to a new version of Db2, stop the DOM agent by issuing the following console command:

    /dbcssid DOM,STOP

   The dbcssid value represents the DBC subsystem ID.

2. Migrate to the new version of Db2.
3. Set up the Common Explain component:

   1. If the names of your DB2 libraries have changed, update the following members to reflect the new names:

      Member	Description	Location
      PSS2ssid	Control members that contain the plan name and Db2 libraries	HLQ.UBMCSAMP
      ACTPSS	Contains the Catalog Managerinterface to SQL Explorer	HLQ.UBMCCLIB
      SQLX edit macro	Contains the plan name and library names for Explaining a single SQL statement from a program	SYSPROC concatenation

   2. Based on the version of Db2 to which you are migrating, complete the appropriate steps to bind packages and plans:

      If you are migrating to this version	Do this
      DB2 Version 10	If SYSIBM.SYSPACKSTMT was not converted to the new DB2 Version 10 format, rebind 1 all packages by using DAAssidP (bind packages), and bind the plan by running DAAssidB (bind plan) in UBMCSAMP. After SYSIBM.SYSPACKSTMT has been converted, run DAAUP9#A. Then, rebind 1 the plan by running DAAssidB (bind plan) in UBMCSAMP. Convert the user plan tables to Unicode by using sample jobs provided by IBM. These jobs include DSNTIJPM, DSNTIJXA, DSNTIJXB, and DSNTIJXC.
      DB2 Versions 11 or 12	Rebind 1 all packages by using DAAssidP (bind packages), and bind 1 the plan by running DAAssidB (bind plan) in UBMCSAMP.

      ^{1 If Automatic Rebind is set to YES or COEXIST, you do not need to perform the rebind.}

   3. Install the ADMIN_EXPLAIN_MAINT stored procedure as follows: 
       

      For Db2 Version 11 or later, use the following procedure to install the ADMIN_EXPLAIN_MAINT stored procedure:

      1. Create a JCL startup procedure for the IBM z/OS Workload Manager (WLM) environment, if you do not already have one.
      2. Set up the IBM stored procedure using the DSNTESR member from the Db2 DSNSAMP data set. Perform the following steps:
         1. Create the following global temporary tables:
            • SYSIBM.EXPLAIN_MAINT_SUMMARY
            • SYSIBM.EXPLAIN_MAINT_SQL
            • SYSIBM.EXPLAIN_MAINT_TB_NOT_UPGRADED
         2. Define the SYSPROC.ADMIN_EXPLAIN_MAINT stored procedure by specifying your WLM environment and the COLLID for the DSN% packages.
         3. Issue a GRANT ALL to PUBLIC authority to the global temporary tables.
         4. Issue a GRANT EXECUTE to PUBLIC authority to the stored procedure.
         5. Remove the comments from the bind statement and run the bind for the DSNADMEM package, specify the DSNDBRM Db2 library, and perform the bind.
      3. Activate the WLM environment.
      4. Start the stored procedure.

      For more information, see the IBM Db2 for z/OS installation documentation.

4. Start the DOM agent by issuing the following console command:

    /dbcssid DOM,START

   Warning

   Important

   For Db2 Version 11 or later, Explains are not functional until you install the ADMIN_EXPLAIN_MAINT stored procedure, as described in the previous step.

You are operating in exploitation mode.