Leonard writes:

> We encountered the following in a job:
>
>  smread fail
>  2146926592 -26214215
>
> Neither of the two vendors involved in the software can explain it. The job seems to have stopped in
> its tracks ("hung") at that point until we aborted it. This is a job that is not new. The job ran
> last night without incident.
>
> Any suggestions?
>
> Thanks.
> --
> Leonard S. Berkowitz
> Perot Health Care Systems
> (Harvard Pilgrim Health Care account)
> voice: 617-509-1212
> fax: 617-509-1955
> pager: 781-226-2431

I am not sure about the 2146926592 value, I can't translate that into something useful
but the second value can be translated in debug

$2 ($17) nmdebug > =-#26214215
$fe7000b9
$3 ($17) nmdebug > wl errmsg(fffffe70, b9)
No entry in message catalog for error #400, subsys #185.

In and of itself that's not very helpful. But the subsystem, #185 (storage mgmt) is
consistent with what reported the error.

hth,

Bill
vCSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *