Create the audit control data sets

The audit control data sets contain information about changes to SCLM-controlled members that are located in groups being audited. The audit control data sets are only required if the audit function is used. You must create the audit control data sets before the audit function is enabled. If auditing is used, each project must have at least one primary audit control data set.

You can create an optional secondary audit control data set. The secondary audit control data set is a backup for the primary audit control data set. It allows you to restore audit control information if the primary audit control data set is corrupted. Choose a unique name for this data set and put it on a different volume than the primary audit control data set. If a secondary data set is used, SCLM's performance will be degraded because updates are made to both the primary and secondary audit control data sets. The information in both data sets should be compared periodically to ensure the integrity of the audit control information.

Use the IDCAMS utility to define audit control data sets. Each audit control data set for the project must be a VSAM cluster. If audit control information for different groups will be kept in separate audit control data sets, you must create additional audit control data sets. The following JCL example defines audit control data sets.

Note: This example JCL is called FLM02VER and is in data set ISP.SISPSAMP that is included with SCLM.

Figure 1. Audit Control Data Set Example (Part 1 of 2)

//jobname  JOB (wkpkg,dpt,bin),'name'
//* code additional JOBCARD statements here
//*********************************************************************
//*
//*  THIS JCL EXAMPLE DEFINES A VSAM CLUSTER TO BE USED AS THE
//*    AUDIT CONTROL DATA SET FOR A GIVEN PROJECT.
//*  THE HIGH LEVEL QUALIFIER MUST BE AN ENTRY IN A VSAM CATALOG
//*    IN ORDER TO CREATE THIS CLUSTER.
//*  TO SPECIFY THE FILE, CHANGE THE DEFINE CLUSTER STATEMENT BELOW
//*    AS FOLLOWS:
//*
//*    1) ADD THE FOLLOWING LINE OF JCL TO DELETE THE VSAM CLUSTER
//*       BEFORE THE ALLOCATION IF THE DATA SET ALREADY EXISTS
//*       AND IT NEEDS TO BE DELETED:
//*       DELETE 'project.version.file' CLUSTER
//*       ADD THIS STATEMENT BETWEEN THE //SYSIN ALLOCATION AND THE
//*       DEFINE CLUSTER LINE OF JCL.
//*    2) CHANGE ALL project.version.file TO THE DESIRED FILE NAME.
//*        THIS VALUE IS SPECIFIED ON THE FLMCNTRL AND FLMALTC
//*        MACROS.  IF MORE THAN ONE VSAM ACCOUNTING DATA SET IS
//*        SPECIFIED ON THE FLMCNTRL AND FLMALTC MACROS, MULTIPLE
//*        IDCAMS DEFINE STEPS ARE REQUIRED.
//*    3) MODIFY CYLINDERS (PRIMARY SECONDARY)
//*    4) SPECIFY THE VOLUME VVVVVV ON WHICH IT WILL BE ALLOCATED
//*
//*  A JOB STEP IS THEN EXECUTED TO INITIALIZE THE FILE.
//*
//**********************************************************************

Figure 2. Audit Control Data Set Example (Part 2 of 2)

//STEP1   EXEC PGM=IDCAMS
//*
//SYSPRINT  DD SYSOUT=H
//*
//SYSIN     DD *
     DEFINE CLUSTER +
        (NAME('project.version.file') +
         CYLINDERS(4 1) +
         VOLUMES(VVVVVV) +
         KEYS(40 0) +
         RECORDSIZE(264 32000) +
         SHAREOPTIONS(4,3) +
         SPEED +
         SPANNED +
         UNIQUE) +
         INDEX(NAME('project.version.file.INDEX') -
         ) +
         DATA(NAME('project.version.file.DATA') -
         CISZ(2048) +
         FREESPACE(50 50) +
         )
/*//*********************************************************************
//*
//*  INITIALIZE THE AUDIT CONTROL FILE
//*
//**********************************************************************
//STEP2    EXEC PGM=IDCAMS
//INPUT  DD *
                        SCLM AUDIT CONTROL FILE INITIALIZATION RECORD
/*
//OUTPUT DD DSN=project.version.file,DISP=SHR
//SYSPRINT  DD SYSOUT=H
//SYSIN     DD *
     REPRO INFILE(INPUT) OUTFILE(OUTPUT)
/*
//*
)CM 5665-402 (C) COPYRIGHT IBM CORP 1980, 1989