🚀 go-pugleaf

--
In article <8JAN199309491490@jhuvms.hcf.jhu.edu>, ecf_stbo@jhuvms.hcf.jhu.edu
writes:

> I think what you
> have here is a case of 'escape from MIS' eventually turning into 'running
>back
> to MIS screaming HELLLLLLP!', in other words: 'we got PCs on our desk so
>we
> wouldn't have to pay MIS for services and to feel we were managing our
>own
> systems but we didn't plan it properly and don't know how to run our
>systems
> and a salesperson told us this would solve all our problems and we
>listened to
> the salesperson instead of our own people ....

Not to be too kind to salespersons, but in my experience it's often been the
MIS staff that didn't consider problems of scale, planning, etc.  This can
happen easily to a company (in a PC-obsessed society) where PCs have a strong
champion.  And then it turns out the champion has little or no experience with
more than 3 systems at a time ... or connecting them to the UNIX servers ...
or network printers ... or ....

Good friend of mine is a senior software manager at a US-wide company that
produces (and sells, very profitably) PC-based software for CASE.  Each of
their sites has a LAN, and all sites are connected over T1 lines.  And my
friend wanted to print from her desktop PC to a networked printer in the same
building.  Couldn't just do it.  System manager couldn't make it work.  After
repeated tries, the problem was solved by attaching a private printer to the
PC's local port.  Thing is, if this company has such difficulties, what are
the world's MIS departments in general able to do?

At Digital we have no such problems, of course. :-)

___Pete

kaiser@uniriv.vbo.dec.com
+33 92.95.62.97, FAX +33 92.95.52.00