Preface

■ Intended readers

This manual describes JP1/Performance Management. It is intended for the following readers:

• Users who are interested in designing and building an operation monitoring system

• Users who are interested in defining conditions for collecting performance data

• Users who are interested in defining reports and alarms

• Users who are interested in referencing performance data that is collected for the purpose of system monitoring

• Users who are interested in using the monitoring results to examine measures to improve a system and to provide instructions for such measures

This manual assumes that the reader is knowledgeable about the operation of the monitored systems and is familiar with their operating systems.

For details about setting up and operating a system that uses JP1/Performance Management, the reader is directed to the following manuals as well:

• JP1/Performance Management Planning and Configuration Guide

• JP1/Performance Management User's Guide

• JP1/Performance Management Reference

To Page Top

■ Organization of this manual

This manual is organized into the parts listed below. Note that this manual applies when the operating system (OS) on the host where JP1/Performance Management - Agent Option for Platform is installed is Windows. When there are differences in functionality between OSs, this manual provides a separate description for each OS.

PART 1: Overview

PART 1 provides an overview of JP1/Performance Management - Agent Option for Platform.

PART 2: Setup and Operation

PART 2 explains installation and setup of JP1/Performance Management - Agent Option for Platform, and how to collect user records.

PART 3: Reference

PART 3 explains the monitoring templates, records, commands, and messages associated with JP1/Performance Management - Agent Option for Platform.

PART 4: Troubleshooting

PART 4 explains the actions to take when a problem occurs with JP1/Performance Management - Agent Option for Platform.

To Page Top

■ Conventions: Diagrams

This manual uses the following conventions in diagrams:

To Page Top

■ Conventions: Fonts and symbols

The following table explains the text formatting conventions used in this manual:

Text formatting	Convention
Bold	Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example: From the File menu, choose Open. Click the Cancel button. In the Enter name entry box, type your name.
Italic	Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example: Write the command as follows: copy source-file target-file The following message appears: A file was not found. (file = file-name) Italic characters are also used for emphasis. For example: Do not delete the configuration file.
Monospace	Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example: At the prompt, enter dir. Use the send command to send mail. The following message is displayed: The password is incorrect.

The following table explains the symbols used in this manual:

Symbol	Convention
|	In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example: A|B|C means A, or B, or C.
{ }	In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example: {A|B|C} means only one of A, or B, or C.
[ ]	In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example: [A] means that you can specify A or nothing. [B|C] means that you can specify B, or C, or nothing.
...	In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted. In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example: A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.
()	Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.

To Page Top

■ Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

• Version 1.00 (or 1.0) is written as 01-00.

• Version 2.05 is written as 02-05.

• Version 2.50 (or 2.5) is written as 02-50.

• Version 12.25 is written as 12-25.

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

To Page Top