home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!ut-emx!slcs.slb.com!BRYDON@linus.slcs.slb.com
- From: brydon@asl.slb.com (Harvey Brydon (713)274-8281)
- Newsgroups: comp.os.vms
- Subject: Re: Help wanted : Running out of ENQLM
- Message-ID: <1992Jul22.125457.23294@slcs.slb.com>
- Date: 22 Jul 92 12:54:57 GMT
- References: <1992Jul21.123724.218@lincoln.ac.nz>
- Sender: news@slcs.slb.com (News Administrator)
- Reply-To: brydon@asl.slb.com
- Organization: Schlumberger/Anadrill Sugar Land, TX
- Lines: 19
- Nntp-Posting-Host: 129.87.14.202
-
- In article <1992Jul21.123724.218@lincoln.ac.nz>, brown@lincoln.ac.nz writes:
- >We have COBOL programs which run out of ENQLM very quickly.
- >
- >I know that ENQLM is the number of locks you can have queued at any
- >one time, and that file i/o can use locks. But I don't really know
- >much more than that, and I would like to understand what is going on.
- >[...]
- >2. What is the effect on the system of a user having a high ENQLM ?
- > How high is high ? Our default is 800. Our COBOL user normally has
- > 2000. We tried with 3000 and still didn't get very far.
-
- An ENQLM of 100 is 'a lot'. If you have values of 3000 and it isn't
- enough, I would submit that you have an application bug that is taking out
- locks and never releasing them. Check your application.
-
- ____________________________________________________________________________
- Harvey Brydon | Internet: brydon@dsn.SINet.slb.com
- Dowell Schlumberger | P.O.T.S.: (918)250-4312
- I bought my VAXstation from my uncle on his deathbead - I wrote him a check.
-