Filter
Top Products
Appendix D Accounting Examples
HPSS Installation Guide September 2002 493
Release 4.5, Revision 2
Sites 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.
Where should the accounting data be stored? The HPSS accounting file and a copy of the current
Account Map should be named with the date and time and stored for future reference. Individual
sites should write scripts to copy/archive the generated accounting report file from its original
location.
D.4 Site Accounting Table
What should be in the Account Map corresponding to the HPSS Account Index number? The HPSS
Account Index will correspond to an Account Map entry that has the site information. The
following are examples of possible Account Maps:
Site-style Account Map:
Acct User UID Charge Update_flag
12 dlk 3152 5A12x401 0
27 dlk 3152 5A12x501 0
341 dlk 3152 5A12x601 0
469 dpc 1478 7A14x401 0
470 dpc 1478 7A14x501 0
471 dmb 5674 5A12x401 0
7111 dmb 5674 7A14x501 0
... ... ... ... ...
UNIX-style Account Map
UID Charge
1478 7A14x401
3152 5A12x401
5674 5A12x401
... ...
If Site-style accounting is in use and Account Validation has been enabled, the user-to-account
index mappings are already maintained in the Account Validation metadata file. If additional
mappings are needed they will need to be kept in the Account Map file.
D.5 Account Apportionment Table
In UNIX-style accounting, the UID (as Account Index) maps only to a specific user. The mapping
of a UID to various percentages of different project charge codes can be done by the site accounting
department in an Account Apportionment Table as shown in the following example:
UID % of (Project(s))
1478 75(DND) 25(CBC)