Situations

This chapter describes the predefined situations of the product.

Overview of situations

You can use the predefined situations shipped with Tivoli® OMEGAMON® XE for Storage on z/OS® as-is or modify them to meet your requirements. If you choose to modify a predefined situation, first make a copy to ensure a fallback, if necessary. You can also create your own situations using the attributes provided by Tivoli OMEGAMON XE for Storage on z/OS.
Note: Do not modify the product-provided situations. If you want to modify a product-provided situation, copy the situation, modify the copy, and rename the copy.
 

Definition of a predefined situation

A situation is a logical expression involving one or more system conditions. Tivoli OMEGAMON XE for Storage on z/OS uses situations to monitor the systems in your network. To improve the speed with which you begin using Tivoli OMEGAMON XE for Storage on z/OS, the product provides situations that check for system conditions common to many enterprises. You can examine and if necessary, change the conditions or values being monitored to those best suited to your enterprise. Be sure to start the situations that you want to run in your environment.

Using situations

You manage situations from the Tivoli management portal using the Situation editor. Using the Situation editor you can perform the following tasks:

  • Create a situation
  • Save a situation
  • Display a situation
  • Edit a situation
  • Start, stop, or delete a situation
  • Investigate the situation event workspace for a situation

When you open the Situation editor, the left frame initially lists the situations associated with the Navigator item you selected. When you click a situation name or create a new situation, the right frame of the Situation editor opens to provide the following information about the situation and allow you to further define that situation:

Condition
View, add to, and edit the condition being tested.
Distribution
View the systems to which the situation is assigned and assign the situation to systems.
Expert advice
Write comments or instructions to be read in the situation event workspace.
Action
Specify a command to be sent to the system.

You can also enter Take Action commands, add a Take Action view to a workspace, select Take Action from the pop-up menu for an item in the Navigator's physical view, or create take action commands and save them for later use.

Until
Reset a true situation when another situation becomes true or a specified time interval elapses.

Predefined situations descriptions

The following predefined situations are included in the Tivoli OMEGAMON XE for Storage on z/OS product.

KS3_Applic_Resp_Time_Critical

If VALUE S3_Application_Monitoring.High_Dataset_MSR GE 50
Monitors the response time components to determine the reason for a poor response time when an application is accessing a data set and the response time is greater than the critical threshold. Also examine the volume for over-utilization, cache settings, and the response time components at the volume level.

KS3_Applic_Resp_Time_Warning

If VALUE S3_Application_Monitoring.High_Dataset_MSR GE 40 and
VALUE S3_Application_Monitoring.High_Dataset_MSR LT 50
Monitors the response time components to determine the reason for a poor response time when an application is accessing a data set and the response time is greater than the warning threshold. Also examine the volume for over-utilization, cache settings, and the response time components at the volume level.

KS3_Cachecu_Cache_Stat_Critical

If VALUE S3_Cache_Control_Unit.Cache_Status NE Active
Monitors for the condition where caching is not active for the control unit. Use the SETCACHE command to activate caching, if appropriate.

KS3_Cachecu_DFW_Retry_Critical

If VALUE S3_Cache_Control_Unit.DFW_Retry_Percent GE 2
Monitors for the condition where the percent of DASD fast write attempts that cannot be satisfied because a shortage of available nonvolatile storage (NVS) space exceeds the critical threshold. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, you need to move a volume or data set to another cache control unit or add NVS to this control unit.

KS3_Cachecu_DFW_Retry_Warning

If VALUE S3_Cache_Control_Unit.DFW_Retry_Percent GE 1 and 
VALUE S3_Cache_Control_Unit.DFW_Retry_Percent LT 2
Monitors for the condition where the percent of DASD fast write attempts that cannot be satisfied because a shortage of available nonvolatile storage (NVS) space has exceeded the warning threshold. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, move a volume or data set to another cache control unit or add NVS to this control unit.

KS3_Cachecu_Inact_Vols_Critical

