Preface

This manual describes methods of operating Job Management Partner 1/Performance Management, how to manage a system when linking with other systems, and troubleshooting. In this manual, Job Management Partner 1 is abbreviated to JP1.

Organization of this preface

Intended readers
Organization of this manual
Conventions: Diagrams
Conventions: Fonts and symbols
Conventions: Meaning of "bookmark"
Conventions: Version numbers

■ 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.

To Page Top

■ 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.

To Page Top

■ Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

To Page Top

■ Conventions: Fonts and symbols

Font and symbol conventions are classified as:

General font conventions
Conventions in syntax explanations
Conventions for mathematical expressions

These conventions are described below.

General font conventions

The following table lists the general font conventions:

Font	Convention
Bold	Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following: From the File menu, choose Open. Click the Cancel button. In the Enter name entry box, type your name.
Italics	Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example: Write the command as follows: `copy` `source-file` `target-file` Do not delete the configuration file.
`Code font`	A code font indicates 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.`

Font

Convention

Bold

Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following:

From the File menu, choose Open.
Click the Cancel button.
In the Enter name entry box, type your name.

Italics

Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:

Write the command as follows:

copy source-file target-file
Do not delete the configuration file.

Code font

A code font indicates 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.

Examples of coding and messages appear as follows (although there might be some exceptions, such as when coding is included in a diagram):

MakeDatabase
...
StoreDatabase temp DB32

In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.

Conventions in syntax explanations

Syntax definitions appear as follows:

StoreDatabase [temp|perm] (database-name ...)

The following table lists the conventions used in syntax explanations:

Example font or symbol	Convention
`StoreDatabase`	Code-font characters must be entered exactly as shown.
`database-name`	This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.
`SD`	Bold code-font characters indicate the abbreviation for a command.
`perm`	Underlined characters indicate the default value.
`[ ]`	Square brackets enclose an item or set of items whose specification is optional.
`\|` (vertical bar)	A vertical bar separates items in a list, and means "OR". For example, `A\|B\|C` means one of `A` or `B` or `C`.
`...`	An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary.
`()`	Parentheses indicate the range of items to which the vertical bar (\|) or ellipsis (...) is applicable.
`{}`	Curly brackets enclose a list of items, and indicate that one (and only one) of the items in the list must be used. A vertical bar (`\|`) separates the items in the list. For example, `{A\|B\|C}` means that one of `A` or `B` or `C` must be used.

Conventions for mathematical expressions

This manual uses the following symbols in mathematical expressions:

Symbol	Meaning
x	Multiplication sign
`/`	Division sign

To Page Top

■ Conventions: Meaning of "bookmark"

In this manual, bookmark is generally used when there is no need to distinguish bookmark and combination bookmark. Combination bookmark is used only for describing original functionalities of combination bookmarks.

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