If you already have external controls that determine what configuration map versions to load into your image when you generate in VisualAge Generator, you might decide to create the migration plan file by hand or to develop a tool to create the migration plan file automatically from your external information. The migration plan file must have a .pln file extension and the following format:
<migrationDefinition> <migrationSet name="migrationSet1" version="migrationSet1Version1" vgName="migrationSet1" vgVersion="migrationSet1Version1"> <configMap name="configurationMap1" version="configurationMap1Version1"> </configMap> <configMap name="configurationMap2" version="configurationMap2Version1"> </configMap> . . . <configMap name="configurationMapN" version="configurationMapNVersion1"> </configMap> </migrationSet> </migrationDefinition>
In the previous example, the following apply:
The migration set name is only used during migration as a way of identifying a group of configuration maps. Other than the situation in which maps span multiple configuration maps in VisualAge Generator, the migration set name is not used after migration.
When you are ready to run the Stage 1 migration tool, do the following:
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.