If VALUE S3_Cache_Control_Unit.Deactivated_Volumes GE 15
Monitors for the condition where the number of deactivated volumes on the control unit exceeds the critical threshold. You can use the SETCACHE command to activate caching on the volumes, if necessary.

KS3_Cachecu_Inact_Vols_Warning

If VALUE S3_Cache_Control_Unit.Deactivated_Volumes GE 10 and 
VALUE S3_Cache_Control_Unit.Deactivated_Volumes LT 15
Monitors for the condition where the number of deactivated volumes on the control unit exceeds the warning threshold. You can use the SETCACHE command to activate caching on the volumes, if necessary.

KS3_Cachecu_NVS_Stat_Critical

If Value_S3_Cache_Control_Unit.NVS_Status NE Active
Monitors for the condition where nonvolatile storage is not active for the control unit. All writes to volumes on the control unit are written directly to the hard disk drive. Use the SETCACHE command to activate NVS (nonvolatile storage), if appropriate.

KS3_Cachecu_Read_HitP_Critical

If VALUE S3_Cache_Control_Unit.Read_Hit_Percent LE 50 and 
VALUE S3_Cache_Control_Unit.Read_Hit_Percent GT 0
Monitors for the condition where the percent of read I/O requests resolved from cache has fallen below the critical threshold. If performance is a problem, look for volume with a low read hit percent and consider moving them to another control unit to balance the load. This condition can be caused by cache-unfriendly applications or a shortage of cache.

KS3_Cachecu_Read_HitP_Warning

If VALUE S3_Cache_Control_Unit.Read_Hit_Percent LE 60 and 
VALUE S3_Cache_Control_Unit.Read_Hit_Percent GT 50
Monitors for the condition where the percent of read I/O requests resolved from cache has fallen below the warning threshold. If performance is a problem, look for volume with a low read hit percent and consider moving them to another control unit to balance the load. This condition can be caused by cache-unfriendly applications or a shortage of cache.

KS3_Cachecu_Trk_Dstg_Critical

If VALUE S3_Cache_Control_Unit.Track_Destaging_Rate GE 70
Monitors for the condition where the rate at which tracks are being removed from cache and written to DASD exceeds the critical threshold. If performance is being impacted, you need to migrate data sets or volumes to another cache control unit. An alternative is to increase the cache capacity.

KS3_Cachecu_Trk_Dstg_Warning

If VALUE S3_Cache_Control_Unit.Track_Destaging_Rate GE 50 and 
VALUE S3_Cache_Control_Unit.Track_Destaging_Rate LT 70
Monitors for the condition where the rate at which tracks are being removed from cache and written to DASD exceeds the warning threshold. If performance is being impacted, you need to migrate data sets or volumes to another cache control unit. An alternative is to increase the cache capacity.

KS3_Cachecu_Trk_Stag_Critical

IF VALUE S3_Cache_Control_Unit.Track_Staging_Rate GE 70
Monitors for the condition where the movement of tracks from the physical device to cache has exceeded the critical threshold. If performance is impacted, you might need to move the logical volume that is causing the excessive activity or to move data sets on the logical volume.

KS3_Cachecu_Trk_Stag_Warning

IF VALUE S3_Cache_Control_Unit.Track_Staging_Rate GE 50 and 
VALUE S3_Cache_Control_Unit.Track_Staging_Rate LT 70
Monitors for the condition where the movement of tracks from the physical device to cache has exceeded the warning threshold. If performance is impacted, you might need to move the logical volume that is causing the excessive activity or to move data sets on the logical volume.

KS3_Cachecu_Write_HitP_Critical

If VALUE S3_Cache_Control_Unit.Write_Hit_Percent LE 45 and 
VALUE S3_Cache_Control_Unit.Write_Hit_Percent GE 0
Monitors for the condition where the percent of DASD/Cache fast write commands that were successfully processed without accessing the volume is below the critical threshold. If performance is impacted you might need to move a volume or data set to another control unit to balance the workload.

KS3_Cachecu_Write_HitP_Warning

