RE: How to check for uncommitted transactions

Ended up being that a journal exit program wasn't committing a delete statement and left a lot of row locks.

Changing the commitment control type and the embedded SQL to use COMMIT's fixed the issue.



-----Original Message-----
From: CRPence [mailto:CRPbottle@xxxxxxxxx]
Sent: Friday, December 19, 2014 1:24 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: How to check for uncommitted transactions

On 19-Dec-2014 11:07 -0600, Matt Olson wrote:

Is there a way to check for uncommitted DB2 SQL transactions that are
hanging around?

Work With Commitment Definitions (WRKCMTDFN) using the *ALL option for the Job (JOB) parameter is often helpful in that regard.

I suspect there might be a database insert that is just sitting there
and hasn't been committed.

Unfortunately I have no way of finding this job, so I'm wondering what
commands would help me find it.

But a file is a known? A state of vague awareness\supposition about pending transactions, without something specific [like a specific file name] seems so amorphous. Display Record Locks (DSPRCDLCK) would show any pending inserts as locked record for the member of the database file. Reviewing the journal entries (DSPJRN) of the database file member can also help find such a job.

FWiW, a doc link:
<http://www.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_71/rzakj/rzakjfindlargeoldtx.htm>
_Finding large or old transactions_
"Use the Work with Commitment Definitions (WRKCMTDFN) command to find large or old transactions.

To find large or old transactions follow these steps:

1. Type WRKCMTDFN JOB(*ALL) OUTPUT(*PRINT) from the character-based interface.
...

This information is also shown when using either System i(r) Navigator or IBM(r) Navigator for i to display transactions, but it is easier to find large or old transactions by searching the single spool file produced by the WRKCMTDFN command, rather than having to display the properties and resource status for each transaction.
..."