CA IDMS/DB Audit storage requirements vary depending on the size of the subschema table being processed, the maximum database page size, the number of buffers, sort storage requirements, whether or not VSAM is used, and the selected AUDIT options.
After processing a valid PROCESS statement, CA IDMS/DB Audit loads the subschema and DMCL load modules or phases into main storage and builds a pseudo-subschema (PSUB) from the real CA IDMS subschema. Once the pseudo-subschema is built, the real CA IDMS subschema and DMCL are deleted from main storage. After parameter processing is completed, a BIND RUN-UNIT is issued. At this time, all of DBIO's work areas are obtained.
CA IDMS/DB Audit then calculates the amount of storage required for its work areas and issues a GETMAIN/GETVIS to obtain this amount from the region/partition. The amount of main storage not obtained by CA IDMS/DB Audit (and DBIO) is available for operating system use (such as CA IDMS/DB Audit's file buffers, VSAM, and sort).
Note: In a z/VSE environment, all of CA IDMS/DB Audit's and DBIO'swork areas are obtained from the GETVIS area, not from the Problem Program Area (PPA). Only the SORT program and associated sort work areas are allocated in the PPA.
Use the formula shown in Figure 5.4 to estimate the amount of virtual storage required to run CA IDMS/DB Audit.
|
VIRTUAL STORAGE = |
|
|
CA IDMS/DB Audit SIZE |
330K. Size of CA IDMS/DB Audit module. |
|
+ CA IDMS/DB Audit Buffers |
Sum of block size times the number of buffers for each non-database file. |
|
+ PSUB |
Approximately 3 times the total size of the subschema and DMCL load modules or core image phases. |
|
+ Database Buffers |
Maximum page size times number of buffers specified in the DMCL named in the subschema. |
|
+ Sort Storage |
Use your installation's default sort size. |
|
+ VSAM Storage |
Optional. Used if database has VSAM files or the DISK option is used. Refer to the appropriate system manual to determine the size of the ACB, EXT list, and RPL. If the DISK option is used to store the db-key table and the db-key save table on VSAM disk, add two 4K buffers. |
|
+ DBKEYTBL |
SETLIMIT value times 9.6 (result is in bytes). Used only if the CORE option is used and auditing CALCSETS and/or USERSETS and/or INDEX. If a SETLIMIT value is not specified, use 28K. |
|
+ DBKEY Save Table |
SETLIMIT value times 8 (result is in bytes). Used only if the CORE option is used and auditing CALCSETS and/or USERSETS and/or INDEX. If a SETLIMIT value is not specified, use 24K. |
|
+ Record Bind Area |
Total length of all audited records defined in the subschema (including prefixes) plus an additional 64 bytes for each record being audited. If auditing integrated index sets, add the largest page size of containing SR8 records. |
|
+ Sort Key Area |
Total length of the symbolic keys of all records with sets being audited. This area is the work area required for validating a member record's symbolic key within a sorted set. |
|
+ Page Bind Area |
Used for page audit. Sum of number of areas audited times 40. |
|
+ IIX Level Save Area |
If auditing integrated index sets, add the maximum SR8 size times the maximum number of index levels. |
Figure 5.4: Formula for Estimating Virtual Storage
|
Copyright © 2013 CA.
All rights reserved.
|
|