If VALUE S3_Cache_Control_Unit.Write_Hit_Percent LE 50 and 
VALUE S3_Cache_Control_Unit.Write_Hit_Percent GT 45
Monitors for the condition where the percent of DASD/Cache fast write commands that were successfully processed without accessing the volume is below the warning level. If performance is impacted you might need to move a volume or data set to another control unit to balance the workload.

KS3_Channel_Busy_Pct_Critical

If VALUE S3_Channel_Path.Complex_Percent_Utilized GE 85
Monitors high response time for I/O requests to volumes being serviced by the channel due to over utilization of that channel. You might need to balance the workload between channels by moving volumes or data sets.

KS3_Channel_Busy_Pct_Warning

If VALUE S3_Channel_Path.Complex_Percent_Utilized GE 70 and 
VALUE S3_Channel_Path.Complex_Percent_Utilized LT 85
Monitors high response time for I/O requests to volumes being serviced by the channel due to over utilization of that channel. You might need to balance the workload between channels by moving volumes or data sets.

KS3_HSM_Backup_Held_Critical

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held and 
VALUE S3_HSM_Function_Summary.Function EQ Backup
Monitors the HSM backup function to see if it is being held. If the hold is inadvertent, issue the HSM RELEASE BACKUP command to allow the backup function to continue processing.

KS3_HSM_Backup_Queue_Critical

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Backup
Monitors the HSM backup queue for a condition where the number of backup requests waiting exceeds the critical threshold. If the number of backup tasks is not at the maximum, use the HSM SETSYS MAXBACKUPTASKS command to increase the number of backup tasks, thus increasing the processing rate. Keep in mind that the number of available backup volumes serves as a constraint on the number of active backup tasks.

KS3_HSM_Backup_Queue_Warning

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 and 
VALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Backup
Monitors the HSM backup queue for a condition where the number of backup requests waiting exceeds the warning threshold. If the number of backup tasks is not at the maximum, use the HSM SETSYS MAXBACKUPTASKS command to increase the number of backup tasks, thus increasing the processing rate. Keep in mind that the number of available backup volumes serves as a constraint on the number of active backup tasks.

KS3_HSM_Dump_Held_Critical

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held and 
VALUE S3_HSM_Function_Summary.Function EQ Dump
Monitors the HSM dump function to see if it is being held. If the hold is inadvertent, issue the HSM RELEASE DUMP command to allow dump processing to continue.

KS3_HSM_Dump_Queue_Critical

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held and 
VALUE S3_HSM_Function_Summary.Function EQ Dump
Monitors the HSM dump queue for a condition where the number of dump requests waiting exceeds the critical threshold. If the number of dump tasks is not at the maximum, use the HSM SETSYS MAXDUMPTASKS command to increase the number of dump tasks, thus increasing the processing rate. Keep in mind that the number of available tape drives serves as a constraint on the number of active dump tasks.

KS3_HSM_Dump_Queue_Warning

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 and 
VALUE S3_HSM_Function_Summary.Function EQ Dump and 
VALUE S3_HSM_Function_Summary.Waiting_Requests LT 50
Monitors the HSM dump queue for a condition where the number of dump requests waiting exceeds the warning threshold. If the number of dump tasks is not at the maximum, use the HSM SETSYS MAXDUMPTASKS command to increase the number of dump tasks, thus increasing the processing rate. Keep in mind that the number of available tape drives serves as a constraint on the number of active dump tasks.

KS3_HSM_Inactive_Host_Warning

IF VALUE S3_HSM_Status.Inactive_HSM_Hosts GT 0
Monitors when an inactive HSM host has been detected. The event workspace for this situation has a link to the DFSMShsm Host Details workspace.

KS3_HSM_Migrate_Held_Critical

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held and 
VALUE S3_HSM_Function_Summary.Function EQ Migration
Monitors the migrate function to see if it is being held. If the hold on the function is inadvertent, issue the HSM RELEASE MIGRATION command to allow migration to continue.

KS3_HSM_Migrate_Queue_Critical

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Migration
Monitors the HSM migration queue for a condition where the number of migration requests waiting exceeds the critical threshold. If the number of migrate tasks is not at the maximum, use the HSM SETSYS MAXMIGRATIONTASKS command to increase the number of migration tasks, thus increasing the processing rate. Note that this affects only those migrations requested by automatic functions. Only one task is available to process command migration requests.

