Blog
DB2utor

Categories

November 05, 2013

Deprecations and Other Changes in DB2 11

As I was reading the DB2 11 announcement letter (U.S. version here; EMEA version here), I noticed that SYNONYMS has been deprecated and the recommendation is to use ALIAS. This could have a huge impact on existing development environments; it will greatly affect DBAs.

In addition to SYNONYMS, these functions have been deprecated in DB2 11:

• SQL processing options NEWFUN(YES) and NEWFUN(NO): Rather than select YES/NO, you'll need to use the DB2 version number -- e.g., NEWFUN(V11) or NEWFUN(V10).

• dsnhdecp parameter values NEWFUN=YES and NEWFUN=NO: Although these values are supported in DB2 11, NEWFUN=V11 and NEWFUN=V10 should be used.

Private_Protocol, a subsystem parameter, is also deprecated in DB2 11. The functionality this parameter controls won't apply to later DB2 releases.

In addition, these utility options are deprecated:

• REORG TABLESPACE UNLOAD (ONLY, PAUSE and EXTERNAL): Use the UNLOAD utility instead.

• REORG TABLESPACE/INDEX  (INDREFLIMIT, OFFPOSLIMIT): Use the DSNACCOX stored procedure to determine if the object needs to be reorganized.

• REORG TABLESPACE/INDEX ( INDREFLIMIT,OFFPOSLIMIT) REPORTONLY.

• REORG INDEX UNLOAD ONLY: Use the DIAGNOSE utility stop the process instead.

• LOAD FORMAT UNLOAD: Use the LOAD FORMAT INTERNAL option to load data that was unloaded with UNLOAD FORMAT INTERNAL.

• COPY CHANGELIMIT: Use the DSNACCOX stored procedure to determine if the object needs to be copied.

• REPAIR VERSIONS: Use the REPAIR CATALOG utility instead.

These utility options are still supported in DB2 11, but they'll be removed in a later DB2 release.

Here are some other notable changes:

• As of DB2 11, password protection for active log and archive log data sets is no

longer supported.

• The DSNH CLIST no longer supports values of NEWFUN=V8 or NEWFUN=V9.

• The following DB2-supplied routines are removed in DB2 11 and are unavailable to callers after migration to conversion mode. A report is added to the DSNTIJPM premigration job to detect occurrences of these routines on an existing subsystem or data sharing group, and to specify that these routines are not available in DB2 11.

– SYSPROC.DSNAEXP

– AMI-based DB2 MQ functions:

DB2MQ1C.GETCOL

DB2MQ1C.MQPUBLISH

DB2MQ1C.MQREAD

DB2MQ1C.MQSUBSCRIBE

DB2MQ1C.MQUNSUBSCRIBE

DB2MQ2C.GETCOL

DB2MQ2C.MQPUBLISH

DB2MQ2C.MQREAD

DB2MQ2C.MQSUBSCRIBE

DB2MQ2C.MQUNSUBSCRIBE

• These subsystem parameters are removed in DB2 11:

ASSIST

COORDNTR

DISABSCL

DISALLOW_DEFAULT_COLLID

MSVGP

MSVGP2

OJPERFEH

OPTIOPIN

OPTIOWGT

OPTIXIO

PGRNGSCR

PTCDIO

RETVLCFK

SEQCACH

SEQPRES

SMSDCFL

SMSDCIX

STATCLUS

• The application programming default value CHARSET has also been removed. In DB2 11, you cannot use the BIND PACKAGE options ENABLE and DISABLE(REMOTE) REMOTE (location-name,...,(luname),...) to enable or disable specific remote connections. You can use the ENABLE(REMOTE) or DISABLE(REMOTE)

options to enable or disable all remote connections.

• Sysplex query parallelism is no longer supported. Packages that used sysplex query parallelism in previous releases use CPU parallelism in DB2 11.

• The DSN1CHKR utility is no longer supported. DSN18101 and DSN18161 messages are issued when the DSN1CHKR utility is invoked.

I’m thinking that the deprecation of synonyms and other functions will affect customers' development processes and production job schedules. (Here's just one consideration: Do you use REORG to unload data?) I'd greatly appreciate your input on this list of deprecations and how your processes might be impacted.