Resolution:
Several customers have reported  problems with the application process for database upgrades for OSB, ObjectStar, Tibco Mainframe Integrator (TMI) on z/OS.

Environment:
============
All z/OS OSB/ObjectStar/ TMI levels where a DB upgrade is being performed.

Symptoms:
=========
Non-Zero return codes from the DB maint apply process.  There MAY be no other messages.

Cause:
======
This is often caused by the Customer's data volumes being greater than that expected by the maint process and/or by customers restricting the resources available to the DB maint apply process, either in the Data Object Broker (DOB), or the Execution Environment (EE).

Resolution:
===========

The DOB parameters for
o DATAPAGELIMIT
oTRXREADLIMIT
o WORKINGSET
should be at least the default values and can be larger.


The batch EE configuration parameters should be set to include
o SESSIONMEMMAX=100M
o TRANMEMMAX=100M
o TRANMAXNUM=9

The z/OS region size should be left at 0M, or at least 300M if that is not allowed.

References:
===========
The OSB Parameters Manual in the sections on DOB & EE parameters

Problems with application of Object Service Broker (OSB)Database upgrade process on z/OS.