VisualAge Generator to Enterprise Generation Language Migration Guide
The migration tool converts VAGen linkage table parts to EGL linkage
options parts. However, some VAGen options have no EGL
equivalent. In addition, EGL has several new linkage 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 linkage 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.
- For callLink, consider the following:
- Not all of the link types from VisualAge Generator are supported in
EGL. For example, CSOCALL is no longer supported. The migration
tool converts CSOCALL to a remoteCall. However, the attributes you must
specify for an EGL remoteCall differ from those for CSOCALL.
- Not all of the remoteComType values from VisualAge Generator are supported
in EGL. For example, DCE and DCESECURE are no longer supported.
The migration tool converts these unsupported values exactly as they are,
which results in an invalid EGL linkage options part. This ensures that
there is an error on the Tasks list as a reminder that you must modify the
linkage options part to specify the option you want to use with EGL.
- If you change to use remoteComType=CICSECI, you must add the
ctgPort and ctgLocation attributes. This does
require the configuration and setup of a CICS Transaction Gateway server for
the invocation of remote CICS transactions.
- If you change to use remoteComType=CICSSSL, you must add the
ctgKeyStore and ctgKeyStorePassword attributes.
In addition, if you have not already included the ctgPort and
ctgLocation attributes in your VAGen linkage table, you must
include them for the EGL remoteComType=CICSSSL.
- conversionTable=BINARY is not supported in EGL. The migration tool
converts this value exactly as it is so that there is a place holder in the
EGL linkage part. However, you must modify the value.
- For fileLink, conversionTable=BINARY is not supported in EGL. The
migration tool converts this value exactly as it is so that there is a place
holder in the EGL linkage part. However, you must modify the
value.
- For asynchLink (VAGen crtxlink), conversionTable=BINARY is not supported
in EGL. The migration tool converts this value exactly as it is so that
there is a place holder in the EGL linkage part. However, you must
modify the value.
- The EGL Transfer To Program linkage information is the equivalent of the
VAGen dxfrlink entry. If you generate for Java and use the VAGen XFER
statement, you might need to add EGL Transfer to Transaction entries.
Refer to the online helps for information about this new linkage entry.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.