The APPLCOMPAT bind option is now used to bind packages during the Bind Product Plans and Packages
task in Post-Install tailoring of the Database Management Solutions for DB2 for z/OS.
The Database Management Solutions for Db2 for z/OS Bind job (ssid0002) must be regenerated and run
when Db2 is upgraded to a new Function Level.
How do the products determine the APPLCOMPAT Bind Option?
Release : 20.0
Component: Database Management for Db2 for z/OS Suite
Below is detail on how the APPLCOMPAT Bind Option is determined:
Common components for Db2 provide a DEFAULT value for APPLCOMPAT of V12R1M500 for Db2 12
running at that level or higher, however the product teams may override.
An example is Batch Processor (and ISQL), which is bound with the SSIDVERF from the
SETUPxx member within hlq.CDBAPARM.
Example 1:
Default is V12R1M500
Product overrides to V12R1M505
SETUP DB2VERF is V12R1M502
The generated APPLCOMPAT will be V12R1M502
Example 2:
Default is V12R1M500
Product overrides to V12R1M502
SETUP DB2VERF is V12R1M505
The generated APPLCOMPAT will be V12R1M502 due to product overrides
APPLCOMPAT on the Bind cannot be higher than the activated Function Level, which must be reflected in the SSIDVERF.
Upgrade to a new DB2 Release or Function Level
In this example the plans are bound at a lower DB2 release level (V11), DB2 was upgraded from M100 to M501, the setup member was updated (SSIDVERF V12R1M501, SSIDVERC V12R1M500), the BIND was not regenerated and run. The packages are still bound at V11 NFM, the ISQL select has a new parameter from V12.
Executing a SELECT thru ISQL receives:
DSNT408I SQLCODE = -4743, ERROR: ATTEMPT TO USE A FUNCTION WHEN THE APPLICATION COMPATIBILITY SETTING IS SET FOR A PREVIOUS LEVEL