Command release incompatibilities

When you migrate from Db2 10 to Db2 11, be aware of the command release incompatibilities.

Begin general-use programming interface information.

Plan for the following changes in Db2 11 that might affect your migration.

Change to DISPLAY UTILITY output

Explanation

The output for the DISPLAY UTILITY command now includes the date and the time when the job was submitted.

Possible impact to your Db2 environment

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.

End general-use programming interface information.

Removing the SYSPUBLIC schema from the PATH bind option

Starting in Db2 11 conversion mode, SYSPUBLIC is the schema that is used for public aliases. As such, the PATH bind option must not specify the SYSPUBLIC schema.

Explanation

In previous versions, you were not restricted from specifying SYSPUBLIC as part of the PATH bind option. With Db2 11 you will no longer be able to specify SYSPUBLIC as part of the PATH bind option.

Possible impact to your Db2 environment

Creation or resolution of some objects that worked in previous versions of Db2 might fail in Db2 11 with SQLCODE -713 if SYSPUBLIC is specified as part of the PATH bind option.

Actions to take

Query the catalog to see if any object schemas use SYSPUBLIC as the schema qualifier. This is highly unlikely for any object, but most likely with objects that use the PATH (functions, procedures, and sequences).

Change any existing PATH bind option to not specify SYSPUBLIC as a schema.

LIBRARY bind option delimiters

Starting in Db2 11, you might need to add single quotation mark (') delimiters to LIBRARY bind option values that specify partitioned data sets.

Explanation

Before Db2 11, LIBRARY bind option values that specify partitioned data set names can be specified with or without single quotation mark delimiters. Partitioned data set names without delimiters are taken as is if the bind command has no TSO segment. When the bind command has a TSO segment, Db2 prefixes nondelimited partitioned data set names with a user name. Db2 11 introduces support for zFS DBRM files. A result is that when the bind command has no TSO segment, the partitioned data set name is also prefixed with a default user name. The timing for resolving the dataset name is changed such that Db2 has no information about whether the bind command has a TSO segment.

Possible impact to your Db2 environment

BIND PACKAGE commands with a LIBRARY option value that indicates a non-delimited value for partitioned data set might fail with z/OS® TSO/E message IKJ56228I.

Actions to take

Determine whether BIND PACKAGE commands must be updated. If a BIND command fails with the z/OS TSO/E message IKJ56228I, add single quotations mark delimiters to the dataset name. If a BIND package command runs successfully, no action is required.