Migrating to VisualAge Generator
This section provides some suggestions for a process to migrate Cross
System Product applications to VisualAge Generator.
- Determine what environment you are going to use (for example, MSLs on the
LAN or workstation).
- Determine if you have the equipment to run VisualAge Generator.
- Determine how you should set up your test environment. For example,
will the data stay on the host or will the data be on the workstation for
testing. This will affect what hardware and software you need.
You need to decide how you will handle your non-Cross System Product
programs for the test environment.
- Determine how you want to handle database access such as SQL, DL/I, and
VSAM. Decide what you want to handle VSAM access and what to do with
DB2/2 and its need for qualifiers.
- Determine if your Cross System Product applications use DL/I. If
so, you need to purchase the appropriate Microfocus IMS products so you can
test the applications on the workstation.
- Determine if your Cross System Product applications are using dynamic or
static SQL. VisualAge Generator does not have an option to use dynamic
SQL as a default. If you used the default dynamic SQL instead of static
SQL in Cross System Product, you will need to determine how you want to set
the permissions on the static plans in DB2.
- Determine what CICS PPT and PCT entries will be required for each program
and get the system programming staff to start updating CICS with these
entries.
- Install and test VisualGen Host Services and VisualAge Generator WorkGroup
Services completely, including researching the PSP buckets for needed
PTFs. For CICS, ensure that the runtime services utility, ELAM, is
installed and working correctly. You will need this utility for problem
determination.
- Export all the MSLs from Cross System Product and import them into
VisualAge Generator. Keep the same MSL structure (for the benefit of
the programmers).
- Keep the same characters to define constant and variable fields when you
import Cross System Program maps into VisualAge Generator (Typically, the
"number/pound" sign (#) character and the "not" character (upper case 6 on a
3270 keyboard). However, the "not" character is not found on personal
computers (PC) keyboards so you need to change this to some character on the
PC keyboard after you have finished importing from your Cross System Product
MSLs.
- Validate the Cross System Product application. This provides a list
of errors where Cross System Product rules were violated but were not caught
until you migrated to VisualAge Generator. Use this list to correct the
errors.
- Copy all JCL templates for your environment (MVS or VSE) to a separate
subdirectory and make the necessary modifications as needed to this
copy. You might want to start by generating and preparing a simple
one-map application. Then, use the JCL errors reported on the initial
preparation to determine how to change the JCL templates to match your
environment.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]