VisualAge Generator to Enterprise Generation Language Migration Guide
To create a high-level configuration map for use in migration do the
following in VisualAge Generator:
- From the VisualAge Organizer, select Options and be sure that
Full Menus is selected.
- From the VisualAge Organizer, select Tools -> Configuration
Maps.
- From the Configuration Maps Browser, select Names ->
Create.
- In the Information Required window, enter the name of the configuration
map and then click on OK. A new edition of the configuration
map is automatically created and selected.
- Select Applications -> Add. Then select each application
that you want to migrate and the version of that application. You can
only specify one version for each application. Click OK when
you have selected the version for each application that you need to
include.
The application versions that you specify will be migrated as a group.
This group determines the set of parts that the migration tools use to resolve
ambiguous situations.
- Version the configuration map by selecting Editions ->
Version.
- Select the configuration map version and load it into your image by
selecting Editions -> Load.
- After you have loaded your new high-level configuration map, you might
also want to validate your programs and tables to ensure that they are valid
in VAGen and that you are not missing any parts. When you validate your
programs, include /GENMAPS, /GENHELPMAPS, and /NOGENTABLES. These 2 map
options enable you to ensure that the maps are valid for the programs in which
they are used. /NOGENTABLES enables you to validate a table just one
time rather than revalidating the table with every program in which the table
is used.
You can chain configuration maps. For example, you can create a
configuration map that lists the version for each of your common
applications. Then, for each subsystem, create a high-level
configuration map for that subsystem that includes the version you need of
each subsystem-specific application. You can include the configuration
map for the common applications in the subsystem configuration map as
follows:
- From the Configuration Maps Browser, select an open edition of the
subsystem configuration map.
- Select Expressions -> Add.
- In the Information Required window, click OK to accept
true as the expression.
- Select true in the Config. Expressions pane. Then
select Required Maps -> Add -> As First. Then select the
configuration map version that contains the common applications.
Version the configuration map by selecting Editions ->
Version.
- Select the configuration map version and load it into your image by
selecting Editions -> Load With Required Maps.
Using required maps provides a simple way of specifying the common
application versions without having to explicitly list the common application
versions in every subsystem's high-level configuration map.
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 Configuration Maps list so that a filter
in the list matches the high-level configuration map you created.
-
When you instruct the Stage 1 tool which preferences file to use, also select
the Overwrite PLN option. This option instructs the Stage 1
migration tool to create the migration plan files for you based on your
high-level configuration maps 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.