Activating Db2 13 function level 500 or higher

When you migrate a Db2 environment to Db2 13, it starts at function level 100. However, many new capabilities in Db2 13 remain unavailable until you activate function level 500 or higher. Also, all new capabilities that depend on Db2 catalog changes in Db2 13 remain unavailable until you activate function level 501 or higher.

About this task

The availability of new function in Db2 13 depends on the type of enhancement, the activated function level, and the application compatibility levels of the applications. For a list of all available function levels in Db2 13, see Db2 13 function levels.

Function level 100

Db2 starts at function level 100 (V13R1M100) during migration to Db2 13, and fallback and coexistence with Db2 12 in data sharing remain possible. Many new capabilities in Db2 13 remain unavailable. For more information, see Function level 100 (for migrating to Db2 13 - May 2022).

Function level 500

Activating function level 500 (V13R1M500) prevents coexistence with and fallback to Db2 12. Function level 500 is also the first opportunity for applications to use many of the new capabilities in Db2 13. However, new capabilities that depend on Db2 13 catalog changes remain unavailable. For more information, see Function level 500 (for migrating to Db2 13 - May 2022).

Function level 501

Function level 501 (V13R1M501) is the first opportunity after migration to Db2 13 for applications to use new features and capabilities that depend on catalog changes in Db2 13. For more information, see Function level 501 (Db2 13 installation or migration - May 2022).

Some virtual storage and optimization enhancements take effect in function level 100. Optimization enhancements become available after full prepare of the SQL statements, depending on the statement type:

• For static SQL statements, after bind or rebind of the package.
• For non-stabilized dynamic SQL statements, immediately, unless the statement is in the dynamic statement cache.
• For stabilized dynamic SQL statements, after invalidation, free, or changed application compatibility level.

Tip: After you activate function level 500, you can activate any higher function level that is available. For a list of available function levels, see Db2 13 function levels.

To activate the initial new function in Db2 13, use one of the following approaches:

• If you are not ready to update the Db2 catalog for Db2 13, you can activate new capabilities that do not depend on catalog changes. To do so, activate and keep Db2 13 at function level 500 until you are ready for the catalog updates. See the "How to activate" section in Function level 500 (for migrating to Db2 13 - May 2022).
• If you are ready to update the Db2 catalog for Db2 13, you can activate function level 501 or higher. To do so, complete the following steps. (Change 5nn to the function level that you want to activate.)
  1. Generate tailored JCL jobs for the CATMAINT and function level activation steps. You can use the DSNTIJBC batch job or the Db2 installation CLIST.

     Tip: You can avoid working through the Db2 installation CLIST panels in interactive mode by running a batch job with valid input files to generate the required JCL jobs and input files with a background process. See Generating tailored Db2 migration or function level activation jobs in the background.

     To generate the required JCL jobs and input files with a background process, complete the following steps:

     1. Customize the DSNTIDOA parameter override file by following that instructions in the file.
     2. Customize the DSNTIJBC job. For example, if prefix.SDSNSAMP(DSNTIDOA) is the customized parameter override file, you can specify the following values in the IPSTART command in DSNTIJBC.

          ISPSTART CMD(%DSNTINSB + 
            OVERPARM(prefix.SDSNSAMP(DSNTIDOA)) + 
            ) BREDIMAX(1)

     3. If you use Db2 Value Unit Edition, you must also provide the data set name of the DSNTIDVU parameter override file in the IPSTART command in the DSNTIJBC job, as shown in the following example, where prefix.SDSNSAMP(DSNTIDVU) is the customized OTC LICENSE file.

          ISPSTART CMD(%DSNTINSB + 
            OVERPARM(<prefix>.SDSNSAMP(DSNTIDOA)) + 
            OTCLPARM(<prefix>.SDSNSAMP(DSNTIDVU)) + 
            ) BREDIMAX(1)

     4. Submit the customized DSNTIJBC job.
     To generate the required JCL jobs and input files with the Db2 installation CLIST in interactive mode, complete the following steps:
     1. In panel DSNTIPA1, specify INSTALL TYPE ===> ACTIVATE. Then, specify the name of the output member from the previous function level activation (or migration) in the INPUT MEMBER field, and specify a new member name in the OUTPUT MEMBER field.
     2. In panel DSNTIP00, specify the current function level and V13R1M5nn in the TARGET FUNCTION LEVEL Field. The Db2 installation CLIST uses this value when it tailors the ACTIVATE command in the DSNTIJAF job and the CATMAINT utility control statement in the DSNTIJTC job.
     3. Proceed through the remaining Db2 installation CLIST panels, and wait for the Db2 installation CLIST to tailor the jobs for the activation process. The output data set contains the tailored jobs for the activation process. For more information, see The Db2 installation CLIST panel session.
  2. Activate function level 500 by running the generated DSNTIJA0 job, or by issuing the following ACTIVATE command:

     -ACTIVATE FUNCTION LEVEL (V13R1M500)

  3. Ensure that no incompatible applications can interfere with the catalog update. For more information, see Identifying applications that are incompatible with catalog updates.
  4. Update the catalog and verify the changes for function level 501 or higher by completing the following steps.
     1. Run the tailored DSNTIJTC job, or run the CATMAINT utility with LEVEL V13R1M5nn to update the catalog to the appropriate catalog level. If multiple catalog updates are required, the CATMAINT job processes each update in sequential order. If a later update in the sequence fails, the previous successful updates do not roll back, and the catalog level remains at the highest level reached. If that occurs, you can correct the reason for the failure and resubmit the same CATMAINT job.
     2. If the CATMAINT utility jobs from the previous step placed any altered Db2 catalog objects in REORG-pending (AREO*) advisory status, run the REORG utility for those objects.
     3. Run the generated DSNTIJX2 job to run the CHECK INDEX utility for Db2 catalog and directory indexes for new objects that are created in Db2 13.
  5. Check that Db2 is ready for function level activation by issuing the following ACTIVATE command with the TEST option:

     -ACTIVATE FUNCTION LEVEL (V13R1M5nn) TEST

     Db2 issues message DSNU757I to indicate the results. For more information, see Testing Db2 function level activation.
  6. Run the tailored DSNTIJAF job, or issue the following ACTIVATE command:

     -ACTIVATE FUNCTION LEVEL (V13R1M5nn)

  7. If you are ready for applications to use new capabilities in this function level, rebind them at the corresponding application compatibility level. For more information, see Controlling the Db2 application compatibility level.
     Optionally, when you are ready for all applications to use the new capabilities of the target function level, you can run the following jobs:

     1. Run DSNTIJUZ to modify the subsystem parameter module with the APPLCOMPAT value that was specified on panel DSNTIP00.
     2. Run DSNTIJOZ job to issue SET SYSPARM command to bring the APPLCOMPAT subsystem parameter changes online.
     3. Run DSNTIJUA job to modify the Db2 data-only application defaults module with the SQLLEVEL value that was specified on panel DSNTIP00.