Table of Contents
Advertisement
System Service
Figure 4-27 shows a typical error message.
ERROR CORRECTING MEMORY LOG ANALYSIS
LOGGING STARTED
FIRST ERROR LOGGED
LAST ERROR LOGGED
LAST LOG UPDATE
DATE: 3/31176
DATE: 3/31/76
DATE: 4/ 1/76
DATE: 4/ 1/76
TIME: 13:35
TIME: 17:45
TIME:
8:29
TIME:
8:54
ADDRESS
ERROR TYPE
ERROR
MEMORY
LOC
ROW
TYPE
BIT
BOARD
CHIP
COUNT
BANK 0
U32K
2
DATA
7
SMA
U710
8
5
DATA
9
SMA
U312
1
BANK 1
L32K
7
CHECK
A
SMA
U119
8
7
CHECK
C
FCA
U112
3
Figure 4-27. Typical Error Message
4-101.
ERRORS.
If
an operational error is encountered by MEMLOGAN, the program will print
the appropriate error information and then terminate. A non-file system error causes the following
message to be displayed:
*MEMLOGAN ERROR: <ERRNUM>:
Where
<ERRNUM> 1= FLOCK ERROR ON MEMLOG FILE
2= FUNLOCK ERROR ON MEMLOG FILE
The occurrence of a file system error will cause an error tombstone to be displayed followed by either
*OUT FILE ERROR* or, *LOG FILE ERROR*.
4·102.
CE OPERATING PROCEDURES
The following commands are suggested for the CE to use to obtain hard copy output of memory errors.
:HELLO FIELD.SUPPORT,HP32230
:FILE OUT;DEV=LP
:RUN MEMLOGAN.PUB.SYS
The line printer will then reproduce a copy of the log file.
4·103.
FLI PCA PROGRAMMING
The FLI PCA only accepts direct I/O commands. These commands cause the FLI PCA to copy the
contents of the MCL error logging array into the FLI I/O logging array (CIO-Read Copy), determine if
4-44
Advertisement
Table of Contents
