Re: This is weird: lock problems where none should exist! -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: This is weird: lock problems where none should exist!
From: Rob Berendt <rob@xxxxxxxxx>
Date: Mon, 30 Jan 2017 07:44:10 -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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Ok, I'm a bit confused. Shouldn't that be
OBJ(&LIB/&OBJname)
and not
OBJ(&LIB/&MBRname)
unless &OBJNAME = &MBRNAME

You might want to try this before the GRTOBJAUT command
WRKOBJLCK OBJ(&LIB/&OBJNAME) OBJTYPE(*FILE) OUTPUT(*PRINT)
and see if there is some process which failed to close the file or some
such thing.

You could open a PMR with IBM.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: This is weird: lock problems where none should exist! , James H. H. Lampert

This mailing list archive is Copyright 1997-2025 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.