Nortel DMS-100 Series Maintenance Manual page 94

1-78 Maintenance overview
The REX test order for feature AF3771 is:
Table REXSCHED must contain data to establish the REX test schedule for
the RLCM/OPM. This table contains the information that the REX test
coordinator requires to schedule the tests according to operating company
specifications. The entry of data in table REXSCHED can disable the test.
For additional information about table REXSCHED, refer to the data
schema section of the Translations Guide.
The system generates the IOAU112 log report for LCMs if the following
events occur:
Expanded LCM REX test results
Table REXSCHED controls scheduling of system REX (SREX) tests for
LCMs. The LCM_REX_TEST task SREX can perform at the same time in
multiples of four. The SREX task also can be performed at the same time as
REX tests of XPMs. The LGC, LTC, and the RCC XPMs can be hosts to
LCMs. Conflicts arise when an XPM scheduled for REX testing is the host
of an LCM scheduled for REX testing.
To avoid conflicts, the SREX controller schedules REX tests of XPMs and
LCMs that occur at the same time. Refer to the following figure SREX
system dependencies. The LCM SREX subsystem registers the
LCM_REX_TEST class. This subsystem also identifies dependencies with
other REX_TEST types during initial program load (IPL). As LCM nodes
are added to the SREX database, the controller enters data with defaults in
table REXSCHED.
297–8351–550 Standard 04.01 August 1999
RESUME resumes REX testing after the interruption of REX testing.
QUERY returns the status of the REX test (active or suspended).
HELP returns a brief description of the REX test.
critical nodes first, like the CM and message switch (MS)
the number of days from the last system or manual REX test
the order of internal PM number
the LCM is not REX tested for more than 7 days
REX test takes longer than specified
REX test cannot start after a defined number of attempts