IBM Tivoli Usage and Accounting Manager Data...

IBM Tivoli Usage and Accounting Manager Data Collectorsfor UNIX and Linux

User’s Guide

Version 6.1

SC32-1556-00

Note • Before using this information and the product it supports, read the information in Appendix E, Notices.

First Edition (September 2006)

© Copyright IBM Corp. 2006. All rights reserved.

US Government Users Restricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Table of Contents

Preface

Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

What This Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Terminology Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

1 • Installing ITUAM Data Collectors for UNIX and Linux and Getting Started

What Are ITUAM Data Collectors for UNIX and Linux? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Installing ITUAM Data Collectors for UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

About Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Running the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Installing ITUAM Data Collectors for UNIX and Linux Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13

Prerequisites for the Target Computer When Installing Remotely . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Installing Remotely—Windows to UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Installing Remotely—UNIX/Linux to UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

ITUAM Data Collectors for UNIX and Linux Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29

Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

UNIX and Linux Data Collection: Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-31

Set the Environment Variables for Data Collection and Consolidation . . . . . . . . . . . . . . . . . . . . . 1-31

Schedule the Data Collection and Consolidation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39

Start UNIX/Linux Process Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40

UNIX/Linux Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide iii ■

■ Table of Contents

Oracle Data Collection—Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43

Linking the ITUAM Oracle Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43

Configuring the ITUAM Oracle Accounting Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44

Starting, Stopping, and Checking the Status of the ITUAM Oracle Accounting Daemon . . . . . . 1-45

Oracle Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49

DB2 Data Collection—Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50

Linking the ITUAM DB2 Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50

Configuring the ITUAM DB2 Accounting Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51

Starting, Stopping, and Checking the Status of the ITUAM DB2 Accounting Daemon . . . . . . . . 1-52

DB2 Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56

Database Accounting Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57

About the Apache and FTPD Data Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57

Apache Metrics Collected and ITUAM Rate Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

FTPD Metrics Collected and ITUAM Rate Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

2 • Using AIX Advanced Accounting

Setting Up Advanced Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

Creating Advanced Accounting Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Configuring AIX Advanced Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Setting Up Advanced Accounting Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Scheduling Advanced Accounting Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Advanced Accounting Metrics Collected and ITUAM Rate Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

Process Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

System Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

File System Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Network Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Disk Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Server VIO Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Client VIO Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

ARM Transaction Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

■ iv IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Table of Contents ■

3 • Data Collection and Consolidation

Setting the Environment Variables for Data Collection and Consolidation . . . . . . . . . . . . . . . . . . . 3-2