KS3_HSM_Migrate_Queue_Warning

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 and 
VALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Migration
Monitors the HSM migration queue for a condition where the number of migration requests waiting exceeds the warning threshold. If the number of migrate tasks is not at the maximum, use the HSM SETSYS MAXMIGRATIONTASKS command to increase the number of migration tasks, thus increasing the processing rate. Note that this affects only those migrations requested by automatic functions. Only one task is available to process command migration requests.

KS3_HSM_Recall_Held_Critical

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held and 
VALUE S3_HSM_Function_Summary.Function EQ Recall
Monitors the recall function to see if it is being held. If the hold on the function is inadvertent, issue the HSM RELEASE RECALL command to allow recalls to resume.

KS3_HSM_Recall_Queue_Critical

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Recall
Monitors the HSM recall queue for a condition where the number of recall requests waiting exceeds the critical threshold. If the number of recall tasks is not at the maximum, use the HSM SETSYS MAXRECAL LTASKS command to increase the number of recall tasks, thus increasing the processing rate.

KS3_HSM_Recall_Queue_Warning

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 and 
VALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Recall
Monitors the HSM recall queue for a condition where the number of recall requests waiting exceeds the critical threshold. If the number of recall tasks is not at the maximum, use the HSM SETSYS MAXRECAL LTASKS command to increase the number of recall tasks, thus increasing the processing rate.

KS3_HSM_Recovery_Held_Critical

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held and 
VALUE S3_HSM_Function_Summary.Function EQ Recovery
Monitors the recovery function to see if it is being held. If the hold on the function is inadvertent, issue the HSM RELEASE RECOVER command to allow recovery function to resume.

KS3_HSM_Recovery_Queue_Critical

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Recovery
Monitors the HSM recovery queue for a condition where the number of recover requests waiting exceeds the critical threshold. If the number of recovery tasks is not at the maximum, use the HSM SETSYS MAXDSRECOVERTASKS command to increase the number of recover tasks, thus increasing the processing rate. Keep in mind that the number of backup tape cartridges serves as a constraint on the number of active recovery tasks.

KS3_HSM_Recovery_Queue_Warning

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 and 
VALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 and 
VALUE S3_HSM_Function_Summary.Function EQ Recovery
Monitors the HSM recovery queue for a condition where the number of recover tasks waiting exceeds the warning threshold. If the number of recovery tasks is not at the maximum, use the HSM SETSYS MAXDSRECOVERTASKS command to increase the number of recover tasks, thus increasing the processing rate. Keep in mind that the number of backup tape cartridges serves as a constraint on the number of active recovery tasks.

KS3_HSM_Status_Inactive_Crit

If VALUE S3_HSM_Status.HSM_Status EQ InActive
Monitors the status of the HSM. If status is not active, restart HSM.

KS3_LCU_Av_Delay_Q_Critical

If VALUE S3_Logical_Control_Unit.Average_Delay_Queue GE 0.500
Monitors for the condition where the average number of requests queued to devices assigned to a logical control unit due to busy conditions on physical paths has exceeded the critical threshold. If performance is impacted, you might be able to balance the workload across multiple LCUs by moving a volume or data set. Otherwise, you need to add physical paths to the LCU.

KS3_LCU_Av_Delay_Q_Warning

If VALUE S3_Logical_Control_Unit.Average_Delay_Queue GE 0.2 and 
VALUE S3_Logical_Control_Unit.Average_Delay_Queue LT 0.500
Monitors for the condition where the average number of requests queued to devices assigned to a logical control unit due to busy conditions on physical paths has exceeded the warning threshold. If performance is impacted, you might be able to balance the workload across multiple LCUs by moving a volume or data set. Otherwise, you need to add physical paths to the LCU.

KS3_LCU_Cont_Rate_Critical

