That is going to be very difficult, unless you have someone on site that is
at least comfortable with HP3000 gear.

Someone onsite needs to be doing the obvious checks for loose cables, room
overheating, reading a hard copy console log, none functional disk arrays,
etc.

You should have a written disaster plan in place, up-to-date, and a printed
copy in a binder sitting in the computer room.  Apparently you don't.  Make
sure after this disaster has passed, and before everyone forgets the impact,
that the sufficient resources are applied to get one created, tested, and
printed copies distributed.

- Pete


On 7/9/07, john pitman <[log in to unmask]> wrote:
>
> Can anybody point me to the next steps in isolating cause please? Its at a
> remote site, I don't have hands on access..
>
>
>
> thanks,
>
> jp
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

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