Execution Options. The Execution Options section enables
you to specify what you want the Stage 1 migration tool to do.
Generate report specifies that you want to create a migration
report showing where each part will be placed in the EGL project, package and
file structure. This report is useful for reviewing the results of
preferences you specified for Common Parts and Unused Parts file names,
Spanning maps suffixes, Common Identifiers for projects and packages, and your
renaming rules. If you select Generate report, the migration tool
creates the report in the drive, directory and file you specify for the Report
file name in the Verification section.
Update database specifies that you want the Stage 1 migration tool
to store the migration plan information, including the External Source Format
for your parts, into the migration database.
You might run the Stage 1 migration tool in several steps as follows:
Step 1 -- Deselect both Generate report and Update database. This
enables you to review the migration plan files that are created an ensure that
your Repository Filters are set correctly and will process the project
versions that you want. If you are not satisfied with the project
versions that are being selected, you can refine your Repository Filters and
run this step again until you are satisfied with the project versions that the
migration tool will process.
Step 2 -- Select only Generate report. This enables you to review the
report that shows how your VAGen projects, packages, and parts will be
assigned to EGL projects, packages, and files during migration. If you
are not satisfied with the placement of parts, you can refine your Mapping and
Renaming rules and run the report again until you are satisfied with the
placement of parts.
Step 3 -- Select both Generate report and Update database. This
provides you with a final report that records the information that is stored
in the migration database.
Note:
Generating the report can take some time. Therefore it is best to
review the .pln files to be sure that the migration tool will process
the project versions that you intend.
The report files are overwritten if a report is generated. If you want
to save previous report files, you must move the report files to a different
directory or point to a new directory for your new report. Because the
report files link to other files, renaming the report files will cause the
links to be lost so the files are no longer viewable.
Database. The Database section enables you to specify
details about the migration database:
Database driver. This value should always one of the
following:
COM.ibm.db2.jdbc.app.DB2Driver
if you are using a local database.
COM.ibm.db2.jdbc.net.DB2Driver
if you are using a remote database.
Database name. This value should always be one of the
following:
jdbc:DB2:databaseName if you are using a local
database.
jdbc:nodeName:databaseName if you are using a
remote database.
Note:
In both cases, databaseName is the name of the migration database
into which the migration tool is to write the migration set
information. By default, the databaseName is VGMIG. 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. By default, the schema name is MIGSCHEMA. 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 your logon user ID. If this attempt fails, 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 your logon password. If this attempt fails, 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. The Service 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. Use the drop-down list to specify
one of the following values:
Fatal error messages are logged. If any of these messages
occur, the migration database might be updated, but the migration plan file
(.pln file) is not changed to have the .done file
extension. This enables you to reprocess the .pln file.
Warning messages, as well as fatal error messages are
logged.
Informational messages, as well as warning and fatal error messages
are logged.
Debug information, as well as informational, warning, and fatal
error messages are logged. DEBUG is the only trace level that causes
the migration tool to write information to the debug file.
The Trace level only affects the log and debug files. All the messages
are written to the Console window.
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, the migration tool writes the log information to a file
named miglog.xml in the drive and directory that you
specified in the Log file name field. If you do not specify a Log file
drive and directory, the migration tool writes the log file to the working
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, the migration tool
writes the debug file information to a file migdebug.xml in
the drive and directory that you specified in the Debug file name
field. If you do not specify a Debug file drive and directory, the
migration tool writes the debug file to the working directory.
Verification.
The Verification section enables you to specify the drive, directory, and file
name for the verification report that is produced when you select the Generate
report preference in the Execution Options section. If you select
Generate report, you must enter a Report file name. You
should always specify the .htm extension. If you do not specify
a drive and directory, the migration tool writes the report file to the
working directory.