PXM0371 XMANAGER REGION INUSE HAS REACHED CRITICAL THRESHOLD FOR EPVT
Article ID: 103117
Updated On:
Products
Bind Analyzer for DB2 for z/OS
SQL-Ease for DB2 for z/OS
SYSVIEW Performance Management Option for DB2 for z/OS
Plan Analyzer for DB2 for z/OS
Subsystem Analyzer for DB2 for z/OS
Issue/Introduction
In the Xmanager output there were the following messages and Xmanager was shutdown.
PXM0373 XMANAGER REGION MOBJ STORAGE SHORTAGE RELIEVED
PXM0371 XMANAGER REGION INUSE HAS REACHED CRITICAL THRESHOLD FOR EPVT
PXM0370 CA/XMANAGER SHUTDOWN IN PROGRESS XMID=1900
A SVC dump was created because of an abend S878.
In the Xmanager JCL there were options OPT='CUSH64(100,200)', REGION=0M and MEMLIMIT=4G that should be enough for all the Xmanager activity.
PXM0373 XMANAGER REGION MOBJ STORAGE SHORTAGE RELIEVED
PXM0371 XMANAGER REGION INUSE HAS REACHED CRITICAL THRESHOLD FOR EPVT
PXM0370 CA/XMANAGER SHUTDOWN IN PROGRESS XMID=1900
A SVC dump was created because of an abend S878.
In the Xmanager JCL there were options OPT='CUSH64(100,200)', REGION=0M and MEMLIMIT=4G that should be enough for all the Xmanager activity.
Environment
Release:
Component: PDT
Component: PDT
Resolution
The SVC Dump has to be reviewed to be sure about the root cause of the problem but first thing you have to review is a large use of IBM DSNTIAUL program.
The way DSNTIAUL processes SQL statements is very particular. It loads them all into one large variable length buffer. The value in the length field encompasses all SQL statements in the buffer, many INSERT statements. Generally the length field represents only the SQL statement being prepared, Detector counts on this length field for capturing the SQL text.
Since DSNTIAUL program is using a non-standard way of passing the SQL text we would like to recommend that DSNTEP2 program, DSNTIAD program or another dynamic SQL program be used to execute these SQL statements.
If DSNTIAUL program is still desired, we would recommend that the collection profile be modified to exclude dynamic SQL statistics collection for PLAN DSNTIAUL.
Enable Detector Statistics Collection ==> Y
Enable dynamic SQL statistics collection ==> N <==
Enable Additional Keys Statistics collection ==> Y
Enable Standard Activity Table/Index Statistics Collection ==> Y
Enable Dynamic SQL table/Index Statistics collection ==> Y
The way DSNTIAUL processes SQL statements is very particular. It loads them all into one large variable length buffer. The value in the length field encompasses all SQL statements in the buffer, many INSERT statements. Generally the length field represents only the SQL statement being prepared, Detector counts on this length field for capturing the SQL text.
Since DSNTIAUL program is using a non-standard way of passing the SQL text we would like to recommend that DSNTEP2 program, DSNTIAD program or another dynamic SQL program be used to execute these SQL statements.
If DSNTIAUL program is still desired, we would recommend that the collection profile be modified to exclude dynamic SQL statistics collection for PLAN DSNTIAUL.
Enable Detector Statistics Collection ==> Y
Enable dynamic SQL statistics collection ==> N <==
Enable Additional Keys Statistics collection ==> Y
Enable Standard Activity Table/Index Statistics Collection ==> Y
Enable Dynamic SQL table/Index Statistics collection ==> Y
Feedback
Yes
No
Powered by
