Re: Unexpected SQL rollback

[CRPence <CRPbottle@xxxxxxxxx>]

On 3/22/11 6:35 PM, Mike Cunningham wrote:
> We have an application written in perl running on a linux OS that
> connects to DB2. There are SQL stored procedures that run some SQL
> functions to do some updating.  The perl app will do a series of
> calls to do inserts using the procedures/functions inside a loop. It
> will add all records except the last one. It is consistent that it
> does not keep the last record. When stepping thru the perl app we can
> see the last record in the database but then it disappears. As if the
> final record is never committed and is rolled back but no rollback is
> even done, in fact the final SQL command just after the loop is a
> COMMIT. Is there anyone who has ever seen this issue? Is there some
> way we can trace the sql being executed by the procedures/functions?
> We can trace the SQL calls being done by the perl app when it crosses
> the boundary between system but not sure how to see what's going on
> inside the procedure and functions

  Review the joblog of the server job servicing the requests.  Review 
the journal to verify the entry was rolled back, and that the final 
COMMIT was issued.  STRTRC, debug, and STRDBMON are all available at the 
server; activating debug messaging or a monitor may be available as a 
setup option from the client interface.  There is also the option of 
creating a custom logging procedure and calling that from specific 
points within the procedures\functions.

Regards, Chuck