I received this message from the nightly backup a few weeks ago, and got such a kick out of it, I thought I'd share it. * Message . . . . : Job holds large number of Locks. Cause . . . . . . : The job YADDA/YADDA/YADDA has 30000 locks. 30000 is a suspiciously large number of locks, and it indicates that an application may be leaving locks behind. Recovery . . . : Determine whether the locks are correct for the application. To do this: 1. Display the job's locks using the Work with Job (WRKJOB) command with job name YADDA, user YADDA, job number YADDA, and option *JOBLCK. NOTES: - WRKJOB may take longer because of the large number of locks involved. - WRKJOB is usable only if the job is still active. 2. On the Work with Job display, verify: a. Which objects are locked. b. How many locks each object has. c. The type of locks involved. 3. If the locks are correct ignore this message. 4. If the locks are not correct, fix the application that acquired the locks. To release the existing locks, end the job. * One day, we'll all be heroes.

Reply With Quote