VisualAge Generator to Enterprise Generation Language Migration Guide
The Mapping page enables you to specify the following:
-
EGL file names for common parts and for unused parts.
-
Suffixes that are used in building EGL project and package names.
- Options that control how your application names are converted to EGL
package names.
-
Information about which VAGen configuration maps and applications contain
common parts.
The following describes the preferences on the Mapping page in more
detail:
- File Names section contains the following:
-
Common Parts enables you to specify the name of an EGL file to
contain parts that are common to multiple unique generatable parts within the
scope of the migration set. Specify the file name without an
extension or path. The migration tool creates a common parts file in
any EGL package that contains parts that are used by (associated with)
multiple generatable parts in the migration set or which are in VAGen
configuration maps or applications that are identified as common configuration
maps or applications. See Placing parts in EGL files for details about whether a part is placed with in a file with a
program or in the Common Parts file.
-
Unused Parts enables you to specify the name of an EGL file to
contain parts that are not used within the scope of the migration set.
Specify the file name without an extension or path. The
migration tool creates an unused parts file in any EGL package that contains
parts that are not used by (associated with) any generatable part in the
migration set, provided the corresponding VAGen configuration map and
application are not identified as common configuration maps or
applications.
-
Spanning Maps section contains the following:
-
Project Suffix enables you to specify a suffix for the Stage 1
migration tool to add to the migration set name to create a new EGL project
name.
The migration tool only creates this new EGL project if a map group and its
maps are spread across multiple VAGen configuration maps within the migration
set. The migration tool adds the suffix to the migration set name
after any Renaming rules are applied.
-
Package Suffix enables you to specify a suffix for the Stage 1
migration tool to add to a project name to create a new EGL package name
within the EGL project. The migration tool only creates this new EGL
package if a map group and its maps are spread across multiple VAGen
applications within a configuration map. The migration tool adds the
suffix after any Renaming rules are applied to create the EGL
project name.
-
EGL Package Naming Options contains the following:
- Use package naming dot notation. If you select this
option, the migration tool converts VAGen application names to EGL package
names by placing a dot before each uppercase letter in the application name
after the first. For example, if you select this option, the migration
tool changes MyOrderEntryApp to
My.Order.Entry.App.
- Convert package names to lowercase. If you select this
option, the migration tool converts VAGen application names to EGL package
names by changing uppercase letters to lowercase. For example, if you
select this option, the migration tool changes MyOrderEntryApp to
myorderentryapp.
In general, you should select both options. If both are selected, the
migration tool changes MyOrderEntryApp to
my.order.entry.app. The EGL Package Naming Options
are applied after any Renaming rules.
-
Common Identifiers. This section enables you to specify a
list of strings with wildcards that the migration tool can use in determining
which configuration maps and applications contain common parts. To add
or delete a common identifier, right click on the field and use the options on
the context menu. When you add an identifier, the editor prompts you to
enter the following information:
- context indicates whether the string is to be matched to the
configuration map name, application name, or both.
-
ConfigMap enables you to specify a string that identifies
configuration maps that contain common parts. The migration tool
matches this string to each configuration map name in the migration set to
determine if the configuration map contains common parts. If the
configuration map name matches any of the strings, all parts within the
configuration map are considered to be "used". Each part will either be
placed in a program file or in the file specified by your Common Parts File
Name preference; the part will not be placed in the unused parts file
even if the part is not used by any generatable part in the migration
set. You can enter multiple ConfigMap strings.
- Application enables you to specify a string that identifies
applications that contain common parts. The migration tool matches this
string to each application name in the migration set to determine if the
application contains common parts. If the string matches an application
name, all parts within the application are considered to be "used".
Each part will either be placed in a program file or in the file specified by
your Common Parts File Name preference; the part will not be placed in
the unused parts file even if the part is not used by any generatable part in
the migration set. You can enter multiple Application
strings.
- Both enables you to specify a string that the migration tool
matches to both configuration map names and application names within the
migration set. Both is equivalent to specifying the same
string with a context of ConfigMap and a context of
Application.
-
Pattern to identify the common code enables you to specify the
string the migration tool should match based on the context you
specified. You can use the * as a wildcard at either the beginning or
end of the string.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.