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.

E0565: Glink, terminal type and resource name limitation

Product: Glink
Platform: All
Status: Fixed in 6.1.6 and 6.2
Last updated: 1999-09-20 11:44:13

The length of the response to the telnet terminal type enquiry
was increased from 14 to 22 characters in release 6.0. However,
a corresponding change to the telnet handler was not made and
the old limit of 14 characters was still being applied in
practice (the change was made to facilitate handling of
responses under the TNVIP regime which was why this was not
caught earlier). The limit has now been extended to the full
22 characters.

A linked problem is that the equivalent response under TNVIP
was limited to a total of 32 characters for the "terminal@resource"
response to a terminal type enquiry. In that the terminal type
can be up to 22 characters and the resource name up to 16 in
the actual Glink configuration, this limit has now been
extended to the maximum possible length (39 characters).
(c) Copyright 1982-2018 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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