Re: OVRDBF - Record lock

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Note that
 dftactgrp(*no) actgrp(*Caller)

Is a bad default for ILE RPG programs called from OPM CL.

It's also bad for ILE RPG called from ILE CL, if you're using CRTBNDCL with
the default DFTACTGRP(*YES)...

In either case, you're committing the first deadly sin of ILE programming...
https://authory.com/JonParisAndSusanGantner/The-Seven-Deadly-Sins-of-ILE

Charles

On Thu, Feb 20, 2025 at 11:15 AM Shane Reeves <SReeves@xxxxxxxxxxxxxxxxxx>
wrote:

> 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
> --
> 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.