The verbose option, when used with the execute command, will provide the craft with the ability to print each unit
completion message on the receive-only printer (ROP). This option can also be specified for REX when it is started
automatically via RC/V. More information about the running of REX automatically can be found in Section 12.5
(REX Automatic Scheduling).
The verbose option should be used with care. No more than two modules should be running with the verbose option
at a time. Having more than two modules running at the same time with the verbose option can result in flooding of
the ROP with unit completion messages, which could result in some messages being lost.
12.4.3 DEMAND OPTION
Some diagnostics have demand phases that are traffic affecting. The demand option is provided to perform tests
that are not run in normal mode operations. This option gives the testers at the factory the ability to run all diagnostic
phases since no consequences from the demand phases are realized.
NOTE:
This option should not be used in an office that has been cutover.
12.4.4 STOP
Stop halts current routine exercise activity. Stop may halt exercises in the entire office, a range of modules, and/or a
single test type. If a test is not executing, the request will be ignored. A message signaling the stop of exercises will
be printed. In both the CM and SMs/SM-2000s, tests in progress are stopped and the unit restored.
In the AM, the user can stop an active or waiting REX process maintenance request in the Deferred Maintenance
Queue (DMQ) of the Maintenance Input Request Administrator (MIRA).
STOP:DMQ
may leave the hardware
community in the OOS state if the REX maintenance request was active, and manual action may be required to
restore the hardware community to service.
STOP:DMQ
does not stop the REX process. The format of the
STOP:DMQ
input message is as follows:
{STOP | STP}:DMQ;{ACTIVE | WAITING|unit#[subunit#]}!
See Procedure 13.3 for complete command syntax.
12.4.5 REPORT
The report command will display a test type result summary of the hardware units tested in the last REX session. In
the case of the DGN and FAB tests, the summary includes the circuit type exercised and a circuit count for each test
status (for example, ATP, STF, etc.). A unit out of service will be skipped by REX, and hence, will appear as part of
the not started totals. For the ELS test, the summary report will contain the number of lines completed, skipped, and
not started.
A summary report may be requested for the entire office (that is, all modules and tests) for a single module (that is,
one SM/SM-2000 or CM) and/or a single test type (for example, ELS). A report for the entire office is automatically
generated every day at 8:00 AM summarizing the activity of the previous night (if any).
See Procedure 13.4 for complete command syntax. Procedures 13.5 and 13.6 show the resulting output
messages for DGN/FAB and ELS, respectively.
12.4.6 REXINH STATUS
12.4.6.1 Module Inhibit Status
The output status command is used to request the REX status for the entire office or a single module (that is,
SMs/SM-2000s or CM). Displayed is the inhibit, the allow, or the in-progress state of a particular test type. The
status may be changed by using the
INH:REX
and
ALW:REX
commands or the start and stop commands.
235-105-210
October 1999
Copyright © 1999
Page 4
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 ...