DASD Billing › Implementation - Suggested Run Procedures › Billing Processing Considerations

Billing Processing Considerations

If a data set is scratched during a billing period and is later recreated or restored, the creation date of the new data set determines how charges are accumulated for it if MODE=ELAPSED, or ADDMISSING is being used.

When a data set is restored with the CA Disk Restore function or moved with the Move/Copy function, it is by default given its original create date. For the purpose of determining the data sets period of occupancy on DASD, this old date is misleading and can result in overcharges.

There are two options to help avoid this overcharging:

• Option 1 — Use the CREATE parameter in either Restore or Move/Copy functions. This parameter sets the creation date to the current date.
• Option 2 — Specify the MODE=IMMEDIATE without the ADDMISSING parameter in the command, and the data set will be charged for only one day no matter when it was restored. If the creation date is greater than the creation date of the original data set, charges will be accumulated for only the days the data set actually existed.

Note: If the creation date of the restored data set is the same as the creation date of the original data set before it was scratched and the ADDMISSING parameter is specified, the data set will be charged for all days in between the two creation dates, even if it did not exist on the volume during that time.