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.

E1076: Glink 3270, HLLAPI IND$FILE can result in an invalid screen

Product: Glink for Windows
Platform: All
Status: Fixed for 8.0.3, 7.2.6, 6.2.9
Last updated: 2005-09-29 08:22:08

After completion of an IND$FILE file transfer started using HLLAPI from
an application, the Glink screen could sometimes be be corrupted with
spurious characters. The file transfer itself worked correctly but the
spurious characters could make the formatted screen invalid, and hitting
XMIT could put Glink into a LOCKED KEYBOARD state.

You could exit this 'locked' state by using the Glink BREAK function
(Alt+B) which forces the IBM mainframe to redisplay a screen. Further
HLLAPI file transfers could leave Glink in an unstable state.

This problem only occured if the 'Wait after transfer' option was set to
"Always" or "Only when failed".

  Settings->File transfer->General->Wait after transfer:

The work-around is to set this option to "Never"

  Settings->File transfer->General->Wait after transfer: Never
(c) Copyright 1982-2018 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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