NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 18 409
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
hardware configuration. If necessary, change NMCONFIG or contact
your Hewlett-Packard Representative for assistance in determining
paths or correcting bus hardware problems.
1480 CLAS0001 MESSAGE: Cannot open configuration file.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator encountered an error while trying to open the
configuration file (“Cause” = 32-bit status from the call to nmconfopen).
ACTION: The module configurator cleaned up and returned an error to
the subsystem.
Verify an NMCONFIG.PUB.SYS file exists. If so, try to verify its format
matches rest of the operating system. If the system was updated, you
may need to run NMMGRVER.PUB.SYS to convert the file to a newer
format. If the system was backdated, you may need to restore an older
copy of NMCONFIG from a backup tape.
Perform a :LISTF,3 command and make sure the file is not protected
by a lockword, and that the user starting the link has the necessary
access rights to open the file.
Perform a :DSTAT ALL command and make sure the disk drive the file
resides on is present and mounted. Make sure the file resides on Ldev 1.
If not, use Fcopy and a file equation with a “;DEV=1” option to force a
copy of the file onto Ldev 1.
Perform a :SHOWPROC 1;TREE;SYSTEM command and verify an
NMFILE process exists. If not, shut down and restart the system, and
retry the operation. If the problem persists, contact your
Hewlett-Packard Representative for assistance with NMCONFIG file
open problems.
1500 CLAS0001 MESSAGE: Cannot read from configuration file.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator was able to open the configuration file, but
encountered an error while trying to data for the link being started
(“Cause” = 32-bit status from the call to nmconfopen).
ACTION: The module configurator cleaned up and returned an error to
the subsystem.
Using NMMGR, verify the path LINK.linkname exists in the
NMCONFIG file and is the exact same linkname which is now being
started. Verify the “Data=Y” flag is set at the top of that LINK screen
(meaning that ENTER has been pressed to save the configuration data
there). If the link is being used with NS, use the VALIDATE function to
validate the network configuration. Correct any configuration errors
and retry the operation.