Mixed processing combines elements of inclusive and exclusive processing. The following examples demonstrate a few ways mixed processing can be used.
Example 1 - Sweep a single area, but do not audit the set TEACHER-CLASS contained in area DEPT-REGION:
PROCESS,SUBSCHEMA=TESTSUB,STARTWITH=NONE AUDIT,USERSETS AREA=DEPT-REGION,SWEEP SET=TEACHER-CLASS,NOAUDIT
In this example, the following sets are audited:
DEPT-TEACHER DEPT-ACADEMIC DEPT-GENERAL PREREQSFOR PREREQSARE SUBJECT-CLASS
If QuickCheck is the audit type, then CLASS-REGION is additionally swept for CLASS records because the set SUBJECT-CLASS is audited.
Example 2 - Sweep and audit all areas, but, within the area DEPT-REGION, audit only the set DEPT-TEACHER
PROCESS,SUBSCHEMA=TESTSUB,STARTWITH=ALL AUDIT,USERSETS AREA=DEPT-REGION,NOSWEEP SET=DEPT-TEACHER,AUDIT
Although the AREA statement specifies NOSWEEP for the area DEPT-REGION, it must be swept in order to audit set DEPT-TEACHER. Other sets in DEPT-REGION are not audited because the audit set overrides the area NOSWEEP for records in DEPT-TEACHER only. However, the area NOSWEEP accomplishes the NOAUDIT for the other sets whose owners are in DEPT-REGION.
Example 3 - Specify NOACCESS in DEPT-REGION and AUDIT DEPT-TEACHER in DEPT-REGION
PROCESS,SUBSCHEMA=TESTSUB,STARTWITH=ALL AUDIT,USERSETS AREA=DEPT-REGION,NOACCESS SET=DEPT-TEACHER,AUDIT
The parameters in this example create a more serious conflict than those in Example 2. In this case, CA IDMS/DB Audit cannot reasonably determine whether area NOACCESS or set AUDIT is more important to the user. Consequently, processing cannot continue and CA IDMS/DB Audit displays an error message.
|
Copyright © 2013 CA.
All rights reserved.
|
|