
To use this facility, the user needs to specify the following:
The Number of the Destination Disk:
This disk must be out-of-service (OOS) or off-line (OFL) and does not
have to be a mate of the active (ACT) disk.
The Full Pathname of the Source File That Exists on an ACT Disk:
If the source is a regular or contiguous
file, then this file must exist on a mounted file system.
The Full Pathname or Number of the Destination Partition on the Nonactive Disk:
If a name is specified,
then it must exist as a special device file on the active disk. If the source is a regular or contiguous file, then this
partition must be a file system.
The Pathname on the Destination Partition Where the File is to be Written:
If the destination pathname is
not specified, then the pathname of the source file will be used. If the destination pathname starts with a ``/'',
then the mount point will be excluded from it (destination pathname). It is not required that all directories in the
pathname specified exist.
Examples of copying files can be found in Section 6 of this document.
3.6.5 EMERGENCY DUMP
On disk, a partition is reserved for emergency dump. When there has been data written in this partition, an
autonomous report (
REPT EMERGENCY DUMP PARTITION FULL
) will be printed. When data has been written in
the emergency dump partition, the emergency dump status flag will be set. Due to the status flag, the previously
mentioned report will be printed periodically. When the flag has been set, no other emergency dump can be written
within the next 12 hours. Therefore, an input message is present to clear the status flag. This message must only be
used when the dumped data has been saved. As soon as the status flag has been cleared, the emergency dump
partition is marked empty. The message to clear the status flag is
CLR:EMERDMP;
. Before saving the data, the
status has to be investigated. This is done by means of the input message
OP:EMERSTAT;
. This will result in a
report indicating on which disk, MHD 0 or 1, the data has been dumped, how many bytes have been written, and the
hexadecimal address of each segment written. To save the dumped data, an emergency dump can be performed.
3.6.6 LOG FILE HANDLING
Hardware and software errors will generate error reports. These reports will either be printed on the ROP, collected
in the log file, or both. The message class of the report is decisive whether a report will either be logged, printed, or
both.
The user can change the log or print option with the input message
CHG:LPS?
. This will direct the output to the
DAYLOG
file or print the data at the devices specified in the ECD for that message class. The
OP:LPS?
message
can be used to determine the current log and print status of a message class.
On MCC display Page 110
SYSTEM INHIBITS, the poke command 902 generates the input message
OP:LPS,MSGCLS=ALL
and causes the status of the message classes to be printed at the ROP.
Log files can be used to do the following:
Detect and Correct Transient Errors:
Correctable memory errors can occur at an increasing rate over many
days. This problem can be detected by studying the log file entries.
Determine a Chronological Order of Events:
This can be done by putting entries from several log files
together.
Log files are defined in the classdef and device forms in the equipment configuration data base (ECD). All log files
235-105-210
October 1999
Copyright © 1999
Page 17
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 ...