RE: library list vs Run SQL Scripts -- 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: library list vs Run SQL Scripts
From: Rob Berendt <rob@xxxxxxxxx>
Date: Fri, 4 Oct 2019 14:23:32 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
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>

I changed the JDBC configuration again. Changed the format from *SQL to *SYS. Now it searches the library list. However it still does not find the table: LOOKUP_TABLE in *LIBL type *FILE not found.

My bad. When you edit the JDBC configuration it closes a few things. Like the
cl: addlible gdihq;
statement. Had to run that again.

Now it works.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: library list vs Run SQL Scripts , Birgitta Hauser

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.