If VALUE S3_Logical_Control_Unit.Contention_Rate GE 1.001
Monitors for the condition where the rate at which I/O requests are being queued to devices on a logical control unit (LCU) due to busy conditions on physical paths has exceeded the critical threshold. If performance is impacted, you need to migrate volumes or data sets to another LCU, otherwise, you need to add physical paths to the LCU.

KS3_LCU_Cont_Rate_Warning

If VALUE S3_Logical_Control_Unit.Contention_Rate GE 0.2 and 
VALUE S3_Logical_Control_Unit.Contention_Rate LT 1.001
Monitors for the condition where the rate at which I/O requests are being queued to devices on a logical control unit (LCU) due to busy conditions on physical paths has exceeded the warning threshold. If performance is impacted, you need to migrate volumes or data sets to another LCU, otherwise, you need to add physical paths to the LCU.

KS3_LCU_IO_Rate_Sec_Critical

If VALUE S3_Logical_Control_Unit.Channel_Path_I/O_Rate GE 600
Monitors for the condition where the I/O rate per second to volumes in the logical control unit (LCU) has exceeded the critical threshold. If performance is impacted, you need to balance the workload across multiple LCUs by moving volumes or data sets.

KS3_LCU_IO_Rate_Sec_Warning

If VALUE S3_Logical_Control_Unit.Channel_Path_I/O_Rate GE 200 and 
VALUE S3_Logical_Control_Unit.Channel_Path_I/O_Rate LT 600
Monitors for the condition where the I/O rate per second to volumes in the logical control unit (LCU) has exceeded the warning threshold. If performance is impacted, you need to balance the workload across multiple LCUs by moving volumes or data sets.

KS3_RMM_CDS_Backup_Critical

IF VALUE S3_RMM_Control_Dataset.Days_Since_Last_Backup GT 3
The number of days since the last backup of the DFSMSrmm™ CDS or Journal exceeded the critical threshold.

KS3_RMM_CDS_Backup_Warning

IF VALUE S3_RMM_Control_Dataset.Days_Since_Last_Backup GT 1 
AND VALUE S3_RMM_Control_Dataset.Days_Since_Last_Backup LE 3
The number of days since the last backup of the DFSMSrmm CDS or Journal exceeded the warning threshold.

KS3_RMM_CDS_Space_Critical

IF VALUE S3_RMM_Control_Dataset.RMM_Percent_Used GT 90
The percentage of space used by the DFSMSrmm CDS or Journal is greater than the critical threshold.

KS3_RMM_CDS_Space_Warning

IF VALUE S3_RMM_Control_Dataset.RMM_Percent_Used GE 80 AND 
VALUE S3_RMM_Control_Dataset.RMM_Percent_Used LE 90
The percentage of space used by the DFSMSrmm CDS or Journal is greater than the warning threshold.

KS3_RMM_Exit_Status_Critical

IF ( ( VALUE S3_RMM_Config.EDGUX200_Status NE Enabled ) OR 
( VALUE S3_RMM_Config.EDGUX100_Status NE Enabled ) )
The DFSMSrmm EDGUX100 or EDGUX200 exit is not Enabled.

KS3_RMM_Journal_Status_Critical

IF VALUE S3_RMM_Config.Journal_Status NE Enabled
The DFSMSrmm Journal is either Disabled or Locked. DFSMSrmm does not allow further updates to the journal until BACKUP is run to back up the DFSMSrmm control data set and to clear the journal. If the Journal is Locked, DFSMSrmm fails any requests that result in an update to the DFSMSrmm control data set. Message EDG2103D might also have been issued to the DFSMSrmm operator console.

KS3_RMM_Operating_Mode_Warning

IF VALUE S3_RMM_Config.Operating_Mode NE Protect
DFSMSrmm is not operating in Protect mode. Certain actions that should be rejected are permitted if DFSMSrmm is not operating in protect mode, for example attempting to read a scratch tape volume.

KS3_RMM_Scratch_Tape_Critical

IF VALUE S3_RMM_Summary.Type EQ 0 AND 
VALUE S3_RMM_Summary.Scratch_Volumes LT 100
The number of Scratch volumes is below the critical threshold.

