FAQ - ConnectWare
First support fpr most common questions
Does ConnectWare run under 64 bit Windows Systems?
On 64 bit systems the system environment e.g. "program files" folder and the system registry entries exist twice, for 64 bit applications and for 32 bit applications. These two environments are strictly separated so that a configuration done in the first will not be seen in the second one. This also applies to the ODBC subsystem.
There are two ODBC administrators to define data sources for the 64 bit and for the 32 bit environment. If you simply start the "ODBCAD32.EXE" either directly or from a system panel you will always get the 64 bit version and data sources that you define will only be usable from 64 bit applications. This "ODBCAD32.EXE" is located in the "\WINDOWS\SYSTEM32" directory. Microsoft kept the original names in their folders and EXE files so "\WINDOWS\SYSTEM32" really contains 64 bit applications and the "ODBCAD32.EXE" that you find there is a 64 bit version of the administrator.
If you want to configure the 32 bit ODBC subsystem you have to use the "ODBCAD32.EXE" from the "\WINDOWS\SYSWOW64" folder. This is the ODBC administrator that you have to use when you are configuring ODBC data sources for 32 bit applications that run under 64 bit Windows.
Only in the case that you have a 64 bit application you would need a 64 bit PARKWAY product.
Error messages with file status codes
To access ISAM files ConnectWare uses the appropriate ISAM file handler of each vendor of the ISAM system. As a result of each file operation these file handlers provide a file status code that indicates successful or unsuccessful execution of each operation.
Expected file status codes like "end of file reached" or "record not found" are converted to an appropriate SQL Code, SQL State and a matching message text.
Unexpected events like errors from the operating system, missing availability of storage media etc. cannot be associated to a matching SQL state. In these cases Connectware produces an SQL Code of "SQL_ERROR" with an SQL State "HY000" (general error) and the message text containing the name of the ISAM file, the operation where the error occured and the ISAM file status code.
The file status codes of ech ISAM system vendor are not standardized. You have to check the documentation of the vendor.
What does the message "Table not found MSYSCONF" in MS Access mean?
When opening a linked ODBC table in MS Access, the error "table not found" is appearing. After entering "ok", everything works.
In the PARKWAY configuration tool (access via the PARKWAY program group)
switch off the option "error in a message box" in the register "errors". This option should only be used for support purposes since all errors are displayed which are exchanged between the ODBC levels/layers also, if these messages don’t directly influence the correct function of ConnectWare. You may also search for the keyword "MSYSCONF" in the online help of MS Access. You will then get closer information on it.
What does the message "DELETE" records in MS Access mean?
When opening an ODBC table with MS Access the messages "DELETE" is displayed.
Description:
For the opening of tables, MS Access always reads the primary key values and internally generates an access table with the key values. With these values, MS Access is executing SELECT instructions with WHERE clauses. If there is something wrong with the primary key "Deleted" is indicated. The data file then is not deleted but MS Access is unable to refind the file and is giving that information.
This may occur when a COBOL picture field is not correctly filled with spaces/blanks. COBOL-sided is assumed that in a zero terminated string the field is filled up with spaces/blanks. For example: a MOVE "ABC" to an alphanumeric COBOL field PIC X(10) writes the letters "ABC" into the field and fills the last 7 digits up with 7 spaces/blanks.ConnectWare is acting the same way if the values are transferred to the File Handler. If there are indeed no spaces/blanks in the ISAM file, MS Access is unable to locate the key value.
Solution:
1. Take care COBOL-sided that the field is correctly filled with spaces/blanks or
2. Change the SQL type of the primary key from „CHAR“ into „BINARY“ when defining the columns in ConnectWare. Only then all 10 bytes will be transferred with their actual content.Similar problems occur with USAGE DISPLAY or COMP-3 fields if these are initiated with spaces/blanks or Low Value COBOL-sided/by COBOL. In this case, the fields have to be initiated correctly with „0“ or occupied with valid values.
What is a Pass Through Statement?
The "Pass Through" Option allows it to pass the SQL statement directly to the ODBC driver of ConnectWare. This is recommended when the Jet Engine of the used ODBC tool is identified as the source for a bad performance in the ODBC part. The PARKWAY driver is reading between 1000 - 5000 (depending on physical limits) data sets per second. Therefore it can raise the performance rapidly.The SQL statements must follow the ANSI SQL standard, only this is supported by ConnectWare. Tools like MS Access uses their own SQL, this is not compatible.
How can the performance of an sql statement be improved?
The following can be noticed on the issue bad performance:
ConnectWare is reading between 1000 - 5000 (depending on physical limits) data sets per second. Therefore, a very fast basic performance is guaranteed.
Known circumstances which decelerate the process extremely:
1. Unfortunately is the Jet Engine of the most tools the reason for a slow performance in the ODBC part. The Jet Engine restructered the SQL statements in several small statements before passing it to the ODBC driver. The solution is to use "Pass Through" SQL statement. With this the PARKWAY SQL engine will be used instead of the Jet Engine. This can raise the performance rapidly. It is important to write the SQL statements in ANSI SQL standard, only this is supported by ConnectWare. Tools like MS Access uses their own SQL, this is not compatible.
2. The ODBC trace is activated.
3. The SQL query is expressed unfavourable, e.g. no key values when linking with Joins.
4. The data is located on another PC to which the connection is very .
5. There is not enough space on the system software drive for the swap file.
Further procedure:
- cheking the known problems above and solving them
- executing the query with another tool to get information on the dependency of the used components
- executing the query on a local drive to get information about network dependency
How can the performance of an sql statement be improved?
The following can be noticed on the issue bad performance:
ConnectWare is reading between 1000 - 5000 (depending on physical limits) data sets per second. Therefore, a very fast basic performance is guaranteed.
Known circumstances which decelerate the process extremely:
1. Unfortunately is the Jet Engine of the most tools the reason for a slow performance in the ODBC part. The Jet Engine restructered the SQL statements in several small statements before passing it to the ODBC driver. The solution is to use "Pass Through" SQL statement. With this the PARKWAY SQL engine will be used instead of the Jet Engine. This can raise the performance rapidly. It is important to write the SQL statements in ANSI SQL standard, only this is supported by ConnectWare. Tools like MS Access uses their own SQL, this is not compatible.
2. The ODBC trace is activated.
3. The SQL query is expressed unfavourable, e.g. no key values when linking with Joins.
4. The data is located on another PC to which the connection is very .
5. There is not enough space on the system software drive for the swap file.
Further procedure:
- cheking the known problems above and solving them
- executing the query with another tool to get information on the dependency of the used components
- executing the query on a local drive to get information about network dependency
Does ConnectWare support Micro Focus Fileshare?
ConnectWare does support Micro Focus Fileshare. ConnectWare uses the Micro Focus File Handler and represents for Fileshare nothing else but a COBOL program. This means as soon as your COBOL applications work together with Fileshare, ConnectWare also is running properly in this environment.
Description:
Mainly, two points need to be considered:
1. Switch on the Micro Focus Fileshare Support:
Start the configuration tool from the PARKWAY program group and choose the register card „Micro Focus“. This register card contains the Micro Focus Fileshare V2 support:
By choosing this option, ConnectWare is initiated to use an access modul which additionally contains the communication components for the Fileshare V2 server instead of using the local Micro Focus data access modul (which can only access to a local or if assigned by a corresponding server software, to an external drive.)
2. Use of the Fileshare server
When creating a data source the Filshare server must be used:Under "path" enter the name of the Fileshare server e.g. $$FSSERVER\C:\DATA
Fileshare is a Micro Focus product. More informationen about installation und configuration can be found in the product documentation.
What is an ODBC log file and how can it be generated?
The Microsoft ODBC administrator allows to log all ODBC calls between application and driver. This information can often be useful to solve problems without an explicit error message.The steps to create the log file:
- stop all ODBC tools if they are running
- open the ODBC administrator and select the 'Tracing' tab.
- specify a new log file name (i.e. C:\PARKWAY.LOG) and start tracing
- close the ODBC administrator
- restart the tool and execute all steps until you reach the error/problem, note that the ODBC performance slows down - open the ODBC administrator and stop tracing
- send the log file to us
- please make sure that you stop the trace if it is not needed anymore- the generated file might become very large, because the reports of each session will be appended
Tip:
In the case that no log file is created it would mean that the ODBC parts are not even working and they cannot cause any problems. The problem is then located in a different component.
© All rights reserved. PARKWAY Software
Wir benötigen Ihre Zustimmung zum Laden der Übersetzungen
Wir nutzen einen Drittanbieter-Service, um den Inhalt der Website zu übersetzen, der möglicherweise Daten über Ihre Aktivitäten sammelt. Bitte überprüfen Sie die Details in der Datenschutzerklärung und akzeptieren Sie den Dienst, um die Übersetzungen zu sehen.