2. COST ACCOUNTING CONCEPTS FOR IS ORGANIZATIONS › 2.7 DASD/DFHSM/SMS Storage Accounting › 2.7.2 Temporary DASD Space Accounting

2.7.2 Temporary DASD Space Accounting

Since temporary DASD data sets exist only for the duration of
the task that allocates them, the VTOC scan technique cannot
accurately capture their space allocations.  Therefore, you
should exclude your temporary data set volumes from the VTOC
scan.

You can treat costs associated with the temporary data set
volumes as overhead and recover them with the cost of the
volumes for your permanent data sets.

Another approach is to actively monitor the space allocations
when they occur.  It can be implemented using the operating
system's DADSM exits under Data Facility/Device Support
(DF/DS) to monitor each temporary data set allocation,
extent, or deletion to produce a record that contains the
data set name, cost center(s), and space allocated or
deleted.  If DF/DS is not installed, you must make operating
system modifications to provide "hooks" to capture the data.

The charging unit considerations for permanent data set
charging also apply to temporary data sets.  Note that cost
center information for temporary data sets is usually derived
from job or step level information (job name, accounting
fields, and/or user ID) because temporary data set names do
not contain sufficient information to identify the owner.  In
either case, the overhead of capturing and processing the
data must be weighed against the benefits of charging for
temporary data sets.