Re: SQLRPGLE CLOSE CURSOR

[tomh@xxxxxxxxx]

Just to keep the list up-to-date with my progress on resolving my problem:

After visiting with our BP, I ordered and installed PTFs SF99105, SF99096,
and SF99450.  These had no affect, my files are still left open after the
/SQL close has been executed.

Finally, I've resorted to breaking my monolithic program down into several
single-function sub-programs. Basically, I've moved each sub-procedure
intact into a separate program (each sets on *INLR), built a data
structure which I pass around as a parm (each sub-program fills in its own
part of the DS), and changed the monolith to be a driver program.  They
still do _exactly_ what they did before as sub-procedure in the monolith.
My files are now being CLOSED and RELEASED - just like I want.

I was really hoping to be able to migrate the sub-procedures into a server
module, but my guess is that if I were to do so my experience would be the
same as in leaving them in the monolith.


Hans, Barbara, et al IBMers lurking - have you been able to follow this
thread?  Is this normal behavior for imbedded SQL?