Operations › CA IDMS/DB Audit Sample JCL and Key › Allocating Work Files for the DISK Option

Allocating Work Files for the DISK Option

If you specify DISK in the AUDIT statement, you must allocate two direct access disk files: one for the db-key hash table and one for the db-key save table. These direct access files may be VSAM or, for z/OS and z/VM only, BDAM. If these files are allocated as VSAM, they must be defined through IDCAMS. This optional step is identical for all environments.

Sample control statements for VSAM file allocation are shown in Figure 5.5 and are contained in source library member USADEFN. A key to the variables (shown in bold) is shown in Figure 5.6.

 DELETE (vsam.dbkhash) CLUSTER
 DELETE (vsam.dbksave) CLUSTER
 DEFINE CLUSTER (-
             NAME(vsam.dbkhash) -
             RECORDS(record.numbersh) -
             NUMBERED -
             RECORDSIZE(4084 4084) -
             SPEED -
             usetype -
             FILE(dname) -
             VOLUMES(volume.name) -
             ) -
       DATA  ( -
             NAME(vsam.dbkhash.DATA) -
             ) -
 DEFINE CLUSTER ( -
             NAME(vsam.dbksave) -
             RECORDS(record.numberss) -
             NUMBERED -
             RECORDSIZE(4064 4064) -
             SPEED -
             usetype -
             VOLUMES(volume.name) -
             ) -
       DATA  ( -
             NAME(vsam.dbksave.DATA) -
             )

Figure 5.5: Control Statements for Allocating VSAM Work Files for the DISK Option

vsam.dbkhash — The dataset name of the VSAM file for the db-key table. This file is needed only if you specify DISK in the AUDIT statement.

record.number — The number of records to be allocated in the VSAM work space for the db-key table. The number of records is equal to:

1.2 * SETLIMIT-value
      510               + 1

For example, if the SETLIMIT value is 3000 (default), you should allocate:

((1.2 * 3000/510)   + 1 = 8

vsam.dbksave — The dataset name of the VSAM file for the db-key save table. This file is needed if you specify DISK in the AUDIT statement.

record.numberss — The number of records to be allocated in the VSAM work space for the db-key save table. The number of records depends on the number of next, prior, or owner pointer errors that you expect CA IDMS/DB Audit to find while set walking. Up to 127 pointer errors can be accommodated by one record. Therefore, you should allocate 1 primary record with extra secondary space, unless you expect more errors. An allocation of (1 10) should be adequate. The maximum number of records is equal to:

SETLIMIT-value
    127                + 1

usetype — The appropriate type: REUSE or UNIQUE. If you specify UNIQUE, you must DELETE and DEFINE this cluster prior to each execution of CA IDMS/DB Audit.

volume.name — Volume to contain the cluster or component.

dname — The DD name of the JCL statement defining the file. Depending upon your environment, the parameter is optional.

Figure 5.6: Key to Figure 5.5