
hours from when the audit was stopped, the Processor Entity audit will resume from the point at which it left off
during its previous execution.
If, after the audit has been stopped, the same EXC command that was used to start it is re-entered more than
24 hours from when the audit was stopped, the Processor Entity audit will start from the beginning (that is with
the first relation on the processor). It will NOT resume from the point at which it left off.
If, after the audit has been stopped, a different EXC command is used to start a Processor Entity audit, the one
that was previously stopped will be abandoned (that is it can never be restarted).
5.14.5.5 All Audits
If no option is provided to the STP command, all executing SODD audits are stopped.
STP:AUD=SODD
5.14.6 STATUS
5.14.6.1 Full Audit
The OP:STATUS command provides information on whether the audit is inhibited or not. This follows the current
dynamic data audits mechanism.
OP:STATUS:AUD=SODD,FULL
5.14.6.2 Incremental Audit
The OP:STATUS command provides information on whether the audit is inhibited or not. This follows the current
dynamic data audits mechanism.
OP:STATUS:AUD=SODD,INCR
5.14.6.3 All Audits
The execution status of both the active and suspended audits can be obtained by using the
OP:AUD=SODD,EXC
command. When the command is entered, the relation/processor currently being executed by the active Full,
Incremental, and Processor Entity audits is displayed. The percentage of the audit's completion is also displayed for
these three audit types. For the other Entity audits, this command provides the actual entity being audited (that is,
TN 2201000).
If a Full, Incremental, or Processor Entity audit has been stopped due to a user request or an internal error, the
audit's status is displayed as
STOPPED
. If desired, the audit can be restarted via the
EXC:AUD=SODD
command.
5.14.7 ANALYZING ERRORS
5.14.7.1 Population Rule Errors
There are primarily two kinds of errors that are produced by the audits. Some error cases have a hand-crafted error
message similar to the ODA cross check errors (custom error messages). The remaining errors (standard error
messages) are automatically generated errors that have at a minimum the relation, the keys to the tuple, and the
location (line number) in the population rule file where the error occurred. In most of the cases, a fragment of the
actual population rule that failed will also be printed as part of the error message. The
Translations Data Manual
(TDM) 235-600-1
xx
provides a listing of all the population rule files and has a discussion on the PRL5.0 language.
NOTE:
The Translations Data Manual is a software release specific document. The document number is based on
each available software release.
235-105-210
October 1999
Copyright © 1999
Page 47
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...