HP 3000 Manuals HP 3000 Manuals
"Nonclass" Errors
Run-Time Codes: System Activity Indicator
When the system is up and running, the LED display issues an alternating
run-time message code as FxFF, where "x" is a hexadecimal digit from 0-A.
The digit represents the percentage of non-idle time.
DCC Error Codes
Toward the end of system start, the data communication configurator (DCC)
executes. This creates the LINK and DTS managers defined in
NMCONFIG.PUB.SYS. If the DCC completes successfully, the following
message is displayed:
DCC STARTUP - OK!
However, if an error occurs, one of the following error messages is
displayed. These messages contain a DCC error number and description.
In the messages below, the P-L number is a DCC procedure number and DCC
location number. These values are needed by your local DCC support
person when a problem is reported. The SSSSSSSS in some messages is an
8-digit hexadecimal value. MMM and LLL are decimal values. PATH is a
NMCONF path or LLIO physical path.
NOTE Currently, the last message issued to the console during a system
startup is DCC STARTUP - ERROR. This is not an actual error. Enter
a Return and the system prompt MPE/XL: is displayed.
MESSAGE DCC ERROR P-L, (LLIO status SSSSSSSS).
CAUSE Low-level I/O services reported status SSSSSSSS. DCC employs
LLIO services io_config, io_get_frame, io_release_frame,
io_get_timer, and io_send.
ACTION For more information decode SSSSSSSS.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (reply status SSSSSSSS, MSG descriptor MMM).
CAUSE Reply message MMM contained reply status SSSSSSSS.
ACTION For more information decode MMM and SSSSSSSS.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (NMCONF file error SSSSSSSS). NM path: PATH
CAUSE NMCONFIG file may not exist, or it is locked by another
entity.
ACTION check to see if NMCONFIG.PUB.SYS exists, if it's a NMCONF type
file, or if it is locked by another entity.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (NMCONF record error SSSSSSSS). NM path: PATH
CAUSE The DCC surrogate was unable to read an NMCONFIG record, or
the data in NMCONFIG.PUB.SYS was not validated or is
corrupted.
ACTION Validate NMCONFIG.PUB.SYS again (for example, VALIDATE
DTS/LINK) and reboot more information decode SSSSSSSS.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, configuration record data was invalid. NM
path: PATH
CAUSE data in NMCONFIG.PUB.SYS was not validated or is corrupted.
ACTION Contact your support personnel. Validate NMCONFIG.PUB.SYS
again (for example, validate the DTS/LINK) and reboot.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (HILO status SSSSSSSS. ldev LLL).
CAUSE high-level I/O services reported status SSSSSSSS for
logical device number LLL. DCC employs HILO services
configure_hilo_device, allocate_device and ldm-port.
ACTION Logical device numbers <99 should not be employed by data comm
products.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (buffer manager status SSSSSSSS).
CAUSE data comm buffer manager reported status SSSSSSSS.
ACTION check buffer-size and number-of-buffer fields in
NMCONFIG.PUB.SYS. For more information decode SSSSSSSS.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (External procedure not found).
CAUSE Native library did not contain expected data comm manager
procedure. Either NMCONFIG.PUB.SYS or the image is corrupted.
ACTION Validate NMCONFIG.PUB.SYS again and reboot.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (memory management status SSSSSSSS).
CAUSE memory management reported status SSSSSSSS. DCC could not
acquire memory. This is serious condition and requires the
intervention of your Hewlett-Packard Support Representative.
ACTION Contact your Hewlett-Packard Support Representative.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (Ports status SSSSSSSS).
CAUSE Ports reported status SSSSSSSS. DCC employs ports procedures
create_port and extended_receive.
ACTION For more information, decode SSSSSSSS.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, time out on reply msg, descriptor MMM.
CAUSE DCC did not receive reply message MMM in the allotted time.
ACTION Contact your DCC support personnel.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, too many DTCs configured.
CAUSE NMCONFIG.PUB.SYS contains more than the supported ten DTCs.
ACTION Remove excess DTCs and reboot.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, link name specified for DTS does not exist.
CAUSE The link name in DTS.DTC screen was not found. The name may
be incorrect in either the LINK screen or the DTC screen or
the NMCONFIG.PUB.SYS file may contain more than the supported
two links.
ACTION Remove excess links and reboot.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, link name for specified DTS is not available.
CAUSE Some error occurred during link configuration.
ACTION Usually the error is hardware related; the card is not in the
configured slot, the card is not connected to the LAN, and so
on. There should be another DCC error message displayed that
relates to the link configuration error. Check additional
error messages.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, TOO MANY LINKS CONFIGURED.
CAUSE NMCONFIG.PUB.SYS contains more than the supported two links.
ACTION Remove excess links and reboot.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, message received on wrong subqueue.
CAUSE Valid message received on wrong subqueue: the message was
rejected.
ACTION None.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, unrecognized message received. All junk mail
will be rejected.
CAUSE Unrecognized message received.
ACTION None.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, internal DCC logic error
CAUSE Unknown.
ACTION Contact your local DCC support person.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (DAM error status SSSSSSSS). LLIO path: PATH
CAUSE IEEE802.3 DAM (for example, the link) reported an error during
configuration. Usually the error is hardware related; for
example, the card is not in the configured slot or the card is
not connected to the LAN.
ACTION Fix and reboot the system.
-------------------------------------------------------------
MESSAGE DCC warning PL, add ldev to class failure (HILO status
SSSSSSSS, ldev LLL).
CAUSE Classes are not supported.
ACTION Remove class from all profiles and reboot.
-------------------------------------------------------------
MESSAGE DCC ERROR P-L, (External procedure not found).
CAUSE This error is printed during each system startup. It does not
affect the startup however, and the startup is successful even
though the message is printed.
ACTION None.
-------------------------------------------------------------
High-Priority Machine Check (HPMC) Errors
High-priority machine check messages take the form:
XXF0 - XXFF
-------------------------------------------------------------
F1 MESSAGE No message. System halts. (E)
CAUSE instruction TLB parity error occurs.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F2 MESSAGE No message. System halts. (E)
CAUSE data TLB parity error occurs. instruction Unit.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F3 MESSAGE No message. System halts. (E)
CAUSE Mid-bus address parity error occurs, or no slave
response.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F4 MESSAGE No message. System halts. (E)
CAUSE Mid-bus read data parity error occurs. The cache
(master) performs a read transaction and detects
bad parity from the slave.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F5 MESSAGE No message. System halts. (E)
CAUSE Multiple bit read error occurs.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F6 MESSAGE No message. System halts. (E)
CAUSE Mid bus write data parity error occurs.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F7 MESSAGE No message. System halts. (E)
CAUSE Mid-bus CMD or external interrupt request register
data parity error occurs, or a mid-bus timeout
occurs.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F8 MESSAGE No message. System halts. (E)
CAUSE cache tag parity error occurs.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
F9 MESSAGE No message. System halts. (E)
CAUSE Data cache read parity error occurs.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
FA MESSAGE No message. System halts. (E)
CAUSE Floating-point high priority machine check.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
FB MESSAGE No message. System halts. (E)
CAUSE Instruction parity error occurs.
ACTION Contact your Hewlett-Packard Support
Representative.
-------------------------------------------------------------
NOTE HPMC codes FC through FF are currently undefined. If more than one
error occurs, only the error with the smallest error code is
displayed. For example, if both errors F4 and F7 occur, only F4 is
displayed.
Console Messages for Log File Errors
Log file errors are reported in one of the following messages. Refer to
Table 30-2 for a summary of log file error numbers, their meaning,
and whether they are recoverable or irrecoverable errors.
LOG FILE NUMBER xxxx ERROR #nn. LOGGING STOPPED indicates that an
irrecoverable error occurred. System logging is disabled until the next
system startup.
LOG FILE NUMBER xxxx ERROR #nn. LOGGING SUSPENDED indicates that a
recoverable error occurred. A recoverable error temporarily suspends
logging until the RESUMELOG command is issued.
Table 30-2. Log File Errors
----------------------------------------------------------------------------------------------
| | | |
| ERROR NO. | ERROR | RECOVERABLE? |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 1 | Input/output error in | No |
| | accessing the system disk. | |
| | | |
| 2 | Input/output error in | No |
| | accessing disk log file. | |
| | | |
| 21 | data parity error. | No |
| | | |
| 26 | Transmission error. | No |
| | | |
| 27 | Input/output timeout. | No |
| | | |
| 28 | data overrun. | No |
| | | |
| 29 | SIO failure. | No |
| | | |
| 30 | Unit failure. | No |
| | | |
| 46 | Insufficient disk space to | Yes |
| | create log file. | |
| | | |
----------------------------------------------------------------------------------------------
Table 30-3. Log File Errors (Continued)
-----------------------------------------------------------------------------------------------
| | | |
| ERROR | ERROR | RECOVERABLE? |
| NO. | | |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 47 | Input/output error on file label. | No |
| | | |
| 57 | Virtual memory not sufficient. | No |
| | | |
| 61 | Group (PUB) disk space exceeded in creating log file. | Yes |
| | | |
| 62 | Account (SYS) disk space exceeded in creating log file. | Yes |
| | | |
| 63 | Group disk space exceeded in allocating new extent to the | Yes |
| | log file. | |
| | | |
| 64 | Account disk space exceeded in allocating new extent to the | Yes |
| | log file. | |
| | | |
| 100 | A file of the same name as the current log file already | Yes |
| | exists in the system file directory. | |
| | | |
| 102 | Directory input/output error. | No |
| | | |
| 103 | System directory overflow. | No |
| | | |
| 105 | Illegal variable block structure. | No |
| | | |
-----------------------------------------------------------------------------------------------