JP1 Version 12 JP1/Integrated Management 2 - Manager Command and Definition File Reference


This manual describes the commands and definition files of JP1/Integrated Management 2 - Manager and JP1/Integrated Management 2 - View systems. In this manual, JP1/Integrated Management is abbreviated to JP1, and JP1/Integrated Management 2 - Manager and JP1/Integrated Management 2 - View are generically referred to as JP1/Integrated Management or JP1/IM. In addition, in this manual, read JP1/Integrated Management - Manager and JP1/Integrated Management - View as JP1/Integrated Management 2 - Manager and JP1/Integrated Management 2 - View, respectively.

Organization of this preface

■ Intended readers

This manual is intended for users who want to manage, use, and operate an infrastructure that manages an open-platform system form JP1/IM. More specifically, it is intended for:

■ Organization of this manual

This manual consists of the following chapters:

1. Commands

Chapter 1 describes the syntax for the commands that can be used in JP1/Integrated Management.

2. Definition Files

Chapter 2 describes the formats and syntax of the definition files for JP1/Integrated Management.

3. JP1 Events

Chapter 3 describes the types and attributes of the JP1 events that are issued by JP1/Integrated Management.

4. Lists of System-Monitoring Objects (for Central Scope)

Chapter 4 describes the system-monitoring objects that are provided by JP1/Integrated Management.

5. Monitoring Tree Models (for Central Scope)

Chapter 5 describes the structures of monitoring trees that are created automatically.

■ Manual suite

JP1/IM manuals provide necessary information according to the phase in the system life cycle (the phases include planning/design, configuration, and operation). Read the manual appropriate for the purpose.

The following figure explains which phases the JP1/IM manuals provide information for.


■ Conventions: Diagrams

This manual uses the following conventions in diagrams:


■ Conventions: Fonts and symbols

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

Text formatting



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 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 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:




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.


Indicates a space.

Δ0: Zero or more spaces (space can be omitted).

Δ1: One or more spaces (space cannot be omitted).


Indicates a tab.


[Figure]A means that a tab character precedes A.

■ Conventions: Installation folders for the Windows version of JP1/IM and JP1/Base

In this manual, the installation folders for the Windows versions of JP1/IM and JP1/Base are indicated as follows:

Product name

Installation folder

Default installation folder#

JP1/IM - View


system-drive:\Program Files\Hitachi\JP1CoView

JP1/IM - Manager


system-drive:\Program Files\Hitachi\JP1IMM


system-drive:\Program Files\Hitachi\JP1Cons


system-drive:\Program Files\Hitachi\JP1Scope



system-drive:\Program Files\Hitachi\JP1Base

#: Represents the installation folder when the product is installed in the default location. The location represented by system-drive:\Program Files is determined at the time of installation by an OS environment variable, and might differ depending on the environment.

■ Conventions: Meaning of "Administrator permissions" in this manual

In this manual, Administrator permissions refers to the Administrator permissions for the local PC. Provided that the user has Administrator permissions for the local PC, operations are the same whether they are performed with a local user account, a domain user account, or in an Active Directory environment.

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

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.

■ Conventions: Paths specified in definition files

A definition cannot include any file name that is specified with a network path.

For example, the event guide information file must have EV_FILE specified with a folder path that is not a network path.

■ Online manuals

JP1/IM comes with an HTML manual that you can read in a web browser.

The HTML manual has the same contents as this manual.

To view the HTML manual:


■ Output destinations of Integrated trace log file

Starting with JP1/IM 12-10, all 32-bit Java processes for JP1/IM have been changed to 64-bit Java processes. Therefore, the integrated trace log output destination output by the Java process function of each function of JP1 / IM is changed.

The following is the destination of the integrated trace log for each JP1/IM function from version 12-10. If you are using the log file trap function, you must change the settings as you change the destination.

Output destinations of Integrated trace log file (32 bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool

Output destinations of Integrated trace log file (64 bit): system-drive\Program Files\Hitachi\HNTRLib2\spool