Re: accessing SQL db in RPG

Hi Chuck,

If you are running this program interactively, there should be information about the errors that scrolls up your screen -- possibly, it's to fast to read? So, please start a fresh sign on screen, and do this:

OVRPRTF FILE(STDOUT) TOFILE(QSYSPRT) HOLD(*YES) OVRSCOPE(*JOB)
OVRPRTF FILE(STDERR) TOFILE(QSYSPRT) HOLD(*YES) OVRSCOPE(*JOB)

now run your program that uses JDBC, in the same interactive job.
Then, sign off.

When you log on again, with any luck, you should find spooled files that contain the text of the errors.

Also, let me explain some of the stuff you keep posting so you don't waste anymore time looking at it. Here's the stuff I'm referring to:

JNIENV_P = SPP:EEDB1E8B3E002000
Drv=12
Mid=8
Str=15
Prop=8

All these say is where data is stored in the computers memory (in the case of JNIENV_P) or in the Java Virtual Machine's memory (For the other 4 items.) It doesn't tell me what data is stored in those memory locations -- it only tells me where they happen to be in your computer. And they have the potential to be different every time you run the program. See what I mean? That's not useful information...

This line:
conn = CallConnectMethod(JNIENV_P: drv: mid: str: prop)

This line tells you that the error is occuring while calling the 'connect' routine in your JDBC driver. So at this point it's calling out to the JAR file you downloaded.

So I guess that's good to know -- but, not really a surprise. Any time it says it has trouble connecting, that's going to be where it occurs.

Please consider trying to capture the error messages, as I described above. Let's see what they tell us -- they may tell us exactly what the problem is.

The other thing, that I'm now suggesting for the 3rd time in this thread -- I strongly suspect there's a problem with the use of the Microsoft JDBC driver. I strongly recommend upgrading to the jTDS driver. Experience shows that this has more features, runs much faster, and is much more reliable.

But, now that you've got me involved, I'm REALLY curious as to what error you're getting with the Microsoft driver -- so please at least try getting the error messages before switching drivers, and show me what you're getting.

-SK



On 12/18/2012 7:11 PM, Graves, Chuck wrote:

Scott,
Thank you so much for your help. You were correct. I'm not sure where I found that, but I had copied it from somewhere on the internet

(??? lies on the internet??? OMG)

At any rate, I got past all my java errors, (by pointing the iSeries to java version 1.6 via a SystemDefault.properties file in my /home/me directory) but I still cannot connect. I'm failing here:

conn = CallConnectMethod(JNIENV_P: drv: mid: str: prop)

in the JDBCR4 *Srvpgm

The values going in are:

JNIENV_P = SPP:EEDB1E8B3E002000
Drv=12
Mid=8
Str=15
Prop=8

I have tried every conceivable combination of everything at this point, including trying to connect to different versions of SQL servers, different users, with & without properties, with & without domain names, with & without the domain property value,
I can sign-on to the SQL server(s), I can access the database all with the various ID's/passwords I've tried through SQL Server Management Console. I've done "netstat -a" and verified that port 1433 is listening

I have NO DOUBT that it is something in my environment and not your code, just don't know where to look

This is what I get everytime:

Java Virtual Machine is Classic.
JVM properties were loaded from a properties file.
Unable to connect.

So, before I hit my head on the table... again, I'll go try to get SSH working to our new bank tomorrow and come back to this.

THANK YOU again...
Chuck