Migration step 3: Identify invalid packages (optional)

Start of changeMigrating to Db2 12 renders some packages invalid. End of change

Procedure

Start of changeTo identify which packages are invalid after migration to Db2 12:End of change

Start of changeRun the following query on the Db2 11 subsystem that you are migrating.End of change
Start of changeBegin program-specific programming interface information.
SELECT DISTINCT SUBSTR(STRIP(BNAME) || '  ', 1, 18), 
 STRIP(DCOLLID) || '.' || STRIP(DNAME) || '.' || HEX(DCONTOKEN)
  FROM SYSIBM.SYSPACKDEP                              
  WHERE (BTYPE = 'I'                                  
         AND BQUALIFIER = 'SYSIBM'
         AND BNAME IN ('DSNOTX01', 'DSNATX02')
        )                                              
   OR (BTYPE = 'T'                                  
       AND BQUALIFIER = 'SYSIBM'
       AND BNAME IN('SYSCONTROLS', 'SYSENVIRONMENT',
                    'SYSINDEXES', 'SYSKEYS',
                    'SYSPACKAGE', 'SYSPACKCOPY',
                    'SYSROUTINES', 'SYSTABLES',
                    'SYSTRIGGERS')
      )                                              
 ORDER BY 1, 2
End program-specific programming interface information.End of change

If you are not in a data sharing coexistence environment, after migration, you can explicitly rebind these packages or let Db2 rebind them automatically. Start of changeIf you are in a data sharing coexistence environment, rebind these packages before you migrate any members to Db2 12.End of change