Direct situation analysis for the Cache CU Performance workspace

The Cache CU Performance workspace produces situation event workspaces when the following situations resolve to true:

You can navigate from one of these situation event workspaces directly to the following workspaces to do direct situation analysis:

Table 1. Situation: KS3_Cachecu_DFW_Retry_Critical/Warning
Workspace for direct situation analysis	Comments
Cache CU Volume DFW Retry	Default navigation is to this workspace. The volumes in the report are ordered by DFW Retry Percent, in descending order. The graphs map DFW Retry Percent and DFW Hit Percent. This workspace derives its data from the Cache Devices attribute table. Use this workspace to determine which volumes, if any, are being impacted by poor DFW retry percent. The report lists all volumes on the control unit. The two bar charts display those devices that are not being treated well by the cache, in other words, poor hit rates.
Cache CU DFW Retry Trend	The plot chart maps DFW Retry Percent. This workspace derives its data from the Cache Control Unit attribute table. Use this workspace to determine if the poor DFW retry percent was a spike or a constant occurrence. The corrective action required varies depending on that information.
Cache CU Volume DFW Retry History	The volumes in the report are ordered by DFW Retry Percent, in descending order. The graphs map DFW Retry Percent and DFW Hit Percent. This workspace derives its data from the Cache Devices attribute table. Use this workspace to determine which volumes, if any, were impacted by poor DFW retry percent. The report lists all volumes on the control unit at that point in time. The two bar charts display those devices that were not being treated well by the cache, in other words, poor hit rates, at that point in time.

Table 2. Situation: KS3_Cachecu_Read_HitP_Critical/Warning
Workspace for direct situation analysis	Comments
Cache CU Volume Read Hit Percent	Default navigation is to this workspace. The report is sorted in ascending order by Read Hit Percent. This workspace derives its data from the Cache Devices attribute table. Use this workspace to determine which volumes were responsible for the poor control unit read hit percent. The report lists all volumes on the control unit. The two bar charts display those devices that are not being treated well by the cache, in other words, poor hit rates.
Cache CU Read Hit Percent Trend	The plot chart maps Read Hit Percent. This workspace derives its data from the Cache Control Unit attribute table. Use this workspace to determine if the poor read hit percent was a spike or a constant occurrence. The corrective action required varies depending on that information.
Cache CU Volume Read Hit Percent History	The volumes in the report are ordered by Read Hit Percent, in ascending order. The graphs map Read Hit Percent and Write Hit Percent. This workspace derives its data from the Cache Devices attribute table. Use this workspace to determine which volumes were responsible for the poor read hit percent. The report lists all volumes on the control unit at that point in time. The two bar charts display those devices that were not being treated well by the cache, in other words, poor hit rates, at that point in time.

Table 3. Situation: KS3_Cachecu_Write_HitP_Critical/Warning
Workspace for direct situation analysis	Comments
Cache CU Volume Write Hit Percent	Default navigation is to this workspace. The report is sorted in ascending order by Write Hit Percent. This workspace derives its data from the Cache Devices attribute table. Use this workspace to determine which volumes were responsible for the poor control unit write hit percent. The report lists all volumes on the control unit. The two bar charts display those devices that are not being treated well by the cache, in other words, poor hit rates.
Cache CU Write Hit Percent Trend	The plot chart maps Write Hit Percent This workspace derives its data from the Cache Control Unit attribute table. Use this workspace to determine if the poor write hit percent was a spike or a constant occurrence. The corrective action required varies depending on that information.
Cache CU Volume Write Hit Percent History	The volumes in the report are ordered by Write Hit Percent, in ascending order. The graphs map Read Hit Percent and Write Hit Percent. This workspace derives its data from the Cache Devices attribute table. Use this workspace to determine which volumes were responsible for the poor write hit percent. The report lists all volumes on the control unit at that point in time. The two bar charts display those devices that were not being treated well by the cache, in other words, poor hit rates, at that point in time.

Table 4. Situation: KS3_Cachecu_Inact_Vols_Critical/Warning
Workspace for direct situation analysis	Comments
Cache CU Volume Inactive Status	The report contains a row for volumes with a cache status of inactive only. One bar chart shows the I/O count for the volumes. This workspace derives its data from the Cache Devices attribute table. Use this workspace to determine which volumes had an inactive status for cache.

Links

Right-clicking on the link to the left of each row of tabular data produces a pop-up menu with links to the following workspaces:

Table 5. Situation: KS3_Cachecu_DFW_Retry_Critical/Warning
Workspace for direct situation analysis	Links to other workspaces
Cache CU Volume DFW Retry	Dataset Performance Summary Physical Volume Group Cache (if applicable, in other words, supported hardware) Device Performance Details Cross System Volume Performance Volume Cache Trend
Cache CU DFW Retry Trend	Cache CU Volume Historical Performance Cache CU Raid Rank Historical Data (if applicable) New workspace: Cache CU Volume DFW Retry History
Cache CU Volume DFW Retry History	Dataset Historic Performance

Table 6. Situation: KS3_Cachecu_Read_HitP_Critical/Warning
Workspace for direct situation analysis	Links to other workspaces
Cache CU Volume Read Hit Percent	Dataset Performance Summary Physical Volume Group Cache (if applicable, in other words, supported hardware) Device Performance Details Cross System Volume Performance Volume Cache Trend
Cache CU Read Hit Percent Trend	Cache CU Volume Historical Performance Cache CU Raid Rank Historical Data (if applicable) New workspace: Cache CU Volume Read Hit Percent History
Cache CU Volume Read Hit Percent History	Dataset Historic Performance

Table 7. Situation: KS3_Cachecu_Write_HitP_Critical/Warning
Workspace for direct situation analysis	Links to other workspaces
Cache CU Volume Write Hit Percent	Dataset Performance Summary Physical Volume Group Cache (if applicable, in other words, supported hardware) Device Performance Details Cross System Volume Performance Volume Cache Trend
Cache CU Write Hit Percent Trend	Cache CU Volume Historical Performance Cache CU Raid Rank Historical Data (if applicable) New workspace: Cache CU Volume Write Hit Percent History
Cache CU Volume Write Hit Percent History	Dataset Historic Performance

Table 8. Situation: KS3_Cachecu_Inact_Vols_Critical/Warning
Workspace for direct situation analysis	Links to other workspaces
Cache CU Volume Inactive Status	Dataset Performance Summary