IBM RELEASE 7.3 - Manual (Page 336)

●
The site will need to create a local site Account Map to maintain a list of
the account IDs for which each user is authorized. This is a locally
designed and written table, not supported by HPSS. See section
13.2.3.1: Site Defined Accounting Configuration Files and Procedures
on page 336 for suggestions for designing and maintaining an Account
Map.
●
Administrators will need to manage user default accounts by updating
the user's LDAP registry information (i.e. the “AA=<default-acct-idx>”
string in the user's hpssGECOS field).
13.2.3.1. Site Defined Accounting Configuration Files and Procedures
This section describes situations in which a site would need additional tables and/or procedures beyond
those provided by HPSS. It offers suggestions on ways to implement these tables and procedures.
13.2.3.1.1. Site Defined Account Maps
If a site does not use Account Validation or if the site requires additional information beyond that
maintained in the Account Validation table, it will need to create a local site defined Account Map. For
example, some sites may need to keep track of a department or company name. The Account Map is
designed, created, and maintained by the site, not by HPSS.
The HPSS Account Index of each user should 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
... ...
Note that 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 table. If no additional mappings are
needed, there is no need for the site to create a separate site defined Account Map.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 336