daly.michael@verizon.net
01-01-1995, 02:00 AM
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.</p> *</p> <font face="System">Message . . . . : Job holds large number of Locks. </p> 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. </p> Recovery . . . : Determine whether the locks are correct for the application. To do this: </p> 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. </p> 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. </p> 3. If the locks are correct ignore this message. </p> 4. If the locks are not correct, fix the application that acquired the locks. To release the existing locks, end the job.</font></p> *</p> One day, we'll all be heroes.