Other release incompatibilities

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

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

Changed default values for some subsystem parameters and installation panel fields

Explanation

The default values for some subsystem parameters and installation panel fields have changed. The new values are listed in the table below.
Table 1. Subsystem parameters and installation panel fields with new default values
Parameter Field Panel Db2 10 default value Db2 11 default value
REORG PART SORT NPSI field (REORG_PART_SORT_NPSI subsystem parameter) REORG PART SORT NPSI (none in Db2 10) DSNTIP62 NO AUTO
SUBQ_MIDX none none DISABLE ENABLE

Possible impact to your Db2 environment

This change has no impact on your Db2 environment if you maintain your current subsystem parameter settings during migration.

Actions to take

If your Db2 subsystem uses the Db2 10 default value for any of these parameters, review the parameter descriptions to determine if the Db2 11 default value is more appropriate.

Changed maximum values for some subsystem parameters

Explanation

The maximum values for some subsystem parameters have changed. The new values are listed in the table below.
Table 2. Subsystem parameters that have new maximum values
Subsystem parameter Db2 10 maximum value Db2 11 maximum value
EDM SKELETON POOL SIZE field (EDM_SKELETON_POOL subsystem parameter) 2097152 4194304
EDM DBD CACHE field (EDMDBDC subsystem parameter) 2097152 4194304
EDM STATEMENT CACHE field (EDMSTMTC subsystem parameter) 1048576 4194304
MAX KEPT DYN STMTS field (MAXKEEPD subsystem parameter) 65535 204800

Actions to take

If your subsystems operate at or near the old maximum value, review the new maximum values and determine if your subsystem would benefit from increasing the value of any of these subsystem parameters.

Change to job DSNTEJ6Z

Explanation

In Db2 11, the DSN8ED7 installation verification program calls the SYSPROC.ADMIN_INFO_SYSPARM stored procedure instead of the SYSPROC.DSNWZP stored procedure.

Possible impact to your Db2 environment

If you do not have the ADMIN_INFO_SYSPARM stored procedure installed the installation verification procedure fails.

Actions to take

If you run job DSNTEJ6Z, which prepares and runs the DSN8ED7 program, ensure that the ADMIN_INFO_SYSPARM stored procedure is installed and correctly configured.

Change to log capture exit routine

Explanation

Begin program-specific programming interface information.

In Db2 11, log buffers are moved from 31-bit key 7 private storage to 64-bit key 0 fetch-protected common storage. Therefore, the log capture exit routine must be invoked in 64-bit mode. In Db2 10, the log capture exit routine is called in AMODE(31), key 7. In Db2 11, the log capture exit routine is called in AMODE(64), key 0. Also in Db2 10, the parameter list consists of two 31-bit pointers. The parameter list now contains two 64-bit pointers that point to the standard EXPL parameter list and to the log capture exit parameter list (LOGX). As in prior releases, the log capture exit routine can be invoked in either TCB or SRB mode.

Possible impact to your Db2 environment

If the log capture exit is not updated to handle the new environment and the modified parameter list, an abend might occur. If you use a data replication product that uses the log capture exit, that product will not work until it is updated.

Actions to take

If you use the log capture exit routine, ensure that the exit is updated to handle the new environment and the modified parameter list.

End program-specific programming interface information.

Expanded fields in trace records

Explanation

Begin program-specific programming interface information.

The following changes are made to trace records in Db2 11:

  • Trace record fields that contain RBA or LRSN values expand to 10 bytes. In most cases, the expanded RBA or LRSN fields move so that offsets of fields that follow do not change. However, field QW0204UR cannot move.
  • Some fields in IFCID 0002 and IFCID 0225 that are related to shareable storage have been expanded from 4 to 8 bytes, moved, and renamed.

Possible impact to your Db2 environment

These changes might affect your environment in the following ways:

  • Programs that format IFCID 0204 output might generate incorrect information.
  • Programs that refer to IFCID 0002 and IFCID 0225 fields by name might need to be changed.

Actions to take

Adjust your programs as follows:

  • Adjust programs that format trace information to account for the increased size of the QW0204UR field, and the modified offsets of the fields that follow it.
  • Adjust programs that refer to IFCID 0002 and IFCID 0225 in the following ways:
    • References to field QISEKSPA in IFCID 0002 must be changed to use new field QISEKSPA8.
    • References to field QW0225SC in IFCID 0225 must be changed to use new field QW0225SC8.
    • References to field QW0225LS in IFCID 0225 must be changed to use new field QW0225LS8.
    • References to field QW0225SX in IFCID 0225 must be changed to use new field QW0225SX8.
    • References to field QW0225HS in IFCID 0225 must be changed to use new field QW0225HS8.
End program-specific programming interface information.

Moved fields in trace records

Explanation

Begin program-specific programming interface information.

