This process of changing the APPLICATION COMPATIBILITY will only be applicable for QMF 13.1 with the PTF for PH52479 applied. For previous releases and for those QMF 13 users who do not have the fix for PH52479 applied they need to follow the process previously documented for QMF V12.
The default QMF bind job, DSQ1BPKG, binds most QMF runtime packages with the default Db2 for the z/OS APPLCOMPAT setting.
The default for this setting is configured by the Db2 for the z/OS subsystem parameter, APPLCOMPAT, which is referenced by the Db2 for the z/OS subsystem parameter module typically called DSNZPARM.
To access and exploit features available in new Db2 for z/OS 13 and higher function levels, QMF for TSO and 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. Updating the APPLCOMPAT bind option of the QMF packages along with setting the CURRENT APPLICATION COMPATIBILITY special register will allow QMF users access to the new Db2 SQL features.
For example,
If QMF were bound with its default APPLCOMPAT option of V12R1M509 and the Db2 for z/OS server was migrated from Version 12 to Version 13 (V13R1M500), users would not be able to use the new SQL statements and constructs available in V13R1M500.
If attempting to use Db2 for z/OS 13 V13R1M500 functions in QMF for TSO and CICS when the packages were bound with the default APPLCOMPAT V12R1M509, 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 13 were migrated from V13R1M500 to V13R1M503, 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 QMF1310.SDSQEXCE(DSQ1DEFS) change:
APPLCOMP = "V13R1M500"
(Or the desired APPLCOMPAT level).
After setting the APPLCOMP variable in the QMF1310.SDSQEXCE(DSQ1DEFS), run the QMF1310.SDSQSAPE(DSQ1BPKG) job to bind the QMF runtime packages with the new APPLCOMPAT option. Verify that the SYSEXEC DDNAME and DSQDEFS DDNAME in the QMF1310.SDSQSAPE(DSQ1BPKG) job references the correct data set name where the DSQ1DEFS 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 V13R1FL500 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(V13R1M500), 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 = 'V12R1M509'
Note:-
This process of changing the APPLICATION COMPATIBILITY will only be applicable for QMF 13.1 with the PTF for PH52479 applied, For previous releases of QMF for TSO/CICS, and also the user of QMF 13.1 who does not have the fix for PH52479 applied they need to follow the process which is described in the previous release.
https://www.ibm.com/docs/en/qmf/12.2.0?topic=roadmaps-exploiting-new-db2-zos-function-levels
https://community.ibm.com/community/user/datamanagement/blogs/robin-zalud1/2020/06/26/qmf-for-tsocics-exploiting-new-db2-for-zos-functio
#Db2 #Db2QMF #Db2Tools #QMF #Db2 for z/OS