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.


E0411: Glink, IND$File to MainWay hangs

Product: Glink, all 3270 emulations, IND$FILE
Platform: All
Status: Fixed for 6.0.4
Last updated: 1998-05-22 16:17:07

The Glink IND$FILE implementation was sending the Telnet EOR
sequence split across two physical TCP/IP blocks. This is
perfectly legal since Telnet is a byte-stream protocol like all
Internet protocols, and the division of any of the Internet
protocols into physical blocks is in theory quite arbitrary,
depending completely on the forwarding algorithms of the TCP/IP
stacks involved.

In the case of TN3270 as implemented on the MainWay this
splitting was causing the TN3270 IND$FILE session to hang. This
does not occur with (for example) the IBM Telnet front-end.

The avoidance procedure in Glink is to do a better
pre-calculation of when the automatic socket write at the lower
level will occur, avoiding overfilling a block, and thus always
including the complete EOR sequence in one socket write. With
most TCP/IP stacks on most modern networks this will result in
the complete sequence being included in one physical TCP/IP block.

The problem is reported to Bull as a MainWay TN3270 problem.

This avoidance has been tested, and works in the customer
environment.
(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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