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.

E1186: GlinkWeb, TSS prompt could give a 1 char input field

Product: GlinkWeb, Glink Enterprise Edition
Platform: Windows
Status: Fixed in 8.0.7, 8.1.3
Last updated: 2008-06-18 14:48:39

When using GlinkWeb in VIP7800 mode to GCOS TSS the command line
prompt (an asterisk '*') could be displayed as a single character
input field. This occured if GlinkWeb comms was configured in CHAR
mode. When in CHAR/ECHO mode GlinkWeb assumes it is connected to an
async host (GCOS6, or even today UNIX/Linux) and tries to guess
where the end of the input field is located, using various methods.
One of the tests is that if the cursor is positioned on one of a
given set of characters, then the input field is defined by the
number of those characters, and the asterisk was in the set, giving a
single character input field for TSS.

Normally the choice of a sync terminal type forces TEXT mode where
applicable, avoiding the problems associated with CHAR/ECHO. This
was not being done when connecting in VIP7804 and VIP7814 modes,
allowing them to be erroneously configured in CHAR.

Work-around is simply to set TEXT mode in the Glink configuration:

  Settings->Emulation->VIP mode setup->Init mode: TEXT
(c) Copyright 1982-2019 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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