[Info-vax] yet another sys$qiow question

[Jan-Erik Soderholm]

Den 2015-08-12 kl. 22:21, skrev Johnny Billquist:
> On 2015-08-12 21:40, Jan-Erik Soderholm wrote:
>> Den 2015-08-12 kl. 21:23, skrev Johnny Billquist:
>>> On 2015-08-12 10:12, Jan-Erik Soderholm wrote:
>>>> Den 2015-08-12 kl. 01:53, skrev Johnny Billquist:
>>>>> On 2015-08-12 00:38, kc at kayceesoftware.com wrote:
>>>>>> this is slightly related issue only as it pertains to the same serial
>>>>>> comm to a card reader.
>>>>>> to refresh: vms 8.4 IA64, tcpip 5.7 ECO 5, C 7.3-018
>>>>>> sys$qiow working fine now and seems very stable, my problem was
>>>>>> getting
>>>>>> the terminator mask correct.
>>>>>>
>>>>>> I've been reading on sockets and will be converting to that mode soon
>>>>>> for
>>>>>> another project and probably change this serial code at that point.
>>>>>>
>>>>>> BUT, in researching a very random NAK of my comm, i've found that the
>>>>>> CRC
>>>>>> sometimes calcs a line feed (LF, ox0a), and the stored string shows
>>>>>> ONLY
>>>>>> the LF i put in it....but the message that ends up at the card reader
>>>>>> has
>>>>>> CRLF, which is then rejected as invalid.
>>>>>>
>>>>>> The terminal port (TNA1) is set pasthru, the VMS IO Ref Manual says
>>>>>> IO$M_NOFORMAT and TT2$M_PASTHRU are basically the same.
>>>>>>
>>>>>> So, is it the TT driver, or tcp, or something else converting the
>>>>>> LF to
>>>>>> CRLF?
>>>>>
>>>>> While I cannot answer, I should repeat what I pointed out before. The
>>>>> "telnet" protocol is really just a TCP stream, with a couple of things
>>>>> thrown in.
>>>>
>>>> You can use TNA ports/devices without using the telnet protocol.
>>>> Just use /prot=none.
>>>
>>> Do you have any specific information what that implies?
>>
>> I do not have anything more then online HELP and the TCPIP
>> user manual (same text at both sources) :
>>
>> TELNET> help create /protocol
>>
>> CREATE_SESSION
>>
>>    /PROTOCOL
>>
>>          /PROTOCOL=options
>>
>>       Optional. Default: NONE. Options include:
>>
>>       o  NONE
>>
>>          Data is sent with no interpretation (raw).
>>
>>       o  NVT
>>
>>          Network Virtual Terminal (NVT), TELNET's internal
>>          representation of a standard network terminal. NVT format
>>          is standard 7-bit ASCII code transmitted in 8-bit octets, the
>>          canonical form of data representation used by both the client
>>          and server.
>>
>>       o  TELNET
>>
>>          Standard TELNET protocol.
>>
>>       o  RLOGIN
>>
>>          Standard RLOGIN protocol.
>>
>>
>>
>> Topic?
>>
>>
>> And I also know from 15 years of setting this up for equipment,
>> that *nothing* apart from what we write to the TNAxxx devices
>> in the QIO(W) is actualy sent on the line.
>
> Thanks for that info. While not definitive, it do sound as if perhaps NONE
> really means none. That still leaves a lot of question marks, though. So
> I'd still recommend tcpdump to find out what actually goes over the net.
>
> (And the "telnet protocol" is such a broken term... :-/ )
>
>      Johnny
>

We haven't used any line trafic dump tool, but we have used
"raw" ports at the other side, and I know that PLCs and
other equipment never seens anything apart from the actual
content of the TCPIP package, the same data as we put in
into the QIO(W) call.

Never mind, I have lost track on who was having some
trouble with this. It wasn't us anyway... :-)

Jan-Erik.