For completeness' sake: the implicit locks placed by default are NOTIFY locks,
nd will not and cannot cause a deadlock or stall condition. Unless the code
omewhere does a KEEP... LONGTERM all potentially problematic locks will be
eleased at the end of the task. I believe Linda has already spoken to this
ssue.
Anyway; a brute force approach would be to automate a series of DCMT displays (D
C TA, D RU, D CV, etc) to run every minute or so on a PC using a tool that can
ubmit them every minute or so and record the output (e.g., something like
inrunner/Loadrunner). You might be able to correlate the stalls with what's
unning at the time they occur.
The other, uglier possibility is to use JREPORT8 to fish around in the journals
ooking for signs of a run-unit modifying the DBKEY your rununit stalled on.
Don Casey
rincipal Consultant
un Right, LLC