The tool that performs Stage 2 of the migration can be invoked through a wizard. To prepare for Stage 2, create a project where you can optionally save Stage 2 preferences for later use. To create the Stage 2 migration preferences, do the following:
Figure 56. Preferences to enter on first page of wizard
Figure 57. Preferences to enter on second page of wizard
Preference
| Meaning | Value |
---|---|---|
Java or COBOL radio button | This choice determines whether the migration tool creates projects that include Java Source folders. |
If you are using WebSphere Studio Site Developer or WebSphere Studio Application Developer, you should always select the Java radio button. For other WebSphere Studio projects, you can select COBOL if you only plan
to generate COBOL and you plan to run migration in online
mode. Selecting COBOL for batch migration can result in projects that
do not have the required EGL properties and which are thus not usable.
|
Migrate remaining VAGen parts | This determines whether or not parts not referenced by any generatable part in the migration set will be converted to EGL. | Select the box to convert unreferenced parts to EGL. Generally, you should select Migrate remaining parts. If you do not select Migrate remaining parts, control parts and any other parts that are unused within the migration set will not be migrated to EGL source. |
Import into workspace | This determines whether or not Stage 3 (importing EGL into files in the
current workspace) will be automatically started after Stage 2 is
complete.
| Select this box to import EGL files directly after the conversion of
parts to EGL. Leave this box unselected to import files later, during
Stage 3.
|
Latest version | This specifies that the latest version of the desired migration sets should be imported. | This option can only be selected if the Import into workspace checkbox is selected. |
Oldest version | This specifies that the oldest version of the desired migration sets should be imported. | This option can only be selected if the Import into workspace checkbox is selected. |
Override existing files | Stage 3 (the import process) uses EGL produced by Stage 2 to create and import the EGL files specified in the Stage 1 report. If EGL files with the same names as the EGL files that Stage 3 is about to import already exist in the workspace, this option determines whether or not those files will be overwritten. | This option can only be selected if the Import into workspace checkbox is selected. Override existing files enables you to specify how you want the Stage 3 migration tool to handle the situation in which the migration set you are currently migrating contains parts that should be placed in a file that is already in your workspace. If you select Override existing files, the Stage 3 migration tool replaces the existing file and includes only those parts that are in the current migration set. If you do not select Override existing files, the Stage 3 migration tool merges any new parts into the existing file. The new parts are placed alphabetically by part type. See Overwriting and merging files for a more complete discussion of the effects of this option. |
Save migrated files to temporary directory | This provides the option to save EGL files to a location in the file system. This allows you to access EGL files for multiple versions of a project at the same time (whereas you can only see one version at a time in the workspace). You can move EGL files directly from here to your repository. | If you plan to migrate multiple versions of a migration set, then do the
following:
|
Folder | This is the directory in which you want to save EGL files. Each migration set version becomes a subdirectory under the directory you specify for Folder. | Specify an existing directory in your file system. |
Migrate Now | This specifies that you want Stage 2 to run at this time, rather than just setting up the preferences file to migrate at a later time. | You must select either Migrate Now to run Stage 2 in online mode or Save current configuration to file to save your preferences so that you can run Stage 2 in batch mode at a later time. You can select both options if you want to retain a copy of your preferences for later reference. Do not select Migrate Now if you have already selected Save migrated files to temporary directory. Saving to a temporary directory can only be done in batch mode. Selecting Migrate Now indicates that you want to migrate in online mode. |
Save current configuration to file | This allows you to save the preferences you are specifying in the wizard
to a file. You can later run Stage 2 again with the saved preferences
by right-clicking on the saved file and selecting Start Migration
from the context menu.
| You must select either Migrate Now to run Stage 2 in online mode or Save current configuration to file to save your preferences so that you can run Stage 2 in batch mode at a later time. You can select both options if you want to retain a copy of your preferences for later reference. If you select this option you must also specify the Path and File Name where the current configuration is to be saved as a .vgmig file. When you run Stage 2 in batch mode, point to the saved .vgmig file to specify your migration preferences. |
Path | This specifies the project into which the file should be saved. | \projectName, where projectName is the name of the project that you want to contain your saved file. |
File Name | This specifies the name of the file to which preferences will be saved. | fileName, where fileName is the desired name for your file WITHOUT a file extension. The extension .vgmig will automatically be appended for you. |
The combinations of the check boxes that you select determine the actions that are performed by the wizard:
Here is an example of a Stage 2 preferences file, stage2.vgmig:
databaseDriverLocation=d:\SQLLIB\java\java\db2java.zip databaseDriver=COM.ibm.db2.jdbc.app.DB2Driver databaseName=jdbc:DB2:VGMIG databaseSchema=MIGSCHEMA databaseUserid=myuserID databasePassword=encoded:AAEDAwQFBwYKCwo+Pw== configurationPlan=MyMigrationSetA,1.1 migrateRemainingParts=yes workspaceImport=latest overrideExistingFiles=yes tempDirectory= logFileLocation=D:\tempmig\MyMigrationSetA\stage2\MyMigrationSetA.log migrateNow=yes projectType=COBOL
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.