topic TCPWARE Telnet issue in Operating System - OpenVMS

TCPWARE Telnet issue

Ayya — Mon, 14 Nov 2005 16:46:00 GMT

VAX openvms 5.5-2H4, TCPWARE 5.6
(Behaves normally with UCX.)

A DIBOL application with a FORM to fill. When a field is completed cursor moves to next field.
The F12 Key on the PC acts as tabs back to previous Field.

works fine run interactively.

When run from a command file the F12 does not move the cursor.
Also when a field is completed does not move the cursor to next field.
Problem only running using a Command file.

The command file test.com is shown below:

$! test.com
$set noon
$set term/noline/esc
$ass tt: sys$input
$Run ProgA

Sini

Re: TCPWARE Telnet issue

Arch_Muthiah — Mon, 14 Nov 2005 17:50:01 GMT

Sini,

Have you checked your keyboard mapping? and Try /translation_attribute with your $ass command.

Archunan

Re: TCPWARE Telnet issue

Ayya — Mon, 14 Nov 2005 20:17:54 GMT

Why does the application work from the DCL prompt but not when run from a command procedure?

Re: TCPWARE Telnet issue

Arch_Muthiah — Tue, 15 Nov 2005 01:21:57 GMT

Thalaiva,

If you can able run successfully in the interactive mode, why did you give this title " TCPware Telnet Issue" ?

Running ProgA from Server and client using TCPware TELNET differs in manyways. I am wondering you could able to run your ProgA interactively from client using TCPware/Telnet, and have problem noninteractive mode.

Unless otherwise you set the control characters (echo, end-of-char, remote-flow-control, terminal speed, terminal type, transmit binary, suppress-Go-ahead,window size) locally, your client machine won't interpret these controls comming from the server. In the same time server also can not translate the control characters it sends to the client especially over TCPware/Telnet.

These are setup we have to do locally for both interactive and non-interactive image run.

Make sure you did all these setup from the client machine. Server won't do anything for the client. server translates the characters it receives, the same way the client can translate the chars it send over the network, but it won't translate the control characters it receives (defined in your FORMS). This is the problem only when you use TCPWare/Telnet. So define these controls to your local terminal driver.

Archunan