Re: SYSLOCKS overflow

Discussion created by ca.portal.admin on Apr 22, 2008
Concern, like beauty, is in the eye of the beholder.
It all depends on what is causing the overflow.
Is the overflow present when you detect it, or has it come and gone?
If it's come and gone, then it may just be a heavy batch cycle and changing the syslocks could cause it to go away. On the other hand, if it is during the batch cycle, once the overflow is allocated there isn't a significant amount of overhead allocated to the overflow during the processing cycle, only at the FINISH and/or COMMIT point of time when we are freeing locks.
During the free process, once we've freed the duplicates, unnecessaries, etc, we check to see if the overflow storage is completely unused. If it is, then we return the overflow storage to the storage pool. If it isn't we continue using it.
How many time in overflow, overflow allocations and highwater mark?