PXM0372 XMANAGER REGION INUSE HAS REACHED SHORTAGE THRESHOLD FOR MOBJ

Products

• Detector for DB2 for z/OS

Issue/Introduction

Got several times the following messages in Xmanager output:
  
PXM0372 XMANAGER REGION INUSE HAS REACHED SHORTAGE THRESHOLD FOR MOBJ 
PDT0171 DETECTOR COLLECTION INTERVAL END FORCED DUE TO XMANAGER STORAGE SHORTAGE, DB2=SSID 
  
In the JCL there was MEMLIMIT=10G and this should be enough for Memory Objects above the bar. 

Environment

Release : 20.0

Component : CA Detector for DB2 for z/OS

Resolution

The problem is at the collection interval end when Detector has to switch to a new interval.

At the collection interval end, a new set of collection buckets are allocated and data for the new interval is stored in those buckets while the externalization process occurs for the prior interval. The memory from the prior interval is not released until the externalization process is complete. So, at interval end there is data from the prior interval held in memory, as well as data from the new interval. As you are externalizing a lot of data, the externalization process may be extended, giving the new interval time to grow in size. Bottom line, memory usage is at its highest at interval change. 

Trying increasing to MEMLIMIT=30G to avoid this problem. If the interval end problem persists then you may consider giving it another 10G.