Initializing the CSD

Before you can use the CSD, you must define it as a VSAM KSDS data set, and initialize it using the DFHCSDUP utility program. (See Figure 11.)

The INITIALIZE command initializes your CSD with definitions of the CICS-supplied resources. After initialization, you can migrate resource definitions from your CICS® control tables, and begin defining your resources interactively with CEDA. You use INITIALIZE only once in the lifetime of the CSD.

The command LIST ALL OBJECTS lists the CICS-supplied resources that are now in the CSD.

Figure 11. Sample job to define and initialize the CSD
//DEFINIT  JOB  accounting information
//DEFCSD   EXEC PGM=IDCAMS
//SYSPRINT DD   SYSOUT=A
//AMSDUMP  DD   SYSOUT=A
//SYSIN    DD   *
   DEFINE CLUSTER -
            (NAME(CICSTS31.CICS.applid.DFHCSD) -
            VOLUMES(volid)               -
            KEYS(22 0)                   -                         1 
            INDEXED                      -
            RECORDS(n1 n2)               -
            RECORDSIZE(200 2000)         -                         2 
            FREESPACE(10 10)             -
            SHAREOPTIONS(2)              -                         3 
            LOG(ALL)                     -                         4 
            Start of changeLOGSTREAMID(CICSTS31.CICS.CSD.FWDRECOV)End of change   -            4 
            BWO(NO)                                                4 
 
          DATA                           -
            (NAME(CICSTS31.CICS.applid.DFHCSD.DATA)   -
            CONTROLINTERVALSIZE(8192))          -
          INDEX                                 -
            (NAME(CICSTS31.CICS.applid.DFHCSD.INDEX))
/*
//INIT     EXEC PGM=DFHCSDUP,REGION=300K
//STEPLIB  DD DSN=CICSTS31.CICS.SDFHLOAD,DISP=SHR
//DFHCSD   DD DSN=CICSTS31.CICS.applid.DFHCSD,DISP=SHR             5 
//SYSPRINT DD SYSOUT=A
//SYSUDUMP DD SYSOUT=A
//SYSIN    DD *
           INITIALIZE
           LIST ALL OBJECTS
/*
//

Notes:

 1  The key length is 22 bytes, and the KEYS parameter must be coded as shown.

 2  The average record size of 200 bytes is calculated for a CSD that contains only the CICS-supplied resource definitions (generated by the INITIALIZE and UPGRADE commands). If you create a larger proportion of terminal resource definition entries than are defined in the initial CSD, the average record size is higher because of the larger size of the terminal-type entries. The TERMINAL and TYPETERM definition record sizes are listed under Calculating CSD disk space. The maximum record size must be 2000 as shown.

 3  Code the SHAREOPTIONS parameter as shown.

 4  You can specify the recovery attributes for the CSD in the ICF catalog instead of using the CSD system initialization parameters. If you decide to use the CSD in RLS mode, you must define the recovery attributes in the ICF catalog.

You specify the recovery attributes as:

If you specify LOG(ALL), you must also specify LOGSTREAMID to define the 26-character name of the MVS™ log stream to be used as the forward recovery log. If you specify recovery attributes in the ICF catalog, and also want to use BWO, specify LOG(ALL) and BWO(TYPECICS).

 5  The DDNAME for the CSD must be DFHCSD.

Creating a larger CSD

To avoid the CSD filling while CICS is running, ensure that you define the data set with primary and secondary space parameters, and that there is sufficient DASD space available for secondary extents. If your CSD fills up while you are running a CEDA transaction (or the offline utility), define a larger data set and use an AMS command, such as REPRO, to recover the contents of the CSD. If your CSD was dynamically allocated, you can close it, delete it, and redefine it as a larger data set. If your CSD was not dynamically allocated, you must shut down CICS to create a larger data set.

For a description of the commands that you can use for copying files, see the MVS/ESA Integrated Catalog Administration: Access Method Services Reference manual.

[[ Contents Previous Page | Next Page Index ]]