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

446 Chapter19
Logging Location Codes
Net Timers Logging Location Codes
MESSAGE: NMMGR fail, defaults used
4280 CLAS0004 CAUSE: While attempting to compute its configuration limits from the
NETXPORT. GPROT. TCP node of the NMCONFIG. PUB. SYS file, the
system routine Nmconfgetdata reported an error. Unable to read
config data, a default configuration was selected as a backup just to get
the network going (PARM = status from Nmconfgetdata).
ACTION: This failure was reported as a warning and Net Timers then
continued with the startup, using a large default configuration. It is
unlikely the default configuration will match your needs as well as a
computed one, however your network may still run correctly. Check to
make sure you have configured the TCP protocol into your network,
specifying some maximum number of connections. Also check to make
sure the NMCONFIG file is available and not being accessed at the
current time. If necessary, submit an SR, specifying the PARM value
from the logging message.
MESSAGE: Already up, start ignored
4300 CLAS0004 CAUSE: An attempt was made to start Net Timers up during or after a
successful startup, but before a complete shutdown. Multiple startups
are not allowed.
ACTION: No harm was done, however some other module on the
system, possibly CP, seems to be confused. If necessary, submit an SR.
MESSAGE: Create Object Failed
4320 CLAS0002 CAUSE: After Net Timers computed its configuration during startup,
an attempt to allocate context memory (port data area or PDA) using
the system routine Create_object, failed. The PDA is where all data
structures needed to operate Net Timers must reside (PARM = status
from Create_object).
ACTION: Depending on the PARM value, your system load, and your
current configuration, it is possible not enough free memory exists on
your system to support the number of timers required by maximum the
number of TCP connections currently configured in NMMGR. If this
seems likely, you might try starting your network sooner after system
startup, or possibly reducing the number of TCP connections
configured. If necessary, submit an SR.
MESSAGE: Cannot freeze memory
4340 CLAS0002 CAUSE: After Net Timers successfully allocated an object for its
context memory (port data area or PDA), the system routine Freeze
reported an error tying to make the entire PDA present in physical
memory. The entire PDA must be frozen so it can be accessed from the
Interrupt Control Stack by Transport, and during timer pops (PARM =
status from Freeze).