VisualAge Generator to Enterprise Generation Language Migration Guide
To create the migration database, do the following:
- Make sure that DB2 and any other applications that use it are shut
down. For example, shut down VisualAge Generator and WebSphere
Studio.
- Open a DB2 Command Window.
- If you are migrating from Java, navigate to the
VisualAgeJava-installation-directory\ide\vgmigration
directory.
- If you are migrating from Smalltalk, navigate to the
VisualAge-Smalltalk-installation-directory.
- Run the file named SetupDatabase.bat. This runs a
file in the same directory called createdatabase.sql and saves the
output to a file called createdatabase.out in the same
directory. This creates a DB2 database called VGMIG, connects to the
database, and configures the database parameters. It might take up to a
minute to create the database. Be sure to wait until all the commands
finish executing.
- Note:
-
- The first command that appears in the console might result in an error
message. You can ignore this message. It simply means that the
VGMIG database did not already exist.
- If you want to create a database with a name other than VGMIG, you must
change all occurrences of VGMIG in createdatabase.sql to your desired
database name. You must also remember to change VGMIG in your Stage 1 -
3 migration tool preferences.
- By default the VGMIG database is not password protected. If you
need password protection, you must change the database to be password
protected.
- Run the file named SetupTables.bat. This runs a
file in the same directory called createtables.sql and saves the output
to a file called createtables.out in the same directory. This
creates all the tables and views that the migration tool needs in the
migration database. The tables are crated with a high-level qualifier
(a schema) called MIGSCHEMA. It might take up to a minute to create the
database. Be sure to wait until all the commands finish
executing.
- Note:
-
- The first commands that appear in the console might result in error
messages. You can ignore these messages. They simply mean that
the tables and views did not already exist.
- If you want to create a schema with a name other than MIGSCHEMA, you must
change all occurrences of MIGSCHEMA in createtables.sql to your desired
schema name. You must all remember to change MIGSCHEMA in your Stage 1
- 3 migration preferences.
- If you ever need to completely clean out the migration database, you can
rerun the SetupTables.bat file from a DB2 Command Window.
- Close the DB2 Command Window.
At this point the migration database, schema, tables, and views have been
created. You are now ready to create a preferences file for the Stage 1
migration tool to use. If you are migrating from Java, see Setting Stage 1 preferences. If you are migrating from Smalltalk, see Setting Stage 1 preferences.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.