Checklist for Db2 Admin Tool installation and migration

The following checklist describes each significant step in the installation or migration of Db2® Admin Tool. Use this checklist to guide you through the entire process of setting up this tool.

Table 1. Installation and migration checklist

A checklist that lists and describes the steps that are required to install or migrate Db2 Admin Tool.

Task Link to detailed instructions
1. Verify hardware requirements
Ensure that you deploy Db2 Admin Tool on a z-series processor that is capable of running the requisite release of z/OS® for the Db2 subsystems that you will be using with Db2 Admin Tool None
2. Verify software requirements
Verify that your environment meets the minimum software requirements. Software requirements for Db2 Admin Tool 13.1
3. Perform the SMP/E installation
a. Install Db2 Admin Tool 13.1 by using System Modification Program Extended (SMP/E) or verify that it has been installed. SMP/E installation instructions are in the Db2 Admin Tool program directory.

Note that Db2 Admin Tool 13.1 requires the installation of two components: Db2 Administration Tool (FMID H0IHD10), which contains the base code, and Db2 Administration Tool Enhanced Function (FMID J0IHD10), which contains the ADBMAIN program that allows you to use the ISPF panels.

Program Directory for Db2 Admin Tool V13.1 (GI13-5526)
b. Verify that TCz is installed. SMP/E installation instructions are in the TCz program directory. Program Directory for IBM Tools Customizer for z/OS 1.1 (GI13-4653)
4. Optional: APF authorize SADBLINK
Several programs and TSO commands must be APF authorized to use them within Db2 Admin Tool. Therefore, ensure that the SADBLINK data set is APF authorized.

Alternatively, you can later copy the appropriate programs to an APF-authorized library (as described under Required in some cases: Update the APF Authorization table later in this table).

None
5. Gather data set names and subsystem names
a. Review the data sets that you will need during the customization process with TCz. Data sets used by Tools Customizer

b. Record the names of all Db2 subsystems on which you want to run Db2 Admin Tool.

None
6. Customize products that will be launched from Db2 Admin Tool
If you plan to enable any of the following products to be launched from Db2 Admin Tool, customize these products with TCz before you customize Db2 Admin Tool:
  • IBM® Db2 Object Comparison Tool for z/OS
  • Db2 Cloning Tool
  • Db2 High Performance Unload
  • Db2 Table Editor
  • Db2 SQL Performance Analyzer

Customizing Db2 Object Comparison Tool (IBM Db2 Object Comparison Tool for z/OS 13.1.0)

Customizing Db2 Cloning Tool (IBM Db2 Cloning Tool for z/OS 3.2.0)

Db2 HPU customization (IBM Db2 High Performance Unload for z/OS 5.1.0)

Customizing Db2 Table Editor (IBM Db2 Table Editor 4.5)

Customizing SQL PA (DB2 SQL Performance Analyzer for z/OS 5.1.0)

7. Optional: Determine LPAR strategy
If you have a multiple-LPAR environment, determine your customization strategy with TCz. Using Tools Customizer in a multiple-LPAR environment
8. Customize Db2 Admin Tool

Complete the steps in the appropriate customization roadmap based on the type of customization that you are performing.

If you are recustomizing Db2 Admin Tool, because you migrated to a new Db2 version, mode, or function level, complete the steps for updating Db2 Admin Tool instead.

Roadmap: Customizing Db2 Admin Tool for the first time

Roadmap: Migrating to Db2 Admin Tool 13.1 from a previous release

Roadmap: Recustomizing Db2 Admin Tool

Updating Db2 Admin Tool after migrating to a new Db2 version, mode, or function level or running CATMAINT

9. Required in some cases: Update the APF Authorization table
Complete this step if the SADBLINK library is not APF authorized or you plan to use HPU. In these cases, copy the ADB2ATH and ADB2UTIL programs and optionally INZUTILB (for Db2 High Performance Unload ) to an APF-authorized library. Updating the APF authorization table
10. Optional: Verify activation of limited functionality
Verify that Db2 Admin Tool is operational. Verifying activation of limited functionality
11. Optional: Complete other configuration tasks

Complete any of the following additional setup tasks as needed depending on the functionality that you want to use:

Optional: Specify naming conventions

If you want Db2 Admin Tool to use your local naming conventions for items such as data sets, utility IDs (UIDs), and plan names, update member SADBSLIB(ADB2UCUS).

Specifying naming conventions
Optional: Tailor the Db2 Tools Launchpad

The Db2 Tools Launchpad enables you to launch all installed IBM Db2 tools that have an ISPF interface directly from a centralized panel.

Creating the Launchpad table
Optional: Grant SELECT access on catalog tables

If you plan to make Db2 Admin Tool available to a large number of users, considering running a TCz job to authorize specific IDs to see the catalog.

Granting SELECT access on catalog tables
Optional: Optimize ADMIN_INFO_SYSPARM and DSNZPARM settings

To optimize performance, verify that the ADMIN_INFO_SYSPARM stored procedure is operational and that the DSNZPARM STORTIME(DSN6SYSP) parameter is set to a reasonable time.

Optimizing ADMIN_INFO_SYSPARM and DSNZPARM settings for GEN and DDL
Optional: Run the RUNSTATS utility

Run the RUNSTATS utility on the Db2 catalog. This action is recommended to optimize performance.

None
Optional: Define stored procedures and REST APIs

If you want to apply certain Db2 Admin Tool functions, such as reverse engineering, to additional software products, define one or more of the provided stored procedures.

If you want to call Db2 Admin Tool functions by using the provided REST APIs, run the sample jobs to bind the provided stored procedures as REST services.

Defining the provided stored procedures
Setting up the provided REST APIs

Optional: Enable Db2 Admin Tool distributed support

To use Db2 Admin Tool on remote Db2 systems, fully enable distributed support.

Enabling distributed support
Optional: Improve performance when making Db2 Admin Tool available to users

To reduce Db2 Admin Tool start-up time, use one of the specified methods for improving performance.

Improving performance when making Db2 Admin Tool available to users
Optional: Set global variables

To set Db2 Admin Tool variables site-wide for all users, use the provided sample invocation exit.

Setting global variables for Db2 Admin Tool
Optional: Enable product discovery

This step is strongly recommended if Db2 Administration Foundation is also installed.

Enabling product discovery for Db2 Admin Tool
Optional: Tailor Db2 Admin Tool Authorization Switching

Authorization switching is deprecated in Db2 Admin Tool. If you still want to use this functionality, complete the setup by following the instructions.

Tailoring Authorization Switching