The TSORATE statement is optional. Use it to introduce an accounting algorithm for chargeback to TSO users.
Similar to the RATE statement for batch jobs, this statement enables the distribution of computer costs associated with TSO sessions as recorded by SMF record types 34, 35, and 40. The TSORATE statement is only applicable to TSO sessions and may be omitted when no data elements involving TSO charges or percentages are selected for a given report.
The CPU identification code associates each TSORATE statement with the appropriate input accounting record. Multiple statements may be required for a given report when processing TSO records from multiple sources. The CPU identification code must match the corresponding CPU identification on the SMF input record for the algorithm to apply. If an accounting record is found that contains a CPU identification other than one found on any TSORATE statement for a given report, the accounting algorithm parameters default to the values on the first TSORATE statement defined for that report. Unless it is altered by use of the grouping feature, the CPU identification is the first character of system identification field in SMF record.
The core factor on the TSORATE statement allows charging for utilization of core storage for the duration of each TSO session. This is a dollar amount charged per 1K block of core used per hour of use during the TSO session.
The basic processor rate is the dollar amount per hour used to calculate the adjusted rate for each TSO session as follows:
Adjusted Rate = Basic Processor Rate + (Core Used x Core Factor)
The connect time rate is the dollar amount per hour used to calculate the connect charge for each TSO session as follows:
Connect Charge = Connect Time x Connect Time Rate
The time factors on the TSORATE statement enable you to weight or delete the various recorded times in calculating the processor time in hours for each TSO session:
Processor Time = Active Time x Active Time Factor +
Total CPU Time x Total CPU Time Factor
Note: Total CPU time is the sum of SRB CPU time and TCB CPU time unless the OPTION statement, positions 53 through 57, has overridden the default behavior. For non-z/OS data, SRB CPU time is always zero.
The time factors are percentages: 080 = 80%. Thus, it is possible to delete recorded times from the processor time calculation by setting the appropriate time factor to 000 (0%), or leaving the factor blank. Likewise, you can calculate the processor time using the straight or unweighted times by setting the appropriate time factor to 100 (100%).
The user-defined processor time and adjusted rate calculate the processor charge for each TSO session as follows:
Processor Charge = Processor Time x Adjusted Rate
The basic I/O rate is the dollar amount per hour used to calculate the I/O charge for each TSO session.
The I/O factors on the TSORATE statement weight or delete the various recorded I/O counts (EXCPs) for the different unit types in the calculation of I/O time in hours as follows:
(Reader I/O Count
I/O Time = ───────────────── +
Reader I/O Factor
Printer I/O Count
───────────────── +
Printer I/O Factor
Punch I/O Count
───────────────── +
Punch I/O Factor
Tape I/O Count
───────────────── +
Tape I/O Factor
Disk I/O Count
───────────────── +
Disk I/O Factor
Other I/O Count
───────────────── / 3600
Other I/O Factor)
The I/O factors define the number of counts recorded for the corresponding unit type that are to be equated to one second of I/O time. In this way, the counts for peripheral devices can be converted to chargeable time. Similarly, a unit type can be omitted from the calculation of I/O time by setting the corresponding I/O factor to 000 (0%), or leaving the factor blank.
In calculating I/O time, CA JARS automatically rounds up to the nearest integer after the division operation for each term in the equation. The last division operation which converts the time from seconds to hours follows standard rounding procedures. For example, if the reader I/O count is 21 and the reader I/O factor is 10, then the first term of the equation would be calculated as three (21/10 = 2.1 = 3). Hence the smaller the factor, the less rounding occurs, providing a more accurate result.
The user-defined I/O time and basic I/O rate calculate the I/O charge for each TSO session as follows:
I/O Charge = I/O Time x Basic I/O Rate
An alternate method of computing I/O charge may be specified by omitting a basic I/O rate. In this case, each I/O factor is interpreted as a rate per thousands of EXCPs and I/O charge is calculated as follows:
I/O Charge = (Reader I/O Count x Reader I/O Factor +
Printer I/O Count x Printer I/O Factor +
Punch I/O Count x Punch I/O Factor +
Tape I/O Count x Tape I/O Factor +
Disk I/O Count x Disk I/O Factor +
Other I/O Count x Other I/O Factor ) /1000
Note that each 3-position I/O factor is interpreted as 9V99 and that the data element I/O time contains zero.
Note: In the above discussion of I/O charges, it is assumed that the OPTION statement, position 52, 'Device Connect instead of EXCPs,' was not set. If it were, then all references to EXCPs would refer to Device Connect Time. The Device Connect Time is stored in 1/1000ths of a second. Thus, in the above example, the I/O factors without a Basic I/O rate would be 9V99 dollars per Device Connect second.
The unit record rates on the TSORATE statement allows charging for utilization of unit record devices and TSO terminal activity. The U/R rates are used to calculate the U/R charge for each TSO session as follows:
U/R Charge = (TPUTS Issued x TPUT Rate +
TGETS Satisfied x TGET Rate) / 1000
Other calculated charges which are accumulated into U/R charge are controlled by FORMRATE statements.
The tape allocation charge field on the TSORATE statement allows you to affix a dollar charge to the private allocation of tape and disk units. The setup charge for each TSO session is calculated as follows:
Setup Charge = # of Tapes x Tape Allocation Charge
The total session charge is the summation of all the various charges as follows:
Total Charge = Connect Charge + Processor Charge +
I/O Charge + U/R Charge + Setup Charge
The minimum session charge on the TSORATE statement applies if it is greater than the computed total charge as per the previous discussion.
|
Position |
Field Length |
Field Name |
Notes |
|---|---|---|---|
|
1 |
1 |
Set Code |
Optional |
|
2-9 |
8 |
Statement Type |
TSORATE |
|
10 |
1 |
CPU Identification |
|
|
11-14 |
4 |
Basic Processor Rate |
9999; dollars per hour |
|
15-17 |
3 |
Basic I/O Rate |
999; dollars per hour |
|
18-21 |
4 |
Core Factor |
99V99; dollars per 1K block per hour |
|
22-25 |
4 |
Connect Time Rate |
99V99; dollars per hour |
|
26-28 |
3 |
Active Time Factor |
999; percentage |
|
29-31 |
3 |
Total CPU Time Factor |
999; percentage |
|
32-34 |
3 |
Reader I/O Factor |
999; EXCP count per second |
|
35-37 |
3 |
Printer I/O Factor |
999; EXCP count per second |
|
38-40 |
3 |
Punch I/O Factor |
999; EXCP count per second |
|
41-43 |
3 |
Tape I/O Factor |
999; EXCP count per second |
|
44-46 |
3 |
Disk I/O Factor |
999; EXCP count per second |
|
47-49 |
3 |
Other I/O Factor |
999; EXCP count per second |
|
50-61 |
12 |
Reserved |
Not used |
|
62-64 |
3 |
TPUT Rate |
9V99; dollars per 1000 |
|
65-67 |
3 |
TGET Rate |
9V99; dollars per 1000 |
|
68-70 |
3 |
Tape Allocation Charge |
9V99; dollars per private allocation |
|
71-73 |
3 |
Reserved |
9V99; dollars per private allocation |
|
74-77 |
4 |
Minimum Session Charge |
99V99; dollars |
|
78-80 |
3 |
Reserved |
Not used |
| Copyright © 2012 CA. All rights reserved. |
|