CA IDMS/DB Audit enables you to selectively include or exclude subschema areas, records, or sets from an audit run. You can also mix inclusive and exclusive processing. For example, you can include named areas and exclude records or sets from those areas. You can also include a record and exclude particular sets that the record owns.
The following parameter options influence inclusive and exclusive processing. These parameters are fully explained in the "Parameters" chapter.
PROCESS Statement: STARTWITH
AREA Statement: NOACCESS/SWEEP/NOSWEEP
BEGIN and END
RECORD Statement: NOACCESS/SWEEP/NOSWEEP
SET Statement: AUDIT/NOAUDIT
To understand inclusive and exclusive processing, you must understand the relationship between STARTWITH and the AREA, RECORD, and SET parameter options.
STARTWITH defines only the starting point of how much is to be audited based on the subschema named in the PROCESS statement. AREA, RECORD, and SET options further identify the scope of processing to be performed.
To initiate inclusive processing, first specify STARTWITH=NONE to exclude all portions of the database from processing. Then supply AREA, RECORD, and SET statements to select portions of the database to be included in processing.
To initiate exclusive processing, first specify STARTWITH=ALL to include all portions of the database for processing. Then supply AREA, RECORD, and SET statements to select portions of the database to be excluded from processing. Because STARTWITH=ALL is the default parameter, it need not be explicitly specified. For clarity, this guide always specifies STARTWITH=ALL for exclusive processing.
Mixed processing combines elements of inclusive and exclusive processing to make very select auditing possible. For example, you could include an area and exclude sets from within that area. You can specify either STARTWITH=ALL or STARTWITH=NONE depending on which portions of the database are to be audited.
|
Copyright © 2013 CA.
All rights reserved.
|
|