dbaudit.extract — The dataset name assigned to your extract file.
disk — An appropriate unit designation for each file.
dbaudit.workfile — The dataset name assigned to your work file.
dbaudit.dbkywork — The dataset name assigned to your db-key work file. This file is needed only if you are auditing or fixing integrated index sets, and you have mandatory-automatic index sets.
dbaudit.indxextr — The dataset name assigned to your integrated index extract file. This file is needed only if you are auditing or fixing integrated index sets.
dbaudit.indxwork — The dataset name assigned to your integrated index work file. This file is needed only if you are auditing or fixing integrated index sets.
dbaudit.dbkhash — The dataset name assigned to your BDAM db-key hash table. This file is only needed if you specify the DISK option of the AUDIT statement.
dbaudit.dbksave — The dataset name assigned to your BDAM db-key save table. This file is only needed if you specify the DISK option of the AUDIT statement.
volser — The volume serial number of the disk that will contain a particular file.
pe,se — The primary/secondary space allocation for the EXTRACTS file allocated to DASD. Space allocation for a DASD file depends on the number of errors detected during the audit phase the maximum record size is 512 bytes and must be blocked by the user (as noted in blkse). Because it is difficult to estimate the number of errors, you can allocate this file to tape. For most cases, DASD can be used. For example, if you are using a 3330 device with a blocksize of 6144, one cylinder can hold 456 extract records. A primary/secondary specification of 10,2 should be adequate.
blkse — The block size of the EXTRACTS and WORKFILE files. The maximum record size is 512 bytes. A blocksize of 6144 is recommended for all device types.
pw,sw — The primary/secondary space allocation for the WORKFILE file allocated to DASD. Space allocation should be twice the space allocation of the EXTRACTS file.
A primary/secondary allocation of 20,4 should be adequate.
pd,sd — The primary/secondary space allocation for the DBKYWORK file allocated to DASD. To estimate the total number of blocks, multiply the total number of integrated index member records of mandatory-automatic sets by 30 (record length) times 2. The result is the total number of bytes. Divide by the block size to get the total number of blocks.
A primary/secondary allocation of 5,2 should be adequate.
blksd — The block size of the DBKWORK file. The record size is 30 bytes. A block size of 6000 is recommended for all device types.
pi,si — The primary/secondary space allocation for the INDXEXTR file and for the INDXWORK file, allocated to DASD. This space is primarily used for integrated index orphan records and secondarily for integrated index errors. If you have inserted a small number of member records in integrated index sets in the database, then you can estimate the total blocks by multiplying the total number of integrated index member records times the maximum record length (588) times 0.5, dividing by the block size. If a large number of member records have been inserted in integrated index sets, multiply the result by 3.
A primary/secondary allocation of 20,4 should be adequate.
blksi — The block size of the INDXEXTR and INDXWORK files. The maximum record size is 588 bytes. A blocksize of 6144 is recommended for all device types.
blkcnt.hash — The number of blocks for the BDAM db-key hash file. See Figure 5.6.
blkcnt.save — The number of blocks for the BDAM db-key save file. See Figure 5.6.
Figure 5.8: Key to Figure 5.7
|
Copyright © 2013 CA.
All rights reserved.
|
|