Start of change

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-function capabilities that depend on Db2 catalog changes in Db2 13 remain unavailable until you activate function level 501 or higher.

Before you begin

Before you activate function level 500 or higher in Db2 13, you must complete the following tasks:

  1. In Db2 12, identify and resolve incompatible changes and activate function level 510 (V12R1M510). You can run the DSNTIJPE premigration queries job in Db2 12 to identify the incompatible changes. For more information, see Activate function level 510 in Db2 12.
  2. Verify that every member was restarted with the fallback SPE applied in Db2 12.
    Important: Inactive members that never started in Db2 12 with the fallback SPE (APAR PH37108) applied cannot start after the first data sharing member is migrated to Db2 13 at function level 100.
  3. If your Db2 environment contains PBR RPN table spaces, APAR PH61633 is an important PE fix that you must apply on all data sharing members before migrating to or activating function levels in Db2 13.
    Attention: If your Db2 environment contains PBR RPN table spaces, do not migrate any data sharing members to function level V13R1M100, or activate function level V13R1M500 or higher, until you apply the PTF for PH61633 on all data sharing members and complete all ++HOLD actions. For more information, see the 21 June 2024 Red Alert.
  4. Migrate the Db2 subsystem or data sharing group to Db2 13, as described in Migrating a Db2 for z/OS subsystem to Db2 13 at function level 100 or Migrating an existing data sharing group to Db2 13.
  5. Verify that you no longer need to fall back to Db2 12.
    Important: After function level 500 is activated in Db2 13, coexistence and fallback to Db2 12 are no longer possible. You can activate function level 100* to disable new capabilities in Db2 13, but function level 100* does not support coexistence or fallback .
  6. In data sharing, ensure that the group has no active Db2 12 members. See Migrating subsequent members of a group to Db2 13.

About this task

Continuous delivery in Db2 13

The availability of most new-function application capabilities in Db2 13 depends on the type of enhancement, the activated function level, and the application compatibility levels of each application. For a list of all available function levels that are currently available in Db2 13, see Db2 13 function levels.

Many new-function enhancements take effect at any function level when you apply a PTF in each Db2 subsystem or data sharing member. For more information, see New-function APARs for Db2 13.

The following table describes the main function levels that are used in the Db2 13 migration process.

Function level Description
FL 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.
FL 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.
FL 500 1 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 500.
Tip: Start of change
  1. After you activate function level 500, you can use a single procedure to activate any higher function level that is available based on the code level of your Db2 environment. Activating a function level also implies activation of all lower function levels. For a list of all available function levels and specific activation procedures for each one, see Db2 13 function levels.
End of change

Procedure

To activate new-function capabilities 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.
  • 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: Start of change 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.End of change
      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 the 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 ISPSTART 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. Identify the target function level that you want to activate. For more information about the new-function capabilities in the available function levels, see Db2 13 function levels. Depending on the code level of your Db2 environment, you might need to apply additional maintenance before you can activate some higher function levels. You can use the -DISPLAY GROUP command to check the code level and highest possible function level in your Db2 13 environment.
    5. 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.

        For information about the changes to the catalog, see Catalog changes in Db2 13.

      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.
    6. 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.
    7. Run the tailored DSNTIJAF job, or issue the following ACTIVATE command:
      -ACTIVATE FUNCTION LEVEL (V13R1M5nn)

    8. If you are ready for applications to use new SQL capabilities in this function level, rebind the applications at the equivalent application compatibility level for higher. For more information, see the following topics:

      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.

What to do next

Complete any of the following actions:

  • If the new function level includes optimization enhancements, Db2 must process a full prepare before any SQL statements can benefit. Whether a full prepare occurs depends 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.
  • If you did not run the jobs to update the APPLCOMPAT and SQLLEVEL subsystem parameters, resolve any application incompatibilities and increase the application compatibility level of your applications after you are satisfied that Db2 is stable at the target function level, as described in Controlling the Db2 application compatibility level.
  • If you encounter regressions or other problems when you activate a Db2 13 function level, minimize the impact to your applications while you resolve the problems by following the general approaches described in Activating lower (*) function levels in Db2 13.
  • You might need to update COPY, RECOVER, and REBUILD INDEX utility jobs to add new or remove obsolete Db2 catalog objects. When a utility encounters the following situations for Db2 catalog objects, it issues message DSNU1530I:
    • The object is no longer used or no longer exists.
    • The object is created in a higher catalog level or function level.

    For best results, make these updates the utility jobs after you activate the function level that the changes support. For more information about the catalog changes in Db2 13, see Catalog changes in Db2 13.

End of change