Verify Db2 13 premigration activities and activate function level 510 in Db2 12

Before you can migrate Db2 to Db2 13, you must complete certain premigration activities and activate function level 510 in Db2 12.

To verify Db2 13 premigration activities in Db2 13

1. Make plans to resolve incompatible changes before migration to Db2 13.
   For more information, see the following topics:
   • Incompatible changes in Db2 13
   • Function that Db2 13 no longer supports
   • Deprecated function in Db2 13
2. Complete the following premigration steps and activate function level 510.
   1. If Db2 12 is still at function level 100, activate function level 500 or 501 first. See Activating Db2 12 new function at migration.
   2. Check that Db2 is at a sufficient code level by issuing a DISPLAY GROUP command, as described in Determining the Db2 code level, catalog level, and function level. The DSN7100I message indicates the Db2 code level for under DB2 LVL in the member details. If DB2 LVL for any member is lower than 121510, apply the PTF for APAR PH33727 and any other required maintenance, so that all members indicate 121510.
      Tip: You can apply any PTF at any function level. It is best to run Db2 at this code level or higher for some time before you proceed with activating the function level. Db2 cannot run at any lower code level after you activate a function level, so you cannot remove any of the required PTFs after you activate a function level.
   3. Run premigration job DSNTIJPE and resolve any release incompatibilities that it identifies.
   4. Rebind any packages that are identified by the DSNTIJPE job. The job uses the following query to identify packages that were used in the last 18 months and were last bound or rebound in a release before Db2 11, and activation of function level V12R1M510 succeeds only if this query returns 0 rows.

      SELECT * 
        FROM SYSIBM.SYSPACKAGE 
             WHERE LASTUSED >= DATE(DAYS(CURRENT DATE) - 548) 
                           AND RELBOUND NOT IN ('P','Q',’R’)
                           AND VALID <> ‘N’ 
                           AND OPERATIVE <> ‘N’;

      Until you complete this step, DISPLAY GROUP command output indicates HIGHEST POSSIBLE FUNCTION LEVEL (V12R1M509) or lower, depending on the catalog level.

      Important: If the DISABLE_EDMRTS subsystem parameter setting is YES in your Db2 12 environment, the SYSPACKAGE.LASTUSED column is not reliable. Function level V12R1M510 activation might succeed even though automatic rebinds remain likely to occur in Db2 13. To avoid such automatic binds from blocking the migration or requiring a fallback, adapt and follow the practices described in Rebind old plans and packages in Db2 12 to avoid disruptive autobinds in Db2 13 as you prepare for migration to Db2 13.
   5. Tailor the CATMAINT and function level activation jobs by running the installation CLIST:
      1. In panel DSNTIPA1, specify INSTALL TYPE ===> ACTIVATE. Then, specify the name of the output member from the previous function level activation (or migration) in the INPUT MEMBER field, and specify a new member name in the OUTPUT MEMBER field.
      2. In panel DSNTIP00, specify TARGET FUNCTON LEVEL ==> V12R1M510. The Db2 installation CLIST uses this value when it tailors the ACTIVATE command in the DSNTIJAF job and the CATMAINT utility control statement in the DSNTIJTC job.
      3. Proceed through the remaining Db2 installation CLIST panels, and wait for the Db2 installation CLIST to tailor the jobs for the activation process. The output data set contains the tailored jobs for the activation process. For more information, see The Db2 installation CLIST panel session.
   6. Run the DSNTIJIC job to take an image copy of the Db2 catalog and directory.
   7. Run the tailored DSNTIJTC job, or run the CATMAINT utility with LEVEL V12R1M510, to update the catalog to the appropriate catalog level. If multiple catalog updates are required, the CATMAINT job processes each update in sequential order. If a later update in the sequence fails, the previous successful updates do not roll back, and the catalog level remains at the highest level reached. If that occurs, you can correct the reason for the failure and resubmit the same CATMAINT job.
   8. If the CATMAINT utility jobs from the previous step placed any altered Db2 catalog objects in REORG-pending (AREO*) advisory status, run the REORG utility for those objects.
   9. Check that Db2 is ready for function level activation by issuing the following ACTIVATE command with the TEST option:

      -ACTIVATE FUNCTION LEVEL (V12R1M510) TEST

      Db2 issues message DSNU757I to indicate the results. For more information, see Testing Db2 function level activation.
   10. Run the tailored DSNTIJAF job, or issue the following ACTIVATE command:

       -ACTIVATE FUNCTON LEVEL(V12R1M510)

       Tip: If older packages run in Db2 12 after you activate function level 510, the HIGHEST POSSIBLE FUNCTION LEVEL value can indicate V12R1M509, even though the HIGHEST ACTIVATED FUNCTION LEVEL value is V12R1M510. In this case, you can still migrate to Db2 13 without any further action. However, possibly disruptive automatic rebinds might occur in Db2 13 unless you rebind these packages first. To determine which packages to rebind, run the queries in the DSNTIJPM or DSNTIJPE migration jobs.