Announcing Db2 12 function level 504

Paul McWilliams

Announcing Db2 12 function level 504

The documentation for Db2 12 function level 504 is now available in IBM Knowledge Center, and you can also read about function level 504 in two Db2 News from the Lab blog posts:

 


Paul A. McWilliams

Db2 for z/OS Technical Writer IBM Silicon Valley Laboratory

Knowledge CenterDoc PDFs | Doc feedback | Db2 for z/OS News from the Lab

Edited By:
Paul McWilliams[Organization Members] @ Mar 06, 2019 - 05:02 PM (America/Eastern)
Paul McWilliams[Organization Members] @ Mar 06, 2019 - 05:03 PM (America/Eastern)

James Campbell

Announcing Db2 12 function level 504
(in response to Paul McWilliams)
> * "You can prevent the creation of new deprecated objects in Db2 12 function level 504"
> http://ibm.biz/Bd2CwC

and if you do and you have QMF, do consider Q.PROFILES.SPACE.

James Campbell


On 6 Mar 2019 at 14:59, Paul McWilliams wrote:

>
> The documentation for Db2 12 function level 504 is now available in IBM Knowledge Center:
> https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/wnew/src/tpc/db2z_fl_v12r1m504
> .html
> You can also read about function level 504 in two Db2 News from the Lab blog posts:
> * "Announcing Db2 12 function level 504!" https://ibm.biz/Bd2CwL
> * "You can prevent the creation of new deprecated objects in Db2 12 function level 504"
> http://ibm.biz/Bd2CwC
>  
>
> Paul A. McWilliams
> Db2 for z/OS Technical Writer IBM Silicon Valley Laboratory
> Knowledge Center | Doc PDFs | Doc feedback | Db2 for z/OS News from the Lab



---
This email has been checked for viruses by AVG.
https://www.avg.com

Perry Spada

RE: Announcing Db2 12 function level 504
(in response to Paul McWilliams)

So based on the previously referenced article,  "You can prevent the creation of new deprecated objects in Db2 12 function level 504", if the IBM program, DSNTEP2, was bound under function level 504 or later due to maintenance, it would generate an error if it attempted to issue CREATE TABLE statement  in an existing classic segmented or simple table space. Under M504, DSNTEP2 would also generate an error if it an encountered a CREATE TABLESPACE with just the SEGSIZE parm specified (for segmented tablespace) or CREATE TABLESPACE with NUMPARTS and SEGSIZE 0 specified (for classic partitioned tablespace). If you cannot readily convert your table spaces to one of the universal table spaces, then specifying the following DDL statement "SET CURRENT APPLICATION COMPATIBILITY ='V12R1M503' (or less) first would allow you to create the deprecated objects using DSNTEP2 bound under M504 or higher. Am I interpreting this correctly?

Phil Grainger

Announcing Db2 12 function level 504
(in response to Perry Spada)
Yes

(Long question, short answer!)

Sent from my iPhone

On 13 Mar 2019, at 17:49, Perry Spada <[login to unmask email]<mailto:[login to unmask email]>> wrote:


So based on the previously referenced article, "You can prevent the creation of new deprecated objects in Db2 12 function level 504", if the IBM program, DSNTEP2, was bound under function level 504 or later due to maintenance, it would generate an error if it attempted to issue CREATE TABLE statement in an existing classic segmented or simple table space. Under M504, DSNTEP2 would also generate an error if it an encountered a CREATE TABLESPACE with just the SEGSIZE parm specified (for segmented tablespace) or CREATE TABLESPACE with NUMPARTS and SEGSIZE 0 specified (for classic partitioned tablespace). If you cannot readily convert your table spaces to one of the universal table spaces, then specifying the following DDL statement "SET CURRENT APPLICATION COMPATIBILITY ='V12R1M503' (or less) first would allow you to create the deprecated objects using DSNTEP2 bound under M504 or higher. Am I interpreting this correctly?

-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.

Phil Grainger

Announcing Db2 12 function level 504
(in response to Phil Grainger)
But people should be aware of the increasingly less-than-subtle hints about deprecated objects and plan for their replacement before you are forced to do so

Sent from my iPhone

On 13 Mar 2019, at 17:51, Grainger, Phil <[login to unmask email]<mailto:[login to unmask email]>> wrote:

Yes

(Long question, short answer!)

Sent from my iPhone

On 13 Mar 2019, at 17:49, Perry Spada <[login to unmask email]<mailto:[login to unmask email]>> wrote:


So based on the previously referenced article, "You can prevent the creation of new deprecated objects in Db2 12 function level 504", if the IBM program, DSNTEP2, was bound under function level 504 or later due to maintenance, it would generate an error if it attempted to issue CREATE TABLE statement in an existing classic segmented or simple table space. Under M504, DSNTEP2 would also generate an error if it an encountered a CREATE TABLESPACE with just the SEGSIZE parm specified (for segmented tablespace) or CREATE TABLESPACE with NUMPARTS and SEGSIZE 0 specified (for classic partitioned tablespace). If you cannot readily convert your table spaces to one of the universal table spaces, then specifying the following DDL statement "SET CURRENT APPLICATION COMPATIBILITY ='V12R1M503' (or less) first would allow you to create the deprecated objects using DSNTEP2 bound under M504 or higher. Am I interpreting this correctly?

-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.
-----End Original Message-----
BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately.