VisualAge Generator to Enterprise Generation Language Migration Guide
You need to consider the following tasks when planning your migration
project:
- Plan a pilot project for migration:
- Select the developers and systems support personnel that will be involved
in the pilot project.
-
Select a small subset of your source code to use in the pilot project.
Use this small subset to verify your environmental setup and your library
management procedures and tools.
- Review the capabilities of the WebSphere Studio product that you plan to
use. Be sure that it includes the features that you require. For
example:
- If you plan to generate COBOL for the zOS environment, you must use the
WebSphere Studio Enterprise Developer product.
- If you plan to use iSeries, you must use the WebSphere Developer Studio
Client for iSeries Advanced Edition.
- Review the prerequisites for the WebSphere Studio product that you plan to
use. In addition, review the prerequisites for your runtime
environment. For example:
- If you plan to generate COBOL for the zOS environment, be sure to review
the prerequisites for the Enteprise Developer Server for zOS product.
- If you plan to generate Java for the Unix System Services(USS)
environment, be sure to review the prerequisites for the Enterprise Developer
Options for zOS components shipped with WebSphere Studio Enterprise
Developer.
- If you plan to generate for iSeries, be sure to review the prerequisites
for the runtime component of the WebSphere Developer Studio Client for iSeries
Advanced Edition
- If you plan to generate Java for a workstation environment, be sure to
review the prerequisites for the runtime component of the WebSphere Studio
product that you plan to use.
- Obtain education for the team that will run the pilot project:
- WebSphere Studio development environment
- EGL language
- VisualAge Generator to EGL migration tools
- Run the pilot project plan to do the following:
- Install WebSphere Studio for the pilot team.
- Run the VAGen Migration Tool for the pilot set of code. See the
following sections for information on the migration tool:
-
Create library management processes:
-
Select and install a source code repository, including access from the
developer workstations.
- Define change management procedures that work with your corporate culture
and your selected source code repository.
- Develop any tools you need for your change management procedures,
including the following:
- Checkin and checkout procedures.
- Version control procedures.
-
Tools to retrieve source code from the source code repository and to load a
WebSphere Studio workspace or directory structure if you want to use batch
generation.
- zOS COBOL target environments:
- Install prerequisites for the Enterprise Developer Server for zOS
V5.0 product, including any changes to your COBOL compiler and
runtime.
- Install the Enterprise Developer Server for zOS V5.0
product.
- Install any required PTFs to Enterprise Developer Server for zOS.
- Install the build server. Also customize the pseudo-JCL build
scripts.
- Java target environments:
-
Generate and prepare your programs:
- Review and modify your build descriptor parts. See Reviewing your EGL build descriptor parts for a list of changes that cannot be handled by the VAGen
Migration Tool.
-
Optionally, build an EGL batch generation server machine. This requires
the use of a source code repository and the creation of tools to load a
directory with all the parts you need for generation.
- Testing:
- Test your development environment to make sure that you can successfully
debug programs. Debugging in the development environment might require
access to DB2, remote VSAM files, and non-EGL programs that only run in your
runtime environment.
- Test at least a representative sample of your programs to ensure you
understand any runtime differences. See Runtime differences for a list of differences.
-
Test your library management procedures and tools using typical changes that
you might make to the EGL source code.
Be sure to test your procedures for changing common code, forms, tables, and
programs for each target environment. Also test your procedures for
adding common code, forms, tables, and programs for each target
environment.
-
Refine your library management procedures and tools based on the results of
the pilot project.
- Document the findings of the pilot project, including:
- Code changes that need to be made, particularly if you are changing target
environments.
- Changes developers need to make to any personal build descriptor
parts.
- References to sections of the Migration Guide that are particularly useful
for your developers based on the problems you encountered during the pilot
project.
- Changes in runtime behavior that your end users will notice.
- Build a plan to complete your migration based on the findings from the
pilot project.
- Provide education for the remaining developers:
- WebSphere Studio development environment
- EGL language
-
Your new source code repository
-
Your new library management process
- Your new generation process
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.