Remigrating in a data sharing environment

You can remigrate one member at a time or all members of a data sharing group.

Before you begin

Before you remigrate, refer to Incompatible changes in Db2 13 because many of those considerations apply to remigration, too. Whether each consideration applies to your subsystem depends on the type of activity that took place on your Db2 12 subsystem after falling back.

Regardless of the ABIND subsystem parameter value, plans and packages continue to run on Db2 13 as bound on Db2 12, until you explicitly rebind them on Db2 13. It is best to do so only after you are certain that Db2 13 is stable and release coexistence and fallback are no longer a concern.

Recommendation: Avoid automatic rebinds during migration and remigration. After your remigrated system is stable, you can rebind your packages with PLANMGMT(EXTENDED). If a new package does not perform adequately, you can rebind with SWITCH(PREVIOUS) to return to the old package.

Procedure

To remigrate your subsystem to Db2 13:

  1. Check the integrity of your Db2 12 catalog and directory:
    • Run the DSN1COPY utility with the CHECK option on your catalog table spaces.
    • Run the CHECK DATA utility.
    • Run the queries in member DSNTESQ of prefix.SDSNSAMP.
  2. Optional: Start of changeUse DSNTIJIC to take an image copy of your Db2 12 catalog.End of change
    This step is not required, but it is recommended.
  3. Stop Db2 12.
  4. Reconnect TSO, IMS, and CICS® to Db2.
    Re-establish your Db2 13 logon procedures and JCL, as well as your Db2 13 CICS and IMS connections.
  5. Rebuild Db2 13 cataloged procedures.
    Rename the Db2 13 procedures that were renamed by job DSNTIJFV during fallback. If job DSNTIJFV was not run, you need to rerun jobs DSNTIJMP, DSNTIJMV, and DSNTIJMW.
  6. Start Db2 13. Ensure that you are using your Db2 13 subsystem parameter load module.
    Tip: Start of changeIf you issued the ACTIVATE command after falling back to Db2 12, Db2 13 might issue reason code 00C900A6 after you remigrate. To resolve this situation, run the CATMAINT utility and specify LEVEL V13R1M100. You can use the DSNTIJTC migration job.End of change
  7. Take an image copy of the Db2 13 catalog by using the DSNTIJIC job.
  8. Verify your Db2 13 system.