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

Chapter 18 395
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
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.
199 ($C7) 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.
ACTION: 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 or DTS, use the VALIDATE
function to validate the network configuration. Correct any
configuration errors and retry the operation.
200 ($C8) MESSAGE: Cannot validate configuration file.
CAUSE: After successfully reading configuration data for a link being
started, the link module configurator checked the data and found it was
not valid. For NS/3000, probably the link type and NI type do not
match.
ACTION: Using NMMGR, verify the path LINK.linkname exists in the
NMCONFIG file and is either a LAPBMUX link type. If the subsystem
being started is NS, verify the link type matches the NI type for the
network being started. If these are not the problem, an incorrect
version of NMMGR may have been used to create the NMCONFIG file
on your system. Run NMMAINT.PUB.SYS;PARM=82 to check versions of
NMMGR components. The format of your NMCONFIG file may be
incompatible with the link driver version installed on your system. Run
NMMGRVER.PUB.SYS to update your NMCONFIG file to a newer version,
or restore an older version from a backup tape, whichever is
appropriate. If the problem still occurs, contact your Hewlett-Packard
Representative for assistance in using NMMGR to configure WAN Sync
MUX links.