my understanding of the Sybase JDBC drivers is that they, like Oracle,
include native code. Thus somewhere out there on your dasd around about
the same place the jdbc drivers are (probably in a jar) there should be
a lib?????.so. You may only be using classes, but they could have native
methods in them - in fact they probably do. This is where someone from
the Sybase user community (or better yet, their support department) would
be very handy to have in on the discusion - they may very well say that
they don't have any, and that all IPC is handled by tcp sockets and high
level protocols... in which case the question to them is "then why does
getConnection() fail under only java_g??" (I'm assuming it works under
normal java) Note that when I started trying to help I understood the
problem to be with in RMI when trying to use Runtime.trace*() . . . my
code does that all the time, thus I was sure I could help you; now that
it's looking like Sybase I'm getting farther and farther out of my watter,
aside from basic JNI issues. -=Chris
At 14:57 10/18/99 -0600, Brandon Anderson wrote:
>I'm sorry, but I'm obviously missing something. What *.so and *_g.so. As
>far as I know the only libraries that I'm using are the ones included
>with the JDK and Debug JDK Versions. I'm using class files for the Sybase
>stuff. And my java files are not being compiled into a library. Maybe
>I'm missing your point, but please enlighten me.
cabbey at home dot net <*> http://members.home.net/cabbey
I want a binary interface to the brain!
Today's opto-mechanical digital interfaces are just too slow!
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
