VisualAge Generator to Enterprise Generation Language Migration Guide
- If you migrate multiple migration sets or migration set versions without
clearing out the migration database, the first migration set version that
contains a part edition controls the project, package and file name for the
EGL part. This generally does not cause a problem if the following are
true:
- If your parts do not move between Java packages and you do not have
differently named migration sets that include the same Java package
name.
- If your parts do not move between Smalltalk applications and you do not
have differently named configuration maps that include the same Smalltalk
applications.
If your situation differs from what is described above, the workaround is
to migrate one migration set version all the way through Stages 1 - 3, then
clear out the migration database, and then migrate the next migration set
version all the way through Stages 1 - 3.
- If you plan to use a remote DB2 database for the migration database, be
sure to run a very small pilot test of Stage 1 through 3 to ensure that you
are able to access the remote database from Stages 2 and 3.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.