[Info-vax] Some questions on software for VMS 7.3 VAX (Stephen Hoffman)
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Mon Jan 11 16:54:03 EST 2016
On 2016-01-11 17:40:42 +0000, Kerry Main said:
>>
>>
> While I agree OpenVMS needs improvements, let's not try and say that
> integrating Windows with Linux and Solaris and Cisco server alarms is
> easy either.
Um, if Linux or Solaris or Cisco are or are not easy — they do have
various add-ons available, of course — then maybe being easier than
those platforms might be an opportunity?
This is not about the current situations from other vendors, nor about
the past. The current situation with other vendors is already at
least a year or two in the past, pragmatically.
This is about operating systems going forward, and about problems folks
are having right now, and about what can be done — and what other
vendors may or will be doing.
Other platforms which you keep telling me are problematic.
But then, these problematic platforms are less problematic than OpenVMS, too.
> Case in point - SNMP service on Windows servers is off by default.
So what? Or is the Microsoft way the only way to do things?
> In addition, while it was raised previously here as a knock against
> VNS, SNMP V3 is not supported on Windows platforms either.
Again, so what? Or, again, is following Microsoft the only approach?
> Current drivers are senior business types who are frustrated with the
> old way of internal IT where end users have to call and tell IT there
> is an issue with something. Business types are asking "why can't IT be
> more proactive and notify us that there is something that has failed
> and what services are impacted?"
Given OpenVMS is arguably worse than these other platforms — in terms
of what's installed and what's available without having to port it all
yourself — then maybe that's likely a problem for the folks that might
be considering the OpenVMS platform? Or the folks that might be
having problems defending keeping the platform around, for that matter.
SNMPv3, syslog/syslog-ng, patch management, crash management, remote
inventory, etc.
> Maintaining the old way of reactive IT (each group doing their own
> tools) is a great way to get out-sourced or, using today's hype, "moved
> to a public cloud" which is just another name for selective IT
> outsourcing.
Which means maybe VMS should not be even more private and more
isolated. Or did I miss something?
Also, get off of Windows for a while, and learn where there might be
different approaches and opportunities. OpenVMS is not competitive
with Windows and Linux, and will have to coexist with them. And
OpenVMS needs to be substantially easier to deal with than it is now,
and in comparison to the other platforms.
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list