Re: Debugging malfunctioning ODBC -- MIDRANGE-L

Subject: Re: Debugging malfunctioning ODBC
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 12 Dec 2021 18:59:03 -0700
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 Sun, Dec 12, 2021 at 2:36 PM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Jack,

However, that C object you refer to must be part of OS/400 then, because
the error happens with an external connection to OS/400. There is no
self-written code involved on OS/400, because the access to OS/400 is via
ODBC.

Hmm, Patrick, this "rings a bell" with me but I don't remember quite what
the story is.

Many, many shops are using ODBC for IBM i connectivity, if you're having a
problem, "something is wrong".

Ask about it on Ryver IBMiOSS.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Debugging malfunctioning ODBC , Patrik Schindler

This mailing list archive is Copyright 1997-2025 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.