[Info-vax] Anyone still around ? :-)

[Jan-Erik Söderholm]

Den 2019-10-10 kl. 10:23, skrev Marc Van Dyck:
> Jan-Erik Söderholm laid this down on his screen :
>> Den 2019-10-09 kl. 01:02, skrev Arne Vajhøj:
>>> On 10/8/2019 8:18 AM, Simon Clubley wrote:
>>>> So where is everyone these days ? :-)
>>>>
>>>> It's a bit quiet around here at the moment.
>>>>
>>>> Has everyone moved from VMS to Linux/Windows/etc ?
>>>
>>> I am still here.
>>>
>>> I suspect that a large portion of the users here are more
>>> hobbyists than full time VMS users.
>>>
>>> Arne
>>>
>>
>> I'm busy working with VMS and have not much spare time
>> to be spent here. :-)
>>
>> I guess that the activity will increase when we have
>> some real VMS/x86 experiences to share. But I had also
>> expected some discussions around VSI TCPIP 10.x…
> 
> Ah, but we are currently actively looking into that. Two test machines
> have been upgraded and we try all our working environment on them.
> So far, no issues encountered with existing programs (even the netbackup
> client, quite old stuff, seems to work fine) but lots of work to port
> our scripts because IP DCL commands and outputs are quite different.
> 
> We have already one call opened regarding the mail protocol, which
> has some features that worked with the original VMS stack, and that
> are broken with the new one.
> 
> And we still have to investigate the TELNET API that we use a lot in
> our environment, as we were told that it doesn't exist with the new
> stack...
> 

I guess that is some "call API", right? What we do is things like:

$ Telnet/create x.x.x.x nnnn mmmm /prot=none/time=(noidle,recon=0:0:15)
$ SET TERM/PERM/DEV=LA120 TNAmmmm

x.x.x.x and nnnn is of course the IP address and port no that some
equipment is listening to. Like port 10001 on Lantronix boxes.

Then we start up our detached communication processes with
/input=TNAmmmm, and they read from sys$input using QIOW and the
normal terminal driver.

This works very well. No handling of network specifics in the
application code, it just reads from a "terminal". Lost links
and reconnects are handled by the Telnet driver.

There is something called NTA devices in V10.x, but I have not
been able to find out if they are equivalent to TNA devices...