Migrating your DB2 subsystem to conversion mode (from Version 8 or Version 9)

Before you migrate to DB2 10 conversion mode (from Version 8 or Version 9), you must have a maintenance level on Version 8 or DB2 9 that contains the fallback SPE, and you must start the subsystem that you are migrating at least once with the fallback SPE applied. If you do not start your Version 8 or DB2 9 subsystem at least once with the fallback SPE applied, your DB2 10 migration process will fail.

If you are migrating from Version 8, ensure that the BSDS has been converted to the new format. To convert to the new format, you can use the DSNJCNVB utility.

When you start DB2, the code level of the starting DB2 is compared to the code level that is required by the current DB2 catalog. If the starting DB2 has a code-level mismatch with the catalog, DB2 does not start and a message is issued.

Refer to the DB2 Program Directory for keyword specifications that are used for Preventive Service Planning (PSP) and for information about the service levels of any coupling facilities. You can use the z/OS DISPLAY CF command to display the service level of coupling facilities. Check Information/Access or the ServiceLink facility of IBMLink for PSP information before you migrate. Or, to help you identify required service, you can instead use enhanced HOLDDATA and fix categories (FIXCATs), which provide a simplified, automated method of identifying and applying missing PTFs that are required for installation or migration. Also check monthly for current information about DB2.

Restriction: After migration to conversion mode (from Version 8 or Version 9), the administrative task scheduler is disabled until you run job DSNTIJRT.