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

Chapter 19 439
Logging Location Codes
Net Timers Logging Location Codes
ACTION: No new timer was obtained. Review information regarding
the previous errors, for possible hints as to the cause. If necessary,
submit an SR, noting this and previous Net Timers errors.
MESSAGE: Not up for processing
2160 CLAS0002 CAUSE: An attempt was made to reset a net timer before or during Net
Timers startup, or during or after shutdown. Timers cannot be reset
unless Net Timers is completely up. (PORT = net timer ID).
ACTION: If this occurs during network shutdown, it can probably be
ignored. If it occurs at any other time, submit an SR. Whether the net
timer ID being freed was valid or not is not known.
MESSAGE: Bad timer ID specified
2170 CLAS0002 CAUSE: An attempt was made to reset a net timer having an ID of zero
(PARM = 0).
ACTION: There is a bug in the calling module. Probably that module
previously attempted to get a timer, but ignored an error reported by
Net Timers and saved the returned ID of zero for later use. It is now
attempting to reset that nonexistent timer. This may lead to other
errors or hangs in the calling module. Submit an SR.
MESSAGE: Bad timer interval
2175 CLAS0002 CAUSE: An attempt was made to reset an existing net timer to a
negative time interval (PORT = net timer ID).
ACTION: The timer was not reset from its current condition, running or
stopped. Negative intervals are not allowed. There is a bug in the
calling module. Probably that module is doing its own timing by
subtracting timestamps over a period of time, and has made an
incorrect calculation. See Appendix A, “Submitting an SR,” of this
manual.
MESSAGE: Accessed a freed timer
2180 CLAS0002 CAUSE: An attempt was made to reset a net timer for which a deferred
release has been posted. Deferred release is used only during the pop of
a timer, since it cannot be freed until the trap routine exits, completing
the pop. Since freed net timers can be immediately reallocated to
anyone, they cannot be safely reset after freeing. (PORT = net timer
ID).
ACTION: This probably means a Transport timer trap- routine has
accidentally reset a timer it already freed. Another possibility is that a
second processor has attempted to reset the freed timer while that trap
routine was still executing; this might be unlikely due to timing
constraints. If necessary, submit an SR.