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.

E0563: Glink/Ggate, attention 1 and 2 (versus break)

Product: Ggate
Platform: All
Status: Fixed in 5.3, the fix can be installed on a 5.2 system
Last updated: 1999-09-17 15:52:00

The 'break' signal is interpreted differently as regards purge
of output, depending on configuration, see Error E0562.

The asynchronous terminals connected to a Datanet or MainWay
terminal manager can use CTRL/A to send an Attention level 1,
and CTRL/Z to send Attention level 2, rather than a break.

The Glink/Ggate 'connection menu' allows you to send an
Attention 1 or Attention 2 signal, rather than a break. These
signals should not purge. Attention 1 is identical to a break,
Attention 2 gives an attention level of 2 (rather than 1) to
the application.

Ggate was incorrectly purging for the the attention signals, and
the attention level 2 was in some cases being delivered to the
application as a 'data attention' rather than an attention with
a level of 2.

This correction sends both attention levels correctly, and never
purges output.

Note that the attention signals can also be typed in the Glink
emulation window as ordinary text messages ($*$A1 and $*$A2) and
will be encoded for Ggate as control records to give the correct
attention signal (unless this possibility has been supressed in
the Glink configuration, see CFIX 2875).
(c) Copyright 1982-2018 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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