Operations › Processing Examples › Parameter Guidelines

Parameter Guidelines

General guidelines on parameter syntax structure and audit processing follow:

• The STARTWITH option and AREA, RECORD, and SET statements are hierarchical: STARTWITH has the broadest impact, and SET has the narrowest. You can use a lower level parameter to reverse an effect caused by a higher level parameter, thereby mixing inclusive and exclusive processing.
• AREA options propagate to logically related records and sets.
• RECORD options propagate to logically related areas and sets.
• SET options propagate to logically related areas and records.
• Use the positive subparameters (AUDIT and SWEEP) in AREA, RECORD, and SET statements to include elements that were excluded through STARTWITH=NONE.
• Specify negative subparameters (NOACCESS and NOAUDIT) to exclude elements that were included through STARTWITH=ALL.
• NOSWEEP is unique in that it can be considered as either a positive (allows access) or negative (do not sweep) option, depending upon use.
• If you specify NOACCESS for either AREA or RECORD statements, do not specify AUDIT for SET statements that are associated with the same area or record.

  Similarly, if you specify NOACCESS on an AREA statement, do not specify a record SWEEP or set AUDIT for records and sets that are associated with the area.

• CA IDMS/DB Audit identifies conflicting parameters as either errors or warnings. Processing terminates if any parameter presents a direct conflict between AREA, RECORD, or SET parameters. Audit processing continues when conflicting options produce warnings, but some options may be overridden, especially when conflicts arise during propagation.
• The Audit Report Areas/Records/Sets report section documents the processing that will occur.
• In the PROCESS statement, specify the SCAN option to allow you to review the Areas/Records/Sets section of the Audit Report and verify what processing is to take place before CA IDMS/DB Audit actually begins that processing.