RE: SQL0518 - What does RPG not like that the run time produces this error?

If you had some indication on the call to the update procedure that this is
(or is not) the last row to be updated, then it seems that your update
procedure could be made smart enough to do this like you want. Will that
work for you?

I don't understand your use of parameter markers in the same discussion with
unknown table names, though, so I might be missing something.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I find television very educating. Every time somebody turns on the set I go
into the other room and read a book."
-- Groucho Marx

My code is somewhat complicated by the fact that the code is dynamic
and is
a sub procedure. It does not know what the table names are until they
are
passed in to the sub procedure. Table names cannot be hard coded. So
dynamic
SQL is the only answer that I am aware of.

I need some help to create a prepare statement that can use a parameter
marker. So far I have used

Declare
Prepare
Open
Fetch
Close

for every record processed.

The process works but it is slow.

My program is event based and updating is done in a service program,
processing 1 record at a time. When I have a batch of records (say 1000)
to
process, the service program does the above for every record. I would
like
to do the DECLARE, PREPARE and OPEN once only to save the cycles. The
service program does monitor for changed file names and automatically
closes
out and initializes for each new file to be processed.

Is there a way to use parameter markers (?) in the PREPARE once in the
code
executing Declare, Prepare and Open once and then simply executing the
FETCH
repeatedly for each call?