Collecting Data: Setting Up the Data Collection Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Check pacct File Script (check_pacct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Nightly Accounting Script (ituam_uc_nightly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Turn Accounting Script (turnacct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Run Account Script (runacct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Sampler Script (sampler) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Database Storage Scripts (get_odb_storage and get_db2_storage) . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Redo Nightly Script (redo_nightly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Consolidating Data: Setting Up the Data Consolidation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Nightly Consolidation Script (CS_nightly_consolidation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

CSR File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10

Identifiers and Rate Codes by CSR File Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13

Processing Identifiers and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Software Package (Process), Unix Interactive, Background, and Storage Rate Codes and Identifiers (CS_sum_<date>.csv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Oracle Rate Codes and Identifiers (CS_sum_ora_<date>.csv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Oracle Table Storage Rate Codes and Identifiers (CS_sum__ora_stor_<date>.csv) . . . . . . . . . . 3-17

DB2 Rate Codes and Identifiers (CS_sum__db2_<date>.csv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

DB2 Table Storage Rate Codes and Identifiers (CS_sum__db2_stor_<date>.csv) . . . . . . . . . . . . . 3-19

UNIX File System Rate Codes and Identifiers (CS_sum_fs_<date>.csv) . . . . . . . . . . . . . . . . . . . . . 3-20

Transferring CSR Files to the ITUAM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

Transferring Log Files to the ITUAM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

4 • Data Processing

About ITUAM Processing Engine Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Modifying Data Processing Files and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

ITUAM Data Collectors for UNIX and Linux Data Processing Architecture . . . . . . . . . . . . . . . . . . . . 4-3

collectors Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

CollectorLogs Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

processes Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

LogFiles Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Processing Data: Setting Up the Data Processing Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13

Nightly Script (nightly.sh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Nightly Job Script (nightly.pl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Processing Script (procCIMS.pl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide v ■


5 • Statistics

UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

block_weeks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

cio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

connect_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

dio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

image_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

image_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

scpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

tcpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

ucpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

win_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6

Oracle logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle session CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle connect time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle UGA memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle PGA memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle recursive CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle user commits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle physical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle physical writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle DB block gets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle disk sorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle messages sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle messages received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8

CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

I/O Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Table Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Unit of Work Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

SQL Statement Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Locks and Deadlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Sort Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

■ vi IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Table of Contents ■

A • Directories, Files, and Scripts

$ITUAM_HOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

bin directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

collectors Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

config Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

jlib Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

lib/CIMS_Lib Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

LogFiles Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

sample_processes and processes Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

scripts Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

$ITUAM_UC_HOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-9

accounting Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

bin Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

CS_input_source Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

data Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

etc Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-14

help Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-15

history Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

log Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

scripts Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

B • Utilities

Using the Command Line Interface (CLI) to Access Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Using the HELP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Authorize Utility (A_authorize) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Convert Utility (A_convert) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Database Utilities (A_db*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

ITUAM Oracle Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

ITUAM DB2 Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

ITUAM Database Accounting Utilities for Oracle and DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Format Utility (A_format) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6

Merge Utility (A_merge) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

Merge Utility MERGE Command and Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

Sampler Utility (A_sampler) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

Select Utility (A_select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

Select Utility Commands and Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

Setup Utility (A_setup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10

File System Resource Utility (CS_fs_resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide vii ■


C • CSR File Format

D • ITUAM Messages

About ITUAM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Example Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Returned Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

RTL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5

CIMSG RTL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

Database RTL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13

Sampler Utility Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16

Convert Utility Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17

ITUAM Oracle Accounting Daemon Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19

ITUAM DB2 Accounting Daemon Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20

E • Notices

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

Glossary

Index

■ viii IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Preface

This guide provides a comprehensive set of procedures and references for installing, configuring, and managing IBM® Tivoli® Data Collectors for UNIX® and Linux™.

For the purposes of world-wide marketing, IBM Tivoli Usage and Accounting Manager is sometimes referred to as IBM Usage and Accounting Manager or ITUAM. Users of this product may see these names in presentations and product collateral. For the purposes of this guide, the product is referred to as ITUAM unless referring to another document or entity that contains the full name.

Who Should Read This Guide 0

Because of its technical content, this guide is primarily intended for users that have experience working in a UNIX/Linux environment. This guide also assumes that users have experience with DB2® and/or Oracle where these database applications are discussed.

ITUAM Data Collectors are components of ITUAM. This guide assumes that the ITUAM system is installed and configured as described in the IBM Tivoli Usage and Accounting Manager Administrator’s Guide and that users are familiar with concepts associated with ITUAM, including the layout and use of CSR files.

What This Guide Contains 0

The following table describes the chapters in this guide.

Ch.No. Chapter Name Content Description

1 Installing ITUAM Data Collectors for UNIX and Linux and Getting Started

This chapter provides the installation, configuration, and getting started procedures for ITUAM Data Collectors for UNIX and Linux.

2 Using AIX Advanced Accounting

This chapter describes how to collect AIX Advanced Accounting data.

3 Data Collection and Consolidation

This chapter describes the environment variables and scripts used for data collection and consolidation.

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide ix ■

■ Preface

Related Publications

Related Publications 0

As you use this guide, you might find it helpful to have these additional guides available for reference:

■ IBM Tivoli Usage and Accounting Manager Administrator’s Guide

■ IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide

4 Data Processing This chapter describes the directories, files, and scripts used to run ITUAM Processing Engine on a UNIX or Linux system.

5 Statistics This chapter describes the UNIX, Oracle, and DB2® statistics processed by ITUAM Data Collectors for UNIX and Linux.

A Directories, Files, and Scripts

This appendix describes the ITUAM Data Collectors for UNIX and Linux directory structure and provides a description of the files and scripts that are in the ITUAM directories.

B Utilities This appendix describes the ITUAM Data Collectors for UNIX and Linux utilities

C CSR File Format This appendix provides the CSR file format.

D ITUAM Messages This appendix describes the messaged produced by ITUAM Data Collectors for UNIX and Linux.

E Notices This appendix provides licensing, copyright, and trademark information.

Ch.No. Chapter Name Content Description

■ x IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Preface ■

Contacting Customer Support

Contacting Customer Support 0

Before contacting IBM Tivoli Software Support with a problem, refer to the IBM Tivoli Software Support site by clicking the Tivoli link at the following Web site:

http://www.ibm.com/software/support/

If you need additional help, contact software support by using the methods described in the IBM Software Support Guide at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The IBM Software Support Guide provides the following information:

■ Registration and eligibility requirements for receiving support.

■ Telephone numbers, depending on the country in which you are located.

A list of information you should gather before contacting technical support.

Conventions Used in This Guide 0

Some or all of the following conventions are used in this guide:

Symbol or Type Style Represents Example

Alternate color

hyperlinked cross-references to other sections or chapters in this guide; if you are viewing this guide online, you can click the cross-reference to jump directly to its location

...see Chapter 3.

Italic words that are emphasized ...the entry after the current entry...

a new term ...called a source object.

the titles of other manuals IBM Tivoli Usage and Accounting Manager Administrator’s Guide

variables in file names or system names

Jobdefinitionname.pl

yyyymmdd.txt

Bold names of interface items such as tabs, boxes, buttons, lists, and check boxes.

Select the CPU Value check box

Type the database name in the Database Name box.

Click Edit.

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide xi ■

http://www.ibm.com/software/support/

http://techsupport.services.ibm.com/guides/handbook.html

■ Preface

Conventions Used in This Guide

Terminology Used in This Guide 0

In this guide, $ITUAM_HOME refers to the top-level directory of the ITUAM installation. This is where ITUAM Processing Engine is installed. For example, assume that the top-level directory is /usr/ituam. In this example, /usr/ituam, is designated by $ITUAM_HOME (for example, /usr/ituam/jlib/lib is shown as $ITUAM_HOME/jlib/lib).

$ITUAM_UC_HOME refers to the home directory for the ITUAM Data Collectors for UNIX and Linux. For example, /usr/ituam/collectors/Unix/data is shown as $ITUAM_UC_HOME/data.

Monospace directories, file names, command names, computer code, computer screen text, system responses, command line commands, what the user types

processes directory

CS_send script

type $ITUAM_HOME/bin/

< > the name of a key on the keyboard

Press <Enter>

navigating a menu or a folder Customer Area Product Downloads

Symbol or Type Style Represents Example

■ xii IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

1Installing ITUAM Data Collectors for UNIX and Linux and Getting Started

This chapter provides the installation, configuration, and getting started steps for ITUAM Data Collectors for UNIX and Linux.

What Are ITUAM Data Collectors for UNIX and Linux? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Installing ITUAM Data Collectors for UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

About Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Running the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Installing ITUAM Data Collectors for UNIX and Linux Remotely . . . . . . . . . . . . . . . . . . . . . . . . . .1-13

Prerequisites for the Target Computer When Installing Remotely . . . . . . . . . . . . . . . . . . . . . . . 1-13

Installing Remotely—Windows to UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Installing Remotely—UNIX/Linux to UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

ITUAM Data Collectors for UNIX and Linux Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29

Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

UNIX and Linux Data Collection: Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-31

Set the Environment Variables for Data Collection and Consolidation . . . . . . . . . . . . . . . . . . . 1-31

Schedule the Data Collection and Consolidation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39

Start UNIX/Linux Process Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40

UNIX/Linux Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide 1-1 ■

■ Installing ITUAM Data Collectors for UNIX and Linux and Getting Started

Oracle Data Collection—Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43

Linking the ITUAM Oracle Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43

Configuring the ITUAM Oracle Accounting Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44

Starting, Stopping, and Checking the Status of the ITUAM Oracle Accounting Daemon . . . . 1-45

Oracle Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49

DB2 Data Collection—Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50

Linking the ITUAM DB2 Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50

Configuring the ITUAM DB2 Accounting Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51

Starting, Stopping, and Checking the Status of the ITUAM DB2 Accounting Daemon . . . . . . 1-52

DB2 Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56

Database Accounting Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57

About the Apache and FTPD Data Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57

Apache Metrics Collected and ITUAM Rate Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

FTPD Metrics Collected and ITUAM Rate Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

■ 1-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Installing ITUAM Data Collectors for UNIX and Linux and Getting Started ■

What Are ITUAM Data Collectors for UNIX and Linux?

What Are ITUAM Data Collectors for UNIX and Linux? 1

ITUAM Data Collectors for UNIX and Linux collect resource usage information from UNIX and Linux environments and produce a common output file that integrates with ITUAM. This output file is called a CSR file.

ITUAM Data Collectors for UNIX and Linux are non-intrusive and do not affect system performance or operation.

ITUAM Data Collectors for UNIX and Linux use a Command Line Interface (CLI) to administer and run the collectors as shown in this guide.

The collectors gather accounting information from standard UNIX and Linux accounting subsystems such as UNIX/Linux process accounting, session accounting, and print accounting (where available). ITUAM Data Collectors for UNIX and Linux also generate accounting files for Oracle Usage Accounting, DB2 Usage Accounting, and ITUAM UNIX Project Accounting.

ITUAM Data Collectors for UNIX and Linux collect data from the following systems, databases, and applications:

■ Unix and Linux operating system and file system.

■ Oracle and DB2

■ AIX Advanced Accounting

■ Apache

■ FTPD

Note • This guide describes all ITUAM Data Collectors that run on the UNIX or Linux operating system. The collectors that are available to you depend on the collector packages that have been purchased for your organization.

Features and Benefits 1

ITUAM Data Collectors for UNIX and Linux provide the following features and benefits:

■ Provides utilities and scripts that enable you to customize data collection for your organization.

■ Collects and consolidates data from multiple UNIX/Linux platforms.

■ Collects usage by users, groups of users, projects, departments, organizations, and cost centers and gathers otherwise undetectable resource usage from databases such as Oracle and DB2.

■ Tracks resource usage for stand-alone nodes and nodes configured in a heterogeneous, open system architecture.

■ Consolidates data from multiple nodes simultaneously to reduce processing time for large client-server configurations.

■ Schedules a regular collection of file system utilization information. New file systems are automatically included in data collection.

■ Automates collection of Oracle and DB2 storage resource information.



System Specifications

System Specifications 1

■ For the ITUAM Processing Engine and ITUAM Data Collectors for UNIX and Linux:

• Any of the following UNIX or Linux operating systems:

• AIX® 5.1, 5.1.0.c, 5.2, or 5.3

• Solaris 7, 8, 9, or 10

• HP-UX 11, 11i, or 11.23

• HP-UX 11.23 Itanium

• Red Hat Enterprise Linux (RHEL) 3.0 or 4.0 for IA32

• RHEL 3.0 or 4.0 for AMD64 and EM64T

• RHEL 3.0 or 4.0 for System z (31 and 64 bit)

• SuSE Linux Enterprise Server (SLES) 8, 9, or 10 for IA32

• SLES 9 or 10 for AMD64 and EM64T

• SLES 8 or 9 for System z (31 bit)

• SLES 9 for System z (64 bit)

• SLES 9 or 10 for PowerPC®

• Linux Itanium for RHEL 3.0 and 4.0 and SLES 9.

• 5 GB minimum available hard drive space for the following:

• ITUAM Processing Engine installation (requires 100 MB minimum)

• The data associated with ITUAM Data Collectors (log files, collector directories, process definition directories, etc.).

Log files, collector-related files and directories, and process definitions are described in Chapter 4, Data Processing.

• 1 GB minimum of memory.

■ For all other components of the ITUAM system, including the database, refer to the IBM Tivoli Usage and Accounting Manager Administrator’s Guide.



Installing ITUAM Data Collectors for UNIX and Linux

Installing ITUAM Data Collectors for UNIX and Linux 1

Complete the installation using the steps in this section and then continue to the following sections as applicable:

■ ITUAM Data Collectors for UNIX and Linux Architecture on page 1-28 to enable the collection of UNIX and Linux operating system and file system data.

■ Oracle Data Collection—Post-Installation Setup on page 1-43 or DB2 Data Collection—Post-Installation Setup on page 1-50 to enable the collection of Oracle or DB2 data.

Preparing for Installation 1

Before you install ITUAM Data Collectors for UNIX and Linux, complete the following tasks. Depending on your processor's speed, current system load, etc., installation time is approximately 10 to 15 minutes.

Perform Backups If you are installing ITUAM Data Collectors for UNIX and Linux:

Although ITUAM does not interfere with or modify the UNIX or Linux system, it is a good precautionary measure to ensure that the system has been recently backed up before you install or upgrade any system level product.

If you are upgrading ITUAM Data Collectors for UNIX and Linux:

Before you perform an upgrade, back up the ITUAM Data Collectors for UNIX and Linux directories so you can recover to the original state, if necessary. In addition, back up any ITUAM scripts that you have modified.

Verify That You Have Enough Disk Space for Installation

Make sure you have enough disk space for installing ITUAM Data Collectors for UNIX and Linux. The application and files require 20 to 25 MB. The additional space requirement is dependent on the size of the accounting files generated on the computer.

Create an ITUAM User Account

ITUAM Data Collectors for UNIX and Linux operate in conjunction with the UNIX or Linux operating system. You have the option of having root maintain ITUAM or setting up an ITUAM user account. The advantage of a user account is that the ITUAM administrator does not need root privileges on a daily basis for maintenance.

You can set up a user account before you install ITUAM or during the installation (see Running the Installation Files on page 1-11).




Create an ITUAM Group (Optional)

Creating an ITUAM GID is recommended. You can set up a group account before installing ITUAM or during the installation (see Running the Installation Files on page 1-11).

Install the UNIX/Linux Process Accounting Subsystem (If Required)

The UNIX/Linux process accounting subsystem is usually present on a platform. However, on some platforms, it must be installed separately. In this case, install the process accounting subsystem on your system.

Examples of process accounting subsystems are:

■ For SuSE 9, rpm acct–6.3.5–675

■ For RedHat 4, rpm pasacct–6.3.2–37




About Installation 1

The ITUAM installation for ITUAM Data Collectors for UNIX and Linux is composed of a base ITUAM package and five collector packages for each of the UNIX/Linux operating systems that are supported by ITUAM (see System Specifications on page 1-4). For example, the base installation package for the AIX operating system is setup-ituam-<version-release>-aix.bin and the collector packages are setup-ituam-pkg#-<version-release>-aix.bin, where # specifies the package number.

Table 1-1 describes each of the packages and their contents. The base ITUAM installation consists of the ITUAM Base Package and Collector Base Package. The availability of the other collector packages depends on the packages that have been purchased for your organization.

The Collector Base Package (collector package 1) and Collector Package for Databases (collector package 3) must be installed on each computer from which you want to collect operating system, file system, or database data. To install these collectors from a central location to multiple computers, refer to Installing ITUAM Data Collectors for UNIX and Linux Remotely on page 1-13.

Important! • All data collector packages other than the Collector Base Package and the Collector Package for Databases, must be installed on the same server as the ITUAM Base Package. The Collector Base Package and the Collector Package for Databases do not require the ITUAM Base Package on the same server.

ITUAM Package Contents Installation File Systems

ITUAM Base Package

This package contains ITUAM Processing Engine and its administrative tools and scripts. This package also creates the directory structure required by ITUAM Data Collectors for UNIX and Linux.

setup-ituam-6-1-aix.bin AIX® 5.1, 5.1.0.c, 5.2, or 5.3

setup-ituam-6-1-solaris.bin Solaris 7, 8, 9, or 10

setup-ituam-6-1-hpux11x.bin HP-UX, 11, 11i, or 11.23

setup-ituam-6-1-hpuxIA.bin HP-UX 11.23 Itanium

Table 1-1 • ITUAM Installation Programs by Package




ITUAM Base Package (continued)

setup-ituam-6-1-linuxz.bin RHEL 3.0 or 4.0 for System z (31 and 64 bit)

SLES 8 or 9 for System z (31 bit)

SLES 9 for System z (64 bit)

setup-ituam-6-1-linuxi.bin RHEL 3.0 or 4.0 for IA32

RHEL 3.0 or 4.0 for AMD64 and EM64T

SLES 8, 9, or 10 for IA32

SLES 9 or 10 for AMD64 and EM64T

Linux Itanium for RHEL 3.0 and 4.0 and SLES 9.

setup-ituam-6-1-linuxp.bin SLES 9 or 10 for PowerPC

Collector Base Package

This package contains the data collectors for UNIX and Linux operating system and file system data.

setup-ituam-pkg1-6-1-aix.bin

setup-ituam-pkg1-6-1-solaris.bin

setup-ituam-pkg1-6-1-hpux11x.bin

setup-ituam-pkg1-6-1-hpuxIA.bin

setup-ituam-pkg1-6-1-linuxz.bin

setup-ituam-pkg1-6-1-linuxi.bin

setup-ituam-pkg1-6-1-linuxp.bin

See ITUAM Base Package on page 1-7 for supported system by package.


Table 1-1 • ITUAM Installation Programs by Package (Continued)




Collector Package for Databases

This package contains data collectors for DB2 and Oracle databases. It also includes the data collectors the Collector Base Package (package 1). Therefore, if you install this package, do not install the base collector package.









Collector Package for Internet Infrastructure

This package contains data collectors for Internet applications.










Collector Package for Network and Printing

This package contains data collectors for network and printing.









Collector Package for Enterprise

This package contains all of the data collectors contained in the preceding packages. If you install this package, the individual collector packages are not required.










Table 1-1 • ITUAM Installation Programs by Package (Continued)




Example Installations

The use of the ITUAM packages is shown in the following examples.

You have purchased just the base ITUAM components:

Install the following packages:

■ ITUAM Base Package

■ Collector Base Package

Note • The Collector Base Package is usually also installed on other servers from which you want to collect data.

You have purchased the base ITUAM components and all ITUAM Data Collectors for UNIX and Linux:



■ Collector Package for Enterprise (Collector package 7)

You have purchased the base ITUAM components, the database collectors, and the Internet collectors:



■ Collector Package for Databases (Collector package 3)

Note • The Collector Package for Databases is usually also installed on other servers from which you want to collect data.

■ Collector Package for Internet Infrastructure (Collector package 4)




Running the Installation Files 1

The following are the steps for installing ITUAM Data Collectors for UNIX and Linux.

To install the ITUAM Base Package:

1 Log on to the UNIX system using the Super-User (root) account. ITUAM installation requires root privilege to create directories and execute privileged commands.

2 Change to the directory in which the ITUAM installation files are located.

3 Type the following command to launch the installation:

./setup-ituam-<version-release>-<OS>.bin

Example:

./setup-ituam-6-1-aix.bin

4 Complete the steps in the InstallShield Wizard as follows:

a At the welcome screen, click Next.

b Review the terms of the license agreement, click I accept the terms of the license agreement, and then click Next. You must accept the terms to continue the installation.

c Click Next to install ITUAM to the default directory (opt/IBM/tivoli/ituam). If you do not want to use the default directory, enter the directory in the Directory Name box (type the directory or click Browse to find the directory).

d Type a user name and group for the ITUAM administrator or accept the defaults (ituam for both). If the user name and group are not pre-existing, select the Add UserName and Group check box.

e Select the features that you want to install, and then click Next. All features are selected by default. Do not clear the check box for a feature unless you do not want to install that feature.

f Review the summary information and click Install to continue or click Back to change the installation options.

g Click Finish when the installation is complete.




To install the ITUAM collectors packages:

1 In the directory in which the ITUAM installation files are located, type the command to launch the installation.

If you are installing the ITUAM Enterprise Collector package (which contains all collectors), type:

./setup-ituam-pkg7-<version-release>-<OS>.bin

Example:

./setup-ituam-pkg7-6-1-aix.bin

If your are installing individual collector packages, type the applicable command for each package as follows:

• To install the Operating System and File System Collector package, type ./setup-ituam-pkg1-<version-release>-<OS>.bin

Example:


• To install the Database Collector package, type ./setup-ituam-pkg3-<version-release>-<OS>.bin

Example:


• To install the Internet Infrastructure Collector package, type ./setup-ituam-pkg4-<version-release>-<OS>.bin

Example:


• To install the Network and Printing Collector package, type ./setup-ituam-pkg6-<version-release>-<OS>.bin

Example:


Complete the steps in the InstallShield Wizard. These are the same steps shown in Step 4 on page 1-11 with the exception that you are not asked for the installation directory or the ITUAM administrator user name and group if this information has already been defined.



Installing ITUAM Data Collectors for UNIX and Linux Remotely

Installing ITUAM Data Collectors for UNIX and Linux Remotely 1

Note • Installation of ITUAM Data Collectors for UNIX and Linux must be executed by the root account to create directories and execute privileged commands.

The Collector Base Package and Collector Package for Databases must be installed on each computer from which you want to collect operating, file system, or database data. To quickly deploy these packages to multiple computers, you can install the packages remotely. Remote installation performs the following tasks:

1 Unpacks the TAR file that contains the data collectors on the target platform.

2 Schedules jobs to gather, format, and consolidate accounting data in the root account crontab file.

3 On RedHat and Linux platforms, renames the file /etc/logrotate.d/psacct to /etc/logrotate.d/psacct.rpmsave.

On SuSE Linux platforms, renames the file /etc/logrotate.d/acct to /etc/logrotate.d/acct.rpmsave.

Important! • The Database Collector package requires that the Collector Package Base is present on the target computer. You must install the base collector package before you install the database package.

All remote installations require an installation file and a deployment manifest file. These files are described in detail in the following sections. For a list of the installation and deployment manifest files and the UNIX and Linux systems that they support, see UnixLinux Directory on page A-3.

The following sections describe how to remotely install ITUAM Data Collectors. The installation steps differ depending on whether you are deploying the collectors from a Windows® system or from a UNIX or Linux system.

Prerequisites for the Target Computer When Installing Remotely 1

Make sure that the target computer meets the following prerequisites:

■ The computer has .5 to 2 GB of available hard drive space depending on the process activity.

■ SSH (Secure Shell) is running on the target computer and the computer is known to the ITUAM server.




Installing Remotely—Windows to UNIX/Linux 1

ITUAM on the Windows system uses the ITUAM Job Runner application and a job file to install ITUAM Data Collectors for UNIX and Linux on multiple computers. ITUAM Job Runner is a Windows console application that executes jobs that are defined in a job file. The use of ITUAM Job Runner and job files is described in detail in the IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide.

ITUAM includes sample job files for deploying ITUAM Data Collectors for UNIX and Linux from a Windows system to a UNIX or Linux system. You can modify these files for your organization and use them to deploy ITUAM Data Collectors to multiple computers.

The following sections describe how to modify and run the sample deployment job file.

Modify the Sample Deployment Job File

Note • The following information is intended for users who have a basic knowledge of XML file structure.

The following sample job files for deploying ITUAM Data Collectors for UNIX and Linux remotely are provided in the ...IBM\ITUAM\JobFiles folder on the ITUAM server. You can modify these files for your organization.

Important! • If you modify the deployment job file or any of the files or scripts provided with ITUAM Data Collectors for UNIX and Linux, it is very important that you rename the file. Otherwise, the file will be overwritten when you upgrade to a new version of ITUAM Data Collectors for UNIX and Linux.

■ SampleDeployLinuxCollector.xml Use this file to deploy the Collector Base Package.

■ SampleDeployLinuxDatabaseCollector.xml Use this file to deploy the Collector Package for Databases.

Important: The Collector Package for Databases requires that the Collector Base Package is present on the target computer. You must install the base collector package before you install the database collector package.




An example of a SampleDeployLinuxCollector.xml job file that has been modified for use is shown in Sample Deployment Job File on page 1-16 (the SampleDeploy LinuxDatabaseCollector.xml file is similar).

The parameters that are specific to the sample deployment job files are indicated in bold and are described in Table 1-2 on page 1-18. For a description of all other attributes and elements in the job file, refer to IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide.

Note that the sample deployment files contain only one deployment step. A separate deployment step is required for each computer on which you want to install data collectors. To deploy to multiple computers, simply copy the deployment step (that is, copy everything from the opening to the closing Step tag) for each computer and modify the values in the step as needed.


Sample Deployment Job File<?xml version="1.0" encoding="utf-8"?><Jobs xmlns="http://www.cimslab.com/CIMSJobs.xsd">

<Job id="DeployUnixLinuxCollector" description="Deploy the ITUAM UNIX/Linux Collector Agent"active="true"dataSourceId=""joblogShowStepParameters="true"joblogShowStepOutput="true"processPriorityClass="Low"joblogWriteToTextFile="true"joblogWriteToXMLFile="true"smtpSendJobLog="false"smtpServer="mail.ITUAMCustomerCompany.com"smtpFrom="[email protected]"smtpTo="[email protected]" stopOnProcessFailure="false">

<Process id="DeployUnixLinuxCollector"

description="Deployment of ITUAM UNIX/Linux Data Collector"joblogShowStepOutput="true"joblogShowStepParameters="true"

active="true">

<Steps stopOnStepFailure="true"><Step id="ITUAM UNIX/Linux Data Collector Deployment"

description="ITUAM UNIX/Linux Data Collector Deployment" type="ConvertToCSR" programName="rpd\rpd.jar" programType="java"active="true">

<Parameters><Parameter JavaCommandLine = ’-cp "%CIMSInstallLocation%\scripts\rpd\rpd.jar;%CIMSInstallLocation%\scripts\rpd\TivoliCommonCLI.jar;%CIMSInstallLocation%\scripts\rpd\jlanclient.jar;%CIMSInstallLocation%\scripts\rpd\jlog.jar;%CIMSInstallLocation%\scripts\rpd\jlogEnglish.jar;%CIMSInstallLocation%\scripts\rpd\remoteaccess.jar;%CIMSInstallLocation%\scripts\rpd\ssh.jar"com.ibm.tivoli.ituam.rpd.RemoteProductDeployment’/>

<Parameter Action = "-install"/>

<Parameter Host = "-host 9.44.163.21"/>

<Parameter UserId = "-userid root"/>

<Parameter Password = "-password abcdefgh"/>

<Parameter Manifest = "-manifest DeploymentManifest_aix5.xml"/>

























<Parameter RPDParameters = ’-parameters path="/opt/IBM/tivoli/ituam/collectors/Unix";user="ituam";’/>

<Parameter Verbose = "-verbose"/>

<Parameter SourcePath = ’-sourcepath"%CIMSInstallLocation%\Collectors\UnixLinux"’/>

</Parameters></Step>

</Steps></Process>

</Job></Jobs>

The Manifest parameter points to the deployment manifest file. This file specifies the installation file and default configuration options for the collectors. The DeploymentManifest_aix5.xml file is shown on page 1-23.



Deployment Job File ParametersTable 1-2 describes the parameters that are specific to the sample deployment job files. Note that some optional parameters have default values. If you do not include these parameters or provide blank values, the default values are used.

ParameterRequired or Optional Description

JavaCommandLine Required Do not change this parameter.

Action Required Do not change this parameter.

Host Required The IP address or DNS name of the computer on which you want to install ITUAM Data Collectors for UNIX and Linux.

UserIdPassword

Required The user ID must be the Super-User (root) account and the password must be the root password on the target UNIX/Linux server.

KeyFilename Required You must use the SSH (Secure Shell) protocol to deploy the installation files (see the Protocol parameter on page 1-19). This parameter defines the SSH server’s host key.

Manifest Required The deployment manifest file. Include the path only if the deployment manifest is in a location other than ...IBM\ITUAM\ Collectors\UnixLinux on the ITUAM server.

The deployment manifest is an XML file that defines the installation file for the collectors (see page 1-23 for an example of a deployment manifest). There are separate deployment manifest and installation files for the base collectors and the database collectors. The deployment manifest and installation files are further broken down by operating system. For example, there is a deployment manifest and installation file for the Collector Base Package on AIX and a deployment manifest and installation file for the Collector Package for Databases on AIX. For a list of the installation and deployment manifest files, see UnixLinux Directory on page A-3.

Table 1-2 • Deployment Job File Parameters




Manifest (continued) Required The parameters in the deployment manifest also define the some of the default configuration options for the collectors (see Set the Environment Variables for Data Collection and Consolidation on page 1-31).

You can change the default parameter values in the deployment manifest or you can change the default values using the job file parameter RPDParameters. The parameters in the deployment manifest are the same as those defined in RPDParameters (see page 1-20).

If you do not want to use one or more of the default parameter values defined in the deployment manifest, it is recommended that you change the corresponding attribute value in RPDParameters rather than changing default values in the deployment manifest.

For example, if you do not want to use the default value for the parameter Parameter name="user" that is defined in the deployment manifest, use the attribute user= in the job file parameter RPDParameters to define the user.

Protocol Optional The protocol used to deploy the installation files.

To deploy to a Unix or Linux system, use ssh (Secure Shell). Make sure that SSH is enabled on the target computer.


Table 1-2 • Deployment Job File Parameters (Continued)




RPDParameters Optional These are the same parameters that are in the deployment manifest (see page 1-23 for an example of a deployment manifest).

These parameters define some of the default configuration options for the collectors (see Set the Environment Variables for Data Collection and Consolidation on page 1-31). The parameter values that you define here override the values in the deployment manifest.

The parameters are:

■ path—The full path in which you want to install ITUAM Data Collectors for UNIX and Linux.

■ user—The account that owns the files on the target computer. For more information, see Create an ITUAM User Account on page 1-5.






RPDParameters (continued)

Optional ■ cs_method— This is the protocol that is used to transfer CSR files from the collector system to the ITUAM server.

Valid values are: FTP (file transfer protocol), SCP (secure copy, valid only if ITUAM server is on Windows), or SFTP (secure FTP, valid only if ITUAM server is on UNIX or Linux).

The default value HOLD specifies that the files remain in the ...ituam/collectors/Unix directory.

■ server—This is ITUAM server name.

■ cs_user—This is the ITUAM server account required to transfer CSR files from the collector system to the ITUAM server.

■ cs_password—This is the password for the account defined by the cs_user parameter.

■ cs_proc_path—This is the path to the processes directory on the ITUAM server.

If procesess is on a UNIX or Linux, system, provide the full path to the directory.

If processes is on a Windows system, provide the virtual directory that points the processes folder. For more information, see processes Directory on page 4-9.






Verbose Optional The value -verbose specifies that the addition information is included in the job log file or debugging and troubleshooting purposes. A job log file provides processing results for each step defined in a job file. For more information about job log files, refer to the IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide.

If you do not include this parameter or leave the parameter value blank, this additional information is not provided in the log file.

SourcePath Required The full path to the ...ituam\collectors\ UnixLinux folder on the ITUAM server. This folder contains the installation files for the Collector Base Package and the Collector Package for Databases.

The install file names are defined in the deployment manifest (see the description of the Manifest parameter on page 1-18).




Sample Deployment ManifestThe following is the deployment manifest for AIX, DeploymentManifest_aix5.xml.

<?xml version="1.0"?><ProductDeployment name = "UNIX/Linux"

description = "ITUAM UNIX/LINUX Data Collector"><Deployments>

<Deployment name="install" targetOS="AIX" deploymentType="install"><Files>

<File name="ituam_uc_aix5.tar"/><File name="v601_unpack_tar"/>

</Files>

<Parameters><Parameter name="path" required="no" defaultValue="/opt/IBM/tivoli/ituam/collectors/Unix"/>

<Parameter name="user" required="no" defaultValue="ituam"/><Parameter name="cs_method"required="no" defaultValue="HOLD"/><Parameter name="server" required="no" defaultValue=""/><Parameter name="cs_user" required="no" defaultValue=""/><Parameter name="cs_pwd" required="no" defaultValue=""/><Parameter name="cs_proc_path" required="no" defaultValue=""/>

</Parameters>

<Actions><Action name="step1" displayMessage="Creating Install folder’%path%’..." actionType="FolderCreate"><Parameters>

<Parameter name="FolderPath" value="%path%"/></Parameters>

</Action>

<Action name="step2" displayMessage="Transferring tar file’%SourcePath%ituam_uc_aix5.tar’..." actionType="FilePut"><Parameters>

<Parameter name="localfilename"value="%SourcePath%ituam_uc_aix5.tar"/>

<Parameter name="remotepath" value="%path%/ituam_uc_aix5.tar"/>

</Parameters></Action>

The installation files are defined here. For a list of the installation files, see UnixLinux Directory on page A-3.

The default configuration options for the collectors are defined here. You can define these options here or in the RPDParameters in the deployment job file (see page 1-20). Options defined in RPDParameters override the options defined here.



Run the Deployment Job File

The following examples show how to run the deployment job file from the Windows command prompt. The job file name is passed as a parameter to ITUAM Job Runner (CIMSJobRunner.exe).

C:\Program Files\IBM\ITUAM\Process Engine>CIMSJobRunner.exe DeployUnixLinuxCollector

Or

C:\Program Files\IBM\ITUAM\Process Engine>CIMSJobRunner.exe DeployUnixLinuxDatabaseCollector

The components that comprise the ITUAM Data Collectors for UNIX and Linux system are installed and configured on each of the computers specified in the deployment job file.

For more information about running job files using ITUAM Job Runner, refer to the IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide.

Installing Remotely—UNIX/Linux to UNIX/Linux 1

ITUAM on a UNIX or Linux system uses the $ITUAM_HOME/collectors/UnixLinux/DeployUnixLinux.pl script to install ITUAM Data Collectors for UNIX and Linux on multiple computers. The following sections describe how to modify and run the DeployUnixLinux.pl script.

Note • Rename the modified script so that it is not overwritten when you upgrade to a new version of ITUAM Data Collectors for UNIX and Linux

Modify the Deployment Script

The DeployUnixLinux.pl script contains required and optional parameters that you must modify for your organization. Table 1-3 describes these parameters.


target_platform Required The IP address or DNS name of the computer on which you want to install ITUAM Data Collectors for UNIX and Linux.

remote_userremote_password

The user ID must be the Super-User (root) account and the password must be the root password on the target UNIX/Linux computer.

Table 1-3 • Deployment Script Parameters




manifest_xml_file Required The full path to the deployment manifest file.

The deployment manifest is an XML file that defines the installation file for the collectors (see page 1-23 for an example of a deployment manifest). There are separate deployment manifest and installation files for the base collectors and the database collectors. The deployment manifest and installation files are further broken down by operating system. For example, there is a deployment manifest and installation file for the Collector Base Package on AIX and a deployment manifest and installation file for the Collector Package for Databases on AIX. For a list of the installation and deployment manifest files, see UnixLinux Directory on page A-3.

The parameters in the deployment manifest also define the some of the default configuration options for the collectors (see Set the Environment Variables for Data Collection and Consolidation on page 1-31).

The parameters are:

■ path—The full path in which you want to install ITUAM Data Collectors for UNIX and Linux.

■ user—The account that owns the files on the target computer. For more information, see Create an ITUAM User Account on page 1-5.


Table 1-3 • Deployment Script Parameters (Continued)




Run the Deployment Script

Run the DeployUnixLinux.pl script.

manifest_xml_file (continued)

■ cs_method— This is the protocol that is used to transfer CSR files from the collector system to the ITUAM server.

Valid values are: FTP (file transfer protocol), SCP (secure copy, valid only if ITUAM server is on Windows), or SFTP (secure FTP, valid only if ITUAM server is on UNIX or Linux).

The default value HOLD specifies that the files remain in the ...ituam/collectors/Unix directory.

■ server—This is ITUAM server name.

■ cs_user—This is the ITUAM server account required to transfer CSR files from the collector system to the ITUAM server.

■ cs_password—This is the password for the account defined by the cs_user parameter.

■ cs_proc_path—This is the path to the processes directory on the ITUAM server.

If procesess is on a UNIX or Linux, system, provide the full path to the directory.


install_path Required The full installation path for ITUAM Data Collectors for UNIX and Linux.


Table 1-3 • Deployment Script Parameters (Continued)



ITUAM Data Collectors for UNIX and Linux Architecture

ITUAM Data Collectors for UNIX and Linux Architecture1

The following is an overview of the key components that comprise the ITUAM Data Collectors for UNIX and Linux architecture.

Utilities 1

ITUAM Data Collectors for UNIX and Linux include utilities that are used to set up, administer, and run the collectors. These utilities are in the $ITUAM_UC_HOME/bin directory. The files that the utilities access are in the $ITUAM_UC_HOME/data directory.

Table 1-4 on page 1-28 lists each of the utilities used to set up ITUAM Data Collectors for UNIX and Linux and the files accessed by these utilities. For more information about these and all collector utilities and files, see Appendix A, Directories, Files, and Scripts and Appendix B, Utilities.

Utility Files Accessed

G_license ■ A_setup.sys. Parameter file — contains license information.

A_setup ■ A_holiday.sys. Holiday file.

■ A_imgmap.sys. Image/Package Mapping file.

■ A_dbinst.sys. Database Instance file.

■ A_queuemap.sys. Queue Mapping file.

■ A_setup.sys. Parameter file.

■ A_shift.sys. Shift file.

■ A_shift.tmp. Backup Shift file.

■ A_term_par.sys. Terminal Parameter file.

A_authorize ■ A_uaf.sys. Authorization file.

A_login, A_login_xm, and A_switch

■ A_activity.sys. Activity file.

■ A_uaf.sys. Authorization file.

■ A_validate.sys. Validation file.

Table 1-4 • ITUAM Data Collectors for UNIX and Linux Administration Utilities




Scripts 1

ITUAM Data Collectors for UNIX and Linux use scripts to perform many operations including performing some set up steps and managing data collection and consolidation on a scheduled basis. Scripts are also available to assist in recovery if an error occurs. These scripts use the parameter files described Parameter Files on page 1-30 to accomplish these tasks.

Scripts are in two locations: the $ITUAM_UC_HOME/etc directory and the $ITUAM_UC_HOME/scripts directory. The $ITUAM_UC_HOME/etc directory contains the scripts used for data collection. These scripts are described in the section Collecting Data: Setting Up the Data Collection Scripts beginning on page 3-2.

The $ITUAM_UC_HOME/scripts directory contains subdirectories that group scripts by function. Table 1-5 lists each of the subdirectories in the scripts directory and provides an overview of the scripts contained in that subdirectory. These scripts are described in detail in this guide as they apply to a particular feature or function.

Subdirectory Description

aacct Contains scripts used to collect AIX Advanced Accounting data. For more information about these scripts, see Setting Up Advanced Accounting Data Collection on page 2-3.

admin Contains scripts that assist you in administering ITUAM Data Collectors for UNIX and Linux.

db2 and oracle Contains DB2 and Oracle setup scripts that your DBA should use to set up the roles and tables needed for ITUAM DB2 and Oracle utilities.

This subdirectoy also contains scripts that manage the ITUAM Oracle or DB2 Accounting daemons. These scripts start, stop, and check the status of all or individual accounting daemons. For more information about these database accounting scripts, see Using Database Accounting Scripts to Start, Stop, and Check ITUAM Oracle Daemons on page 1-46 or Using Database Accounting Scripts to Start, Stop, and Check ITUAM DB2 Daemons on page 1-53.

enterprise Contains the operational scripts used to consolidate and send data to the ITUAM. These scripts are described in the section Consolidating Data: Setting Up the Data Consolidation Scripts beginning on page 3-9.

Table 1-5 • ITUAM Data Collectors for UNIX and Linux Script Overview




Parameter Files 1

For first time installations, the ITUAM parameter files are delivered so that a minimal ITUAM Data Collectors for UNIX and Linux system operates without any tailoring.

Parameter File

The Parameter file ($ITUAM_UC_HOME/data/A_setup.sys) contains system-wide flags and parameters that define your configuration.

ITUAM Data Collectors for UNIX and Linux sets the initial values in the A_setup.sys file during installation. The file is created and maintained by the A_setup utility.

Configuration Parameter File

The Configuration Parameter file ($ITUAM_UC_HOME/data/A_config.par) provides a common configuration file that is used by the ITUAM Data Collectors for UNIX and Linux data collection and consolidation scripts to define your ITUAM environment. You can modify the environment variables in this as needed for your organization using a text editor such as vi.

The environment variables in the A_config.par file are described in Set the Environment Variables for Data Collection and Consolidation on page 1-31.

Node Parameter File

The Node Parameter file ($ITUAM_UC_HOME/data/A_node.par) contains one entry for the node on which the file is installed. For example, if the file is installed on the server zeus, then the node entry in the file is zeus.



UNIX and Linux Data Collection: Post-Installation Setup

UNIX and Linux Data Collection: Post-Installation Setup1

This section provides the information that you need to get started using ITUAM Data Collectors for UNIX and Linux. To help you to get started quickly, this section does not contain the detailed information found in other chapters in this guide. Where applicable, references to more detailed information are provided.

Set the Environment Variables for Data Collection and Consolidation 1

The Configuration Parameter file ($ITUAM_UC_HOME/data/A_config.par) provides a common configuration file that is used by the ITUAM Data Collectors for UNIX and Linux scripts to define your ITUAM environment. The file is commented and organized by the stages in the data collection process.

The initial variable values in the A_config.par file are set during installation. However, you can modify these values as needed for your organization using a text editor (for example, vi).

Important! • When you upgrade to a new release of ITUAM Data Collectors for UNIX and Linux, some environment variables in the A_config.par file are overwritten to the default values. A backup file configuration file named A_config.bak contains the variable settings prior to the upgrade. After you complete the upgrade, you should compare the values in the A_config.par file to the values in the A_config.bak file.

Table 1-6 describes the key variables in the A_config.par file. Descriptions of each variable are also provided in the file.

Variable Description

ITUAM Directory Variables

ITUAM_ACCDAT through ITUAM_UPATH

These variables define the directory paths used by ITUAM Data Collectors for UNIX and Linux. Key variables are:

■ ITUAM_ACCDAT—This is the path for the accounting directory. For example, if ITUAM_HOME is /usr/ituam, this variable would be defined as follows:

ITUAM_ACCDAT=/usr/ituam/collectors/Unix/accounting

This variable is defined during installation. For more information about the accounting directory, see page A-9.

Table 1-6 • Environment Variables in the A_config.par File




ITUAM_ACCDAT through ITUAM_UPATH(continued)

■ ITUAM_USER—This is the ITUAM Data Collectors for UNIX and Linux user account on the collector platform.

■ ITUAM_UPATH—This is the root account’s directory path. On most systems, this is / or /root.

Data Collection File Cleanup Variables

CLEANUP_HISTORY and CLEANUP_AGE The CLEANUP_HISTORY variable specifies if files in the $ITUAM_UC_HOME/history directory are purged. If set to Y, files older than the CLEANUP_AGE value are purged from the directory each night as part of the execution of the ituam_uc_nightly script.

The default CLEANUP_HISTORY value is Y. The default CLEANUP_AGE value is +4. Files older than four days are purged.

CLEANUP_ACCT and CLEANUP_ACCT_AGE

The CLEANUP_ACCT variable specifies if in the $ITUAM_UC_HOME/accounting directory are purged. If set to Y, files older than the CLEANUP_ACCT_AGE value are purged from the directory each night as part of the execution of the ituam_uc_nightly script.

The default CLEANUP_ACCT value is Y. The default CLEANUP_ACCT_AGE value is +45. Files older than 45 days are purged.

CLEANUP_CSIS and CLEANUP_CSIS_AGE

The CLEANUP_CSIS variable specifies if in the $ITUAM_UC_HOME/CS_input_source directory are purged. If set to Y, files older than the CLEANUP_ACCT_AGE value are purged from the directory each night as part of the execution of the ituam_uc_nightly script.

The default CLEANUP_ACCT value is Y. The default CLEANUP_ACCT_AGE value is +45. Files older than 45 days are purged.

CLEANUP_CLIENT_ACC This variable specifies whether nightly accounting and storage files are to be purged from the history directory after they have been transferred to the $ITUAM_UC_HOME/accounting/<nodename> directory.

The default is Y.


Table 1-6 • Environment Variables in the A_config.par File (Continued)




CLEANUP_CLIENT_ACC This variable specifies whether nightly accounting and storage files are to be purged from the history directory after they have been transferred to the $ITUAM_UC_HOME/accounting/<nodename> directory.

The default is Y.

CLEANUP_STATFILES This variable specifies whether temporary accounting files created by the A_format utility are to be purged from the data directory.

The default is Y.

Data Collection File Transfer Variables

TRANSFER_VIA, ITUAM_SERVER, and ITUAM_DEST

These variables are used to transfer the nightly accounting and storage files from the history directory to the $ITUAM_UC_HOME/accounting/<nodename> directory. For more information about these variables, see page 3-8.

ITUAM_KEY This variable is required only if TRANSFER_VIA is set to FTP. In this situation, set this variable to the password for the account designated by ITUAM_USER.






Data Collection for AIX Advanced Accounting Variables:

AACCT_TRANS_IDS This variable designates the AIX Advanced Accounting record types that are included in the usage reports created by the ituam_format_aacct script.

Valid values are:

■ 1 Process record

■ 2 Aggregated process record

■ 4 System processor and memory interval record

■ 6 File system activity interval record

■ 7 Network interface I/O interval record

■ 8 Disk I/O Interval record

■ 10 Sever VIO interval record

■ 11 Client VIO interval record

■ 16 Aggregated ARM transaction record

The default is "1,4,6,7,8".

AACCT_ONLY Set this variable to Y if you want to collect AIX Advanced Accounting data and do not want to collect traditional UNIX/Linux process accounting data.

The default is N.






Data Collection for Oracle Variables:

A_ORACLE_ACCT Set this variable to Y if you want to collect Oracle data. This variable instructs the ituam_uc_nightly script to include the ITUAM Oracle Accounting file ($ITUAM_UC_HOME/data/A_dbacct.sys) in the collection and formatting of the nightly accounting file. The default is N.

Note that to include Oracle data in the CSR file, you must set the GEN_ORACLE variable to Y (see page 1-38).

USE_SESSION_OSUSER Set this variable to Y to instruct the ITUAM Oracle Accounting daemon to retrieve the OS user name from the V$SESSION table. By default, the daemon will retrieve the name from the V$PROCESS table. In some environments, a more unique value can be found the V$SESSION table.

The default is Y.

ORACLE_STR_SAMPLE Set this variable to Y if you want to include Oracle tablespace and datafile storage data in the collection and formatting of the nightly accounting file. The default is N.

Note that to include Oracle storage data in the CSR file, you must also set the GEN_ORACLE_ STORAGE variable to Y (see page 1-38).

ORA_SEND_STARTMSG If you are using the ituam_check_odb script with the start argument (see page 1-48), setting this variable to Y instructs the script to send notification via e-mail to the list of users specified by the ORA_STARTMSG_RCPT variable.

The default is N.

ORA_STARTMSG_RCPT Set this variable to the list of e-mail users to be notified if the ITUAM Oracle Accounting daemon is re-started by the ituam_check_odb script. Use a comma to separate multiple e-mail addresses.

This variable is valid only if the ORA_SEND_ STARTMSG variable is set to Y.

The default is N.

TNS_ADMIN Set this variable to the location of the tnsnames.ora file if other than the $ORACLE_HOME/network/admin directory.






Data Collection for DB2 Variables

A_DB2_ACCT Set this variable to Y if you want to collect DB2 data. This variable instructs the ituam_uc_nightly script to include the ITUAM DB2 Accounting file ($ITUAM_UC_HOME/data/A_db2acct.sys) in the collection and formatting of the nightly accounting file. The default is N.

Note that to include DB2 data in the CSR file, you must also set the GEN_DB2 variable to Y (see page 1-38).

DB2_STR_SAMPLE Set this variable to Y if you want to include DB2 database partition storage information in the collection and formatting of the nightly accounting file. The default is N.

Note that to include DB2 storage data in the CSR file, you must also set the GEN_DB2_STORAGE variable to Y (see page 1-38).

DB2_SEND_STARTMSG If you are using the ituaml_check_db2 script with the start argument (see page 1-55), setting this variable to Y instructs the script to send notification via e-mail to the list of users specified by the DB2_STARTMSG_RCPT variable.

The default is N.

DB2_STARTMSG_RCPT Set this variable to the list of e-mail users to be notified if the ITUAM DB2 Accounting daemon is re-started by the ituam_check_db2 script. Use a comma to separate multiple e-mail addresses.

This variable is valid only if the DB2_SEND_ STARTMSG variable is set to Y.






Data Collection for Storage Variables

ITUAM_SAMPLE Set this variable to Y if you want to collect file system storage data. This data is provided in the Storage file ($ITUAM_UC_HOME/data/A_storage.sys). For more information about collecting storage data, see page 3-7.

The default is N.

ITUAM_DYNAMIC_STORAGE_PAR If this variable and ITUAM_SAMPLE are both set to Y, the Storage Parameter file ($ITUAM_UC_HOMEdata/A_storage.par) is rebuilt each night before the sampler script is run.

The default is N.

Data Consolidation Variables for proc_multi Script

ITUAM_NODE_FILE This variable defines the Node Parameter file. The default file is $ITUAM_UC_HOME/data/A_node.par.

For more information about the Node Parameter file, see page 1-30

SELECT_QUALS This variable is used to pass command line qualifiers to the Select utility ($ITUAM_UC_HOME/bin/A_select) when the utility is called from the proc_multi script.

For example, if PROPRIETARY_SOFTWARE is enabled in the $ITUAM_UC_HOME/data/A_setup.sys file and you want to automatically add process names to the Image Mapping file ($ITUAM_UC_HOME/data/A_image.sys), define this variable as follows:

SELECT_QUALS=/ADD_IMAGE (this is the default)

If PROJECT_ACCOUNTING is enabled in the A_setup.sys file, define this variable as:

SELECT_QUALS=/UNKNOWN=LAST

If both the PROPRIETARY_SOFTWARE and PROJECT_ACCOUNTING flags are enabled, define this variable as:

SELECT_QUALS=/ADD_IMAGE/UNKNOWN=LAST

RANGE_BACK and RANGE_AHEAD These variables define a window for consolidating data.

The default for both variables is 3.






Data Consolidation Variables for Generating CSR Files

GEN_UNIXPROC If set to Y, this variable instructs the CS_nightly_ consolidation script to create a CSR file containing UNIX process usage data.

The default is Y.

GEN_PROCONLY If set to Y, interactive, background, and storage type records are not included in the CSR file. The usage in these types of records is already included in the process and file system type records.

The default is Y.

GEN_UNIXFS If set to Y, this variable instructs the CS_nightly_ consolidation script to create a CSR file containing UNIX file system usage data.

The default is Y.

GEN_ORACLE If set to Y, this variable instructs the CS_nightly_ consolidation script to create a CSR file containing UNIX Oracle usage data.

The default is N.

GEN_ORACLE_STORAGE If set to Y, this variable instructs the CS_nightly_ consolidation script to create a CSR file containing UNIX Oracle tablespace and data file utilization data.

The default is N.

GEN_DB2 If set to Y, this variable instructs the CS_nightly_ consolidation script to create a CSR file containing UNIX DB2 usage data.

The default is N.

GEN_DB2_STORAGE If set to Y, this variable instructs the CS_nightly_ consolidation script to create a CSR file containing UNIX DB2 partition storage utilization data.

The default is N.






Schedule the Data Collection and Consolidation Scripts 1

Notes • If you installed the Collector Base Package or Collector Package for Databases remotely, the scripts in this section are scheduled automatically.

If you installed these packages using the setup files described in Installing ITUAM Data Collectors for UNIX and Linux on page 1-5, you need to schedule these scripts.

The scripts described in this section are described in detail in Chapter 3, Data Collection and Consolidation.

The scripts described in this section must be scheduled to run on a regular basis. You can use any batch scheduler to run these scripts; however, the scripts must be run under the root user account. During the ITUAM Data Collectors for UNIX and Linux installation, the file $ITUAM_UC_HOME/etc/cron.entry was created. This file contains sample crontab entries for these scripts.

■ $ITUAM_UC_HOME/etc/ituam_uc_nightly. This nightly collection script should be scheduled to run nightly around 1 a.m. If you use the example entry in the cron.entry file, output from this script is redirected to the log file $ITUAM_UC_HOME/log/ituam_uc_nightly.log.

This script collects the raw UNIX and ITUAM accounting files and formats and sorts the files into one nightly accounting file. The script also executes the Sampler utility ($ITUAM_UC_HOME/bin/A_sampler) to get a snapshot of file system use. This snapshot is written to a nightly storage file.

The nightly accounting and storage files are transferred to the $ITUAM_UC_HOME/accounting/<nodename> directory.

Variables for Sending CSR Files to ITUAM

CS_PLATFORM through CS_PROC_PATH

These variables are used to transfer the CSR files to ITUAM. For more information about these variables, see page 3-22.

Other variables

TURN_WTMP If this variable is set to Y, a new UNIX or Linux wtmp (or wtmpx) file is created each night when the ituam_uc_nightly script executes.

The default is N.






■ $ITUAM_UC_HOME/etc/check_pacct. This script should be called three times each hour. It is used to manage the size of the UNIX/Linux process accounting (pacct) file. This file usually resides on the root file system in /var/adm. The location varies for different UNIX/Linux types.

This script checks the size of the current pacct file. If the file has reached a threshold size (2000 blocks by default), the file is moved to $ITUAM_UC_HOME/history/pacct_hold and a new file is started.

■ $ITUAM_UC_HOME/scripts/enterprise/CS_nightly_consolidation. This script should be scheduled to run nightly after the ituam_uc_nightly script has run. The CS_nightly_consolidation script consolidates the nightly accounting and storage files for the previous day. Refer to the comments in the beginning of the script to determine the best script configuration for your site.

The CS_nightly_consolidation script produces CSR files, which are used as input to ITUAM.

■ $ITUAM_UC_HOME/scripts/enterprise/CS_send. This script places the CSR files produced by the CS_nightly_consolidation script in a designated process definition directory on the ITUAM system. The CS_send script should be run after the CS_nightly_consolidation script has run. Refer to the comments in the beginning of the script to determine the best script configuration for your site.

Start UNIX/Linux Process Accounting 1

Notes • If you installed the Collector Base Package or Collector Package for Databases remotely, the steps in this section are performed automatically.

If you installed these packages using the setup files described in Installing ITUAM Data Collectors for UNIX and Linux on page 1-5, you need perform these steps.

The scripts described in this section are described in detail in Chapter 3, Data Collection and Consolidation.

After installing ITUAM Data Collectors for UNIX and Linux and scheduling the data collection and consolidation scripts, start UNIX/Linux process accounting as follows:

1 ITUAM Data Collectors for UNIX and Linux manages the UNIX/Linux process accounting file, var/account/pacct. Therefore, you should verify that no other processes are currently manipulating this file.

2 On most UNIX platforms, check in the adm account crontab file to verify that the accounting scripts runacct, monacct, and ckpacct are not currently scheduled. If these scripts are scheduled, comment them out of the adm account crontab file.




3 On Linux platforms, the cron.daily script calls the logrotate script, which compresses the current process accounting file, pacct, and starts a new file. You must disable this function as follows:

• On RedHat Linux platforms, copy the script /etc/logrotate.d/psacct to/etc/logrotate.d/psacct.rpmsave.

• On SuSE Linux platforms, copy the script /etc/logrotate.d/acct to/etc/logrotate.d/acct.rpmsave.

4 Start UNIX/Linux process accounting using the $ITUAM_UC_HOME/etc/turnacct script. As the root user, execute the following command:

> $ITUAM_UC_HOME/etc/turnacct on

If you need to suspend UNIX/Linux process accounting, call this script with the argument off.




UNIX/Linux Metrics Collected 1

Note • The ITUAM rate codes for UNIX/Linux operating system and file system metrics are in Identifiers and Rate Codes by CSR File Type on page 3-13.

The following metrics are collected from the wtmp file:

■ User name of the user that logged in.

■ Controlling terminal (when there is one).

■ Name of the remote system (when there is one).

■ Time logged in or logged out.

Note • Most UNIX systems do not store the user name in the logout record, only in the login record.

The followin metrics collected from the pacct file:

■ Command name.

■ UID and GID of the user that executed the command.

■ Controlling terminal (when there is one).

■ Amount of user and system CPU time that it took to execute that command.

■ Time the command started executing.

■ Time that it took to execute the command (the elapsed time).

■ Average memory usage.

■ Number of blocks read or written.

■ Where provided by the system, the number of characters transferred.



Oracle Data Collection—Post-Installation Setup

Oracle Data Collection—Post-Installation Setup 1

After you have installed the Oracle data collector, you must complete the steps in this section to enable data collection.

Linking the ITUAM Oracle Accounting Utilities 1

ITUAM Oracle Accounting Utilities are delivered in UNIX archive object library form as opposed to an executable. Therefore, you must link the library with the appropriate database libraries to create an executable for each ORACLE_HOME on your system. The archive object library files are in the $ITUAM_UC_HOME/collectors/Unix/bin directory and end in .a (e.g., libdbao.a).

To link the ITUAM Oracle Accounting Utilities:

Use the script $ITUAM_UC_HOME/scripts/oracle/link_A_dbao. You must know the ORACLE_SID for each instance in addition to having defined the ORACLE_HOME environment variable.

The link_A_dbao script creates the following ITUAM Oracle Accounting utilities in ITUAM_UC_HOME/bin:

■ A_dbao.<Oracle version> (ITUAM Oracle Accounting daemon)

■ A_dbso.<Oracle version> (ITUAM Oracle Storage utility)




Configuring the ITUAM Oracle Accounting Daemon 1

The ITUAM Oracle Accounting daemon collects resource usage data from the V$ system tables within an Oracle instance. To activate ITUAM Oracle Accounting, you must set A_ORACLE_ACCT=Y in the Configuration Parameter file (ITUAM_UC_HOME/data/A_config.par). This variable directs the Nightly Accounting script ($ITUAM_UC_HOME/etc/ituam_uc_nightly) to include the ITUAM Oracle Accounting file ($ITUAM_UC_HOME/data/A_dbacct.sys) in the script’s nightly process.

If you want to collect Oracle tablespace and datafile storage data as well, set ORACLE_STR_SAMPLE=Y in the A_config.par file.

Configuration for the Oracle Instance

You must perform the following steps for each Oracle instance. You might need to have the Oracle Database Administrator (DBA) perform some of these steps.

1 In the init.ora file (this file should be named init<ORACLE_SID>.ora), set the value TIMED_STATISTICS = TRUE. This setting initiates the tracking of CPU statistics within the Oracle instance.

This ensures that TIMED_STATISTICS is set to TRUE the next time the instance is shut down and restarted.

You can use the following SQL command to dynamically set TIMED_STATISTICS:

SQL> ALTER SYSTEM SET TIMED_STATISTICS = TRUE;

2 To enable the ITUAM Oracle Accounting daemon to connect to Oracle, create an Oracle user account and password. An Oracle user account ituam is typically created.

3 Once the Oracle user account has been defined, the DBA can run the SQL script $ITUAM_UC_HOME/scripts/oracle/ituam_view.sql. This SQL script creates a role called ituam_view and assigns the role to the Oracle user account. This role grants select on the V$ tables required for ITUAM Oracle Accounting.

If you are not using ituam as the Oracle user account, edit the ituam_view.sql script and replace the name ituam with the appropriate Oracle account name.

4 Create an ITUAM DB instance record for each Oracle instance. To create this record, you must know the Oracle user account and password that will be used by the ITUAM Oracle Accounting daemon to connect to the instance. In addition, you must know the frequency of sampling that you want for the daemon.

If same Oracle account name will be used for all instances, individual database instance records are not required. You can modify the default ORACLE DB Instance record as follows:

SETUP> mod/dbinst/user=ituam/pass=xxx/freq=30 A_ORA_DEFAULT




You can also specify a different oracle_user, oracle_password, and oracle_frequency parameter for each Oracle instance. These parameters are provided in the Database Instance file ($ITUAM_UC_HOME/data/A_dbinst.sys). To set these parameters, use the Setup utility ($ITUAM_UC_HOME/bin/A_setup) as shown in the following example. In this example, the Oracle instance is D920.

% $ITUAM_UC_HOME/bin/A_setupA_SETUP> add/dbinst/user=ituam/pass=xxx/freq=60 D920%SETUP-S-ADDED, 1 node record successfully modified

The following command reports on the database instance information:

% $ITUAM_UC_HOME/bin/A_setupA_SETUP> rep/dbinst

This command produces the following database instance report:

DB Type Instance Username Frequency (sec) --------------------------------------------------------------------ORACLE A_ORA_DEFAULT ituam 60 DB2 A_DB2_DEFAULT default 300 INFORMIX _INF_DEFAULT default 300 SYBASE A_SYB_DEFAULT default 300ORACLE D920 ituam 60

Starting, Stopping, and Checking the Status of the ITUAM Oracle Accounting Daemon 1

You must start the ITUAM Oracle Accounting daemon for each Oracle instance for which you want to gather accounting data.

If you created an ITUAM group, any member of the group can start an ITUAM Oracle Accounting daemon. At many sites, the Oracle DBAs are made members of the ITUAM Group because the daemon must be stopped and started whenever the instance is shutdown and rebooted.

The following files owned by the ITUAM user should have group read/write privileges to allow group members to start and stop the daemon:

$ITUAM_UC_HOME/data/A_dbpid.sys$ITUAM_UC_HOME/data/A_dbinst.sys$ITUAM_UC_HOME/data/A_dbacct.sys$ITUAM_UC_HOME/log/A_dbao_<SID>.log

The ITUAM Oracle Accounting file (A_dbacct.sys) and the daemon log file ($ITUAM_UC_HOME/log/A_dbao_<SID>.log) are created the first time the daemon is started. The daemon writes informational and error messages to this log. The log file name contains the Oracle instance name for which you started the daemon. For example, if the $ORAINSTANCE is orainst1, the log file is named A_dbadao_orainst1.log.




Using Database Accounting Scripts to Start, Stop, and Check ITUAM Oracle Daemons

ITUAM Data Collectors for UNIX and Linux provide Oracle Accounting scripts to manage the Oracle Accounting daemons. These scripts start, stop, and check the status of all or individual accounting daemons. The scripts can be configured to notify administrators when daemons are started.

The ITUAM Oracle Accounting scripts are in the $ITUAM_UC_HOME/scripts/oracle directory. These scripts are described in Table 1-7.

Script Description

ituam_start_odb This script starts the ITUAM Oracle Accounting daemons for one or all Oracle instances. This script takes one argument, which is either:

■ The name of an Oracle instance, which specifies that only the daemon for that instance should be started.

■ The keyword ALL, which specifies that the daemon for each Oracle instance listed in the Oracle oratab file should be started.

For example:

$ITUAM_UC_HOME/scripts/oracle/ituam_start_odb ORAINST1

$ITUAM_UC_HOME/scripts/oracle/ituam_start_odb all

This script will first check to see if the instance or instances are up and then will check to see if a daemon is currently running for the instance(s). If not, the script will start the daemon for the instance(s).

You can also start the daemon from the command line. The following example commands start the daemon for instances D815 and D817:

% $ITUAM_UC_HOME/bin/A_dbao.V8.1.5 -SID D815 &% $ITUAM_UC_HOME/bin/A_dbao.V8.1.7 -SID D817 &

Table 1-7 • ITUAM Oracle Accounting Scripts




ituam_stop_odb This script stops the ITUAM Oracle Accounting daemons for one or all Oracle instances. This script takes one argument, which is either:

■ The name of an Oracle instance, which specifies that only the daemon for that instance should be stopped.

■ The keyword ALL, which specifies that the daemon for each Oracle instance listed in the Oracle oratab file should be stopped.

For example:

$ITUAM_UC_HOME/scripts/oracle/ituam_stop_odb ORAINST1

$ITUAM_UC_HOME/scripts/oracle/ituam_stop_odb all

The daemon writes a record to the $ITUAM_UC_HOME/data/A_dbacct.sys file for each session that it is currently tracking. Therefore, you should stop the daemon only if you are shutting down the instance. Otherwise, the currently active sessions could be counted twice when the daemon is restarted.

You can also stop the daemon from the command line using the kill command as follows:

kill -USR ’PID’

Where PID is the process ID of the daemon.

Script Description





ituam_check_odb This script monitors the status of the ITUAM Oracle Accounting daemon. This script takes one argument, which is either:

■ The name of an Oracle instance, which specifies that only the daemon for that instance should be checked.

■ The keyword ALL, which specifies that the daemon for each Oracle instance listed in the Oracle oratab file should be checked.

For example:

$ITUAM_UC_HOME/scripts/oracle/ituam_check_odb ORAINST1

$ITUAM_UC_HOME/scripts/oracle/ituam_check_odb all

An optional second argument, start, can be used with this script. For example:

$ITUAM_UC_HOME/scripts/oracle/ituam_check_odb all start

If this argument is present, the script will first check to see if the instance or instances are up and then will check to see if a daemon is currently running for the instance(s). If not, the script will start the daemon for the instance(s).

The start argument is intended to be used in a crontab entry that periodically checks the status of the daemon and restarts the daemon if it is not running. For a sample crontab entry, see the comments at the beginning of the ituam_check_odb script.

Script Description





Oracle Metrics Collected 1

Note • The ITUAM rate codes for Oracle metrics are in Identifiers and Rate Codes by CSR File Type on page 3-13.

The Oracle metrics collected include the following:

■ UID and user name of the user

■ GID and group of the user

■ Oracle user name used to access the database

■ Oracle instance name

■ Statistics reflecting the resources used



DB2 Data Collection—Post-Installation Setup

DB2 Data Collection—Post-Installation Setup 1

After you have installed the DB2 data collector, you must complete the steps in this section to enable data collection.

Linking the ITUAM DB2 Accounting Utilities 1

ITUAM DB2 Accounting utilities are delivered in UNIX archive object library form as opposed to an executable. Therefore, you must link the library against the appropriate database libraries to create an executable for each version of DB2 on your system. The archive object library files are in the $ITUAM_UC_HOME/collectors/Unix/bin directory and end in .a (e.g., libdbadb2.a).

To link the ITUAM DB2 Accounting Utilities:

Run the script $ITUAM_UC_HOME/scripts/db2/link_A_dbadb2. The link_A_dbadb2 script uses the file $ITUAM_UC_HOME/scripts/db2/A_db2_home. The A_db2_home file defines the standard locations of some DB2 versions. You might need to modify this file to reflect your DB2 installation.

The link_A_dbadb2 script creates the following ITUAM DB2 Accounting utilities in $ITUAM_UC_HOME/bin for the appropriate type of DB2:

■ A_dbadb2_<DB2 version> (ITUAM DB2 Accounting daemon)

■ A_dbsdb2_<DB2 version> (ITUAM DB2 Storage utility)




Configuring the ITUAM DB2 Accounting Daemon 1

The ITUAM DB2 Accounting daemon collects event monitor data from DB2 databases within a DB2 instance. To activate ITUAM DB2 Accounting, you must set A_DB2_ACCT=Y in the Configuration Parameter file ($ITUAM_UC_HOME/data/A_config.par). This variable directs the Nightly Accounting script ($ITUAM_UC_HOME/etc/ituam_uc_nightly) to include the ITUAM DB2 Accounting file ($ITUAM_UC_HOME/data/A_db2acct.sys) in the script’s nightly process.

If you want to collect DB2 database partition storage data as well, set DB2_STR_SAMPLE=Y in the A_config.par file.

Setting the System Monitor Parameters

ITUAM Data Collectors for UNIX and Linux acquires the DB2 statistics through the DB2 Snapshot Monitor. The DB2 Snapshot Monitor configuration must be modified to allow the proper database system monitors to be invoked. The following database system monitor parameters must be turned ON:

Buffer pool (DFT_MON_DUFPOOL)Lock (DFT_MON_LOCK)Sort (DFT_MON_SORT)Unit of work (DFT_MON_UOW)

The GET DATABASE MANAGER CONFIGURATION (or GET DBM CFG) command displays the current state of these parameters. The UPDATE DATABASE MANAGER CONFIGURATION (or UPDATE DBM CFG) command changes the designated parameters to the specified state.

These parameters are OFF by default. The following command turns these parameters ON:

#db2db2=>UPDATE DBM CFG using DFT_MON_BUFPOOL ONDFT_MON_LOCK ON DFT_MON_SORT ON DFT_MON_UOW ONdb2=>QUIT#

Creating an ITUAM DB Instance Record for Each Db2 Instance

You must create an ITUAM DB instance record for each DB2 instance. To create this record, you must know the DB2 user account and password that will be used by the ITUAM DB2 Accounting daemon to connect to the instance. In addition, you must know the frequency of sampling that you want for the daemon.

If same DB2 account name will be used for all instances, individual database instance records are not required. You can modify the default DB2 DB Instance record as follows:

SETUP> mod/dbinst/user=ituam/pass=xyz/freq=30 A_DB2_DEFAULT




You can specify a different db2_user, db2_password, and db2_frequency parameter for each DB2 instance. These parameters are provided in the Database Instance file ($ITUAM_UC_HOME/data/A_dbinst.sys). To set these parameters, use the Setup utility ($ITUAM_UC_HOME/bin/A_setup) as shown in the following example. In this example, the DB2 instance is db2inst1.

% $ITUAM_UC_HOME/bin/A_setupA_SETUP> add/dbinst/user=ituam/pass=xyz/freq=60 db2inst1

The user account used by the daemon must be a member of the DB2 SYSMAINT group. The password is this user's UNIX password.

Starting, Stopping, and Checking the Status of the ITUAM DB2 Accounting Daemon 1

You must start the ITUAM DB2 Accounting daemon for each DB2 instance for which you want to gather accounting data.

If you created an ITUAM group, any member of the group can start an ITUAM DB2 Accounting daemon. At many sites, the DB2 DBAs are made members of the ITUAM Group because the daemon must be stopped and started whenever the instance is shutdown and rebooted.

The following files owned by the ITUAM user should have group read/write privileges to allow group members to start and stop the daemon:

$ITUAM_UC_HOME/data/A_dbpid.sys$ITUAM_UC_HOME/data/A_dbinst.sys$ITUAM_UC_HOME/data/A_db2acct.sys$ITUAM_UC_HOME/log/A_dbadb2_<SID>.log

The ITUAM DB2 Accounting file (A_db2acct.sys) and the daemon log file ($ITUAM_UC_HOME/log/A_dbadb2_<SID>.log) are created the first time the daemon is started. The daemon writes informational and error messages to this log. The log file name contains the DB2 instance name for which you started the daemon. For example, if the $DB2INSTANCE is db2inst1, the log file is named A_dbadb2_db2inst1.log.




Using Database Accounting Scripts to Start, Stop, and Check ITUAM DB2 Daemons

ITUAM Data Collectors for UNIX and Linux provide DB2 Accounting scripts to manage the DB2 Accounting daemons. These scripts start, stop, and check the status of all or individual accounting daemons. The scripts can be configured to notify administrators when daemons are started.

The ITUAM DB2 Accounting Scripts are in the $ITUAM_UC_HOME/scripts/db2 directory. These scripts are described in Table 1-8.

Script Description

ituam_start_db2 This script starts the ITUAM DB2 Accounting daemons for one or all DB2 instances. This script takes one argument, which is either:

■ The name of a DB2 instance, which specifies that only the daemon for that instance should be started.

■ The keyword ALL, which specifies that the daemon for each DB2 instance listed in the $ITUAM_UC_HOME/data/A_db2_ilist file should be started. The A_db2_ilist file is created when the ITUAM DB2 Accounting daemon is linked.

For example:

$ITUAM_UC_HOME/scripts/db2/ituam_start_db2 DB2INST1

$ITUAM_UC_HOME/scripts/db2/ituam_start_db2 all

Note: Make sure that the db2_user, db2_password, and db2_frequency parameters have been entered in the Database Instance file (A_dbinst.sys) before starting the DB2 Accounting daemons (see Creating an ITUAM DB Instance Record for Each Db2 Instance on page 1-51).

This script will first check to see if the instance or instances are up and then will check to see if a daemon is currently running for the instance(s). If not, the script will start the daemon for the instance(s).

You can also start the daemon from the command line. The following example commands start the daemon for instances db2inst1 and db2inst1:

% $ITUAM_UC_HOME/bin/A_dbadb2.V8.1 -SID db2inst1 &% $ITUAM_UC_HOME/bin/A_dbadb2.V8.1 -SID db2inst2 &

Table 1-8 • ITUAM DB2 Accounting Scripts




ituam_stop_db2 This script stops the ITUAM DB2 Accounting daemons for one or all DB2 instances. This script takes one argument, which is either:

■ The name of a DB2 instance, which specifies that only the daemon for that instance should be stopped.

■ The keyword ALL, which specifies that the daemon for each DB2 instance listed in the $ITUAM_UC_HOME/data/A_db2_ilist file should be stopped.

For example:

$ITUAM_UC_HOME/scripts/db2/ituam_stop_db2 DB2INST1

$ITUAM_UC_HOME/scripts/db2/ituam_start_db2 all

The daemon writes a record to the $ITUAM_UC_HOME/data/A_db2acct.sys file for each session that it is currently tracking. Therefore, you should stop the daemon only if you are shutting down the instance. Otherwise, the currently active sessions could be counted twice when the daemon is restarted.

You can also stop the daemon from the command line using the kill command as follows:

kill -USR ’PID’

Where PID is the process ID of the daemon.

Script Description





ituam_check_db2 This script monitors the status of the ITUAM DB2 Accounting daemon. This script takes one argument, which is either:

■ The name of a DB2 instance, which specifies that only the daemon for that instance should be checked.

■ The keyword ALL, which specifies that the daemon for each DB2 instance listed in the $ITUAM_UC_HOME/data/A_db2_ilist file should be checked.

For example:

$ITUAM_UC_HOME/scripts/db2/ituam_check_db2 DB2INST1

$ITUAM_UC_HOME/scripts/db2/ituam_check_db2 all

An optional second argument, start, can be used with this script. For example:

$ITUAM_UC_HOME/scripts/db2/ituam_check_odb db2 start

If this argument is present, the script will first check to see if the instance or instances are up and then will check to see if a daemon is currently running for the instance(s). If not, the script will start the daemon for the instance(s).

The start argument is intended to be used in a crontab entry that periodically checks the status of the daemon and restarts the daemon if it is not running. For a sample crontab entry, see the comments at the beginning of the ituam_check_db2 script.

Script Description





DB2 Metrics Collected 1

Note • The ITUAM rate codes for DB2 metrics are in Identifiers and Rate Codes by CSR File Type on page 3-13.

The DB2 metrics collected include the following:

■ UID and user name of the user

■ GID and group of the user

■ DB2 authorization ID used to access the database

■ DB2 database name

■ DB2 application ID

■ Statistics reflecting the resources used



Database Accounting Best Practices

Database Accounting Best Practices 1

Consider the following when using database accounting:

■ If you have created UNIX user account for administering ITUAM, use this account for running the database accounting daemons.

■ Make sure that the following files are owned by the ITUAM user account with mod 664:

• A_dbacct.sys

• A_db2acct.sys

• A_dbid.sys

• Database accounting log files ()

■ Schedule the ituam_check_odb script with the start argument in the ITUAM user account crontab.

■ For Oracle database accounting, if domain names are required in the Oracle service name of the instance, use the $ITUAM_UC_HOME/scripts/oracle/ituam_ora_db_domain.txt file to define the database domain for the instance.

About the Apache and FTPD Data Collectors 1

The Apache and FTPD data collectors gather data from usage logs. These logs must be placed in the appropriate $ITUAM_HOME/CollectorLogs/<collector>/<feed> directory, where collector is either Apache or FTPD and feed is the source of the log. For example, Apache log files from the server zeus are in the Apache/zeus subdirectory.

If the CollectorLogs directory is on the same computer as the log file, you can use the $ITUAM_UC_HOME/scripts/enterprise/CS_log_send script to transfer the Apache or FTPD logs from their source location to the CollectorLogs directory. For more information about this script, see Transferring Log Files to the ITUAM Server on page 3-25.

If the log file is not on the same computer as the CollectorLogs directory, you need to ensure that the log file is placed in the correct subdirectory in CollectorLogs.



About the Apache and FTPD Data Collectors

Apache Metrics Collected and ITUAM Rate Codes 1

Table 1-9 shows the metrics that are collected from the Apache log files. The table also shows the ITUAM rate code that is assigned to each metric.

FTPD Metrics Collected and ITUAM Rate Codes 1

Table 1-9 shows the metrics that are collected from the FTPD log files. The table also shows the ITUAM rate code that is assigned to each metric.

Metric Rate Code

Apache 200 level hits AP-2




Table 1-9 • Apache Metrics Collected

Metric Rate Code

FTP incoming jobs F-FIJOBS

FTP outgoing jobs F-FOJOBS

FTP MB incoming F-MBIN

FTP MB outgoing F-MBOUT

FTP transfer seconds F-TTIME

Table 1-10 • FTPD Metrics Collected


2Using AIX Advanced Accounting

Setting Up Advanced Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Creating Advanced Accounting Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Configuring AIX Advanced Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Setting Up Advanced Accounting Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Scheduling Advanced Accounting Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Advanced Accounting Metrics Collected and ITUAM Rate Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Process Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

System Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

File System Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Network Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Disk Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Server VIO Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Client VIO Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

ARM Transaction Metrics Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9


■ Using AIX Advanced Accounting

Setting Up Advanced Accounting

Setting Up Advanced Accounting 2

Note • To collect Advanced Accounting data, the AIX system must be at Maintenance Level 3 or later.

Creating Advanced Accounting Data Files 2

Using the Advance Accounting utility acctctl, create two data files with enough space to hold a day of Advanced Accounting records. The space required depends on the amount of process activity and the Advanced Accounting configuration.

Advanced Accounting collects and can aggregate accounting information as determined by its configuration. If Advanced Accounting is configured to aggregate processing records, a smaller file size is required. If Advanced Accounting is not configured to aggregate records, a larger file size is required. Aggregated records do not include the process name in the record.

To create the Advanced Accounting Data files, use these commands:

> acctctl fcreate /var/aacct/aacct1.dat 4> acctctl fcreate /var/aacct/aacct2.dat 4

These commands create two data files allocated for 4 MB each. This is enough space for a day of hourly system interval records as well as aggregated process records.

Configuring AIX Advanced Accounting 2

Configure Advance Accounting to generate system interval and aggregated process records as shown in these example commands:

> acctctl isystem 60> acctctl iprocess 60In this example, the system interval records are created every 60 minutes. The process interval is also set to 60 minutes. The process interval record time is required because process aggregation is set to on.

The command agproc on enables record aggregation. If you do not want to aggregate records (for example, you want accounting information at the process name level), use the command agproc off. If you do not use aggregation, you must create larger data files. The following are the command for agproc on and off:

> acctctl agproc on

> acctctl agproc off

If you are gathering ARM application transactions or third-party kernel extension records, the data files might require a larger size and you must enable aggregation of these records as follows:

> acctctl agarm on> acctctl agke on


Using AIX Advanced Accounting ■


Setting Up Advanced Accounting Data Collection 2

Advanced Accounting data can be collected manually or automatically using the following scripts in the $ITUAM_UC_HOME/scripts/aacct directory. These scripts use values in the $ITUAM_UC_HOME/data/a_config.par file. If you want to collect Advanced Accounting data and do not want to collect traditional UNIX/Linux process accounting, set the variable AACCT_ONLY=Y in the a_config.par file.

■ ituam_get_aacct. This script retrieves the "Active" Advanced Accounting data file and copies it to a ITUAM_UC_HOME/history/aacct<date>.dat file. The script can be called multiple times a day if needed. If this script is called more than once a day, subsequent Advanced Accounting data files are copied to ITUAM_UC_HOME/history/aacct_n_<date>.dat, where n specifies the sequential numbering of the data files.

After copying the file the script restarts accounting and resets the AACCT data file. The ability to execute the script multiple times a day is provided as a means to respond to alerts from Advanced Accounting when data files are nearing capacity. This should not occur if data files have been created with enough space to hold data for an entire day.

■ ituam_format_aacct. This script generates usage logs from the Advanced Accounting data files in the history directory (/history/aacct_n_<date>.dat).

The Advanced Accounting record types that are included in the logs are defined by the AACCT_TRANS_IDS variable in the A_config.par file. By default, AACCT_TRANS_IDS is set to "1,4,6,7,8". Each ID number indicates one of the following Advanced Accounting Record types:

• 1 or 2 Process records

• 4 System processor and memory interval record

• 6 File system activity interval record

• 7 Network interface I/O interval record

• 8 Disk I/O Interval record

• 10 Server VIO interval record

• 11 Client VIO interval record

• 16 Aggregated ARM transaction record

The ituam_format_aacct script creates the usage logs in the $ITUAM_HOME/CS_input_source/aacctn_<date>.txt, where n is and Advanced Accounting record type.

You can call the ituam_format_aacct script with an optional date argument where date is in the format YYYYMMDD. The date argument specifies that only those data files that contain the specified date in the file name are included in the usage report/log. If no argument is present, data files with the current date in the file name are included. If multiple data files exist in the history directory for the specified day, all files for that day are included in the generated logs.




Examples

ituam_format_aacct (Advanced Accounting records with the current date are included in the usage logs)

ituam_format_aacct 20060916 (Advanced Accounting records with the date 20060916 are included in the usage logs)

■ ituam_send_aacct. This script is used to transport the usage logs to the ITUAM server where they are processed and loaded into the ITUAM database.

You can call the script with an optional date argument where date is in the format YYYYMMDD. The data argument specifies that only those usage logs that contain the specified date in the file name are transferred. If not argument is present, logs with the current data in the file name are transferred.

The ituam_send_aacct script uses the $ITUAM_HOME/scripts/enterprise/CS_log_send to connect and transfer the logs to the ITUAM server. Refer to the notes in the A_config.par file to determine the settings that work best for your environment.

The CS_log_send script uses the following variables in the A_config.par file.

• CS_METHOD. This is the protocol that is used to transfer CSR files from the collector system to the ITUAM server. Valid values are: RCP (remote copy protocol), FTP (file transfer protocol), SCP (secure copy), or SFTP (secure FTP).

• CS_USER. This is the account required to log on to the ITUAM server.

• CS_KEY. This variable is required only if the TRANSFER_VIA is set to FTP. In this situation, set this variable to the password for the account designated by CS_USER.

• CS_COLL_PATH. This is the path for the CollectorLogs directory.

If CollectorLogs is on a UNIX or Linux, system, provide the full path to the directory.

If CollectorLogs is on a Windows system, provide the virtual directory that points the CollectorLogs folder. For more information, see CollectorLogs Directory on page 4-8.

For more information about the CS_log_send script, see Transferring Log Files to the ITUAM Server on page 3-25.




Scheduling Advanced Accounting Data Collection 2

Jobs to collect and format Advanced Accounting data should be scheduled in root account crontab. The following example crontab entries collect the current AACCT data files, extract reports, and send the reports to the ITUAM server where they are processed and loaded into the ITUAM database.

5 1 * * * ( /opt/IBM/tivoli/ituam/collectors/Unix/scripts/aacct/ituam_get_aacct 1> /opt/IBM/tivoli/ituam/collectors/Unix/log/ituam_get_aacct.log 2>&1 )

10 1 * * * ( /opt/IBM/tivoli/ituam/collectors/Unix/scripts/aacct/ituam_format_aacct 1> /opt/IBM/tivoli/ituam/collectors/Unix/log/ ituam_format_aacct.log 2>&1 )

15 1 * * * ( /opt/IBM/tivoli/ituam/collectors/Unix/scripts/aacct/ituam_send_aacct 1> /opt/IBM/tivoli/ituam/collectors/Unix/log/ ituam_send_aacct.log 2>&1 )



Advanced Accounting Metrics Collected and ITUAM Rate Codes

Advanced Accounting Metrics Collected and ITUAM Rate Codes 2

The tables in the following sections show the metrics that are collected from the Advanced Accounting data files by record type. The table also shows the ITUAM rate code that is assigned to each metric.

Process Metrics Collected 2

Metric Rate Code

Interval count AAID0101

Elapsed time in seconds AAID0102

Elapsed thread time in seconds AAID0103

CPU time in seconds AAID0104

Elapsed disk pages in seconds AAID0105

Elapsed real pages in seconds AAID0106

Elapsed virtual memory pages in seconds AAID0107

Local file I/O in MB AAID0108

Other file I/O in MB AAID0109

Local sockets I/O in MB AAID0110

Other sockets I/O in MB AAID0111

Table 2-1 • Advanced Accounting Process Metrics Collected




System Metrics Collected 2

File System Metrics Collected 2

Metric Rate Code

Number of CPUs (interval aggregate) AAID0401

Entitled capacity (interval aggregate) AAID0402

System pad length (interval aggregate) AAID0403

System idle time in seconds AAID0404

User process time in seconds AAID0405

Interrupt time in seconds AAID0406

Memory size in MB (interval aggregate) AAID0407

Large page pool in MB AAID0408

Large page pool in-use in MB AAID0409

Pages in AAID0410

Pages out AAID0411

Number start I/O AAID0412

Number page steals AAID0413

Table 2-2 • Advanced Accounting System Metrics Collected

Metric Rate Code

Bytes transferred in MB AAID0601

Read/write requests AAID0602

Number opens AAID0603

Number creates AAID0604

Number locks AAID0605

Table 2-3 • Advanced Accounting File System Metrics Collected




Network Metrics Collected 2

Disk Metrics Collected 2

Server VIO Metrics Collected 2

Client VIO Metrics Collected 2

Metric Rate Code

Network number I/O AAID0701

Network bytes transferred in MB AAID0702

Table 2-4 • Advanced Accounting Network Metrics Collected

Metric Rate Code

Transfers AAID0801

Block reads AAID0802

Block writes AAID0803

Transfer block size (interval aggregate) AAID0804

Table 2-5 • Advanced Accounting Disk Metrics Collected

Metric Rate Code

Server bytes in AAID1001

Server bytes out AAID1002

Table 2-6 • Advanced Accounting Server VIO Metrics Collected

Metric Rate Code

Client bytes in AAID1101

Client bytes out AAID1102

Table 2-7 • Advanced Accounting Client VIO Metrics Collected




ARM Transaction Metrics Collected 2

Metric Rate Code

Application time AAID1601

Response time in seconds AAID1602

Queued time in seconds AAID1603

Application CPU time in seconds AAID1604

Table 2-8 • Advanced Accounting ARM Accounting Metrics Collected


3Data Collection and Consolidation

This chapter describes the files and scripts used for data collection and consolidation. The files and scripts are in the $ITUAM_UC_HOME/collectors/Unix directory.

Setting the Environment Variables for Data Collection and Consolidation . . . . . . . . . . . . . . . . . 3-2

Collecting Data: Setting Up the Data Collection Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Check pacct File Script (check_pacct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Nightly Accounting Script (ituam_uc_nightly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Turn Accounting Script (turnacct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Run Account Script (runacct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Sampler Script (sampler) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Database Storage Scripts (get_odb_storage and get_db2_storage) . . . . . . . . . . . . . . . . . . . . . . 3-7

Redo Nightly Script (redo_nightly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Consolidating Data: Setting Up the Data Consolidation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Nightly Consolidation Script (CS_nightly_consolidation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

CSR File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10

Identifiers and Rate Codes by CSR File Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13

Processing Identifiers and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Software Package (Process), Unix Interactive, Background, and Storage Rate Codes and Identifiers (CS_sum_<date>.csv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Oracle Rate Codes and Identifiers (CS_sum_ora_<date>.csv) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Oracle Table Storage Rate Codes and Identifiers (CS_sum__ora_stor_<date>.csv) . . . . . . . . 3-17

DB2 Rate Codes and Identifiers (CS_sum__db2_<date>.csv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

DB2 Table Storage Rate Codes and Identifiers (CS_sum__db2_stor_<date>.csv) . . . . . . . . . . . 3-19

UNIX File System Rate Codes and Identifiers (CS_sum_fs_<date>.csv) . . . . . . . . . . . . . . . . . . . 3-20

Transferring CSR Files to the ITUAM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

Transferring Log Files to the ITUAM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25


■ Data Collection and Consolidation

Setting the Environment Variables for Data Collection and Consolidation

Setting the Environment Variables for Data Collection and Consolidation 3

The Configuration Parameter file ($ITUAM_UC_HOME/data/A_config.par) provides a common configuration file that is used for data collection and consolidation scripts that are used to define your ITUAM environment.

To ensure that the data collection and consolidation process runs correctly, set the variables in the A_config.par file as needed for your organization before you run the scripts described in this chapter. You can modify the file using a text editor such as vi.

The A_config.par file environment variables are described in Set the Environment Variables for Data Collection and Consolidation on page 1-31.

Collecting Data: Setting Up the Data Collection Scripts 3

During the data collection process, ITUAM Data Collectors for UNIX and Linux gather data from files produced by the UNIX/Linux operating system and from the optional Oracle or DB2 accounting files that are produced by ITUAM.

ITUAM Data Collectors for UNIX and Linux format the individual UNIX/Linux and ITUAM accounting files and produce one nightly accounting file. The records in the nightly accounting file contain a jobtype that specifies the source of the data in that record. The job types are software package; UNIX/Linux interactive, background, and storage; Oracle; Oracle table storage; DB2; and DB2 table storage.

ITUAM Data Collectors for UNIX and Linux also optionally gather data from file systems and produce a nightly storage file. The records in the nightly storage file contain the jobtype file system.

The following scripts are used during the data collection process. All scripts are in the $ITUAM_UC_HOME/etc directory with the exception of the get_odb_storage and get_db2_storage scripts. These database storage scripts are in the $ITUAM_UC_HOME/scripts/oracle and db2 directories, respectively.

■ Check pacct File script (check_pacct). This script should be called three times each hour. It is used to manage the size of the UNIX pacct file. You might need to run this script more often; however, it is recommended that you do not run this script at the top of the hour because other jobs are usually scheduled at that time.

■ Nightly Accounting script (ituam_uc_nightly). This script handles all of the steps in the data collection process, including calling the following scripts used for data collection. This script should be run only once a day. The variables required for this script and the following scripts are provided set in the A_config.par file (see page 3-2).

Note • You can use any batch scheduler to run the check_pacct and ituam_uc_nightly scripts; however, the scripts must be run under the root user account. During the ITUAM Data Collectors for UNIX and Linux installation, the file $ITUAM_UC_HOME/etc/cron.entry was created. This file contains example crontab entries for these scripts.


Data Collection and Consolidation ■

Collecting Data: Setting Up the Data Collection Scripts

• Turn Accounting script (turnacct). This script moves the raw UNIX and ITUAM accounting files into the history directory and prepares the files to be formatted by the runacct script.

• Run Accounting script (runacct). This script processes the raw UNIX and ITUAM accounting files and generates the nightly accounting file.

• Sampler script (sampler). This script calls the A_sampler utility to gather data from the UNIX/Linux file system and produce the nightly storage file.

• Database storage scripts (get_odb_storage and get_db2_storage). Collect Oracle data objects and datafile storage information and DB2 partition storage information, respectively.

Check pacct File Script (check_pacct) 3

The check_pacct script checks the size of the UNIX/Linux pacct file. You schedule this script to perform periodic checks through the clock daemon (cron).

The UNIX/Linux system imposes a limit on the size of the pacct file. When the usage of the root file system reaches 98 percent, the UNIX/Linux kernel will turn process accounting off without notification. No information is recorded until the usage of the root file system is below the system threshold.

The check_pacct script helps to assure that no UNIX/Linux accounting data is lost because the script maintains the size of the pacct below a user specified limit. When the pacct file exceeds the specified limit, this script places the current pacct file in a holding area in the history directory and re-initializes the live pacct file. Depending on the activity on your system, multiple pacct files can be generated in one day.

The runacct script processes the multiple pacct files and incorporates all the data in the nightly accounting file.




Nightly Accounting Script (ituam_uc_nightly) 3

The Nightly Accounting script (ituam_uc_nightly) performs the following functions:

■ Calls the turnacct script to move the raw UNIX and ITUAM accounting files to the history directory.

■ Calls the runacct script to processes the raw UNIX and ITUAM accounting files and generate the nightly accounting file.

■ If the ITUAM_SAMPLE variable is set to Y in the A_config.par file, calls the sampler script to get a snapshot of file system use and generate the nightly file system storage file.

■ If the ORACLE_STR_SAMPLE variable is set to Y in the A_config.par file, calls the get_odb_storage script to collect table and datafile information and create the nightly Oracle storage file.

■ If the DB2_STR_SAMPLE variable is set to Y in the A_config.par file, calls the get_db2_storage script to collect database partition storage information and create the nightly DB2 storage file.

The ituam_uc_nightly script should be scheduled to run nightly around 1 a.m. Nightly processing keeps the accounting and storage data uniform and in sync for more precise and controllable resource management and chargeback.

You can use any batch scheduler to run this script; however, the script must be run under the root user account.

If you use the example entry in the $ITUAM_UC_HOME/etc/cron.entry file to run this script, output from this script is redirected to the log file $ITUAM_UC_HOME/log/ituam_uc_nightly.log.




Turn Accounting Script (turnacct) 3

The turnacct script moves the following raw UNIX and ITUAM accounting files into the history directory and prepares the files to be formatted by the runacct script:

■ UNIX/Linux wtmp, wtmpx, and pacct files.

■ ITUAM Activity file ($ITUAM_UC_HOME/data/A_activity.sys) (optional). This file is created only if project accounting is enabled.

■ ITUAM Oracle Accounting file ($ITUAM_UC_HOME/data/A_dbacct.sys) (optional). To collect data from this file, you must have the variable A_ORACLE_ACCT set to Y in the A_config.par file.

■ ITUAM DB2 Accounting file ($ITUAM_UC_HOME/data/A_db2acct.sys) (optional). To collect data from this file, you must have the variable A_DB2_ACCT set to Y in the A_config.par file.

The turnacct script renames the file to include the date in YYYYMMDD format and then re-initializes the file to collect the next day’s data.

The turnacct script is also used to turn UNIX/Linux process accounting on or off. For this use of the script, the command line arguments are:

turnacct onturnacct off




Run Account Script (runacct) 3

Because the individual UNIX and ITUAM accounting files contain raw data in binary format, they must be formatted on the computer on which the data was collected. The runacct script runs the A_format utility against the raw UNIX and ITUAM accounting files in the history directory and creates temporary accounting files.

The runacct script chronologically sorts the records in the temporary accounting files and produces one nightly accounting file, acc_<date>.dat, where <date> is in YYYYMMDD format.

This runacct script uses the first sixteen characters of the statistics record to sort. These characters contain the date and record type, which are unique, to assure proper sorting. Under UNIX, the UNIX sort command that is used is: sort +0.0 -0.16.

If your temporary accounting files are very large and the TEMP directory is too small for sorting, you might need to add the option -T to the UNIX sort command in the runacct script.

The following is a sample of the CLI commands for the A_format utility to format accounting data from within the runacct script:

# A_format FORMAT> FORMAT/TYPE=ACTIVITY/ZERO "/usr/ituam/history/activity_<date>"%FRMT-I-PROCFILE, processing file-"usr/ituam/history/activity_<date>"FORMAT> FORMAT/TYPE=ACCT/ROLL/ZERO "/usr/ituam/history/pacct_<date>" %FRMT-I-PROCFILE, processing file-"usr/ituam/history/pacct_<date>"FORMAT> FORMAT/TYPE=WTMP/ZERO "/usr/ituam/history/wtmp_<date>"%FRMT-I-PROCFILE, processing file-"usr/ituam/history/wtmp_<date>"FORMAT> EXIT #

The /ZERO qualifier re-initializes the temporary accounting file. This qualifier ensures that only the current day's statistics are contained in the file.

Using the /ROLL Qualifier

The A_format utility has an additional qualifier when processing the UNIX image accounting data in the UNIX pacct file. This qualifier is /ROLL. The /ROLL qualifier combines similar image records from background jobs into a rolled accounting record. When the same image is run by a user several times in background (no controlling terminal), these image records are rolled into one roll-up record that indicates the number of times the image was executed. This qualifier can reduce the size of the resulting nightly accounting file when numerous background jobs are performed.

You should not use the /ROLL qualifier if you use the /UNKNOWN_ PROJECT qualifier with the A_select utility (see Select Utility (A_select) on page B-8).

Using the /AGGREGATE Qualifier

The /AGGREGATE qualifier instructs the A_format utility to treat all process records as background jobs. This means that all process records are rolled up based on username and processname. This qualifier has meaning only when used with the /ROLL qualifier.




Sampler Script (sampler) 3

The sampler script invokes the A_sampler utility. The A_sampler utility traverses the file systems that include specific directory trees that are defined in the Storage Parameter file ($ITUAM_UC_HOME/data/A_storage.par).

To prevent double counting of NFS and automounted file systems, the A_sampler utility traverses only locally mounted file systems.

The A_sampler utility writes the sampled disk space usage information to the Storage file ($ITUAM_UC_HOME/data/A_storage.sys). The A_sampler utility accumulates the amount of file space allocated to the file system and the amount of file space used by UID and GID.

The sampler script moves the A_storage.sys file to the history directory and renames the file str_<date>.dat, where <date> is in YYYYMMDD format.

To execute the sampler script, the variable ITUAM_SAMPLE must be set to Y in the $ITUAM_UC_HOME/data/A_config.par file.

Database Storage Scripts (get_odb_storage and get_db2_storage) 3

If the ORACLE_STR_SAMPLE variable is set to Y in the A_config.par file, the ituam_uc_nightly script calls the get_odb_storage script to collect Oracle data objects and datafile storage information. This information is output into the $ITUAM_UC_HOME/history/ora_sto_<date>.dat file.

If the DB2_STR_SAMPLE variable is set to Y in the A_config.par file, the ituam_uc_nightly script calls the get_db2_storage script to collect DB2 database partition storage information. This information is output into the $ITUAM_UC_HOME/history/db2_sto_<date>.dat file.




Redo Nightly Script (redo_nightly) 3

If the ituam_uc_nightly script fails, use this script to reprocess the following files in the history directory:

■ pacct_<date>

■ wtmp_<date>

■ activty_<date>

■ dbacct_<date>

■ db2acct_<date>

The redo_nightly script accepts the following command line arguments:

redo_nightly today yesterday all yyyymmdd

Where:

■ today=process files with the current day’s date (this is the default)

■ yesterday=process files with yesterday’s date (the day before the current day)

■ all=process files for all dates

■ yyyymmdd=process files with a specific date (the date must be in yyyymmdd format)

The redo_nightly script invokes the runacct script, which creates and sends a new nightly accounting file or files to the $ITUAM_UC_HOME/accounting/<nodename> directory. Therefore, existing nightly accounting files for the same date are overwritten. If you want to save existing files, you must move them out of the accounting/<nodename> directory.



Consolidating Data: Setting Up the Data Consolidation Scripts

Consolidating Data: Setting Up the Data Consolidation Scripts 3

During the data consolidation process, ITUAM Data Collectors for UNIX and Linux process the nightly accounting and storage files that were created by the data collection scripts and produce an output CSR file. ITUAM processes the data in the CSR file and provides comprehensive job accounting, chargeback, and cost analysis capabilities in addition to capacity and resource reporting.

The following scripts are used during the data consolidation process.

■ Nightly Consolidation script ($ITUAM_UC_HOME/scripts/enterprise/CS_nightly_consolidation). This script calls the following scripts that support the consolidation process. The variables required for this script and the following scripts are set in the A_config.par file (see page 3-2).

• Process Multiple Nodes script ($ITUAM_UC_HOME/etc/proc_multi). This script consolidates the nightly accounting and storage files.

• CS Generate Summary script ($ITUAM_UC_HOME/scripts/enterprise/CS_gen_sum). This script generates CSR files from the consolidated data produced by the proc_multi script.

Nightly Consolidation Script (CS_nightly_consolidation) 3

The CS_nightly_consolidation script should be scheduled to run nightly after the ituam_uc_nightly script has been run. Refer to the comments in the beginning of the script to determine the best script configuration for your site.

The CS_nightly_consolidation script does the following:

■ Calls the proc_multi script to consolidate the nightly accounting and file system storage files for the previous day.

■ Calls the CS_gen_sum file to generate CSR files from the consolidated accounting and storage files.

■ Concatenates the nightly Oracle and DB2 storage files for the previous day to create CSR files of tablespace and datafile usage.

■ Calls the CS_fs_resource utility to read nightly storage files and generate CSR file of file system usage.

■ Places the CSR files in the $ITUAM_UC_HOME/CS_input_source directory. The files are transferred from this directory to the ITUAM system.



CSR File Types

CSR File Types 3

The data consolidation produces one or more of the CSR files shown in the following table. Although the format of each CSR file type is the same (see Appendix C, CSR File Format), the data that appears in the files depends on the environment variables that you set in the A_config.par file and the parameters that you pass from the CS_nightly_consolidation script.

CSR File Description

CS_sum_<date>.csv By default, the CS_nightly_consolidation script passes the following parameters to the CS_gen_sum script to produce this CSR file:

package node user packagename

The package parameter specifies that UNIX/Linux package/process jobtype is included in the CSR file. The keywords node, user, and packagename specify that the identifiers SYSTEM_ID, USERNAME, and PROCESSNAME appear in the CSR records.

For a description of the identifiers and rate codes that appear in the CSR file records, see page 3-13.

CS_sum_ora_<date>.csv To produce this CSR file containing Oracle metrics, the environment variable GEN_ORACLE must be set to Y in the A_config.par file.

By default, the CS_nightly_consolidation script passes the following parameters to the CS_gen_sum script to produce this CSR file:

oracle node user or_base or_user

The oracle parameter specifies that the Oracle jobtype is included in the CSR file. The keywords node, user, or_base, and or_user specify that the identifiers SYSTEM_ID, USERNAME, OR_BASE, and OR_USER appear in the CSR records.


Table 3-1 • CSR Files Produced by the CS_gen_sum Script



CSR File Types

CS_sum_orasto_<date>.csv To produce this CSR file containing Oracle table storage metrics, the environment variable GEN_ORACLE_STORAGE must be set to Y in the A_config.par file.

This file is created by the CS_nightly_ consolidation script, which concatenates the individual Oracle storage files.


CS_sum_db2_<date>.csv To produce this CSR file containing DB2 metrics, the environment variable GEN_DB2 must be set to Y in the A_config.par file.

By default, the CS_nightly_consolidation script passes the following parameters to the CS_gen_sum script to produce this CSR file:

db2 node user db2_base

The db2 parameter specifies that the DB2 jobtype is included in the CSR file. The keywords node, user, and db2_base specify that the identifiers SYSTEM_ID, USERNAME, and DB2_BASE appear in the CSR records.



Table 3-1 • CSR Files Produced by the CS_gen_sum Script (Continued)



CSR File Types

CS_sum_db2sto_<date>.csv To produce this CSR file containing DB2 table storage metrics, the environment variable GEN_DB2_STORAGE must be set to Y in the A_config.par file.

This file is created by the CS_nightly_ consolidation script, which concatenates the individual DB2 storage files.


CS_sum_fs_<date>.csv To produce this CSR file containing UNIX/Linux file system metrics, the environment variable GEN_UNIXFS must be set to Y in the A_config.par file (this is the default).

The CS_nightly_consolidation script calls the CS_fs_resource utility to read the nightly storage files and generate the records for this CSR file.



Table 3-1 • CSR Files Produced by the CS_gen_sum Script (Continued)



Identifiers and Rate Codes by CSR File Type

Identifiers and Rate Codes by CSR File Type 3

The following sections show the default identifiers and rate codes that appear in the CSR files. If you want to use identifiers and rate codes other than those listed, please contact IBM Software Support for assistance.

Processing Identifiers and Resources 3

All identifiers and resource rate codes that are in the CSR records are defined by default in ITUAM. However, the resource rate codes require a monetary value and other user-defined options that must be defined before the CSR records are processed. To configure rate codes, use the ITUAM Administrator application as described in the IBM Tivoli Usage and Accounting Manager Administrator’s Guide.

Software Package (Process), Unix Interactive, Background, and Storage Rate Codes and Identifiers (CS_sum_<date>.csv) 3

The CS_sum_<date>.csv file contains separate records for software package (processes) and UNIX/Linux interactive, background, and storage metrics. These records begin with the headers UNIXINTR, UNIXBACK, UNIXSTOR, and UNIXSPCK, respectively. The identifiers and rate codes for each record type are described in Table 3-2 (identifiers) and Table 3-3 on page 3-14 (rate codes).

Identifier Description

Interactive, Background, and Storage Records

SYSTEM_ID Server node name.

USERNAME OS user name.

Software Package Records



PROCESSNAME Process name.

Table 3-2 • UNIX Operating System Identifiers




Rate Code Description

Interactive Records

LLA101 Unix Interactive Block I/O (1,000s)

LLA102 Unix Interactive Character I/O (100,000s)

LLA103 Unix Interactive Image Time (Hours)

LLA104 Unix Interactive Connect Time (Hours)

LLA105 Unix Interactive User CPU (Minutes)

LLA106 Unix Interactive System CPU (Minutes)

LLA107 Unix Interactive Total CPU (Minutes)

LLA108 Unix Interactive Memory (MB Days)

LLA109 Unix Interactive Image Count

LLA110 Unix Interactive Logins

LLA111 Unix Interactive SU Image Count

LLA112 Unix Interactive SU Count

LLA113 Unix Interactive SU Time (Hours)

LLA114 Unix Interactive Window Time (Hours)

LLA115 Unix Interactive Chg Image Time (Hours)

LLA116 Unix Interactive Chg Connect Time (Hours)

LLA117 Unix Interactive Chg SU Time (Hours)

LLA118 Unix Interactive Chg Win Time (Hours)

Background Records

LLB101 Unix Background Block I/O (1,000s)

LLB102 Unix Background Character I/O (100,000s)

LLB103 Unix Background Image Time (Hours)

LLB104 Unix Background User CPU (Minutes)

LLB105 Unix Background System CPU (Minutes)

LLB106 Unix Background Total CPU (Minutes)

Table 3-3 • UNIX Operating System Rate Codes




Background Records (continued)

LLB107 Unix Background Memory (MB Days)

LLB108 Unix Background Image Count

LLB109 Unix Background Logins

LLB110 Unix Background Chg Image Time (Hours)

Storage Records

LLD101 Unix Block Weeks (not in CIMSRate table by default)

Software Package Records

LLG101 Unix Process Block I/O (1,000s)

LLG102 Unix Process Character I/O (100,000s)

LLG103 Unix Process Image Time (Hours)

LLG104 Unix Process User CPU (Minutes)

LLG105 Unix Process System CPU (Minutes)

LLG106 Unix Process Total CPU (Minutes)

LLG107 Unix Process Memory (MB Days)

LLG108 Unix Process Image Count

LLG109 Unix Process SU Image Count

LLG110 Unix Process Chg Image Time (Hours)


Table 3-3 • UNIX Operating System Rate Codes




Oracle Rate Codes and Identifiers (CS_sum_ora_<date>.csv) 3

The CS_sum__ora_<date>.csv file contains records with Oracle metrics. These records begin with the header ORCLUNIX. The identifiers and rate codes in these records are described in Table 3-4 and Table 3-5.




OR_BASE Oracle instance.

OR_USER Oracle user name.

Table 3-4 • Oracle Identifiers


LLE101 Unix Oracle Logins

LLE102 Unix Oracle Session CPU (Minutes)

LLE103 Unix Oracle Connect (Hours)

LLE104 Unix Oracle UGA Memory (MB Days)

LLE105 Unix Oracle PGA Memory (MB Days)

LLE106 Unix Oracle Rec CPU (Minutes)

LLE107 Unix Oracle User Commits

LLE108 Unix Oracle Physical Reads

LLE109 Unix Oracle Physical Writes

LLE110 Unix Oracle DB Block Gets

LLE111 Unix Oracle Disk Sorts

LLE112 Unix Oracle Messages Sent

LLE113 Unix Oracle Messages Received

Table 3-5 • Oracle Rate Codes




Oracle Table Storage Rate Codes and Identifiers (CS_sum__ora_stor_<date>.csv) 3

The CS_sum__ora_stor_<date>.csv file contains separate records for Oracle table storage and data file metrics. These records begin with the headers ORCLUNST and ORCLDFIL, respectively. The identifiers and rate codes for each record type are described in Table 3-6 and Table 3-7.


All Records


OR_BASE Oracle instance.

OR_USER Oracle user name/schema.

OR_TSPACE Tablespace for storage records. Tablespace/data file name for data file records.

OR_SEGNAME Segment name. This identifier is optional and is not recommended. To use this identifier you must modify the $ITUAM_UC_HOME/scripts/oracle/get_odb_storage script.

Table 3-6 • Oracle Table Storage Identifiers


Storage Records

LLY101 Unix Oracle Blocks

LLY102 Unix Oracle Mbytes

LLY103 Unix Oracle Extents

Data File Records

LLY104 Unix Oracle Datafile Tablespace Allocated (MB)

LLY105 Unix Oracle Datafile Tablespace Allocated (Oracle Blocks)

Table 3-7 • Oracle Table Storage Rate Codes




DB2 Rate Codes and Identifiers (CS_sum__db2_<date>.csv) 3

The CS_sum__db2_<date>.csv file contains records with DB2 metrics. These records begin with the header UDB2UNIX. The identifiers and rate codes in these records are described in Table 3-8 and Table 3-9.




DB2_BASE Database name.

Table 3-8 • DB2 Identifiers


LLF101 Unix DB2 Commit SQL Stmts

LLF102 Unix DB2 Deadlocks

LLF103 Unix DB2 Direct Reads

LLF104 Unix DB2 Direct Writes

LLF105 Unix DB2 Int Deadlock Rollbacks

LLF106 Unix DB2 Lock Wait Time

LLF107 Unix DB2 Logins

LLF108 Unix DB2 PD LReads

LLF109 Unix DB2 PD PReads

LLF110 Unix DB2 PD Writes

LLF111 Unix DB2 PI LReads

LLF112 Unix DB2 PI PReads

LLF113 Unix DB2 PI Writes

LLF114 Unix DB2 Rollback SQL Stmts

LLF115 Unix DB2 Rows Deleted

LLF116 Unix DB2 Rows Inserted

LLF117 Unix DB2 Rows Selected

LLF118 Unix DB2 Rows Updated

Table 3-9 • DB2 Rate Codes




DB2 Table Storage Rate Codes and Identifiers (CS_sum__db2_stor_<date>.csv) 3

The CS_sum_db2_stor_<date>.csv file contains records with DB2 table storage metrics. These records begin with the header UDB2UNST. The identifiers and rate codes in these records are described in Table 3-10 and Table 3-11.

LLF119 Unix DB2 System CPU (Minutes)

LLF120 Unix DB2 Sort Overflows

LLF121 Unix DB2 Total Sorts

LLF122 Unix DB2 User CPU (Minutes)

LLF123 Unix DB2 UOW Log Space Used (MB Days)


Table 3-9 • DB2 Rate Codes (Continued)



DB2_INST DB2 instance.

DB2_BASE Database name.

DB2_TSPACE Tablespace name.

DB2_TSTYPE Table space type.

Table 3-10 • DB2 Table Storage Identifiers


LLY201 Unix DB2 Total Storage (4k Pages)

LLY202 Unix DB2 Usable Storage (4k Pages)

LLY203 Unix DB2 Used Storage (4k Pages)

LLY204 Unix DB2 Free Storage (4k Pages)

LLY205 Unix DB2 High Water Mark

LLY206 Unix DB2 Extent Size (4k pages)

LLY207 Unix DB2 Prefetch Size (4k pages)

LLY208 Unix DB2 Containers

Table 3-11 • DB2 Table Storage Rate Codes




UNIX File System Rate Codes and Identifiers (CS_sum_fs_<date>.csv) 3

The CS_sum_fs_<date>.csv file contains records with UNIX file system metrics. These records begin with the header UNIXFSYS. The identifiers and rate codes in these records are described in Table 3-12 (identifiers) and Table 3-13 (rate codes).



FS_MOUNT_PT File system mount point.

FS_DEVICENAME File system device name.

Table 3-12 • UNIX File System Identifiers


LLR101 Unix Filesystem Size (512-byte Blocks)

LLR102 Unix Filesystem Blocks Used (512-byte Blocks)

LLR103 Unix Filesystem Number of Files

LLR104 Unix Filesystem Size (GB Days)

LLR105 Unix Filesystem Used (GB Days)

Table 3-13 • UNIX File System Rate Codes



Transferring CSR Files to the ITUAM Server

Transferring CSR Files to the ITUAM Server 3

The CS Send script ($ITUAM_UC_HOME/scripts/enterprise/CS_send) transfers the CSR files produced during the consolidation process from the CS_input_source directory to one of the process definition directories on the ITUAM server. The destination process definition directory depends on the CSR file type as shown in the following table. (For a description of the CSR file types produced by ITUAM Data Collectors for UNIX and Linux, see page 3-10).

Each process definition directory contains feed subdirectories that reflect the source of the data. For example, UNIX file system CSR files (CS_sum_fs_<date>.csv) from the server zeus are placed in the subdirectory zeus within the process definition directory UnixFS (i.e., UnixFS/zeus) on the ITUAM system. If the subdirectory does not exist in the process definition directory, it is created the first time that the CS_send script is run.

Note • The CS_send script also renames the CSR files when the files are transferred to a feed subdirectory in the process definition folders. For example, all CS_sum_fs_ <date>.csv CSR files are sent to a subdirectory in the UnixFS process definition directory and are renamed <date>.txt.

The CS_send script should be run after the CS_nightly_consolidation script has completed. Refer to the comments in the beginning of the script to determine the best script configuration for your site.

To process the CSR files using ITUAM, refer to the IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide.

Destination Process Definition Folder Name CSR File Type

processes/UnixDB2 The CS_sum_db2_<date>.csv CSR files are sent to a feed subdirectory within this directory.

processes/UnixDB2Storage The CS_sum_db2_stor_<date>.csv CSR files are sent to a feed subdirectory within this directory.

processes/UnixORA The CS_sum_ora_<date>.csv CSR files are sent to a feed subdirectory within this directory.

processes/UnixORAStorage The CS_sum_ora_stor_<date>.csv CSR files are sent to a feed subdirectory within this directory.

processes/UnixFS The CS_sum_fs_<date>.csv CSR files are sent to a feed subdirectory within this directory.

processes/UnixOS The CS_sum_<date>.csv CSR files are sent to a feed subdirectory within this directory.

Table 3-14 • Process Definition Folders and CSR Files




Setting the Configuration Variables for File Transfer

To transfer the CSR files to the ITUAM system using the CS_send script, set the following variables in the $ITUAM__UC_HOME/data/A_config.par file.

The variable descriptions are grouped by CS_METHOD variable value because this value determines the values that you can set for other variables. The CS_METHOD variable defines the protocol that is used to transfer the CSR files to the ITUAM system.


CS_METHOD=MV Move.

CS_USER Not applicable.

CS_KEY Not applicable.

CS_PROC_PATH The path to the processes directory on the ITUAM server.

If the ITUAM server is on a Windows system, this variable is not applicable.

If the ITUAM server is on a UNIX or Linux system, provide the full path to the procesess directory.

This variable is used by the CS_send script.

CS_COLL_PATH The path to the ITUAM CollectorLogs directory on the ITUAM server.

If the ITUAM server is on a Windows system, this variable is not applicable.

If the ITUAM server is on a UNIX or Linux system, provide the full path to the CollectorLogs directory.

This variable is used by the CS_log_send script (see Transferring Log Files to the ITUAM Server on page 3-25).

CS_PLATFORM Not applicable.

CS_UPATH Not applicable

Table 3-15 • Variables for File Transfer to ITUAM




CS_METHOD=FTP

CS_USER The account required to log on to the ITUAM server. If the ITUAM server is on a Windows system and you are using a domain account, use the following format for the user name:

CS_USER="<domain name>\\\\<account name>"

Make sure that you use the four backslashes between the account name and domain name as shown.

CS_KEY The password for the account defined by the CS_USER variable.

CS_PROC_PATH The path to the processes directory on the ITUAM server.

If processes is on a UNIX or Linux, system, provide the full path to the directory.



CS_COLL_PATH The path to the CollectorLogs directory on the ITUAM server. If CollectorLogs is on a UNIX or Linux, system, provide the full path to the directory.

If CollectorLogs is on a Windows system, provide the virtual directory that points the CollectorLogs folder. For more information, see CollectorLogs Directory on page 4-8.

This variable is used by the CS_log_send script.

CS_PLATFORM The ITUAM server name.

CS_UPATH The home directory for the account running the CS_send or CS_log_send script.


Table 3-15 • Variables for File Transfer to ITUAM (Continued)




CS_METHOD=SFTP

Or

CS_METHOD=SCP

To use SFTP (Secure FTP, valid only if ITUAM server is on UNIX or Linux) or SCP (Secure Copy, valid only if ITUAM server is on Windows), the user defined by the ITUAM_USER variable must have a null Secure Shell Public Key on the ITUAM system for the account defined by ITUAM_USER. This enables the ITUAM_USER account to connect to ITUAM as the CS_USER account and no password is needed.

ITUAM_USER The ITUAM account on the collector platform.

CS_USER The receiving account on the ITUAM system.

CS_KEY Not applicable.

CS_PROC_PATH The path to the procesess directory on the ITUAM server.

If CS_METHOD=SCP, provide the full path to the Processes folder.

If CS_METHOD=SFTP, provide the full path from the login directory to the processes directory.


CS_COLL_PATH The path to the ITUAM CollectorLogs directory on the ITUAM server.

If CS_METHOD=SCP, provide the full path to the CollectorLogs folder.

If CS_METHOD=SFTP, provide the full path from the login directory to the CollectorLogs directory.

This variable is used by the CS_log_send script.

CS_PLATFORM The ITUAM server name.

CS_UPATH Not applicable.


Table 3-15 • Variables for File Transfer to ITUAM (Continued)




Transferring Log Files to the ITUAM Server 3

You can send UNIX/Linux subsystem log files that contain usage data directly to the ITUAM server for conversion to a CSR file and subsequent processing. For example, you might want to transfer the xferlog produced by some ftpd systems directly to the ITUAM server.

You can use the CS Log Send script ($ITUAM_UC_HOME/scripts/enterprise/CS_log_send) to transfer the log files to ITUAM. The log file is placed in the CollectorLogs directory on the ITUAM system in the following subdirectory architecture: CollectorLogs/<collector>/<feed>.

Note • To transfer log files to the ITUAM system using the CS_log_send script, you must set the same variables in the A_config.par file as shown in Setting the Configuration Variables for File Transfer on page 3-22.

The steps required to process the log files once they are transferred to the CollectorLogs directory depends on the ITUAM system that you are using.

To process the log files using ITUAM, refer to the "ITUAM Universal Data Collector" chapter in the IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide.

Setting the Script Parameters for File TransferThe CS_log_send script requires the following parameters.

Parameter Description

log-file The complete path and file name of the log file that you want to send to the ITUAM server (e.g., /var/log/vsftpd.log).

proc-type The name of the process subdirectory in the CollectorLogs directory on the ITUAM server (e.g., FTPD). You must create the subdirectory prior to running the CS_log_send script if the subdirectory does not exist.

Table 3-16 • CS_log_send Script Parameters




ExampleIf you use the following command to transfer a vsftpd.log file from server hestia to the ITUAM server:

> CS_log_send /var/log/vsftpd.log FTPD

The log file would be placed in the ...CollectorLogs/FTPD/hestia directory.

outfile-name (optional) The name of the output file that will be placed in the CollectorLogs/<process>/<feed> subdirectory. The feed subdirectory is created automatically.

If this parameter is not provided, the file is named YYYYMMDD.txt, where YYYYMMDD is the current date.

Parameter Description

Table 3-16 • CS_log_send Script Parameters (Continued)


4Data Processing

This chapter describes the directories, files, and scripts used to run ITUAM Processing Engine on a UNIX or Linux system. Before running ITUAM Processing Engine, you must set the administrative options for data processing as described in the IBM Tivoli Usage and Accounting Manager Administrator’s Guide.

About ITUAM Processing Engine Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Modifying Data Processing Files and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

ITUAM Data Collectors for UNIX and Linux Data Processing Architecture . . . . . . . . . . . . . . . . . . 4-3

collectors Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

CollectorLogs Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

processes Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

LogFiles Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Processing Data: Setting Up the Data Processing Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13

Nightly Script (nightly.sh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Nightly Job Script (nightly.pl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Processing Script (procCIMS.pl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15


■ Data Processing

About ITUAM Processing Engine Programs

About ITUAM Processing Engine Programs 4

ITUAM Processing Engine is a fast, efficient data processing engine capable of handling large volumes of data. ITUAM Processing Engine consists of the following programs. Each of these programs is a JAR file in the $ITUAM_HOME/jlib directory.

■ CIMSAcct. This program processes the CSR or CSR+ files provided ITUAM Data Collectors for UNIX and Linux and performs functions such as account code conversion. CIMSAcct produces a CSR+ output file, which is sorted by the CIMSSort subroutine and sent to CIMSBill.

■ CIMSBill. This program processes the sorted CSR+ file from CIMSAcct and builds output files that contain the billing information that is used to generate invoices and reports.

■ CIMSLoad. This program loads the output files from CIMSAcct and CIMSBill into an Oracle, SQL Server, or DB2 for z/OS database.

For more information about the ITUAM Processing Engine components, including the input and output files for each component, refer to IBM Tivoli Usage and Accounting Manager Administrator’s Guide.

The following sections described the directories, files, and scripts used in the data processing cycle on a UNIX or Linux system.

Modifying Data Processing Files and Scripts 4

Important! • If you modify any of the files or scripts provided with ITUAM Data Collectors for UNIX and Linux, it is very important that you rename the file. Otherwise, the file will be overwritten when you upgrade to a new version of ITUAM Data Collectors for UNIX and Linux.

Although you can modify any of the files and scripts shipped with ITUAM Data Collectors for UNIX and Linux, the following scripts will most likely require modification. These files are used to process data and load the output files to the ITUAM database.

■ $ITUAM_HOME/scripts/nightly.sh

■ $ITUAM_HOME/scripts/nightly.pl

■ $ITUAM_HOME/scripts/loadCIMS.sh

■ $ITUAM_HOME/scripts/loadCIMS.pl

■ $ITUAM_HOME/processes/process definition/Jobdefinitionname.pl

■ $ITUAM_HOME/processes/process definition/ProcCntl.xml

Instructions for modifying these files and scripts are included in this chapter. All ITUAM Data Collectors for UNIX and Linux scripts also include instructions in the script.


Data Processing ■

ITUAM Data Collectors for UNIX and Linux Data Processing Architecture

ITUAM Data Collectors for UNIX and Linux Data Processing Architecture 4

The following is an overview of the components that comprise the ITUAM Data Collectors for UNIX and Linux data processing architecture.

The components are grouped by directory in which they reside. It might be helpful to refer to the directories as you read the following sections.

collectors Directory 4

By default, the $ITUAM_HOME/collectors directory contains the following subdirectories:

■ Unix. This directory contains all of the files and scripts required to run the collectors in the Collector Base Package (package 1) and the Collectors Package for Databases (package 2). These are the files and scripts described in Chapter 3, Data Collection and Consolidation.

■ UnixLinux. This directory contains the files required to install the Collector Base Package and the Collectors Package for Databases on multiple remote computers. For more information, see Installing ITUAM Data Collectors for UNIX and Linux Remotely on page 1-13. For a list of the files used for remote installation, see UnixLinux Directory on page A-3.

■ Individual directories for the AIX Advanced Accounting, Apache, and FTPD data collectors.

Individual collector directories for Advanced Accounting include a conversion script and an XML job file that is used to process the input usage log file and create a CSR file.

Individual collector directories for the Apache and FTPD collectors include only a conversion script.

The following sections describe the components that can appear in the individual collectors directories.


■ Data Processing


Conversion Script

The conversion script performs the following conversion and processing tasks depending on the data collector.

Conversion script tasks for the Apache and FTPD data collectors:

■ Reads the usage metering files contained in the $ITUAM_HOME/CollectorLogs/<collector name>/<feed> directory, where feed defines the source of the usage file. For example, Apache log files from the server zeus are in the Apache/zeus subdirectory.

If there are multiple feed subdirectories for a collector, the conversion script will search for usage metering files in all subdirectories.

■ Calls ITUAMPerl Aggregation Engine (if applicable). ITUAM Perl Aggregation Engine (cs_agtools.pm) is a Perl module that aggregates the records within a usage metering file by identifier values. That is, if multiple records within a file contain the same identifier values,ITUAM Aggregation Engine produces one record that contains sum total resource values for the rate codes within these records. Aggregation reduces the amount of data that ITUAM Processing Engine must process and improves processing time.

■ Defines the chargeback identifiers and resources that are collected from the usage metering data for input into the CSR file. (Note that this is not applicable to all collectors.)

The most useful identifiers and resources for each collector are defined in the collector’s conversion script. These are the identifiers and resources that appear in the CSR file records.

If you want to define identifiers and/or resources other than the default values in the conversion script, you need to modify the script. Note that if you want to use resources other than those defined, you need to add the rate codes for any new resources to the CIMSRate table as described in the IBM Tivoli Usage and Accounting Manager Administrator’s Guide.

■ Calls the Cleanup subroutine to purge usage metering files from the feed subdirectories. Usage metering files older the than Clean_Age parameter value will be purged. For more information about the Cleanup subroutine, see About the Scan and Cleanup Subroutines on page 4-10.


Data Processing ■


Conversion script tasks for the AIX Advanced Accounting data collectors:

■ Calls the ITUAM Integrator utility ($ITUAM_HOME/jib/CIMSIntegrator.jar) to process the Advanced Accounting usage log files in $ITUAM_HOME/CollectorLogs/<AACCT_n>/<feed> directories, where feed defines the source of the usage file.

ITUAM Integrator uses the parameters defined in an XML job file to process the logs. ITUAM Integrator and the XML job file are described in XML Job File (for AIX Advanced Accounting Data Collection Only) on page 4-7. For example, Advanced Accounting log files for record type one from the server zeus are in the AACCT_1/zeus subdirectory.

■ Calls the Cleanup subroutine to purge usage metering files from the <AACCT_n>/<feed> subdirectories. Usage metering files older the than cleanup_age parameter value will be purged. For more information about the Cleanup subroutine, see About the Scan and Cleanup Subroutines on page 4-10.

Conversion Script ParametersThe conversion scripts for the AIX Advanced Accounting, Apache, and FTPD collectors require the parameters shown in the following table.

Parameter Description/Values

LogDate The log date specifies the date for the data that you want to collect. For more information about using a log date, including valid log date values, see Nightly Script (nightly.sh) on page 4-13.

RetentionFlag This parameter is for future use.

AllowMissingFiles Specifies whether a warning or error occurs when feed subdirectories do not contain a file that matches the log date value. Valid values are:■ "TRUE" (a warning occurs, processing continues)

■ "FALSE" (an error occurs, processing fails)

AllowEmptyFiles Specifies whether a warning or error occurs when feed subdirectories contain a zero-length file that matches the log date value. Valid values are:■ "TRUE" (a warning occurs, processing continues)


OutputFolder The process definition directory for the collector.

Table 4-1 • Conversion Script Parameters


■ Data Processing


LogFolder The full path to the subdirectory in the CollectorLogs directory that contains the conversion script. For example, if you are running the Apache conversion script (Apache.pl) the path the Apache subdirectory might be /usr/ituam/CollectorLogs/Apache. The conversion script will search for all usage metering files in the CollectorLogs feed subdirectories that match the LogDate parameter value.

LogFileName (optional) By default, the conversion script searches for usage metering files that match the LogDate parameter value. However, you can use this parameter to specify another file name.


Table 4-1 • Conversion Script Parameters (Continued)


Data Processing ■


XML Job File (for AIX Advanced Accounting Data Collection Only)

ITUAM Integrator is a utility that enables you to modify input data provided in a variety of formats. The AIX Advanced Accounting data collectors use ITUAM Integrator to process the Advanced Accounting log files in the $ITUAM_HOME/CollectorLogs/<AACCT_n>/<feed> directories.

ITUAM Integrator uses an XML job file to define the input Advance Accounting log file to be processed and the output file that is created. The default output file is a CSR file.

You must modify the path /opt/IBM/tivoli/ituam/ for the following attributes in the job file as appropriate for your installation:

■ <File name="/opt/IBM/tivoli/ituam/CollectorLogs/AACCT_n/CurrentLog.txt" />

This is the path the Advanced Accounting usage log file.

■ <File name="/opt/IBM/tivoli/ituam/CollectorLogs/AACCT_n/CSRout.txt" />

This is the path for the output CSR file that is created by ITUAM Integrator. The conversion script transfers the CSR file to the appropriate feed directory in the process definition directory (see processes Directory on page 4-9).

For a detailed description of ITUAM Integrator and the XML job file, IBM Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide.


■ Data Processing


CollectorLogs Directory 4

This $ITUAM_HOME/CollectorLogs directory contains the usage metering files produced by the AIX Advanced Accounting, Apache, and FTPD data collectors.

For example, the usage log file or files produced by the data collector for AIX Advanced Accounting are placed in the appropriate subdirectory according to the type of records that are in the log file. That is, usage log files with AIX Advanced Accounting record type 1 data are sent to the AACCT_1 subdirectory, log files for record type 3 are sent to the AACCT_3 subdirectory, etc.

Within each CollectorLogs subdirectory, there is a feed subdirectory, where feed defines the source of the usage file. For example, usage logs containing Advanced Accounting data for record type 1 from the server zeus are in the AACCT_1/zeus subdirectory.

If there are multiple feed subdirectories for a collector, the conversion script will search for usage metering files in all subdirectories.

If the CollectorLogs directory is on a Windows system, you must FTP the usage metering files to the directory. To facilitate the navigation of the FTP site, you may create a virtual directory that points to the CollectorLogs directory.


Data Processing ■


processes Directory 4

The ITUAM Data Collectors for UNIX and Linux installation includes the $ITUAM_HOME/sample_processes directory. The subdirectories in sample_processes are referred to as process definitions. A process definition is a directory that contains the files required to process usage data from a particular source such as a database, operating system, or application.

When you install ITUAM Data Collectors for UNIX and Linux, the sample_processes directory and all of its contents are copied to the $ITUAM_HOME/processes. Each time that you re-install ITUAM Data Collectors for UNIX and Linux or upgrade to a new release, the application searches for the processes directory and recreates the directory if it does not exist.

When a new release of ITUAM Data Collectors for UNIX and Linux contains a new process definition directory or changes to an existing subdirectory or its contents, the additions and changes are made in the sample_processes directory. You can then copy the new or updated directories/files to the processes directory.

To help to ensure that you do not lose data, it is recommended that you include the processes directory in your back up schedule.

Each process definition directory contains the following. Each of these components are described in the following sections.

■ A Perl job script, Jobdefinitionname.pl, that contains the processing instructions for ITUAM Processing Engine on a UNIX or Linux system.

■ One or more feed subdirectories that contain the CSR or CSR+ files created by ITUAM Data Collectors for UNIX and Linux.

■ Files used to process the data in the CSR or CSR+ files, including the ProcCntl.xml file. This file contains the parameters for the CIMSAcct, CIMSBill, and CIMSLoad programs.

A separate process definition is required for each subsystem that you collect data from. Default process definition directories are provided for the CSR files produced by ITUAM Data Collectors for UNIX and Linux.

If a process definition directory does not exist for the collector, you can simply copy and rename an existing directory and modify the job script.

If the processes directory is on a Windows system, you must FTP the usage metering files to the directory. To facilitate the navigation of the FTP site, you may create a virtual directory that points to the processes directory.


■ Data Processing


Job Script

The Perl job script, Jobdefinitionname.pl, performs the following tasks depending on the data collector.

If you are processing CSR files produced by the Collector Base Package or the Collector Package for Databases:

1 Calls the Scan subroutine to gather the yyyymmdd.txt CSR or CSR+ files in the process definition subdirectories, where the date is in yyyymmdd format. The files that are gathered depend on the LogDate parameter that you supply (see Using the LogDate Parameter). For example, if you provide a LogDate parameter of 20060318, all files named 20060318.txt are gathered.

2 Calls the procCIMS.pl script to run CIMSAcct, CIMSBill, and CIMSLoad (see Processing Script (procCIMS.pl) on page 4-15).

3 Calls the Cleanup subroutine to purge files from the process definition directory and feed subdirectories.

If you are processing CSR files produced by other collector packages:

If you are using ITUAM Processing Engine to process CSR or CSR+ files produced by the other collector packages, the job script first calls the conversion script (see Conversion Script on page 4-4) before performing the preceding steps.

Using the LogDate ParameterThe job script requires the LogDate parameter to select the files that are processed by ITUAM Processing Engine. This parameter is entered in the command line when the nightly.sh script is run. For more information about the LogDate parameter and the nightly.sh script, see Nightly Script (nightly.sh) on page 4-13.

About the Scan and Cleanup Subroutines

Note • The Scan and Cleanup subroutines are in the Perl module CS_libs.pm (see processes Directory on page 4-9).

The job script calls the Scan subroutine to perform the following tasks:

1 Verifies that the subdirectory or subdirectories in the process definition directory contain a CSR or CSR+ file with a date in its file name that matches the LogDate parameter.

2 If there are multiple subdirectories that contain files that match the LogDate parameter, concatenates the CSR or CSR+ files from each subdirectory into one file.

3 Outputs the final CSR or CSR+ file to the process definition directory. The file name for the final CSR or CSR+ file is either yyyymmdd.txt or CurrentCSR.txt depending on the value that you set for the retainDateFlag parameter in the job script.


Data Processing ■


The job script calls the Cleanup subroutine to delete CSR or CSR+ files that have yyyymmdd in the file name from the process definition subdirectories. The job script includes a Clean_Age parameter that enables you to specify the number of days that you want to retain files before they are deleted.

Modifying the Job ScriptThe job script calls and passes the following parameters to the conversion script (if applicable), the Scan and Cleanup subroutines, and the procCIMS.pl script. You need to modify these parameters for you organization as needed.


this_job The name of the process definition directory in which the job script resides. Do not change this parameter unless the name of the process definition directory has been changed.

job_xml The XML file that contains the parameters for the CIMSAcct, CIMSBill, and CIMSLoad programs.

The default file name is ProcCntl.xml. Do not change this parameter unless you have changed the file name.

For more information about the ProcCntl.xml file, refer to the IBM Tivoli Usage and Accounting Manager Administrator’s Guide.

retainDateFlag Specifies whether the date is retained in the CSR or CSR+ file that is produced by the Scan subroutine (i.e., yyyymmdd.txt rather than CurrentCSR.txt). Valid values are:■ "TRUE" (the file name is yyyymmdd.txt)

■ "FALSE" (the file name is CurrentCSR.txt)

The default is "FALSE".

allowEmptyFiles Specifies whether a warning or error occurs if the feed subdirectories contain a zero-length file that match the log date value. Valid values are:■ "TRUE" (a warning occurs, processing continues)


The default is "TRUE".

allowMissingFiles Specifies whether a warning or error occurs when feed subdirectories do not contain a file that matches the log date value. Valid values are:■ "TRUE" (a warning occurs, processing continues)



Table 4-2 • Parameters Passed From the Job Script


■ Data Processing


Feed Subdirectory

Feed subdirectories are used to store CSR or CSR+ files ITUAM Data Collectors for UNIX and Linux. The CSR or CSR+ file name contains a date in yyyymmdd format.

The Scan subroutine processes and concatenates the CSR or CSR+ files in the feed subdirectories by the date in the file name. The resulting output file is placed directly in the process definition directory. For more information, see About the Scan and Cleanup Subroutines on page 4-10.

Important! • To prevent data processing errors, the process definition directory should not contain subdirectories other than feed subdirectories and feed subdirectories should not contain files other than CSR or CSR+ files.

Clean_Age The number of days that you want to keep yyyymmdd.txt CSR or CSR+ files in the process definition directory after their creation date.

Example:

Clean_Age="60"

This example specifies that all files that are older than 60 days from the current date are deleted.

The default is 100 days from the current date.

Note: CSR or CSR+ files named yyyymmdd.txt appear in the process definition directory only when the retainDateFlag parameter is set to TRUE. Otherwise, the files are named CurrentCSR.txt. In this case, the existing CSR/CSR+ file is overwritten each time a new file is created. Therefore, excess files are not accumulated and file clean up is not required.

SubDirs Specifies whether the yyyymmdd.txt files that are contained in the feed subdirectories are deleted. The files are deleted on the schedule set by the Clean_Age parameter. Valid values are:

■ "TRUE" (the files are deleted)

■ "FALSE" (the files are not deleted)



Table 4-2 • Parameters Passed From the Job Script (Continued)


Data Processing ■

Processing Data: Setting Up the Data Processing Scripts

LogFiles Directory 4

The $ITUAM_HOME/LogFile directory contains log files that contain the results of each job that you ran by day. If a warning or failure occurs during processing, the file indicates at which point the warning/failure occurred.

The contents of the job file are included in an e-mail message that notifies recipients of successful, successful with warning, or failed processing. The e-mail recipients are defined in the nightly.sh script as described on page 4-13.

Note • A job log file is not created until the job is run. If an error occurs and the job is not run (for example, the job script contains a syntax error) a log file is not generated and a notification e-mail is not sent. To ensure that the job runs correctly and that a log file is generated, you can run the job script from the command line.

The log files are named nightly_PREDAY_yyyymmdd.txt or nightly_yyyymmdd.txt, where nightly_yyyymmdd.txt is the most recent log. The date in nightly_PREDAY_yyyymmdd.txt is the day that the nightly.sh script was run. The date in nightly_yyyymmdd.txt is the date specified by the LogDate parameter.

Processing Data: Setting Up the Data Processing Scripts 4

The $ITUAM_HOME/scripts directory contains the scripts described in the following sections. The scripts are ordered by their position in the processing cycle.

Nightly Script (nightly.sh) 4

The ITUAM Data Collectors for UNIX and Linux installation includes the sample_nightly.sh script. When you install ITUAM Data Collectors for UNIX and Linux, the sample_nightly.sh script is copied to create the nightly.sh script. Each time that you re-install ITUAM Data Collectors for UNIX and Linux or upgrade to a new release, the application searches for the nightly.sh script and recreates the script if it does not exist.

You need to set variable values in the nightly.sh script. If a new release of ITUAM Data Collectors for UNIX and Linux contains changes to the sample_nightly.sh script, you can incorporate those changes into the nightly.sh script that you have modified rather than replacing the script. If you replace the script, any existing variable values that you have set are overwritten.

The nightly.sh script performs the following tasks:

■ Calls the nightly.pl Perl script to begin processing.

■ Calls the mailx utility to send e-mail notification of successful, successful with warning, or failed processing.

The nightly.sh script must be scheduled to run on a regular basis. You can use any batch scheduler to run this script. It is recommended that you run the script using the ITUAM user account designated during the installation of ITUAM Data Collectors for UNIX and Linux.


■ Data Processing


Example

To schedule the nightly.sh script to run every morning at 4:15, the following crontab entry could be used:

15 4 * * * /usr/cims/scripts/nightly.sh PREDAY

Defining Variables in the nightly.sh Script

You need to define the following variables in the nightly.sh script:

Using the LogDate Parameter

The nightly.sh script requires the LogDate parameter. This parameter is used to select the files that are processed by ITUAM Data Collectors for UNIX and Linux.

The following are valid values for the LogDate parameter.

■ preday (previous day)

■ rndate (current day)

■ curday (current day and previous day)

■ date in yyyymmdd format

This parameter is entered in the command line when running the nightly.sh script.

MAIL_UTIL The name of the mail utility used to send mail messages on this computer. Usually mail or mailx.

MAIL_LIST A comma-separated list of e-mail recipients. For example, [email protected],[email protected],....


Data Processing ■


Nightly Job Script (nightly.pl) 4

Note • The nightly.pl script follows the same conventions as described for the nightly.sh script (see Nightly Script (nightly.sh) on page 4-13).

The nightly.pl script calls all jobs that you want to run. This script contains the Perl array @job_list, which defines the process definition jobs that will be executed. Jobs are called in the order that they appear in the list. You can add and remove jobs to and from this list.

The nightly.pl script requires the LogDate parameter, which is entered in the command line when running the nightly.sh script.

The nightly.pl script contains the stopOnProcessFailure parameter. If set to TRUE, the nightly process will stop if a failure is returned for a job. If set to FALSE, processing will continue to the next job defined in the @job_list array.

Processing Script (procCIMS.pl) 4

The procCIMS.pl script calls the CIMSAcct, CIMSBill, and CIMSLoad programs described in About ITUAM Processing Engine Programs on page 4-2.

The procCIMS.pl script also calls the CIMSSort subroutine that produces a sorted version of the CSR+ Output file created by CIMSAcct. This file is used as input into CIMSBill.

The procCIMS.pl script requires the parameters shown in the following table. These parameters are passed from the job script.


ProcessName The process definition directory that contains the XML control file for CIMSAcct, CIMSBill, and CIMSLoad.

XML_JobFile The control file for CIMSAcct, CIMSBill, and CIMSLoad. The default file name is ProcCntl.xml. This file contains the parameters used by the processing programs.

Table 4-3 • procCIMS Script Parameters


■ Data Processing



5Statistics

This chapter describes the UNIX, Oracle, and DB2 statistics processed by ITUAM Data Collectors for UNIX and Linux.

UNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

block_weeks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

cio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

connect_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

dio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

image_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

image_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

scpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

tcpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

ucpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

win_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle session CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle connect time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle UGA memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle PGA memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Oracle recursive CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle user commits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle physical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle physical writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle DB block gets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle disk sorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle messages sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Oracle messages received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7


■ Statistics

DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8

CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Buffer Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

I/O Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Table Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Unit of Work Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

SQL Statement Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Locks and Deadlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Sort Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9


Statistics ■

UNIX/Linux

UNIX/Linux 5

The following is a list of UNIX and Linux statistics processed by ITUAM Data Collectors for UNIX and Linux.

block_weeks 5

The block_weeks statistic is a space/time measurement to indicate the amount of utilization of the disk storage over time. Block week represents the use of a 512-byte block of storage for a one week period.

Given a starting time (date & time), an ending time, and the average number of blocks per day used by users and groups in the nightly storage files, the number of block weeks is computed as follows:

time_difference = ending_time - starting_time (days)

weeks = time_difference/7.0

block_weeks = average_blocks_per_day * weeks

The time_difference is dependent on the /SINCE and /BEFORE qualifiers used with the A_select utility. Therefore, the results are based on the period that you select when you consolidate data. The greater the selected period the better the reported block weeks.

The average_blocks_per_day is determined by the nightly storage samples taken by the A_sampler utility. This utility reports in 512-byte blocks that provides a consistent metric regardless of the operating system.

Exampleif A_select is run for a one-day period:

block_weeks = average_blocks_per_day * 1.0/7.0if A_select is run for a two-day period:

block_weeks = average_blocks_per_day * 2.0/7.0

Assume that a user has 70 blocks on the first day of the month and that disk usage never changes during the month. At the end of the first week, the user has 70 block weeks or 10 blocks weeks daily. At the end of the second week, the user has 140 block weeks. At the end of the four-week month, the user has 280 block weeks.

cio 5

The cio (Character I/O) statistic is the number of characters transferred (terminal I/O) by read/write. The cio statistic might not be available for some BSD-based systems. The cio statistic is maintained per process. ITUAM Data Collectors for UNIX and Linux reports cio in units of 100,000.


■ Statistics

UNIX/Linux

connect_time 5

The connect_time statistic indicates the amount of time the user is connected in a login session. The connect_time statistic is in units of hours. Connect time is the actual seat time or elapsed wall-clock time for a user. This means connect time does not amass when using window applications. Therefore, login time is not inflated. Window time (win_time) specifies the time spent in window applications.

dio 5

This dio (Disk I/O) statistic is the number of block reads/writes. The dio statistic is maintained per process. ITUAM Data Collectors for UNIX and Linux reports dio in units of 1,000.

image_time 5

The image_time statistic is the amount of time processes executed. ITUAM Data Collectors for UNIX and Linux reports image_time in units of hours.

image_count 5

The image_count statistic is the number of times a process was run.

logins 5

The login statistic is the number of login sessions that a person has connected to a system. A login is defined as:

■ Interactive logins

■ Project switches

■ CXbatch jobs (convex only)

■ NQS batch jobs

memory 5

The memory statistic indicates the approximate amount of virtual memory. Memory utilization is based on the resident portion of the memory segments. The value and algorithm of this statistic varies from one UNIX type to another. In general, virtual memory utilization is an approximation of the mean process size. Therefore, the amount of memory is determined for a process then adjusted according to the CPU time used by the process.


Statistics ■

UNIX/Linux

ExampleUnder HP-UX the process memory is determined by the following algorithm:

ac_mem = (data size) + (text size) +

(number of in-core processes sharing text) +

sum of ((shared memory segment size) /

(number of in-core processes attached to segment))

The virtual memory is determined by:

ac_mem/(ac_stime+ac_utime)

The units for memory utilization vary from platform to platform (for example, HP-UX: 1k block, SunOS: 1k bytes, IRIX: 4k page). Check acct in UNIX man pages on your system for the definition of this metric.

scpu 5

The scpu statistic is the CPU time spent in the system state. This includes time spent executing system calls, administrative functions on the program's behalf, device driver code, and any kernel code executed by the system. System CPU time can be controlled to some degree by the programmer, particularly in regard to I/O handling that uses extensive amounts of system services.

ITUAM Data Collectors for UNIX and Linux reports this metric in minutes.

tcpu 5

The tcpu statistic is the total of the scpu and ucpu statistics.

ucpu 5

The ucpu statistic is the amount of CPU time spent running a program in user state. This includes time spent executing library functions, but excludes time spent executing system calls.

ITUAM Data Collectors for UNIX and Linux reports this metric in minutes.

win_time 5

The win_time (Window time) statistic indicates the amount of time spent using a window application; win_time is the elapsed time for all window sessions during an interactive login session. The win_time statistic is in units of hours. Window time is specified for each window application.


■ Statistics

Oracle

Oracle 5

The following is the list of Oracle statistics gathered by ITUAM Data Collectors for UNIX and Linux.

Oracle logins 5

The Oracle logins statistic is the number of connections made to an Oracle instance.

Oracle session CPU 5

The Oracle session CPU statistic is the amount of CPU used in an Oracle session. ITUAM Data Collectors for UNIX and Linux reports this metric in minutes.

Oracle connect time 5

The Oracle connect time statistic is the amount of time a session is connected to Oracle. ITUAM Data Collectors for UNIX and Linux reports this metric in hours.

Oracle UGA memory 5

The Oracle UGA memory statistic is the amount of memory used in the User Global Area (UGA). UGA is memory used in multi-threaded server mode.

Oracle PGA memory 5

The Oracle PGA memory statistic is the amount of memory used in the Program Global Area or Process Global Area (PGA). PGA is a non-shareable and process specific memory region. One PGA is allocated for each process

When not in multi-threaded server mode, PGA contains process specific information such as stack, program variables, and so on. When running in multi-threaded server mode, only the stack information is stored in PGA and the other process information is stored in System Global Area (SGA).

The SGA is a shareable memory area for the database instance. All processes connected to Oracle (User and Oracle background) have access to the SGA. This is probably the most sensitive area of an instance. The following information is stored in the SGA:

■ Database buffer cache.

■ Redo log buffer.

■ Shred pool.

■ Request and response queues (multi-threaded server).

■ Data dictionary cache.

■ Other instance related info.


Statistics ■

Oracle

Oracle recursive CPU 5

The Oracle recursive CPU statistic is the amount of CPU used to update internal tables during Oracle recursive processing. Oracle performs recursive calls for the following operations:

■ Dynamic extension of segments.

■ Misses on the data dictionary cache.

■ Firing of database triggers.

■ Execution of DDL (Data Definition Language) statements.

■ Execution of SQL statements within stored procedures, functions, packages, and anonymous PL/SQL blocks.

■ Enforcement of referential integrity constraints.

Oracle user commits 5

The Oracle user commits statistic is the number of commits performed by the user.

Oracle physical reads 5

The Oracle physical reads statistic is the number of data blocks read from disk

Oracle physical writes 5

The Oracle physical writes statistic is the number of data blocks written to disk.

Oracle DB block gets 5

The Oracle DB block gets statistic is the number of times a CURRENT block was requested.

Oracle disk sorts 5

The Oracle disk sorts statistic is the number of sort operations that required at least one disk write.

Oracle messages sent 5

The Oracle messages sent statistic is the number of messages sent to background processes. This statistic reflects traffic between server and client processes.

Oracle messages received 5

The Oracle messages received statistic is the number of messages received from background processes. This statistic reflects traffic between server and client processes.


■ Statistics

DB2

DB2 5

The following is the list of IBM DB2 statistics gathered by ITUAM Data Collectors for UNIX and Linux.

CPU Usage 5

The CPU usage statistics provide the following:

■ User CPU time—the total user CPU time used by the database manager process.

■ System CPU time—the total system CPU time used by the database manager process.

Buffer Pool Activity 5

The buffer pool statistics provide the following:

■ Buffer pool data logical reads—the number of logical read requests for data pages that have gone through the buffer pool.

■ Buffer pool data physical reads—the number of read requests that required I/O to get data pages into the buffer pool.

■ Buffer pool data writes—the number of times a buffer pool data page was physically written to disk.

■ Buffer pool index logical reads—the number of logical read requests for index pages that have gone through the buffer pool.

■ Buffer pool index physical reads—the number of physical read requests to get index pages into the buffer pool.

■ Buffer pool index writes—the number of times a buffer pool index page was physically written to disk.

I/O Activity 5

The I/O activity statistics provide the following:

■ Direct reads—the number of read operations that do not use the buffer pool.

■ Direct writes—the number of write operations that do not use the buffer pool.

These statistics are not available for DB2 PE.


Statistics ■

DB2

Table Activity 5

The Table Activity statistic provides the following:

■ Rows deleted—the number of row deletion operations attempted.

■ Rows inserted—the number of row insertion operations attempted.

■ Rows updated—the number of row update operations attempted.

■ Rows selected—the number of rows selected and returned to the application.

Unit of Work Status 5

The Unit of Work Status statistic provides the following:

■ Unit of work log space used—the amount of log space (in bytes) used in the current unit of work of the monitored application.

SQL Statement Activity 5

The SQL Statement Activity statistic provides the following:

■ Commit statements attempted—the total number of SQL commit statements that have been attempted.

■ Rollback statements attempted—the total number of SQL rollback statements that have been attempted.

■ Internal rollbacks due to deadlock—the total number of rollbacks initiated by the database manager due to a deadlock. The rollback is performed on the current unit of work in an application selected by the database manager to resolve the deadlock.

Locks and Deadlocks 5

The LOCKS and Deadlocks statistic provides the following:

■ Time waited on locks—the total elapsed time waited for a lock.

■ Deadlocks detected—the total number of deadlocks that have occurred.

Sort Work 5

The Sort Work statistic provides the following:

■ Total sorts—the total number of sorts that have been executed.

Sort overflows—the total number of sorts that ran out of sort heap and might have required disk space for temporary storage.


■ Statistics

DB2


ADirectories, Files, and Scripts

This appendix describes the ITUAM Data Collectors for UNIX and Linux directory structure and provides a description of the files and scripts in the ITUAM directories. In some cases, these files and scripts are described in detail in other chapters of this guide by the context in which they are used. Where applicable, references to other chapters and sections are included in the file or script description.

$ITUAM_HOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

bin directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

collectors Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

config Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

jlib Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

lib/CIMS_Lib Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

LogFiles Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

sample_processes and processes Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

scripts Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

$ITUAM_UC_HOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-9

accounting Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

bin Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

CS_input_source Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

data Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

etc Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-14

help Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-15

history Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

log Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

scripts Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide A-1 ■

■ Directories, Files, and Scripts

$ITUAM_HOME Directory

$ITUAM_HOME Directory A

The directories within $ITUAM_HOME directory are as follows.

bin directory A

This directory contains the ITUAM Processing Engine Administrator program (ITUAMAdmin.jar). This program enables ITUAM Processing Engine to connect to the ITUAM database or databases. This program is described in detail in the IBM Tivoli Usage and Accounting Manager Administrator’s Guide.

bin This directory contains the ITUAM Processing Engine Administrator program (ITUAMAdmin.jar).

CollectorLogs This directory contains usage metering files produced by ITUAM Data Collectors for UNIX and Linux.

collectors This directory contains files and scripts required by ITUAM Data Collectors for UNIX and Linux.

config This directory contains configuration files used to connect to the ITUAM database and to process data.

jlib This directory contains ITUAM Processing Engine JAR files.

lib/CIMS_lib This directory contains Perl modules used by the ITUAM Data Collectors for UNIX and Linux job and conversion scripts.

LogFiles This directory contains log files that contain the results of each job that you ran by day.

processes and sample_processes

This directory contains process definitions. When you install ITUAM Data Collectors for UNIX and Linux, the sample_processes directory and all of its contents are copied to the processes directory.

scripts This directory contains the scripts that process data and load it into the ITUAM database.

■ A-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Directories, Files, and Scripts ■


collectors Directory A

Unix Directory

This directory contains the files and scripts used by the data collectors in the Collector Base Package and the Collectors Packge for Databases.

Individual Collector Directories

These directories contain the files and scripts required by the data collectors in collector packages other than the Collector Base Package and the Collectors Packge for Databases.

UnixLinux Directory

This directory contains the deployment manifest and installation files required to install the Collector Base Package and the Collectors Packge for Databases on multiple servers from a central location (see Installing ITUAM Data Collectors for UNIX and Linux Remotely on page 1-13).

The ITUAM Data Collectors for UNIX and Linux installation files are uuencoded, compressed tar files specific to the supported UNIX or Linux platforms.




Operating System and File System Deployment Manifest Files

DeploymentManifest_aix5.xml Manifest for AIX 5.x platforms. This manifest points to the installation file ituam_uc_aix5.tar.

DeploymentManifest_hp.xml Manifest for HP-UX 9000/x platforms running HP-UX 11, 11i, or 11.23. This manifest points to the installation file ituam_uc_hp.tar.

DeploymentManifest_hpia.xml Manifest for HP-UX ia64 platforms running HP-UX 11.23 Itanium. This manifest points to the installation file ituam_uc_hpia.tar.

DeploymentManifest_sol127.xml Manifest for Sun-based systems running Solaris 7, 8, 9, or 10. This manifest points to the installation file ituam_uc_sol127.tar.

DeploymentManifest_linux.xml Manifest for x86 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10. This manifest points to the installation file ituam_uc_linux.tar.

DeploymentManifest_linx86_64.xml Manifest for x86 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9. This manifest points to the installation file ituam_uc_linx86_64.tar.

DeploymentManifest_lin390.xml Manifest for S390 31-bit Linux platforms running RHEL 3, RHEL 4, SLES 8, or SLES 9. This manifest points to the installation file ituam_uc_linx86_64.tar.

DeploymentManifest_lin390x.xml Manifest for S390 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9. This manifest points to the installation file ituam_uc_lin390x.tar.

DeploymentManifest_linppc64.xml Manifest for ppc64 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10. This manifest points to the installation file ituam_uc_linppc64.tar.

DeploymentManifest_linia64.xml Manifest for Itanium 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9. This manifest points to the installation file ituam_uc_linppc64.tar.




Database Collector Deployment Manifest Files

DeploymentManifest_aix5_dblibs.xml Manifest for AIX 5.x platforms. This manifest points to the installation file ituam_uc_dlibs_aix5_.tar.

DeploymentManifest_hp_dblibs.xml Manifest for HP-UX 9000/x platforms running HP-UX 11, 11i, or 11.23. This manifest points to the installation file ituam_uc_dlibs_hp_.tar.

DeploymentManifest_hpia_dblibs.xml Manifest for HP-UX ia64 platforms running HP-UX 11.23 Itanium. This manifest points to the installation file ituam_dlibs_hpia.tar.

DeploymentManifest_sol127_dblibs.xml

Manifest for Sun-based systems running Solaris 7, 8, 9, or 10. This manifest points to the installation file ituam_uc_dlibs_sol127.tar.

DeploymentManifest_linux_dblibs.xml Manifest for x86 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10. This manifest points to the installation file ituam_uc__dlibs_linux.tar.

DeploymentManifest_linx86_64_dblibs.xml

Manifest for x86 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9. This manifest points to the installation file ituam_uc__dlibs_linx86_64.tar.

DeploymentManifest_lin390_dblibs.xml

Manifest for S390 31-bit Linux platforms running RHEL 3, RHEL 4, SLES 8, or SLES 9. This manifest points to the installation file ituam_uc__dlibs_lin390.tar.

DeploymentManifest_lin390x_dblibs.xml

Manifest for S390 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9. This manifest points to the installation file ituam_uc__dlibs_lin390x.tar.

DeploymentManifest_linppc64_dblibs.tar

Manifest for ppc64 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10. This manifest points to the installation file ituam_uc__dlibs_linppc64.tar.

DeploymentManifest_linia64_dblibs.tar

Manifest for Itanium 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9. This manifest points to the installation file ituam_uc__dlibs_linia64.tar.




Operating System and File System Collector Remote Installation Files

v601_unpack_tar Contains the remote installation script.

ituam_uc_aix5.tar Distribution for AIX 5.x platforms.

ituam_uc_hp.tar Distribution for HP-UX 9000/x platforms runningHP-UX 11, 11i, or 11.23.

ituam_uc_hpia.tar Distribution for HP-UX platforms runningHP-UX 11.23 Itanium.

ituam_uc_sol127.tar Distribution for Sun-based systems running Solaris 7, 8, 9, or 10.

ituam_uc_linux.tar Distribution for x86 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10.

ituam_uc_linx86_64.tar Distribution for x86 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9.

ituam_uc_lin390.tar Distribution for S390 31-bit Linux platforms running RHEL 3, RHEL 4, SLES 8, or SLES 9.

ituam_uc_lin390x.tar Distribution for S390 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9.

ituam_uc_linppc64.tar Distribution for ppc64 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10.

ituam_uc_linia64.tar Distribution for Itanium 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9.




Database Collector Remote Installation Files

Note • The operating system and file system data collectors must be installed on the target system before you install the database collectors.

config Directory A

This directory contains the following configuration files used to connect to the ITUAM database and process data. These files are described in detail IBM Tivoli Usage and Accounting Manager Administrator’s Guide.

jlib Directory A

This directory contains the JAR files for the ITUAM Processing Engine programs described in About Processing Data on page 3-3.

v601_unpack_dlibs_tar Contains the remote installation script.

ituam_uc_dlibs_aix5_.tar Distribution for AIX 5.x platforms.

ituam_uc_dlibs_hp_.tar Distribution for HP-UX 9000/x platforms runningHP-UX 11, 11i, or 11.23.

ituam_uc_dlibs_hpia.tar Distribution for HP-UX platforms runningHP-UX 11.23 Itanium.

ituam_uc_dlibs_sol127.tar Distribution for Sun-based systems running Solaris 7, 8, 9, or 10.

ituam_uc__dlibs_linux.tar Distribution for x86 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10.

ituam_uc__dlibs_linx86_64.tar Distribution for x86 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9.

ituam_uc__dlibs_lin390.tar Distribution for S390 31-bit Linux platforms running RHEL 3, RHEL 4, SLES 8, or SLES 9.

ituam_uc__dlibs_lin390x.tar Distribution for S390 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9.

ituam_uc__dlibs_linppc64.tar Distribution for ppc64 Linux platforms running RHEL 3, RHEL 4, SLES 9, or SLES 10.

ituam_uc__dlibs_linia64.tar Distribution for Itanium 64-bit Linux platforms running RHEL 3, RHEL 4, or SLES 9.

CIMSDBConfig.xml This file contains the parameters needed to connect to one or more databases within your organization.

cims.par This file contains the parameters needed to run CIMS Processing Engine.




lib/CIMS_Lib Directory) A

This directory contains the following Perl modules used by the ITUAM Data Collectors for UNIX and Linux job and conversion scripts:

LogFiles Directory A

This directory contains log files that contain the results of each job that you ran by day. If a warning or failure occurs during processing, the file indicates at which point the warning/failure occurred. For more information about this directory, see LogFiles Directory on page 4-13.

sample_processes and processes Directories A

The sample_processes directory contains process definitions. A process definition is a directory that contains the files required to process usage data from a particular source such as a database, operating system, or application.

When you install ITUAM Data Collectors for UNIX and Linux, the sample_processes directory and all of its contents are copied to the processes directory. Each time that you re-install ITUAM Data Collectors for UNIX and Linux or upgrade to a new release, the application searches for the processes directory and recreates the directory if it does not exist.

For more information about the sample_processes and processes directory, see processes Directory on page 4-9.

scripts Directory A

This directory contains the scripts that process data and load it into the ITUAM database. These scripts are described in Processing Data: Setting Up the Data Processing Scripts on page 4-13.

$ITUAM_HOME/lib/CIMS_lib/CS_libs.pm

This module contains subroutines that validate arguments, search directories, scan files, and perform other operational tasks required by job and conversion scripts.

$ITUAM_HOME/lib/CIMS_lib/CS_aggtools.pm

This module contains the subroutines and objects used to support the ITUAM Perl Aggregation Engine.



$ITUAM_UC_HOME Directory

$ITUAM_UC_HOME Directory A

The directories within $ITUAM_UC_HOME directory are as follows.

accounting Directory A

The accounting directory contains a subdirectory for each node that performs data collection. If you are using the same server for data collection and consolidation, there is only one node subdirectory.

The node subdirectory or subdirectories in the accounting directory contains the nightly accounting and storage files from the node of the same name. The nightly accounting and storage files are named acc_<date>.dat and str_<date>.dat, respectively.

The location of the accounting directory is defined by the ITUAM_ACCDAT variable in the $ITUAM_UC_HOME/data/config.par file.If you have enabled Oracle or DB2 storage collection, the accounting directory will also contain the nightly database storage file: ora_sto_<date>.dat or db2_sto_<date>.dat.

accounting Contains the nightly accounting and storage files.

bin Contains utilities and libraries.

CS_input_source Contains the CSR files created by the data consolidation process.

data Contains data files needed to maintain and administer ITUAM Data Collectors for UNIX and Linux.

description Contains the description files for data extraction.

etc Contains scripts needed to maintain and administer ITUAM Data Collectors for UNIX and Linux.

examples Contains miscellaneous information that includes A_gui and A_graph resource files.

help Contains the ITUAM Data Collectors for UNIX and Linux on-line help files.

history Contains historical raw UNIX and ITUAM accounting files.

log Contains log files created by various utilities and scripts.

scripts Contains various scripts grouped by function in subdirectories, including the scripts used to integrate ITUAM Data Collectors for UNIX and Linux with ITUAM.




bin Directory A

The bin directory contains the following:

■ Binaries of the ITUAM Data Collectors for UNIX and Linux utilities described in Appendix B, Utilities.

■ Object libraries needed to build the ITUAM Oracle and DB2 Accounting utilities.

Note • All of the files in the bin directory are mandatory and cannot be deleted.

The location of the bin directory is defined by the ITUAM_BIN variable in the $ITUAM_UC_HOME/data/A_config.par file.

Oracle Libraries

The ITUAM Oracle libraries libdbao.a and libdbso.a build the ITUAM Oracle utilities A_dbao and A_dbso, respectively. If you do not use Oracle and do not plan on using Oracle, you can delete these libraries.

DB2 Libraries

The ITUAM DB2 libraries libdbadb2.a and libdbsdb2.a build the ITUAM DB2 utilities A_dbadb2 and A_dbsdb2, respectively. If you do not use DB2 and do not plan on using DB2, you can delete these libraries.

CS_input_source Directory A

The CS_input_source directory contains the output CSR files produced by the data consolidation process. For more information about the types of CSR files produced and the methods for transferring the CSR files to ITUAM, see Chapter 3, Data Collection and Consolidation.

The CS_input_source directory is created the first time that the CS_nightly_ consolidation script is run.

data Directory A

The data directory is an important directory. This directory contains the data files needed to operate ITUAM Data Collectors for UNIX and Linux.

The location of the data directory is set using the ITUAM_DATA variable in the A_config.par file.

Files that end with .sys are formatted files and can be modified only using ITUAM Data Collectors for UNIX and Linux utilities.

Files that end with .dat are processed files created by ITUAM Data Collectors for UNIX and Linux utilities.

Files that end with .par are text files that you can modify using a text editor such as vi.




.sys Files

Activity File (A_activity.sys)The A_activity.sys file contains ITUAM login/logout and switch records that are used to support the project accounting feature. The A_activity.sys file is a mandatory file and cannot be deleted.

The A_login and A_switch utilities write records to the A_activity.sys file. These records contain the following information:

■ UID

■ GID

■ Time the user logged in or switched projects.

■ New project name.

■ Terminal name.

ITUAM Oracle and DB2 Files (A_db*.sys) (Optional)Files that begin with A_db (see the following) are optional and are produced by the ITUAM Oracle or DB2 Database Accounting daemons as described in Oracle Data Collection—Post-Installation Setup on page 1-43 or .DB2 Data Collection—Post-Installation Setup on page 1-50 These files should never be edited with a text editor.

Holiday File (A_holiday.sys)The A_holiday.sys file contains the dates that you want to consider holidays. The options and parameters in this file are required only if you want to designate holidays as a different shift.

This file is created and maintained by the A_setup utility. This is a mandatory file and cannot be deleted.

A_dbacct.sys The ITUAM Oracle Accounting daemon (A_dbao) adds a record to this file each time the daemon detects that a user has disconnected from a database instance or at designated intervals.

A_db2acct.sys The ITUAM DB2 Accounting daemon (A_dbadb2) adds a record to this file each time the daemon detects that a user has disconnected from a database instance or at designated intervals.

A_dbinst.sys This file is managed by the A_setup utility and contains information used by ITUAM Database Accounting daemons when they connect to the database.

A_dbpid.sys This file is managed by the A_dbpidman utility and contains the PID number of all currently running ITUAM Database Accounting daemons.




Image Mapping File (A_imgmap.sys)The A_imgmap.sys file contains the names of images that you want to track and package names for the images.


Login Projects File (A_lgiproj.sys)The A_lgiproj.sys file is created by the A_format utility. This file records the date/time, node name, user name, and project name for each entry detected in the most recently processed A_activity.sys file. This optional file is for internal use only and should not be modified.

Oracle Basename File (A_odb_base.sys)The A_odb_base.sys file is created by the A_setup utility and maintained by the A_select utility. The file contains a record for each Oracle instance being tracked by the ITUAM Oracle Accounting daemons. This file should not be modified.

Oracle Username File (A_odb_user.sys)The A_odb_user.sys file is created by the A_setup utility and maintained by the A_select utility. The file contains a record for each Oracle user name detected by the A_select utility while processing the ITUAM Oracle Accounting file. This file should not be modified.

Process Statistics File (A_procstat.sys)The A_procstat.sys file is created by the A_format utility. This is a mandatory file for producing the nightly accounting file, but can be deleted after the nightly accounting file has been created.

Queue Mapping File (A_queuemap.sys)The A_queuemap.sys contains a list of batch and print queue names.


Parameter File (A_setup.sys)The A_setup.sys file contains system-wide flags and parameters that define your configuration. The file is created and maintained by the A_setup utility.

Intermediate Statistics File (A_stat.sys)The A_stat.sys file is created by the A_select utility as a result of processing the nightly accounting files. This file is then input to A_merge utility to produce the Merged Statistics file (A_stat.dat).

Storage File (A_storage.sys)The A_storage.sys contains file system usage collected and logged by the A_sampler utility. This file is copied into a daily storage file (str_<date>.dat) by the sampler script.

Terminal Parameter File (A_term_par.sys)The A_term_par.sys file contains terminal names, groups, and factor values. This is a mandatory file and cannot be deleted.




Authorization File (A_uaf.sys)The A_uaf.sys file contains flags, parameters, and values pertaining to user and project accounts. This file is created and maintained by the A_authorize utility.

Validation File (A_validate.sys)The A_validate.sys file contains user and project name associations used to implement the user/project validation method.

It is a mandatory file for the user/project validation method.

wtmp Statistics File (A_wtmpstat.sys) The A_wtmpstat.sys file is created by the A_format utility. This is one of several files used to create the nightly accounting file.

.dat Files

Merged Statistics File (A_stat.dat) The A_stat.dat file is created by the A_merge utility as a result of processing the following files: A_stat.sys, A_uaf.sys, and nightly storage files.

This file is mandatory for producing CSR files, but can be deleted after the CSR files have been created.

.par Files

Parameter Configuration File (A_config.par)The A_config.par file provides a common configuration file that is used by the ITUAM Data Collectors for UNIX and Linux scripts to set up your enterprise environment. The file is commented and organized by the stages in the data collection process.

ITUAM Data Collectors for UNIX and Linux sets the initial variable values in the A_config.par file during installation. However, you can modify these values as needed using a text editor.

For more information about the A_config.par file, see page 1-31.

Node Parameter File (A_node.par)The A_node.par file contains one entry for the node on which the file is installed. For example, if the file is installed on the server zeus, then the node entry in the file is zeus.

Storage Parameter File (A_storage.par)The A_storage.par file contains a list of file systems monitored by ITUAM Data Collectors for UNIX and Linux. This is a required file for the Sampler utility to operate correctly and should not be deleted when you are doing storage sampling.

If the variable ITUAM_DYNAMIC_STORAGE_PAR is set to Y in the A_config.par file, a new A_storage.par file is created each night when the sampler script is called by the ituam_uc_nightly script. This ensures that if any changes have been made to the file systems, the changes will be automatically reflected in the nightly sample.




Collapsible Terminal File (A_terminals.par)The A_terminals.par file contains a list of terminal names that are collapsed by the A_select utility when the TERMINAL_BY_USER option is enabled. The following is the default list of terminal names:

ftp

X:

1tu

Xty

ptm

uucp

NT:

tty

pts

Any terminal name that begins with one of the names on this list is truncated to the list name. For example, the first terminal name, ftp, specifies that all terminal names starting with ftp (for example, ftp1256) are collapsed to simply ftp.

This is a mandatory file and cannot be deleted.

etc Directory A

The etc directory contains scripts used to maintain and operate ITUAM Data Collectors for UNIX and Linux.

The location of the etc directory is set using the ITUAM_ETC variable in the $ITUAM_UC_HOME/data/config.par file.

Date Script

The ituam_date.awk script handles all date calculations used by ITUAM Data Collectors for UNIX and Linux scripts.

Environment Script (ituam_env)

The ituam_env script sets up the ITUAM Data Collectors for UNIX and Linux environment using values in the $ITUAM_UC_HOME/data/A_config.par file.

UNIX Platform Script (ituam_platform)

The ituam_platform script sets up the proper environment variables specific to individual UNIX/Linux platform types supported by ITUAM Data Collectors for UNIX and Linux.

Check Pacct Script (check_pacct)

The check_pacct script checks the size of the pacct file and maintains the size below a user specified limit. When the pacct file exceeds the specified limit, this script places the current pacct file in a holding area in the history directory and re-initializes the live pacct file.




By default, the pacct file is allowed to grow to 2 MB before being re-initialized. This value can be changed by modifying the value for pacct_max_size in the check_pacct script.

For more information about the check_pacct script, see page 3-3.

Nightly Accounting Script (ituam_uc_nightly)

The ituam_uc_nightly script handles all of the steps in the data collection process, including calling the turnacct, runacct, and sampler, scripts used for data collection.

For more information about the ituam_uc_nightly script, see page 3-4.

Turn Accounting Script (turnacct)

The turnacct script moves the raw UNIX and ITUAM accounting files into the history directory and prepares the files to be formatted by the runacct script.

For more information about the turnacct script, see page 3-5.

Runacct Script (runacct)

The runacct script calls the A_format utility to sort and format the raw UNIX and ITUAM accounting records into one nightly accounting file.

For more information about the runacct script, see page 3-6.

Sampler Script (sampler)

The sampler script calls the A_sample utility to gather data from the UNIX/Linux file system and produce the nightly storage file.

For more information about the sampler script, see page 3-7.

Redo Nightly Script

If the ituam_uc_nightly script fails, use the redo_nightly script to reprocesses the raw Unix and ITUAM accounting files in the history directory.

For more information about the redo_nightly script, see page 3-8.

help Directory A

The help directory contains the ITUAM Data Collectors for UNIX and Linux on-line help files. The location of the help directory is set using the ITUAM_HELP variable in the $ITUAM_UC_HOME/data/config.par file.




history Directory A

The history directory contains historical raw UNIX and ITUAM accounting files. These files include the pacct and wtmp, A_dbacct.sys, and A_db2acct.sys files. Once the information in these files has been formatted into the nightly accounting file, the raw accounting files can be removed. It is recommended that these files are saved until the nightly accounting files have been consolidated in case you need to recreate a particular accounting file.

The location of the history directory is set using the ITUAM_HISTORY variable in the $ITUAM_UC_HOME/data/config.par file.

log Directory A

The log directory is a repository for log files created by various ITUAM Data Collectors for UNIX and Linux utilities and scripts. The location of the log directory is set using the ITUAM_LOG variable in the $ITUAM_UC_HOME/data/config.par file.

scripts Directory A

The scripts directory contains scripts that are organized by function in the following subdirectories:

The location of the scripts directory is set using the ITUAM_SCRIPTS variable in the $ITUAM_UC_HOME/data/config.par file.

admin Contains scripts that assist you in administering ITUAM Data Collectors for UNIX and Linux.

db2 and oracle Contains DB2 and Oracle setup scripts that your DBA should use to set up the roles and tables needed for ITUAM DB2 and Oracle utilities.

This subdirectoy also contains scripts that manage the ITUAM Oracle or DB2 Accounting daemons. These scripts start, stop, and check the status of all or individual accounting daemons. For more information about these database accounting scripts, see Using Database Accounting Scripts to Start, Stop, and Check ITUAM Oracle Daemons on page 1-46 or Using Database Accounting Scripts to Start, Stop, and Check ITUAM DB2 Daemons on page 1-53.

enterprise Contains the operational scripts used to consolidate and send data to the ITUAM system. These scripts are described in the section Consolidating Data: Setting Up the Data Consolidation Scripts beginning on page 3-9.


BUtilities

This appendix describes the ITUAM Data Collectors for UNIX and Linux utilities, which are located in the $ITUAM_UC_HOME/bin directory.

Using the Command Line Interface (CLI) to Access Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Using the HELP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Authorize Utility (A_authorize) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Convert Utility (A_convert) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Database Utilities (A_db*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

ITUAM Oracle Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

ITUAM DB2 Accounting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

ITUAM Database Accounting Utilities for Oracle and DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Format Utility (A_format) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6

Merge Utility (A_merge) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

Merge Utility MERGE Command and Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

Sampler Utility (A_sampler) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

Select Utility (A_select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

Select Utility Commands and Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

Setup Utility (A_setup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10

File System Resource Utility (CS_fs_resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide B-1 ■

■ Utilities

Using the Command Line Interface (CLI) to Access Utilities

Using the Command Line Interface (CLI) to Access Utilities B

The CLI enables you to access the following utilities:

■ Authorize (A_authorize)

■ Format (A_format)

■ Merge (A_merge)

■ Select (A_select)

■ Setup (A_setup)

■ License (G_license)

Other utilities do not use the CLI and are invoked from the ITUAM Data Collectors for UNIX and Linux scripts.

The CLI for each of the utilities in the preceding list provides a prompt with the appropriate utility name. For example, the prompt for the A_setup utility is A_SETUP>. To run the utility, type a command followed by qualifiers associated with the command at the prompt. For example, the following command and qualifier display database instance settings in the A_setup utility:

# A_setupA_SETUP> REP/DBINST

Shell scripts may also invoke the CLI by calling the utility and passing commands and qualifiers in a quoted string as an argument to the call. For example:

$ITUAM_UC_HOME/bin/A_setup "REP/DBINST"

Using the HELP Command B

To view the commands and qualifiers for a utility, type the HELP command at the prompt for the utility. For example, the following enables you to view descriptions of the commands and qualifiers for the A_setup utility:

# A_setupA_SETUP> HELP

■ B-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Utilities ■

Authorize Utility (A_authorize)

Authorize Utility (A_authorize) B

The A_authorize utility enables the ITUAM administrator to initialize, modify, and examine user and project parameters, options, and validation combinations. These parameters and options are used when the project accounting feature is enabled. The A_authorize utility provides a means of managing user and project accounts, including the default accounts. This utility creates and maintains the Authorization file (A_uaf.sys) and Validation file (A_validate.sys).

Several utilities access the A_uaf.sys and A_validate.sys files. Changes to these files take effect the next time a utility reads the files.

Convert Utility (A_convert) B

The A_convert utility is used when you upgrade from an earlier release of ITUAM Data Collectors for UNIX and Linux. This utility is called to update the individual ITUAM files.

The A_convert utility can also be used to display the current version of the following files in the data directory:

# A_convert%CONVERT-I-FILUTD, A_setup.sys is up to date.%CONVERT-I-PRODVER, converting collector data files to V5%CONVERT-I-FILUTD, A_uaf.sys is up to date.%CONVERT-I-FILUTD, A_validate.sys is up to date.%CONVERT-I-FILUTD, A_rates.sys is up to date.%CONVERT-I-FILUTD, A_term_par.sys is up to date.%CONVERT-I-CNVTDONE, A_convert completed


■ Utilities

Database Utilities (A_db*)

Database Utilities (A_db*) B

The utilities that have file names beginning with A_db are used to perform database accounting.

ITUAM Oracle Accounting Utilities B

The utilities in Table B-1 are used for ITUAM Oracle accounting.

For more information about the use of these utilities, see Oracle Data Collection—Post-Installation Setup on page 1-43.

Script Description

A_dbao.<Oracle version> The ITUAM Oracle Accounting daemon (A_dbao.<version>) is used to track usage within an Oracle instance. For example, the daemon executable for a version 9.0.1 Oracle instance would be A_dbao.V9.0.1.

A soft link named A_dbao is in the $ORACLE_HOME/bin directory of the instance.

A_dbso.<Oracle version> The ITUAM Oracle Storage utility (A_dbso.<version>) is used to gather a nightly sample of datafile and data object storage usage within an Oracle instance. For example, the storage utility for a version 9.0.1 Oracle instance would be A_dbso.V9.0.1.

A soft link named A_dbso is in the $ORACLE_HOME/bin directory of the instance.

Table B-1 • ITUAM Oracle Accounting Utilities


Utilities ■

Database Utilities (A_db*)

ITUAM DB2 Accounting Utilities B

The utilities in Table B-2 are used for ITUAM DB2 Accounting.

For more information about the use of these utilities, see DB2 Data Collection—Post-Installation Setup on page 1-50.

ITUAM Database Accounting Utilities for Oracle and DB2 B

The utilities in Table B-3 are used for both ITUAM Oracle and DB2 Accounting.

Script Description

A_dbadb2_<DB2 version> The ITUAM DB2 Accounting daemon (A_dbadb2.<version>) used to track usage within a DB2 instance. For example, the daemon executable for a version 8.1 DB2 instance would be A_dbadb2_v8.

A_dbsdb2_<DB2 version> The ITUAM DB2 Storage utility (A_dbsdb2.<version>) is used to gather a nightly sample of tablespace storage usage within a DB2 instance. For example, the storage utility for a version 8.1 DB2 instance would be A_dbsdb2_v8.

Table B-2 • ITUAM DB2 Accounting Utilities

Script Description

A_dbpidman The A_dbpidman utility is used to display and maintain the PID numbers of active ITUAM Database Accounting daemons. When a daemon starts, its PID number is recorded in the A_dbpid.sys file. This prevents multiple daemons from being run against the same instance.

If a daemon process ends unexpectedly, this utility can be used to remove the PID number from the A_dbpid.sys file before the daemon is restarted.

A_dbsdb_read The A_dbsdb_read utility is used to read the A_dbstorage.sys file and generate CSR records containing database storage usage. The ITUAM Oracle and DB2 Storage utilities write a sample to the A_dbstorage.sys file and the A_dbsdb_read utility extracts the data in CSR format.

Table B-3 • ITUAM Database Accounting Utilities (Oracle and DB2)


■ Utilities

Format Utility (A_format)

Format Utility (A_format) B

The A_format utility is called by the runacct script as part of the data collection process. This utility formats the following raw UNIX and ITUAM accounting files into temporary accounting files as shown in Table 2-4. The temporary accounting files are sorted together to produce a nightly accounting file.

Raw Accounting File Temporary Accounting File

pacct A_procstat.sys

wtmp/wtmpx/wtmps A_wtmpstat.sys

prtacct A_printstat.sys

A_dbacct.sys) A_dbstat.sys

A_db2acct.sys A_dbstat.sys

A_activity.sys A_lgistat.sys

Table 2-4 • Accounting Files and Correlating Temporary Accounting Files


Utilities ■

Merge Utility (A_merge)

Merge Utility (A_merge) B

The A_merge utility merges the nightly accounting files (acc_<date>.dat) with information from the Authorization file (A_uaf.sys) and the nightly Storage files (str_<date>.dat). The output file is the Merged Statistics file (A_stat.dat). The A_stat.dat file is then used by the CS_gen_sum script to generate CSR files.

This utility is called by the proc_multi script as part of the data consolidation process or can be invoked interactively after the A_select utility has produced the Intermediate Statistics file (A_stat.sys).

The files that the A_merge utility reads must be located in the $ITUAM_UC_HOME/data directory. If the files are not stored in the data directory, the files must be copied or linked to the directory before running the A_merge utility. If the A_merge utility is called from the proc_multi script, the script automatically links nightly accounting and storage files to the data directory.

Merge Utility MERGE Command and Qualifiers B

The A_merge utility has only one command: MERGE. This command has the following qualifiers that affect how the MERGE command runs, but do not affect the data itself.

Sampler Utility (A_sampler) B

The A_sampler utility scans specified file systems and logs storage usage information in the A_storage.sys file. This utility samples all file systems that have an entry in the Storage Parameter file ($ITUAM/collectors/Unix/data/A_storage.par).

This utility is called by the sampler script as part of the data collection process.

/STATISTICS This qualifier outputs resource statistics that show how much CPU time, elapsed time, I/O, etc., the MERGE command itself used. This option is valid only on certain UNIX platforms.

/VERBOSE This qualifier causes the A_merge utility to output more detailed messages for debugging and troubleshooting purposes.


■ Utilities

Select Utility (A_select)

Select Utility (A_select) B

The A_select utility processes the nightly accounting files (acc_<date>.dat) for inclusion in the Merged Statistics file (A_stat.dat). This utility is called by the proc_multi script as part of the data consolidation process.

If you have mapped process names to software packages in the Image Mapping file (A_imgmap file), each time the A_select utility encounters one of these processes in the accounting files, it adds the statistics associated with the image/process to a package record as well as a background or interactive record in the Intermediate Statistics file (A_stat.sys).

The A_select utility can work cumulatively. If you do not use the /ZERO qualifier (see page B-9), you can allow the A_select utility to add data to the existing data in the A_stat.sys file.

You can also remove the A_stat.sys file so that the A_select utility creates a new file as it begins consolidating the data for a new reporting period.

The acc_<date>.dat file that the A_select utility reads must be located in the data directory. If the files are not stored in the data directory, the files must be copied or linked to the directory before running the A_select utility. If the A_select utility is called from the proc_multi script, the script automatically links the necessary files to the data directory.

Select Utility Commands and Qualifiers B

The A_select utility has three commands, plus several qualifiers, that dictate how the data is processed.

The commands are:

If you are using a combination of the commands at one time, the SELECT command should come first followed by the AUDIT and CAPACITY commands delimited by a forward slash. Examples of how the command should be input are as follows.

A_SELECT> SELECT ...A_SELECT> AUDIT/CAPACITY ...A_SELECT> SELECT/AUDIT/CAPACITY ...

SELECT This is the most commonly used command. This command produces the A_stat.sys file.

AUDIT The AUDIT command produces the Audit Statistics file (A_audit.dat). This file contains session audit information and is used by the A_report utility.

CAPACITY The CAPACITY command produces the Capacity Statistics file (A_cap.sys). This file contains node utilization information and is used by the A_report utility.


Utilities ■

Select Utility (A_select)

The command is then followed by additional qualifiers in the following order.

/SINCE and /BEFORE These qualifiers set the data accounting period. The accounting period is one of the most important things to decide before processing the data. The accounting period you select can depend on any number of factors: such as company policies, government regulations, financial requirements, and so forth. The accounting period can range from daily to weekly to monthly.

The accounting period is defined by a starting date and an ending date. The starting date is defined using the /SINCE qualifier. The ending date is defined using the /BEFORE qualifier. For example, you might want a starting date of 1-mar-2006 and an end date of 1-apr-2006. Note that neither date includes a time. The time is always assumed to be 00:00. Thus, this reporting period goes from 00:00 on the first of March to 00:00 on the first of April and includes all the time in March.

/NODE This qualifier indicates the node name where the data that is currently being processed originated. The node name is included in the A_stat.sys file.

/ZERO (Optional) The /ZERO qualifier is used to zero out all the resource statistics previously stored in the A_stat.sys file from a prior run of the SELECT command. Records that already exist in the A_stat.sys file are not deleted; however, the statistics in the records are set to zero.

You can use this qualifier if you are using the SELECT command to process the accounting data for several nodes, and one node's processing does not complete correctly. This qualifier is used to zero out the bad statistics for only that node’s records before reprocessing the node's data. This way you do not have to remove the statistics file and reprocess all nodes.

If you are creating monthly reports, you should remove the A_stat.sys file for last month prior to processing for the current month instead of using the /ZERO qualifier. If you continue to use the /ZERO qualifier from month to month, records for users that are no longer accessing your systems are retained until the A_stat.sys file is removed.

/ADD_ACCOUNTS(Optional)

The /ADD_ACCOUNTS qualifier can be used to add users and projects found in the accounting data to the uaf.sys file. By default, users and projects are not added by SELECT. If /ADD_ACCOUNTS is used to add users and projects, the new record’s fields will be copied from the DEFAULT user and DEFAULT project records.


■ Utilities

Setup Utility (A_setup)

An example command for consolidating data to produce resource and audit reports from the CLI is as follows.

# A_selectA_SELECT> SELECT/AUDIT/SINCE=01-Jan-2006/BEFORE=01-Feb-2006/NODE=SPARKYA_SELECT> EXIT#

Setup Utility (A_setup) B

The A_setup utility lets the ITUAM administrator display or modify the system-wide parameters and options in the A_setup.sys file. These options and parameters indicate what ITUAM Data Collectors for UNIX and Linux features are enabled and how these features are implemented.

The A_setup utility also displays and manages values contained in the following files:

■ Database Instance file (A_dbinst.sys)

■ Image Mapping file (A_imgmap.sys)

Note • Parameters and options that control individual user or project accounts are maintained by the A_authorize utility.

/ADD_IMAGE (Optional)

The /ADD_IMAGE qualifier can be used to automatically add image records to the Image Mapping file (A_imgmap file). This qualifier has meaning only if the PROPRIETARY_SOFTWARE flag is enabled in the A_setup.sys file.

When the PROPRIETARY_SOFTWARE flag is enabled, the A_select utility will check to see if process names from the nightly accounting file are present in the A_imgmap.sys file. If a process names is present, the A_select utility adds the statistics associated with the image/process to a package record as well as a background or interactive record in the A_stat.sys file.

When the /ADD_IMAGE qualifier is present and the A_select utility encounters an accounting record for a process that is not present in the A_imgmap file, a record is added with the process name as the package name.

/STATISTICS (Optional)

The /STATISTICS qualifier outputs resource statistics that show how much CPU time, elapsed time, I/O, and so forth, the SELECT command itself used. This qualifier is valid only for certain platforms.

/VERBOSE (Optional)

The /VERBOSE qualifier causes SELECT to output more detailed messages during the execution of the SELECT command. These messages can be useful for debugging and troubleshooting purposes.


Utilities ■

File System Resource Utility (CS_fs_resource)

File System Resource Utility (CS_fs_resource) B

The CS_fs_resource utility reads the nightly storage files and generates the records for the CS_sum_fs_<date>.csv CSR file. This utility is called by the CS_nightly_consolidation script as part of the data consolidation process.


■ Utilities

File System Resource Utility (CS_fs_resource)


CCSR File Format

The CSR file is automatically produced by ITUAM Data Collectors for UNIX and Linux.

The CSR records are in a standard ASCII display format (no packed, binary, or bit data) with commas for delimiters and decimal points included in resource amounts. A negative sign should precede the numeric data, with no sign when the data is positive. When the identifier data contains commas, there must be double quotes around the identifier character data.

CSR records can contain a very large number of identifiers and resources. However, the maximum length for the records in the output CIMSAcct Detail file is 5,000 bytes with a limit of 100 resources.

The following table describes the fields in the CSR record.

Pos. Field Name Length Type Description

1 Header 8 Character Defines the source of data. For example, records that contain Oracle data have a header of ORCLUNIX.

There is no standard for this header and any unique combination of characters can be used.

2 Start Date of Usage

8 Number Date in format YYYYMMDD.

3 End Date of Usage 8 Number Date in format YYYYMMDD.

4 Start Time of Usage

8 Character Time in format HH:MM:SS.

5 End Time of Usage 8 Character Time in format HH:MM:SS.

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide C-1 ■

■ CSR File Format

6 Shift Code 1 Character Alphanumeric code denoting time of day usage occurred. Allows billing different rates by shift. If you do not want to charge by shift, the field should be blank.

7 Number of Identifiers

2 Number Number of identifiers in the following fields.

8 Identifier Name 1 32 Character The name of the identifier.

9 Identifier Value 1 Variable Character Includes items such as server node name, OS user name, database instance, file system mount point, and so forth. This should be shortened as much as possible to a meaningful code for further translation.

10 Identifier Name 2 32 Character The name of the identifier.

11 Identifier Value 2 Variable Character Includes items such as server node name, OS user name, database instance, file system mount point, and so forth. This should be shortened as much as possible to a meaningful code for further translation.

12 Identifier Name x 32 Character The name of the identifier.

13 Identifier Value x Variable Character Includes items such as server node name, OS user name, database instance, file system mount point, and so forth. This should be shortened as much as possible to a meaningful code for further translation.

X Number of Resources

2 Number Number of resources being tracked in the following fields.

X Rate Code 1 8 Character The rate code for the resource.

X Resource Value 1 Variable Number Resource usage value such as process user CPU time, file system size, database logins and connect time, database tablespace allocated, etc.

X Rate Code 2 8 Character The rate code for the resource.


■ C-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

CSR File Format ■

X Resource Value 2 Variable Number Resource usage value such as process user CPU time, file system size, database logins and connect time, database tablespace allocated, etc.

X Rate Code x 8 Character The rate code for the resource.

X Resource Value x Variable Number Resource usage value such as process user CPU time, file system size, database logins and connect time, database tablespace allocated, etc.


IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide C-3 ■

■ CSR File Format

■ C-4 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

DITUAM Messages

This appendix describes the messaged produced by ITUAM Data Collectors for UNIX and Linux.

About ITUAM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-2

Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-2

Example Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Returned Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

RTL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-5

CIMSG RTL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

Database RTL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13

Sampler Utility Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16

Convert Utility Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17

ITUAM Oracle Accounting Daemon Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19

ITUAM DB2 Accounting Daemon Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20

I

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide D-1 ■

■ ITUAM Messages

About ITUAM Messages

About ITUAM Messages D

ITUAM Data Collectors for UNIX and Linux uses a centralized message facility. The messages are produced for various levels of severity: success, informational, warning, error, and fatal. Each ITUAM Data Collectors for UNIX and Linux utility defines messages that pertain to its operation. In addition, ITUAM Data Collectors for UNIX and Linux uses runtime libraries (RTLs) that are common routines and these routines produce messages. Some ITUAM Data Collectors for UNIX and Linux messages occur due to a system error so the message contains the system error, also.

Message Format D

The messages displayed by ITUAM Data Collectors for UNIX and Linux have the following format:

%FACILITY-L-IDENT, text[errno = unix-errno, errno-text] (unix only)

Where:

■ FACILITY is the ITUAM Data Collectors for UNIX and Linux component name (see Table D-1).

■ L is a severity level indicator (see Table D-2 on page D-3).

■ IDENT is an abbreviation of the message text. The message descriptions in this chapter are alphabetized by this abbreviation.

■ text is an explanation of the message.

■ unix-errno and errno-text is the value of errno and text returned by UNIX.

Facility Descriptions

Facility ITUAM Component

ITUAM ITUAM runtime library

AUTHORIZE A_authorize utility

DBAO ITUAM Oracle Accounting daemon

DBADB2 ITUAM DB2 Accounting daemon

DBPLO ITUAM for UNIX Oracle Project LOGIN

DBPSO ITUAM for UNIX Oracle Project SWITCH

DBRTL ITUAM for UNIX DATABASE Runtime Library

CIMSG CIMSG Runtime Library

FRMT A_format utility

Table D-1 • Message Facility Descriptions

■ D-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

ITUAM Messages ■

Message Format

Severity Level Descriptions

MERGE A_merge utility

RPT A_report utility

SAMPLER A_sampler utility

SELECT A_select utility

SETUP A_setup utility

SMERGE A_smerge utility

VALID A_authorize utility

Severity Level Description

S The component performed your request successfully.

I The component performed your request successfully and provides some additional meaningful information.

W The component could have performed some, but not all, of its function and you might need to verify the results.

E The component's output is incorrect but the component can continue execution.

F The component cannot continue execution because the error is so severe.

Table D-2 • Severity Level Descriptions

Facility ITUAM Component

Table D-1 • Message Facility Descriptions (Continued)


■ ITUAM Messages

Message Format

Example Message D

The following is an example error message:

%ITUAM-F-OPENFAIL, error opening file - A_uaf.sysUNIX errno = 2, No such file or directory

Where:

■ Facility=ITUAM

■ Security Level=OPENFAIL

■ Ident=F

■ text=error opening file—A_uaf.sys

■ Unix errno=2

■ Unix errno text=No such file or directory

Returned Error Status D

When a UNIX shell interpreter executes a command or application program, the exit status of the process is returned in a shell variable (that is, $? for sh or ksh and $status for csh). The severity level of the last signaled message is returned to the shell by the ITUAM Data Collectors for UNIX and Linux utilities. You can use the shell status variable to determine the severity level of the last error message.

Values returned by the severity levels are:

■ S Success 1

■ I Info 3

■ W Warning 0

■ E Error 2

■ F Fatal 4


ITUAM Messages ■

RTL Messages

RTL Messages D

The RTLs generate the following messages:

ITUAMVER, ITUAM product version 5.1

Explanation: A ITUAM Data Collectors for UNIX and Linux utility displayed the ITUAM product version in response to the utility's IDENT command.

User Action: None.

BUFTOSMALL, buffer too small for input

Explanation: A buffer used to retrieve input was too small for a user's input.

User Action: Specify a smaller response when possible; otherwise, report the problem to IBM Software Support.

CMDAMBIG, ambiguous command verb <string>

Explanation: A command was entered in response to a utility's prompt, and the verb indicated by <string> was ambiguous.

User Action: Enter enough characters of the command verb to make it unambiguous.

CMDUNKNOWN, unknown command verb

Explanation: A command was entered in response to a utility's prompt, but the command is not a valid command in that utility.

User Action: Enter a valid command.

CONFLICT, illegal combination of command elements—<string>,<string>

Explanation: A command was entered in response to a utility's prompt, and the elements indicated are conflicting.

User Action: Enter the command without conflicting elements.

CREATE, error creating file—<string>

Explanation: An error was encountered during the creation of the specified file.

User Action: This message is accompanied by a system call error. Resolve the error by examining the cause of the system call error. Check the owner and group permissions on the directory where the file is to be created.

ESTABLISH, error establishing facility

Explanation: An internal software error has occurred.

User Action: Report this to IBM Software Support.


■ ITUAM Messages

RTL Messages

EXPIRED, this copy of ITUAM has expired as of <date>

Explanation: The ITUAM Data Collectors for UNIX and Linux software has expired as of the indicated date.

User Action: If you have a newer ITUAM Data Collectors for UNIX and Linux license PAK, install it. Otherwise, report this to IBM Software Support.

FDOPENERR, error returned from fdopen

Explanation: An error has occurred during an fdopen operation on a file.

User Action: This message is accompanied by a system call error. Resolve the error by examining the cause of the system call error. Check the owner and group permissions on the file.

FILNOTCONV, file not converted—<string>version found—<vers>, version expected—<vers>

Explanation: The file indicated by the <string> has not been converted to the latest version.

User Action: You must use the A_convert utility to convert the file so it can be accessed properly by this utility.

INTCONERR, internal inconsistency error

Explanation: An internal software error has occurred.


INVPASSWD, invalid password

Explanation: An invalid password was entered.

User Action: Use only characters that are valid for passwords.

INVPROJNAM, invalid project name

Explanation: An invalid project name was entered.

User Action: Use only characters that are valid for project names.

INVRECTYPE, invalid record type detected

Explanation: An invalid record type was detected in the Authorization file (A_uaf.sys).



ITUAM Messages ■

RTL Messages

INVTIME, invalid time

Explanation: A ITUAM Data Collectors for UNIX and Linux routine detected an invalid date/time.

User Action: This error occurred entering a time on the command line. The ITUAM CLI accepts dates in the format DD-MMM-YYYY.

IOERROR, I/O error from studio routine—<string>

Explanation: An error was returned by one of the standard UNIX I/O routines.

User Action: Examine the protection of the file indicated in the message to determine if access is prohibited. Check the owner and group permissions of the file.

KEYAMBIG, ambiguous keyword—<string>

Explanation: A command was entered in response to a utility's prompt, and the keyword indicated by <string> was ambiguous.

User Action: Enter enough characters in the keyword to make it unique.

KEYUNKNOWN, unknown keyword—<string>

Explanation: A command was entered in response to a utility's prompt, and the keyword indicated is unknown.

User Action: Enter a valid keyword.

KEYWRDREQ, keyword value is required—<string>

Explanation: A qualifier has been entered on the command line that requires a keyword.

User Action: Check the online help for the valid keywords for this qualifier and enter the command again with an appropriate keyword.

KWDVALREQ, keyword requires a value—<string>

Explanation: A keyword has been entered on the command line that requires a value, but none was supplied.

User Action: Enter the command with appropriate value for the indicated keyword.

LOCKERR, error locking file—<file-name>

Explanation: An error has occurred during a lock operation on a file.

User Action: This message is accompanied by a system call error. Resolve the error by examining the cause of the system call error.


■ ITUAM Messages

RTL Messages

MATCHQUOT, matching quote not found—<string>

Explanation: A command was entered in response to a utility's prompt, and a matching quote was not found.

User Action: Enter the command correctly with a matching quote.

MAXPARM, too many parameters—reenter with fewer parameters

Explanation: A command was entered in response to a utility's prompt containing too many parameters.

User Action: Enter the command with the correct number of parameters.

MEMALLOC, error allocating memory

Explanation: An error was encountered while allocating memory.

User Action: Determine the necessary resource quota and expand the quota.

NODEFPROJ, error reading DEFAULT project

Explanation: An error has occurred reading the DEFAULT project record from the A_uaf.sys file.

User Action: Verify that the A_uaf.sys file is accessible and no file corruption has occurred.

NODEFUSR, error reading DEFAULT user

Explanation: An error has occurred reading the DEFAULT user record from the A_uaf.sys file.

User Action: Verify that the A_uaf.sys file is accessible and no file corruption has occurred.

NOLIST, qualifier or keyword does not take a list of values—<string>Explanation: A command qualifier or a keyword that does not take a list of values was specified with a value list.

User Action: Enter the command again and correctly specify the qualifier or keyword.

NOPAREN, value improperly delimited—supply parenthesis—\<string>\

Explanation: A command value supplied as part of a parenthesized value list is missing a parenthesis.

User Action: Enter the command with the missing parenthesis.


ITUAM Messages ■

RTL Messages

NOPWDENT, error getting passwd entry

Explanation: ITUAM Data Collectors for UNIX and Linux could not retrieve an entry from the UNIX passwd file.


NOREPKWD, error repeating keyword <key> for qualifier <qual>

Explanation: You repeated a keyword on the command line.

User Action: Enter the specified keyword only once.

NOREPQUAL, error repeating qualifier <qual>

Explanation: You repeated the indicated qualifier on the command line.

User Action: Enter the specified qualifier only once.

NOVALIDENT, no entries in the ITUAM Validation File for USER <string>

Explanation: The user requested that a list of authorized projects be displayed and no entries were found in the A_validate.sys file for that user.

User Action: None.

NOVALUE, qualifier does not take a value—<string>

Explanation: A command qualifier that does not take a value was specified with a value.

User Action: Enter the command and qualifier with no value.

NULVAL, missing qualifier value—respecify

Explanation: A command qualifier that requires a qualifier value was specified, but no value was found.

User Action: Enter the command correctly specifying the qualifier and its value.

NUMERIC, invalid numeric value—supply an integer—\<string>\

Explanation: The command value must be an integer.

User Action: Enter the command correctly specifying the value as an integer.

OPENERR, error opening file—<string>

Explanation: An error has occurred during an open operation on a file.



■ ITUAM Messages

RTL Messages

PARMDEL, invalid parameter delimiter—check use of special characters \<string>\

Explanation: A command was entered incorrectly. The incorrect input is indicated by the <string>.

User Action: Enter the command using correct syntax.

POSERR, error positioning file—<string>

Explanation: An error has occurred during a seek operation on a file.


PUTENV, error expanding environment

Explanation: An error was encountered while expanding the environment.


QUALAMBIG, ambiguous command qualifier—<string>

Explanation: An ambiguous command qualifier was entered.

User Action: Enter enough characters in the qualifier to make it unique.

QUALUNKNOWN, unrecognized command qualifier—<string>

Explanation: A command qualifier was entered that is unknown.

User Action: Enter the command correctly specifying all qualifiers.

QUALVALREQ, qualifier value required—<string>

Explanation: A command qualifier was specified that requires a value, but no value was specified.

User Action: Enter the command correctly specifying the qualifier and its value.

READENV, error reading <environ-variable> from environment

Explanation: ITUAM Data Collectors for UNIX and Linux was not able to read the indicated environment variable.

User Action: Ensure that the environment variable indicated has been placed in the process environment.

READERR, error reading file—<string>

Explanation: An error has occurred during a read operation on a file.



ITUAM Messages ■

RTL Messages

RENAMERR, error renaming file from <name-1> to <name-2>

Explanation: The utility could not rename the name-1 file to name-2.

User Action: The system call error should indicate why the file could not be renamed. Correct the error and try the command again.

SCANFERR, scanf error

Explanation: An error has occurred during a scanf operation on a file.

User Action: This message is accompanied by a system call error. Resolve the error by examining the cause of the system call error. When you cannot resolve the error, report this to IBM Software Support.

STINXERR, error generating stat index tree

Explanation: An invalid index value in one of the ITUAM Data Collectors for UNIX and Linux mapping files has been detected.

User Action: This error usually occurs if a new copy of a mapping file has been created after the data consolidation phase. You must run data consolidation again.

TRUNERR, error truncating file—<string>

Explanation: An error has occurred during a truncate operation on a file.


TTYERR, error modifying terminal

Explanation: An error has occurred while performing an operation on a terminal.


UNLOCKERR, error unlocking file—<string>

Explanation: An error has occurred during an unlock operation on a file.


WRITEERR, error writing to file—<string>

Explanation: An error has occurred while performing a write operation on a file.



■ ITUAM Messages

CIMSG RTL Messages

CIMSG RTL Messages D

The ITUAM Data Collectors for UNIX and Linux CIMSG RTLs generate the following messages:

CHKREQ, checksum qualifier is required

Explanation: The /CHECKSUM qualifier is required on the ADD command.

User Action: Enter the command with the /CHECKSUM qualifier.

OPENERR, error opening file—<name>



READERR, error reading file—<name>

Explanation: An error has occurred during a read operation on a file.


SWHASEXP, software has expired

Explanation: ITUAM Data Collectors for UNIX and Linux has expired on this machine.

User Action: Install the ITUAM Data Collectors for UNIX and Linux update. Otherwise, report this to IBM Software Support.

UNLICMACH, unlicensed machine

Explanation: You are not licensed to run ITUAM Data Collectors for UNIX and Linux on this machine.

User Action: Run ITUAM Data Collectors for UNIX and Linux on a licensed machine or contact IBM Software Support for information about licensing the machine.

UNLICOPT, unlicensed option

Explanation: You are not licensed to run this utility on this machine.

User Action: Run the utility on a licensed machine or contact IBM Software Support for information about licensing the option required to run the utility.

UNLICVER, unlicensed version

Explanation: You are not licensed to run this version of ITUAM Data Collectors for UNIX and Linux on this machine.

User Action: Run a version of ITUAM Data Collectors for UNIX and Linux that is licensed on this machine or contact IBM Software Support for information about licensing this version of ITUAM Data Collectors for UNIX and Linux.


ITUAM Messages ■

Database RTL Messages

Database RTL Messages D

The ITUAM Data Collectors for UNIX and Linux database RTLs generate the following messages:

AUTHFAIL, project authorization failure

Explanation: A project authorization failure has been detected that is caused by an illegal project just entered, an illegal default project, an illegal password, or a user/project validation failure.

User Action: Check to see when the project name and password have been correctly entered and when the user is authorized to access this project.

COMERR, error committing transaction to Oracle Database

Explanation: An error has been returned committing an update to the ITUAM_PROJECT table. This error can only occur in environments using the Project Accounting feature.

User Action: Verify that the ITUAM_PROJECT table exists and is accessible to the Oracle user used by the ITUAM Oracle Accounting daemon to connect to the Oracle instance.

CONNERR, error connecting to Oracle Database

Explanation: An error has occurred in connecting to the Oracle Instance.

User Action: Verify that the Oracle user name and password used by the ITUAM Oracle Accounting daemon are valid. These values are entered into the Database Instance file (A_dbinst.sys) using the A_setup utility.

CURSCLOSE, error closing Oracle Database cursor data area

Explanation: An error has occurred in closing the Oracle database cursor data area.

User Action: This error occurred while shutting down the ITUAM Oracle Accounting daemon. The daemon will continue to shutdown. Note that cursors are not used in Oracle 8i.


■ ITUAM Messages


CURSOPEN, error opening Oracle Database cursor data area

Explanation: An error has occurred opening the Oracle database cursor data area.

User Action: Cursors are not used in Oracle 8i. In earlier versions, this error indicates a problem in allocation space for the cursor data area within Oracle.

INTERR, internal error accessing Oracle Database

Explanation: An unexpected error condition occurred when calling one of the OCI routines: odescr(), odefin(), oexfet(), or ofen().

User Action: Contact IBM Software Support.

INVSQL, invalid SQL statement

Explanation: An invalid SQL statement was passed to an ITUAM Database RTL subroutine.

User Action: The SQL statements used by the ITUAM Oracle Accounting daemon are internal to the utility and this message should never occur. If you see this message contact IBM Software Support.

LOGOFFERR, error logging off from Oracle Database

Explanation: An error has occurred logging off from the Oracle database.

User Action: An error was returned from the Oracle OCI ologof() while shutting down the ITUAM Oracle Accounting daemon. Shutdown will continue.

LOGONERR, error logging on to Oracle Database

Explanation: An error has occurred logging on to the Oracle database.

User Action: Verify that the Oracle user name and password used by the ITUAM Oracle Accounting daemon are valid. These values are entered into the A_dbinst.sys file using the A_setup utility.

PARAMERR, error fetching operating parameters

Explanation: An error has occurred fetching operating parameters.

User Action: Verify the values in the entry for this instance in the A_dbinst.sys file. Values can be viewed using the REPORT/DBINSTANCE command in the A_setup utility. This error indicates that one of the fields in the Database Instance file record is empty. Try to remove and then re-enter the record with the REMOVE/DBINSTANCE and ADD/DBINSTANCE commands.


ITUAM Messages ■


PARSERR, error parsing SQL statement

Explanation: An error has occurred in parsing the SQL statement.

User Action: This error indicates a failure in the Oracle OCI routine oparse(). The error will most often be reported to the ITUAM Oracle Accounting daemon log file during startup of the daemon when Project Accounting is enabled in the ITUAM Parameter file (A_setup.sys), but the ITUAM_PROJECT table has not been created in the Oracle instance. If you are not doing Project Accounting for Oracle usage, this error can be ignored. If this error occurs after startup, the accounting daemon will shutdown. Try to re-start the daemon.

PROJCTEXP, project has expired

Explanation: User is attempting to enter a project account that has expired.

User Action: Consult the ITUAM administrator regarding extending the expiration date.

READERR, error reading row from Oracle Database

Explanation: Oracle tried to read the indicated row, but could not.

User Action: This error indicates the ITUAM Oracle Accounting daemon could not read a row from one of the Oracle V$ tables. Confirm that the Oracle account used by the daemon has SELECT access to these tables.


■ ITUAM Messages

Sampler Utility Messages

Sampler Utility Messages D

The A_sampler utility generates the following messages:

CHDIRFAIL, cannot change to directory <dir>

Explanation: The A_sampler utility has encountered an error while attempting to move to the indicated directory.

User Action: The errno status was indicated in the error message. Review the error indicated by errno to resolve the problem.

NOENTRY, no entry in A_storage.par file

Explanation: There are no directory tree entries in the A_storage.par file.

User Action: Enter at least one directory tree to sample in the A_storage.par file.

OPENFAIL, error opening file—<file>

Explanation: The A_sampler utility has detected an error when opening the A_storage.par file or the indicated directory with the UNIX opendir system call.

User Action: The UNIX errno status was indicated in the error message. Review the error indicated by errno to resolve the problem.

PARAMINV, invalid Storage Parameter File specification—“<spec>”

Explanation: An entry in the A_storage.par file is not a directory.

User Action: Enter only valid directory names in the A_storage.par file.

POSERR, error positioning file—<file>

Explanation: The A_sampler utility has detected an error when positioning a file descriptor.


READENV, error reading <environ-variable> from environment

Explanation: The A_sampler utility was not able to read the indicated environment variable from the environment.

User Action: Ensure that the environment variable indicated has been placed in the process' environment.

SAMPLDIR, beginning to sample directory <dir>

Explanation: The A_sampler utility is beginning to sample the indicated directory.

User Action: None.


ITUAM Messages ■

Convert Utility Messages

SMPLRDONE, A_sampler completed

Explanation: The A_sampler utility has completed processing.

User Action: None.

STATFAIL, error getting file statistics—“<file>”

Explanation: The A_sampler utility tried to stat the indicated file and failed.


STATFSERR, failing to stat file system for <file-system>

Explanation: The A_sampler utility tried to get the number of blocks available in the file system using the statfs call, but failed.


Convert Utility Messages D

The A_convert utility generates the following messages:

CNVTDONE, A_convert completed

Explanation: The A_convert utility has completed processing.

User Action: None.

CREATERR, error creating file—<string>

Explanation: An error was encountered during the creation of the specified file.


FILCON, file converted—<string>version found—<vers>, version expected—<vers>

Explanation: The file indicated by the string has been converted to the latest version.

User Action: None.

FILUTD, "<filename> is up to date.",

Explanation: The file indicated is up to date.

User Action: None


■ ITUAM Messages

Convert Utility Messages

INVFILVER, "invalid file version detected—<filename>;version <version number>",

Explanation: The file indicated is an invalid version.

User Action: The indicated file may be corrupted. New versions of most ITUAM Data Collectors for UNIX and Linux files can be created by renaming the old file and running the ITUAM utility that usually maintains the file. For instance, if this message was produced while trying to convert the A_uaf.sys file, rename A_uaf.sys to A_uaf.org. Now run the A_authorize utility and you will be prompted to create a new A_uaf.sys file.

INVRATJT; invalid rate record jobtype detected

Explanation: The rate record jobtype detected is invalid.

User Action: The A_rates.sys file is corrupt. You must create a new file. Rename the A_rates.sys to A_rates.corrupt. Now run the A_rates utility and you will be prompted to create a new A_rates.sys file.

MEMERR, error allocating memory

Explanation: An error was encountered while allocating memory.


MLTDEFUSER, creating new user record; <filename>; for multiple DEFAULT user record detected

Explanation: A new user record was created as the stated user name because multiple DEFAULT user records were detected.

User Action: None.

MLTDEFPROJ, creating new project record; <filename>; for multiple DEFAULT project record detected

Explanation: A new project record was created as the stated filename because multiple DEFAULT project records were detected.

User Action: None.

NOPWDENT, error getting passwd entry

Explanation: ITUAM Data Collectors for UNIX and Linux could not read the user password entry.


PRODVER, converting ITUAM files to <version number>

Explanation: ITUAM Data Collectors for UNIX and Linux is displaying the current product version.

User Action: None.


ITUAM Messages ■

ITUAM Oracle Accounting Daemon Messages

RDVERR, error reading file version—<filename>

Explanation: An error occurred in reading the version of the file.

User Action: The indicated file may be corrupted. New versions of most ITUAM Data Collectors for UNIX and Linux files can be created by renaming the old file and running the ITUAM utility that usually maintains the file. For instance, if this message was produced while trying to convert the A_uaf.sys file, rename A_uaf.sys to A_uaf.org. Now run the A_authorize utility and you will be prompted to create a new A_uaf.sys file.

RENAMERR, error renaming <filename> to <filename>

Explanation: An error occurred during the execution of the COMPRESS command.

User Action: Correct the system error displayed and attempt the command again.

ITUAM Oracle Accounting Daemon Messages D

The ITUAM Oracle Accounting daemon generates the following messages:

CLOSERR, error closing file

Explanation: An error has occurred during a close operation on a file.


INTRNLERR, internal table or mechanical failure

Explanation: An error occurred getting the column of an Oracle Instance table.

User Action: This error is preceded by another message in the ITUAM Oracle Accounting daemon log file. Check the earlier message and correct that condition.

INVARG, invalid command line argument specified

Explanation: The command line contains an invalid argument.

User Action: An invalid argument was used when starting the ITUAM Oracle Accounting daemon. Use the startup scripts provided in the $ITUAM_UC_HOME/scripts/oracle directory.

INVSID, unable to obtain a valid SID

Explanation: The ITUAM Oracle Accounting daemon did not have a valid ORACLE_SID value on startup.

User Action: Use the startup scripts provided in the $ITUAM_UC_HOME/scripts/oracle directory.


■ ITUAM Messages

ITUAM DB2 Accounting Daemon Messages

OPENERR, error returned from open



STATNAMERR, error in formatting A_dbstatname.sys

Explanation: The format of the $ITUAM_UC_HOME/data/A_dbstatname.sys file is incorrect.

User Action: A copy of the A_dbstatname.sys file is located in $ITUAM_UC_HOME/scripts/oracle directory. Copy this file to the data directory and re-start the ITUAM Oracle Accounting daemon.

WRITEHEAD, error updating ITUAM DB Accounting file header

Explanation: An error has occurred in updating the ITUAM Database Accounting file header.

User Action: Verify that the owner of the ITUAM Oracle Accounting daemon process has access to the ITUAM Database Accounting file.

ITUAM DB2 Accounting Daemon Messages D

The ITUAM DB2 Accounting daemon generates the following messages:

ABNORMAL, DB2 API <API name>;abnormal completion code

Explanation: Unsuccessful completion due to DB2 API call failure.

User Action: Correct the problem reported by the DB2 API and restart the ITUAM DB2 Accounting daemon.

CLOSEACCT, error closing ITUAM IBM DB2 Accounting file; <filename>

Explanation: An error has occurred in closing DB2 accounting file <filename>.

User Action: The error occurred while shutting down the ITUAM DB2 Accounting daemon. Shutdown will continue.

DATAERR, error reading snapshot data

Explanation: Unexpected data/format was captured.

User Action: Report this error to IBM Software Support.


ITUAM Messages ■


INVARG, invalid command line argument <DB2 name>

Explanation: When starting the ITUAM DB2 Accounting daemon, an invalid argument was detected on the command line.

User Action:

OPENLOG, error opening ITUAM IBM DB2 log file

Explanation: An error has occurred in an open action on the DB2 log file.

User Action: Use the startup script provided in the $ITUAM_UC_HOME/scripts/db2 directory.

OPENACCT, error opening ITUAM IBM DB2 Accounting file;<filename>

Explanation: An error has occurred in an open action on the ITUAM DB2 accounting file.

User Action: Check the ownership and group permissions on the ITUAM DB2 Accounting file.

RENAMERR, error renaming old ITUAM IBM DB2 Accounting file

Explanation: An error has occurred during execution of the COMPRESS command.

User Action: Correct the system error displayed and re-start the ITUAM DB2 Accounting daemon.

SNAPSHOT, error obtaining snapshot from DB2 database;<DB2 name>

Explanation: An error has occurred in obtaining snapshot data from a DB2 database.

User Action: Verify that DB2 Monitor parameters are set and that the Monitor table is accessible.

WRITEHEAD, error updating ITUAM IBM DB2 Accounting file

Explanation: An error has occurred in writing to the DB2 Accounting file.

User Action: Verify that the owner of the ITUAM DB2 Accounting daemon process has access to the ITUAM Database Accounting file.


■ ITUAM Messages



ENotices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide E-1 ■

■ Notices

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

■ E-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Notices ■

Trademarks

Trademarks E

The following are trademarks of International Business Machines Corporation in the United States, other countries, or both:

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Windows is a trademark of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

AIX IBM Tivoli

DB2 PowerPC

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide E-3 ■

■ Notices

Trademarks

■ E-4 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Glossary

crontab • A UNIX command that creates a table or list of commands, each of which is to be executed by the operating system at a specified time.

CSR File • The resource file that contains the data that is input into ITUAM. The records in this file are comma-delimited and can contain a very large number of resource identifiers and resources. See also identifier and rate code.

CSR+ File • CSR+ files are similar to CSR files, with the exception that the records in the CSR+ file contain an additional header at the beginning of the record.

identifier • In the CSR file records, a unique key that denotes the source of a resource that has been consumed. Examples include device name, server name, system ID, phone number, user ID, state code or building number. A consumed resource can have one to many identifiers.

rate code • A rate code represents the resource units being reported (for example, CPU time, transactions processed, or lines printed). The rate code includes the value for the resource and other rate processing information.

XML • Acronym for Extensible Markup Language. A simple, very flexible text format derived from SGML. XML allows for more precise declarations or content and more meaningful search results across multiple platforms.

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide Glossary-1 ■

■ Glossary

■ Glossary-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Index

Aaccounting directory, about A-9Activity file (A_activity.sys), about A-11aggregating data, CS_aggtools.pm subroutine 4-4AIX Advanced Accounting

configuring 2-2data collection

scheduling 2-5scripts for 2-3setting up 2-3

data files, creating 2-2record types collected 2-3scripts for data collection 2-3 to 2-4

Authorization file (A_uaf.sys), about A-13Authorize utility (A_authorize), about B-3

Bbin directory

in $ITUAM_HOME, about A-2in $ITUAM_UC_HOME, about A-10

Ccheck_pacct script, about 3-3CIMS Oracle and DB2 files (A_db*.sys), about

A-11cimsu_check_db2 script, about 1-55cimsu_check_odb script, about 1-48cimsu_start_db2 script, about 1-53cimsu_start_odb script, about 1-46cimsu_stop_db2 script, about 1-54cimsu_stop_odb script.about 1-47Cleanup subroutine, about 4-10Collapsible Terminal file (A_terminals.par),

about A-14

collectors directory, about A-3config directory, about A-7Configuration Parameter file (A_config.par)

about 1-30environment variables in 1-31 to 1-39

conversion scriptsabout 4-4parameters for 4-5 to 4-6

Convert utility (A_convert), about B-3CS_aggtools, about 4-4CS_input_source directory, about A-10CS_nightly_consolidation script, about 3-9CSR files

format description C-1 to C-3rate codes and identifiers in

CS_cims_sum_db2_<date>.csv 3-18 to 3-19CS_cims_sum_db2_stor_<date>.csv 3-19CS_cims_sum_ora_<date>.csv 3-16CS_cims_sum_ora_stor_<date>.csv 3-17CS_sum_<date>.csv 3-13 to 3-15CS_sum_fs_<date>.csv 3-20

transferring to ITUAM server 3-21 to 3-24

Ddaemon for DB2 database accounting

checking 1-55configuring 1-51 to 1-52starting 1-52, 1-53stopping 1-54

daemon for Oracle database accountingchecking 1-48configuring 1-44 to 1-45starting 1-45, 1-46stopping 1-47

IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide Index-1 ■

■ Index

data collectionaccounting files, creating 3-6DB2 table storage file, creating 3-7Oracle table storage file, creating 3-7pacct file size, managing 3-3scripts

get_db2_storage 3-7get_odb_storage 3-7ituam_uc_nightly 3-4overview 3-2redo_nightly 3-8runacct 3-6sampler 3-7turnacct 3-5

system storage files, creating 3-7data consolidation

scriptsCS_nightly_consolidation 3-9overview 3-9

data directoryabout A-10files in

Activity file (A_activity.sys) A-11Authorization file (A_uaf.sys) A-13CIMS Oracle and DB2 files A-11Collapsible Terminal file (A_terminals.par)

A-14Configuration Parameter file (A_config.par)

1-30Holiday file (A_holiday.sys) A-11Image Mapping file (A_imgmap.sys) A-12Intermediate Statistics file (A_stat.sys) A-12Login Projects file (A_lgiproj.sys) A-12Merged Statistics file (A_stat.dat) A-13Node Parameter file (A_node.par) 1-30Oracle Basename file (A_odb_base.sys) A-12Oracle Username file (A_odb_user.sys) A-12Parameter file (A_setup.sys) A-12Process Statistics file (A_procstat.sys) A-12Queue Mapping file (A_queuemap.sys) A-12Storage file (A_storage.sys) A-12Storage Parameter file (A_storage.par) A-13Terminal Parameter file (A_term_par.sys)

A-12Validation file (A_validate.sys) A-13wtmp Statistics file (A_wtmpstat.sys) A-13

data processingarchitecture 4-3 to 4-13

ITUAM Processing Engine, about 4-2scripts for 4-13 to 4-15

database accountingDB2, scripts for 1-53 to 1-55Oracle, scripts for 1-46 to 1-48setting up 1-43 to 1-57suggestions for 1-57

date calculation in scripts A-14DB2

accounting daemonchecking 1-55configuring 1-51 to 1-52scripts for 1-53 to 1-55starting 1-52, 1-53stopping 1-54

accounting utilitieslinking 1-50list of 1-50

collector preparation procedures 1-50 to 1-56table storage files, creating 3-7

directoriesaccounting A-9bin

in $ITUAM_HOME A-2in $ITUAM_UC_HOME A-10

collectors A-3config A-7CS_input_source A-10data A-10 to A-14etc A-14help A-15history A-16jlib A-7jlib/CIMS_Lib A-8log A-16LogFiles A-8processes A-8sample_processes A-8scripts

$ITUAM_HOME A-8in $ITUAM_UC_HOME A-16

■ Index-2 IBM Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide

Index ■

Eenvironment variables for data collection and

consolidation, setting 1-31 to 1-39etc directory

about A-14scripts in

check_pacct 3-3ituam_date.awk A-14ituam_env A-14ituam_platform A-14ituam_uc_nightly 3-4redo_nightly 3-8runacct 3-6sampler 3-7turnacct 3-5

FFile System Resource utility (CS_fs_resource),

about B-11files

Authorization file (A_uaf.sys) A-13Collapsible Terminal file (A_terminals.par)

A-14Configuration Parameter file (A_config.par)

1-30Intermediate Statistics file (A_stat.sys) A-12Login Projects file (A_lgiproj.sys) A-12Merged Statistics file (A_stat.dat) A-13Node Parameter file (A_node.par) 1-30Oracle Basename file (A_odb_base.sys) A-12Oracle Username file (A_odb_base.sys) A-12Parameter file (A_setup.sys) A-12Process Statistics file (A_procstat.sys) A-12Queue Mapping file (A_queuemap.sys) A-12raw accounting, list of B-6Storage file (A_storage.sys) A-12Storage Parameter file (A_storage.par) A-13temporary accounting, list of B-6Terminal Parameter file (A_term_par.sys) A-12Validation file (A_validate.sys) A-13wtmp Statistics file (A_wtmpstat.sys) A-13

Format utility (A_format), about B-6

Gget_db2_storage script, about 3-7get_odb_storage script, about 3-7getting started 1-31 to 1-41

process accounting, starting 1-40scripts, scheduling 1-39 to 1-40setting environment variables 1-31 to 1-39

Hhelp directory, about A-15history directory, about A-16Holiday file (A_holiday.sys), about A-11

IImage Mapping file (A_imgmap.sys), about A-12installation

about 1-7clean up after 1-41DB2 preparation procedures 1-50 to 1-56files

list of 1-7 to 1-9running 1-11 to 1-12

Oracle preparation procedures 1-43 to 1-49preparing for 1-5 to 1-6remote

about 1-13files for A-4 to A-7prerequisites for target computer 1-13UNIX/Linux to UNIX/Linux 1-25 to 1-27Windows to UNIX/Linux 1-14 to 1-25

Intermediate Statistics file (A_stat.sys), about A-12

ITUAM Data Collectors for UNIX and Linuxabout 1-3conversion scripts for 4-4 to 4-6features and benefits 1-3installing 1-5 to 1-12installing remotely 1-13 to 1-27

ITUAM Processing Engineabout 4-2CS_aggtools, about 4-4directory for 4-2installing 1-11

ituam_date.awk script, about A-14ituam_env script, about A-14ituam_format_acct script, about 2-3ituam_get_aacct script, about 2-3ituam_platform script, about A-14


■ Index

ituam_send_aacct script, about 2-4ituam_uc_nightly script, about 3-4

Jjlib directory, about A-7job log files

about 4-13directory for 4-13naming convention for 4-13

job scriptsabout 4-10directory for 4-9parameters for 4-11 to 4-12

Llib/CIMS_Lib directory, about A-8linking

DB2 accounting utilities 1-50Oracle accounting utilities 1-43 to 1-50

logdirectory, about A-16files

ituam_uc_nightly.log 3-4sending to ITUAM server 3-25 to 3-26

log files See job log filesLogDate parameter

about 4-14values for 4-14

LogFiles directory, about A-8Login Projects file (A_lgiproj.sys.sys), about A-12

MMerge utility (A_merge)

about B-7commands and qualifiers B-7

Merged Statistics file (A_stat.dat), about A-13messages, ITUAM

about D-2CIMSG RTL D-12Convert utility D-17 to D-19Database RTL D-13 to D-15example D-4format of D-2 to D-3ITUAM DB2 Accounting Daemon D-20 to D-21ITUAM Oracle Accounting Daemon D-19 to

D-20RTL D-5 to D-11Sampler utility D-16 to D-17

Nnightly

accounting filecreating 3-6

collection script (ituam_uc_nightly) 3-4consolidation script,

(CS_nightly_consolidation) 3-9DB2 storage files, creating 3-7Oracle storage file, creating 3-7system storage files, creating 3-7

nightly.pl scriptabout 4-15parameter requirements for 4-15

nightly.sh scriptabout 4-13scheduling 4-13variables in 4-14

Node Parameter file (A_node.par), about 1-30

OOracle

accounting daemonchecking 1-48configuring 1-44 to 1-45scripts for 1-46 to 1-48starting 1-45, 1-46stopping 1-47

accounting utilitieslinking 1-43 to 1-50list of 1-43

Basename file A-12collector preparation procedures 1-43 to 1-49table storage files, creating 3-7Username file A-12

overview ofdata collection scripts 3-2data consolidation scripts 3-9ITUAM Data Collectors for UNIX and Linux

architecture 1-28 to 1-30


Index ■

Ppacct file

managing size of 3-3Parameter file (A_setup.sys), about A-12Perl

modulesCS_aggtools.pm, about 4-4, A-8CS_libs.pm, about A-8directory for A-8

pre-installation checklist 1-5 to 1-6procCIMS.pl script

about 4-15parameters for 4-15

process accountingstarting 1-40turning on and off 3-5

process definitionsabout 4-9, A-8contents of 4-9creating 4-9

Process Statistics file (A_procstat.sys), about A-12processes directory A-8

See also process definitionsabout 4-9back up schedule for 4-9

processing dataCS_aggtools, about 4-4

Qqualifiers

A_format utility/AGGREGATE 3-6/ROLL 3-6

A_merge utility/STATISTICS B-7/VERBOSE B-7

A_select utility/ADD_COUNTS B-9/ADD_IMAGE B-10/NODE B-9/SINCE and /BEFORE B-9/STATISTICS B-10/VERBOSE B-10/ZERO B-9

Queue Mapping file (A_queuemap.sys), about A-12

Rrate codes and identifiers

list ofAIX Advanced Accounting 2-6 to 2-9Apache 1-58background 3-13 to 3-15DB2 3-18 to 3-19DB2 table storage 3-19FTPD 1-58interactive 3-13 to 3-15Oracle 3-16Oracle table storage 3-17process 3-13 to 3-15storage 3-13 to 3-15UNIX/Linux file system 3-20

raw accounting files, list of B-6redo_nightly script, about 3-8remote installation

about 1-13files for A-4 to A-7prerequisites for target computer 1-13UNIX/Linux to UNIX/Linux 1-25 to 1-27Windows to UNIX/Linux 1-14 to 1-25

runnacct script/AGGREGATE qualifier used with 3-6/ROLL qualifier used with 3-6

runnacct script, about 3-6

Ssample_processes directory, about A-8sampler script, about 3-7Sampler utility (A_sampler), about B-7Scan subroutine, about 4-10scripts

conversion scripts 4-4 to 4-6data collection

check_pacct 3-3get_db2_storage 3-7get_odb_storage 3-7ituam_uc_nightly 3-4overview 3-2redo_nightly 3-8runacct 3-6sampler 3-7turnacct 3-5

data consolidationCS_nightly_consolidation 3-9overview 3-9


■ Index

DB2cimsu_check_db2 1-55cimsu_start_db2 1-53cimsu_stop_db2 1-54

directory for 4-13ituam_date.awk A-14ituam_env A-14ituam_format_acct 2-3ituam_get_aacct 2-3ituam_platform A-14ituam_send_aacct 2-4job script 4-10 to 4-12nightly.pl 4-15nightly.sh 4-13Oracle

cimsu_check_odb 1-48cimsu_start_odb 1-46cimsu_stop_odb 1-47

procCIMS.pl 4-15scheduling on client and server nodes 1-39 to

1-40scripts directory

$ITUAM_HOMEabout A-8

in $ITUAM_UC_HOME, about A-16Select utility (A_select)

about B-8commands and qualifiers B-8 to B-10

sendingCSR files to ITUAM server 3-21 to 3-24log files to ITUAM server 3-25 to 3-26

Setup utility (A_setup), about B-10statistics processed by ITUAM Data Collectors for

UNIX and LinuxDB2 statistics 5-8 to 5-9Oracle statistics 5-6 to 5-7UNIX/Linux statistics 5-3 to 5-5

Storage file (A_storage.sys), about A-12Storage Parameter file (A_storage.par), about

A-13system

architecture, described 4-3 to 4-15system specifications 1-4

Ttemporary account files, list of B-6Terminal Parameter file (A_term_par.sys), about

A-12transferring

CSR filesto ITUAM server 3-21 to 3-24

log files to ITUAM server 3-25 to 3-26turnacct script, about 3-5

UUNIX/Linux process accounting

starting 1-40turning on and off 3-5

utilitiesA_authorize B-3A_convert B-3A_format B-6A_merge B-7A_sampler B-7A_setup B-10CS_fs_resource B-11linking

DB2 1-50Oracle 1-43 to 1-50

Select (A_select) B-8 to B-10

VValidation file (A_validate.sys), about A-13

Wwtmp Statistics file (A_wtmpstat.sys), about A-13


IBM Tivoli Usage and Accounting Manager Data...

Documents

Transcript of IBM Tivoli Usage and Accounting Manager Data...