Migrating database applications
You have three options for migrating work that uses a database feature:
Database Manager menu choice
Use this option to migrate the following:
• Native DB2 support to CLI
• The database manager IBM DATABASE2 has been discontinued and replaced by IBM DB2-CLI. If you have connection specs which use IBM DATABASE2, you must complete this step for migrating native DB2 support to CLI.
• Multi-Database applications to ODBC support (or for ORACLE, to native ORACLE support)
• An application to a new manager if you changed the connection alias so it points to a different database manager.
Database Access Set Runtime menu choice
Use this option to add universal fields to your database application. This is required for all Version 3.0 database applications.
Dynamic to Static menu choice
Use this option to migrate a DB2 CLI application with universal fields to a Static DB2 application.
The option(s) you choose, depend on the database your Version 3.0 application supports and the database you want your current VA Smalltalk application to support. You may need to use more than one option. For example, if you are migrating a Version 3.0 native DATABASE2 application to Static DB2, use all three options sequentially:
1. Use the Migrate > Database Manager choice of the Organizer's Applications menu to migrate native DATABASE2 code to DB2 CLI.
2. Use the Migrate > Access Set Runtime choice of the Organizer's Applications menu to add support for universal fields to the DB2 CLI code.
3. Use the Migrate > Applications menu of the Organizer. choice of the Applications menu to migrate the DB2 CLI code with universal fields to Static DB2.
The materials below describe how to use the three options.
Last modified date: 07/02/2019