[Info-vax] Programming languages on VMS

[DaveFroble]

Simon Clubley wrote:
> On 2018-01-29, DaveFroble <davef at tsoft-inc.com> wrote:
>> It's my thinking that describing something as a risk is sort of like FUD.  If I 
>> have something that works, does the job, then I use it.
>>
> 
> I hope you don't think that way when it comes to operating systems or
> other software that can be potentially used to compromise a system. :-)
> 
> In case the point is too subtle, you not only have to think about what
> the software is supposed to do, but also what it may potentially _now_
> be able to do when a newly discovered security vulnerability comes along.
> 
> Simon.
> 

Ok, I'll be specific, and you can decide.

I've implemented some relays, which act as a service to VMS clients, and then as 
a client to trading partners over the internet.  I'm using Catalyst SocketTools 
for communications, and I keep up to date on versions.

As to why I'm doing this, look no further than the dismal state of 
communications on VMS.  In this manner I get TLS V1.2 and such for the internet 
communications.

The VB6 is just a jacket for the main functionality.

Could there be problems?  Sure, always.  But in this case I think I have things 
such that it's not likely.

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486