Migration and continuous delivery in documentation

The Db2® 13 migration process and continuous delivery of new capabilities can affect how you use this information. Before you activate new function in Db2 13, you might need to continue to refer to the documentation for the previous release.

Documentation updates for continuous delivery

This Db2 13 for z/OS® product documentation generally assumes that the highest available function level is activated and that your applications are running with the highest available application compatibility level, with the following exceptions:

The following documentation sections describe the Db2 13 migration process and how to activate new capabilities in function levels:
FL 500 Labels like this one usually mark new content or changes for Db2 function levels. The lable is also a link to the description of the function level that introduces the changes. For more information, see How Db2 function levels are documented.

Continuous delivery in Db2 13

The availability of most new-function application capabilities in Db2 13 depends on the type of enhancement, the activated function level, and the application compatibility levels of each application. For a list of all available function levels that are currently available in Db2 13, see Db2 13 function levels.

Many new-function enhancements take effect at any function level when you apply a PTF in each Db2 subsystem or data sharing member. For more information, see New-function APARs for Db2 13.

Availability of virtual storage and optimization enhancements

Some virtual storage and optimization enhancements take effect in function level 100. Optimization enhancements become available after full prepare of the SQL statements, depending on the statement type:

For static SQL statements, after bind or rebind of the package.
For non-stabilized dynamic SQL statements, immediately, unless the statement is in the dynamic statement cache.
For stabilized dynamic SQL statements, after invalidation, free, or changed application compatibility level.

Revision marks for changed content

Start of change Technical revisions are marked like this paragraph to identify any of the following types of changes: End of change

Changes that are introduced at general availability (GA) in the Db2 13 release.
Changes that are introduced by maintenance after the GA of Db2 13.
Changes introduced in new Db2 13 function levels.
Clarifications in response to customer and internal feedback.

Editorial and organizational changes that do not affect the technical meaning of the content are generally not marked.