13.2.3.1.2.  Site Defined Accou nt Apportionment Table
In UNIX-style accounting, the UID (as Account Index) maps only to a specific user.   Some sites may 
wish to apportion different percentages of the charges for a single UID among different project  charge 
codes, but without using site style accounting.  HPSS does not provide a means to do this, but a sit e could 
implement its own table and utilities to do so.  Here is an example of an Account Apportion ment Table 
which a site might implement to do this:
UID % of (Project(s))
1478 75(DND) 25(CBC)
3152 45(DDI) 25(DND) 30(CBC)
5674 100(DDI)
... .................
The site would need to write utilities to tie the Apportionment tabl e to the HPSS accounting report.
13.2.3.1.3.  Maintaining Site  Defined Accounting FilesSites which require a site defined Account Map, Apportionment Table, or other  accounting files must 
develop tools to maintain and modify the files according to local accounting policies. Tool s will be 
necessary to change, add, or delete an HPSS Account Index and its associated information. Site  
administrators must implement their own policies on what to do when an account is deleted,  a user moves 
to another project, or a user leaves the system.
Other needed mappings, if any, must be maintained by the site in the Account Map file. When Account 
Validation is disabled, the site will need to maintain the user-to-account inde x mappings in the Account 
Map file as well.
UNIX-style accounting changes of this nature are handled through the normal utilities that set  up and 
modify users and UIDs. A basic set of site-developed utilities are described in more detail below.
•Add a user and account. New entries can be made and the next available HPSS Account Index 
number will be assigned from the free-list. The free-list will most likely consist of the last  
assigned number plus one, but could include reclaimed index numbers if a site chooses to re-use 
Account Index numbers that were previously assigned and no longer referenced. It is not likely 
that a site will need to reclaim Account Index numbers, but it is an option.
•Delete a user. When a user is deleted from the Account Map, the HPSS files must be reas signed 
to another HPSS Account Index. This should be done from the HPSS client interface side. The  
update_flag should be set to true to indicate that this account index  number can be reclaimed. 
The reclaiming tool should check for files using the account number before reclaiming it. When  
the Account Index is reclaimed, it can be put on the free-list to be re-used. It is important to keep 
a copy of the Account Map that corresponds to the HPSS accounting snapshot of storage space  in 
use for that time period so that the proper site information can be matched.
•Delete account. When an account is deleted, it is handled in the same manner as when a user  is 
deleted.
•Modify account. The entries in the Account Map can be modified to correlat e the Account Index 
to different information, but care should be taken to keep a copy of the corresponding tables  for 
past HPSS accounting runs.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 337