Lane writes:
> Anybody have any experience with SA2505 on 6.0pp2+? I didn't have the time
> to take a memory dump so the RC won't/can't tell me anything.
>
> The full text is
>
> System abort 2505 from subsys 202
> Secondary Status Info=-2 Subsys=110
> System Halt 7,$09c9
>
> FLT DEAD
>     b807
>     0109
>     02c9
>
>
> Thanks,
> Lane

The full description of an SA2505 as taken from an actual SA2505 is this:

SYSTEM ABORT #740 FROM SUBSYSTEM #122 (Port (IPC) Facility)
The procedure ENABLE_TIMEOUT can not get timer for time out; bad status
from GET_TIMER.

SECONDARY STATUS: INFO = #-2, SUBSYSTEM = #110 (Clock/Timers Manager)
GET_TIMER/GET_TIMER_IN_TICKS failed to get a new timer entry from TABLE
MANAGEMENT.

The 'timer globals' timer table is full most likely because something that has been consuming
these entries hasn't been releasing them.

Without a memory dump it really is difficult to determine who or what did this because timer
entries are a common consumable in the OS.

You can monitor the timer table with Threshold Manager to see if it might be filling up which
could be indicative of a 'leak' of sorts. If you see consumption rising it should be possible
then to try to make some determination of use before the system actually rolls over. There
is no way I know of to free up orphaned entries but knowledge that the table is approaching
overflow would let you plan the downtime and get a memory dump.

Hope this helps,

Bill
HP/CSY