Re: CMTW (commit wait) on a large number of jobs

[Brian Parkins <goodprophet.bp@xxxxxxxxx>]

You might get more responses on MIDRANGE-L Reeve?

Brian.

On 19/06/2025 06:33, Reeve wrote:
> A customer has been periodically experiencing a backlog of CMTW's at
> certain times of the day and we determined the cause was an attempt to save
> a read-only table using this command:
> SAVOBJ     OBJ(&table) LIB(&datalib) DEV(*SAVF) OBJTYPE(*FILE) +
>               SAVF(&SAVFLIB/&SAVF) TGTRLS(V7R3M0) UPDHST(*NO) SAVACT(*LIB) +
>
>               DTACPR(*HIGH) SAVACTWAIT(*NOMAX)
>
>
> The SAVACTWAIT(*NOMAX) is likely the villain...but why when the apps are
> just reading?
>
> There were about 1,000 *SHRRD locks on the table in question.  I set
> commitment control to *CHG.  I have WITH *NC on each select.  All SQL, of
> course.  V7R3.  The app is a complex, database-heavy pricing service
> program used in interactive and batch jobs.  I will add PRECHK(*YES)
> ACCPTH(*NO).
>
> Even though the backup in question ran every night at 1800, we didn't
> always have the problem.  There are other unrelated jobs triggering at 1800.
>
> This is a puzzler.  Thank you for your insight!
>
> --rf