RE: OVRDBF - Record lock -- MIDRANGE-L

Subject: RE: OVRDBF - Record lock
From: Shane Reeves <SReeves@xxxxxxxxxxxxxxxxxx>
Date: Thu, 20 Feb 2025 18:15:02 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Thanks everyone for the suggestions and hints.

I narrowed it down to the RPG side which I'm including here just for completeness.
It had CTL-opt dftactgrp(*no) actgrp(*Caller) which has kind of just been our default/standard in-house and something I've never had to much look into.
Changing it to actgrp(*NEW) allowed the process to only find a lock on the actual library that had a lock, and update the rest of the library/files without issue.

Thanks

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: OVRDBF - Record lock , Charles Wilt

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.