SQL issues with V5R1 (resolved)

[Frank.Kolmann@xxxxxxxxxx]

The cume 3007 has resolved most of my issues.

I think I had figured out what went wrong with the ALCOBJ and
DLCOBJ commands. (I have raised this issue previously)

Due to a version upgrade we happened to recompile all our
programs.  The CRTSQLRPGI  default is CLOSQLCSR(*ENDACTGRP).
NB.  I DO ISSUE SQL CLOSE operations, what the CLOSE does is a mystery
BECAUSE  if the program is compiled with the default you can see
 files open in the job EVEN AFTER THE PROGRAM ends with LR ON.

I have programs are called repeatedly to access data from different
libraries and then the SQL cursors open the wrong files.

When other jobs did an ALCOBJ *EXCL the lock cannot be applied
due to the file being OPEN for *SHRRD even though the user is now
in a completely different process.

When I recompiled the programs with CLOSQLCSR(*ENDMOD)  the files
were correctly closed when the program ends, and the job works properly.

We use BPCS and the suppliers recommendation is to use
CLOSQLCSR(*ENDACTGRP) and not to use CLOSQLCSR(*ENDMOD).
Apart from performance issues I cannot understand why one would
issue such a recommendation.

By the way the default for CRTSQLRPG CLOSQLCSR(*ENDPGM) is the
effectively the opposite for CRTSQLRPGI .

Perhaps others have not seen the issues because these problems
only happend AFTER we recompiled all the programs AFTER we went
to V5R1.

Frank Kolmann