3. IMPLEMENTATION › 3.12 Implementing Tape Accounting
3.12 Implementing Tape Accounting
Follow this checklist to implement resource usage charges for
Tape Data Set using the CA MICS Tape Analyzer and CA MICS
Accounting and Chargeback.
___ 1. Ensure that CA MICS Accounting and Chargeback is
installed in each CA MICS unit that contains the Tape
Analyzer.
If you are using CA MICS Accounting and Chargeback in
a production environment, we recommend that you
implement your Tape algorithm in a test unit before
modifying your production CA MICS unit(s).
___ 2. Determine whether you wish to charge from the TLM
Analyzer files at the DETAIL or at the DAYS timespan.
Modify prefix.MICS.PARMS(TLMOPS) so that it contains
one of the following statements:
ACCOUNTING DETAIL
or
ACCOUNTING DAYS
The default is ACCOUNTING DAYS. ACCOUNTING DAYS
causes the TLM component to account for tape data
sets at the DAYS summarization level. At the DAYS
summarization level, tape data set name, VOLSER, and
other detailed information is not available. Instead,
each observation represents the total tape/megabyte
hours used by a group of tape data sets, aggregated
together, using the sequence/summary keys for the
TMCTMD file at the DAYS timespan.
If you need exception level charging based on either
VOLSER or DSNAME (or any other character data element
not in the SORT key of the DAYS timespan), you have
two choices:
1) Specify ACCOUNTING DETAIL instead of ACCOUNTING
DAYS in prefix.MICS.PARMS(TLMOPS). The downside
to this approach is the high volume of journal
records generated; one for each tape data set
segment (multiple data set segments exist for tape
data sets that span tape volumes).
2) Specify ACCOUNTING DAYS, but populate the VOLGROUP
and/or one or more account code variables
(TLMACT1-9) with data values that can be used to
apply differential rates. VOLGROUP and the
account code variables are summarization keys, so
that unique values in these elements will result
in separate DAYS timespan observations. The
VOLGROUP data element and the routine used to
populate it is discussed extensively in section
7.1.3.2 of the CA MICS Tape Analyzer Option guide.
Submit prefix.MICS.CNTL(TLMPGEN) and ensure that it
completes with condition code 0.
Perform this step for each CA MICS unit that contains
both the Tape Analyzer and CA MICS Accounting and
Chargeback.
___ 4. Select Option 6, Rate Table, from the Accounting
Parameter Specification and Generation Menu, and
select the desired unit database.
Select the ACTJTV Tape Data Set Journal File that
contains the algorithm id JTV and computation code
3300, and set the desired rate.
HINT: After you select the journal file, choose
Option 3 from the Journal File Options menu
and a list of algorithms will be displayed.
Select each algorithm to review or modify it.
If you have more than one algorithm, you will
need to use Option 4 to qualify them.
Submit the MAGRUN job when you END from the Rate
Table and ensure that it completes with condition
code 0. Review the MICSLOG to ensure that it ends
with the BAS00172I message GENERATION PROCESS
COMPLETED SUCCESSFULLY.
Review the Schedule of Rates report produced by the
MAGRUN to verify your computation code and rate for
the Tape journal file.
Perform this step for each CA MICS unit that contains
both the Tape Analyzer and CA MICS Accounting and
Chargeback.
___ 5. This completes the implementation of your Tape
charging algorithm. The ACTJTV journal file will be
created in the next CA MICS DAILY run; you should
review the Journal Run Status Log (MWF;4;2;4;5;1;1)
to validate the charges.
You can also refer to the Daily Charges Summary
Report by submitting prefix.MICS.CNTL(BGTCNTL).
3.13 Avoiding IDMS Duplicate Charging
Duplicate charging can occur when multiple computation
codes are selected for charging IDMS CPU time.
The standard computation codes whose associated data
elements contain IDMS CPU time follow:
Comp Data
Code Element Description
---- ------- -----------------------------------
1902 SUASYSTM IDMS Task CPU System Time
1903 SUAUSRTM IDMS Task CPU User Time
1904 SUACPUTM IDMS Total Task CPU Time
1905 SUASUCTM IDMS zIIP Eligible CPU Time on a CP
1906 SUASPNTM IDMS Normalized zIIP CPU Time
1907 SUAXCSTM IDMS CPU Time Without zIIP Eligible
The total CPU time on a general processor (CP) is contained
in data element SUACPUTM (1904).
This total CPU time on CP processors is broken down in two
different ways:
1) SUASYSTM (1902) + SUAUSRTM (1903) = SUACPUTM (1904)
2) SUAXCSTM (1907) + SUASUCTM (1905) = SUACPUTM (1904)
With number 1 - You can charge differently for User time
versus System time.
With number 2 - You can charge differently for work that had
to run on a CP engine versus work that could
have run on a zIIP processor if it had been
available.
The following table shows you how to avoid duplicate charging
for CP processor CPU time based on the computation codes you
use:
AVOIDING DUPLICATE CHARGES:
+-----------------------------------------------------------+
| If you charge for | You should not |
| COMP CODE: | charge for: |
|----------+-------------------|----------+-----------------|
| COMP | Associated | COMP | Associated |
| CODE | Data element | CODE | Data element |
|===========================================================|
| 1902 | SUASYSTM | 1904 | SUACPUTM |
| | | 1905 | SUASUCTM |
| | | 1907 | SUAXCSTM |
|----------|-------------------|----------|-----------------|
| 1903 | SUAUSRTM | 1904 | SUACPUTM |
| | | 1905 | SUASUCTM |
| | | 1907 | SUAXCSTM |
|----------|-------------------|----------|-----------------|
| 1904 | SUACPUTM | 1902 | SUASYSTM |
| | | 1903 | SUAUSRTM |
| | | 1905 | SUASUCTM |
| | | 1907 | SUAXCSTM |
|----------|-------------------|----------|-----------------|
| 1905 | SUASUCTM | 1902 | SUASYSTM |
| | | 1903 | SUAUSRTM |
| | | 1904 | SUACPUTM |
|----------|-------------------|----------|-----------------|
| 1907 | SUAXCSTM | 1902 | SUASYSTM |
| | | 1903 | SUAUSRTM |
| | | 1904 | SUACPUTM |
+-----------------------------------------------------------+
Copyright © 2014 CA.
All rights reserved.
|
|