The following table is a list of definition of fields in the DASD Billing report:
The user code is the account code used in DASD Billing to group particular data sets for a billing report. It is specified by the user in the USERCODT member of parmlib or by use of format-1 DSCB displacement or index level processing.
This is descriptive information for the user code. It is entered in the DSBUSERD member of parmlib, and is used for printing purposes only.
The name of the data set for which billing is being done.
The volume on which the data set occupies space.
The type of device of the volume.
The creation date of the data set (Julian format).
The date the data set was last used (Julian format).
The date that billing ACCUMULATE processing was last run for the data set.
The number of tracks that are allocated to the data set.
Note: The allocation figure represents the size of a data set at the time it was last examined. Unless it is a very static data set, its size can change from day to day. This circumstance will make it difficult for you to check the K/B DAYS or TRK DAYS field for accuracy through a manual calculation unless you already know that the data set has remained static in its allocation. The K/B DAYS or TRK DAYS fields, although correct in the report, can be misleading in such cases. keep this in mind when looking at your report.
The number of tracks that are actually being used by a data set as opposed to the number of tracks that are allocated.
The total number of kilobytes allocated to the data set multiplied by the number of days' occupancy. The algorithm is as follows:
(TRACKS * TRACK SIZE) * NUMBER OF DAYS OCCUPANCY / 1000
The total number of tracks allocated to the data set multiplied by the number of days' occupancy. The algorithm is as follows:
TRACKS * NUMBER OF DAYS OCCUPANCY
The rate of charge (per day) to be applied to a data set. The format of this field depends on which value is specified for sysparm DSBALTRT. If it is specified with a value of N, standard rate processing will be used and the format will be whole numbers. If it is specified with a value of 1, foreign currency rate processing will take effect and the format of the field will have a decimal point. (The last type of process is intended for currencies such as the Japanese yen or Italian lire.)
The total amount that is charged for the data set during this billing cycle.
The total number of data sets being billed in the billing cycle.
The total track allocation of all data sets that were billed in the billing cycle.
The total number of K/B DAYS for all data sets in the billing cycle.
The total number of TRACK DAYS for all the data sets in the billing cycle.
The total amount charged for all data sets in the billing cycle.
CA Disk DASD Billing uses fullword arithmetic in its calculations for totals. This restricts the highest number to hex 7FFFFFFF or decimal 2,147,483,647. If the number of K/B DAYS accumulated in a cycle is higher than this, the totals will be incorrect. However, the grand totals on the report will be correct.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|