Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.

E0897: Glink, AffinityVisual client connect failure with TNVIP

Product: Glink Professional 7.1.4
Platform: All Windows
Status: Fixed for 7.1.5
Last updated: 2003-08-14 07:39:35

This problem is a general problem for all client/server
applications when the client connects to a GCOS server by TNVIP.
It also applies to normal Glink connections using scripts.

At connect time TNVIP issues a series of information messages.
These are all sent with a Telnet 'go-ahead' signal. The 'go-ahead'
signal is used by TNVIP to give the 'turn' to the client. These
premature turn signals cause the client application to lose
synchronization with the log-in process.

The following is an AffinityVisual case that illustrates the

The TNVIP server sends:

[11:30:35.513] In:(43)
00:2D 50 61 74 69 65 6E 74 65 7A 3A 20 63 6E 78 20 -Patientez:cnx
10:65 6E 20 63 6F 75 72 73 20 FF EF FF F9 60 00 20 en cours '~`.
20:20 02 1B 4E 1B 5B 30 6D 0C FF EF                 ..N.[0m.'

The first, incorrect, go-ahead (FF F9) from the TNVIP server
causes the AffinityVisual client to react prematurely.

The result in the AffinityVisual program was that the
LocalDialog connection FORM was still be on the screen, and the
AffVis program recognized it (again), re-filled it out and
resent it. This caused the connection to fail.

In earlier versions of Glink this will sometimes work, depending
on timing, because the 'clear screen' in the text following the
premature go-ahead might be processed in Glink before the
AffVis application examines the screen.

This is not the case in Glink 7.1.4, due to the fix "E0833: Glink
processed characters after an Etx". Glink 7.1.4 purges the input
occuring after go-ahead. The 'Clear screen' data sent by the
TNVIP server after the premature go-ahead is lost.

Glink has been corrected to ignore the TNVIP Go-Ahead when
receiving TNVIP Information Messages.

Please note that this fix removes only one of the problems with
TNVIP. Because of premature, or even worse, missing, go-ahead
signals TNVIP is not recommended as a connection for
application/application dialog. If you are developing client
applications for GCOS servers using AffinityVisual or any other
tool, such as G&R Gweb, then you should use G&R/DSA or Ggate
connections. DSA and Ggate faithfully signal only the real 'turn'
signals sent from the GCOS application, and they do not lose any
of them.

(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors