Using EASYLABEL and an AS/400 Open Database Connectivity (ODBC) Driver

The purpose of this document is to provide troubleshooting information when using an ODBC driver with EASYLABEL.

Section I. Identifies some common issues that pertain to the ODBC driver setup.
Section II.Identifies some common issues that pertain to EASYLABEL and connection to the data file specified in the ODBC driver setup.

I. Common issues pertaining to the ODBC driver setup.

Data Source Name is not listed in EASYLABEL’s « DATABASE SYSTEM » selection box.

Common Causes:
– the ODBC driver is not installed.
– the ODBC driver is installed; however the path for the data source is incorrect.

The data file name is not listed in EASYLABEL’s « TABLE NAME » selection box.

Common Causes:
– the ODBC driver version is incompatible with the application version
– the path in the ODBC driver setup is incorrect.
– the data file is already open and the ODBC driver cannot display an open file.

EASYLABEL cannot display the field names.

Common Causes:
– if there are any index files associated with the data file, the index files may be corrupt.
– the data file may be corrupt.

II. Issues regarding EASYLABEL and the data file.

On an AS/400, using Easylabel and retrieving data via ODBC, Easylabel saw 3 database files, now Easylabel only sees 2.

Previously, two of the three original physical database files were joined as a logical file. To solve an application issue, the customer changed the files on the AS/400 so that all three files were a logical join. After the change, this logical file could be read correctly as three separate database files under other applications, but not Easylabel.

On an AS/400, the data file to be used with Easylabel also creates a file of the type; SQLPKG (SQL-package). By removing this file before using Easylabel, the logical database file can be read correctly.

Customer has configured his Client Access ODBC driver correctly and can select the Database System and Table Name in EASYLABEL. When the customer tries to select a field name, the following message appears:

‘Extended Dynamic Support Disabled’

The message is generated by the ODBC driver for the AS/400. The message occurs because there is a mismatch between the SQL package object on the AS/400 server and the ODBC.INI settings for the application that uses the package object.

In the ODBC.INI file, the following line was set incorrectly:

Package = QGPL/LABELMA (FBA),2,0,1

The last three (3) values on the Package= line tells the ODBC driver about the use of the AS/400 package object when running an application. Please verify that the last three values (usage, pkg full option and pkg not used option) on the Package= line are set to one of the following:

a. Package=QGPL/LABELMA (FBA),0,0,0
b. Package=QGPL/LABELMA (FBA),2,1,1

Please refer to your Client Access AS/400 help documentation for more information.