RE: RPG Stored Procedures, SQL, and Closing files/Activation Groups

[dslessman@xxxxxxxxxxxxxxxxxxxxxx]

To all who replied:

Thanks for the replies.  Here are some results:

1. Closing the cursor returns no result set.
2. Checking SQLSTT on the open/close of the cursor will still yield the
message in the job log.
3. I will need to check into "enable persistence".  While I know generally
what you are talking about, I will need further research.
4. So far, ensuring I am not using the same name on two different declares
and not closing the cursors has eliminated the message in the job log and
everything is still working okay.

>From the standpoint of VB, everything seems to make sense.  The user starts
the application, I get a connection to the 400, a QZDASOINIT job is
started, the stored procedures run there and life is good.

What I still do not understand is from the Web side.  When I run the
application from the web, I see a QZADASOINIT server job.  That job does
not end (until I restart the server).  In the actual RPG stored procedures,
I do not turn on LR anywhere so I was assuming the program was still active
and its variables still loaded with stuff.  I figured this was like on the
S/38 where program A called program B and program B returned to program A
without LR on, subsequent calls to program B still showed its variables,
open files, etc.

ILE RPG and SQL cursors must not work that way I guess.  Any insights?

Thanks,

Dwight Slessman