Hi Aldous Carlos,

Thanks for sharing some details about your new environment. It sounds like you were using Server Express 5.1 previously, and are now moving to Visual COBOL 8.

Can you let us know the exact error message you receive when you try to connect?

Also, have you tried using the isql utility (interactive SQL prompt, which I believe is provided with UnixODBC) to confirm the UnixODBC configuration is set up correctly on the new machine?

Hi Again,

I've just noticed that you are connecting to Microsoft SQL Server 2012. Please note that this version of SQL Server is not supported in Visual COBOL 8.0 . Please see this page in the Visual COBOL documentation for information, by Visual COBOL product version, on supported Relational Database Management Systems and versions.

Yes Blair, the unixODBC is configured correctly.   

On our cobol code we are seeing this




When we enabled the trace in the odbcinst.ini ,  we are seeing this on the  trace file.



What we did notice is that in the RHEL6, it seems a new connection is re-established after a detected link failure, but in RHEL8 as seen above it sticks .

We tried to connect to a SQLServer2019  to see if the db reconnect improves, but still had the same result.

Thanks.

Looks like we have managed to find a workaround.  Our COBOL developers were able to solve the reconnect issue by incorporating the lines below:

EXEC SQL CONNECT RESET CURRENT END-EXEC


Thanks