Facebook

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.


E0877: MainWay TNVIP server hangs Glink, work-around

Product: Glink
Platform: All
Status: Fixed in 7.2, fix available for 7.1
Last updated: 2003-03-28 07:35:50

As previously reported in:

   E0321:  MainWay TNVIP server hangs Glink

An error in the MainWay implementation of the TNVIP server would sometimes
suppress the 'turn' leaving Glink locked with the line 'busy' waiting for
turn. This error was corrected by a patch in the MainWay, ser 75152
applicable to both DNS-E V2U1.03 and V2U2.02. It seems that this patch has
dropped out of later MainWay releases, and we also meet situations where
the customer is unable to apply the patch to solve the immediate problem.

We have therefore added a work-around in Glink. This work-around is not
recommended, it is far better to apply the correction to the MainWay.

The Glink help text for the TNVIP work-around:

  This option specifies the transmit lock mode that Glink will use
  for the application dialog.

  When using TNVIP, Glink should set the line 'busy' when you
  transmit (locking the keyboard), and keep it busy until it
  receives the 'TURN'. This is a signal that the application is
  ready to accept input.

  Due to known errors in some versions of the TNVIP server, the
  'TURN' from the application may not reach Glink, and leave Glink
  in a busy state with the keyboard locked. This option is a work-
  around if you are communicating with such a TNVIP server. It
  causes Glink to unlock when it receives any reply from the
  application. This allows you to continue, even if the TNVIP
  server error has suppressed the 'TURN'.

  Note that if this option is set then you will often be in a
  situation where you will be allowed to transmit data even if the
  application is not yet ready to receive it. In these cases the
  result is unpredictable. Your application may give errors, or
  scripts that rely on this kind of synchronization may fail.
(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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