23-Jul-2004

ISEE SPOP configured

I spent most of today watching the configuration and learning about the ISEE SPOP machine. This machine is the focal point for all OpenVMS machines that have the ISEE client software installed on them.

Automated service calls are created by the SPOP in response to hardware and/or software events on the client machines, and are then forwarded to HP where they are assigned for action by the services organization.

While the ISEE software has been around for about two and a half years, the OpenVMS client is only a couple of months old. Needless to say, I have noticed a couple of bugs in it already today. I hope HP quickly addresses these, as this appears to be one of the better automated service packages I've seen so far. I'm particularly impressed by the visibility into the call process by the customer (i.e., us).

Posted at July 23, 2004 1:12 PM
Tag Set:
Comments

So lets see, you had the option of not using an windows SPOP and logging the calls direct to hp from VMS.

But you chose to introduce a single point of failure, and a windows one at that.

Really that kind of action just speaks for itself.

Posted by: Alex Daniels at August 15, 2004 10:58 AM

Yes, but it has its advantages as well, including a single point of management for all calls.

I have only rolled it out to one machine so far, and I have already discovered problems with it. So far, I have not had time to investigate the VMS only approach.

Would you care to share your experiences?

Posted by: Jim Duff at August 16, 2004 9:53 AM

Comments are closed