You should analyze the file or files you are going to migrate.
There are
a number of reasons for doing this:
- Each alternate index path must be mapped. Analysis of the file
establishes
the characteristics of each alternate index path.
- Identify all of the application programs that access the file. This allows
you to develop a test plan. It also allows you to identify all of the
batch JCL procedures that need to be modified to enable
CICS®
VT access to a migrated data set.
- Some of the fields or records in the file might be obsolete. You should
choose whether you want to migrate potentially obsolete data to
DB2® or take the
opportunity to clean up the file.
- Identify future requirements for the file, after it has been migrated to
DB2.
For example, you might want to add new columns to the table to support
enhancements
that you plan to make to the application.
- Some files might have multiple copybooks. You need to decide how
to handle this.
- CICS VT
supports multiple START BROWSE processes in
CICS, up to a limit specified as a
CICS VT
user option. This is covered in
Generating CICS VT runtime modules.
You should establish the maximum number of concurrent browse processes
for each file to be migrated.
When you have analyzed your file or files, you will know the basic
design
of the
DB2
tables
that will be used and which batch and
CICS
programs will need to be tested.