2. USAGE GUIDELINES › 2.2 CA MICS Product Interfaces › 2.2.1 Accounting and Chargeback Interface

2.2.1 Accounting and Chargeback Interface

The CA MICS VAX/VMS Analyzer resource usage files contain
data that can be used for billing VMS system use.  This data
includes CPU time, I/O counts, and disk space usage.

See the CA MICS Accounting and Chargeback Guide for
information about the VAX/VMS Analyzer files and elements
that are used.

Accounting and Chargeback for Disk Space Usage

You can use CA MICS Accounting and Chargeback to apply a rate
per megabyte-hour against the space occupied by a file or
group of files in VMS, as recorded in the DESDKU file.  A
comprehensive series of ISPF panels guide the accounting
administrator through the process of assigning rates and
other setup activities.

The result of this administrative setup is a series of SAS
macros that are strategically invoked by the CA MICS VAX/VMS
Analyzer during the DAILY run.  No special pass of the data
is required to compute and store the cost; accounting is,
therefore, an optional but seamless extension to the
processing involved in updating the CA MICS database.

The VAX/VMS Analyzer offers a choice of DETAIL or DAYS level
accounting support for VMS disk space usage processed from
the DESDKU file.  DETAIL accounting allows each individual
file to be priced according to the space occupied over time.
DETAIL allows the customized accounting algorithms access to
variables such as UIC group and member, directory name, and
file name (DEXGRP, DEXMBR, DKUDIR, and DKUFILE respectively).

DAYS level accounting presents summarized observations from
the DAYS level DESDKU file to the CA MICS Accounting and
Chargeback algorithms.  Once summarized into a single
observation according to a set of sort/sequence variables,
variables such as DEXGRP, DEXMBR, DKUDIR, and DKUFILE for
each file are lost.  The aggregate of megabyte-hours for
multiple data files under a given organizational entity is
presented to the accounting code, based on the disk account
code assignment routine (DEXACRTD).

DAYS-level DESDKU observations presented to the accounting
code are derived from the DETAIL time-span of the DESDKU
file.  Regardless of the selection of DETAIL or DAYS, the
disk account code assignment routine is always applied to the
DETAIL level of DESDKU; therefore, all DETAIL-level variables
are available for deriving account codes.  The account code
elements are part of the set of sort/sequence variables for
both DETAIL and DAYS levels.

Chapter 7 of this guide describes the parameters you must
specify to properly implement accounting applications. The
CA MICS Accounting and Chargeback Guide discusses various
methodologies that can be used with CA MICS VAX/VMS files.