FAQ
OpenRDA for Intellution Fix/Dynamics

Q1 What versions of FIX intellution is supported by OpenRDA ODBC for FIX?

Q2: If I use ms-access to check out some values in the archive table. Why all delete# values shows up?

Q3: When I try to access the archive data I get the following error:[ATI][OpenRDA ODBC]fix_archive_init_group_properties() [FIX] HdaSetStart returned.

Q4: When I try to access the Archive data I get the following error:[ATI][OpenRDA ODBC] fix_archive_ntf_read() [FIX] Error adding the NTF:D11: to the group, HdaAddNtf() returned : alarm - OK

Q5: Running a query through Microsoft access 97. Get an ODBC failure error when the date range is greater than 99 days. How do I query more than 99 days?

Q6: I am having some problem with the server software. It appears to time-out when it is running overnight or over several days. Is this a limitation of the demo copy?

Q7: When setting up database entries in the administration tool, what entries can I make in the type field? I have been using fix as my type - what else is allowed in that field?

Q8: How do I access my lab data?

Q9: I have a problem when I use the 'insert into' command to update multiple tags with a single query.

Q10: I am having a problem using wildcard characters?

Q11: We have a problem generating a report using Crystal Report.

Q12: If I try to access all the nodes using Intellution Serve 7.2 I get the following error:
print_err: Error Message = fix_enum_nodes() [FIX] Problem traversing node li st, is FIX running? eda_enum_scada_nodes() returned (FE_ERR: System Error)

Q13: If we run any query on TAGVALUE or TAG table it goes in an infinite loop.

Solution: OpenRDA ODBC for Intellution and Dynamics allows fully ODBC and SQL compliant access to the real-time and historical data in an Intellution FIX 6.x, FIX 7.x or FIX Dynamics 2.x systems. It supports both read and write to the real-time database.

Solution: Do not select any field in Unique Record Identifier Window.

Solution: It looks like the problem is with the date and time setting of your system.

Please go to windows control panel | Regional Settings | Time tab |

Make sure the time style is set as h:mm:ss tt | select the Date tab |

Make sure the short date style is set as M/D/YY.

Q4: When I try to access the Archive data I get the following error.
[ATI][OpenRDA ODBC] fix_archive_ntf_read() [FIX] Error adding the
NTF:D11: to the group, HdaAddNtf() returned : alarm - OK

Solution: It looks like the error is in reading a particular tag value from your archive table. Could you please try queries on archive table for a specific tag?

select * from archive where tag='XYZ';

Please try to see which tag name is causing a problem.

Q5: Running a query through Microsoft Access 97. Get an ODBC failure error when the date range is greater than 99 days. How do I query more than 99 days?

Solution: The FIX Historical Data Access (OpenRDA ODBC driver uses this FIX library to access history files) has a limit of 99 days for duration. To query more data you need to split the date range or do multiple queries and combine the query results.

Solution: The demo copy is identical to the released version and has no limitations. The client expects to receive a response within 3600 sec. So if the server is taking longer than 1 hr to process the results it would time out. You can change this setting by editing the Openrda.ini Configuration file on the client side to have may be a 6hr timeout. The maximum setting should be less than 32000 sec's.

[CLIENT]
RESPONSE_TIME_OUT=21600

Q7: When setting up database entries in the Administration Tool, what entries can I make in the Type Field? I have been using Fix as my Type - what else is allowed in that field?

Solution: The only allowed type with OpenRDA ODBC for FIX is FIX. Our other products allow building servers to access multiple types of data sources. With the OpenRDA ODBC for FIX it only includes services to connect to FIX historian & real-time.

Our OpenAccess ODBC SDK product allows ODBC drivers to be developed for any non-SQL or proprietary databases. If in your plant you have other data sources like FIX that you would like to access from tools like MS Access, you may want to ask your vendor to consider building an ODBC driver with our toolkit. We even offer services to build custom ODBC drivers.

If you work on non-Windows platforms like Solaris, SCO UNIX, OpenVMS etc, we offer products that allow you to access any ODBC datasources on NT/95 (SQL Server, Oracle, MS Access, and FIX) from these platforms. This solution is useful for your Data Warehousing or web server projects. Please let us know if you need further details on any of our other data access products.

Q8: How do I Access My Lab Data?

Solution: Lab Data can be accessed by using the following procedure;

1. Create a directory under the HTRDATA directory (or the path under which history files are kept) called LABDATA. You can use any name you want for the directory. This will give you c:\fix32\htrdata\labdata.

2. Place all .L24 files and the associated LABDATA.DEF file in this directory.

3. From the client, you can now query the tags in the .L24 files by using LABDATA as the node name.

For example, if you have a node named DEMO, now you can either query for tags in the .HXX files for node DEMO or the lab data file using node name LABDATA.

From interactive SQL,

Select * from archive where node = 'LABDATA’ and time='6/20/1998' and duration='20:00:00';

This query will give you data for all lab data for the 20 hours on 6/20/1998.

The only current limitation is that you cannot mix lab data and regular historical data in the same directory.

Q9: I have a problem when I use the 'insert into' command to update multiple tags with a single query.
If I use the ACV field value with the following query, it is ok.
If I use the CV field value with the following query, it is not ok.

Solution: With the 'insert into' statement to Update multiple tags you can use only the ACV field values.

Please refer to the User's Manual for OpenRDA ODBC Driver for FIX Page 4-4 & 4-5.

Q10: I am having a problem using wildcard characters?

Here are the some examples for working with Wildcard characters. The example configuration is as follows:
NODE: DEMO
TAG: RM60.F_CV

- tag='%60' does NOT work. Wildcards require the "LIKE" operator

- tag LIKE 'RM__' does NOT work. Insufficient characters are specified.

- tag LIKE 'RM60' does NOT work. The extension characters are
required OR you can specify tag = 'RM60'

- tag LIKE '%60' does NOT work. The extension characters are required.

- tag LIKE '%60.F_CV' works IF there is a history block for the starting TIME.

A "history block for the starting TIME" means that a history block exists that would include that TIME, whether or not there is data in the history block.

Q11: We have a problem generating a report using Crystal Report.

This seems to be a Bug in Crystal report.
Workaround: Once you generate the report do some editing in the query manually. Open Show SQL Query Window. Now insert some characters and then delete them (i.e. just touch the query). Now either save the report without data or preview the report, it will work.

Q12: If I try to access all the nodes using Intellution Serve 7.2 I get the following error:
print_err: Error Message = fix_enum_nodes() [FIX] Problem traversing node list, is FIX running? eda_enum_scada_nodes() returned (FE_ERR: System Error)

Solution: Please contact the support at support@OpenAccessSoftware.com for the available patch.

Q13: If we run any query on TAGVALUE or TAG table it goes in an infinite loop.

Solution: Please make sure you don't have Local Node Alias option selected on your FIX Intellution server under: system configuration -> configure -> local startup.
Please contact OpenRDA FIX support at support@OpenAccessSoftware.com if you need this option.

Technical Support Number and Hours

Phone support is available from 8:00 AM to 6:00 PM PST by calling 408-350-7023 and selecting "1" for OpenRDA and FIX-ODBC support and "2" for the OpenAccess SDK family of products.

Email

For technical questions we suggest email. Please send your email to: support@OpenAccessSoftware.com You can expect a response based on your support plan.