Re: FOUND IT, Re: Running into a problem with JDBCR4 expansion -- JAVA400-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: FOUND IT, Re: Running into a problem with JDBCR4 expansion
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 08 Jul 2013 14:43:40 -0700
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

On 7/8/13 2:01 PM, Gary L Peskin wrote:

Glad you sorted it out. That was going to be my next question. I would
have thought you would have received some type of runtime error message
though.

. . . except that the wrapper put the prototyped Java call inside of a monitor, that returned an *OFF if it was tripped, effectively making an improper call look exactly like a proper call that simply failed.

--
JHHL

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.