Problem
When running Progress Version 6.x or 7.x on SCO OpenServer Release 5.0.0, connection attempts by new users fail and may result in error messages or may hang the user's process.
Cause
There is a known problem in SCO OpenServer Release 5.0.0 with the
system call setsockopt(SSC) when using the SO_REUSEADDR option.
Users running Progress in client/server mode on SCO OpenServer
Release 5.0.0 may be affected by this issue. The problem occurs
when a non-Progress application binds to a port that is being used
by Progress. Users already connected to the database will not be
affected, but subsequent connection attempts by new users will fail
and may result in error messages or may hang the user's process.Note: Users running with only local clients, even if the server was started with -S <servicename>, will not be affected by this SO_REUSEADDR issue.
Solution
Apply the SCO Networking Supplement Release 1.0 for SCO
OpenServer Release 5. This supplement corrects the behavior
of setsockopt(SSC) with the SO_REUSEADDR option.