Okay I got the update and I think the Run SQL Scripts tool has a BUG in it. I used Run SQL Scripts initially and had success but another programmer is not. We changed his JDBC settings but nothing changed. The error returned is "SQL0204 X in Y type *FILE not found." Which is what we get when we use *SQL naming but we have changed that setting and still get this message. If we query using SCHEMA.TABLE notation we get results.
I found the JDBC settings in my base configuration folders (..\IBM\iAccessClient\RunSQLScripts) but changes do not seem to affect the Run SQL Scripts. I thought before with the iNav version that the JDBC settings were applied at the server you connected to because you could only set them based on server name you connect to. I opened the old iNav version and changed my settings fro *SQL from *SYS and then back to *SYS, ran a query then closed but that did not seem to affect the newer version.
Does anyone know where ACS Run SQL Scripts is actually getting its naming convention value from?
Thanks, Matt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