The following changes are made to trace records in Db2 11:

  • Field QW0225DMH in IFCID 0225 has moved. In Db2 10, this field follows field QW0225F2. In Db2 11, this field is at the end of section 4, following field QW0225HS8.

Possible impact to your Db2 environment

This change might affect your environment in the following ways:

  • Programs that refer to IFCID 0225 fields by offset need to be changed.

Actions to take

Adjust your programs as follows:

  • Ensure that your applications use the latest DSNDQW03 mapping macro, so that the applications reference
  • the correct IFCID 0225 fields.
End program-specific programming interface information.

Changed default classes for monitor trace

Explanation

Begin program-specific programming interface information.

In previous releases of Db2, when a monitor trace was started without the CLASS keyword, only monitor trace class 1 was started. In Db2 11, monitor trace class 11 is also started.

Possible impact to your Db2 environment

The return area that is defined in your IFI applications might be too small to hold the additional trace records.

Actions to take

Adjust your programs in one of the following ways:

  • Specify the CLASS or IFCID keyword in your START TRACE command so that you start only the trace classes or IFCIDs that you need.
  • Increase the size of the IFI return area.
End program-specific programming interface information.

Client information in messages

In Db2 11 conversion mode, the length of client information values in several messages might change significantly. The maximum length and blank padding of client information values for user ID, workstation name, application name, and accounting information as set by the connection.

Explanation

In Db2 11 the following messages length changes for client information values:
  • DSNB260I
  • DSNI031I
  • DSNJ031I
  • DSNR035I
  • DSNR048I
  • DSNT318I
  • DSNT375I
  • DSNT376I
  • DSNT377I
  • DSNT378I
  • DSNV436I
  • DSNV437I

Possible impact to your Db2 environment

Any programs that read message text must tolerate changes to the length of token values.

Actions to take

If you have applications that read the message text, change your applications to process the updated text.

The SPUFI DBRM (DSNESM68) is now versioned

Explanation

In past releases, DSNESM68, the DBRM for the SPUFI facility, was not versioned. It also had a fixed consistency token of x'149EEA901A79FE48', making it possible for SPUFI to connect to remote locations where the package was bound only locally. Although this provision was convenient, it raised the risk of enhancements and service changes. In Db2 11, DSNESM68 is versioned.

Possible impact to your Db2 environment

This change might affect how you must bind SPUFI to connect to remote locations.

Actions to take

Use standard procedure to bind SPUFI at a remote location using a versioned DSNESM68 DBRM. The following example shows how to bind Db2 11 SPUFI to connect to a remote DB2® 10 server. Use the bind statements for the DSNESPCS package and plan as a model for binding the DSNESPRR and DSNESMUR packages and plans.
DSN SYSTEM(v11_ssid)
  BIND PACKAGE(DSNTIAP) MEMBER(DSNTIAP) -
       ACTION(ADD) ENCODING(EBCDIC) -
       LIBRARY('db2_v11_prefix.SDSNDBRM')
  BIND PACKAGE(v10_location.DSNTIAP) MEMBER(DSNTIAP) -
       ACTION(ADD) ENCODING(EBCDIC) -
       LIBRARY('db2_v11_prefix.SDSNDBRM')

  BIND PACKAGE(DSNESPCS) MEMBER(DSNESM68)
       ACTION(ADD) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) -
       LIBRARY('db2_v11_prefix.SDSNDBRM')
  BIND PACKAGE(v10_location.DSNESPCS) MEMBER(DSNESM68)
       ACTION(ADD) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) -
       LIBRARY('db2_v11_prefix.SDSNDBRM')
  BIND PLAN(DSNESPCS) -
       PKLIST(*.DSNESPCS.DSNESM68, -
              *.DSNTIAP.DSNTIAP) -
       ACTION(ADD) RETAIN -
       ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC)

New impact of IIPHONORPRIORITY parameter

Explanation

In Db2 11 , when the IIPHONORPRIORITY parameter in the IEAOPTxx member of SYS1.PARMLIB is set to NO, Db2 does not allow system tasks to become eligible for IBM® Z Integrated Information Processor (zIIP) processing.

Possible impact to your Db2 environment

If your IIPHONORPRIORITY parameter is set to NO, you might observe fewer tasks being routed to zIIP specialty engines in Db2 11 .

Actions to take

Examine your zIIP workloads and determine whether your current IIPHONORPRIORITY setting is still appropriate for your environment.
  • If IIPHONORPRIORITY is changed dynamically to YES, restart Db2 to allow system tasks to become eligible for zIIP processing.
  • If IIPHONORPRIORITY is changed dynamically to NO, restart Db2 to stop system tasks being routed to zIIP specialty engines.

Changed messages and codes

The text of some messages and codes is changed. In general, the change is effective in conversion mode. If you have applications that read the message and code text, change your applications to process the updated text. See the troubleshooting information for lists of changed messages and codes. Your application must also tolerate changes to the length of token values.