VisualAge Generator to Enterprise Generation Language Migration Guide
The Execution page enables you to specify information about the location of
the migration database, as well as the logging, debug, and report information
you want to capture during Stage 1. The following describes the
preferences you can specify on the Execution page in more detail:
- Database information. This section enables you to
specify details about the migration database:
-
DB is the name of the migration database into which the migration
tool is to write the migration set information. If you changed the
database name from VGMIG when you created the migration database, you must
change the database name specified by this preference to match the name you
used.
-
Schema is the name used as the qualifier for the database
tables. If you do not specify the schema, the migration tool uses
MIGSCHEMA as the default. If you changed the schema name from MIGSCHEMA
when you created the migration database, you must change the schema name
specified by this preference to match the name you used.
-
Userid is the user ID needed to connect to the migration
database. If you not specify the Userid, the migration tool attempts to
connect using the user ID specified in your VAGen SQL Preferences as the
default. If the connection fails, the migration tool attempts to use
your logon user ID. If both attempts fail, the migration tool displays
a dialog window asking for the information.
- Password is the password needed to connect to the migration
database. If you not specify the password, the migration tool attempts
to connect using the password specified in your VAGen SQL Preferences as the
default. If the connection fails, the migration tool attempts to use
your logon password. If both attempts fail, the migration tool displays
a dialog window asking for the information.
- Note:
- The password is not encrypted in the preferences file. If this is a
concern, do not enter the password in the preferences file. Wait for
the prompt.
- Service information. This section enables you to specify
details about the logging and debug information you want to capture during
Stage 1. You can specify the following:
-
Trace Level enables you to specify the level of information that
you want to write to the debug file. You can specify one of the
following values:
-
FATAL (Level 1) -- Error messages are logged.
-
WARN (Level 2) -- Warning messages and error messages are
logged.
-
INFO (Level 3) -- Informational, warning, and error messages are
logged.
-
DEBUG (Level 4) -- Debug information, as well as informational,
warning, and error messages are logged. DEBUG is the only trace level
that causes the migration tool to write information to the debug file.
-
Log File Name enables you to specify the drive, directory, and file
name for a log file. You can create the log file with any file
extension, but it is best viewed as an .xml file. If you omit
the log file name, a file named migLog.xml is written to the
drive and directory that you specified in the Log File Name field. If
you do not specify a drive and directory, the migration tool writes the log
file to the migration plan directory.
- Debug File Name enables you to specify the drive, directory,
and file name for a debug file that might be needed by IBM support. You
can create the debug file with any file extension, but it is best viewed as an
.xml file. Information is only written to this file if the Trace
Level preference is set to DEBUG. If you omit the debug file name and
you specify a Trace Level of DEBUG, a file named
migDebug.xml is written to the drive and directory that you
specified in the Debug File Name field. If you do not specify a drive
and directory, the migration tool writes the debug file to the migration plan
directory.
-
Verification information. This section enables you to
specify information about the report file that can be output from the Stage 1
migration tool. You can specify the following:
-
Report File Name enables you to specify the drive, directory, and
file name to be used for the report file. This report contains
information about how your VAGen files are going to be migrated. You
can create the report file with any file extension, but it is best viewed as a
.htm file. If you omit the report file name, a file named
report\MigrationReport.xml is written to the drive and
directory that you specified in the Report File Name field. If you do
not specify a drive and directory, the migration tool writes the report file
to the migration plan directory.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.