RE: i/o module

David,

Java is an object-oriented language that knows nothing about databases.
RPG is a database-oriented language that knows nothing about objects.

If a Java programmer has to access a database, he/she must do all sorts of
awkward things with connection, connection handles, connection pools,
statement handles, etc. Very complicated stuff. So for a Java programmer
it makes much more sense to call a program/function/method that does all
the hard work. Thus it makes sense to create programs to give the Java
side access to the database.

OTOH it would be rather silly to force RPG programmers to use those
programs to access the database. RPG is perfectly suited for database
access. That would be sort of like asking the Java programmers to write
procedural Java because the RPG programmers don't know anything about
objects.

Joep Beckeringh


rpg400-l-bounces@xxxxxxxxxxxx wrote on 29-05-2008 09:22:35:

The idea is that a program doesn't have to know anything about the
database in order to use it. This has become a topic since we were
joined by team of JAVA developers. Since I had to create a new PF, I
got the order to create a separate I/O module as a kind of guinea
pig for future developement, the idea being that we would do the
same for every new file on the system.

All fors and againsts are extremely welcome and I thank all those
who have responded so far.