Re: Job holds large number of locks.

[Chuck Lewis <clewis@xxxxxxxxxx>]

Thanks Scott !

That's sort of the take I had too. Then we upgraded our 3rd party application
package and backups starting taking a LOT longer (turned out they added a BUNCH
of detail files that caused this, and of course DASD usage to go UP...). As I 
was
hunting around, I remembered this (the message) and was wondering if there was
any performance penality along with it ?

Chuck

Scott Mildenberger wrote:

> We get the message in our backup job also.  As far as I have determined this
> in not a problem and occurs because a backup job has to lock a lot of
> objects.  The message is just informational and letting you know that you
> may want to check the job that is receiving it to make sure this is proper
> that is has a lot of locks.  I think it is to watch for jobs that
> continually lock objects and never release them.  Since a backup job will
> need to lock a lot of objects then I feel it's ok, and the backup does
> release all the locks when it finishes.
>
> Scott Mildenberger
>
> > -----Original Message-----
> > From: Chuck Lewis [SMTP:clewis@iquest.net]
> > Sent: Friday, October 20, 2000 7:08 AM
> > To:   Midrange-L List
> > Subject:      Job holds large number of locks.
> >
> > Hi Folks,
> >
> > Any idea WHY I am getting this message ?
> >
> > CPI1466 - Job holds large number of locks.
> >
> > It is being logged to QSYSOPR while our backup job is running and with
> > virtually NOTHING else running at the time.
> >
> > The low level stuff says:
> >
> >  The job nnnnnn/xxxxxxxxxx/xxxxxxxxxx has 30000 locks.  30000 is a
> > suspiciously large number of locks, and it indicates that an application
> > may be leaving locks behind.
> >
> > (I would HATE to think of locks getting left behind; do I need to order
> > more bagels ?)
> >
> > And goes on to explain how to look for the causes but this is running at
> > 12:30 a.m.
> >
> > I get the message when the job FIRST starts and RIGHT before it ends an
> > hour latter...
> >
> > Thanks !
> >
> > Chuck
> >
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---