VisualAge Generator to Enterprise Generation Language Migration Guide
The preferences listed below control the migration of the VAGen syntax to
the EGL syntax. Unless otherwise noted, these preferences are used in
Stage 2 for both a Stage 1 - 3 migration and for single file migration.
To set these preferences, from the Workbench window, select Window ->
Preferences -> VAGen Migration -> VAGen Migration Syntax
Preferences.
-
Renaming preferences
-
Renaming Prefix. The migration tool uses this prefix
whenever a VAGen data item, record, function or map name is an EGL or SQL
reserved word or starts with the # symbol. The tool adds the Renaming
Prefix to the VAGen part name to create a valid EGL part name. For
example, date is an EGL reserved word. If you have a function named
DATE and use the default Renaming Prefix of VAGen_, then the migration tool
changes the function DATE to VAGen_DATE. The tool also changes all
references to the function from DATE to VAGen_DATE. You can set the
Renaming Prefix to any value that you want other than blank or EZE. In
addition, the Renaming Prefix cannot start with the # symbol. Be sure
to select something that will not cause conflicts with any of your part
names.
-
Level77 Suffix. The migration tool uses this suffix whenever
a VAGen working storage record contains level 77 items. EGL does not
support level 77 items. The migration tool splits the VAGen working
storage record into two EGL records. The first record is named the same
as the original VAGen working storage record and contains all the non-level 77
items. The second record contains all the level 77 items. The
migration tool names this second record based on the original working storage
record name concatenated with the Level77 Suffix. For example, if the
original working storage record is named MYRECORD and you use the default
Level77 Suffix of _Level77Items, the EGL record that contains the level 77
items will be named MYRECORD_Level77Items. You can set the Level77
Suffix to any value that you want other than blank. However, be sure to
select something that will not cause conflicts with any of your part
names.
-
Help Map Suffix. The migration tool uses this suffix
whenever the main map group and the help map group for a program have maps
with the same name. EGL requires that all forms in both form groups for
a program have unique names. The migration tool renames maps in the
help group that conflict with map names in the main map group. Consider
the following example. The main map group for a program is MAPGP1 and
contains MAP1. The help map group for the same program is MAPGP2 and
contains MAP1. Using the default Help Map Suffix of _helpmap, the
migration tool renames the MAP1 in MAPGP2 to be MAP1_helpmap. You can
set the Help Map Suffix to any value that you want other than blank.
However, be sure to select something that will not cause conflicts with any of
your part names.
-
SQL preferences
-
Result Set Suffix. In VisualAge Generator, when an SQL
REPLACE function needs to reference the corresponding UPDATE or SETUPD
function, the REPLACE function must specify the function name. In EGL,
multiple I/Os are supported within a single function. A result set ID
is used to uniquely identify a get or open statement. The migration
tool creates the result set ID from the function name by concatenating the
Result Set Suffix. For example, if there a function is named MY-SETUPD
and you use the default Result Set Suffix of _RSI01, then the result set ID
that is included in the open statement for the function will be
MY-SETUPD_RSI01. You can set the Result Set Suffix to any value that
you want other than blank. However, be sure to select something that
will not cause conflicts with any of your part names.
-
Prepare Suffix. In VisualAge Generator, if you need to have
an SQL I/O statement prepared at runtime, you select Execution Time Statement
Build. The corresponding EGL statement is the prepare
statement. The prepare statement includes a prepare statement ID so
that other I/O statements such as close, get, execute, and open can specify
which prepare statement they are associated with. The migration tool
creates the prepare statement ID from the function name by concatenating the
Prepare Suffix. For example, if there is a function named
MY-EXEC-TIME-BUILD and you use the default Prepare Suffix of _PREP01, then the
prepare statement ID that is included in the prepare statement is
MY-EXEC-TIME-BUILD_PREP01. You can set the Prepare Suffix to any value
that you want other than blank. However, be sure to select something
that will not cause conflicts with any of your part names.
-
Data Items preferences
- Convert shared data items to primitive item definition.
If you select this preference, then whenever shared data items are used in
records, tables, function local storage, function parameter lists, or program
parameter lists, the migration tool converts the shared items to primitive
item definitions. If you have current organization standards that
discourage the use of shared data items in new applications, this option
enables you to remove the use of shared data items from existing applications
as you migrate.
- Include shared data items in EGL file. This option is
preselected. The shared data items are always included in the EGL
file.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.