Resolution:
Description:
============
After upgrading to R5.2 jobs/transactions may fail with "Update refused - maximum number of updates pending".  These jobs worked at R5.0

Environment:
============
o Object Service Broker R5.2.x on z/OS

Symptoms:
=========
Jobs unexpectedly fail with "Update refused - maximum number of updates pending" after R5.2 upgrade.

Cause:
======
The above message is produced when the combined size of all the database updates in a commit exceeds the COMMITSIZE parameter value, at which point the COMMITLIMIT exception is raised.

COMMITSIZE can be between 16K and 32K.
16K is the default.

There was a bug in the R5.0 product which meant that the COMMITSIZE parm, or default, was ignored if it was less than 31K and 31K was used instead.
In R5.2 the COMMITSIZE parm works correctly.

This means that jobs that attempt to commit between 16K and 31K of data would erroneously run on R5.0 but correctly fail on R5.2.

Resolution:
===========
There are 2 possible solutions.

1) Modify the user code to commit before hitting the COMMITSIZE limit, COMMITLIMIT.

2) Change COMMITSIZE to be 32K.

Jobs fail with "Update refused - maximum number of updates pending" after upgrade to R5.2