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 a 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.
DCCERR 1 DCC ERROR P-L, (LLIO status SSSSSSSS). (DCCERR=1)
Cause: A problem exists with the low-level I/O services.
Action: Contact your Hewlett-Packard support representative.
DCCERR 2 DCC ERROR P-L, (reply status SSSSSSSS, msg descriptors MMM).
(DCCERR=2)
Cause: A problem exists with interprocess communication.
Action: Contact your Hewlett-Packard support representative.
DCCERR 3 DCC ERROR P-L, Configuration file open error SSSSSSSS.
(DCCERR=3)
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.
DCCERR 4 DCC ERROR P-L, (NMCONF record error SSSSSSSS). NM Path:
NMMGRpath (DCCERR=4)
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.
DCCERR 5 DCC ERROR P-L, configuration record data was invalid. NM
Path: NMMGRpath (DCCERR=5)
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.
DCCERR 6 DCC ERROR P-L, (HLIO status SSSSSSSS, ldev LLL). (DCCERR=6)
Cause: A problem exists with the high-level I/O services.
Action: Contact your Hewlett-Packard support representative.
DCCERR 7 DCC ERROR P-L, (Buffer manager status SSSSSSSS). (DCCERR=7)
Cause: A problem exists with the datacomm buffers.
Action: Contact your Hewlett-Packard support representative.
DCCERR 8 DCC ERROR P-L, (External procedure not found). (DCCERR=8)
Cause: A problem exists with DCC execution.
Action: Contact your Hewlett-Packard support representative.
DCCERR 9 DCC ERROR P-L, (Memory management status SSSSSSSS). (DCCERR=9
Cause: A problem with the system occurred; the DCC cannot obtain memory.
Action: Contact your Hewlett-Packard support representative.
DCCERR 10 DCC ERROR P-L, (Ports status SSSSSSSS). (DCCERR=10)
Cause: A problem with the DCC or the port's subsystem occurred.
Action: Contact your Hewlett-Packard support representative.
DCCERR 11 DCC ERROR P-L, time out on reply msg, descriptors MMM.
(DCCERR=11)
Cause: The DCC did not receive a reply message within the allotted time.
Action: Contact your Hewlett-Packard support representative.
DCCERR 12 DCC ERROR P-L, too many DTCs configured. (DCCERR=12)
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.
DCCERR 13 DCC ERROR P-L, link name specified for the DTS does not
exist. (DCCERR=13)
Cause: The link name configured in NMMGR on the DTS Configuration screen
does not exist.
Action: Go to the DTS Configuration screen and enter the link name.
DCCERR 14 DCC ERROR P-L, link name specified for the DTS is not
available. (DCCERR=14)
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 and connections.
DCCERR 15 DCC ERROR P-L, too many links configured. (DCCERR=15)
Cause: More than eight links are configured.
Action: Delete all unused links so that eight or less links are used.
DCCERR 16 DCC ERROR P-L, message received on wrong subque. (DCCERR=16)
Cause: A problem exists with the interprocess communication.
Action: Contact your Hewlett-Packard support representative.
DCCERR 17 DCC ERROR P-L, unrecognized message received. (DCCERR=17)
Cause: A problem exists with the interprocess communication.
Action: Contact your Hewlett-Packard support representative.
DCCERR 18 DCC ERROR P-L, internal DCC logic error. (DCCERR=18)
Cause: A problem internal to the DCC exists.
Action: Contact your Hewlett-Packard support representative.
DCCERR 19 DCC ERROR P-L, Link error status. (DCCERR=19)
Cause: A problem occurred while configuring the link manager.
Action: Contact your Hewlett-Packard support representative.
DCCERR 20 DCC WARNING P-L, Add LDEV to class failure (HLIO status
SSSSSSSS, ldev LLL). (DCCERR=20)
Cause: A class contains more than 255 devices, or a conflict in class
names exists.
Action: Run SYSGEN to verify the conflict.
DCCERR 21 DCC ERROR P-L, Configuration file close error SSSSSSSS.
(DCCERR=21)
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.
DCCERR 22 NLIO status SSSSSSSS, ldev LLL) (DCCERR=22)
Cause: A problem exists in the NLIO services.
Action: Contact your Hewlett-Packard support representative.
DCCERR 23 DCC ERROR P-L, Blank NODENAME. (DCCERR=23)
Cause: A host node name was not configured.
Action: Configure a host node name.
DCCERR 24 DCC ERROR P-L, Configuration file not validated. (DCCERR=24)
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 and then revalidate the file.
DCCERR 25 DCC ERROR P-L, X.25 Level 1&2 not configured in NMMGR, status
SSSSSSSS. (DCCERR=25)
Cause: Level 1&2 of the X.25 network management structure have not been
configured in NMMGR.
Action: Supply the required information in the X.25 Level 1&2 screen in
NMMGR.
DCCERR 26 DCC ERROR P-L, X.25 Level 3 not configured in NMMGR, status
SSSSSSSS (DCCERR=26)
Cause: Level 3 of the X.25 network management structure have not been
configured in NMMGR.
Action: Supply the required information in the X.25 Level 3 screen in
NMMGR.
DCCERR 27 DCC ERROR P-L, Invalid card number specified, status
SSSSSSSS, card number = cardnumber. (DCCERR=27)
Cause: You have specified an invalid card number for the DTC type.
Action: For DTC 72MX, the valid range for card number is 0 to 3. For
DTC 48, the valid range for card number is 0 to 5. For DTC 16, you may
use card 0 and 1 for connector cards and card 2 for X.25 card.
DCCERR 28 DCC ERROR P-L, Invalid DTC type specified, status SSSSSSSS.
(DCCERR=28)
Cause: The NMCONFIG.PUB.SYS file may be corrupt.
Action: Use a backup configuration file, verify and update your
configuration, validate and cross-validate with SYSGEN, and reboot your
system. Keep the corrupt configuration file and report this condition to
your HP representative.
DCCWARN 100 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.
DCCWARN 101 DCC WARNING P-L, (Startup) cannot open NMCONFIG, status
SSSSSSSS. (DCCWARN=101)
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.
DCCWARN 102 DCC WARNING P-L, (Startup) cannot purge NMCONFIX, status
SSSSSSSS. (DCCWARN=102)
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.
DCCWARN 103 DCC WARNING P-L, (Startup) cannot open NMCONFIX, status
SSSSSSSS. (DCCWARN=103)
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.
DCCWARN 104 DCC WARNING P-L, (Startup) cannot create NMCONFIX, status
SSSSSSSS. (DCCWARN=104)
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 file system problems exist. Then,
verify that no hardware problems exist.
DCCWARN 105 DCC WARNING P-L, (Startup) cannot copy record from
NMCONFIX, status SSSSSSSS. (DCCWARN=105)
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.
DCCWARN 106 DCC WARNING P-L, (Startup) cannot copy record to NMCONFIG,
status SSSSSSSS. (DCCWARN=106)
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.
DCCWARN 107 DCC WARNING P-L, (Startup) cannot close NMCONFIG, status
SSSSSSSS. (DCCWARN=107)
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.
DCCWARN 108 DCC WARNING P-L, (Startup) cannot close NMCONFIX, status
SSSSSSSS. (DCCWARN=108)
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.