VisualAge Generator to Enterprise Generation Language Migration Guide
The Renaming page enables you to control the names of the EGL projects and
packages that are derived from your VAGen configuration map and application
names. The number in the Order column indicates the order in which the
migration tool is to apply the renaming rules, with the lowest numbered rule
applied first. To add or delete a renaming rule, click on a rule and
use the options on the context menu. Add Rule always puts the new rule
at the end of the list. When you add a rule, the editor prompts you to
enter the following information:
- 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 configuration map, application, or version name.
- back means that the rule applies if the from string appears at
the end of a configuration map, application, or version name.
- any means that the rule applies if the from string appears
anywhere within a configuration map, application, or version name.
- token means that the rule applies only if the from string is an
exact match for the configuration map, application, or version name.
-
mapping context indicates whether the migration tool is to apply
the renaming rule to a configuration map, application, or version name.
The values for mapping context are as follows:
- configMap means that the renaming rule only applies to VAGen
configuration map names.
- application means that the renaming rule only applies to VAGen
application names.
- both means that the renaming rule applies to both VAGen
configuration map names and VAGen application names.
-
version means that the renaming rule applies to the version names
for all configuration maps. 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 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.