×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Using the API input qsysinc/qrpglesrc(ezdaep) - DS EZDSQLF2, variable is EZDQSTL
The length of the SQL statement captured can be very large, I have captured some statements with lengths exceeding 32k. When writing them out to a file I push the statement into a VARCHAR, current ALLOCATE on it is 4k.
So my question is, what is the most efficient means to handle these when I only will keep a set length of any returned statement? Are there breakpoints in variable sizes to consider? I have not set the maximum length yet, that is still being discussed.
Substring it? I also would like to efficiently uppercase the string to make scans easier looking for SQL keywords the IBM qsys2.parse_statement does not handle.
Chris
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
