Re: Record lock question: WAITRCD override or loop w/ nn retries?

[Dan <dan27649@xxxxxxxxx>]

Thanks Jon,

I defer to your judgement, but it seems to me that a one-time override
would have far less overhead than multiple CHAIN retries that could occur
for hundreds of different CHAIN attempts.  (FWIW, this is a batch program
that runs in the middle of the night.)

We could also vary the WAITRCD value, if desired, depending on run-time
factors.

- Dan

On Thu, Nov 2, 2023 at 3:22 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

> For starters, I personally don't like the approach of issuing an override
> to the wait time. There is overhead in issuing that command.
>
> But what I meant was that it was easier to vary the wait time this way. In
> one case the probability of encountering a lock was higher at certain times
> of the day. So at those times, we would increase the sleep time before
> retrying and in some cases put out a "retry" message to the user. etc. etc.
>
> Jon P.