3. REPORTS › 3.3 VM Management Objective Reports › 3.3.4 VM Management Objective Report Options › 3.3.4.2 Report Options MACRO Example
3.3.4.2 Report Options MACRO Example
Once the management objectives for VM have been established,
they can easily be incorporated into the CA MICS VM and CMS
Analyzer reports.
The specification of the management objectives to be used in
the reporting process are defined in the #VMCMOBJ member
contained in the sharedprefix.MICS.SOURCE library. This
member consists of a series of SAS MACRO variables which
define values for the required objectives.
The #VMCMOBJ member is distributed with a set of default
values. It is the responsibility of the CA MICS System
Administrator to initially tailor the values and to maintain
them for subsequent installation changes and, of course, for
CA MICS system maintenance itself.
Prior to discussing the specification of the objectives,
several points should be explained. All values input by the
user for defining objectives are specified as SAS MACRO
variables for ease of incorporation into the reporting
process. A brief explanation of SAS MACRO variables is
provided. For instance, the objective for average Q1 service
time might be defined as:
%LET VMCSEC = 3;
A SAS MACRO variable is defined by the word %LET followed in
order by the name used to reference the variable, an equal
(=) sign, the value that is to be substituted any time the
variable is used in a SAS program, and the semicolon; which
signifies the end of the variable definition. For example,
the name of the variable in the above statement is &VMCSEC.
Any time that &VMCSEC is referenced in the CA MICS code, the
value 3 is substituted.
In changing the objectives used in the reports, you are
simply changing the appropriate MACRO variable's value to
reflect what should be used in the reports for your
installation.
You must ensure that the word %LET, the CA MICS MACRO
variable name, and the ending semicolon ARE NOT ALTERED IN
ANY WAY, and the only item changed is the value following the
equal sign.
The #VMCMOBJ member is organized to enable you to quickly
identify the values that require changing and is illustrated
in Figure 3-63.
/* AVERAGE Q1 RESPONSE SPECIFICATIONS */
%LET VMCDSECX = ? ; /* DAILY : AXIS */
%LET VMCSEC = ? ; /* : REFERENCE */
%LET VMCWSECX = ? ; /* WEEKLY : AXIS */
%LET VMCWSEC = ? ; /* : REFERENCE */
%LET VMCMSECX = ? ; /* MONTHLY : AXIS */
%LET VMCMSEC = ? ; /* : REFERENCE */
/* UPTIME SPECIFICATIONS (IN MINUTES) */
%LET VMCDUTX = ? ; /* DAILY : AXIS */
%LET VMCUT = ? ; /* : REFERENCE */
%LET VMCWUTX = ? ; /* WEEKLY : AXIS */
%LET VMCWUT = ? ; /* : REFERENCE */
/* CPU CONSUMPTION SPECIFICATION */
%LET VMCSAX = ? ; /* DAILY : AXIS */
%LET VMCSREF = ? ; /* : REFERENCE */
%LET VMCWSAX = ? ; /* WEEKLY : AXIS */
%LET VMCWSRF = ? ; /* : REFERENCE */
%LET VMCMSAX = ? ; /* MONTHLY : AXIS */
%LET VMCMSRF = ? ; /* : REFERENCE */
/* THROUGHPUT SPECIFICATION */
%LET VMCCAX = ? ; /* DAILY : AXIS */
%LET VMCCREF = ? ; /* : REFERENCE */
%LET VMCWCAX = ? ; /* WEEKLY : AXIS */
%LET VMCWCRF = ? ; /* : REFERENCE */
%LET VMCMCAX = ? ; /* MONTHLY : AXIS */
%LET VMCMCRF = ? ; /* : REFERENCE */
/* TIME SELECTION SPECIFICATION */
%LET VMCDLHR = ? ; /* DAILY : START HOUR */
%LET VMCDHHR = ? ; /* : END HOUR */
%LET VMCWLHR = ? ; /* WEEKLY : START HOUR */
%LET VMCWHHR = ? ; /* : END HOUR */
%LET VMCLOZN = ? ; /* MONTHLY : START ZONE */
%LET VMCHIZN = ? ; /* : END ZONE */
/* AVAILABILITY SPECIFICATIONS */
%LET VMCMPCT = ? ; /* MONTHLY : TARGET PERCENT */
%LET VMCRPCT = ? ; /* : REFERENCE */
Figure 3-63. VM Report Options in #VMCMOBJ
Figure 3-64 shows how the VM options have been defined in
#VMCMOBJ in the distributed version of the member.
/* AVERAGE Q1 RESPONSE SPECIFICATIONS */
%LET VMCDSECX = 0.8; /* DAILY : AXIS */
%LET VMCSEC = 0.1; /* : REFERENCE */
%LET VMCWSECX = 0.8; /* WEEKLY : AXIS */
%LET VMCWSEC = 0.1; /* : REFERENCE */
%LET VMCMSECX = 0.8; /* MONTHLY : AXIS */
%LET VMCMSEC = 0.1; /* : REFERENCE */
/* UPTIME SPECIFICATIONS (IN MINUTES) */
%LET VMCDUTX = 60 ; /* DAILY : AXIS */
%LET VMCUT = 60 ; /* : REFERENCE */
%LET VMCWUTX = 60 ; /* WEEKLY : AXIS */
%LET VMCWUT = 60 ; /* : REFERENCE */
/* CPU CONSUMPTION SPECIFICATION */
%LET VMCSAX = 3600; /* DAILY : AXIS */
%LET VMCSREF = 2700; /* : REFERENCE */
%LET VMCWSAX = 3600; /* WEEKLY : AXIS */
%LET VMCWSRF = 2700; /* : REFERENCE */
%LET VMCMSAX = 3600; /* MONTHLY : AXIS */
%LET VMCMSRF = 2700; /* : REFERENCE */
/* THROUGHPUT SPECIFICATION */
%LET VMCCAX = 50000; /* DAILY : AXIS */
%LET VMCCREF = 20000; /* : REFERENCE */
%LET VMCWCAX = 50000; /* WEEKLY : AXIS */
%LET VMCWCRF = 20000; /* : REFERENCE */
%LET VMCMCAX = 50000; /* MONTHLY : AXIS */
%LET VMCMCRF = 20000; /* : REFERENCE */
/* TIME SELECTION SPECIFICATION */
%LET VMCDLHR = 7; /* DAILY : START HOUR */
%LET VMCDHHR = 17; /* : END HOUR */
%LET VMCWLHR = 7; /* WEEKLY : START HOUR */
%LET VMCWHHR = 17; /* : END HOUR */
%LET VMCLOZN = 1; /* MONTHLY : START ZONE */
%LET VMCHIZN = 3; /* : END ZONE */
/* AVAILABILITY SPECIFICATIONS */
%LET VMCMPCT = 100; /* MONTHLY : TARGET PERCENT */
%LET VMCRPCT = 100; /* : REFERENCE */
Figure 3-64. Sample #VMCMOBJ Contents
