are located in the directory /log/log. The pathname for each log file is defined in the particular device form.
3.6.7 SIZE OF LOG FILES
To prevent a file system overflow, the files are limited in size. When a log file is first created, the file will be called
XXXXX1, where XXXXX stands for the log filename. When half of the disk space is used, the contents of XXXXX1
is copied into XXXXX0, and the most recent information will be stored in XXXXX1 again. When all disk space is
used, the ``1-part'' is again copied into the ``0-part'' which will overwrite the old information by then and the ``1-part''
will be filled again with the most recent information. Each log file entry has time of day information, real-time clock
values, and sequence numbers.
The log files must be dumped at regular intervals to avoid losing the contents of the files. It is advisable to dump the
files once a day.
The available space in the log file for operations on recent change data, RCLOG, can be obtained by using the
OP:AVAILLOG;
input message.
3.6.8 TYPES OF LOG FILES
There are several log files present in the exchange. Most of them are related to the administrative module (AM).
Table 3-5 shows the log files related to the AM. Table 3-6 shows the log files related to recent change
and equipment data and input messages.
Table 3-5
Review of the Log Files Related to the AM
LOG FILE
DESCRIPTION
CONFLOG
Configuration management log file. This file contains a record of each error detected in a hardware unit.
Activation of storing the information in
CONFLOG
is done by the
ALW:CNFLG
message.
ERLOG
Error interrupt log file. This file contains control unit (CU) error interrupts, except memory related ones.
MEMLOG
Memory history log file. This file contains the supplementary data for memory error interrupts. This log
file will be used to locate transient memory failures.
IODRVLOG
Input/output driver log file. This file contains the error reports associated with the Input/Output Driver and
Disk Driver.
PMLOG
Postmortem log file. This file contains the postmortem dumps.
SPLLOG
Spooler output log file. This file contains the spooler output process (SOP) failure printouts.
SIMLOG
System integrity monitor log file. This file contains errors detected by the system integrity monitor, usually
dealing with resource overload conditions.
CMONLOG
Maintenance monitor log file. This file contains a record of terminated and restarted maintenance
interface processes.
DAYLOG
Daylog file. This file contains output messages from the AM as well as SM, CM, and other areas of the
switch. It is used to debug software faults and has detailed information that is not required for routine
office operation. This file is an ASCII file. The method used to dump the file is dependent upon the
software release.
OLBLOG
AM off-line boot log file. This file contains output messages and PRMs directed to the ROP on the
off-line side during the off-line boot (OFLBOOT) procedure.
Table 3-6
Log Files Used for Recent Change Data and Input Messages
LOG FILE
DESCRIPTION
RCLOG
Operations on recent change (RC) log files. This file contains the changes made by operations on RC
data. When an insert is made, the log file will contain the new data. When an update is made, the log file
will contain the new data. When a deletion has taken place, the old data will be stored in the log file. To
inhibit logging of operations on RC data, the command 612 at the master control center (MCC), Page
110 - SYSTEM INHIBITS, must be keyed in. Note that unlogged operations on RC data will be lost after
a boot. When an RC log file reaches 100 percent in use, the major alarm will be set off and the LOG
FILE FULL message will be printed on the ROP, indicating that the RC/Vs are locked out until a backup
is done.
ECDLOG
Equipment configuration data log file. This file contains all the changes made in the equipment
235-105-210
October 1999
Copyright © 1999
Page 18
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 ...