HP 3000 Manuals HP 3000 Manuals
Net Timers Logging Location Codes
1020 CLAS0003 Message: Out of resources
Cause: A free- pool entry was needed for a
timer-entry element, to hold information about a new
net timer being obtained, but the pool was empty. A
separate timer entry must exist for every net timer on
the system.
Action: No new timer was obtained. The system is
probably operating under a heavy load. Other
processes on the system have used up all the free
timer entries, or are starting timers with
granularities so small as to use up all the pool
entries for timer-intervals. Other processes on the
system will probably start seeing this problem as
well, though that should be a temporary condition.
One possible workaround is to configure a higher value
in NMMGR for the maximum number of TCP connections.
1040 CLAS0003 Message: Out of resources
Cause: A free- pool entry was needed for an interval-
head element, to link a net timer into a new interval,
but the pool was empty. A new interval is required
whenever there is no open interval positioned where a
timer entry needs one.
Action: If the error occurred when getting a new
timer, no new timer was obtained. If it occurred on a
reset, the timer was not reset, and has been left
stopped. The system is probably operating under a
heavy load. Other processes on the system have used
up all the free timer entries, or are starting timers
with granularities so small as to use up all the pool
entries for timer-intervals. Other processes on the
system will probably start seeing this problem as
well, though that should be a temporary condition.
One possible workaround is to configure a higher value
in NMMGR for the maximum number of TCP connections.
1060 CLAS0002 Message: Cannot free a systimer
Cause: When releasing a system timer following a
race-condition when that timer could not be cached,
the system routine Release_timer reported an error.
Timers must be released when the net timer cache is
full or not configured (PARM = status from
Release_timer).
Action: Unless there is corruption within system
timers, this probably indicates a Net Timers bug.
Another remote possibility is that the Net Timers port
data has been corrupted from outside, so other,
possibly serious problems may soon appear as well. In
addition, one system timer may have been lost; if this
continues, the system could eventually run out of
system timers. Submit an SR.
1080 CLAS0002 Message: Cannot reset a systimer
Cause: While attempting to stop, restart, or
reschedule an existing system timer, the system
routine Reset_ timer_ in_ heartbeats failed or
reported a status which was not expected given the
current state of Net Timers. Resetting a system timer
is a normal operation done whenever the first interval
in a timer list changes (PARM = status from Reset_
timer_ in_ heartbeats, PORT = address of timer list).
Action: Unless there is corruption within system
timers, this probably indicates a Net Timers bug.
Another remote possibility is that the Net Timers port
data has been corrupted from outside, so other,
possibly serious problems may soon appear as well.
All timers associated with the faulty system- timer
are now stalled, and will probably never pop.
Depending on your configuration, this may or may not
affect all timers on that system's network. Submit an
SR.
1120 CLAS0002 Message: Cannot get a systimer
Cause: While attempting to obtain a new system timer,
the system routine Get_ timer_ in_ heartbeats failed.
Getting a new system timer is done the first time each
configured timer list is used, and also during normal
processing of race conditions when no cached timer was
available (PARM = status from Get_ timer_ in_
heartbeats, PORT = address of timer list).
Action: Unless there is corruption within system
timers, the system has probably run out of timers;
this might be indicated by a PARM value of FFFE006E:
no entry available. If the error occurred when
getting a new timer, no new timer was obtained. If it
occurred on a reset, the timer was not reset and has
been left stopped; all timers to be associated with
that system timer are now stalled, and will probably
never pop. Depending on your configuration, this may
or may not affect all timers on that system's network.
Submit an SR.
1160 CLAS0003 Message: Cannot get interval head
Cause: This is supplemental logging to a previous Net
Timers error. While attempting to start a new net
timer or restart an existing one, as part of a
higher-level reset- or get- timer operation, it was
determined that a new interval was needed, but the
free pool was empty, preventing allocation of a new
interval- head element. A new interval is required
whenever there is no open interval positioned where a
timer entry needs one. (PORT = net timer ID)
Action: Review information regarding the previous
errors, for possible hints as to the cause. Other
processes on the system have used up all the free
entries in the pool.
1180 CLAS0002 Message: Timer list is stalled
Cause: This is supplemental logging to a previous Net
Timers error. While attempting to start a net timer
as part of a higher-level reset- or get-timer
operation, there was a problem resetting the system
timer associated with that net timer and others. A
timer list's system timer is normally reset whenever
insertion of the new net timer changed the first
interval in the list. (PORT = net timer ID)
Action: 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.
1220 CLAS0002 Message: Cannot start a timeout
Cause: This is supplemental logging to a previous Net
Timers error. While attempting to reschedule a
running net timer, the timer was successfully removed
from the old interval it was running in, but there was
a problem restarting it. To get the net timer running
again, all steps necessary to attach it to a new
interval must succeed. (PORT = net timer ID)
Action: 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.
2020 CLAS0002 Message: Not up for processing
Cause: An attempt was made to free a net timer before
or during Net Timers startup, or during or after
shutdown. Timers cannot be freed 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.
2030 CLAS0002 Message: Bad timer ID specified
Cause: An attempt was made to free 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 free that nonexistent timer. This
may lead to other errors or hangs in the calling
module. Submit an SR.
2040 CLAS0002 Message: Accessed a freed timer
Cause: An attempt was made to free a net timer for
which a deferred release has already 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 freed twice. (PORT = net timer ID).
Action: This probably means a Transport timer trap-
routine has accidentally re-freed a timer it already
freed. Another possibility is that a second processor
has attempted to free the same timer while that trap
routine was still executing; this might be unlikely
due to timing constraints. If necessary, submit an
SR.
2080 CLAS0002 Message: Accessed a freed timer
Cause: An attempt was made to free a net timer which
had already been freed, or a timer which was in some
sort of bad state. Since freed net timers can be
immediately reallocated to anyone, they cannot be
safely freed twice. (PORT = net timer ID).
Action: If you suspect the timer has not been freed,
another remote possibility is data corruption of the
timer entry. If necessary, submit an SR.
2100 CLAS0002 Message: Not up for processing
Cause: An attempt was made to get a net timer before
or during Net Timers startup, or during or after
shutdown. Timers cannot be obtained 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.
2105 CLAS0002 Message: Bad timer interval
Cause: An attempt was made to set a new net timer to
a negative time interval.
Action: No new timer was obtained. 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
"Submitting an SR" in appendix A of this manual.
2120 CLAS0003 Message: Cannot get timer entry
Cause: This is supplemental logging to a previous Net
Timers error. While attempting to get a new net
timer, it was discovered that the free pool was empty,
preventing allocation of a new timer entry element. A
separate timer entry must exist for every net timer on
the system.
Action: Review information regarding the previous
errors, for possible hints as to the cause. Other
processes on the system have used up all the free
entries in the pool.
2140 CLAS0002 Message: Cannot start a timeout
Cause: This is supplemental logging to a previous Net
Timers error. While attempting to start a new running
net timer, there was a problem getting it into a
running timer list. For the new net timer to run, it
must be successfully attached to an interval in a
timer list having a running system timer.
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.
2160 CLAS0002 Message: Not up for processing
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.
2170 CLAS0002 Message: Bad timer ID specified
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.
2175 CLAS0002 Message: Bad timer interval
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 "Submitting an SR"
in appendix A of this manual.
2180 CLAS0002 Message: Accessed a freed timer
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.
2200 CLAS0002 Message: Cannot reset a timeout
Cause: This is supplemental logging to a previous Net
Timers error. While attempting to reschedule a
running net timer, there was a problem removing the
timer from the old interval it was running in, or a
problem restarting it. Both steps must succeed for
the rescheduling to work. (PORT = net timer ID).
Action: The timer has been left in an indeterminate
state. 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.
2220 CLAS0002 Message: Cannot start a timeout
Cause: This is supplemental logging to a previous Net
Timers error. A problem occurred while attempting to
restart a stopped net timer. To run a previously-
stopped net timer, the timer must be successfully
attached to an interval in a timer list having a
running system timer. (PORT = net timer ID).
Action: The timer has been left in an indeterminate
state. 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.
2240 CLAS0002 Message: Cannot start a timeout
Cause: This is supplemental logging to a previous Net
Timers error. A problem occurred while attempting to
reschedule a popping net timer. By definition a
popping net timer is already stopped, so to get it
running again it needs to be successfully attached to
an interval in a timer list having a running system
timer. (PORT = net timer ID).
Action: The timer has been left in an indeterminate
state. Probably a Transport timer trap routine was
attempting to reset the timer. 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.
2260 CLAS0002 Message: Accessed a freed timer
Cause: An attempt was made to restart a net timer
which had already been freed, or a timer which was in
some sort of bad state. Since freed net timers can be
immediately reallocated to anyone, they cannot be
safely restarted after freeing. (PORT = net timer
ID).
Action: If you suspect the timer has not been freed,
another remote possibility is data corruption of the
timer entry. If necessary, submit an SR.
2300 CLAS0002 Message: Accessed a freed timer
Cause: An attempt was made to stop a net timer which
had already been freed, or a timer which was in some
sort of bad state. Since freed net timers can be
immediately reallocated to anyone, they cannot be
safely stopped after freeing. (PORT = net timer ID).
Action: If you suspect the timer has not been freed,
another remote possibility is data corruption of the
timer entry. If necessary, submit an SR.
3080 CLAS0002 Message: Timer list is stalled
Cause: This is supplemental logging to a previous Net
Timers error. While getting ready to pop one or more
net timers, there was a problem restarting the system
timer associated with the timer list those net timers
came from. Unless the list's system timer is
restarted, no other net timers on that list will pop
from now on.
Action: 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.
3100 CLAS0003 Message: Bad trap call frees timer
Cause: While popping a net timer, a Transport timer
trap- routine reported a nonzero status. In response,
Net Timers has freed the timer entry which popped
(PARM = status from trap routine, PORT = net timer
ID).
Action: A part of the normal operation of Net Timers,
this information is provided for Transport debugging
purposes only. Any SR filed or action taken should
address the problem of the failing trap routine, whose
error status was reported in PARM. Operation of Net
Timers should be unaffected.
3120 CLAS0003 Message: Bad/unknown message type
Cause: Instead of a timeout or other supported
message, the Net Timers port received a message which
was not recognized or supported. Illegal messages
cannot be acted upon; they are dropped and their
message frames returned to the system (PORT = address
of message frame, PARM = message descriptor).
Action: The operation of Net Timers should be
unaffected. However, some other module on the system
seems to be sending the wrong messages to the wrong
places. Submit an SR, specifying the PARM value which
was logged.
3140 CLAS0002 Message: Failed reset-timer test
Cause: Reported by Hewlett-Packard internal tests
only. This indicates resetting of a popping net timer
yielded a status other than one indicating the timer
was currently popping.
Action: This should never been seen outside the
factory; submit an SR.
3160 CLAS0002 Message: Failed trap-call test
Cause: Reported by Hewlett-Packard internal tests
only. This indicates a net timer trap- routine
reported a false error, leading to release of the
popped timer.
Action: This should never been seen outside the
factory; submit an SR.
3180 CLAS0002 Message: Failed free-timer test
Cause: Reported by Hewlett-Packard internal tests
only. This indicates freeing of a popping net timer
yielded a status other than one indicating the timer
was currently popping.
Action: This should never been seen outside the
factory; submit an SR.
3200 CLAS0002 Message: Failed free-timer test
Cause: Reported by Hewlett-Packard internal tests
only. This indicates freeing of a popping net timer,
already previously freed, yielded a status other than
one indicating the timer was not in use.
Action: This should never been seen outside the
factory; submit an SR.
3220 CLAS0002 Message: Failed reset timer test
Cause: Reported by Hewlett-Packard internal tests
only. This indicates resetting of a popping net
timer, previously freed, yielded a status other than
one indicating the timer was not in use.
Action: This should never been seen outside the
factory; submit an SR.
3240 CLAS0002 Message: Cannot freeze memory
Cause: While attempting to freeze a caller- specified
statistics buffer into memory, the system routine
Freeze reported an error. Freezing is required, to
avoid page faults while Net Timers data structures are
locked for the statistics report (PARM = status from
Freeze).
Action: Net Timers will continue to run as normal,
though no statistics data was obtained. Whichever
utility was trying to read Net Timers information did
not get it. Submit an SR.
3280 CLAS0003 Message: Data truncated
Cause: A caller-specified statistics buffer was too
small to hold the entire statistics block. Partial
statistics- reads are not supported; to read
statistics only, the caller must specify the exact
length of the Net Timers statistics block.
Action: No statistics were returned. If this error
was reported by a Hewlett-Packard-supplied program,
submit an SR against that program.
3300 CLAS0003 Message: Data truncated
Cause: A caller-specified statistics buffer was large
enough to hold statistics, but not large enough to
hold all the timer map data. Net Timers ran out of
room trying to record a timer list head. Partial
reads of timer- map data are not recommended.
Action: Statistics were returned, but the timer map
data returned is incomplete; caller should have
specified a larger buffer. If this error was reported
by a Hewlett-Packard-supplied program, submit an SR
against that program.
3320 CLAS0003 Message: Data truncated
Cause: A caller-specified statistics buffer was large
enough to hold statistics, but not large enough to
hold all the timer map data. Net Timers ran out of
room trying to record a timer interval. Partial reads
of timer- map data are not recommended.
Action: Statistics were returned, but the timer map
data returned is incomplete; caller should have
specified a larger buffer. If this error was reported
by a Hewlett-Packard-supplied program, submit an SR
against that program.
3340 CLAS0003 Message: Data truncated
Cause: A caller-specified statistics buffer was large
enough to hold statistics, but not large enough to
hold all the timer map data. Net Timers ran out of
room trying to record a timer entry. Partial reads of
timer- map data are not recommended.
Action: Statistics were returned, but the timer map
data returned is incomplete; caller should have
specified a larger buffer. If this error was reported
by a Hewlett-Packard-supplied program, submit an SR
against that program.
3360 CLAS0002 Message: Cannot unfreeze memory
Cause: While attempting to unfreeze a caller-
specified statistics buffer previously frozen into
memory, the system routine Unfreeze reported an error.
Unfreezing is necessary to avoid memory fragmentation
over time (PARM = status from Unfreeze).
Action: Net Timers will continue to run as normal,
though no statistics data was obtained, and some
memory space may be lost until the next system
startup. Submit an SR.
3380 CLAS0002 Message: Not up for processing
Cause: An attempt was made to perform a Net Timers
control operation during Net Timers startup, or during
or after shutdown. Control operations cannot be
performed unless Net Timers is completely up.
Action: No control operation was performed. If this
occurs during network shutdown, it can probably be
ignored. If it occurs at any other time, submit an
SR.
3400 CLAS0003 Message: Bad/unknown function code
Cause: An unrecognized or unsupported function code
was passed in a call to NETTMR_ CONTROL. Only
supported control functions can be acted on.
Action: The call was ignored; the operation of Net
Timers should be unaffected. However, some other
module on the system seems to be passing bad function
codes. If necessary, submit an SR.
4020 CLAS0004 Message: Not up, stop ignored
Cause: An attempt was made to shut Net Timers down
before a successful startup, or during or after a
shutdown. Multiple shutdowns 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.
4040 CLAS0004 Message: Stopping
Cause: Net Timers is being shut down (PARM = Net
Timers port data address).
Action: No action is required.
4060 CLAS0002 Message: Unfreed systimers remain
Cause: While releasing inuse system timers during
shutdown, the system routine Release_timer reported an
error. All inuse timers are normally deallocated
during any shutdown of Net Timers (PORT = unfreed
system timer ID, PARM = status from Release_timer).
Action: Net Timers will report the failure as a
warning and continue with the shutdown. Unless there
is corruption within system timers, this probably
indicates a Net Timers bug. Another remote
possibility is that the Net Timers port data has been
corrupted from outside, so other, possibly serious
problems may soon appear as well. In addition, one
system timer may have been lost; if this continues,
the system could eventually run out of system timers.
Submit an SR.
4100 CLAS0002 Message: Unfreed ports remain
Cause: While Net Timers was attempting to release its
message port during shutdown, the system routine
Purge_port reported an error. Purging the port is a
normal part of resource cleanup during any Net Timers
shutdown. Releasing port ownership during startup
should have insured the port could be purged later,
even if by a different process (PORT = Net Timers port
ID, PARM = status from Purge_port).
Action: Net Timers will report the failure as a
warning and continue with the shutdown. One message
port may have been lost, but probably not any message
frames; if this continues, the system could eventually
run out of ports. Submit an SR.
4120 CLAS0002 Message: Frozen memory remains
Cause: During shutdown, while Net Timers was
attempting to unfreeze its previously frozencontext
memory (port data area or PDA), the system routine
Unfreeze reported an error. Unfreezing the PDA is
normally done during any Net Timers shutdown, in
preparation for freeing the PDA object (PORT = port
data address, PARM = status from Unfreeze).
Action: Net Timers will report the failure as a
warning and continue with the shutdown. Some memory
space may be lost until the next system startup, but
unless this happens repeatedly, the system should
continue to run. Submit an SR.
4140 CLAS0002 Message: Unfreed objects remain
Cause: During shutdown, while Net Timers was
attempting to release its context memory (port data
area or PDA), the system routine Release_object
reported an error. Freeing of the PDA is the final
stage of resource cleanup by Net Timers during any
shutdown (PORT = port data address, PARM = status from
Release_ object).
Action: Net Timers will report the failure as a
warning and continue with the shutdown. Some memory
space may be lost until the next system startup, but
unless this happens repeatedly, the system should
continue to run. Submit an SR.
4280 CLAS0004 Message: NMMGR fail, defaults used
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.
4300 CLAS0004 Message: Already up, start ignored
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.
4320 CLAS0002 Message: Create Object Failed
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.
4340 CLAS0002 Message: Cannot freeze memory
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).
Action: Depending on the PARM value, your system
load, and your current configuration, it is possible
too much resident memory is already in use on your
system to support the number of timers required by
maximum the number of TCP connections currently
configured in NMMGR, and thus the required PDA size.
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.
4360 CLAS0002 Message: Find Procedure Failed
Cause: During startup, when attempting to load the
address of an NL. PUB. SYS procedure to service the
Net Timers port, the system routine Hpgetsysplabel
reported an error trying to locate the system routine
nettmr_ ics_ server. This procedure is required so
the system will know who to call to process timeout
messages arriving at the port (PARM = status from
Hpgetsysplabel).
Action: Net Timers failed to start; instead it
cleaned up after itself and reported an error. If you
just installed a new release of the Transport
subsystem, possibly the installation was incorrect,
incomplete, or corrupted. There is also a remote
possibility the system has run out of room for
dynamically- loaded procedures. If necessary, submit
an SR.
4380 CLAS0002 Message: Create Port Failed
Cause: During startup, while attempting to create a
message port to receive system-timer timeout messages,
the system routine Create_ port failed. The port is
needed as a destination for timeout messages for the
system timers which drive Net Timers (PARM = status
from Create_ port).
Action: Net Timers failed to start; instead it
cleaned up after itself and reported an error. If
your system is heavily loaded, it is possible the
system has run out of ports; if you think this is the
case, you might try reducing system load, however a
significant reduction would be needed to allow all of
Transport to start up. If necessary, submit an SR.
4400 CLAS0002 Message: Cannot disown port
Cause: During startup, after successful creation of a
port for Net Timers, the system routine Port_ control
reported an error trying to release CP's ownership of
the port. Port ownership must be released in case a
different process deletes the Net Timers port later
(PARM = status from Port_control).
Action: Net Timers failed to start; instead it
cleaned up after itself and reported an error. Submit
an SR.
4420 CLAS0002 Message: Semaphore setup error
Cause: During startup initialization of the Net
Timers context memory (port data area or PDA), the
system routine Cb_init reported an error trying to
clear the Net Timers semaphore. The semaphore is
required because multiple callers can access the same
timer list, and that list can pop at any time (PARM =
status from Cb_init).
Action: Net Timers failed to start; instead it
cleaned up after itself and reported an error. Submit
an SR.
4440 CLAS0004 Message: Starting
Cause: Net Timers is being started up (PARM = Net
Timers port data address).
Action: This logging is provided for information
purposes only. No action is required.