7. DEFINING PARAMETERS › 7.4 Other Related Parameters

7.4 Other Related Parameters

This section contains information on other parameters related
to the operation and use of the CA MICS VAX/VMS Analyzer.
CA MICS requires that Systems to be input be identified to
ensure that your expectations in using the VAX/VMS Analyzer
are met.  Thus you must make sure that the parameter
Computing System Parameters (SYSID) has an entry for each
VAX/VMS system to be input.

If you use CA MICS Accounting and Chargeback, you should
review the following definitions:

o  Charging Elements for VAX/VMS

o  Data collection method effects on charging

o  Rounding effects on charging

These areas are discussed further in the remainder of this
section.

Computing System Parameters (SYSID)
-----------------------------------

Data in the CA MICS database are associated with and
summarized according to the computing system that produced
the raw data used to create the database data.  Each
computing system is identified by its SYSID.

Information about the SYSIDs used at your installation is
coded in prefix.MICS.PARMS(SYSID).  Changing this information
after CA MICS is in use is a two-step process:  first, change
the SYSID member in prefix.MICS.PARMS and second, execute the
job BASPGEN in the prefix.MICS.CNTL library.

CA MICS may either exclude data or terminate with a user
abend if input data comes from a SYSID that is not defined in
the PARMS library.  The choice of exclusion or termination is
discussed completely in Section 2.3.2.2 of the CA MICS
Planning, Installation, Operation, and Maintenance Guide.

The following text summarizes how to code parameters for
prefix.MICS.PARMS(SYSID):

o  The format of the statements is free-form but
   positional.  Data element placement is as follows:

   -  ORGSYSID (should match DEXOPS definitions)

   -  Logical SYSID

   -  CPU Model (enclosed in quotes)

   -  SCP (VMS, VAXVMS, or *)

   -  RMF CPU Conversion Factor (set to .  or 0)

   -  MIPS Rate (Any base unit of performance--VUPs,
                 SpecMarks etc.)
      where VUP rating for VAX 11/780 = 1

   -  System Name (1 to 30 character name enclosed in
                   quotes)

o  A sample entry in SYSID:

      VMS1 VMS1 '11/780' VMS 0 1.0 'VMS SYSTEM ONE'

o  Considerations for the CA MICS VAX/VMS Analyzer:

   -  When coding SYSID parameter for a VMS system, Logical
      SYSID may be any value, although it is typically the
      same as the ORGSYSID.  System entries in SYSID can be
      "autodefined".  In this process the ORGSYSID values
      defined in DEXOPS will be automatically added to the
      SYSID Parameter (see the Section 2.3.2.2 of the
      CA MICS Planning, Installation, Operation and
      Maintenance Guide).

   -  VMS does not use the RMF Conversion Factor.  It is
      necessary to code a value for this parameter, even for
      VMS systems, as a place holder in the SYSID statement.

   -  The MIPS rate is optional (see note below).  It is
      necessary to have a value for this parameter as a
      place holder in the SYSID statement.


                      IMPORTANT NOTE
                      ==============

The "MIPS Rate" may employ any base unit of performance and
is used to populate an element known as fffCPUNI (where fff
can refer to several files) representing the number of
instructions executed.  These elements simply represent CPU
time multiplied by the "MIPS Rate" (base) factor specified.
As a different rate can be employed in each system entry the
resultant elements can be used as a comparative measure of
work independent of machine speed.  The value if specified
may be derived from hardware vendors, comparative industry
surveys, or benchmark studies conducted at your site.  Site
benchmarks will be the best source of input however they must
be maintained over time and can be intensive in terms of
processing and staffing.  Typically any base factor(MIPS,
VUPS(VMS units of Performance), SpecMarks etc.) will
ultimately have been derived from a benchmark study on a
specific set of work and workload mix effects the ratings.

Charging Elements for VAX/VMS
-----------------------------

The CA MICS Accounting and Chargeback Guide describes the
specific charging elements available for VAX/VMS resource
usage.  In general, these elements are supplied from the
files in the VMS Accounting information area and from the
Disk Usage (DKU) file in the VMS System Usage information
area.


Data Collection Method Effects on Charging
------------------------------------------

The frequency and approach you choose for source data
collection from VMS can affect the accuracy of certain
charges for VMS usage.  Our recommendations:

o  Avoid collecting duplicate data from multiple systems for
   such resources as disk space on shared disks.  Be sure you
   are not feeding the same data into CA MICS under multiple
   SYSIDs.

o  Be aware of the impact of data collection frequency on
   disk occupancy statistics.  Disk occupancy is calculated
   in megabyte hours, which has space and duration
   components.  Duration is affected by frequency of data
   collection.  In cases where duration is relatively short,
   occupancy measures are more susceptible to rounding to
   zero for the detail measurements.


Rounding Effects on Charging
----------------------------

For VMS disk usage charging, review your definition of the
number of decimals for rounding in CA MICS Accounting and
Chargeback.  This value is set in the Accounting Options
dialog, under the General Specifications option.  A rounding
value of 4 decimal places should be adequate to maintain
accuracy for even small VMS files, depending on the charges
per megabyte hour.

Be sure to review the DISKACCT option of DEXOPS.  Your
setting for this parameter may have an impact on the rounding
effects you will experience.  See section 7.3.1, VAX/VMS
Processing Options (DEXOPS).