Task 3: Execute the DDL samples to address Db2 repository changes
This section describes the Db2 repository changes that you need to make.
Ensure the database is at the correct pre-upgrade level
The Code Pipeline database must be fully up-to-date to ensure that the version 22.01 upgrade DDLs run correctly. Depending on what level of PTFs your database matches, some of the DDLs (listed in this section) may have been applied as part of either the installation of version 18.02 or performing Code Pipeline maintenance HOLDDATA. If not applied, you must apply these Code Pipeline version 18.02 DDLs before running the version 22.01 DDLs.
These DDL members are located in the <hlq>.BPWMUDDL data set. If DDL180N is executed, a REORG is necessary. You can find the REORG job in the <hlq>.BPWMSAMP data set member ($WZDREOG).
If not applied previously, you must apply the DDLs in the following sequence:
- DDL180A
- DDL180B
- DDL180C
- DDL180D
- DDL180E
- DDL180F
- DDL180G
- DDL180H
- DDL180K
- DDL180L
- DDL180M
- DDL180N
- DDL180O
- DDL180Q
Run the DDL members DDL2201A and DDL2201B during the upgrade
DDL2201A and DDL2201B in the <hlq>.BPWMUDDL data set contain all the SQL required to upgrade the Code Pipeline repository to the new version. This also includes adding the SubAppl column to several tables and pre-populating the field to match the Application (Appl) for the entries. Perform the following steps:
- Run the DDL DDL2201A to perform the first part of the upgrade.
- Run a REORG job by using the sample JCL, $WZDREOG. You can find the REORG job in the <hlq>.BPWMSAMP data set.
- Run the following DDLs to perform the second part of the upgrade:
- DDL2201B
- DDL2201C
- DDL2201D
- Rerun the bind JCL ($WZD6PKG).