[Info-vax] Programming languages on VMS

[Stephen Hoffman]

On 2018-02-12 22:25:09 +0000, Robert A. Brooks said:

> On 2/12/2018 5:18 PM, Stephen Hoffman wrote:
>> 
>> When next the manufacturing line gets rebuilt, the folks will be 
>> looking for upgrades and replacements.  They may decide to upgrade and 
>> to re-use their existing software, but they also routinely look around 
>> to see what other process control offerings and platforms are 
>> available.  More than a few of these folks use an outside vendor here, 
>> too.   It's this outside vendor and this replacement cycle that VSI and 
>> other vendors and particularly the app partners need to be ready for 
>> and competitive for, too.
> 
> And VSI is ready to provide the industry-leading suite of OMNI products 
> (OMNIAPI, OMNIMMS, OSAP/H1, OSAP/S7, OSAP/AP) for your shop floor 
> automation pleasure.

Somebody still has to sew all those pieces together, which involves 
adding a whole lot of time and effort and code to those and to other 
parts.    Supporting BASEstar Classic and BASEstar Open (BASEstar Open 
used to include DEComni API IIRC) and related pieces and parts is 
roughly analogous to supporting IPv4 and IPv6 and core network services 
on compute servers, in consideration with the amount of other added 
vendor code that's involved around actually productively using those 
and other pieces.    What went before BASEstar and related was really 
ugly and so was the ladder logic used on the early PLCs, but there's 
still vast amounts of bespoke code involved in a typical factory floor 
installation.  Well beyond BASEstar and related.   And then there's how 
to securely network OpenVMS and all of those other pieces together, 
something which OpenVMS and developers working on apps for OpenVMS 
could definitely use some help with.   Gotta make installing and 
developing for and using OpenVMS and BASEstar and the rest easier and 
more secure, too.



-- 
Pure Personal Opinion | HoffmanLabs LLC