Address Spaces situations
You can identify common storage problems in address spaces.
- IMS_Common_PageIn_High_Critical
- The address space identified in the exception is causing high
page in rates for common storage. This can indicate a problem with
an application using too much common storage or possibly looping.
If this condition persists, look at the job logs for the started task
to determine if the region is abending.
The formula is:
Address_Spaces.Common_Page-In_Rate GE 3.0 - IMS_Common_PageIn_High_Warning
- The address space identified in the exception is causing high
page in rates for common storage. This can indicate a problem with
an application using too much common storage or possibly looping.
If this condition persists, look at the job logs for the started task
to determine if the region is abending.
The formula is:
Address_Spaces.Common_Page-In_Rate GE 2.0 AND Address_Spaces.Common_Page-In_Rate LT 3.0 - IMS_CPU_High_Critical
- The address space identified in the exception is using a higher
percent of CPU than the specified thresholds. This can indicate a
runaway task or the region is in the middle of error recovery. If
this condition persists, look at the job logs for the started task
to determine if the region is abending.
The formula is:
Address_Spaces.CPU_Percentage GE 60.00 - IMS_CPU_High_Warning
- The address space identified in the exception is using a higher
percent of CPU than the specified thresholds. This can indicate a
runaway task or the region is in the middle of error recovery. If
this condition persists, look at the job logs for the started task
to determine if the region is abending.
The formula is:
Address_Spaces.CPU_Percentage GE 50.00 AND Address_Spaces.CPU_Percentage LT 60.00 - IMS_CPU_Low_Critical
- The address space identified in the exception is using a less
than the expected percent of CPU than the specified thresholds. This
can indicate that part or all of your IMS system
has stalled. If the problem persists, verify that the JOB for the
region is running.
The formula is:
Address_Spaces.CPU_Percentage LE 10.00 - IMS_CPU_Low_Warning
- The address space identified in the exception is using a less
than the expected percent of CPU than the specified thresholds. This
could be an indication that part or all of your IMS system has stalled. If the problem persists,
verify that the JOB for the region is running.
The formula is:
Address_Spaces.CPU_Percentage LE 12.00 AND Address_Spaces.CPU_Percentage GT 10.00 - IMS_Private_PageIn_High_Critical
- The address space identified in the exception is causing high
page in rates for private storage. This can indicate a problem with
an application using too much private storage or possibly looping.
If this condition persists, look at the job logs for the started task
to determine if the region is abending.
The formula is:
Address_Spaces.Private_Page-In_Rate GE 3.0 - IMS_Private_PageIn_High_Warning
- The address space identified in the exception is causing high
page in rates for private storage. This can indicate a problem with
an application using too much private storage or possibly looping.
If this condition persists, look at the job logs for the started task
to determine if the region is abending.
The formula is:
Address_Spaces.Private_Page-In_Rate GE 2.0 AND Address_Spaces.Private_Page-In_Rate LT 3.0 - IMS_Region_EXCP_High_Critical
- The address space identified in the exception is doing more I/O
requests then the specified thresholds. The region might be in abend
processing and generating a dump or attempting to recover from I/O
errors on a database. If the problem persists, verify that the JOB
for the region is running.
The formula is:
Address_Spaces.EXCP_Rate GE 3.0 - IMS_Region_EXCP_High_Warning
- The address space identified in the exception is doing more I/O
requests then the specified thresholds. The region might be in abend
processing and generating a dump or attempting to recover from I/O
errors on a database. If the problem persists, verify that the JOB
for the region is running.
The formula is:
Address_Spaces.EXCP_Rate GE 2.0 AND Address_Spaces.EXCP_Rate LT 3.0 - IMS_Region_EXCP_Low_Critical
- The address space identified in the exception is doing fewer I/O
requests then the specified thresholds. This can indicate that part
or all of your IMS system has
stalled. If the problem persists, verify that the JOB for the region
is running.
The formula is:
Address_Spaces.EXCP_Rate LE 1.0 - IMS_Region_EXCP_Low_Warning
- The address space identified in the exception is doing fewer I/O
requests then the specified thresholds. This can indicate that part
or all of your IMS system has
stalled. If the problem persists, verify that the JOB for the region
is running.
The formula is:
Address_Spaces.EXCP_Rate LE 2.0 AND Address_Spaces.EXCP_Rate GT 1.0 - IMS_WSS_High_Critical
- The address space identified in the exception has a large working
set size then the specified threshold. This can indicate a problem
with an application not freeing up storage after it is used or possibly
a looping condition. If this condition persists, look at the job logs
for the started task to determine if the region is abending.
The formula is:
Address_Spaces.Working_Set_Size GE 1500 - IMS_WSS_High_Warning
- The address space identified in the exception has a large working
set size then the specified threshold. This can indicate a problem
with an application not freeing up storage after it is used or possibly
a looping condition. If this condition persists, look at the job logs
for the started task to determine if the region is abending.
The formula is:
Address_Spaces.Working_Set_Size GE 1200 AND Address_Spaces.Working_Set_Size LT 1500 - IMS_WSS_Low_Critical
- The address space identified in the exception has a smaller working
set size then the specified threshold. This can indicate a problem
with an application or region being in a stalled state. If this condition
persists, look at the job logs for the started task to determine if
the region is still usable.
The formula is:
Address_Spaces.Working_Set_Size LE 50 - IMS_WSS_Low_Warning
- The address space identified in the exception has a smaller working
set size then the specified threshold. This can indicate a problem
with an application or region being in a stalled state. If this condition
persists, look at the job logs for the started task to determine if
the region is still usable.
The formula is:
Address_Spaces.Working_Set_Size LE 60 AND Address_Spaces.Working_Set_Size GT 50