×
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.
just for a contrary point of view Booth, this is pointless. Being that we
have SQL procedures, functions and table functions, there is not much use
for ILE procedures and service programs. Instead of writing reusable
modules of code as an ILE procedure, write it as an SQL function or
procedure. The SQL routine can have a long name, just like an ILE
procedure. And it can be called from anywhere on the system, especially
and most importantly, from SQL itself. This reuse of code comes without
the cost of the complexity of the bind process and the dreaded signature
violation.
For the web service part, use PHP. That is what it is written to do. And
PHP natively calls your reusable SQL routines.
But wait, I just thought about an advantage of ILE - the debugger. And
error messages. Debugging SQL code is very difficult. So the more you rely
on routines written in SQL the more you have to fear that you will not be
able to determine why your production code failed.
midrange.com
