Default language.

Task 3: Execute the DDL samples to address Db2 repository changes


This section describes the Db2 repository changes that you need to make.

Warning

Important

Before performing this task, back up your data. Work with your DBA to make image copies of all the tablespaces to ensure that no data is lost if anything goes wrong.

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:

  1. DDL180A
  2. DDL180B
  3. DDL180C
  4. DDL180D
  5. DDL180E
  6. DDL180F
  7. DDL180G
  8. DDL180H
  9. DDL180K
  10. DDL180L
  11. DDL180M
  12. DDL180N
  13. DDL180O
  14. DDL180Q

Run the DDL members DDL2201A and DDL2201B during the upgrade

Warning

Important

Because some conversion processes are included with the DDL upgrade process and DDL will change the schema, you must run the DDL upgrade jobs during the upgrade window and not in advance.

Please consult with your Db2 DBA to ensure that the appropriate backups have been performed. This is important for recovering the pre-upgrade schema and data. Plan the backout process carefully, and consider backing up the Code Pipeline lifecycle and warehouse datasets as well.

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:

  1. Run the DDL DDL2201A to perform the first part of the upgrade.
  2. Run a REORG job by using the sample JCL, $WZDREOG. You can find the REORG job in the <hlq>.BPWMSAMP data set.
  3. Run the following DDLs to perform the second part of the upgrade:
    1. DDL2201B 
    2. DDL2201C 
    3. DDL2201D 
  4. Rerun the bind JCL ($WZD6PKG).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevX Code Pipeline 22.01