Nathan,
My point is that you can use prepared SQL statements in the native language environment, and evoke them from Net.Data to improve performance. <<
Planned on that sort of thing anyway, via REXX if possible and SQL stored procedures or calling SQL stored procedures from Net.Data.
If you're serious about Net.Data, consider using the native language environment for business logic and DB I/O. Use Net.Data for generating the output stream. <<<
And input stream... planned on that all along.
So, I'm going to prototype using both Net.Data and PHP. Now all I have to do is get the darn environments running and learn how to use them which is a bit harder then editing a file with REXX statements or COBOL or whatever and running them. It seems I have to set up a whole commo and execution environment instead of it being naturally installed like i5 compilers and interpreters when the whole system is first set up.
Thanks,
Dave
Nathan Andelin <nandelin@xxxxxxxxx> 8/12/2008 12:00 >>>
From: Jim Dillard
Comparison of Net.Data vs. PHP on IBM's web site (2/2007)
http://www.ibm.com/developerworks/systems/library/es-phppart2/
It's interesting that IBM would give that assignment to a team of interns. They seemed to enjoyed it.
One thing that struck me was the performance comparison between Net.Data and PHP in outputting an SQL result set to an HTML table, where PHP was allowed to use a prepared SQL statement, but Net.Data wasn't afforded that opportunity. Was that a bias in favor of PHP? Or, didn't they know how to do that in Net.Data?
Net.Data includes a set of service program procedures for generating "tables" from ILE programs. For example, Net.Data could call an RPG program, which could dump an SQL result set to a Net.Data table.
I used that technique to compare the performance of Net.Data vs. CGIDEV2. In my case the Net.Data macro and the CGIDEV2 program used the same service program for DB I/O, so the performance comparison was limited to generating HTML, where Net.Data was slightly faster than CGIDEV2.
My point is that you can use prepared SQL statements in the native language environment, and evoke them from Net.Data to improve performance.
In fact, that's the type of thing I've been advocating throughout this thread. If you're serious about Net.Data, consider using the native language environment for business logic and DB I/O. Use Net.Data for generating the output stream.
If that's you're architecture, it doesn't really matter that PHP has tons of literature and sample code. For you're purposes you're only using the scripting environment for browser I/O, and perhaps a bit of application control.
Nathan.
midrange.com
