[Info-vax] VAX VMS going forward

[Jan-Erik Söderholm]

Den 2020-07-22 kl. 15:28, skrev Arne Vajhøj:
> On 7/22/2020 9:02 AM, Simon Clubley wrote:
>> On 2020-07-22, Arne Vajhøj <arne at vajhoej.dk> wrote:
>>> On 7/22/2020 8:34 AM, Simon Clubley wrote:
>>>> On a more serious note, what I haven't seen discussed is the situation
>>>> regarding the VAX Layered Products.
>>>>
>>>> Did you just get a core set of the VAX LP source code, such as some of the
>>>> compilers, or did you get pretty much everything ever produced for VAX
>>>> by DEC including products like VAXELN ?
>>>
>>> When you say VAXELN do you mean the VMS source code for the tools
>>> running on VMS generating VAXELN code or do you mean the source code
>>> for the VAXELN stuff?
>>>
>>> (the answer may be the same but it could be different)
>>
>> For all practical purposes, they are the same thing.
>>
>> I don't know how much experience you have with embedded systems, but
>> with tools like VAXELN, the libraries used to construct the final
>> bootable system images ship as part of VAXELN.
>>
>> You use a VAXELN compiler running on VMS (such as the VAXELN version
>> of Pascal) to compile your source code and then you use another VAXELN
>> tool, also running on VMS, to generate the final system image that is
>> then booted on the target system.
> 
> I know that.
> 
> And the first is obviously useless without the second.
> 
> But while the first is running on VMS then the second is not.
> 
> Which could mean a difference per the contract between HPE and VSI.
> 
> You could argue that if they are treated different in the contract
> then it an error in the contract, but I doubt anyone was thinking about
> VAXELN when the drafted the contract.
> 
> Arne

And what say the sites still using/running VAXELN? A major kitchen
applience manufacturer in Sweden had multiple VAXELN system for
their assembly lines up to at least 3-4 years ago. Not sure of
the actual status today...