Re: ALCOBJ Fails, WRKOBJLCK Shows No Locks -- MIDRANGE-L

Subject: Re: ALCOBJ Fails, WRKOBJLCK Shows No Locks
From: Sam_L <lennon_s_j@xxxxxxxxxxx>
Date: Wed, 30 Nov 2011 17:23:16 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Definitely no referential integrity. (old, old application...)

However, the file was journaled, for Mimix. And there was a remote journal attached. Though, can't see how that would impact file locks. I did look at the journal records from 8:00 am until the problem occurred around noon and saw nothing that I didn't expect.

Sam

On 11/30/2011 5:06 PM, Alan Campin wrote:

Any referential integrity?

On Wed, Nov 30, 2011 at 2:54 PM, Sam_L<lennon_s_j@xxxxxxxxxxx> wrote:

A batch job tried:

ALCOBJ OBJ((xxxxxPF *FILE *SHRNUP *N)) WAIT(0)

It failed with CPF1002.

So it appears that something had a lock on the file that WRKOBJLCK could
not show. Any ideas?

Sam

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.