HP 3000 III Series Manual page 245

MCU/Main Memory Overview
tern is brought up. Therefore, if a non-default timing interval
is desired, MEMTIMER must be run after each initialization of the
system.
6-40. Output. MEMLOGAN output will vary according to whether
the MEMLOG file is null or updated and, if updated, whether er-
rors have occurred. If the MEMLOG file is null (after running
MEMLOGAN with PARM=l) MEMLOGAN will terminate after displaying
the mes sage:
*NO ENTRIES IN MEMLOG FILE*
If the MEMLOG file is not empty, MEMLOGAN will print the date an~
time of the first and last log updates. If errors have been
logged, the date and time of the -first and last error logged will
also be printed. If no errors have been logged, MEMLOGAN will
terminate after displaying the message:
LOGGING STARTED -DATE:
LAST LOG UPDATE -DATE:
***NO ERRORS LOGGED***
If errors have been logged, MEMLOGAN will continue by printing a
tabular interpretation of the information in the MEMLOG file.
The format of the printout is shown in figure 6-8. A typical
printout is shown in figure 6-9.
6-41. 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 tomb-
stone to be displayed followed by either *OUT FILE ERROR* or,
*LOG FILE ERROR*.
6-42. Obtaining Memory Errors Copy. Use the following commands
to obtain a line printer copy of the log file:
:HELLO FIELD.SUPPORT,HP32230
: FILE OUT; DEV =LP
:RUN MEMLOGAN.PUB.SYS
6-43. 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 PCA's Error Logging Array into the FLI PCA'S I/O Log-
ging Array (CIO-Read Copy), determine if an error log (1) was
transferred (TIO-Read Cbpy Error), search the I/O Logging Array
6-21