Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference


Preface

This manual describes the commands and definition files of Job Management Partner 1/Integrated Management - Manager and Job Management Partner 1/Integrated Management - View systems. In this manual, Job Management Partner 1/Integrated Management is abbreviated to JP1, and Job Management Partner 1/Integrated Management - Manager and Job Management Partner 1/Integrated Management - View are generically referred to as JP1/Integrated Management or JP1/IM.

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.

[Figure]

■ Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

■ Conventions: Fonts and symbols

Font and symbol conventions are classified as:

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, and 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 the 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 may 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.

If multiple items are enclosed, either omit them all or select one of them.

Example:

[A] means either nothing or A must be specified.

[B|C] means nothing, or B, or C must be specified.

|

Only one of the options separated by a vertical bar can be specified at the same time.

Example:

A|B|C means 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.

{ }

One of the items or sets of items enclosed in curly brackets must be selected. Inside the curly brackets, each item or set of items is separated by a vertical bar (|).

Example:

{A|B|C} means that A, or B, or C must be specified.

[Figure]

Indicates a space.

[Figure]0: Zero or more spaces (space can be omitted).

[Figure]1: One or more spaces (space cannot be omitted).

[Figure]

Indicates a tab.

Example:

[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

View-path

system-drive:\Program Files\Hitachi\JP1CoView

JP1/IM - Manager

Manager-path

system-drive:\Program Files\Hitachi\JP1IMM

Console-path

system-drive:\Program Files\Hitachi\JP1Cons

Scope-path

system-drive:\Program Files\Hitachi\JP1Scope

JP1/Base

Base-path

system-drive:\Program Files\Hitachi\JP1Base

#: Denotes the installation folder for each product when a default installation is performed.

For Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, and Windows Vista, the location represented by system-drive:\Program Files is determined at 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.

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

Note: