3. IMPLEMENTATION › 3.1 Strategies for DASD Accounting
3.1 Strategies for DASD Accounting
This section discusses charging for three types of data sets:
those that reside on active DASD volumes (primary storage),
those that have been migrated to migration levels 1 or 2 by
DFHSM, and backup versions. See Section 2.7, DASD/DFHSM/SMS
Storage Accounting, in the CA MICS Accounting and Chargeback
Option Concepts and Overview Guide.
CHARGING FOR ACTIVE DATA SETS ON PRIMARY STORAGE
CA MICS Accounting and Chargeback Option supports both SMS
and traditional device dependent algorithms for DASD
charging. This allows you to charge your SMS data sets by
Storage Class and Management Class while you continue to
charge your non- SMS data sets by device dependent
measurements.
If you are currently using traditional algorithms to charge
for SMS data sets, you can continue to do so, or you can
implement Storage Class and Management Class algorithms for
your SMS data sets without affecting the charges for non-SMS
data sets.
CA MICS Accounting and Chargeback Option also supports VSAM
accounting from either the VTOC or ICF catalog. See Section
2.7.5, VSAM Accounting, in the CA MICS Accounting and
Chargeback Option Concepts and Overview Guide.
CA MICS Accounting and Chargeback Option provides the
following features to support both SMS and traditional DASD
charging:
o The ACTJDA journal file for charging data sets by device
type or other traditional algorithms. You should always
activate this journal file if you are charging for DASD.
VSAM data sets can be charged from this file based on the
information available in the VTOCs; this is the default.
If you prefer, however, you can charge your VSAM data sets
based on the ICF catalog information by activating the
ACTJVS journal file described next.
o The ACTJVS journal file for charging VSAM data sets by
device type or other traditional algorithms. You only need
to activate this journal file if you want to charge for
VSAM data sets based on the information available in the
ICF catalogs. The default is to charge for VSAM data sets
in the ACTJDA file described above.
o The ACTJHF journal file for charging HFS and zFS data set
by device type or other traditional algorithms. You only
need to activate this journal file if you want to charge
for HFS and zFS data sets. The default is to charge for
HFS and zFS data set in the ACTJDA file.
o The ACTJMS journal file for charging SMS data sets by
Storage Class and Management Class algorithms. You need to
activate this journal file only if you want to charge your
SMS data sets by SMS algorithms. If you do not activate
this journal file, your SMS data sets will be charged in
the ACTJDA journal file (and in the ACTJVS journal file if
it is active).
If this file is active, it will contain all charges for
SMS data sets, both VSAM and non-VSAM, based on the
information available in the VTOCs.
NOTE: Managed data sets are identified by a non-blank
value in the VCA Storage Class (STORSTGC) variable.
o A special SMS Storage Class invoice category (7230) that
contains one charging element for each Storage Class and
also a default charging element (computation codes 1830-
1836). These charging elements can be used in the SMS
journal file and allow you to have a different rate for
each Storage Class, if necessary.
o A special SMS Management Class invoice category (7240) that
contains one charging element for each Management Class and
also a default charging element (computation codes
1840-1850). These charging elements can be used in the SMS
journal file and allow you to have a different rate for
each Management Class, if necessary.
o Device dependent and megabyte-hour charging elements for
use in the non-VSAM and VSAM journal files (computation
codes 1800-1804, 1811-1814, and 1820).
o Sample SMS charging algorithms are shipped with the SMS
non-VSAM and VSAM journal files.
o Support for DASD accounting from the VCA Analyzer files at
either the DETAIL or DAYS timespan.
The content of the journal files depends on which ones you
have activated for charging as follows:
o If only the ACTJDA journal file is active, all data sets,
VSAM and non-VSAM, SMS and non-managed, are charged in
that file.
ACTJDA Journal File
---------------------------------------------------
| SMS data sets (VSAM and non-VSAM) |
| Non-managed data sets (VSAM and non-VSAM) |
---------------------------------------------------
o If the ACTJDA and ACTJMS journal files are active, all
non-managed data sets are charged in the ACTJDA file, and
all SMS data sets are charged in the ACTJMS file.
ACTJDA Journal File
---------------------------------------------------
| Non-managed data sets (VSAM and non-VSAM) |
---------------------------------------------------
ACTJMS Journal File
---------------------------------------------------
| SMS data sets (VSAM and non-VSAM) |
---------------------------------------------------
This is the approach that we recommend.
o If the ACTJDA, ACTJHF, ACTJMS, and ACTJVS journal files are
all active, non-managed non-VSAM data sets are charged in
the ACTJDA file, all HFS and zFS data sets are charged in
the ACTJHF file, all SMS data sets (VSAM and non-VSAM) are
charged in the ACTJMS file, and non-managed VSAM data sets
are charged in the ACTJVS file.
ACTJDA Journal File
---------------------------------------------------
| Non-managed data sets (non-VSAM only) |
---------------------------------------------------
ACTJHF Journal File
---------------------------------------------------
| HFS and zFS data set |
---------------------------------------------------
ACTJMS Journal File
---------------------------------------------------
| SMS data sets (VSAM and non-VSAM) |
---------------------------------------------------
ACTJVS Journal File
---------------------------------------------------
| Non-managed data sets (VSAM only) |
---------------------------------------------------
o If only the ACTJDA and ACTJVS journal files are active, all
non-VSAM data sets (both SMS and non-managed) are charged
in the ACTJDA file and all VSAM data sets (both SMS and
non-managed) are charged in the ACTJVS file.
ACTJDA Journal File
---------------------------------------------------
| Non-VSAM data sets (SMS and non-managed) |
---------------------------------------------------
ACTJVS Journal File
---------------------------------------------------
| VSAM data sets (SMS and non-managed) |
---------------------------------------------------
o If only the ACTJDA and ACTJHF journal files are active, all
HFS and zFS data sets are charged in the ACTJHF file and
all non-managed non-VSAM data sets are charged in the
ACTJDA file.
ACTJDA Journal File
---------------------------------------------------
| Non-VSAM data sets (SMS and non-managed) |
---------------------------------------------------
ACTJHF Journal File
---------------------------------------------------
| HFS and zFS data set |
---------------------------------------------------
IMPLEMENTING SMS CHARGING ALGORITHMS
See Section 3.1.1 for instructions on how to implement SMS
Charging Algorithms.
CHARGING FOR MIGRATED DATA SETS
CA MICS Accounting and Chargeback Option supports charging
for migrated data sets with the ACTJMG Migrated Data Journal
file. This journal file is derived from the HSMMIG file and
contains information on migrated data sets from the DFHSM
Migration Control Data Set (MCDS).
The ACTJMG journal file allows you to charge different rates
for data sets based on the migration level of the data, level
1 or 2. This can be done using control variable charging
based on the HSMLEVEL variable, or using algorithm
qualification based on SUBTYPE. See Section 4.3.1.4,
Specifying Algorithms, and Section 4.3.1.5, Qualifying
Algorithms, for more information on control variable charging
and algorithm qualification.
You can also charge different rates based on the SMS
Management Class value by using control variable charging
based on the MGMTCLAS variable, or by using Algorithm
Qualification based on SUBSYSID.
Thus, used in conjunction with the VCA primary storage
journal files discussed in the previous section, the ACTJMG
journal file allows you to implement the rate pyramid shown
in Section 2.7.3 of the CA MICS Accounting and Chargeback
Option Concepts and Overview Guide.
NOTE: If you activate this journal file, you must specify NO
for the Accounting Options parameter that indicates
whether HSM data sets will be passed to the VCA DAA
and _VS journal files. Otherwise, duplicate charging
may occur. See Section 4.15, Specifying Whether HSM
Data is Available, for more information on this
specification.
CHARGING FOR BACKUP VERSIONS
CA MICS Accounting and Chargeback Option supports charging
for backup versions of data sets via the ACTJBC Backup Data
Journal file. This journal file is derived from the HSBBAC
file and contains information on backup versions of data sets
from the DFHSM Backup Control Data Set (BCDS).
The SMS Management Class is often used to indicate the backup
frequency of the data set and the number of backup versions
that must be kept. Because data sets that are backed up more
frequently, or require an extensive number of backup copies
require more space and thus have a higher cost than do those
with less stringent requirements, the ACTJBC journal file
allows you to charge different rates for data sets based on
the SMS Management Class value by using control variable
charging based on the MGMTCLAS variable, or via Algorithm
Qualification based on SUBSYSID.
See Section 4.3.1.4, Specifying Algorithms, and Section
4.3.1.5, Qualifying Algorithms, for more information on
control variable charging and algorithm qualification.
Thus, used in conjunction with the VCA primary storage
journal files discussed in the earlier section, the ACTJBC
journal file allows you to implement the rate pyramid shown
in Section 2.7.4 of the CA MICS Accounting and Chargeback
Option Concepts and Overview Guide.
NOTE: An alternate approach to using the ACTJBC journal file
to charge for backup versions of data sets would be to
have proportional rates for data sets on primary
storage based on their backup requirements (frequency
and number of versions kept). Since the size of the
backup versions will be proportional to the size of
the data set on primary storage, if you charge for
megabyte hours based on Management Class, and if you
can identify the data set's backup requirements based
on its Management Class value, this should provide a
reasonable approximation of its backup costs.
The following sections provide additional strategic
information to help you account for DASD usage:
1 - Implementing SMS Accounting
2 - Auditing DASD Charges
3 - Avoiding VCA Duplicate Charging
Copyright © 2014 CA.
All rights reserved.
|
|