RE: Verifying SQLRPGLE -- CODE400-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: Verifying SQLRPGLE
From: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 28 May 2003 08:35:54 -0500
List-archive: <http://archive.midrange.com/code400-l>
List-help: <mailto:code400-l-request@midrange.com?subject=help>
List-id: CODE/400 Discussion & Support <code400-l.midrange.com>
List-post: <mailto:code400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=unsubscribe>

Rick

There's an option in the CRT commands for embedded SQL, to save the generated source. Then you could compile from this, or perhaps verify that. Not the ideal, but doable?

HTH

Vern

At 07:38 AM 5/28/2003 -0500, you wrote:

I experience the same situation using 5.0.  I do a lot of embedded SQL and
would sure like to be able to verify the SQLRPGLE source members if there is
a way to do it.

Rick

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.