Expert Advice

KM5_No_Sysplex_DASD_Filter_Warn  
Situation Description
Possible Causes
Suggested Actions
Situation Description

No sysplex DASD devices are being monitored.

 

Possible Causes
  1. No sysplex DASD filter is being used.
  2. The sysplex DASD filter is too strong. All devices are being eliminated by the filter criteria.

 

Suggested Actions

If no Sysplex DASD Filter situation is in place and you wish to start monitoring Sysplex DASD information, add a Sysplex DASD Filter situation.

If a Sysplex DASD Filter is in use, consider weakening the situation's filtering criteria to allow some devices to be monitored.

Large DASD installations often have large numbers of well behaved devices that do not need constant monitoring. Eliminating monitoring of these well behaved DASD devices at the sysplex level can save significant resources. Only you can determine what filtering criteria are right for your environment. To avoid the adverse consequences of monitoring large numbers of devices, no devices are reported unless a DASD filter is provided to limit the data to interesting devices.

The product-provided situation KM5_Model_Sysplex_DASD_Filter can be used as the basis for your filtering situation. To use this model, use the Situation editor to:

  • Adjust the thresholds for the Average Response Time and I/O Rate to appropriate values for your environment.
  • Distribute it to *MVS_SYSPLEX managed system list.
  • Select the desired sampling interval (on the Formula tab). Hint: It is good to make this value similar to your RMF collection interval.
  • Set the situation to run at startup.

You can find more information about how to construct a Sysplex DASD filtering situation by clicking the following "Product Documentation" link and searching for "DASD Filtering".

Product Documentation

 

Copyright IBM Corp. 2008 All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contact IBM