[Info-vax] Possible VMS jobs

[abrsvc]

On Friday, December 21, 2018 at 10:10:05 PM UTC-5, Kerry Main wrote:
> > -----Original Message-----
> > From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Arne Vajhøj
> > via Info-vax
> > Sent: December 19, 2018 1:22 PM
> > To: info-vax at rbnsn.com
> > Cc: Arne Vajhøj <arne at vajhoej.dk>
> > Subject: Re: [Info-vax] Possible VMS jobs
> > 
> > On 12/19/2018 12:31 PM, Bill Gunshannon wrote:
> > > So, if one is to believe the comments posted here, there are a lot of
> > > places out there now with homegrown legacy applications written in
> > > legacy languages still running on VMS (possibly even legacy versions
> > > on legacy hardware).
> > 
> > We know there are VMS systems out there.
> > 
> > And there may be more than we think.
> > 
> > I am sure that the people behind VSI got to see some numbers at HP before
> > VSI was created and that those numbers must have looked interesting
> > because otherwise there would not have been a VSI.
> 
> See note below - the actual number of OpenVMS Customers WW is actually much higher than what HP told VSI.
> 
> > 
> > And it seems reasonable to assume that a very large part of them run at least
> > partly bespoke solutions.
> > 
> > The number of standard solutions only available on VMS is small and if a
> > standard solution was also available on Unix/Linux/Windows, then they likely
> > would have migrated years ago.
> > 
> > And the vast majority of these systems was introduced decades ago (if
> > recent then another platform would have been chose).
> > 
> > That indicates that the main language must be one of the traditional
> > languages (Cobol, Fortran, Pascal, C and maybe Ada or PL/I).
> > DEC C++, Java, PHP, Python etc. was not available back then.
> > Some peripheral stuff may have been added later in newer languages.
> > 
> > So yes they should be there.
> > 
> > >                                                 Any idea how one with
> > > legacy experience might find these people with the intention of
> > > seeking some work they might need done?
> > 
> > That is a very good question.
> > 
> > VSI (and HPE) should have some insight based on service contracts and
> > various purchases.
> > 
> > But that is not available to the public.
> > 
> > Obviously many people know small pieces of the puzzle.
> > 
> > But they may not want to publish it to the public.
> > 
> > I think you should ask for people that know about VMS systems to send you
> > some info via direct email.
> > 
> 
> Just to clarify something - HPE has no idea of how many OpenVMS systems are out there. 
> 
> How do I know? Well, having spent 34 years at DEC/Compaq/HP gives me a bit of insight.
> 
> First, DEC/Compaq/HP did not keep track of OpenVMS contracts or HW or SW that was sold through partners, distributors etc. In many (most?) cases, the distributors did not want HP going direct, so would purposely not share Cust info.
> 
> Second - there was at least 15 WW local contract management systems across the globe that were consolidated over numerous decades to more centralized contract mgmt. systems. In most cases, each time this consolidation was done, only the current on contract Customer info was migrated to the new system. All those systems which were not on contract were  "lost" from a tracking perspective. Still very active systems, but in many cases, Customers had no issues with OpenVMS over a long period, so they dropped the contracts to save $'s.
> 
> Third - fast forward to today. Remember now that all of HPE Customer Service was outsourced to Unisys  in the last year, so one would assume that Unisys now has the contract mgmt. responsibility for all those Alpha/VAX/Integrity systems that might still be on contract. I wonder if they imported all the contract info from HPE or just the active Customer contracts?
> 
> 
> Regards,
> 
> Kerry Main
> Kerry dot main at starkgaming dot com

I can agree with this as I had a few clients that had dropped support due to the high cost.  One in particular since they had contacted HP for assistance only to get someone on the phone that could barely spell OpenVMS let alone assist with a problem.  The question was what was the support cost for since the "expert" new less than the asking party.  I was called and was able to resolve the problem, but again, what was the support contract for if no assistance could be provided.  Customer was not happy with HP.  Worked out forme though, I got a 4+ year contract out of that one...