KS3_RMM_Scratch_Tape_Warning

IF VALUE S3_RMM_Summary.Type EQ 0 AND 
VALUE S3_RMM_Summary.Scratch_Volumes LT 200 AND 
VALUE S3_RMM_Summary.Scratch_Volumes GE 100
The number of Scratch volumes is below the warning threshold.

KS3_RMM_Inactive_Critical

IF VALUE S3_RMM_Config.Subsystem_Status EQ Inactive
The DFSMSrmm subsystem is inactive.

KS3_Stg_Toolkit_Result_Critical

If VALUE S3_Storage_Toolkit_Result_Summary.Return_Code GT 4
A DFSMShsm™ or DFSMSdss™ command issued by the Storage Toolkit returns a value greater than 4. The DFSMShsm or DFSMSdss facilities typically return a value greater than 4 when a command fails to complete. Check the messages in the action log to determine whether the warning requires further attention.

KS3_Stg_Toolkit_Result_Warning

If VALUE S3_Storage_Toolkit_Result_Summary.Return_Code EQ 4
A DFSMShsm or DFSMSdss command issued by the Storage Toolkit returns the value 4. The DFSMShsm or DFSMSdss facilities typically return the value 4 as a warning. Check the messages in the action log to determine whether the warning requires further attention.

KS3_Storage_Gr_Pct_Free_Crit

IF VALUE S3_Volume_Group_Summary.Free_Space_Percent LT 5.0 AND 
VALUE S3_Volume_Group_Summary.Group_Type EQ SMSGROUP AND 
VALUE S3_Vol ume_Group_Summary.Free_Space_Percent GE 0.0
Monitors the percentage of free space available for allocation in the storage group and detects when free space has dropped below the critical threshold. To prevent allocation failures, you might have to either add one or more logical volumes to the storage group, or to move data sets off of the logical volumes in the storage group.

KS3_Storage_Gr_Pct_Free_Warning

IF VALUE S3_Volume_Group_Summary.Free_Space_Percent LT 10.0 AND 
VALUE S3_Volume_Group_Summary.Group_Type EQ SMSGROUP AND 
VALUE S3_Volume_Group_Summary.Free_Space_Percent GE 5.0",
Monitors the percentage of free space available for allocation in the storage group and detects when free space has dropped below the warning threshold. In order to prevent allocation failures, you might have to either add one or more logical volumes to the storage group, or to migrate data sets off of the logical volumes in the storage group.

KS3_Vol_Cache_DFW_Retry_Critical

If VALUE S3_Cache_Devices.DFW_Retry_Percent GE 2 and 
VALUE S3_Cache_Devices.I/O_Count GE 25
Monitors for the condition where the percentage of DASD fast write attempts for a volume that cannot be satisfied due to a shortage of available nonvolatile storage (NVS) space exceeded the critical threshold. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, move a volume or data set to another cache control unit or to add NVS to this control unit.

KS3_Vol_Cache_DFW_Retry_Warning

If VALUE S3_Cache_Devices.DFW_Retry_Percent GE 1 and 
VALUE S3_Cache_Devices.DFW_Retry_Percent LT 2 and 
VALUE S3_Cache_Devices.I/O_Count GE 25
Monitors for the condition where the percentage of DASD fast write attempts for a volume that cannot be satisfied due to a shortage of available nonvolatile storage (NVS) space exceeded the warning threshold. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, move a volume or data set to another cache control unit or to add NVS to this control unit.

KS3_Vol_Cache_Read_HitP_Critical

If VALUE S3_Cache_Devices.Read_Hit_Percent LE 45 and 
VALUE S3_Cache_Devices.Read_Hit_Percent GE 0 and 
VALUE S3_Cache_Devices.I/O_Count GE 25
Monitors for the condition where the cache read hit percent is below the critical threshold. If performance is impacted determine the reason for the low read hit percent. Common problems are cache-unfriendly applications and over-utilization of the control unit.

KS3_Vol_Cache_Read_HitP_Warning

