In the above example, line 2 shows that a user using account 634 made a total of 89 accesses to COS 1
and has 125 files stored in COS 1 which together total 4168147 storage units. The storage units reported
by the report utility may be configured in the Accounting Policy to represent bytes, kilobytes, megabytes,
or gigabytes.
Line 3 shows that 87 of the accesses to COS 1 made by account 634 were in storage class 1, and line 4
shows that 2 of them were in storage class 2. Line 3 shows that account 634 transferred 201256 bytes in
or out of storage class 1 within COS 1 and line 4 shows 0 bytes in or out of storage class 2.
Site administrators may wish to write a module that will redirect the accounting data into a local
accounting data base. This module would replace the default HPSS module, acct_WriteReport( ), which
writes out the HPSS accounting data to a flat text file.
Sites may also wish to correlate the accounting report with a site-provided Account Map (see section
13.2.3: Accounting Procedures to determine the appropriate accounting charges.
The HPSS accounting report and a copy of any current site defined accounting configuration files, if
used, should be named with the date and time and stored for future reference. Site administrators may
choose to write scripts to copy/archive the generated accounting report file fr om its original location.
13.2.3. Accounting Proced ures
The amount of work needed to support accounting varies according to the style of accounting used,
whether or not Account Validation is being used, and whether the site requires additional information
beyond that maintained by HPSS:
●For UNIX-style accounting, with or without Account Validation, no additional work is needed to
manage accounting.
●For site style accounting:
●The site must define and maintain a mapping of user IDs to account Ids. For each user,
the mapping must define the user's default account ID and any other accounts for which
the user is authorized.
●If Account Validation is enabled:
●The user ID to account ID mapping is maintained in the Account
Validation table. For each user, this table can store the default account
ID of the user and any other accounts for which he is authorized. The
site must maintain this table. HPSS provides the table and a tool for
maintaining it, the Account Validation Metadata editor (hpss_avaledit) .
See the hpss_avaledit man page for more details.
●If the site requires additional information beyond that supplied by the
Account Validation table, it must create and maintain a site defined
Account Map. See section 13.2.3.1:Site Defined Accounting
Configuration Files and Procedureson page 336.
●For Account Validation to work, a Gatekeeper must be configured. Also,
the Account Validation flag must be enabled on the Accounting Policy
window.
●If Account Validation is disabled:
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 335