DCC Error Messages [ Configuring Systems for Terminals, Printers, and Other Serial Devices ] MPE/iX 5.5 Documentation
Configuring Systems for Terminals, Printers, and Other Serial Devices
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 restart DTS. If the error
persists, replace the file, validate it, and restart DTS.
(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 restart DTS.
(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, status
SSSSSSSS). (DCCERR=8)
Cause: A problem exists with DCC execution.
Action: Contact your Hewlett-Packard support representative.
(DCCERR 9) DCC ERROR P-L, (Memory management error 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: Delete the excess DTCs from the NMCONFIG.PUB.SYS file and
restart DTS.
(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, then
restart DTS.
(DCCERR 14) DCC ERROR P-L, link name specified for the DTS is not
available (link status SSSSSSSS). (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, then restart
DTS.
(DCCERR 15) DCC ERROR P-L, too many links configured. (DCCERR=15)
Cause: More that eight links are configured.
Action: Delete all unused links so that eight or less links are used,
then restart DTS.
(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 SSSSSSSS. LLIO path:
NMMGRpath (DCCERR=19)
Cause: A problem occurred while configuring the link manager.
Action: Contact your Hewlett-Packard support representative.
(DCCERR 20) DCC ERROR 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, or NMCONFIG.PUB.SYS was not cross-validated with files
created with SYSGEN.
Action: Run SYSGEN to verify the conflict.
(DCCERR 21) DCC WARNING P-L, Configuration file close error SSSSSSSS.
(DCCWARN=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, status
SSSSSSSS. (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, (DCC 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, (DCC 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 restart DTS.
Keep the corrupt configuration file and report this condition to your HP
representative.
(DCCERR 29) DCC ERROR P-L, DTC is not configured, NM path: NMMGRpath
(DCCERR=29)
Cause: A dynamic configuration change was attempted on a DTC that DCC
has not yet created.
Action: Delete the DTC from the NMCONFIG file and run DTCCNTRL. Then add
the DTC back to the NMCONFIG.PUB.SYS file.
(DCCERR 30) DCC ERROR P-L, Ldev is already configured, (ldev: LLL).
(DCCERR=30)
Cause: The ldev #LLL is already configured on the system.
Action: Validate the NMCONFIG.PUB.SYS file and then cross-validate with
SYSTEM and then restart DTS.
(DCCERR 31) DCC ERROR P-L, Duplicate node address or DTC node name. NM
path: NMMGRpath (DCCERR=31)
Cause: The node address or DTC nodename of a DTC that was added
dynamically or automatically is already configured on an existing DTC.
Action: Verify the node address and nodename of the new DTC and retry
the operation. If the error occurs again, check the configurations of
the other DTCs that are in the NMCONFIG.PUB.SYS file. If the duplicate
entry is not found then restart DTS.
(DCCERR 32) DCC ERROR P-L, DTC name is already configured. NM PATH:
NMMGRpath (DCCERR=32)
Cause: The DTC name of a DTC that was added dynamically or automatically
is already configured.
Action: Verify that the DTC name doesn't already exist in the NMCONFIG
file. If the DTC name doesn't exist in the NMCONFIG file then restart
DTS or pick a different name for the DTC.
(DCCWARN 33) DCC WARNING P-L, Ldev not added to class. (HLIO status
SSSSSSSS, ldev LLL). (DCCWARN=33)
Cause: A class contains more than 255 devices, a conflict in class names
exists, or NMCONFIG.PUB.SYS was not cross-validated with files created
with SYSGEN.
Action: The ldev is still usable but will not be in the class. Validate
the NMCONFIG.PUB.SYS file and run SYSGEN to verify conflict.
(DCCERR 34) DCC ERROR P-L, Delete Ldev from class failure. (HLIO
status SSSSSSSS, ldev LLL). (DCCERR=34)
Cause: The DTC name of a DTC that was added dynamically or automatically
is already configured.
Action: A problem occurred while deleting the ldev from a class.
(DCCWARN 35) DCC WARNING P-L, Ldev not deleted from class. (HLIO
status SSSSSSSS, ldev LLL). (DCCWARN=35)
Cause: The ldev has already been deleted from the class or the class no
longer exists on the system.
Action: This is a warning. If it persists, make sure no other system
utilities are being used to delete classes or remove devices from
classes.
(DCCERR 36) DCC ERROR P-L, Failed to delete ldev LLL. Ldev still in
use. (DCCERR=36)
Cause: An attempt was made to delete an ldev that is logged on or is
SPOOLED.
Action: Logoff the session using the device or stop the spooler on the
device and retry the operation.
(DCCERR 38) DCC ERROR P-L, Failed to delete ldev LLL. (HLIO status
SSSSSSSS). (DCCERR=38)
Cause: An internal error occurred while deleting an ldev. The ldev is
probably unusable.
Action: Do a DTS shutdown and restart. If the problem persists, then
reboot the system.
(DCCERR 39) DCC ERROR P-L, Unable to stop spooler on ldev LLL. (Status
SSSSSSSS). (DCCERR=39)
Cause: An internal error occurred while stopping the spooler during a
DTS shutdown with forced=y.
Action: Do a DTS restart and check the device. If the device is not
operating then shutdown and restart DTS.
(DCCERR 40) DCC ERROR P-L, nn dev(s) are owned, shutdown not done.
(DCCERR=40)
Cause: While attempting a DTS shutdown, nn ldevs were found to be still
logged on or spooled. The shutdown operation was aborted.
Action: Logoff or stop the spooler on the devices that are still in use.
Retry the DTS shutdown.
(DCCERR 41) DCC ERROR P-L, LLIO error (Status: SSSSSSSS, path:
NMMGRpath) (DCCERR=41)
Cause: A problem exists with the low-level I/O services.
Action: Contact your Hewlett-Packard support representative.
(DCCERR 42) DCC ERROR P-L, Too few non-nailed ldevs found. (DCCERR=42)
Cause: While deleting non-nailed ldevs, there were fewer unused
non-nailed ldevs found to delete than requested.
Action: Logoff sessions that are using non-nailed ldevs and retry the
operation.
(DCCWARN 43) DCC ERROR P-L, Unexpected procedure label status. (Status
SSSSSSSS) (DCCWARN=43)
Cause: A internal problem exists with process management.
Action: Contact your Hewlett-Packard support representative.
(DCCERR 44) DCC ERROR P-L, Can't update data in NMCONFIG file. (Status
SSSSSSSS) NM Path: NMMGRpath. (DCCERR=44)
Cause: While performing Automatic configuration of a DTC, DCC was not
able to add the configuration to the NMCONFIG.PUB.SYS file.
Action: Make sure the NMCONFIG file is not in use by another session.
Check that the file is not full. Compress the file to free unused space.
(DCCERR 45) DCC ERROR P-L, Not enough room in NMCONFIG file. (Status
SSSSSSSS) (DCCERR=45)
Cause: There is not enough room left in the NMCONFIG.PUB.SYS file to
successfully add a new DTC automatically.
Action: Compress the NMCONFIG.PUB.SYS file to remove unused space and
optionally expand the size with NMMGR. Retry the operation.
(DCCERR 47) DCC ERROR P-L, Time out waiting for DTC boot request.
(DCCERR=47)
Cause: While automatically adding a new DTC no boot request was received
within the allowed time. The DTC is either powered off or the LAN
address specified is not correct.
Action: Make sure the DTC is powered on and the correct LAN address is
specified.
(DCCWARN 48) DCC WARNING P-L, (LLIO status SSSSSSSS) (DCCWARN=48)
Cause: An internal problem has occurred with low-level I/O.
Action: This is a warning. If it persists contact your Hewlett-Packard
support representative.
(DCCWARN 49) DCC WARNING P-L, Ldev LLL is unusable until next DTS
restart. (DCCWARN=49)
Cause: The ldev was being accessed programatically when a DTS Shutdown
was performed and the forced=y option was specified.
Action: Logoff the session or job that was accessing the device and
restart DTS. Perform another DTS shutdown and restart.
(DCCWARN 50) DCC WARNING P-L, Waiting 30 sec for ldevs to become free.
(DCCWARN=50)
Cause: One or more ldevs were in use when DTS shutdown with the forced=y
option specified. DCC is waiting for the reset and/or STOPSPOOL to
complete.
Action: No action needed. DCC will proceed automatically.
(DCCWARN 51) DCC WARNING P-L, Dynamic configuration is disabled.
(DCCWARN=51)
Cause: DCC could not find the Dynamic ID in the config file.
Action: Perform a DTS shutdown and restart. If the warning persists,
contact your Hewlett-Packard support represnentative.
(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) can not 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) can not 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) can not 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) can not 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) can not 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) can not 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) can not 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) can not 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.
MPE/iX 5.5 Documentation