If VALUE S3_Cache_Devices.Read_Hit_Percent LE 55 and 
VALUE S3_Cache_Devices.Read_Hit_Percent GT 45 and 
VALUE S3_Cache_Devices.I/O_Count GE 25
Monitors for the condition where the cache read hit percent is below the warning threshold. If performance is impacted determine the reason for the low read hit percent. Common problems are cache-unfriendly applications and over-utilization of the control unit.

KS3_Vol_Cache_Writ_HitP_Critical

If VALUE S3_Cache_Devices.Write_Hit_Percent LE 20 and 
VALUE S3_Cache_Devices.Write_Hit_Percent GE 0 and 
VALUE S3_Cache_Devices.I/O_Count GE 25
Monitors for the condition where the cache write hit percent for a volume is below the critical threshold. Check the status of the nonvolatile storage in the cache control unit. You can move volumes or data sets to balance the workload.

KS3_Vol_Cache_Writ_HitP_Warning

If VALUE S3_Cache_Devices.Write_Hit_Percent LE 30 and 
VALUE S3_Cache_Devices.Write_Hit_Percent GT 20 and 
VALUE S3_Cache_Devices.I/O_Count GE 25
Monitors for the condition where the cache write hit percent for a volume is below the warning threshold. Check the status of the nonvolatile storage in the cache control unit. You can move volumes or data sets to balance the workload.

KS3_Vol_Disabled_VTOC_Critical

If VALUE S3_DASD_Volume_Space.VTOC_Index_Status EQ Disabled
Monitors for the condition where a VTOC index has been disabled. This condition can degrade performance on the volume. Enable the VTOC index.

KS3_Vol_EAV_Fragment_Index_Crit

IF VALUE S3_DASD_Volume_Space.Extended_Address_Volume EQ Yes AND
VALUE S3_DASD_Volume_Space.Track_Managed_Fragmentation_Index GE 850
The fragmentation index in the track managed area of an Extended Address Volume exceeds the critical threshold.

KS3_Vol_EAV_Fragment_Index_Warn

IF VALUE S3_DASD_Volume_Space.Extended_Address_Volume EQ Yes AND
VALUE S3_DASD_Volume_Space.Track_Managed_Fragmentation_Index GE 650 
AND VALUE S3_DASD_Volume_Space.Track_Managed_Fragmentation_Index LT 850
The fragmentation index in the track managed area of an Extended Address Volume exceeds the warning threshold.

KS3_Vol_EAV_Free_Space_Pct_Crit

IF VALUE S3_DASD_Volume_Space.Track_Managed_Percent_Free LE 5.0 
AND VALUE S3_DASD_Volume_Space.Track_Managed_Percent_Free GE 0.0 AND
VALUE S3_DASD_Volume_Space.Extended_Address_Volume EQ Yes
The percentage of free space in the track managed area of an Extended Address Volume is below the critical threshold.

KS3_Vol_EAV_Free_Space_Pct_Warn

IF VALUE S3_DASD_Volume_Space.Track_Managed_Percent_Free LE 10.0
AND VALUE S3_DASD_Volume_Space.Track_Managed_Percent_Free GT 5.0 AND
VALUE S3_DASD_Volume_Space.Extended_Address_Volume EQ Yes
The percentage of free space in the track managed area of an Extended Address Volume is below the warning threshold.

KS3_Vol_Fragment_Index_Critical

If VALUE S3_DASD_Volume_Space.Fragmentation_Index GE 850
Monitors for the condition where a volume has a fragmentation index that exceeds the critical threshold. Defragment the volume so that free extents are combined to help prevent data set allocation failures.

KS3_Vol_Fragment_Index_Warning

If VALUE S3_DASD_Volume_Space.Fragmentation_Index GE 650 and 
VALUE S3_DASD_Volume_Space.Fragmentation_Index LT 850
Monitors for the condition where a volume has a fragmentation index that exceeds the warning threshold. Defragment the volume so that free extents are combined to help prevent data set allocation failures.

KS3_Vol_Free_Space_Pct_Critical

