× 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.



On 20 Mar 2013 14:20, Thomas Garvey wrote:
I'm working on an embedded SQL command that would create a temporary
file of random records from another file. The SQL statement works
when executed interactively using STRSQL, but fails with SQL0117
(Statement contains wrong number of values).

Here's the SQL statement...

create table qtemp/F3003 as
(select IREFFF,rand() as idx from QGPL/F3003
order by idx fetch first 380 rows only) with data

So, F3003
the file by that name in QGPL
exists as a table with 50 fields, and some 40,000 records. This
statement should create a new table in qtemp with 380 records,
consisting only of the IREFFF field and a random number, cast as
named as
field idx.

It works fine interactively. But when this statement is performed in
RPGLE embedded SQL (as a string, which is then PREPAREd and
EXECUTEd), I get the SQL0117. When I look up the SQL0117 explanation,
I don't see that any of the conditions exist.

FWiW the string can be executed with EXECUTE IMMEDIATE instead.

Anyone have any ideas? And I always thought: if I could do it
interactively, I could certainly do it in embedded SQL.

That would occur and be expected if the SQL honored an override of the name F3003 to the database file QGPL/F3003. Check for overrides when the application runs, versus when the STRSQL was being utilized; or use different name for the created file than the selected FROM file.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.