I have written a front-end program to run interactive SQL statements. I am using a technique that executes the SQL statement by passing it to STRQMQRY. My SELECTs are limited to 255 columns. Is there a way to overcome this Limit, (Maybe creating a QMFORM)? My company has just licensed the SQL product; STRSQL does not have this limit. Is there a call to a program or an API that I could use instead of STRQMQRY?
You could try specifying *OUTFILE for the output type on the STRQMQRY. And then issue RUNQRY against the *OUTFILE created by the STRQMQRY request. (Thanks to Chuck Pence for his help on this answer.)
If you want to look at other SQL-based tools, here are some other alternatives to consider. One alternative would be embedding SQL Prepare & Execute statements that could construct interactive SQL statements dynamically and execute them. If you can use a browser interface, you might want to look at the Net.Data product, it's very easy to embed SELECT statements (without a 255 column limit) and then have Net.Data perform the HTML formatting to display the results. Another possible alternative would be the graphical version of DB2 Query Manager - IBM QMF for Windows product. There are even macros to convert DB2 Query Manager definitions into QMF definitions. For more info on QMF, including trial download, click here.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this online event, Getting the Most out of SQL & DB2 UDB for the iSeries.
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
Create a host variable of the where in statement on the fly with dynamic SQL. Continue Reading
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading