
input command. Similarly, maintenance personnel can suspend a scheduled test session for maintenance reasons
via the STP:ATTS input command, including running on-demand testing, and restart the scheduled test session
when ready again. The schedule resumes at the appropriate time in the schedule, skipping tests that were
scheduled for the period of suspension.
The ATTS is an automatic test tool. Manual demand testing of trunks may use various test directors. Manual testing
has priority over automatic testing, so maintenance personnel do not have to wait for an entire session to complete
before a contested director resource is provided for the demand test. The ATTS and demand requests for director
resources are queued when received. In demand testing, maintenance personnel wait only while the next ATTS test
is executed before the request is serviced.
3.5.2.3 ATTS Reports
Two types of reports are possible:
demand
reports and
autonomous
(scheduled) reports.
The output of the report can be directed to a desired printer/output device
To avoid cluttering the receive-only printer (ROP), the ATTS reports can be printed as they occur at the end of
each test, or printing may be suppressed. The data is logged to allow printing at a later time.
Output report format is similar to the manual demand-tests output. Some changes are made for variations in
output format (for example, tabular output format) because of output-format constraints. The output reports for
one trunk group (that is, session) are output contiguously. The CLLI field (trunk group name field) is output from
the trunk group relationship along with each trunk group output.
Full test results are logged incrementally as they are executed. Maintenance personnel can interrogate the
logging file to derive standardized reports of the results. Selection of report type (for example, failed trunks only,
or complete results) is made when the output report is requested via the
DUMP:ATLOG
message with an
appropriate command parameter. Maintenance personnel have access to the logging file to do regular
file-management transactions, such as the printing of selected parts.
The ATTS results go to a binary file, then the report generator can be used to print results. The report generator
results can be routed to an American Standard Code for Information Interchange (ASCII) file that can be
browsed through and printed later. These files can be archived for later usage.
The ATTS results are logged for a minimum of 7 days. Although maintenance personnel get results daily, a
7-day log covers events such as weekends and holidays. There are warning messages to show when the log
file reaches 95 percent of its capacity.
Output-sorting criteria - The users of the report generator can provide the following options as parameters to
the
DUMP:ATLOG
input message used for retrieving ATTS reports containing logged test results.
Select an output report for all schedules, or a specific schedule of logged results on a specific week and
day of the schedule. Thus daily activities can be scheduled based on these results.
Select an output report based on a trunk group number to obtain the results for that trunk group from the
entire log.
Obtain a full dump of the log results.
Specify whether the above reports include all test results, just failed test results, or just aborted test results.
The test results show one of the following for each tested trunk:
235-105-210
October 1999
Copyright © 1999
Page 10
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 ...