History File - Nortel Meridian 1 Planning, Installation And Operating Instructions

A failure on a trunk may keep the trunk from detecting incoming calls. The
threshold mechanism cannot detect such a failure, so this program also
records how many days it has been since each trunk received an incoming
call. If you suspect some incoming calls are not being processed, you can use
the command LMAX in Trunk Diagnostic 1 (LD 36) to identify the trunk with
the maximum idle days.
System Loader
The System Loader program loads all call processing programs and data, and
starts memory-checking diagnostics. After all required programs and data
have been loaded and all checks performed, the System Loader is erased from
system memory, the Initialize Program runs, and normal call processing
begins. This process is called a sysload (or system reload).
The System Loader operates automatically on system power up or if a
common equipment or power fault destroys information in the system
memory.

History File

If a printer is connected to the system, each system message is printed as it is
received. If a printer is not connected, you can use the History File (if
equipped) to store a limited number of system messages in protected memory.
The contents of the file may then be printed on demand, using LD 22.
The messages stored are specified on a system basis and can be one or more
of the following types:
• customer service changes (CSC)
• maintenance messages
• service changes (SCH)
• software errors
• initialization and sysload messages
• traffic messages
For information on selecting the messages to be stored, see the Option 11C
Compact Software Guides.
Option 11C Compact
Chapter 25 — Fault locating and clearing
Planning, Installation, Fault Clearing and CCBR Guide
Page 451 of 536