To access and exploit features available in new Db2 for z/OS 12 function levels, QMF for TSO/CICS administrators can adjust QMF's APPLCOMPAT bind option as appropriate. The QMF bind package job can then be rerun to bind QMF packages with the updated APPLCOMPAT option which will allow QMF users access to the new Db2 SQL features.
For example, if QMF were bound with its default APPLCOMPAT option of V11R1 and the Db2 for z/OS server was migrated from Version 11 to Version 12 FL500, users would not be able to use the new SQL statements and constructs available in FL500.
If attempting to use Db2 for z/OS 12 FL500 functions in QMF for TSO/CICS when the packages were bound with the default APPLCOMPAT V11R1, users would get query error messages similar to:
DSQ10496 ATTEMPT TO USE A FUNCTION WHEN THE APPLICATION COMPATIBILITY SETTING IS SET FOR A PREVIOUS LEVEL.
Similarly, if Db2 12 were migrated from FL500 to FL501, the same situation can happen.
To allow users the option of exploiting the new SQL statements by adjusting the APPLCOMPAT bind option, the following modifications can be made:
In QMF1210.SDSQEXCE(DSQ1BPKO) change:
DSNopt = DSNopt || ' APPLCOMPAT(V11R1)'
to:
DSNopt = DSNopt || ' APPLCOMPAT(V12R1M500)'
(or the desired APPLCOMPAT level).
Run the QMF1210.SDSQSAPE(DSQ1BPKG) job to bind the QMF runtime packages with the new APPLCOMPAT option. Verify that the SYSEXEC DDNAME in the QMF1210.SDSQSAPE(DSQ1BPKG) job references the correct data set name where the DSQ1BPKO modification was made.
Verify the DSQ1BPKG job output binds the QMF packages with the correct APPLCOMPAT option.
QMF for TSO/CICS can then be restarted to access the FL500 SQL statements.
If it is desired to revert back to a previous function level behavior, the QMF packages can be bound at the previous APPLCOMPAT level or, users can use the SET CURRENT APPLICATION COMPATIBILITY register to set the behavior to a previous function level value.
For example, using the above method, if QMF packages were bound with APPLCOMPAT(V12R1M504), and behaviors were not as expected, users run the following SQL statement from the QMF SQL Query panel to return behavior to a previous level:
SET CURRENT APPLICATION COMPATIBILITY ='V12R1M503'
Special note and warning to users migrating to Db2 12 FL504 or higher: Be aware that running QMF for TSO/CICS packages with APPLCOMPAT(V12R1M504) or higher will inhibit the ability of Db2 to create new tables in existing simple or segmented table spaces. If your users still SAVE DATA to existing simple and segmented table spaces, (check Q.PROFILES.SPACE to be sure), then you should not implement QMF's usage of FL504 or higher until you migrate your users SAVE DATA usage to implicit table spaces.
See the earlier community update '
Deprecation of simple and segmented table spaces in Db2 and its effects on QMF for TSO/CICS SAVE DATA' for more info.
#QMF #Db2z/OS