RE: backup causing 30000 locks??

Are they specifying PRECHK(*YES)?  Do the libraries have lots of files or
lots of file members?

I had thought that the precheck generated locks.  We've been seeing this
message for years, even before we went to save while active.  It's not a
problem.  The message text states that it's just a warning that your job may
not be releasing locks.  In the case of a backup the locks are expected and
will be released when the save is complete.

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


-----Original Message-----
From: Richard B Baird [mailto:rbaird@esourceconsulting.com]
Sent: Tuesday, November 27, 2001 1:11 PM
To: midrange-l@midrange.com
Subject: backup causing 30000 locks??


hey all,

a client has just recently begun recieving this message during the nightly
backup.  it is only informational, but seems weird to me.

any ideas on whether this is a problem or normal?

Thanks!

Rick

Message ID . . . . . . :   CPI1466       Severity . . . . . . . :  10
 Message type . . . . . :   Information
 Date sent  . . . . . . :   11/26/01      Time sent  . . . . . . : 01:11:06
 Message . . . . :   Job holds large number of locks.
 Cause . . . . . :   The job 072436/QSYSOPR/QEZBKTMMON 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 QEZBKTMMON, user QSYSOPR, job number 072436, 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.

If the problem appears to be in IBM system code, use the Analyze Problem
(ANZPRB) command to report the problem to IBM. To release the existing
locks, end the job.