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

Chapter 21 509
Logging Location Codes
Control Process Logging Location Codes
error trying to add the name of the file into a CM Port Dictionary entry
named “NMCONFIG” (PARM = 16-bit result code returned by the call
to dict_add). The entry was used as a way to partially lock the file, so
NMMGR could tell Transport was up and running. The CM Port
Dictionary is an operating system lookup service used by, but not part
of, Transport.
ACTION: This error was not fatal, and network startup continued.
However, additional errors will occur later when NETCP tries to delete
the Dictionary entry (see error 609). In addition, assumptions made by
Transport and NMMGR about the partial lock on the file will not be
valid; all NMMGR access to the NMCONFIG file during the time this
instance of Transport is up should be avoided. Restart the network. If
the problem persists, see Appendix A , “Submitting a CR,” of this
manual.
618 CLAS0002 MESSAGE: INTERNAL ERROR; Data dictionary error
CAUSE: While starting the X25 protocol module for an X25 network that
was being started, NETCP encountered an error trying to add a
linkname it created for one of the X25 devices, into a CM Port
Dictionary entry (PARM = 16-bit result code returned by the call to
dict_add). The CM Port Dictionary is an operating system lookup
service used by, but not part of, Transport. There should be one entry
per X25 device, named "X25.linkid", where “linkid” consists of 4
unprintable bytes defining the binary SDI link ID for that link,
dynamically assigned by the Link Support Services subsystem.
ACTION: This error was not fatal, and network startup continued.
However, additional errors will occur later when NETCP tries to delete
the linkname (see error 660). In addition, certain X25 operations may
not work correctly. Restart the network. If this problem continues, see
Appendix A , “Submitting a CR,” of this manual.
619 CLAS0002 MESSAGE: INTERNAL ERROR; Device open
CAUSE: While attempting to start a device on an existing NI type other
than a ROUTER, NETCP encountered an error trying to create a frozen
inbound buffer pool for that device’s reads (PARM = 32-bit status
returned by the call to cp_get_read_pool). Always preceded by
another error indicating the original failure (see error 404).
ACTION: The device did not start. Check the packet size configured in
the NMCONFIG file; for non LAPB links, pool creation parameters are
computed from the base figures found in this file. Depending on the
error, it is possible too much frozen memory is being used by the
system, but this can change with time. Use GLANCEXL or a similar
utility to check memory usage by the system. If these are not the causes
and the problem persists even if retried after a suitable waiting period,
see Appendix A , “Submitting a CR,” of this manual.