HP 3000 III Series Manual page 242

MCU/Main Memory Overview
initialization phase of MPE (coolstart, warmstart, coldstart, re-
load, update). MEMLOGP cannot be activated at any other time.
If MEMLOGP cannot be initiated successfully during initializa-
tion, another attempt cannot be made until the system is brought
up again. Initially, MEMLOGP attempts to obtain the status of
the FLI PCA (DRT 2). If the PCA does not respond, error correct-
ing memory is absent from the system and MEMLOGP immediately ter-
minates. If this occurs, no message relating to error logging
will appear at the system console. If MEMLOGP initiation is suc-
cessful, the following message appears at the system console:
ST/<TIME>/MEMORY ERROR LOGGING INITIATED
The message occurs after the DATE/TIME messages and before the
WELCOME message. MEMLOGP attempts to open the system memory er-
ror disc file MEMLOG (MEMLOG.PUB.SYS). If no such file exists on
the system, a new file will be created. If MEMLOG already ex-
ists, the file will be opened without altering the information
contained in the file. The file remains open as long as the sys-
tem is up. During those periods when MEMLOGP is accessing the
file, it will lock and unlock the file as necessary to ensure no
other access to it. The log analysis program (MEMLOGAN) similar-
ly locks and unlocks the file when it is accessing it. If an
operational error is encountered by MEMLOGP, the process will
display an error message and terminate. The message displayed
is:
ST/<TIME>/MEMORY LOGGING ERROR#<ERRNUM>.LOGGING STOPPED
The range and definitions for <ERRNUM> are:
1-10 Internal MEMLOGP errors.
1 FLOCK error on MEMLOG· file.
2 FUNLOCK error on MEMLOG file.
3 TIO error. Error logging hardware not ready.
4 CIO error during copy operation from logging array.
5 RIO error during scan of logging array. (Errors 6-10
reserved for future use.)
20-500 File system errors involving MEMLOG file. All file
errors encountered by MEMLOGP are fatal to the process
and cause it to terminate. Refer to the MPE Intrinsics
Reference Manual, part no. 30000-90010 for definitions
of the file system error numbers.
Once the MEMLOG file has been opened, MEMLOGP periodically inter-
rogates the error logging array in the MCL PCA via the FLI PCA.
If errors have occurred, the MEMLOG file is updated. The error
logging array is interrogated via the FLI PCA when MEMLOG is
first activated and thereafter once approximately every hour. If
one or more errors have occurred in the hour interval since the
last log update, MEMLOGP will perform the following operations:
6-18