If the number of jobs to migrate to
CICS BAC is too large to migrate
them all at once, you probably need to adopt the alternative migration
plan described here. In this plan, you invoke the migration utility
from the JCL that drives the existing product from which you are migrating.
Using this technique, the migration utility not only migrates your
existing input statements into the
CICS BAC equivalent, but it also
sets up the environment for the
CICS BAC batch request utility. For
this purpose, the sample migration utility is written to enable it
to operate as follows:
- Allocate dynamically the required data sets for DD names CBKIN
and CBKPRINT
- Write the migrated statements to the CBKIN file
- Invoke the CICS BAC batch request utility to execute the migrated
statements in CBKIN.
The final step above is done by issuing an MVS™ LINK
macro to pass control to the CBKBMAIN program. This approach allows
you to drive the
CICS BAC batch request utility using your existing
JCL when the migration utility has migrated the statements. With
this technique, you can fully migrate subsets of your JCL to
CICS BAC over
a period of time, slowly eliminating the need for the migration utility.