TSM Accounting
with the administrative switch “SET ACCOUNTING ON” TSM starts accounting on every client session, unfortunately the information on what ist accounted is not documentend in each TSM / ISP version
It could be found e.g. https://www.ibm.com/support/knowledgecenter/SSATMW_6.4.0/com.ibm.itsm.srv.doc/t_account_records_tsm_monitoring.html:
Tivoli® Storage Manager accounting records show the server resources that are used during a session. This information lets you track resources that are used by a client node session.
Task | Required Privilege Class |
---|---|
Set accounting records on or off | System |
At installation, accounting defaults to OFF. You can turn accounting on by using the SET ACCOUNTING
command. When accounting is set to ON, the server creates a session resource usage accounting record whenever a client node session ends.
- AIX operating systems, HP-UX operating systems, Linux operating systems, Oracle Solaris operating systems
Accounting records are stored in the dsmaccnt.log file.
TheDSMSERV_ACCOUNTING_DIR
environment variable specifies the directory where the accounting file is opened. If this variable is not set when the server is started, thedsmaccnt.log
file is placed in the current directory when the server starts.
For example, to set the environment variable to place the accounting records in the /home/engineering directory, enter this command:
export DSMSERV_ACCOUNTING_DIR=/home/engineering
- Windows operating systems
Accounting records are stored in a file named dsmaccnt.log, which is located in the server directory.
The accounting file contains text records that can be viewed directly or can be read into a spreadsheet program. The file remains opened while the server is running and accounting is set to ON. The file continues to grow until you delete it or prune old records from it. To close the file for pruning, either temporarily set accounting off or stop the server.
There are 31 fields, which are delimited by commas (,). Each record ends with a new-line character. Each record contains the following information:
Field | Contents |
---|---|
1 | Product version V(5,6,7,8) |
2 | Product sublevel incl. RMF |
3 | Product name, ‘ADSM' |
4 | Date of accounting (mm/dd/yyyy) |
5 | Time of accounting (hh:mm:ss) |
6 | Node name of Tivoli Storage Manager client |
7 | Client owner name (UNIX only) |
8 | Client Platform |
9 | Authentication method used |
10 | Communication method used for the session |
11 | Normal server termination indicator (Normal=X'01' / 1 , Abnormal=X'00' / 0 ) |
12 | Number of archive store transactions requested during the session |
13 | Amount of archived files, in kilobytes, sent by the client to the server |
14 | Number of archive retrieve transactions requested during the session |
15 | Amount of space, in kilobytes, retrieved by archived objects |
16 | Number of backup store transactions requested during the session |
17 | Amount of backup files, in kilobytes, sent by the client to the server |
18 | Number of backup retrieve transactions requested during the session |
19 | Amount of space, in kilobytes, retrieved by backed up objects |
20 | Amount of data, in kilobytes, communicated between the client node and the server during the session |
21 | Duration of the session, in seconds |
22 | Amount of idle wait time during the session, in seconds |
23 | Amount of communications wait time during the session, in seconds |
24 | Amount of media wait time during the session, in seconds |
25 | Client session type: |
A value of 1 or 4 indicates a general client session. | |
A value of 5 indicates a client session that is running a schedule. | |
Values other than 1, 4, or 5 are reserved for the Tivoli Storage Manager server's internal use, and you can ignore them. | |
26 | Number of space-managed store transactions requested during the session |
27 | Amount of space-managed data, in kilobytes, sent by the client to the server |
28 | Number of space-managed retrieve transactions requested during the session |
29 | Amount of space, in kilobytes, retrieved by space-managed objects |
30 | Product release |
31 | Product level |