Re: File Still Open

On 30 Apr 2012 09:19, Jerry C. Adams wrote:

First, V5R1.

I have an SQLRPGLE program that uses embedded SQL to update multiple
records (potentially, anyway) in a master file. I build a string
based upon the user's options and then use
EXECUTE IMMEDIATE :sqlstring.
The master file is referenced only in the sqlstring;
i.e., it is not defined in the F-specs. The string is:
UPDATE TSTQS36F/"A.IVMAST"
SET impidx = 'X ' , imprcd = ' '
WHERE impidx = 'CONW' AND imprcd = ' '

I never noticed before that, when the program ends, the master file
is still open when I run DSPJOB option 14. Is this normal, some
keyword I need to add to the UPDATE string, or something else to be
sure the file is closed?

The feature of the database SQL called "parameter marker conversion" can make that statement reusable, for which a pseudo-closed cursor may be the effect. If the effectively identical statement [only difference being the literals] was performed more than once, then the second time the statement\file was only pseudo-closed to reduce the overhead for the presumed-to-occur next open; i.e. the effect would be normal. So instead of asking how to make sure the file is closed, consider instead [of trying to defeat this attempt by the SQL to improve the performance of the next open], just why would the file _need_ to be closed? Is there some problem that is caused by the file being left in that manner? To be clear, an actual problem, not merely perceived; as in, not just because a file is left open after calling this other function\program, where in this case, the SQL is the other function\program. That is to suggest, if there are no problems that arise from the file being left open, then is there really any need to ensure the file is closed.

Regards, Chuck