[Info-vax] OpenVMS 7.3-2, Patch V26.0 -> sh mem/cache=(vol=*, topqio=2) -> EXE crashing

[Stephen Hoffman]

On 2015-06-30 17:25:49 +0000, IanD said:

> And there-in is the rub
> 
> These old VMS systems / application has battled on for years with 
> little love by the business
> 
> They don't want to spend money on upgrading as it's many millions of 
> dollars for a new system (non VMS) and well a number of million for an 
> upgrade of the VMS application (so I'm told, seems a lot to me but I 
> believe it includes support etc) for a system that looks after a 
> customer base that isn't core business going forward
> 
> When these systems go, my job also goes, hence it's a bit of 
> self-preservation here keeping these systems viable for as long as I 
> can without trying to get them added to the 'cost to much to run' list, 
> which really = 'to be decommissioned' list

Given that IT management has a policy of not maintaining these servers, 
either you get to fight IT management directly or via the stakeholders 
or via the C-suite — fighting IT management seldom ends well for the 
employees involved — or simply kick this problem up to management and 
then do what they tell you here, and also start (or continue) getting 
clear of this environment.

Get your resumé dusted off, upgrade your skills, get more experience 
with more modern tools and configurations, and get clear of this job 
and this place on your schedule.

Post patch-lockdown, there's no listing of patches that's available 
openly AFAIK.  I've suggested that to HP (particularly around the 
enhancements they were adding to OpenVMS via the UPDATE kits), but they 
didn't see the value of that, given the costs that would apparently be 
involved.   The HP folks are probably going to be tied up with the 
corporate split for the next several months and the HPE folks 
continuing the end-game for OpenVMS at HP too, I wouldn't expect to see 
changes in this area.


-- 
Pure Personal Opinion | HoffmanLabs LLC