Skip to content


Folders and files

Last commit message
Last commit date

Latest commit



18 Commits

Repository files navigation


SQL iQuery for IBM i *SAVF download image Licensed Program 2COZ-IQ8

It is a Web, CL and Interactive SQL query tool for IBM i, replacing the legacy Query/400 and provides an SQL/RPG style scripting langauge for more powerful queries.

With SQL iQuery you can run SQL in any of the following environments:

  • Command Entry
  • HTML/Javscript Web pages
  • CL programs
  • menus
  • the job scheduler
  • batch jobs

Download and Installation Instructions

To download SQL iQuery for IBM i V7R3 and later click here for IBM i v7r3+ build

To download SQL iQuery for IBM i V7R2 and later click here for IBM i v7r2 build

SQL iQuery Script Reference Manual (in development)

Existing SQL iQuery customers can update to this version at no charge. It contains bug fixes and minor enhancements over prior versions.

Service, Support and Training

While SQL iQuery is completely free, users may request support, enhancements, training and local user group (LUG) lectures for a reasonable fee. Send a request for support to Bob Cozzi or contact him on LinkedIn for more information.

Installation Instructions

After you download the iQuery.savf save file, it must be uploaded to your IBM i operating system server. You can do that using FTP binary transfer from Windows, Mac OS, or Linux based PCs

I normally upload it to the QGPL library. If the file suffix being uploaded is .savf FTP should create a valid SAVF object on the system. If it is something else, such as iquery.FILE then FTP will NOT create a valid save file on the server. You can work around this by first creating a save file on the IBM i server using the CRTSAVF CL command.


Once uploaded, use the RSTLICPGM CL command to install SQL iQuery. However, before you do that, it is recommended that you deleted any current installation of SQL iQuery. To check which version, if any, you currently have installed, use the LICPGM menu.


Next scroll down, usually to the bottom of the list, and see if 2COZ-IQn is installed, where n is the iQuery version (normaly 6, 7 or 8). If it is installed, first remove that installation to prepare for the new version.


Again, where n is the installed version number.

Once deleted or if it wasn't installed, proceed with the following installation command:


Note: Use the save file name IQUERY72 if you are running on IBM i V7R2.

Once complete, you are prompted for some install-time customizations. After that screen is completed, SQL iQuery is installed and ready to go.

We include several SQL iQuery Scripts with SQL iQuery. You can verify that everything is installed correctly by running one of these scripts. For example our demo script can be run by running the following CL command:


Fixes and Enhancements Log

The following are recenty enhancements and fixes to SQL iQuery
Released DateDescription
21-JUNE-2024 Corrected an issue withe IQRYEMAIL - the SQL iQuery interface that evokes the email client selected during installation. It was not clearing a structure and caused garbage characters to appear in the email when sending attachments.

Converted SQL iQuery to a no-charge (non-license key) product. Anyone may download, install and use SQL iQuery for free; no license key required.

Support and training are chargable, if needed. Please contact Bob Cozzi for support and training options.


Corrected an issue with EMAIL options where the new FROM ADDRESS would not properly replace the configuration record &FA code when no address is specified.

Corrected an issue where users would edit the config.xml file in the iQuery config folder, changing the tags and it would improperly use any value other than ACS as the file suffix. This has been corrected.

Corrented an issue during install that would insert an improper tag when the iQuery option is selected during install.

Enhanced the WRKFUNC (Work with SQL Functions) command. It is now a stand-alone interface and works on international language systems.

21-SEP-2023Corrected an issue when STMF(XXXXXXX) is specified and STMFNAME(*STMF) is also specified. The program would create a folder named XXXXXXX and then create the output streamfile on the IFS in /home/<user>/xxxxxxx/xxxxxxx.xls Now it works as expected and creates the file /home/<user>/xxxxxxx.xls