Db2 command release incompatibilities
When you migrate from Db2 11 to Db2 12, or apply maintenance in Db2 12, be aware of the command release incompatibilities.
Plan for the following changes in Db2 12 that might affect your migration.
The following incompatible changes apply at any Db2 12 function level, including when you first migrate to Db2 12. For incompatible changes that might impact your Db2 12 environment when you activate function levels 501 and higher, see Incompatible changes summary for function levels 501 and higher.
Change to DISPLAY UTILITY output
The output for the DISPLAY UTILITY command now includes message DSNU285I, regardless of whether the SWITCHTIME parameter was specified in the REORG INDEX or REORG TABLESPACE utility control statement. In Db2 11, message DSNU285I was displayed only if SWITCHTIME was specified in the REORG INDEX or REORG TABLESPACE utility control statement.
Applications that parse DISPLAY UTILITY output might need to be updated.
Actions to take
Determine if any of your applications parse output of the DISPLAY UTILITY command and update the applications if needed.
Changed REBIND command result for SWITCH option with invalid package copies
If you issue a REBIND PACKAGE or REBIND TRIGGER PACKAGE command with the SWITCH option and you specify an invalid package, the command now fails.
In previous releases, the only productive reason to switch to an invalid package copy was as the first action of a two-step process. The second step was to rebind the packages with the APREUSE option to reuse the access path information from the invalid package as input for access path reuse.
Actions to take
If you previously used the two-step process to reuse access paths from invalid copies, modify your process to use a single step. Rebind with the APREUSE option and specify PREVIOUS or ORIGINAL for the APREUSESOURCE bind option to specify whether the previous or original package copy as input for access path reuse.
Change to START RLIMIT command result
Explanation
Messages DSNT731I and DSNT732I might be issued for START RLIMIT commands if resource limit tables are detected with deprecated or unsupported formats.
Starting in Db2 12, DSNRLSTxx table formats and related index formats from before DB2® version 8 format are not supported. When Db2 detects DSNRLSTxx tables with unsupported formats, it issues message DSNT731I.
DSNRLMTxx table formats and related index formats from before Db2 11 are deprecated. In Db2 12, if Db2 detects DSNRLMTxx tables in a deprecated format, it issues message DSNT732I, processing for the START RLIMIT command continues, and the resource limit facility starts using the deprecated objects.
Dynamic SQL applications that are specified in the obsolete resource limit tables can run without the limits.
Actions to take
Update existing resource limit tables to use the supported formats. The DSNTIJSG installation job contains statements that create the database, table space, tables, and indexes for the resource limit facility. You can tailor those statements to create or update the format of resource limit tables.