Creating a CSD

If you do not already have a CSD in use at your installation:

  1. Decide how much disk space you require.
  2. Decide whether you want to use the CSD in RLS or non-RLS mode. Having the CSD open in RLS mode allows more than one CICS® region to update the CSD concurrently. However, if your CSD is defined as a recoverable data set, and you want update it using the batch utility, DFHCSDUP, you must quiesce the CSD in the CICS regions before running DFHCSDUP.

    If you decide to use RLS for the CSD, specify CSDRLS=YES as a system initialization parameter. See VSAM record-level sharing (RLS).

  3. Decide whether the CSD is to be eligible for backup-while-open (BWO6). If so, you require the following components of DFSMS 1.2 or later:

    If the CSD data set is to be eligible for BWO, it must have an ICF catalog entry and be defined in SMS-managed storage. You must also specify:

  4. Define and initialize the CSD.
  5. Decide what CICS file processing attributes you want for your CSD. Although the CSD is a CICS file-control-managed data set, you define file control resource definitions for the CSD by specifying CSDxxxxx system initialization parameters (see Defining CSD attributes).
  6. Decide what backup and recovery procedures you require for your CSD.
  7. Decide if you want to use command logs for RDO; see Logging RDO commands for details of the CADL, CAIL, CRDI, CSDL, CSFL, CSKL, CSPL, and CSRL destinations that CICS uses for RDO command logs.
  8. Make the CSD available to CICS, either by using dynamic allocation or by including the necessary DD statement in the CICS startup job stream. For dynamic allocation of the CSD, you name the fully qualified data set name, and the disposition, on the CSDDSN and the CSDDISP system initialization parameters respectively.

    When you have started CICS, test the RDO transactions CEDA, CEDB, and CEDC. For information about these transactions, see the CICS Resource Definition Guide.

  9. Finally, if you want to restrict access to particular CICS-supplied transactions by applying security, define the necessary transaction profiles to RACF® or other external security manager (ESM) and authorize userids as appropriate. For information about how to do this, see the CICS RACF Security Guide.

For information about migrating CICS control tables to RDO using the MIGRATE command, see the CICS Operations and Utilities Guide.


6.
Eligibility for BWO means that DFSMS components can back up the CSD while the data set is open for update.

[[ Contents Previous Page | Next Page Index ]]