If VALUE S3_DASD_Volume_Space.Percent_Free_Space LE 5 and 
VALUE S3_DASD_Volume_Space.Percent_Free_Space GE 0
Monitors for the condition where the percentage of free space on a volume is below the critical threshold. If data sets on the volume require more space, then either migrate some data sets to another volume or release space from data sets that might be over-allocated.

KS3_Vol_Free_Space_Pct_Warning

If VALUE S3_DASD_Volume_Space.Percent_Free_Space LE 10 and 
VALUE S3_DASD_Volume_Space.Percent_Free_Space GT 5
Monitors for the condition where the percentage of free space on a volume is below the critical threshold. If data sets on the volume require more space, then either migrate some data sets to another volume or release space from data sets that might be over-allocated.

KS3_Vol_Perf_Resp_Time_Critical

If VALUE S3_DASD_Volume_Performance.Response_Time GE 55 and 
VALUE S3_DASD_Volume_Performance.I/O_Count GE 25
Monitors for the condition where response time for the volume exceeds the critical threshold. Look at the volume to see if high utilization is a problem. If so, it might be necessary to migrate data sets from the volume to reduce utilization. Also check the cache status of the volume. Look at the components of I/O to determine where the time is being spent and address the problem accordingly.

KS3_Vol_Perf_Resp_Time_Warning

If VALUE S3_DASD_Volume_Performance.Response_Time GE 35 and 
VALUE S3_DASD_Volume_Performance.Response_Time LT 55 and 
VALUE S3_DASD_Volume_Performance.I/O_Count GE 25
Monitors for the condition where response time for the volume exceeds the warning threshold. Look at the volume to see whether high utilization is a problem. If so, you can migrate data sets from the volume to reduce utilization. Also check the cache status of the volume. Look at the components of I/O to determine where the time is being spent and address the problem accordingly.

KS3_VTS_Disconnect_Time_Crit

If VALUE S3_VTS_Overview.Virtual_Disconnect_Time GE 500
Monitors for the condition where the logical control unit disconnect time for the virtual tape server exceeds the critical threshold. This condition is often an indication that the tape volume cache capacity is being exceeded.

KS3_VTS_Host_GB_Warning

If VALUE S3_VTS_Overview.Host_Channel_Activity_GB GE 18
Monitors for the condition where the activity between the MVS™ system and the virtual tape server on the host channels exceeds 19 GB over the hour interval. This condition can be an indication that the virtual tape server is being overloaded.

KS3_VTS_Pct_Copy_Throt_Warn

IF VTSTPVOLC.PCTCPT  > 50
Monitors for the condition where copy is the predominant reason for throttling.

KS3_VTS_Pct_Wr_Over_Throt_Warn

IF VTSTPVOLC.PCTWROT   > 50
Monitors for the condition where write overrun is the predominant reason for throttling.

KS3_VTS_Recall_Pct_Warning

If VALUE S3_VTS_Overview.Volume_Recall_Percent GE 20
Monitors for the condition where the percent of virtual tape mounts that required a physical tape mount to be satisfied exceeded the warning threshold. This condition can lead to unacceptably large virtual mount times. If so, then investigate the reason for the recalls. If rescheduling or removing the application workload is not possible, you need to increase the cache capacity of the VTS.

KS3_VTS_Virt_MtPend_Av_Warning

If VALUE S3_VTS_Overview.Average_Virtual_Mount_Pend_Time GE 300
Monitors for the condition where the average seconds required to satisfy a virtual mount in the virtual tape subsystem exceeded the warning threshold. If this condition persists, then further study is required to determine the cause for the elongated mount times. The condition might be due to VTS-hostile applications or to a shortage of VTS resources.

KS3_VTS_Virt_MtPend_Mx_Warning

VALUE S3_VTS_Overview.Maximum_Virtual_Mount_Pend_Time EQ 900
Monitors for the condition where the maximum seconds required to satisfy a virtual mount in the virtual tape subsystem exceeded the warning threshold. If this condition persists, then further study is required to determine the cause for the elongated mount times. The condition might be due to VTS-hostile applications or to a shortage of VTS resources.