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: Sam_L <lennon_s_j@xxxxxxxxxxx>
Date: Fri, 20 Aug 2021 12:55:23 -0400
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>

Can you change the JOBD for the QZDASOINIT jobs to maximum logging? Might help...

On 8/20/2021 6:41 AM, Patrik Schindler wrote:

Of course, there isn't any output in the job logs of any QZDASOINIT, so I don't know what exactly is going on. I also can't find entries in QHST hinting to an error.

How can I debug on OS/400 what's going wrong here?

Thank you.

(Please refrain from advising to use current OS's. I'm a retrocomputing hobbyist.)

:wq! PoC

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.