ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

MSU4HPCT and MSU4HAVG

book

Article ID: 53717

calendar_today

Updated On:

Products

CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services Datacom/AD CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Compress Data Compression for MVS Compress Data Compression for Fujitsu Cross Enterprise Application Performance Management (APM) SYSVIEW Performance Management NXBRIDGE - SYSVIEW/ENDEVOR

Issue/Introduction

Description:

MSU4HPCT and MSU4HAVG - what there is to know about these new fields.

Solution:

There are two rolling 4 hour average MSU monitor variables available in CA SYSVIEW r12:

  Variable         Description                                            
 -----------    ----------------------                                 
 MSU4HAVG       4 hour average MSU                                                
 MSU4HPCT       4 hour average MSU pct  

MSU4HAVG would be coded using a numeric MSU value. So, for example, you would code a limit of 25 to be notified if the rolling 4-hour average exceeded 25 MSU's. MSU4HPCT is the same rolling 4-hour MSU, but expressed as a percentage of the LPAR's total image capacity. So, if total image capacity was 38, then using the above example MSU4HPCT would be coded as 66 (25 as a percentage of 38).

There are no threshold variables available to monitor the growth of the MSU value from interval to interval. If you are licensed for the CAPTURE feature, there are some new displays in r12 that will help. For example, the RMMSU command.

From HELP for that command we show:

+------------------+--------------------------------------------------+        
| 4h Avg           | The average MSU/hour consumed during the last    |        
|                  | 4 hours.                                         |        
+------------------+--------------------------------------------------+

If you also had CA OPS/MVS, you could create an exec to get this data using the SYSVIEW REXX API. Or write an exec to get the data directly from the RCT.

So these fields are useful where Software Capping is concerned. There is no way at this time to generate an alert if capping is taking place for an LPAR, just if the 4 hour average is over its threshold.

Environment

Release:
Component: CA90S