Migrating from IBM Db2 AI for z/OS 1.6.0 maintenance level 1 to IBM Db2 AI for z/OS 1.6.0 maintenance level 2

You can migrate your installation of IBM Db2 AI for z/OS 1.6.0 plus APARs PH56674 and PH57810 (maintenance level 1) to IBM Db2 AI for z/OS 1.6.0 plus APARs PH59095, PH59096, and PH60511 (maintenance level 2).

Before you begin

Important: If you have not already done so, you must apply the required Db2 APARs for your target Db2 connections prior to migrating to IBM Db2 AI for z/OS 1.6.0 maintenance level 2. The required and recommended Db2 APARs to apply are:

Db2 12 (either 5650-DB2 or 5770-AF3), function level V12R1M500 activated with the following maintenance:: Required: APARs PH43916, PH46962, PH52152, PH54410, and PH56078; Recommended: APARs PH52441, PH56228, PH56328, PH56410, PH57723, PH57841, and PH57971
Db2 13 (either 5698-DB2 or 5698-DBV), function level V13R1M100 or later activated with the following maintenance:: Required: APARs PH46962, PH52152, PH54410, and PH56389; Recommended: APARs PH52441, PH56228, PH56328, PH56410, PH57723, PH57841, and PH57971

Note: It is best practice to migrate to the latest available Db2ZAI APAR level.

Procedure

To migrate from IBM Db2 AI for z/OS 1.6.0 maintenance level 1 to IBM Db2 AI for z/OS 1.6.0 maintenance level 2:

Db2ZAI 1.6.0 requires that IBM® z/OS maintenance be applied where Db2ZAI tasks run. See Hardware and software requirements for the Db2ZAI installation for a list of the z/OS PTFs to be applied.
Stop ML and stop Db2ZAI:
- Use the Db2ZAI user interface to stop ML on all target Db2 systems.
- Stop the Db2ZAI server processes (run $DB2ZAI_HOME/scripts/db2zai_services_stop, or stop using JCL). See Stopping the Liberty and Node.js servers with JCL or Stopping the Liberty and Node.js servers with USS.
If you are using the started task procs to start the Db2ZAI servers, you will need to replace the current started task procs with the updated version, found in SCOYSAMP.
Upgrade Db2ZAI:
1. (Optional) Back up the $DB2ZAI_HOME directory or the entire DB2ZAI_HOME zFS, as well as the Db2ZAI metadata database. See Backing up IBM Db2 AI for z/OS.
2. Run the update.sh script in $DB2ZAI_INSTALLATION/configuration/scripts to update the Db2ZAI configuration to the new version (config.json + script directory):
```
./update.sh migrate
```
Upgrade the target Db2 catalog objects to the new version. Repeat these steps for each target Db2:
Note: Apply the Db2 SMP/E PTF(s) listed in the Hardware and software requirements topic to the target Db2 subsystems to support this Db2ZAI maintenance. See Hardware and software requirements for the Db2ZAI installation.
1. (Optional) Back up the existing target database. See Backing up IBM Db2 AI for z/OS.
2. Complete the customization of any new JCL include variables for batch jobs:
  - Customize hlq.SCOYSAMP(COYIVPC). COYIVPC is included in multiple hlq.SCOYSAMP(COYV*) jobs:
3. Customize and run the batch jobs provided in hlq.SCOYSAMP.
  1. COYV061A – create new indexes.
  2. COYV061B – update stored procedures.
    Note: The JCL job COYV061B is required for APAR PH57810. If you ran this job previously, you don't need to run it again.
  3. COYV062A – update stored procedures.
Re-run the grant jobs for the various Db2ZAI users, including the Db2ZAI metadata administrator, the Db2ZAI target catalog administrator, the Db2ZAI target scheduler ID, and the Db2ZAI end users.
Start the server processes at the new release level using the JCL PROC or from the USS script. See Starting the Liberty and Node.js servers with JCL or Starting the Liberty and Node.js servers with USS.

Note: Make sure to update the current JCL PROC with the latest version or use a USS script to start the server processes.
Restart ML on all target Db2 systems using the Db2ZAI user interface.