VisualAge Generator to Enterprise Generation Language Migration Guide
- Note:
- VisualAge Generator does not support PLPs if the project names or version
names include DBCS characters. If your project or version names include
DBCS characters, see Creating a migration plan file manually for information on how to create the migration plan file without
using a PLP.
To create a high-level PLP project for use in migration do the following in
VisualAge Generator:
- From the Workbench window, select the Projects tab.
-
Create a new Java project to contain the Project List Part. For
example, create a project called MySubsystem1.
- Select the new project, right-click and select Manage -> Configure
VAGen Required Projects from the context menu.
-
In the Configure VAGen Required Projects window, select each project that you
want to include in your migration set. For each project you can select
a specific version to include in the migration set. Alternatively, you
can select Most recent edition, which causes the migration tool to
automatically include the version that is currently at the top of the list
whenever you use this project during migration.
- After you have selected all the project versions that you require for the
migration set, click OK.
- Version and release the high-level PLP project, for example
MySubsystem1.
- Test that the PLP project correctly loads the project versions you want
for your migration set as follows:
-
Delete the high-level PLP project from your workspace.
- Click Selected -> Add -> Project.
- From the Add Project window, do the following:
- Select Add projects from the repository.
- Select the high-level PLP project that you just created and the version
that you created.
- Also select Add VAGen required projects.
- Click Finish.
- The high-level PLP project and all the project versions it specifies are
added to your workspace.
- From the VAGen Parts Browser, select Tools -> Show Duplicate
Parts. There should not be any parts on the list. If there
are, you need to change the high-level PLP project so that there are no
duplicates.
-
You might also want to run validation for your programs and tables to ensure
that they are valid in VAGen and that you are not missing any parts.
You can chain PLP projects. For example, create a PLP project that
lists the project versions for all your common projects. Then, for each
subsystem, create a high-level PLP project for that subsystem that includes
all the subsystem-specific project versions and the PLP project that specifies
all the common project versions. This way you do not have list each
common project version in every subsystem's high-level PLP
project.
When you are ready to run the Stage 1 migration tool, do the
following:
-
When you set your Stage 1 preferences, on the Build plans page, in
the Repository Filters section, set the Projects list so that a filter in the
list matches the high-level PLP project you created.
- When you instruct the Stage 1 tool which preferences file to use, also
specify the -o option. The -o option instructs
the Stage 1 migration tool to create the migration plan files for you based on
your high-level PLP projects and to overwrite any existing migration plan
files.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.