Re: embedded SQL loop leaves multiple files open

Peter,

Years ago, I wrote high-level wrappers around IBM's SQL CLI procedures,
which today supports 99.9% of our SQL interface requirements. I never
really got into using SQLRPGLE interfaces much, which seem somewhat clunky
to me in comparison; That might just be personal preference. One nice thing
about the SQL CLI approach is that you have full control over the open,
navigation, and close of SQL result sets via program logic. Have you ever
considered something like that?

I don't know what you mean by a program running 300 SQL statements and
generating 300 values. You say the program joins only 4 DB tables. Couldn't
you just create an SQL View joining the 4 tables, then refresh the View 300
times using different "where" clause criteria? Seems like SQL CLI could
handle that very easily with very readable code.

We always run SQL CLI interfaces using "server" mode, where the statements
(open, navigation, close, etc.) run in an instance of one of the QSQLSVR
prestart jobs, rather than the Job which uses the result sets. SQL CLI
appears to use shared memory for communicating with Jobs which use the
result sets.

Nathan.