RE: Proposal for New RPG BIF -- 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: Proposal for New RPG BIF
From: Justin Taylor <jtaylor.0ab@xxxxxxxxx>
Date: Wed, 31 Jul 2024 13:32:38 -0500
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>

I was thinking the same thing.

date: Wed, 31 Jul 2024 15:58:11 +0200
from: Patrik Schindler <poc@xxxxxxxxxx>
subject: Re: Proposal for New RPG BIF

Hello Birgitta,

Am 31.07.2024 um 15:15 schrieb Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>:

I wrapped a lot of SQL functions that were not available in RPG as RPG

functions (in a single Service Program) ;)

... no need to use directly embedded SQL

Isn't this generating a lot of call overhead, compared to a BIF? No matter
where you put it?

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Proposal for New RPG BIF , Justin Taylor

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.