3. Installation › 3.5 Generate a Database Unit › 3.5.6 Generate and Allocate the Database › 3.5.6.3 Generation Data Group Catalog Index Creation

3.5.6.3 Generation Data Group Catalog Index Creation

The CA MICS backup and archive processes require a number of
generation data groups.  The actual data set names used are
listed in section 4.3.10, Data Set Names.

The use of generation data groups requires that a special
index be created in the control volume (or VSAM) catalog.
The CA MICS job GDGSGEN will generate the statements to
create this index for either type of catalog.  Whether the
statements are generated for an OS control volume or a VSAM
catalog is determined by whether you specify the CVOLSER or
VCATSER parameter in the JCLDEF parms member.

Before each index is built, it is deleted.  These DLTX (or
DELETE) statements will cause an error message if no entry
exists.  This is done so that the number of entries can be
respecified, without the user having to delete each of the
index entries.

DLTX and BLDG (or DELETE and DEFINE) will fail if there is a
cataloged data set with the same index.  IEHPROGM (or IDCAMS)
will issue a message and give a return code of 8.  This is
not a problem for non-GDG entries or if the GDG already has
the desired number of entries.

If you want to change the number of entries kept in a GDG
with cataloged data sets, you must do the following:

    1) Uncatalog any existing entries in the GDG.
    2) Delete the index with a DLTX (or DELETE).
    3) Create the index with a BLDG (or DEFINE).
    4) Catalog any entries uncataloged in step 1.

The job GDGSGEN is submitted for execution to create the
generation data group entries for each component.  This job
will examine the generation data groups defined to the
CA MICS system and compare this set against the catalog.  An
entry will be created for any generation data groups which
have been defined to CA MICS that are not found.  GDGSGEN may
be run at any time without affecting the CA MICS data sets
that are already allocated.

Note:  The GDGSGEN job does NOT create the index entries for
       the optional incremental update tape database files or
       for any optional tape DETAIL files.  These GDG indexes
       are associated with a specific product in the unit
       database and are created by the individual product's
       cccIUGDG or cccGDGGN job.  Please see the individual
       product guides for more information on optional
       incremental update tape database files and/or optional
       tape DETAIL files.


To run GDGSGEN submit the job as follows:

          SUB 'prefix.MICS.CNTL(GDGSGEN)'