SQL0100 means there was no row in a table matching your selection criteria
(WHERE clause). Re-examine your statement again. If there truly is no
difference from the first run, then that means that your first run and RPG
program have somehow changed the data (either deleted it or updated it) so
there are no matching rows left for the 2nd run.
Or perhaps that query is joining to tableA and since you've already inserted
missing rows from tableB, there are no more missing rows (just extrapolating
here, we'll need more information to be more precise).
Just in case you didn't know, you can run DSPMSGD SQL0100 QSQLMSG on a
command line and see the message description explaining what that error code
means. SQL0100 is not really an error, so your processing shouldn't have
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
Subject: RUNSQLSTM Question
I am using a insert into process to "sort" the file.
The error I get is a SQL0100 error. The only difference in the two sql
statements is that the second has two extra fields in the order by
statement. Otherwise, the second was copied from the first.
This mailing list archive is Copyright 1997-2019 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