Re: 4Gl->EGL->Java - "no suitable driver"
Posted in 2005
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Java & JDBC Development, Internationalization & Character Sets
Well, I've had no replies here and nothing of any use on the EGL forum. I wouldn't recommend this In fact I've just posted this response on there to someone's reply: <quote> Hi xxxxxx. I have converted a 4gl program using the conversion wizard, but in essence it is highly similar to the one you have demonstrated. The "DefineDatabaseAlias" and "connect" lines are identitical in format to yours. My issue is that the program fails at the "connect" line with the "no suitable driver" message. I am at the end of my tether and am beginning to wonder if this product is worth the ridiculous amount of effort I have put in so far just to get a simple bit of 4GL to run as an EGL/Java program. It is unwieldy, non-user friendly and counter-intuitive, bloated and slow. I can't find anything good to say about it so far. If It fails on this simple 4gl what hope is there for our 7,000+ 4gls, some of which are highly complex? Malc <unquote> I wouldn't recommend this product - which has been touted as being simple to use for a 4gl programmer - to a friend if I had one.
Hi ,
This is in fact well documented in the 4GL TO EGL conversion guide
PP 4-12:
also available at
http://www-128.ibm.com/developerworks/rational/library/egldoc.html
The values bulleted below should be defined in at least one of the
.properties files. The values in the example assume that the EGL
application references a database named stores7, that it supports
switching servers based on INFORMIXSERVER values, and that the server
connection is enabled without a password through .rhosts, and that the
application and the database server are not running on the same UNIX
host. v
INFORMIXSERVER=myserver vDEFAULT_USER=id v
DEFAULT_PASSWORD=pw v
stores7@myserver=jdbc:informixsqli://host:port/database:INFORMIXSERVER=myserver;
If the application and the database server are running on the same
host, DEFAULT_USER or DEFAULT_PASSWORD are not required. If the
application and the database server are operating on different UNIX
hosts, you can specify the application host in the .rhosts file of the
database server host. You do not need to specify the DEFAULT_USER and
DEFAULT_PASSWORD values. If the application does not require a value
for INFORMIXSERVER, INFORMIXSERVER can be omitted as a separate value.
If the application directly supplies userid and password values through
the CONNECT statement, the DEFAULT_USER and DEFAULT_PASSWORD values can
remain unspecified. For more information on .properties files, see the
genProperties and Java runtime properties help topics.
In my case I used a file with the name as user.properties under
C:\\Documents and Settings\\Administrator in windows ( as I logged in as
administrator user)
malc_p@btinternet.com wrote:
> Well, I've had no replies here and nothing of any use on the EGL forum.
> I wouldn't recommend this
> In fact I've just posted this response on there to someone's reply:
> <quote>
> Hi xxxxxx.
> I have converted a 4gl program using the conversion wizard, but in
> essence it is highly similar to the one you have demonstrated.
> The "DefineDatabaseAlias" and "connect" lines are identitical in format
> to yours. My issue is that the program fails at the "connect" line with
> the "no suitable driver" message.
> I am at the end of my tether and am beginning to wonder if this product
> is worth the ridiculous amount of effort I have put in so far just to
> get a simple bit of 4GL to run as an EGL/Java program.
> It is unwieldy, non-user friendly and counter-intuitive, bloated and
> slow.
> I can't find anything good to say about it so far.
> If It fails on this simple 4gl what hope is there for our 7,000+ 4gls,
> some of which are highly complex?
> Malc
> <unquote>
> I wouldn't recommend this product - which has been touted as being
> simple to use for a 4gl programmer - to a friend if I had one.
Related threads
- Column name length in Informix
- Caching Data to Buffers
- Checkpoint Duration
- dbaccess standalone.
- Getting executable name.