Anyone using CONNX ADABAS SQL Gateway with FMP 15.
Performance does not seem to be the best.
Found some of the problem. Using the utility INFONAUT, it reads 18k records a second and displays the first page in less than 4 seconds.
Doing a trace with
The trace indicates it is also doing a SELECT * COUNT which I did not write. Maybe it has to but it has to read all records before displaying the table list to get the COUNT.
Anyway, I can tell it not to count??????????????????????
That is not a compatible SQL-source for FileMaker so that might be your problem
With CONNX ODBC connection, it works just fine.
This ODBC translates SQL into ADABAS direct calls.
I've some prototyping and it works, but not well.
There is a lot of things that is working, but since FileMaker clearly says what SQL database sources you can work with that they support, I think you better stay with that. What if they release a new version of FileMaker where ADABAS is not working?
The base system (legacy) is the main system.
FMP is only going to be used for legacy data access and inquiry apps for
FileMaker clearly states what sources may be used with ESS. Before ESS and to some extent now, with the proper ODBC driver, other SQL sources can be used with the script steps:
These require using SQL queries and the data is not real-time as one would find with and ESS table on a FileMaker layout. YMMV, and not be as effective as with the "approved" sources.
And you can make FileMaker Server as an ODBC source that may work (the other app communicates with FMS):
There are other ways to link with ODBC data sources besides using FileMaker Pro as an ODBC client application. You can write SQL queries to use FileMaker Pro as a data source. See Sharing FileMaker Pro data via ODBC or JDBC, FileMaker ODBC and JDBC Guide, and FileMaker SQL Reference.
On occasion, I've used another method involving a web site that can read/write SQL and make it a bridge for FileMaker (which can be web published with ODBC, too) and any other SQL source.
Thank you. Will look at these references.
I think the real problem for us is that I do not believe the indexes
(defined) are being used properly.
ADABAS has a 'READ' and 'FIND' which uses indexes. So I don't think the
translation from SQL to ADABAS direct calls is working the same way Native
ADABAS works. And I am not surprised. I am doing log tracing now to try
and see what actual commands are being used. I have also testing with a
CONNX companion tool INFONAUT and my SQL script runs in 3 seconds versus
1:56 using the SQL same script in FMP and trying to used defined indexes.
Remember, ExecuteSQL() -> ... FM is not a SQL database.
I am connecting to ADABAS.
great! can you provide a few more details on how you are doing that, please?
we are using CONNX ADABAS SQL Gateway using ODBC
1. Created a dictionary that defines adabas files and SQL data types
2. Created an ODBC driver for connection
3. Use basic sql tools to check out connection and access(all work)
4. Import data in FMP with the ODBC Data Source
5. Execute script select ........ TCP/IP access to a z/os mainframe
to a SQL driver running on the mainframe, translates SQL into ADABAS
and returns data
thank you! it is unlikely that you will be able to direct-connect FM to this. the other suggestions may point you to ways that may work (or not) for you.
I am writing my script from 'import records' for testing.
I meant that FMP15 is issuing the SELECT * COUNT not the other utility.
Retrieving data ...