Functions that are no longer supported for systems migrating from Version 8

If you are migrating to DB2® 10 from Version 8, be aware of the functions that are no longer supported.

The following functions are not supported in DB2 10.

BookManager format is discontinued

IBM® is discontinuing the BookManager® format as part of an ongoing effort to deliver the best possible information experience to our customers. IBM optimizes DB2 10 for z/OS® documentation for viewing in IBM Knowledge Center.

The BookManager books will continue to be provided for the life cycle of DB2 Version 8 and DB2 9; however, IBM is not delivering BookManager books beginning in DB2 10. The includes all of the information that you are used to seeing in BookManager and PDF, plus many improved features for finding and viewing the information that you need to do your job.

msys for Setup DB2 Customization Center

In DB2 10, msys for Setup DB2 Customization Center is removed. Instead, use the installation panels. For more information about using the installation panels, see Tailoring DB2 jobs to your environment using the installation CLIST.

Optimization Service Center

In DB2 10, Optimization Service Center is no longer supported. The recommended no-charge query optimization and service tool is IBM Data Studio, which is a query serviceability tool for DB2 10 for z/OS. This tool is based and built on the foundation of Optimization Service Center and Optimization Expert.

Java stored procedures no longer run in resettable JVMs (starting in DB2 9)

In releases before DB2 9, Java stored procedures could be run in resettable JVMs. In DB2 10, Java stored procedures cannot be run in resettable JVMs.

Because Java stored procedures cannot be run in resettable JVMs, they are no longer automatically prevented from impacting the execution of future Java stored procedures in the following ways:

Setting system properties.
Attempting to access or modify the security configuration objects.
Loading a native library.

Such actions can impact the ability of other Java stored procedures to use that JVM. For more information about resettable JVMs and for a full list of actions that are prevented, see the "Unresettable actions" topic of the Persistent Reusable Java Virtual Machine User’s Guide.

Recommendation: After you migrate to DB2 10, modify your applications that use functions of resettable JVMs to not run Java stored procedures in resettable JVMs.

DB2-established stored procedure address spaces (starting in DB2 9)

DB2-established stored procedure address spaces are no longer supported. Stored procedures must be moved to a WLM environment.

Recommendation: Before you migrate to DB2 10, modify your DB2-managed stored procedures to be managed by WLM. For more information, see WLM management of stored procedures.

JDBC/SQLJ Driver for OS/390 and z/OS (starting in DB2 9)

The JDBC/SQLJ Driver for OS/390® and z/OS is no longer supported. All Java application programs and Java routines that are currently written to work with the JDBC/SQLJ Driver for OS/390 and z/OS need to be modified to work with the IBM Data Server Driver for JDBC and SQLJ (formerly known as the DB2 Universal JDBC Driver).

All WLM-managed stored procedures address spaces that are set up to execute Java routines must be modified to reference the IBM Data Server Driver for JDBC and SQLJ. Existing WLM environments that are configured to use the JDBC driver fail when the address space initializes. Data sharing groups that have Version 8 or DB2 9 members in coexistence with members in DB2 10 conversion mode (from Version 8 or Version 9) fail if a Java routine is invoked on any DB2 10 members where the WLM-SPAS JCL does not reference the IBM Data Server Driver for JDBC and SQLJ.

Recommendation: Before you migrate to DB2 10, modify your WLM-SPAS JCL to use the IBM Data Server Driver for JDBC and SQLJ.

Creation of simple table spaces (starting in DB2 9)

Simple table spaces that were created in previous releases can still be read and updated. However, you can no longer create simple table spaces. Because DB2 does not support creating new table spaces in DB2 10, it is possible to accidentally drop a simple table space that you cannot recover.

Recommendation: To avoid accidentally dropping a simple table space that you cannot recover, complete one of the following tasks before you migrate to DB2 10:

Issue an ALTER TABLE ... ADD RESTRICT ON DROP statement against tables that are in a simple table space to restrict dropping these simple table spaces.
Convert your simple table spaces.

Connections from VAX machines and the PASCAL L string data type (starting inDB2 9)

For DRDA connections to DB2 for z/OS, the following items are no longer supported:

Connections from VAX machines
The PASCAL L string data type

AIV Extender, Text Extender, and Net Search Extender (starting in DB2 9)

AIV Extender, Text Extender, and Net Search Extender have been removed.DB2 10 incorporates substantial text function into the base product. Use the new functions and indexing for text applications.

Net.Data (starting in DB2 9)

Net.Data® has been removed. WebSphere® is the strategic IBM solution for delivering DB2 data to web applications.

QMF Visionary Studio program (starting in DB2 9)

The QMF™ Visionary Studio program has been removed from QMF Enterprise Edition.

DB2 Estimator (starting in DB2 9)

