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.

E0038: GL_DSA Fails to return error after Transport Timeout

Product: Host Links 4.0.0, Gline
Platform: Any
Status: Closed, fixed in 4.0.1 and 4.1.0
Last updated: 1996-07-19 03:22:54

Original customer report:

I think I have found a bug in the gl_dsa module while developing a program
using the GLAPI's to "poll" both Ethernet ports on every Datanet in the
network. I have 2 RSC's configured in the dsa.cfg file, one for each
Ethernet port of a given Datanet. My program attempts to connect to a
"dummy" DMB on the first RSC. If the port/Datanet is up, DNS immediately
returns a 0x0104 error. If the port/fep is down, it eventually times out
and the OSI stack returns a Transport Timeout (0x00000000) error. Once a
response is received, it then attempts a connect to the second RSC/Ethernet
port. This process is repeated every minute to test the state of both ports
and the FEP.
What I have found is that if both ports are up, or both are down, all works
OK. If one is up and one is down, after receiving the 0x0104 from the "up"
port, gl_dsa never returns the Transport Timeout for the second port.


Confirmed, there was a problem so that after an error had first been
reported on one connect, errors on subsequent connects weren't reported.
(c) Copyright 1982-2018 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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