#K — The number of kilobytes of storage to be made available to the program execution phase. For more information, see the Storage Requirements section.
your.loadlib — The dataset name of the MVS/PDS library into which you downloaded CA IDMS/DB Audit.
idms.loadlib — The dataset name of the MVS/PDS library in which your DMCL and subschema reside.
sort.loadlib — The dataset name of the MVS/PDS library in which your sort modules reside.
disk — The unit address of the disk drive you want to use for the CA IDMS/DB Audit execution file, or a generic assignment to indicate a disk drive allocation.
ps,ss — Primary/secondary space allocation for the SORT. Space allocation depends on the number of error extract records created in the audit phase. In most cases, the number of extracts created is small. A primary/secondary specification of 5,2 should be adequate. The total sortwork space allocated should be twice the space allocated to the EXTRACTS file.
If your database has numerous errors or the sets containing errors are long, the extract file may be large. In that case, you may need more than four SORTWK datasets.
If you are auditing integrated index sets and you have index orphans, then you need enough extra space to accommodate twice the number of index orphans written to the index extract file.
dbfil01/dbfilnn — The DDNAMEs of the database files to be accessed.
user.dbfil01/user.dbfilnn — The dataset names of the database files to be accessed.
dbaudit.extract — The dataset name assigned to your extract file.
dbaudit.workfile — The dataset name assigned to your work file.
sortmsg — The DDNAME of the message file for your SORT product.
a — The appropriate SYSOUT class for your installation.
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 integrated 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.
vsam.dbkhash — The dataset name of the VSAM file for the db-key hash table. This file is needed only if you specify DISK in the AUDIT statement. You must predefine this file using the IDCAMS control statements shown in Figure 5.5. Optionally, this file may be defined as BDAM (see Figures 5.7c, 5.8a, and 5.9c).
vsam.dbksave — The dataset name of the VSAM file for the db-key save table. This file is needed only if you specify DISK in the AUDIT statement. You must predefine this file using the IDCAMS control statements shown in Figure 5.5. Optionally, this file may be defined as BDAM (see Figures 5.7c, 5.8a, and 5.9c).
subschema-name — The name of the subschema that describes the database you want audited.
SYSIDMS— This file is always required for the CA IDMS physical environment parameter to be read. For instance, DMCL=xxxxxxxx must be specified, where xxxxxxxx is the name of the specific DMCL.
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.
Figure 5.10: Key to Figure 5.9
|
Copyright © 2013 CA.
All rights reserved.
|
|