VisualAge Generator to Enterprise Generation Language Migration Guide
The Renaming page enables you to specify renaming rules for your projects,
packages, and version names. The Renaming Rules section
enables you to control the names of the EGL projects and packages that are
derived from your VAGen project and package names. The number in the
order column indicates the order in which the Stage 1 migration tool is to
apply the renaming rules, with the lowest numbered rule applied first.
To add or remove a renaming rule, use the Add and Remove push buttons.
To update a renaming rule, overtype the contents of the cells in the
table. You can double-click on any of the column headings to sort the
rules based on that column. You specify a rule by specifying the
following information:
- order specifies the order in which the rules are to be
applied.
- From String specifies the characters in the VAGen name that you
want to change.
- To String specifies the characters you want to use in the
resulting EGL name.
- String Context specifies the location in the VAGen name where
the migration tool should look for the from string during renaming. The
values are as follows:
- front means the rule applies if the from string appears at the
beginning of a project, package, or version name.
- back means that the rule applies if the from string appears at
the end of a project, package, or version name.
- any means that the rule applies if the from string appears
anywhere within a project, package, or version name.
- token means that the rule applies only if the from string is an
exact match for the project, package, or version name.
-
Mapping Context indicates whether the migration tool is to apply
the renaming rule to a project, package, or version name. The values
for Mapping Context are as follows:
-
project means that the renaming rule only applies to VAGen project
names.
-
package means that the renaming rule only applies to VAGen package
names.
- both means that the renaming rule applies to both VAGen project
names and VAGen package names.
-
version means that the renaming rule applies to the version names
for all project names. Use a version renaming rule if your version
names include special characters such as a semicolon (:) that are not
permitted in directory or file names. The default
MigPreferences.xml file includes several version renaming
rules to help ensure that your version names do not result in invalid
directory or file names. The migration tools use the renamed versions
to create the migration plan file name (or names) in Stage 1 and to create
directory names in Stage 3 of migration.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.