RE: Job holds large number of locks (CPI1466)

Ahhh. I bet that is it. That sparked the ole memory. The last time I saw
anything like this was years ago and my previous employer. We were using
Sales Tracker and it was creating MASSIVE numbers members everyday. The
theory was that folks would create a view into history and that would pretty
much work for them and others. The reality was that they never seemed to be
reused...

Thanks !

Chuck

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of ouuch@xxxxxxxxxxx
Sent: Wednesday, February 25, 2004 12:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: Job holds large number of locks (CPI1466)

Hiya,

On 25 Feb 2004 at 7:55, Chuck Lewis wrote:

> And the verbiage goes "The job 529586/CHUCK/RBBU001C has 30000 locks.
30000
> is a suspiciously large number of locks, and it indicates that an
> application may be leaving locks behind."

We also had that during backups some time ago. After some research we found
that one file
had more than 20.000+ members. 

Check the number of objects in the libs in the savlib command. If you do a
savlib(lib1 lib2 lib3)
the save job will lock all objects in the 3 libs, and file members also
count here.

After we got rid of all these excessive members, the message went away.

Regards,

Oliver