Preface
This manual describes methods of operating JP1/Performance Management, how to manage a system when linking with other systems, and troubleshooting.
- Organization of this preface
■ Intended readers
This manual is intended for:
-
Those who wish to gain an understanding of the operating procedures for JP1/Performance Management in the context of an operation monitoring system
-
Those who wish to define conditions for collecting performance data
-
Those who wish to define reports and alarms
-
Those who wish to monitor a system with reference to collected performance data
-
Those who wish to plan strategies for improving the system based on the monitoring results
This manual assumes that the reader is familiar with the system being monitored.
For details on how to collect performance data using JP1/Performance Management - Agent or JP1/Performance Management - Remote Monitor, refer to the manuals for each of these products.
■ Organization of this manual
This manual is organized into the following parts. Note that this manual contains information common to all the operating systems that this product supports. If there are differences relating to specific operating systems, we note these differences in the text.
- PART 1: Operation
-
PART 1 describes how to operate JP1/Performance Management.
- PART 2: System Linkage
-
PART 2 describes how to configure and operate JP1/Performance Management when you use it in a cluster system or a multiple-monitoring configuration, or link it with other systems.
- PART 3: Troubleshooting
-
PART 3 describes how to detect errors with JP1/Performance Management and what action you should take when a problem occurs.
■ 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:
|
Italic |
Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:
Italic characters are also used for emphasis. For example:
|
Monospace |
Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:
|
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. |
■ 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.