Re: Weird lock problem

I was going to respond to this two hours ago.

On 7/17/23 9:44 AM, Charles Wilt wrote:

"Weird lock problem" and "lock conflict of some sort" doesn't tell us
much.

What was the actual error?

I wish I could tell you. Unfortunately, the owners of the box have it set to clear away output queues. All I can recall from memory is that after it had already written 51000 records to the file, at some point just after midnight, Saturday morning, it tried to write the 51001st record to the file, and got a lock-conflict exception message.


On 7/17/23 10:57 AM, Buck Calabro wrote:

Without specifics, one is reduced to guessing, and yet...

Consider the situation where the program in question is continuously running. Reading, adding, and updating records. This sort of access
does not require an exclusive lock on the file - *SHRUPD will do.
Now, along comes say a weekly backup, which wants a *EXCL lock on
that file. That would result in the backup throwing a 'Cannot
allocate object' error.

I think it might have been "Cannot allocate object." At any rate, even though the file is opened as "UF A," it never does an UPDATE to the file.

I was wondering if it might be their backup. But then how is it that my program was getting the exception, rather than the backup program?

And no, there shouldn't be anything else using the file.

--
JHHL