last updated at 28 Nov, 2006 16:46 (1 times)
rsteiner (22 Nov, 2006 00:05):
with a nice intuitive facility for laying out data entry/display screens and perform record searches and sorting.
[quote]magog (25 Nov, 2006 02:35):
You can also use Java to create VIO applications and with JDBC drivers you can also use several different databases (MySQL, PostgreSQL,...).
It's very easy to create a VIO program with Java.
Or you could also use the open source Java Apache Derby --an implementation of which is provided by IBM (as a no cost download) and known as CloudScape:
Although the implementation examples files are provided for Linux (*.ksh files) and WinXX (*.bat files), you can adapt them to execute under OS/2. If you Kow REXX, you can make your own implementations. Notwithstanding, since I run the EMX and Linux utilities (like the public domain Korn Shell for OS/2), I made the following changes.
Assuming an CloudScape installation directory on drive J:, a CLASSPATH, PATH, etc environment variables could be set in an OS/2 *.CMD file for the network server side (that could be running in your same machine), say /os2/mycloudscapeNet.cmd, as:
Whereas for the client side, you might write your OS/2 CMD file, say \os2\mycloudscapenetClient.cmd, as:
Needless to say the JAVA_HOME environment is assumed to point to a drive F: (were my Golden Code Development Java resides).
The next step would be to rem out all the statements relating to CLASSPATH in the *ksh files in the direcory:
...hence the statements to be REM'd by inserting a # at the very beginning would be like:
in each file where those ending *CP.ksh lines appear.
Note that although the open source Apache Derby does not come with an DB2 JDBC universal driver, IBM makes it available from:
for those people not desiring to download CloudScape and opting for Apache Derby instead.
After the changes made above, we are ready to work. From the OS/2 EMX environment and using the port of OS/2's public domain Korn Shell instead of the OS/2 shell, I execute:
start /i mycloudscapeNet.cmd
...and I follow it with the command to enter my ksh environment again:
and ONLY AFTER the network server is executing, then can the Client CMD be executed:
start /i mycloudscapenetClient
...and as before I reenter my ksh environment with:
(Note that if the network server side of CloudScape is not executing, you will not be able to start the client side)
And the client is ready to accept your SQL statements to create a persistent data storage and manage it, for example.
For more info about the Java RDBM, you may want to buy and study the manual Apache Derby --Off to the Races.
Good Luck !