Db2 Admin Tool support for migrating to Db2 13

1. Upgrade to Db2 Admin Tool 13.1.

   Version 13.1 is the minimum level that supports Db2 13. Version 13.1 also supports Db2 12.

2. Apply the fixes for APARs PH46240 and PH46162 .

   These APARs provide additional Db2 Admin Tool 13.1 functionality to support Db2 13.

3. Apply any additional Db2 Admin Tool fixes for Db2 13 function levels 502 and higher, as needed.

   For a list of required PTFs for each function level, see Db2 13 function level support.

4. Apply the fix for APAR PH42701 to IBM® Tools Customizer for z/OS (TCz).

   This APAR provides support for Db2 13. For more information, see https://www.ibm.com/support/pages/apar/PH42701.

5. Run TCz for Db2 Admin Tool.

   Complete the steps in Updating Db2 Admin Tool after migrating to a new Db2 version, mode, or function level. These steps guide you through the process of regenerating and running the jobs that are required to rebind the necessary ADB plans and packages. If your Db2 library names are version dependent, you must specify the new Db2 13 library names.

Can I run Db2 Admin Tool 12.1 with Db2 13 FL 100?

No. Db2 13 is not supported by Db2 Admin Tool 12.1.

Can I run Db2 Admin Tool 13.1 with Db2 12 FL 100?

No. Db2 Admin Tool 13.1 supports Db2 12 FL500 and later.

What is the difference between a tolerated function level and a supported function level?

A tolerated function level means that you can run Db2 Admin Tool, but not all enhancements in that function level are guaranteed to be supported. A supported function level means that you can use the enhancements in that function level with Db2 Admin Tool.

For more information about the maintenance that is required for Db2 Admin Tool to support each function level, see Db2 13 function level support.

What APPLCOMPAT value should I specify for Db2 Admin Tool packages?

When you rebind Db2 Admin Tool packages, generally you should specify the APPLCOMPAT value for the function level that you want to use.

More specifically, the APPLCOMPAT value that you specify must be less than or equal to the currently activated Db2 function level for your Db2 subsystem or data sharing group:

• The safest value to specify for the APPLCOMPAT bind option is the highest function level that is currently supported by Db2 Admin Tool. This value prevents users from exploiting features until they are fully supported by Db2 Admin Tool.
• If you rebind at a function level that is higher than the highest supported function level, you can manually run your DDL through ISPF panels or execute a work statement list (WSL) that exploits features at that function level. For more information about running SQL manually, see Running SQL statements from screen input.
• If you rebind at a function level that is lower than that highest supported function level (to restriction enhancements), you must set the target function level (tgt_db2fl) to the same (or lower) function level that you specified for the Db2 Admin Tool packages. Otherwise, Db2 Admin Tool might generate DDL that subsequently cannot be run. For more information about setting the target function level, see Db2 function level settings in Db2 Admin Tool.
• When the version of Db2 Admin Tool is 13.1 and the version of Db2 is 12, the lowest APPCOMPAT value that you can specify is V10R1.

Do I need to run TCz for Db2 Admin Tool when I activate a new Db2 13 function level?

Yes. Complete the steps that are described in Updating Db2 Admin Tool after migrating to a new Db2 version, mode, or function level. You must take these actions in TCz to account for any Db2 catalog changes and to be able to use the enhancements in that function level.

Can I use Db2 Object Comparison Tool 12.1 with Db2 Admin Tool 13.1?

No. Db2 Object Comparison Tool 13.1 is the minimum level that you can use with Db2 Admin Tool 13.1.

Db2 Object Comparison Tool 13.1 is no longer separately orderable. How do I get Db2 Object Comparison Tool functionality for Db2 Admin Tool 13.1?

You must order one of the following solution packs:

• IBM Db2 Change Management Solution Pack for z/OS 1.2 (5655-CH1)
• IBM Db2 Administration Solution Pack for z/OS 3.3 (5697-ASP)

Both of these solution packs include Db2 Object Comparison Tool 13.1.

Why does Db2 Admin Tool 13.1 have two FMIDs?

Version 13.1 requires the installation of two components (FMIDs):

• Db2 Administration Tool (FMID H0IHD10), which contains the base code
• Db2 Administration Tool Enhanced function (FMID J0IHD10), which contains the ADBMAIN program that allows you to use the ISPF panels

Before migrating Db2 Admin Tool from version 12.1 to version 13.1, does version 12.1 need to be at the latest maintenance level?

No. You can migrate to version 13.1 from any maintenance level of version 12.1.

Converting non-universal table spaces to the universal table space (UTS) type by using Db2 Admin Tool

Converting to UTS can help you take advantage of the growing list of Db2 12 and Db2 13 features that operate only on UTS. You can use Db2 Admin Tool to help you convert partitioned table spaces to PBR UTS. See Convert a group of partitioned table spaces to PBR UTS.

You can also use Db2 Admin Tool to move tables from deprecated multi-table table spaces to UTS. See Moving tables from multi-table table spaces to UTS.

When you develop a Db2 migration plan, you likely set target dates for using the new functionality that is introduced in the release. Db2 Admin Tool can potentially help you move that date forward. Because Db2 Admin Tool supports Db2 13 enhancements, it can help you quickly adopt new features such as Db2 utility history and online conversion of PBG table spaces to PBR table spaces.

Db2 Admin Tool supports features that are available in the base release and features that are available in function levels. For the latest information about the Db2 13 features that Db2 Admin Tool supports, see What's new in Db2 Admin Tool 13.1.

If you have additional questions or need more help when migrating to Db2 13, please contact IBM Software Support. IBM is ready to help you successfully migrate to Db2 13 and use Db2 Admin Tool to more easily manage your data.