Just moments ago I said, without paying attention:

> 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.

Gee, that looks like an SA740 and not an SA2505... which through the wonders of cut'n'paste
I managed to send out.

Here would be the _actual_ SA2505 message taken from the _actual_ SA2505 :-)

SYSTEM ABORT #2505 FROM SUBSYSTEM #202 (#202)
START_CM_TIMER can not get timer; bad status returned by 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 rest of the things I said were correct (as the coffee kicks in). You can monitor the
consumption with Threshold Manager.

And, I do not see this abort as occuring recently, in other words, it isn't "a known problem"
on 6.0 or later.

Sorry for the confusion.

Bill
HP/CSY