Defining and initializing the global catalog

The global catalog is a VSAM key-sequenced data set (KSDS) is used to store start type information, location of the CICS® system log, resource definitions, terminal control information and profiles.

Before you begin

  1. You must ensure that the REGION parameter on your CICS jobs is high enough to cope with the increase in buffer storage used for the global catalog, because this storage comes out of region storage not EDSA. For details, see Sizing buffer space for the global catalog data set.
  2. Estimate the amount of space needed in your global catalog to keypoint installed resource definitions, table entries, and control blocks. You must regularly review your space usage to ensure that extents are not running too close to the limit for your environment. For details, see Calculating the amount of space for the global catalog.

About this task

You can define and initialize the CICS global catalog in two ways. You can use the sample job as described below, or you can use the CICS-supplied job, DFHDEFDS.

Note: If you have to reinitialize the global catalog for any reason, you must also reinitialize the local catalog.

If you need to perform a cold start, do not delete and redefine the global catalog data set. If you were to delete and redefine the global catalog, CICS would perform an initial start, and all recovery information for remote systems would be lost. When remote systems reconnected, CICS would inform them that it had lost any information that they needed to resynchronize their units of work, and messages would be produced to record the fact, on both the local and the remote systems. Instead, to specify that the next start should be cold, use the DFHRMUTL utility with the SET_AUTO_START=AUTOCOLD option. For more information, see Reusing the global catalog to perform a cold start.

Procedure

You can edit the sample job as follows:

  1. Edit the data set name in the CLUSTER definition to be the same as the DSN parameter in the DD statement for the global catalog in the CICS startup job stream.
  2. The primary and secondary extent sizes are shown as n1 and n2 cylinders. Calculate the size required to meet your installation requirements, and substitute your values for n1 and n2.
    Whichever IDCAMS parameter you use for the global catalog data set space allocation (CYLINDERS, TRACKS, or RECORDS), make sure that you specify a secondary extent. CICS abends if your global catalog data set fills and VSAM cannot create a secondary extent. For information about record sizes, see Table 1 in Calculating the amount of space for the global catalog.
  3. Specify the REUSE option on the DEFINE CLUSTER command.
    This option enables the global catalog to be opened repeatedly as a reusable cluster. Also specify REUSE if you intend to use the COLD_COPY input parameter of the DFHRMUTL utility.
  4. Edit the CONTROLINTERVALSIZE values for the VSAM definition if required.
    This job does not specify a minimum or maximum buffer size explicitly, but accepts the default that is set by VSAM. You can code an explicit value if you want to define buffers of a specific size. See Sizing buffer space for the global catalog data set for more information.
  5. Use the recovery manager utility program, DFHRMUTL, to initialize the data set. Specify this utility in the job step INITGCD.
    DFHRMUTL writes a record to the data set, specifying that on its next run using this global catalog, if START=AUTO is specified, CICS is to perform an initial start and not prompt the operator for confirmation. This record is called the autostart override record.
  6. Add a job step to run the DFHCCUTL utility.
    Adding this step means that the global and local catalogs do not get out of step.
  7. Define the data definition statement for CICS.

    The following statement shows the minimum specification for a global catalog for use by a single CICS region.

    //DFHGCD  DD  DSN=CICSTSnn.CICS.applid.DFHGCD,DISP=OLD

    The prefix of the data set reflects the release of CICS TS. For example, it is CICSTS62.CICS.applid.DFHGCD for CICS TS 6.2.

  8. Add the relevant AMP subparameters to the DD statement to help improve restart and shutdown time.
    The AMP parameter is described in z/OS MVS JCL Reference and an example is shown in the CICS startup job stream in CICS startup.

Example job to define and initialize the global catalog

In the example JCL, the high level qualifier (CICSTSnn.CICS) assumes the release level of CICS TS 6.2. You must adapt it for your own CICS release.

Figure 1. Example job to define and initialize the global catalog
//GLOCAT   JOB accounting info,,CLASS=A
//DEFGCD   EXEC PGM=IDCAMS
//SYSPRINT DD   SYSOUT=*
//SYSIN    DD   *
      DEFINE CLUSTER -
               (NAME(CICSTS62.CICS.applid.DFHGCD) -               
               INDEXED                      -
               CYLINDERS(n1 n2)             -                     
               FREESPACE(10 10)             -
               SHAREOPTIONS(2)              -
               RECORDSIZE(4089 32760)       -
               REUSE                        -                     
               VOLUMES(volid))              -
             DATA                           -                     
               (NAME(CICSTS62.CICS.applid.DFHGCD.DATA)  -
               CONTROLINTERVALSIZE(32768)    -                     
               KEYS(52 0))                  -
             INDEX                          -
               (NAME(CICSTS62.CICS.applid.DFHGCD.INDEX) )
/*
//INITGCD  EXEC PGM=DFHRMUTL,REGION=1M                            
//STEPLIB  DD DSNAME=CICSTS62.CICS.SDFHLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=A
//DFHGCD   DD DSNAME=CICSTS62.CICS.applid.DFHGCD,DISP=OLD
//SYSIN    DD *
SET_AUTO_START=AUTOINIT
/*