SET CURRENT APPLICATION COMPATIBILITY = 'V12R1M505' before Drops

Products

• RC/Migrator for DB2 for z/OS
• RC/Update for DB2 for z/OS
• RC Compare for DB2 for z/OS

Issue/Introduction

In RC/Migrator for DB2 for z/OS, Drop statements for tablespaces are wrapped with:

    SET CURRENT APPLICATION COMPATIBILITY = 'V12R1M505'

Why is this needed before a Drop statement, and why is this SET to FL 505?

Environment

Database Management for DB2 for z/OS r20

Resolution

DROP TABLESPACE statements are wrapped with ' SET CURRENT APPLICATION COMPATIBILITY' statements in order to prevent the dropping of other explicitly created objects.

This was introduced in RCM PTF SO10974 Mitigate Enhanced Drop Table Support. The RCU equivalent is SO10975.

Db2 12 FL506 changed the behavior of DROP TABLESPACE statements, if the table residing in it contained any LOB columns, explicitly created LOB
tablespaces and Auxiliary tables they would also be dropped. By setting the  application compatibility to 505,  this behavior will not occur.