Re: Debugging malfunctioning ODBC -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Debugging malfunctioning ODBC
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 20 Aug 2021 08:39:02 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Fri, Aug 20, 2021 at 4:42 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

- Failing client machines can successfully query a similarly configured
(odbc.ini) V7R2 machine.
- The problem is appearing on two independent, but manually
try-to-keep-configurations-synchronized server machines running V4R5.

Patrick, I think you know the answer and don't wish to face it :)

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.