Falling back to Db2 12

If you encounter serious errors after tailoring the catalog and directory for Db2 13, you can return to Db2 12. Fallback to Db2 12 is only supported if Db2 13 is at function level 100.

Before you begin

Fallback to Db2 12 is not supported after activation of function level 500 in Db2 13.

Before you fall back to your previous Db2 version, consider the implications of doing so. For details, see Implications of falling back.

About this task

Fallback is the process of returning to Db2 12 after migrating the catalog and directory to Db2 13, as described in Migration step 16: Tailor the Db2 13 catalog: DSNTIJTC. It is best to fall back only if you encounter severe errors while operating in Db2 13. After fallback, the catalog remains a Db2 13 catalog.

You cannot fall back to Db2 12 after you activate function level 500.

Remigrating is the process of returning to Db2 13 after falling back.

Procedure

To fall back to Db2 12, complete the following steps:

  1. Stop Db2 13.
  2. Run job DSNTIJFV to rename the cataloged procedures and reactivate Db2 12 code.
  3. Reconnect TSO, IMS, and CICS® to Db2 12.
  4. Start Db2 12.
  5. Run the Db2 12 installation verification jobs (DSNTEJxx).

What to do next

You can save your Db2 13 TSO logon procedures and JCL for remigration to Db2 13.