The On-Switch ECD Audit, audits the disk version of the ECD Data base. Note that it does not audit the incore
version of the ECD so it is advisable to perform an ECD RC/V 'activate' to copy the incore data base to disk prior to
execution of the audit.
To request manual execution of the audit, the following input message should be used:
EXC:ECDAUD
5.15.6 STOPPING THE AUDIT
To stop a currently running ECD Audit, the following input message should be used:
STOP:ECDAUD
5.15.7 STATUS
To obtain the status of a currently running audit or a previously run audit, the following input message should be
used:
OP:ECDAUD
To inhibit execution of the audit, the following input message should be used:
INH:ECDAUD
To allow execution of the audit, the following input message should be used:
ALW:ECDAUD
5.15.8 ANALYZING ERRORS
If ECD errors were detected during the execution of the audit, an output message similar to the following will be
received:
EXC ECDAUD COMPLETED - 5 ERRORS, OUTPUT FILE /database/ecdaud.err
The output file should now be analyzed. In most cases, the file should be small enough to dump to the ROP. It will
contain error-by-error English descriptions of the errors encountered. The ECD form, keys, field being checked, and
error message that are contained in the file will allow the user to correct the data as needed.
An example of an error might be as follows:
form=ucb key1=; key2=; key3=MHD key4=0 field=21 current_value=GROW "error: MHD 0 major_status must be
OOS"
5.16 FEATURE ACTIVATION COUNTING AND RECONCILIATION (FACR)
5.16.1 FEATURE DEFINITION
The Feature Activation Counting and Reconciliation (FACR) program is a new process designed to provide the
customer the ability to monitor feature usage in their 5ESS-2000 switches and provides Lucent Technologies a
vehicle for billing the customer for assigned software features. Release 1 of FACR has the ability to count a subset
of the existing feature packages. For more information on the feature packages which are monitored by the FACR
audit, contact your Lucent Technologies Network Systems Account Representative, or your FACR coordinator. It is
intended that FACR eventually be able to count all feature packages and replace the current Feature Billing
Verification (FBV) process.
This feature does NOT have a Right to Use (RTU) fee. However, in order to be able to use this feature, the
customer must make the necessary arrangements with their Lucent Technologies Network Systems Account
Representative, including having the necessary PC (personal computer) hardware and software in place.
5.16.2 FACR ARCHITECTURE
The FACR feature consists of four components: FACR Data Collection Audit, FACR-RSCANS Communication
Software, Lucent Technologies Billing Center Personal Computer (PC) and Customer Purchasing Center and/or
Marketing Analysis Center Personal Computer. The following is a description of each component:
235-105-210
October 1999
Copyright © 1999
Page 61
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 ...