DB2 Estimator, which was available for download from the web for DB2 Version 8, is not provided for DB2 10.

Visual Explain for DB2 for z/OS (starting in DB2 9)

Visual Explain for DB2 for z/OS, which was available for download from the web for DB2 Version 8, is not provided for DB2 10. Instead, IBM Data Studio for DB2 for z/OS, part of the IBM DB2 Accessories Suite for z/OS, extends the capability of Visual Explain and adds more SQL tuning functions. IBM Data Studio works with both DB2 Version 8 and DB2 10.

DB2 XML Extender

DB2 XML Extender is no longer supported. In DB2 10, you can use the XML data type instead.

DB2 Management Clients feature

DB2 Management Clients feature, which includes DB2 Administration Server, DB2 Control Center, and DB2 Development Center, is no longer supported. Instead, use IBM Data Studio to design, develop, deploy, and manage your data-driven applications.

Several subsystem parameters

The DBPROTCL subsystem parameter is no longer supported. The default for the DBPROTOCOL bind option is DRDA. You can still specify DBPROTOCOL(PRIVATE) explicitly when binding packages and plans, but DB2 issues a warning message if you perform any bind with this value.

The following subsystem parameters have been removed:

EDMBFIT
HOPAUTH
LOGAPSTG
MAX_OPT_ELAP
MAX_UTIL_PARTS
MORE_UNION_DISTRIBUTION
OPTIXOPREF
PARTKEYU
RELCURHL
In DB2 10, the option to hold a lock after commit is eliminated. DB2 always releases the page or row lock for cursor hold at commit, which allows for greater concurrency.
SJMISSKY
STORPROC
SUPPRESS_TS_CONV_WARNING
DB2 10 always operates as if SUPPRESS_TS_CONV_WARNING=NO.
TABLES_JOINED_THRESHOLD

Some supplied routines

The following supplied routines are removed in DB2 10 and are unavailable to callers after migration to conversion mode (from Version 8 or Version 9). 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 Version 10.

DSN8.DSN8EXP
AMI-based DB2 MQ functions
- DB2MQ1C.GETCOL
- DB2MQ1C.MQPUBLISH
- DB2MQ1C.MQREAD
- DB2MQ1C.MQREADALL
- DB2MQ1C.MQREADALLCLOB
- DB2MQ1C.MQREADCLOB
- DB2MQ1C.MQRECEIVE
- DB2MQ1C.MQRECEIVEALL
- DB2MQ1C.MQRECEIVEALLCLOB
- DB2MQ1C.MQRECEIVECLOB
- DB2MQ1C.MQSEND
- DB2MQ1C.MQSUBSCRIBE
- DB2MQ1C.MQUNSUBSCRIBE
- DB2MQ2C.GETCOL
- DB2MQ2C.MQPUBLISH
- DB2MQ2C.MQREAD
- DB2MQ2C.MQREADALL
- DB2MQ2C.MQREADALLCLOB
- DB2MQ2C.MQREADCLOB
- DB2MQ2C.MQRECEIVE
- DB2MQ2C.MQRECEIVEALL
- DB2MQ2C.MQRECEIVEALLCLOB
- DB2MQ2C.MQRECEIVECLOB
- DB2MQ2C.MQSEND
- DB2MQ2C.MQSUBSCRIBE
- DB2MQ2C.MQUNSUBSCRIBE
- DB2MQ1N.GETCOL
- DB2MQ1N.MQPUBLISH
- DB2MQ1N.MQREAD
- DB2MQ1N.MQREADALL
- DB2MQ1N.MQREADALLCLOB
- DB2MQ1N.MQREADCLOB
- DB2MQ1N.MQRECEIVE
- DB2MQ1N.MQRECEIVEALL
- DB2MQ1N.MQRECEIVEALLCLOB
- DB2MQ1N.MQRECEIVECLOB
- DB2MQ1N.MQSEND
- DB2MQ1N.MQSUBSCRIBE
- DB2MQ1N.MQUNSUBSCRIBE
- DB2MQ2N.GETCOL
- DB2MQ2N.MQPUBLISH
- DB2MQ2N.MQREAD
- DB2MQ2N.MQREADALL
- DB2MQ2N.MQREADALLCLOB
- DB2MQ2N.MQREADCLOB
- DB2MQ2N.MQRECEIVE
- DB2MQ2N.MQRECEIVEALL
- DB2MQ2N.MQRECEIVEALLCLOB
- DB2MQ2N.MQRECEIVECLOB
- DB2MQ2N.MQSEND
- DB2MQ2N.MQSUBSCRIBE
- DB2MQ2N.MQUNSUBSCRIBE
MQSeries® publish and subscribe XML routines
- DB2MQ1C.PUBLISHXML
- DB2MQ2C.PUBLISHXML
MQSeries XML routines
- DMQXML1C.DXXMQGEN
- DMQXML1C.DXXMQGENCLOB
- DMQXML1C.DXXMQINSERT
- DMQXML1C.DXXMQINSERTALL
- DMQXML1C.DXXMQINSERTALLCLOB
- DMQXML1C.DXXMQINSERTCLOB
- DMQXML1C.DXXMQRETRIEVE
- DMQXML1C.DXXMQRETRIEVECLOB
- DMQXML1C.DXXMQSHRED
- DMQXML1C.DXXMQSHREDALL
- DMQXML1C.DXXMQSHREDALLCLOB
- DMQXML1C.DXXMQSHREDCLOB
- DMQXML1C.MQPUBLISHXML
- DMQXML1C.MQRCVALLXMLCLOB
- DMQXML1C.MQREADALLXML
- DMQXML1C.MQREADALLXMLCLOB
- DMQXML1C.MQREADXML
- DMQXML1C.MQREADXMLCLOB
- DMQXML1C.MQRECEIVEALLXML
- DMQXML1C.MQRECEIVEXML
- DMQXML1C.MQRECEIVEXMLCLOB
- DMQXML1C.MQSENDXML
- DMQXML1C.MQSENDXMLFILE
- DMQXML1C.MQSENDXMLFILECLOB
- DMQXML2C.DXXMQGEN
- DMQXML2C.DXXMQGENCLOB
- DMQXML2C.DXXMQINSERT
- DMQXML2C.DXXMQINSERTALL
- DMQXML2C.DXXMQINSERTALLCLOB
- DMQXML2C.DXXMQINSERTCLOB
- DMQXML2C.DXXMQRETRIEVE
- DMQXML2C.DXXMQRETRIEVECLOB
- DMQXML2C.DXXMQSHRED
- DMQXML2C.DXXMQSHREDALL
- DMQXML2C.DXXMQSHREDALLCLOB
- DMQXML2C.DXXMQSHREDCLOB
- DMQXML2C.MQPUBLISHXML
- DMQXML2C.MQRCVALLXMLCLOB
- DMQXML2C.MQREADALLXML
- DMQXML2C.MQREADALLXMLCLOB
- DMQXML2C.MQREADXML
- DMQXML2C.MQREADXMLCLOB
- DMQXML2C.MQRECEIVEALLXML
- DMQXML2C.MQRECEIVEXML
- DMQXML2C.MQRECEIVEXMLCLOB
- DMQXML2C.MQSENDXML
- DMQXML2C.MQSENDXMLFILE
- DMQXML2C.MQSENDXMLFILECLOB

