Defining the local catalog

The local catalog is a VSAM key-sequenced data set (KSDS). The local catalog is not shared by any other CICS region.

Before you begin

Unlike the global catalog, which must be defined with enough space to cope with any increase in installed resource definitions, the size of the local catalog is relatively static. The following section describes the information held on the local catalog.

CICS® Transaction Server for z/OS® is divided into functional areas (or components) known as domains. These domains communicate through a central component, the CICS kernel, and their initialization and termination is controlled by the domain manager. All the domains require an individual domain parameter record, and these are stored in the local catalog. The CICS domains use the local catalog to save some of their information between CICS runs and to preserve this information across a cold start. For further guidance information about what is written to the local catalog, and about how CICS uses the local catalog for startup and restart, see Controlling start and restart.

About this task

You can define and initialize the CICS local catalog in two ways. You can use the sample job as described below or you can use the CICS-supplied job, DFHDEFDS, to create a local catalog for an active CICS region.

Edit the sample job as follows:

Procedure

  1. If you are defining local catalogs for multiple CICS regions, identify the clusters uniquely by making the specific APPLID of each CICS one of the data set qualifiers. For example, you might use the following names for the clusters of active and alternate CICS regions, where DBDCCIC1 and DBDCCIC2 are the specific APPLIDs:
    DEFINE CLUSTER -
           (NAME( CICSTS54.CICS.DBDCCIC1.DFHLCD)
    
    DEFINE CLUSTER -
           (NAME( CICSTS54.CICS.DBDCCIC2.DFHLCD)
  2. Space for 200 records is probably adequate for the local catalog. However, specify space for secondary extents as a contingency allowance.
  3. The local catalog records are small in comparison with the global catalog. Use the record sizes shown, which, with the number of records specified, ensure enough space for the data set.
  4. Define the data definition statement for the local catalog as follows:
    //DFHLCD  DD  DSN=CICSTS54.CICS.applid.DFHLCD,DISP=OLD

Example

Figure 1. Sample job to define and initialize the local catalog
//LOCAT    JOB accounting info,,CLASS=A
//DEFLCD   EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
         DEFINE CLUSTER -
                (NAME( CICSTS54.CICS.applid.DFHLCD) -  1
                 INDEXED                       -
                 RECORDS( 200 10 )             -                  2
                 FREESPACE(10 10)              -
                 SHAREOPTIONS( 2 )             -
                 REUSE                         -
                 VOLUMES( volid ))             -
           DATA                                -
                (NAME( CICSTS54.CICS.applid.DFHLCD.DATA )   -
                 KEYS( 52 0 )                  -
                 RECORDSIZE( 70 2041 )         -                  3
                 CONTROLINTERVALSIZE( 2048 ))  -
           INDEX (NAME( CICSTS54.CICS.applid.DFHLCD.INDEX ) )
/*
//*****************************************************************
//INITLCD EXEC PGM=DFHCCUTL
//*
//*            INITIALIZE THE CICS LOCAL CATALOG
//*
//STEPLIB   DD DSN=CICSTS54.CICS.SDFHLOAD,DISP=SHR
//SYSPRINT  DD SYSOUT=*
//SYSUDUMP  DD SYSOUT=*
//DFHLCD    DD DSN=CICSTS54.CICS.applid.DFHLCD,DISP=SHR
//*
//


dfha2_def_local_catalog.html | Timestamp icon Last updated: Sunday, 4 June 2017