Re: Weird lock problem

James,
Regarding: "Unfortunately, the owners of the box have it set to clear away
output queues."
Might it be that you are looking for spooled joblogs only? Starting many
moons ago (6.1 I believe) IBM gave us the option to leave joblogs in *PND
or pending state instead of spooling them up. Try WRKJOBLOG
JOBLOGSTT(*PENDING *SPOOLED)

On Mon, Jul 17, 2023 at 3:29 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.