The Meridian 1 can be set to run diagnostic overlay programs at a specified time, normally in a quiet traffic period (eg, at midnight). The automatic daily running of diagnostic overlays helps to identify and correct faults before users become aware of them.
When the Meridian 1 detects a fault during daily routines, it will automatically run a diagnostic program, overlay program 45, to identify and report the fault condition. A Data Save/Dump (LD 43) is also performed during the daily routines.
Which Overlays are run
You can check which overlays are set to run on your system, and at what time, by printing the Configuration Record (CFN) in LD 22. This provides a lot of information, but the part pertaining to background and daily routine tasks is shown in the "OVLY" section. You may also print just the overlay data, by entering OVLY at the TYPE prompt.
>LD 22 REQ prt TYPE ovly OVLY SID 100 BKGD 044 PBXH X TODR 00 DROL 030 034 038 045 060 135 137 CY45 02 MULTI_USER ON
The above shows that:
- The System ID (SID) is 100
- LD 44 (Software Audit) is running as a background task.
- Message Waiting Lamp tests (PBXH) are disabled.
- The Daily Routines are run at 0000hrs - midnight (TODR)
- The Daily Routine overlays run are... (DROL)
- On detection of a fault, LD 45 will be run 02 times (CY45)
Adding Overlays to the Daily Routines
This is done in LD 17.
REQ CHG TYPE CFN OVLY YES SID XXXX - your system ID, found in LD 2 with TSID BKGD XX XX - background diagnostic overlays, to remove type X before PBXH 00-23 - hour at which message waiting lamp tests are done TODR 00-23 - hour at which daily routines are performed DROL XX XX - specify the overlays for daily routines CACH (0) 2-32 - specify the numbery of overlays to be stored in cache PRTY XX XX XX - specify priority overlays that are to stay in cache MULTI_USER - enter ON to allow more than one user to log in at a time TRLL 1-31 1-31 - numbers for RPE local loopback, if applicable CY45 (0)-31 - set the number of times LD 45 is to run on fault detection REQ END - terminate overlay 17
Valid Background overlays:
30, 33, 34, 35, 36, 37, 38, 40, 41, 43, 44, 45, 46, 53, and 135
Valid Daily Routine overlays:
30, 32, 33, 34, 35, 36, 37, 38, 40, 41, 43, 44, 45, 46, 51, 53, 60, 61, and 135
To remove an overlay, type X before the overlay number.
- LD 30 (and LD 45) in the DROL will disable any digital sets which are unplugged. In stead of removing LD 30, prevent a set from being disabled by adding CLS FLXA. A set with the class of service FLXA will not disable during the daily routines.
- LD 135 in the DROL will cause a CPU swap. This is no longer recommended with Pentium and newer processors.
- The DROL should consist of at least loads 30, 34, 60 (if you have digital trunks), and 43.
- You can manualy invoke the DROL (to test) with LD 135, MIDN, and then logout.
It is good practice to always perform a data dump after making any programming changes.
>LD 43 . EDD DATA DUMP COMPLETE
Checking the Daily Routine output
There are two ways you can do this. The simplest way is to leave the termial (hyper-terminal) or printer on/connected overnight, and later check the output. Hyper-termial is useful due to its "scroll-back buffer" which should be set to the maximum size.
Alternatively, you can read the System Event List (SEL) with LD 117. This is also useful for checking other system event messages.
>LD 117 => PRT SEL nn - where nn = 0-(20)-SELSIZE
This will print the most recent records in system event list.
SELSIZE is usually 500 (
PRT SELSIZE to find the setting), meaning the
system event log will hold 500 events. The SEL is also searchable using the
FIND XXXX command.
You can also manually invoke the routines, and watch the output.
>LD 135 REQ: MIDN
MIDN command (in LD 135) will run the routines after LD 135 is aborted and the TTY
is logged out.
Normally, no problems should occur. A typical printout will show each overlay in the DROL list starting and exiting normally. Any problems will be shown by the relavent system message, SCH, ERR, etc. Again, these messages will be stored in the system event log.
DROL000 DAILY ROUTINE BEGIN DTIM LD60 BEGIN 00:04 8/8/2001 DROL001 DAILY ROUTINE END DTIM LD60 END 00:04 8/8/2001 DROL000 DAILY ROUTINE BEGIN CCED LD135 BEGIN 00:04 8/8/2001 DROL001 DAILY ROUTINE END CCED LD135 END 00:04 8/8/2001 AUD0000
The 'AUD0000' is the output from LD 44 (Software Audit) and indicates that an error free audit pass was made. No errors detected. System software OK. No action to be taken. Happy, happy!