VisualAge Generator to Enterprise Generation Language Migration Guide
In VisualAge Generator, control parts are entered using a free-form text
editor. The control parts are not validated until they are actually
used during generation. Whether something is in upper or lower case is
not significant. In EGL, control parts are stored in .eglbld
files in XML notation, with a special editor for each type of control
part. In EGL, upper and lower case are significant.
The tables in this section compare the information you enter in the VisualAge
Generator free-form text editor with the XML tag or attribute value that is
used in EGL. The tables only show the tag or attribute values, not the
actual XML syntax.
- Note:
-
-
Where possible, the migration tool migrates generation options, linkage table
options, and resource association options for runtime environments that are
not supported at this time, but which are currently planned for
support. This preserves as much of your information as possible in as
useful a way as possible. For example, most IMS generation options are
migrated even though IMS is not a currently supported runtime
environment. These options are not displayed when you use the normal
EGL Build Part Editor. However, you can see the options if you open the
file with the Text Editor.
- The migration tool includes as comments those generation options, linkage
table options, and resource association options that have no corresponding EGL
replacement but which might be useful to you in determining related
information that is required for EGL. For example, the /MFSDEV
generation option that is used for the IMS environment cannot be migrated at
this time. The migration tool includes the option as a comment to
preserve the information for future use. These comments are not
displayed when you use the normal EGL Build Part Editor. However, you
can see the comments if you open the file with the Text Editor.
-
The migration tool eliminates generation options that have no corresponding
EGL replacement if the information is not useful in determining current or
future EGL options. For example, there is no replacement for
/lineinfo, which was an option to assist IBM support in debugging
the VAGen generator. This option is not useful for the EGL generator,
so the migration tool does not include it as a comment.
-
The migration tool does not rename control parts. The tool issues an
error message of the part name conflicts with an EGL reserved word.
The control parts section is organized into the following tables:
- General control part information, Figure 120
-
Generation options, Figure 121
- Generation options - conversion table values, Figure 122
- Linkage table options for :calllink, Figure 123
- Linkage table options for :filelink, Figure 124
- Linkage table options for :crtxlink, Figure 125
- Linkage table options for :dxfrlink, Figure 126
- Resource association, Figure 127
- Link edit options, Figure 128
- Bind control, Figure 129
Figure 120. General control part information
VisualAge Generator 4.5
| EGL produced by the migration tool
| Migration tool considerations
|
VAGen control part names:
- Can include the period (.) in the name.
- For bind and linkedit parts, any portion of the name after the first
period is treated as a suffix. The suffix can be specified in the /bind
and /linkedit generation options.
| EGL build parts:
- The period (.) is not valid in a build part name.
| The migration tool changes the period (.) to an underscore
(_).
|
Upper and lower case are not significant in VAGen control part tags and
values.
| Upper and lower case are significant in EGL control part tags and
values.
| The migration tool converts the control part tags and values to the
correct case required for EGL.
|
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.