These preferences apply to the management of the difference
templates between the Pacbase and
the local generation. Difference templates are character strings that
are deleted or added in the local code. They have no impact on the
functional code. Difference templates and regular expressions are
grouped into validation types. The regular expressions apply to the
difference templates or directly to the differences (entire code lines
with a difference). You can specify migration options for each validation
type.
As it is running, the migration help writes records in
a file that contains the difference templates between the Pacbase generation and the
local generation. The complete file path is displayed in the Template
file field. By default, this file is named DifferenceBank.xml and
is generated in the .metadata directory of your
workspace. You can modify its name or path by clicking Browse.
This
file is required to validate the migration. If you did not keep it
after the migration, you can rebuild it by clicking
Rebuild
the template file. It will be created again in the complete
file path that is indicated in the
Template file field.
Note: This
file is generated in your workspace, so it is not stored on the Rational Team Concert™ server.
You must then copy or rebuild it to validate the migration from a
workspace that is not the migration workspace. If several persons
complete the migration for various projects, the contents of their DifferenceBank.xml file
differ and cannot be merged.
Predefined validation types
are provided in the validation.xml file. These
types can be customized.
The validation.xml file
that contains the predefined types is under the root of the installation
directory of your Rational® Software
Delivery Platform, under rpp/migration. If the
validation types have already been customized in your company, you
must know where to find this customized file. If you started the migration
with the --validationFile parameter, the file that
is specified in this parameter is copied to the .metadata directory
of the local workspace and is recognized by the validation preferences.
If you did not start the migration help with the
--validationFile parameter,
you must explicitly call the file that contains the validation types.
To do so, click
Import and select the complete
file path. The list of the validation types are then displayed in
the table of the preferences. This table contains the following columns:
- The first column contains the validation type ranking number.
This number is useful to spot the validation type upon the migration
validation.
- The Name column explains the validation
type.
- The Warning column indicates whether the
warnings that correspond to the validation types will be displayed
in the Problems view. By default, they will
not be displayed.
- The Migration choice column indicates whether
the local code will be kept (default option) or replaced by the Pacbase code upon the migration
validation.
You can complete the following actions on the validation
types:
- Modify the related options. Select a validation type and select Edit.
Modify the options in the wizard that opens then.
- Add a validation type. Click Add and indicate
the options for this new validation type in the wizard that opens
then. You must be an expert to complete this task because it can cause
migration problems.
- Remove a validation type. Select a type and click Remove.
You must be an expert to complete this task because it can cause migration
problems.
- Change the order of the validation types. Select a type and move
it up or down by clicking the corresponding button. If you do not
click OK, the initial line numbers are kept.
You can then easily revert to the initial order. Changing the order
of the lines is not advised because a difference template can be associated
with only one validation type. If it is associated with more than
one validation type, it is taken into account in the first one only.
If you click OK, the numbers are automatically
recalculated according to the new positions in the table.
When you click OK, the regular
expressions are controlled. If an expression is incorrect, an error
message gives details about the error and prevents you from saving
if the error is not corrected.
When you save, all the generated
COBOL files of your workspace are analyzed and migration warnings
are set or not set in the Problems view, depending
on the preference choice. You can run this task in the background
or cancel it
When the task is complete, the recalculated warnings
of the migration help are displayed in the Problems view.
You can analyze them and remove them to migrate the files.
You
can manage the warnings directly in the Problems view.
You can also manage them in a more automatic way in the Validation
Manager view. To open this view, select .
To make the customized validation.xml file
available, click Export.