RE: prepared SELECT - was: runsqlstm

I do not understand your point...
By definition, SELECT statement returns a set of records.
To work with a set of records in a procedural language, you need a cursor
(to iterate through the set of records returned).
So yes, SELECT requires a cursor.

In your example

SELECT_STMT2 =  'SELECT RRN(T), QRECN, QTITY, QTISTY ',
                'FROM QAYPETIDX T',
                'ORDER BY 3   ',
                'FOR FETCH ONLY '
EXECSQL,
     'PREPARE S1 FROM :SELECT_STMT2'
(* ) EXECSQL,
     'EXECUTE S1'  <-- this won't work, you need a cursor

When statement (*) is executed without cursor - what is the target of
select?
Where values for RRN(T), QRECN, QTITY, QTISTY are supposed to go.
When you work with STRSQL or QM, there is an implicit target - display
screen or printable report - with a lot of rules, how this should look
like.
When you use procedural language, it is your responsibility to provide a
target for select list. And the vehicle to relate select list to program
variables is cursor (and a FETCH statement).


    Alexei
always speaking for myself