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

When you migrate to a new release of Db2® Admin Tool from a previous release, you must customize the configuration by using Tools Customizer (TCz).

Complete the steps in the following table to migrate to Db2 Admin Tool 13.1 from a previous release.

Tips:

For multiple-LPAR environments, determine your customization strategy first: Using Tools Customizer in a multiple-LPAR environment.
For guidance on any input fields in TCz, position your cursor on the input field and press F1 (Help).

Table 1. Steps for migrating to Db2 Admin Tool 13.1 from a previous release
Step	Procedure	Links to more information
Start Tools Customizer.	On the ISPF Command shell panel, issue the following command: `EX 'hlq.TCZ110.SCCQEXEC(CCQTCZ)'`	Starting Tools Customizer (IBM Tools Customizer for z/OS 1.1)
Specify the Db2 Admin Tool Metadata Library.	On the IBM Tools Customizer for z/OS (CCQPHME) panel, specify option `1` (Customize a product). On the Specify the Product or Pack Metadata Library (CCQPHLQ) panel, specify the Db2 Admin Tool metadata library in the Product or pack metadata library field, such as `DMTOOL.ADBD1PTF.SADBDENU`. The default name of the product metadata library is `high_level_qualifier`.SADBDENU, where `high_level_qualifier` is all of the segments of the data set name except the lowest-level qualifier.	Specifying the metadata library for the product or pack to customize (IBM Tools Customizer for z/OS 1.1)
Run the Discover EXEC.	On the Customizer Workplace (CCQPWRK) panel, issue the DISCOVER command, and press Enter. On the Discover Customized Product Information (CCQPDSC) panel, specify values for the following required input fields: Source Customized table library (`DMTOOL.ADBC1PTF.SADBTLIB`) Target Customized table library (`DMTOOL.ADBD1PTF.SADBTLIB`) Issue the RUN command. Upon completion, the DISCOVER process populates all Tools Customizer input fields from the previous customization to the current customization. Specifically, the DISCOVER process automatically copies the settings from the customization table ADBTPARM and populates the input fields on the Product Parameters (CCQPPRD) panel and the DB2 Parameters (CCQPDB2) panel. If you use Launchpad, the DISCOVER process also ensures that the Launchpad table ADBDMT is discovered and copied from the specified site-specific source data set to the target data set. If DISCOVER is not used during an Db2 Admin Tool upgrade, the Launchpad panel (if used) might be missing Launchpad product settings that were established before the upgrade.	Discovering Db2 Admin Tool information automatically
Define product parameters.	On the Customizer Workplace (CCQPWRK) panel, specify the E line command against the Product parameters field. Confirm that the DISCOVER process populated the input fields accordingly. Verify the following input fields to ensure that the current libraries for Db2 Admin Tool and Object Comparison Tool are specified: Admin Tool/OC CLIST Admin Tool DBRM Admin Tool/OC EXEC Admin Tool/OC Load Admin Tool/OC Message Admin Tool/OC Panel Admin Tool/OC Skeleton Admin Tool/OC Table Customized Table lib Admin Tool hlq Admin Tool PROCLIB	Defining Db2 Admin Tool parameters
Define LPAR parameters.	On the CCQPWRK panel, specify the E line command against the LPAR parameters field. Confirm that the DISCOVER process populated the input fields accordingly.	Defining LPAR parameters
Edit the new Db2 entry.	On the Customizer Workplace (CCQPWRK) panel, specify the E line command against the site-specific SSID to display the Db2 parameters. On the DB2 Parameters (CCQPDB2) panel, confirm that the DISCOVER process populated the input fields accordingly. Tip: To use Db2 13 functionality, ensure that the APPLCOMPAT field is set to V13R1M500 or higher. For details, see Db2 13 function level support	Defining Db2 parameters
Generate the jobs.	On the Customizer Workplace (CCQPWRK) panel, issue the G line command against a site-specific SSID, and press Enter.	Generating customization jobs (IBM Tools Customizer for z/OS 1.1)
Submit the jobs.	On the Finish Product Customization (CCQPCST) panel, submit the generated jobs in the order that they are displayed. For example, the following three generated jobs are all that need to be submitted to install or migrate Db2 Admin Tool for subsystem DSNC: ... Member SSID ... Template ... Description ... -------- ---- ... -------- ... ----------------- ... ... A0CUSTAA DSNC ... ADBCUST ... General customization ... A2SETUAA DSNC ... ADBSETUP ... Admin Tool Setup Task ... A5BINDAA DSNC ... ADBBIND ... Binds ------------------------End of customized jobs------ ... If the Product Parameters option Change Management database is set to YES, the following jobs are generated and must be submitted in the order they are displayed: ... Member SSID ... Template ... Description ... -------- ---- ... -------- ... ------------------------- ... ... A0CUSTAA DSNC ... ADBCUST ... General customization ... A2SETUAA DSNC ... ADBSETUP ... Admin Tool Setup Task ... A3CMBAT -- ... ADBCMBAT ... Create CM Batch JCL procedure ... A4CMBSAA DSNC ... ADBCMBSS ... Create CM Batch items ... A5BINDAA DSNC ... ADBBIND ... Binds ... B0CMBIAA DSNC ... ADBCMBIV ... Verify CM Batch JCL procedure ---------------------------End of customized jobs----------- ...	Submitting the customization jobs
Propagate the customizations to additional LPARs as needed.	If you have a multiple-LPAR environment, use one of the specified methods to propagate your customization to other LPARs.	Using Tools Customizer in a multiple-LPAR environment