CICS / WebSphere

After you confirm the new data set names, CICS DA submits a job to create them. You need to customize the new region (e.g., to assign SYSIN parameters), but much of the process is automated. From here, you can add the new CICS region to the CICSPlex.

Managing Resource Definitions

You can migrate CICS resource definitions by using CICS Configuration Manager (CM) for z/OS to convert from CSD into CICSPlex SM Business Application Services (BAS) resources. In this way, you can populate your new multi-region environment with a consistent set of definitions that support the new architecture.

To convert CICS resources:

1. Use the CICS CM plug-in for the CICS Explorer to open the Groups window and select the CSD group that contains your resources. The resulting display shows the groups that are currently associated with the GENAPP application and the artifacts required to support the new application.
2. Right-click a CSD group, then select Show all resources to see the programs in the application (see Figure 6).
3. You can use the Interactive System Productivity Facility (ISPF) interface to select all the resources in a group and copy them into the target group in the CICSPlex SM data repository. This transfer creates the resources in a BAS definition format and makes them available for deployment across the CICSPlex.

To migrate resource definitions, identify all the artifacts that constitute the application and populate a change package in CICS CM:

1. Open the ISPF interface to CICS CM. All the resources in the CSD groups you installed for the application are displayed. To select a resource for packaging, enter P next to each entry (see Figure 7).
2. Define any additional migration rule sets and transform rules for those resources. For example, you can move resources from the CSD file referenced by the REDDVA42 CICS region to the CSD file referenced by the REDDVB42 CICS region.
3. Specify any transformations. For example, you can change the data set name of the KSDSCUST file resource from DEVELOP to PRODUCT so that it’s identified correctly after migration.

Moving VSAM Data to DB2

You can use CICS VSAM Transparency (VT) to migrate KSDS and RRDS data sets to DB2 without changing existing VSAM-based applications. The data is then open to new uses using regular DB2 SQL calls. Because the programs are unchanged, you need to test only that the migrated data is in the correct format and the programs can access the DB2 data successfully.

You can use CICS IA to discover which CICS applications use specific VSAM data; this is useful for testing.

5 Pages