Path: utzoo!attcan!lsuc!teecs!belkin
From: belkin@teecs.UUCP (Hershel Belkin)
Newsgroups: comp.sys.hp
Subject: Re: Monitor 6.5
Message-ID: <1690004@teecs.UUCP>
Date: 10 Oct 89 05:32:07 GMT
References: <1306@oce-rd1.oce.nl>
Organization: Litton Systems, Toronto ONT
Lines: 20

I think it's obvious that many HP users find the monitor program extremely
valuable.  I have managed to obtain each version of it (as required) from
our early use of the 9000/550 to our current 825 without too much
difficulty.  That it is unsupported has never bothered me (although
about 3 years ago our local -- now dormant -- HP9000 user group submitted
a group request to have it supported).  What _is_ bothersome is having
to pester our SE to get it.  Many times it is not readily available to
the SE for one reason or another, so he has to track down the proper
version, get it put on a tape, and send it to me.  I assume this same
situation repeats itself _many_ times with each major HP-UX release.
Surely the wasted SE time and user frustration warrant putting monitor
in the contrib/bin directory on each new release!?  A README file 
clearly warning that it is unsupported -- as would anything in /usr/contrib/bin
be unsupported -- should suffice to protect HP from a barrage of technical
questions about it...

This is just one minor source of frustration associated with each major 
upgrade of HP-UX (or hardware system).  If HP is _really_ interested
in improving things (and it sure looks like they are), how about
a policy change with regard to monitor?  Let's see it in release 7!!