You question was directed at Buck, but here's my opionion FWIW.
In .Net, PHP, Ruby, etc. it's almost always a good idea to call business logic as stored procedures where the logic is tied to a specific database whether IBMi, SQL Server or Oracle.
This practice is quite common with Oracle, SQL Server, so it also makes sense to use same context with IBMi to call business logic.
I don't think management probably needs much convincing to use sprocs.
Leave the business logic where it's at and call as needed from wherever.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 4
date: Thu, 6 Jul 2017 15:30:07 -0600
from: Nathan Andelin <nandelin@xxxxxxxxx>
subject: Re: RPG easier/harder to use than other languages?
On Mon, Jul 3, 2017 at 11:23 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
In the case of my organisation, .NET running on Microsoft Windows. The
web team get the data via stored procs (mostly) and it took time
convincing management that the web people didn't need ODBC direct to DB2
tables.
Buck, would you be willing to share what convinced your management to call
stored procedures from MS .Net apps? What do your stored procedures do? As
you intimated, MS .Net developers have other options for retrieving and
updating IBM i data. Do your web developers view you and your stored
procedures as a valued resource? As a gate-keeper? As a bottleneck?
midrange.com
