Making the CSD available to CICS

To make your CSD available to CICS®, you can either include a DD statement in the CICS startup job or use dynamic allocation.

Installing the RDO transactions

The RDO transactions, CEDA, CEDB, and CEDC are defined in the CICS-supplied group, DFHSPI. This group is also included in DFHLIST, the CICS group list. Ensure that a copy of DFHSPI is included in the group list that you use for your CICS startup. You specify the group list on the GRPLIST system initialization parameter.

For information about the CEDA, CEDB, and CEDC transactions, see the CICS Resource Definition Guide.

Moving your CICS tables to the CSD

When you have created a CSD, and initialized it with CICS-supplied definitions, you are ready to move the contents of your CICS tables to the CSD data set. You do this by running the offline utility, DFHCSDUP, using the MIGRATE command to specify the table you want to migrate. For information about the DFHCSDUP utility program and the available commands, see the CICS Operations and Utilities Guide. For information about moving the contents of CICS tables to the CSD, see the CICS Resource Definition Guide.

Note:
If you are using a CSD with an earlier release of CICS, upgrade your CSD as part of the process of migration. For information about upgrading the CSD, and about the release compatibility of the CSD after upgrading, see the CICS Transaction Server for z/OS® Migration from CICS TS Version 2.3.

Installing definitions for the Japanese language feature

If you have the Japanese language feature, install the definitions for the feature in the CSD, by running DFHCSDUP and specifying:

UPGRADE USING(DFHRDJPN)

For information about the DFHCSDUP utility program and the available commands, see the CICS Operations and Utilities Guide.

[[ Contents Previous Page | Next Page Index ]]