VisualAge Generator to Enterprise Generation Language Migration Guide
The migration tool converts VAGen resource association parts to EGL resource
associations parts. However, some VAGen options have no EGL
equivalent. In addition, EGL has several new resource association
options that you might need to set. You might see errors on the Tasks
list due to either of these changes. See IWN.xxx messages on the Tasks list for help in resolving common messages on the Tasks list that are
a result of the migration process. Also refer to the online helps for
details about the resource association options that are supported for your
environment. You need to perform the following steps regardless of
whether you used Stage 1 - 3 migration or single file migration:
- Review and resolve the messages in the migration log and on the Tasks
list. You might need a text editor to resolve some of the
problems.
- Not all of the file types from VisualAge Generator are supported in
EGL. For example, BTRIEVE and MFCOBOL are no longer supported.
The migration tool converts these unsupported options exactly as they are so
that there is a place holder in the resource association part. This
ensures that there is an error on the Tasks list as a reminder that you must
modify the resource associations part to specify the option you want to use
with EGL. Depending on the EGL file type option you select, there might
be additional attributes you must set for the resource association
entry.
- Review the online helps for the FormFeedOnClose and
text attributes to determine if you need to set these values for
your environment. In VisualAge Generator, the equivalent options, /noff
and /text respectively, can only be specified in a resource association file
for the workstation environment. Therefore, these options are not set
by the migration tool because the tool only processes resource association
parts.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.