Migration modes for DB2 9 to DB2 10

Migration from DB2® 9 to DB2 10 new-function mode includes five migration modes. Four of these modes are differentiated from the modes that are part of migration from Version 8 to DB2 10.

The names of the modes during migration from DB2 9 are:

• Conversion mode from Version 9
• Conversion mode* from Version 9
• Enabling-new-function mode from Version 9
• Enabling-new-function mode* from Version 9
• New-function mode

New-function mode is not differentiated by the release from which you are migrating.

Each of the DB2 modes has a corresponding short name that is used in the DB2 output. The short names are also used in some topics to improve readability where multiple mode names are mentioned. The following table shows the short names of the DB2 modes for migration from DB2 9 and the corresponding long names.

To see the current mode of a DB2 subsystem, issue a DISPLAY GROUP command. The output shows the short name for the migration mode. The definition of each mode is as follows:

Conversion mode from Version 9

The state of the catalog after the DB2 10 migration process is complete. In a DB2 data sharing group, members in CM9 can coexist with members that are still in DB2 9. New DB2 10 functions are not available for use in CM9. A subsystem that is in CM9 can fall back to only DB2 9.

Conversion mode* from Version 9

A state that is similar to CM9, but the asterisk (*) indicates that, at one time, the subsystem or data sharing group was in ENFM9, ENFM9* or NFM. You can still access objects that were created in ENFM9 or NFM. Data sharing groups that have a member in this mode cannot have any DB2 9 members. A subsystem that is in CM9* cannot fall back to DB2 9.

Enabling-new-function mode from Version 9

A transitional state that indicates that the DB2 subsystem or data sharing group is in the process of enabling new function. New DB2 10 functions are not available in ENFM9. A subsystem that is in ENFM9 cannot return to CM9, but it can revert to CM9*. A subsystem that is in ENFM9 also cannot fall back to DB2 9 or coexist with a DB2 9 subsystem.

Enabling-new-function mode* from Version 9

A transitional state that is similar to ENFM9, but the asterisk (*) indicates that, at one time, the DB2 subsystem or data sharing group was in NFM. In ENFM9*, you can still access objects that were created in NFM, but you cannot create new objects. A subsystem that is in ENFM9* can revert to CM9*, but it cannot fall back to DB2 9 or coexist with a DB2 9 subsystem.

New-function mode

The state of the catalog after enabling-new-function mode processing is complete and job DSNTIJNF runs successfully. The catalog has been marked as being in new-function mode. All new DB2 10 functions are available in NFM. A subsystem that was migrated to DB2 10 NFM from CM9 can revert to CM9* or ENFM9*. However, the subsystem cannot fall back to DB2 9 or coexist with a DB2 9 subsystem.

The process of migrating from DB2 9 to DB2 10 begins with migration to CM9. From there, you can migrate to ENFM9 and then to NFM.

The flow from one migration mode to another is illustrated in the following figure:

CM9* and ENFM9* are optional modes that you can revert to if you encounter problems in another mode or if you want to temporarily prevent the use of new function.

Starting in DB2 10, data sets for the DB2 catalog and directory are managed by DB2 and must be SMS-managed. The SMS environment that you use for DB2 catalog and directory data sets must be established before you begin migration to DB2 10. The SMS environment must include a data class for allocating the data sets in extended format and using extended addressability. You are not required to convert existing DB2 catalog and directory data sets to the SMS environment before migrating to DB2 10. These data sets will be converted the next time the related table space is reorganized.