EXPLAIN tables in pre-DB2 Version 8 format and EXPLAIN tables in EBCDIC encoding

In DB2 10, EXPLAIN tables in a format earlier thank DB2 Version 8 are no longer supported. Before migration to DB2 10, these tables must be converted to the format of the current (DB2 Version 8 or DB2 9) release. Starting in DB2 10 conversion mode (from either DB2 Version 8 or DB2 9), DB2 returns SQLCODE -20008 for statements or commands that invoke EXPLAIN processing if EXPLAIN tables are in a pre-Version 8 format.

Also in DB2 10, EXPLAIN tables that are encoded in EBCDIC are no longer supported. If an EXPLAIN table is in DB2 10 format and encoded in EBCDIC, SQLCODE -878 is returned. However, for transition purposes, EXPLAIN tables that are in Version 8 or DB2 9 format can be encoded in EBCDIC. Statements or commands that invoke EXPLAIN processing return SQLCODE +20520 reason code 2 if an EXPLAIN table is in Version 8 or DB2 9 format, regardless of the encoding type. For more information about converting your EXPLAIN tables, see Converting EXPLAIN tables (before migration).

Private protocol

The private protocol remote data access method is no longer supported as of DB2 10. DRDA protocol must be used instead. Packages and plans that were bound with DBPROTOCOL(PRIVATE) in a previous release can exist in DB2 10 and might run in DB2 10. If an application that executes packages or plans that were bound with DBPROTOCOL(PRIVATE) only accesses objects that are local to the DB2 subsystem, the application should run successfully. If an application that executes packages that were bound with DBPROTOCOL(PRIVATE) accesses a remote location, the application fails.

REORG TABLESPACE SHRLEVEL NONE on LOB table spaces

In DB2 10 new-function mode, running the REORG TABLESPACE utility with the SHRLEVEL NONE option on a LOB table space is no longer supported. If SHRLEVEL NONE is specified, the utility immediately completes with return code 0 without performing the reorganization. SHRLEVEL REFERENCE or SHRLEVEL CHANGE should be used instead.

INDEXES keyword for REPAIR

The INDEXES keyword of the REPAIR utility is no longer supported. To repair all indexes, specify INDEX(ALL), followed by a table-space-spec.