DB2 & IMS

You should also be aware of the removal of the AIV Extender, Text Extender, and Net Search Extender, along with Net.Data, effective with DB2 9.

If planning a skip-level migration, you should reformat the Boot Strap Data Set (BSDS) and be aware of the removal of DB2 managed stored procedures and the deprecation of simple table space.

As of DB2 9, Partitioned Data Set Extended (PDSE) is required for certain target and distribution libraries in addition to a few SMP/E libraries.

There are four DB2 target and distribution libraries that must use PDSE in DB2 9 and DB2 10. This change affects you if you’re performing a skip-level upgrade from DB2 V8 to DB2 10. The change is already part of a DB2 V8 to DB2 9 migration. The four data sets are ADSNLOAD, ADSNLOD2, SDSNLOAD, and SDSNLOD2. Everything that must be completed is documented in the DB2 10 Installation and Migration Guide (GC19-2974).

With every new version, new DSNZPARM keywords are introduced, defaults and maximums are changed, and some keywords are eliminated. You will want to note the DSNZPARM keywords that are eliminated. Determine if whatever action the ZPARM controls is being eliminated by the next version of DB2 or if it’s becoming part of the product. If something you use is going away, or something you choose not to use is becoming part of the product, determine how that will affect you and plan appropriately.

When upgrading from V8 to DB2 9, some subsystem parameters—MAX_OPT_ELAP, MORE_UNION_DISTRIBUTION, RELCURHL, STORPROC, SUPPRESS_TS_CONV_WARNING, and TABLES_JOINED_THRESHOLD—will be removed. If migrating to DB2 10 from DB2 9, EDMBFIT, LOGAPSTG, MAX_UTIL_PARTS, OPTIXOPREF, PARTKEYU, and SJMISSKY are removed. If a skip-level migration is performed, all the ZPARMs listed previously will be removed. To learn more, refer to “A First Look: DB2 10 DSNZPARM Changes” in the June/July 2011 z/Journal.

Summary

If you’ve been avoiding using DFSMS with DB2 for z/OS, you can’t do so anymore. The DB2 10 catalog and directory must be DFSMS-managed. The SMS environment the DB2 catalog and directory uses must be established before you can begin a migration (or installation) to DB2 10. This is one more migration task you can complete before your actual DB2 10 migration begins. For more information, see “The DB2 Catalog Gets a Makeover” in the December/January 2011 z/Journal.

Regardless of your migration timetable, there are steps you can take to prepare. PM04968 supplies the DB2 10 DSNTIJPM routine to DB2 V8 and DB2 9 as job DSNTIJPA. DSNTILPA can be used to check out DB2 9 and DB2 V8 to ensure they’re suitable for use with DB2 10 for z/OS. The APARs cover all the details about DSNTIJPM. Running this one routine can have a significant effect on the success of your DB2 10 migration.

Education is important, too. Build your DB2 10 and DB2 migration skills as soon as possible. Start by downloading the DB2 10 product documentation from the Web. For example, www.ibm.com/support/docview.wss?uid=swg27019288 points to the DB2 10 product library in PDF format (BookManager is no longer supported in DB2 10) and provides links to the Information Center on the Internet. The Information Center contains DB2 product documentation for all active versions in one place. It’s easy to search and easy to read and is an excellent place to get DB2 for z/OS information.

There’s also a free, one-day DB2 Migration Workshop available from IBM. It’s a terrific way to get ready for a DB2 10 migration. Contact your IBM DB2 specialist for information.

If you want to verify that your DB2 is ready to migrate to DB2 10, information is abundantly available. A little planning and pre-migration cleanup can make for a smooth DB2 10 migration.

2 Pages