Migrating a Db2 for z/OS subsystem to Db2 13 at function level 100
The migration process for Db2 13 has a single phase. However, many new capabilities and enhancements in Db2 13 remain unavailable until you issue an ACTIVATE command to activate function level 500 or higher.
Before you begin
- Read all information in Preparing your system to install or migrate to Db2 13.
- Follow the documented migration procedures carefully.Attention: Failure to follow documented migration procedures can cause unpredictable results after migration.
- Activate the last Db2 12 function level, function level 510, as described in Activate function level 510 in Db2 12.
-
Apply the fallback SPE (APAR PH37108) and stop and restart Db2 12 after the fallback SPE is applied, for every Db2 subsystem or data sharing member that you plan to migrate to Db2 13.
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. - Ensure that Db2 12 is at the appropriate service level. See Required maintenance for Db2 13 installation or migration.
- 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.
- When migrating a data sharing group to Db2 13, complete the migration steps for the first member to Db2 13 at function level 100 before starting any other members on Db2 13. For more information, see Migrating an existing data sharing group to Db2 13.
About this task
When you start Db2, the code level of the starting Db2 is compared to the code level that is required by the current Db2 catalog. If the starting Db2 has a code-level mismatch with the catalog, Db2 does not start and a message is issued.
No structural changes are applied to Db2 catalog objects with the catalog updates in this task. The first updates to Db2 catalog objects for Db2 13 occur later, when you update the catalog for function level V13R1M501 or higher.
Refer to the Db2 Program Directory for keyword specifications that are used for Preventive Service Planning (PSP) and for information about the service levels of any coupling facilities. You can use the z/OS® DISPLAY CF command to display the service level of coupling facilities. Check Information/Access or the ServiceLink facility of IBMLink for PSP information before you migrate. Or, to help you identify required service, you can instead use enhanced HOLDDATA and fix categories (FIXCATs), which provide a simplified, automated method of identifying and applying missing PTFs that are required for installation or migration. Also, check monthly for current information about Db2.
Procedure
To migrate a Db2 for z/OS subsystem to Db2 13, complete the following steps:
- Generate tailored JCL jobs for migrating to Db2 13. You can use the DSNTIJBC batch job or the Db2 installation CLIST. Tip:To generate the required JCL jobs and input files with a background process, complete the following steps: 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.
- Customize the DSNTIDOM parameter override file by following the instructions in the file.
- Customize the DSNTIJBC job. For example, if prefix.SDSNSAMP(DSNTIDOM) is the customized parameter override file, you can specify the following values in the IPSTART command in DSNTIJBC.
ISPSTART CMD(%DSNTINSB + OVERPARM(prefix.SDSNSAMP(DSNTIDOM)) + ) BREDIMAX(1) - 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. For more information, see Generating tailored installation, migration, or function level activation jobs by running the Db2 installation CLIST in interactive mode. - Complete the migration tasks that are listed in the following table. Tip: Tasks that are marked
optional
in the following table are not strictly required for a successful migration to Db2 13. However, they are generally recommended as best practices, and some of them might be required in your Db2 environment.When you complete the tasks in the preceding table, Db2 13 is available for use at function level 100.
What to do next
- When you no longer require the option to fall back to Db2 12, and you are ready to use new capabilities in Db2 13, you can activate function level 500 or higher. For more information, see Activating Db2 13 function level 500 or higher. For more information about the new-function capabilities in all available function levels, see Db2 13 function levels.Important: Do not issue the ACTIVATE command or run job DSNTIJAF for activation of Db2 13 until you are certain that the subsystem or data sharing group can proceed on Db2 13, without the possibility of falling back to or coexistence with Db2 12. In data sharing, the ACTIVATE command has group scope. Fallback and coexistence become impossible with the successful activation of function level 500 or higher.
- Install, configure, and verify Db2-supplied routines that depend on Db2 13 function levels, as described in Installing and configuring Db2-supplied routines that use new function: DSNTIJRT.
- Verify the successful migration to Db2 13, as described in Verifying successful migration to Db2 13.