HP 3000 Manuals HP 3000 Manuals
DCC Error Messages
As system start-up nears completion, the Datacomm Configurator (DCC)
creates the LINK and DTS managers. If the procedure is successful, the
following message will be displayed on the console:
DCC STARTUP - OK!
If the procedure is not successful, the message above is replaced by one
or more error messages. When looking up an error message, note that the
following strings of characters are used to represent information that is
inserted when the message is generated:
* P-L is replaced by a DCC procedure number and DCC location number;
used for detailed diagnostics by Hewlett-Packard support
representative.
* SSSSSSSS is replaced by an eight-digit hexadecimal value; also
used for detailed diagnostics.
* MMM and LLL are replaced by decimal values; used for detailed
diagnostics.
* PATH is replaced by an NMCONF path or LLIO physical path.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (LLIO status SSSSSSSS).
CAUSE A problem exists with the low-level I/O services.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (reply status SSSSSSSS, msg
descriptors MMM).
CAUSE A problem exists with interprocess communication.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, Configuration file open error
SSSSSSSS.
CAUSE The configuration file does not exist or it is
locked.
ACTION Check to see if NMCONFIG.PUB.SYS exists. If it
exists, verify that it is the proper file type and
that it is not locked.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (NMCONF record error SSSSSSSS).
NM Path: NMMGRpath
CAUSE The DCC surrogate cannot read a record in
NMCONFIG.PUB.SYS, or data in the file was not
validated or the data is corrupt.
ACTION Validate the NMCONFIG.PUB.SYS file and reboot. If
necessary, replace the file, validate the file, and
reboot the system.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, configuration record data was
invalid.
NM Path: NMMGRpath
CAUSE Data in the NMCONFIG.PUB.SYS file was not validated
or the data is corrupt.
ACTION Validate the NMCONFIG.PUB.SYS file and reboot the
system.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (HLIO status SSSSSSSS, ldev LLL).
CAUSE A problem exists with the high-level I/O services.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (Buffer manager status SSSSSSSS).
CAUSE A problem exists with the datacomm buffers.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (External procedure not found).
CAUSE A problem exists with DCC execution.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (Memory management status SSSSSSSS).
CAUSE A problem with the system occurred; the DCC cannot
obtain memory.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, (Ports status SSSSSSSS).
CAUSE A problem with the DCC or the port's subsystem
occurred.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, time out on reply msg, descriptors
MMM.
CAUSE The DCC did not receive a reply message within the
allotted time.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, too many DTCs configured.
CAUSE The NMCONFIG.PUB.SYS file contains more than the
supported number of DTCs.
ACTION Remove excess DTCs from the NMCONFIG.PUB.SYS file
and reboot.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, link name specified for the DTS does
not exist.
CAUSE The link name configured in NMMGR on the DTS
DATACOMM & TERMINAL CONTROLLER CONFIGURATION screen
does not match that on the LINK SELECTION screen.
ACTION Go the DTS DATACOMM & TERMINAL CONTROLLER
CONFIGURATION screen and enter the correct link
name.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, link name specified for the DTS is
not available.
CAUSE A problem occurred with the link hardware; the
LANIC might be in the wrong slot or it might not be
connected to the LAN.
ACTION Check the hardware configuration connections.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, too many links configured.
CAUSE More that eight links are configured.
ACTION Delete all unused links so that eight or less links
are used.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, message received on wrong subqueue.
CAUSE A problem exists with the interprocess
communication.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, unrecognized message received.
CAUSE A problem exists with the interprocess
communication.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, internal DCC logic error.
CAUSE A problem internal to the DCC exists.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, Link error status.
CAUSE A problem occurred while configuring the link
manager.
ACTION Contact your Hewlett-Packard support
representative.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, Add Ldev to class failure (HLIO
status SSSSSSSS, ldev LLL).
CAUSE A class contains more than 255 devices, or a
conflict in class names exists.
ACTION Run SYSGEN to verify the conflict.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, Configuration file close error
SSSSSSSS.
CAUSE A problem occurred while closing the
NMCONFIG.PUB.SYS file or the NMCONFIX.PUB.SYS file.
ACTION Check that the files exist, and that adequate disk
space is available for them. If the files exist
and the disk space is large enough, check for file
system or hardware problems.
---------------------------------------------------------------
MESSAGE WARNING: I/O config from last START NORECOVERY will
be used. (DCCWARN 100)
CAUSE A routine message; this indicates that a start
recovery is being attempted.
ACTION No action is required.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, (Startup) cannot open NMCONFIG,
status SSSSSSSS.
CAUSE Cannot open the NMCONFIG.PUB.SYS file.
ACTION Check that the file exists and that it is not
locked. If the file exists and is not locked,
check for file system or hardware problems.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, (Startup) cannot purge NMCONFIX,
status SSSSSSSS.
CAUSE The NMCONFIX.PUB.SYS file cannot be purged.
ACTION Check that the file exists. If the file exists,
check for file system or hardware problems.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, (Startup) cannot open NMCONFIX,
status SSSSSSSS.
CAUSE The NMCONFIX.PUB.SYS file exists but it cannot be
opened.
ACTION Check that the file is not locked. If the file is
not locked, check for file system or hardware
problems.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, (Startup) cannot create NMCONFIX,
status SSSSSSSS.
CAUSE A disk space problem, a file system problem, or a
hardware problem exists.
ACTION Verify that enough disk space is available. If
enough disk space is available, verify that no the
file system problems exist. Then, verify that no
hardware problems exist.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L , (Startup) cannot copy record from
NMCONFIX, status SSSSSSSS.
CAUSE The NMCONFIX.PUB.SYS does not exist, or a file
system or hardware problem exists.
ACTION Check that the NMCONFIX.PUB.SYS file exists. If it
does not, restore it. If the file exists, check
for file system or hardware problems.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, (Startup) cannot copy record to
NMCONFIG, status SSSSSSSS.
CAUSE The NMCONFIG.PUB.SYS file does not exist, or a file
system or hardware problem exists.
ACTION If the file does not exist, create it. If the file
exists, check for file system or hardware problems.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, (Startup) cannot close NMCONFIG,
status SSSSSSSS.
CAUSE The NMCONFIG.PUB.SYS file does not exist, or a disk
space, a file system, or hardware problem exists.
ACTION Check that the NMCONFIG.PUB.SYS file exists. If it
does not exist, restore it. If the file exists,
check for a disk space problem, a file system
problem, or a hardware problem.
---------------------------------------------------------------
MESSAGE DCC WARNING P-L, (Startup) cannot close NMCONFIX,
status SSSSSSSS.
CAUSE The NMCONFIX.PUB.SYS file does not exist, or a disk
space, file system, or hardware problem exists.
ACTION Check that the NMCONFIX.PUB.SYS exists. If it does
not exist, restore it. If the file exists, check
for a file system problem or a hardware problem.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, Blank NODENAME.
CAUSE A host node name was not configured.
ACTION Configure a host node name.
---------------------------------------------------------------
MESSAGE DCC ERROR P-L, Configuration file not validated.
CAUSE Either modifications were made to the network
management configuration file and the file was not
validated, or the file was validated but the errors
listed to the console were not corrected.
ACTION Either validate the network management
configuration file, or correct the errors listed to
the console when the file was first validated.
Then revalidate the file. The host will be
rebooted.
---------------------------------------------------------------