Re: Query "stopped" in its tracks, still "running"

Commitment control? Ain't got no time fo' dat!

Seriously, we only recently set up journaling on our production files
because we finally got on the HA bandwagon. So, unless someone's written
an application that uses CC within the past few months (highly unlikely),
CC isn't the issue here.

(And, just for reference, I basically had to go over our tech lead's head
to develop a service program. We have at least one developer who still
codes GOTOs in RPG. It goes without saying that free-RPG is not in her
skillset.)

On Thu, Feb 15, 2018 at 12:20 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Not to be Mr. Negative but is the OP really using commitment control? Not
as many people who should, do. Out of the box vendor applications might
not because journalling wasn't supported on the S/36 and they'd hate to
modernize. That, and, implemented poorly, journalling can be a big
performance impact and they don't want Mr. Smug Competitor to be able to
say their product performs better.
If they are not doing commitment control they may have picked the wrong
option.