Job Management Partner 1 Version 10 Job Management Partner 1/Performance Management Reference

3021-3-349-20(E)

Notices

Relevant program products

Job Management Partner 1/Performance Management - Manager (for Windows):

P-2W2C-AAAL Job Management Partner 1/Performance Management - Manager 10-50

The above product includes the following:

P-CC242C-AAAL Job Management Partner 1/Performance Management - Manager 10-50 (for Windows Server 2003)

P-CC2A2C-AAAL Job Management Partner 1/Performance Management - Manager 10-50 (for Windows Server 2008, Windows Server 2012)

Job Management Partner 1/Performance Management - Manager (for UNIX):

P-812C-AAAL Job Management Partner 1/Performance Management - Manager 10-50 (for Linux 5 (x86), Linux 5 (x64), Linux 5 Advanced Platform (x86), Linux 5 Advanced Platform (x64), Linux 6 (x86), Linux 6 (x64))

P-9D2C-AAAL Job Management Partner 1/Performance Management - Manager 10-50 (for Solaris 10 (SPARC))

P-1M2C-AAAL Job Management Partner 1/Performance Management - Manager 10-50 (for AIX V6.1, AIX V7.1)

Job Management Partner 1/Performance Management - Base (for Windows):

P-2W2C-AJAL Job Management Partner 1/Performance Management - Base 10-50

The above product includes the following:

P-CC242C-AJAL Job Management Partner 1/Performance Management - Base 10-50 (for Windows Server 2003)

P-CC2A2C-AJAL Job Management Partner 1/Performance Management - Base 10-50 (for Windows Server 2008, Windows Server 2012)

Job Management Partner 1/Performance Management - Base (for UNIX):

P-1J2C-AJAL Job Management Partner 1/Performance Management - Base 10-50 (for HP-UX 11i V3 (IPF))

P-812C-AJAL Job Management Partner 1/Performance Management - Base 10-50 (for Linux 5 (x86), Linux 5 (x64), Linux 5 Advanced Platform (x86), Linux 5 Advanced Platform (x64), Linux 6 (x86), Linux 6 (x64))

P-9D2C-AJAL Job Management Partner 1/Performance Management - Base 10-50 (for Solaris 10 (SPARC), Solaris 11 (SPARC))

P-1M2C-AJAL Job Management Partner 1/Performance Management - Base 10-50 (for AIX V6.1, AIX V7.1)

Job Management Partner 1/Performance Management - Web Console (for Windows):

P-2W2C-ARAL Job Management Partner 1/Performance Management - Web Console 10-50

The above product includes the following:

P-CC242C-ARAL Job Management Partner 1/Performance Management - Web Console 10-50 (for Windows Server 2003)

P-CC2A2C-ARAL Job Management Partner 1/Performance Management - Web Console 10-50 (for Windows Server 2008, Windows Server 2012)

Job Management Partner 1/Performance Management - Web Console (for UNIX):

P-812C-ARAL Job Management Partner 1/Performance Management - Web Console 10-50 (for Linux 5 (x86), Linux 5 (x64), Linux 5 Advanced Platform (x86), Linux 5 Advanced Platform (x64), Linux 6 (x86), Linux 6 (x64))

In addition to the above products, this product is targeted at the PFM - Agent and PFM - RM products of Job Management Partner 1/Performance Management, which require Job Management Partner 1/Performance Management - Base. Also, these products include parts that were developed under licenses received from third parties.

Trademarks

AMD, AMD Opteron, and combinations thereof, are trademarks of Advanced Micro Devices, Inc.

HP-UX is a product name of Hewlett-Packard Development Company, L.P. in the U.S. and other countries.

IBM is trademark of International Business Machines Corporation, registered in many jurisdictions worldwide.

IBM, AIX are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

IBM, AIX 5L are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

Intel is a trademark of Intel Corporation in the U.S. and/or other countries.

Internet Explorer is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.

Itanium is a trademark of Intel Corporation in the United States and other countries.

Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft and Hyper-V are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

ODBC is Microsoft's strategic interface for accessing databases.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United States and other countries.

RSA and BSAFE are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries.

SAP and R/3 and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc., in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

UNIX is a registered trademark of The Open Group in the United States and other countries.

VMware is a registered trademark or a trademark of VMware, Inc. in the United States and/or other jurisdictions.

Win32 is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Other product and company names mentioned in this document may be the trademarks of their respective owners. Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the capitalization used by the manufacturer, or by writing the name with initial capital letters. Hitachi cannot attest to the accuracy of this information. Use of a trademark in this document should not be regarded as affecting the validity of the trademark.

The following program products contain some parts whose copyrights are reserved by Sun Microsystems, Inc.: P-9D2C-AAAL, P-9D2C-AJAL.

The following program products contain some parts whose copyrights are reserved by UNIX System Laboratories, Inc.: P-9D2C-AAAL, P-9D2C-AJAL.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project.

Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.

This product includes software developed by the University of California, Berkeley and its contributors.

This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).

Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

This product includes software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http://www.modssl.org/).

This product includes software developed by IAIK of Graz University of Technology.

This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes software developed by Andy Clark.

Job Management Partner 1/Performance Management - Web Console includes RSA BSAFE(R) software developed by EMC Corporation of the United States.

Restrictions

Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty.

Material contained in this document may describe Hitachi products not available or features not available in your country.

No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

IIS

Microsoft(R) Internet Information Services

Internet Explorer

Microsoft(R) Internet Explorer(R)

Windows(R) Internet Explorer(R)

MSCS

Microsoft(R) Cluster Service

SQL Server

Microsoft(R) SQL Server 2005 Enterprise Edition

Microsoft(R) SQL Server 2005 Standard Edition

Microsoft(R) SQL Server 2008 Enterprise

Microsoft(R) SQL Server 2008 Enterprise R2

Microsoft(R) SQL Server 2008 Standard

Microsoft(R) SQL Server 2008 Standard R2

Microsoft(R) SQL Server 2012 Business Intelligence Edition

Microsoft(R) SQL Server 2012 Enterprise Edition

Microsoft(R) SQL Server 2012 Standard Edition

Windows Server 2003

Windows Server 2003 (x64)

Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2003, Standard x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition

Windows Server 2003 (x86)

Microsoft(R) Windows Server(R) 2003, Enterprise Edition

Microsoft(R) Windows Server(R) 2003, Standard Edition

Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard Edition

Windows Server 2008

Windows Server 2008

Microsoft(R) Windows Server(R) 2008 Enterprise

Microsoft(R) Windows Server(R) 2008 Enterprise without Hyper-V(R)

Microsoft(R) Windows Server(R) 2008 Standard

Microsoft(R) Windows Server(R) 2008 Standard without Hyper-V(R)

Windows Server 2008 R2

Microsoft(R) Windows Server(R) 2008 R2 Datacenter

Microsoft(R) Windows Server(R) 2008 R2 Enterprise

Microsoft(R) Windows Server(R) 2008 R2 Standard

Windows Server 2012

Windows Server 2012

Microsoft(R) Windows Server(R) 2012 Datacenter

Microsoft(R) Windows Server(R) 2012 Standard

Windows Server 2012 R2

Microsoft(R) Windows Server(R) 2012 R2 Datacenter

Microsoft(R) Windows Server(R) 2012 R2 Standard

WSFC

Microsoft(R) Windows Server(R) Failover Cluster

Windows Server 2003, Windows Server 2008, and Windows Server 2012 are sometimes referred to as Windows.

Issued

Dec. 2014: 3021-3-349-20(E)

Copyright

All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.

(C)opyright 2000-2009, by Object Refinery Limited and Contributors.

Summary of amendments

The following table lists changes in this manual (3021-3-349-20(E)) and product changes# related to this manual.

Changes

Location

The following OS is now supported:

Windows Server 2012 R2

--

The monitoring suspension function is now supported.

1.1, 1.3, 1.3.2, 1.4, 1.4.1, 1.4.2, 1.4.8, 1.4.10(1), 1.4.16, 1.8.2(1), Appendix D.1, Appendix D.2, Appendix E.1(3), Appendix F.1, Appendix H

The quickGuideHideReportIcon item was added to the initial settings file (config.xml).

1.4.3, Appendix E.1(3)

Functionality (the history collection priority function) that prioritizes the collection of history data over displaying real-time reports is now supported.

1.4.3, 1.4.5, 1.8.2(1), Appendix F.1, Appendix H

The Process Monitoring Settings > Create a New

Application Definition > Add from Running Processes window can now display the data acquisition date.

1.4.15(3)

Functionality that waits for the alarm command to execute is now supported.

Notes on commands, Appendix F.1

The following commands were added:

jpcconf acc display

jpcconf acc setup

jpcconf acc unsetup

jpcparamdump

jpctool monitor list

jpctool monitor resume

jpctool monitor status

jpctool monitor suspend

Commands, jpcconf acc display, jpcconf acc setup, jpcconf acc unsetup, jpcparamdump, jpctool monitor list, jpctool monitor resume, jpctool monitor status, jpctool monitor suspend, Appendix I

The examples of output and the coding format for the parameter file of the following commands were changed to those of version 0110:

jpcasrec output

jpcasrec update

jpcasrec output, jpcasrec update

The realtime-report-data-collection-mode tag was added to the parameter file of the jpcasrec update command.

jpcasrec update

A description about monitoring suspension was added for the following commands:

jpcconf ha setup

jpcconf ha unsetup

jpcconf hc enable

jpctool alarm active

jpcconf ha setup, jpcconf ha unsetup, jpcconf hc enable, jpctool alarm active

A description about real-time reports was added for the following command:

jpcrpt

jpcrpt

A -wait option was added to the following commands:

jpctool alarm active

jpctool alarm bind

jpctool alarm check

jpctool alarm copy

jpctool alarm delete

jpctool alarm export

jpctool alarm import

jpctool alarm inactive

jpctool alarm list

jpctool alarm unbind

jpctool alarm active, jpctool alarm bind, jpctool alarm check, jpctool alarm copy, jpctool alarm delete, jpctool alarm export, jpctool alarm import, jpctool alarm inactive, jpctool alarm list, jpctool alarm unbind

The following PFM - Manager messages were added:

KAVE00252-E to KAVE00255-E, KAVE00258-E to KAVE00262-E, KAVE00487-I, KAVE00493-E,

KAVE00500-W to KAVE00512-I, KAVE00515-W to KAVE00523-E, KAVE00525-W to KAVE00529-E, KAVE00531-E to KAVE00532-W, KAVE04902-E,

KAVE05470-E to KAVE05492-I, KAVE05971-E to KAVE05974-E, KAVE06171-E to KAVE06178-E, KAVE06180-I to KAVE06194-I, KAVL15105-W

4.4.1, 4.5.1, 4.6

The following PFM - Web Console messages were added:

KAVJJ8577-Q to KAVJJ8579-Q, KAVJK2563-E to KAVJK2568-E, KAVJK4002-E, KAVJK6522-I, KAVJK6523-I, KAVJS2541-E to KAVJS2549-E, KAVJS2640-E, KAVJS2663-E to KAVJS2667-E, KAVJS4017-E, KAVJS4018-E, KAVJS6569-I, KAVJS6570-I

4.4.2, 4.6

The following PFM - Manager messages were changed:

KAVE00398-W, KAVE05415-E, KAVE06158-E, KAVE06161-E

4.6

The following PFM - Web Console messages were changed:

KAVJK2559-E, KAVJS2530-E, KAVJS2604-E, KAVJS2607-E, KAVJS2629-E, KAVJS2702-E, KAVJS5001-I

4.6

The Random Retry Mode label was added to the Common Section of the startup information file (jpccomm.ini). This is related to the dispersion of the reconnection.

Appendix F.1

The Action Handler Section was added to the startup information file (jpccomm.ini). This is related to the functionality for the synchronous execution controller for actions.

Appendix F.1, Appendix H

In addition to the above changes, minor editorial corrections have been made.

#

Product changes include functionalities that were supported from the release of version 10-10 to the release of version 10-50.

Preface

This manual describes the Job Management Partner 1/Performance Management windows, commands, log information, and messages. In this manual, Job Management Partner 1 is abbreviated to JP1.

Intended readers

This manual is intended for:

Those who wish to design or set up 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 chapters listed below. This manual is intended for use with multiple operating systems (OS). When there are differences in functionality between operating systems, this manual provides a separate description for each OS.

1. PFM - Web Console Windows

Chapter 1 describes the JP1/Performance Management - Web Console window that is displayed using a Web browser.

2. Commands

Chapter 2 describes the JP1/Performance Management commands.

3. Log Information Output by Performance Management

Chapter 3 describes the log information that is output by JP1/Performance Management and its output formats.

4. Messages

Chapter 4 describes the messages output by JP1/Performance Management - Manager and JP1/Performance Management - Web Console in terms of their formats and their output destinations. It provides a list of the messages output to syslog and the Windows event log, and it describes and explains the messages individually.

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

-

The hyphen is used as an option delimiter. An option may consist of the following:

One or more alphanumeric characters

One or more alphanumeric characters and arguments.

Note that an option can be included within an argument. When an option or a space is included in an argument, it may be necessary to enclose the entire argument in single (') or double (") quotation marks.

{ }

One of the items enclosed in curly brackets must be specified. The items are delimited with a vertical bar (|).

[ ]

Square brackets enclose an item or set of items whose specification is optional.

|

A vertical bar indicates that only one of the options separated by a vertical bar can be specified at the same time.

...

An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary.

Conventions for mathematical expressions

The following table lists the conventions used in mathematical formulas:

Symbol

Meaning

x

Multiplication sign

/

Division sign

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 functionality unique to combination bookmarks.

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.

1 PFM - Web Console Windows

PFM - Web Console enables you to use a Web browser to monitor visually the operating status of monitoring agents. It can also display the system performance data collected by each monitoring agent in graphical report formats.

This chapter describes each window used in PFM - Web Console and the items that are displayed in each window.

1.1 List of PFM - Web Console windows

The following table lists and describes the windows displayed in PFM - Web Console:

Table 1‒1: List of PFM - Web Console windows

Window name

Description

Login window

Used to log into PFM - Web Console.

Main window

Main window of PFM - Web Console that is displayed when you log into PFM - Web Console.

From this window you can display any of the various windows used for operation monitoring of monitoring agents.

You can also display the operating status of all agents under the directory selected in the navigation frame (Display Summary).

Agents window

Displays a monitoring agents tree. This window enables you to do the following:

Display reports on each monitoring agent.

Check the status of alarms and the event history.

Check the health check status.

Add a new monitoring agent and create a tree of monitoring agents.

Bind monitoring agents and alarm tables.

Display combination reports and register bookmarks.

Create reports and alarms by using Quick Guide.

Suspend or resume monitoring.

To display this window: In the navigation frame of any PFM - Web Console window, choose the Agents tab.

Reports window

Displays a reports tree.

This window enables you to create, copy, and edit reports.

To display this window: In the navigation frame of any PFM - Web Console window, choose the Reports tab.

Bookmarks window

Displays a bookmarks tree.

This window enables you to manage bookmarks or combination bookmarks by changing, editing, and deleting the names of bookmarks. The window also enables you to display a View Report window by clicking a bookmark or to display a combination report window by clicking a combination bookmark.

To display the Bookmarks window: In the navigation frame of any PFM - Web Console window, choose the Bookmarks tab.

Alarms window

Displays an alarms tree.

This window enables you to create new alarm tables and alarms and to edit them. It also enables you to import and export alarms.

This window is displayed only when the login user has the administrator user permission.

To display this window: In the navigation frame of any PFM - Web Console window, choose the Alarms tab.

Services window

Manages the services of the Performance Management programs. This window enables you to display, edit, and distribute properties, and to stop services.

This window is displayed only when the login user has the administrator user permission.

To display this window: In the navigation frame of any PFM - Web Console window, choose the Services tab.

Users window

Manages Performance Management users. This window enables you to create user accounts and to change user account information.

This window is displayed only when the authentication mode of the user account is PFM authentication mode, and the login user has the administrator user permission.

To display this window: In the navigation frame of any PFM - Web Console window, choose the Users tab.

Table 1‒2: List of windows displayed from the Main window

Window name

Description

Reference

Event Monitor

Displays event information for the monitoring agents.

1.3.2

Change Password

Changes the login user password.

1.3.3

Environment Settings

Sets the interval for automatically updating the screen display.

1.3.4

About

Displays the PFM - Web Console version information.

1.3.5

Help

Displays the Performance Management manuals.

1.3.6

Table 1‒3: List of windows displayed from the Agents window

Window name

Description

Reference

System Operational Status Summary

Lists the operating status of all agents under the directory selected in the Navigation frame.

1.4.2

Stopped Host List

Quick Guide

Creates a quick report or sets an alarm.

1.4.3

Quick Guide > Search Fields

Quick Guide > Create Alarm

Quick Guide > Create Alarm > View Results

Search Results: number-of-records record(s)

Search Results: List of number-of-fields field(s) found in record record-name

Display Reports > Select Report

Displays a report.

1.4.4

1.4.5

View Report

Baseline

Save Report Definition

Save Report Definition (for entering a folder name)

Description of Record and Fields

Print Reports

Prints or saves a report.

1.4.6

Combination Report

Displays a combination report.

1.4.7

Alarm Status

Displays the status of an alarm in an alarm table that is bound to (associated with) the selected monitoring agent.

1.4.8

Properties

Service Properties

Displays the properties of the selected monitoring agent service (Agent Collector service, Remote Monitor Collector service, or each remote agent and group agent).

1.4.9

Event History

Displays the event history for the monitoring agent.

1.4.10

Alarm Table Bind Settings [Select Alarm Tables]

Used to bind (associate) or unbind a monitoring agent and multiple alarm tables. This window is displayed when the functionality for binding an alarm to multiple alarm tables is enabled.

1.4.11

Bind Alarm Table [Select Alarm Tables]

Used to bind (associate) a monitoring agent and alarm tables. This window is displayed when the functionality for binding an alarm to multiple alarm tables is disabled.

1.4.12

Edit Agent Tree

Edits the Agents tree.

1.4.13

Edit Agent Tree > Copy [Select Copy Place]

Edit Agent Tree > New Folder

Edit Agent Tree > New Agents

Edit Agent Tree > Rename

Regist Bookmark > Select Report

Selects a report for registration as a bookmark or a combination bookmark from the Agents tree.

1.4.14

Bookmark

Bookmark (the folder name entry)

Process Monitoring Settings

Sets process monitoring for PFM - Agent for Platform and PFM - RM for Platform.

1.4.15

Process Monitoring Settings > Create a New Application Definition

Process Monitoring Settings > Edit an Application Definition

Process Monitoring Settings > Delete an Application Definition

Process Monitoring Settings > Application Definition Templates

Process Monitoring Settings > Save an Application Definition Template

Process Monitoring Settings > Create a New Application Definition > Input Using Application Definition Template

Process Monitoring Settings > Create a New Application Definition > Add from Running Processes

Process Monitoring Settings > Create a New Application Definition > Add from Running Processes (Command Lines)

Process Monitoring Settings > Create a New Application Definition > Add from Services

Process Monitoring Settings > Edit an Application Definition > Input Using Application Definition Template

Process Monitoring Settings > Edit an Application Definition > Add from Running Processes

Process Monitoring Settings > Edit an Application Definition > Add from Running Processes (Command Lines)

Process Monitoring Settings > Edit an Application Definition > Add from Services

Process Monitoring Settings > Create a New Application Definition Template

Process Monitoring Settings > Edit an Application Definition Template

Process Monitoring Settings > Delete an Application Definition Template

Process Monitoring Settings > Create a New Application Definition Template > Input Using Application Definition Template

Process Monitoring Settings > Create a New Application Definition Template > Add from Running Processes

Process Monitoring Settings > Create a New Application Definition Template > Add from Running Processes (Command Lines)

Process Monitoring Settings > Create a New Application Definition Template > Add from Services

Process Monitoring Settings > Edit an Application Definition Template > Input Using Application Definition Template

Process Monitoring Settings > Edit an Application Definition Template > Add from Running Processes

Process Monitoring Settings > Edit an Application Definition Template > Add from Running Processes (Command Lines)

Process Monitoring Settings > Edit an Application Definition Template > Add from Services

Monitoring Suspension Settings

Suspends or resumes monitoring.

1.4.16

Monitoring Suspension Settings > Change Settings

Monitoring Suspension Settings > Check Changes

Monitoring Suspension Settings > Check Results

List of Selected Agents

Lists the currently selected agents.

1.4

Table 1‒4: List of windows displayed from the Reports window

Window name

Description

Reference

New Folder

Creates a new report folder under the User Reports folder or a report folder you have selected.

1.5.2

New Report > Name and Type

Creates a new report definition or changes an existing report definition.

1.5.3

New Report > Field

New Report > Field > Search Fields

New Report > Filter

New Report > Indication Settings (Realtime)

New Report > Indication Settings (Historical)

New Report > Indication Settings

New Report > Graph

New Report > Drilldown

New Report > Drilldown > Select Report

New Report > Drilldown > Edit Conditional Expression for Drilldown

Edit > Name and Type

Edit > Field

Edit > Field > Search Fields

Edit > Filter

Edit > Indication Settings (Realtime)

Edit > Indication Settings (Historical)

Edit > Indication Settings

Edit > Graph

Edit > Drilldown

Edit > Drilldown > Select Report

Edit > Drilldown > Edit Conditional Expression for Drilldown

Search Results: number-of-records record(s)

Search results: List of number-of-fields field(s) found in record record-name

Description of Record and Fields

Import

Imports report folders and report definitions.

1.5.4

Properties

Displays the properties of the selected report definition.

1.5.5

Copy

Copies the selected report definition to a report folder.

1.5.6

Rename

Renames a report folder under User Reports or a report definition.

1.5.7

Table 1‒5: List of windows displayed from the Bookmark window

Window name

Description

Reference

New Folder

Creates a new bookmark folder under the root or the selected bookmark folder.

1.6.2

Edit

Changes the display method for the combination report.

1.6.3

Properties

Displays the properties of the selected bookmark or combination bookmark.

1.6.4

Rename

Changes the name of the selected bookmark folder, bookmark, combination bookmark, or baseline.

1.6.5

Tiling Display

Tiles the graphs of history reports managed by the selected bookmark.

1.6.6

Tiling Display Settings

Table 1‒6: List of windows displayed from the Alarms window

Window name

Description

Reference

Import

Imports alarm folders, alarm tables, and alarms.

1.7.2

New Alarm Table > Main Information

Creates a new alarm table definition.

1.7.3

New Alarm Table > Alarm Conditions

New Alarm Table > Alarm Conditions > Search Fields

New Alarm Table > Action

New Alarm Table > Action > Select a report

New Alarm Table > Action Definitions

New Alarm Table > Action Definitions > JP1 Event Settings

New Alarm > Main Information

Creates a new alarm definition or changes an existing alarm definition.

1.7.4

New Alarm > Alarm Conditions

New Alarm > Alarm Conditions > Search Fields

New Alarm > Action

New Alarm > Action > Select a report

New Alarm > Action Definitions

New Alarm > Action Definitions > JP1 Event Settings

Edit > Main Information

Edit > Alarm Conditions

Edit > Alarm Conditions > Search Fields

Edit > Action

Edit > Action > Select a report

Edit > Action Definitions

Edit > Action Definitions > JP1 Event Settings

Search Results: number-of-records record(s)

Search results: List of number-of-fields field(s) found in record record-name

Description of Record and Fields

Properties

Displays the properties (definitions) of the selected alarm.

1.7.5

Copy > Input Name [Alarm Table]

Copies an alarm table or an alarm.

1.7.6

Copy > Input Name [Alarm]

Active Setting

Sets whether to enable or disable a defined alarm.

1.7.7

Show Bound Agents

Displays the monitoring agents bound to (associated with) the selected alarm table.

1.7.8

Table 1‒7: List of windows displayed from the Services window

Window name

Description

Reference

Service Properties

Displays the properties of the selected service.

1.8.2

LOGIF Expression Editor

Service status

Displays the status of the selected service.

1.8.3

Distribute Property > Select Service

Distributes properties.

1.8.4

Distribute Property > Select Property

Distribute Property > Progress Reports

Table 1‒8: List of windows displayed from the Users window

Window name

Description

Reference

New User

Creates a new Performance Management user.

1.9.2

Copy

Creates a copy of an existing user account.

1.9.3

Edit

Changes the information about an existing user account.

1.9.4

Reference note

When you use Internet Explorer to display any of the following windows, you can display the menu bar and the status bar. However, the menu bar and the status bar in the Web browser will not appear if you choose to hide them in the Main window of PFM - Web Console.

View Report window

Combination Report window

Event monitor window

Event history window

Properties window for alarms

Properties window for reports

1.2 Login window

The Login window is the first window that appears when you use a Web browser at the monitoring console to access the monitoring console server.

The following shows the Login window:

Figure 1‒1: Login window

The following describes the displayed items:

User name

Enter your user account name, from 1 through 16 bytes.

In the PFM authentication mode:

Enter a user account name that has been registered for a Performance Management user.

In the JP1 authentication mode:

Enter a user account name that has been registered in JP1/Base for a JP1 user.

Password

Enter a new password, from 1 through 16 bytes. Any blank spaces entered before and after the password are ignored.

1.3 Main window

This is the Main window of PFM - Web Console. It is displayed when a user logs in successfully to PFM - Web Console. This window consist of four frames:

Menu bar frame

Navigation frame

Method frame

Information frame

The following figure shows the Main window of PFM - Web Console.

Figure 1‒2: Main window

The following describes the frames and items displayed in the Main window:

Menu bar frame

Displays a menu that is common to all PFM - Web Console windows.

The following describes the items displayed in the menu bar frame:

Event Monitor

Displays the Event Monitor window.

See 1.3.2 Event Monitor window.

Change Password

Displays the Change Password window.

See 1.3.3 Change Password window.

Environment Settings

Displays the Environment Settings window.

See 1.3.4 Environment Settings window.

About

Displays the About window.

See 1.3.5 About window.

Help

Displays the Help window.

See 1.3.6 Help window.

Logout

Logs out from PFM - Web Console. Choosing this item displays a message box for confirming your intention to log out.

Navigation frame

The navigation frame displays the items (tabs) described below. Selecting an item displays the corresponding window.

Agents

Displays the Agents window.

See 1.4 Agents window.

Reports

Displays the Reports window. You can use the initialization file (config.xml) to specify whether to display the Reports window for a user who logs in with an account that has general user permissions only. For details about the initialization file (config.xml), see E. Initialization File (config.xml).

See 1.5 Reports window.

Bookmarks

Displays the Bookmarks window.

See 1.6 Bookmarks window.

Alarms

Displays the Alarms window. This item is displayed only when the login user has the administrator user permission.

See 1.7 Alarms window.

Services

Displays the Services window. This item is displayed only when the login user has the administrator user permission.

See 1.8 Services window.

Users

Displays the Users window. This item is displayed only when the login user has the administrator user permission.

See 1.9 Users window.

Refresh

Refreshes the information displayed in the window.

An icon is displayed to the left of each configuration component. The following table shows the icons and describes each.

Table 1‒9: Configuration component icons and their meaning

Component

Description

root()

The root of each tree. You cannot change the root name.

For the agents tree

Products is displayed as the root name for the monitoring trees for products.

If you set business groups for operation, you can also display the tree for each business group. When you display the tree for a business group, the business group name is displayed as the root name.

Also, if you monitor the trees created for each login user, User Agents (login-user-name) is displayed as the root name.

You can select which tree you want to display from Indication Settings in the navigation frame of the Agents window.

For the reports tree

User Reports or System Reports is displayed as the root name.

For the bookmarks tree

Bookmarks is displayed as the root name.

For the alarms tree

User Alarms or Template Alarms is displayed as the root name.

For the services tree

System is displayed as the root name.

If set business groups for operation, you can display a tree for each business group. If you display the tree for an application group, the business group name is displayed as the root name.

For the users tree

Users is displayed as the root name.

When multiple selections are possible, this icon indicates that there are multiple selectable nodes under the applicable folder, and all selectable nodes under the root folder (all folders down to the lowest tree) are selected.

When multiple selections are possible, this icon indicates that there are multiple selectable nodes under the applicable folder, and some of the selectable nodes under the root folder (all folders toward the lowest tree) are selected.

Folder ()

A component for grouping agents or reports.

When you create trees, you can create a maximum of eight trees under the root (root, agent, report, and alarm trees are not included).

When multiple selections are possible, this icon indicates that there are multiple selectable nodes under the applicable folder, and all selectable nodes under the root folder (all folders down to the lowest tree) are selected.

When multiple selection is possible, this icon indicates that there are selectable nodes under the applicable folder, and some of the selectable nodes under the folder (all folders down to the lowest tree) are selected

Bookmark folder ()

A component for grouping bookmarks.

Alarm folder ()

A component for grouping alarms.

Service folder ()

A component for grouping services.

User folder ()

A component for grouping users.

There are three folders: management user, ordinary users, and business group ordinary users. Business group ordinary users is displayed when the access control functionality is enabled.

Agent ()

PFM - Agent that is connected to PFM - Manager.

The service ID is displayed as the agent name.

For details about service IDs, see the appendix that explains the naming rules for services in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Indicates normal.

Indicates warning.

Indicates abnormal.

Indicates that monitoring is suspended.

Indicates that the status of the agent is either of the following, and that there is no substance:

Agent service information was deleted, after which the PFM - Web Console was updated by the jpcconf service sync command.

Because of configuration changes in a business group, the user's reference privilege for agents was deleted.

This icon is displayed only when User Agents is selected for Indication Settings in the navigation frame of the Agents window. You cannot perform any agent operation when this icon is displayed.

Remote Monitor Collector service ()

PFM - RM service that collects performance data.

The Remote Monitor Collector service is displayed as instance-name[name-of-host-on-which-PFM - RM-runs].

Remote agent ()

Agent that monitors programs managed by PFM - RM. A remote agent is created for each monitoring target program for PFM - RM.

A remote agent is displayed as instance-name[monitoring-target-name@name-of-host-on-which-PFM - RM-runs].

Group agent ()

Indicates an agent that monitors multiple PFM - RM monitoring target programs concurrently.

A group agent is displayed as instance-name[group-name@name-of-host-on-which-PFM - RM-runs].

Report ()

Indicates a report. The report can be either a PFM - Agent report or a PFM - RM report.

Bookmark ()

Indicates a bookmark.

Combination bookmark()

Indicates a combination bookmark.

Baseline()

Indicates a baseline.

Alarm table ()

Indicates an alarm table. If the table is under Template Alarms, its name begins with PFM.

Alarm ()

Indicates an alarm.

User ()

Indicates a user.

Method frame

Displays the actions that are available in the selected target window. The items displayed in the method frame correspond to the item chosen in the navigation frame.

Information frame

Displays the results of the operation executed in the window that is displayed by choosing an item in the navigation frame.

1.3.1 Transitions from the Main window

The following shows the window transitions from the Main window:

Figure 1‒3: Window transitions from the Main window

1.3.2 Event Monitor window

The Event Monitor window displays event information for the monitoring agents. To display this window, in the Main window, from the menu bar frame, choose Event Monitor. The Event Monitor window consists of the following two pages:

View report page

Show Options page (Event Monitor Settings window)

This subsection describes these pages.

(1) View report page

This page displays information about the events that have occurred on the monitoring agents. On the Show Options page of the Event Monitor Settings window, you can set display conditions, including the agents for which you want to display events, and the maximum number of items to be displayed.

The following figure shows the Event Monitor window (View report page).

Figure 1‒4: Event Monitor window (View report page)

The following describes the items displayed on this page:

View

Enables you to select from the pull-down menu, the type of events to be displayed in the table frame. The following event types are available:

All events

Agent events

Alarm events

Health check events

Health check statuses

The default is All events. When you select Health check statuses, only the icons, agents, host names, and status are displayed.

Refresh

Refreshes the information displayed in the table frame.

Table frame

Displays a list of the events of the event type selected in View.

The following describes the items displayed in the table frame:

Event status icons

An icon indicates each event's status. The following explains the event status icons that can be displayed for each event type selected with View:

Agent events

An agent event indicates the status of an agent. An agent event is issued when the status of an agent that is bound to an alarm table changes.

The event status icons have the meanings described below. The meanings vary by the product (PFM - Agent or PFM - RM).

: Normal, inactive status (status unknown)

: Warning status

: Abnormal status

: Monitoring suspended status

If monitoring is resumed, the icon corresponding to the alarm status of the agent at the time is displayed.

Caution:

- If Always notify is selected in the alarm definition, no agent event is issued because changes of agent status are not monitored.

- If an agent is added to or deleted from a host where monitoring is suspended, the event is displayed by the icon that indicates the normal status, but actually monitoring is suspended. You can check the correct status from the icon in the navigation frame.

Alarm events

An alarm event indicates the status of an event with an icon. An alarm event is issued when the threshold for a warning or an abnormality is reached. The event status indicated varies as follows according whether State changes for each record instance is selected:

When State changes for each record instance is selected:

An icon is displayed to indicate the status of the instance of a record for which an alarm event occurred.

When State changes for each record instance is not selected:

An icon is displayed to indicate the status of an alarm that caused the alarm event.

(green): Normal event

(yellow): Warning event

(red): Abnormal event

#: Abnormal or warning event

#: This icon is displayed only if Always notify is selected in the alarm definition.

Health check events or health check status:

A health check event is issued when a health check status changes. The following show the health check status icons and their meanings:

: Not Supported

: Running

: Monitoring suspended

: Incomplete

: Stopped

: Unconfirmed

: Host Not Available

For details about the health check status, see the chapter that explains error detection of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

Example of displaying alarm notifications of state changes for each instance is specified:

When notification of state changes for each instance is specified, alarm event icons and alarm name icons are displayed separately in the Event Monitor window. The following describes the status indicated by icons for the notification of state changes for each instance:

Alarm event icon

This icon indicates the status of an instance.

Alarm name icon

This icon indicates the status of an alarm.

The following describes an example of displaying information for a multi-instance record that has instance 1 (Disk C:) and instance 2 (Disk E:):

Instance 1 (Disk C:) of the record is now in an abnormal status, and an alarm is thereby generated. Assume that a warning event is issued for instance 2 (Disk E:) of the record. The following figure shows an example of displaying alarm information (on the View report page) in the Event Monitor window in such a case.

Figure 1‒5: Example of display when notification of state changes for each instance is specified

Because instance 2 (Disk E:) is in the warning status, the alarm event icon is displayed in yellow and the Status column displays Warning.

The alarm status of each instance is as follows:

Record instance 1 (Disk C:): Abnormal status

Record instance 2 (Disk E:): Warning status

Because the abnormal status for instance 1 (Disk C:) is at a high severity level, the alarm name icon for instance 1 turns to red.

Date and Time

Displays the system date and time (according to the locale) at the agent where the event occurred. For details, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Agent

Displays the service ID of the monitoring agent where the event occurred.

Host

Displays the host name of the monitoring agent where the event occurred. For a remote agent, the monitoring host name is displayed. For a group agent, the primary host name is displayed.

Status

Displays the event's status; one of the following is displayed:

For agent events and alarm events:

OK: Normal event

Exception: Abnormal event

Warning: Warning event

Inactive: Inactive event or event whose status is unknown

Suspended: Monitoring suspended event

Resumed: Monitoring resumed event

For health check events:

Not Supported: Not Supported

Running: Running

Incomplete: Incomplete

Stopped: Stopped

Unconfirmed: Unconfirmed

Host Not Available: Host Not Available

Report

Displays whether there is a report associated with the event. If there is an associated report, clicking the report icon displays related reports. The meanings of items displayed and icons are described below. The icons vary by the product (PFM - Agent or PFM - RM).

n/a: There is no report (for an agent event or a health check event)

-: There is no report (for an alarm event)

: There is a report (Windows)

: There is a report (UNIX)

Alarm name

Displays an alarm status icon and the name of the alarm resulting from the event. For an agent event or a health check event, n/a is displayed.

Clicking the icon in the Alarm name column opens the Properties window, where you can check the content of the alarm definition.

(green): Normal status

(yellow): Warning status

(red): Abnormal status

#: Abnormal or warning status

#: This icon is displayed only if Always notify is selected in the alarm definition.

Alarm table

Displays the name of the alarm table to which the alarm resulting in the event belongs. For an agent event or a health check event, n/a is displayed.

Message

Displays the message output by the monitoring agent or the message defined in the New Alarm method in the Alarms window. The following lists the main messages that are displayed:

For agent events:

Startup: PFM - Agent or PFM - RM has started.

Shutdown: PFM - Agent or PFM - RM has stopped.

State change: The status of PFM - Agent or PFM - RM has changed.

State change(Unconfirmed): PFM - Manager could not confirm the agent alarm status, but it inferred the status of PFM - Agent or PFM - RM from the received alarm event.

State information: PFM - Manager correctly confirmed the agent alarm status.

State information(Unconfirmed): PFM - Manager could not confirm the agent alarm status.

Heartbeat timeout: The Agent Collector or Remote Monitor Collector service is busy or inactive.

Heartbeat detected: The Agent Collector or Remote Monitor Collector service has recovered from a busy or inactive status.

Monitored System Unavailable: Operating information could not be collected because the monitored system had stopped.

Monitored System Available: The monitored system recovered from not being able to collect operating information because the monitored system had stopped.

Suspend: Monitoring has been suspended.

Resume: Monitoring has been resumed.

Other than those mentioned above, a message that begins with KAV might be displayed.

If Heartbeat timeout is displayed, check the status of the PFM - Agent or PFM - RM. If a message that begins with KAV is displayed, see the chapter that explains messages in the PFM - Agent or PFM - RM manuals. There is no need to take any action for other messages because they are not error messages.

For alarm events:

Alarm updated/deleted

Alarm deactivated

The meaning of these messages depends on the setting of alarmCompatibleMode, an item in the initialization file (config.xml) used to set the PFM - Web Console operating environment.

For details about alarmCompatibleMode, see E. Initialization File (config.xml).

When alarmCompatibleMode does not exist:

Alarm updated/deleted: The alarm definition was updated or deleted.

Alarm deactivated: The alarm is no longer active.

When alarmCompatibleMode is true:

Alarm updated/deleted: The alarm definition was updated or deleted.

Alarm deactivated: The alarm is no longer active, or the alarm was updated and the previous alarm status was initialized.

When alarmCompatibleMode is false:

The meaning of the messages depends on the PFM - Manager version.

When the PFM - Manager version is 09-10-19 or later:

Alarm updated/deleted: The alarm definition was deleted.

Alarm deactivated: The alarm is no longer active, or the alarm was updated and the previous alarm status was initialized.

When the PFM - Manager version is earlier than 09-10-19:

Alarm updated/deleted: The alarm definition was updated or deleted.

Alarm deactivated: The alarm is no longer active.

State changed(No instance data): The status of an instance changed, but there is no data on the instance.

In the case of multi-instance records, the following processing occurs:

When a value in the abnormal or warning range is detected for at least one of the target instances

The user-defined message set during alarm definition is displayed in Message. If a measurement value for performance data is set to be displayed in the message text, the value of the instance exceeding the threshold is set.

When the status recovers from abnormal or warning to normal

If the function for measurement value output at alarm recovery is enabled, the user-defined message set during alarm definition is displayed in Message text. In addition, if you set that the measurement value of performance data is to be displayed in Message text, the current measurement value of the instance that triggered issuance of the last error or warning alarm is set.

If this function is disabled, a normal event is issued, but all instance values are within the normal range, and the value that triggered issuance of the event cannot be identified. As a result, nothing is displayed in Message text.

For details about the function for measurement value output at alarm recovery, see the chapter that explains operation monitoring with the use of alarms in the Job Management Partner 1/Performance Management User's Guide.

When you define multiple alarms in an alarm table and bind the alarm table to an agent, whether an agent event is issued depends on the result of evaluating the status of each alarm in the table. So if even one of multiple alarms is in an abnormal status, the status of the agent remains abnormal. Therefore, although an alarm event is issued to restore the status from abnormal to normal, an agent event might not be issued to restore the status if other alarms remain in an abnormal status. (Note that an alarm event and an agent event are not always issued at the same time).

For health check events:

Message text is displayed in HC: health-check-status format.

In addition, message text indicating the operating status of the service is displayed after the operating status of the agent. For details about display rules and examples of message texts, see the section that explains the health check agent in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Close

Closes the Event Monitor window.

(2) Show Options page

This page is used to set the display conditions for the View report page, including conditions for the agents whose events you want to display and the maximum number of display items. The display conditions set on this page remain in effect until the user logs out from PFM - Web Console.

The structure of this page is different when the business group access control functionality is enabled and when it is disabled.

The following figure shows the Event Monitor window (Show Options page).

Figure 1‒6: Event Monitor window (Show Options page) when the business group access control functionality is enabled

Figure 1‒7: Event Monitor window (Show Options page) when the business group access control functionality is disabled

The following describes the items displayed on this page:

Close button

Closes the Event Monitor window.

OK button

Accepts the settings and returns to the View report page. The events on this page are displayed together with the display conditions you set.

Cancel button

Discards the specified settings and returns to the View report page.

Filter Settings

Specifies the agents whose events are to be displayed.

Display all agents

Select this check box to display all agents' events. The default is that this check box is selected.

If you clear this check box, no events will be displayed unless you set at least one agent in Visible agents.

Select business group

Displayed when the business group access control functionality is enabled. If Display all agents is selected, this pull-down menu is not available.

Set this item if you want to filter the agents that are displayed in Hidden agents according to business group. The following items are available on the pull-down menu:

All business groups

Select this item to display all agents.

Business group name

Select this item to display only agents to which business groups are assigned. Only business groups with the reference privilege are displayed.

Unassigned

Select this item to display agents to which no business groups are assigned. This item is displayed only when the user has logged in as a system user.

Hidden agents

Lists the agents that are currently not subject to event display. If you want to include any of these agents in the event displays, select the applicable agent and then use the arrow button (/) to move it to Visible agents.

Visible agents

Lists the agents that are currently subject to event display. If you want to remove any of these agents from the event displays, select the applicable agent and then use the arrow button (/) to move it to Hidden agents.

Arrow buttons (///)

Move agents between Hidden agents and Visible agents. Use the button to move agents from Hidden agents to Visible agents, and use the button to move agents from Visible agents to Hidden agents.

You can also use the arrow button () to move all agents in Hidden agents to Visible agents and the arrow button () to move all agents in Visible agents to Hidden agents. These arrow buttons (/) are displayed when the business group access control functionality is enabled.

Color Settings

Applies color-coding by status to the events displayed in the Event Monitor window. Different colors can be set for the statuses normal, warning, and abnormal.

Event color scheme

From the pull-down menu, select a scheme for color-coding the events displayed in the Event Monitor window by event status. When a color scheme is selected, the background of the rows displaying events is color-coded according to the event status. The default is None.

Available selections are as follows:

None (no color-coding)

Pastel colors

For agent events and alarm events:

Status

Color

Normal

Light green (R=204, G=255, B=204)

Warning

Light yellow (R=255, G=255, B=204)

Abnormal

Light red (R=255, G=204, B=255)

Inactive or status unknown

Light green (R=204, G=255, B=204)

Monitoring suspended

Light gray (R=224, G=224, B=224)

Monitoring resumed

Light blue (R=204, G=224, B=255)

For health check events and the health check status:

Status

Color

Not Supported

Light yellow (R=255, G=255, B=204)

Running

Light green (R=204, G=255, B=204)

Monitoring suspended

Light gray (R=224, G=224, B=224)

Incomplete

Light orange (R=255, G=224, B=204)

Stopped

Light orange (R=255, G=224, B=204)

Unconfirmed

Light orange (R=255, G=224, B=204)

Host Not Available

Light red (R=255, G=204, B=255)

Bright colors

For agent events and alarm events:

Status

Color

Normal

Green (R=000, G=255, B=000)

Warning

Yellow (R=255, G=255, B=000)

Abnormal

Red (R=255, G=000, B=000)

Inactive or status unknown

Green (R=000, G=255, B=000)

Monitoring suspended

Gray (R=204, G=204, B=204)

Monitoring resumed

Blue (R=000, G=000, B=255)

For health check events and the health check status:

Status

Color

Not Supported

Yellow (R=255, G=255, B=000)

Running

Green (R=000, G=255, B=000)

Monitoring suspended

Gray (R=128, G=128, B=128)

Incomplete

Orange (R=255, G=128, B=000)

Stopped

Orange (R=255, G=128, B=000)

Unconfirmed

Orange (R=255, G=128, B=000)

Host Not Available

Red (R=255, G=000, B=000)

Reference note

When you select Bright colors, the text color is white for Abnormal, Monitoring suspended, Monitoring resumed, Incomplete, Stopped, Unconfirmed, and Host Not Available. The text color is black for other cases.

Event Settings

Sets the maximum number of events (records) to be displayed in the Event Monitor window.

Maximum number of events to display

Enter an integer in the range of 1 to 999. The default is 256.

1.3.3 Change Password window

The Change Password window is used to change the login user's password. To display this window, in the Main window, from the menu bar frame, choose Change Password.

The following figure shows the Change Password window.

Figure 1‒8: Change Password window

The following describes the displayed items:

Close button

Closes the Change Password window.

Current password

Enter your current password (before change).

Password and Confirm new password

Specify a new password with 1 to 16 characters. The permitted characters are the alphabetic characters (both upper case and lower case), numeric characters, and symbols (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ] \ ^ _ ` { | } ~ space). The alphabetic characters are case sensitive.

Any leading and trailing spaces entered are deleted.

OK button

Applies the specified settings and closes the Change Password window. When this button is clicked, the specified settings take effect.

Cancel button

Discards the specified settings and closes the Change Password window.

Note

For Performance Management, it is recommended that a password consist of at least six characters and include a mixture of alphabetic characters, numeric characters, and symbols. If the password you enter is not consistent with these recommendations, such as a password consisting of only alphabetic characters, only numeric characters, or fewer than six characters, a confirmation message will be displayed. A message will also be displayed if the entered password is the same as your user name.

1.3.4 Environment Settings window

The Environment Settings window is used to set the refresh interval when window displays are to be refreshed automatically. To display this window, in the Main window, from the menu bar frame, choose Environment Settings.

The following windows and items are refreshed automatically at the refresh interval set in this window:

Event Monitor window

Monitoring agent status and health check status in the Agents window

Alarm status in the Alarm Status window

System Operational Status Summary window

The following figure shows the Environment Settings window.

Figure 1‒9: Environment Settings window

Close

Closes the Environment Settings window.

Automatic refresh

Sets the refresh interval if you wish to have window displays refreshed automatically.

Refresh interval

Set a value in the range 10 to 3600 (seconds). The default is 60 seconds.

OK button

Accepts the specified settings and closes the Environment Settings window. Clicking this button enables the settings.

Cancel button

Discards the specified setting and closes the Environment Settings window.

1.3.5 About window

The About window displays the PFM - Web Console version information. This window opens as a new window when you choose the About menu from the menu bar frame in each PFM - Web Console window.

The following figure shows the About window.

Figure 1‒10: About window

1.3.6 Help window

The Help window displays the Performance Management manuals. Choosing Help from the menu bar frame in any PFM - Web Console window opens a separate Help window.

The following figure shows the Help window.

Figure 1‒11: Help window

The following describes the displayed items:

Close

Closes the Help window.

Common

Enables you to view the following manuals:

Job Management Partner 1/Performance Management Planning and Configuration Guide (HTML/PDF version)

Job Management Partner 1/Performance Management User's Guide (HTML/PDF version)

Job Management Partner 1/Performance Management Reference (HTML/PDF version)

Agents

Enables you to view the PFM - Agent or PFM - RM manuals.

Note

Any manual must have been set up in order to be displayed from PFM - Web Console's Help window. For details about how to perform setup, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

1.4 Agents window

The Agents window is used to display reports related to agents and to check alarm status and event history. By using the Quick Guide, you can create brief reports or set up alarms.

You also use this window to add new agents, edit a monitoring agents tree, and bind agents and an alarm table.

To display this window, in the navigation frame in any PFM - Web Console window, click the Agents tab.

The following figure shows the Agents window.

Figure 1‒12: Agents window (when the business group access control functionality is disabled)

The following describes the displayed items:

Menu bar frame

Displays a menu that is common to all windows.

For details, see the description of the menu bar frame in 1.3 Main window.

Navigation frame

Displays hierarchically the agents managed by Performance Management.

You can select the format for displaying the agents tree.

Except for the following items, the items are the same as the items in the navigation frame of the Main window. For details, see 1.3 Main window.

Display format

Enables you to select the display format for the agents tree. The available display formats are as follows:

Products

Displays the agents tree grouped by PFM - Agent or PFM - RM products.

User Agents

Displays any Agents tree created by the login user.

Multi select

Selecting this check box enables you to select multiple target agents from the agents tree to execute the same operation on all the selected agents. This check box is cleared as a default.

Tip

If you click the root or a folder when Multi select is selected, you can select or clear all nodes under the root or selected folder. If you click a folder in which all or some nodes are cleared, all nodes under the folder are selected. However, if you click a folder that contains only selected nodes, all of the nodes under the folder are cleared. If there are any subfolders under the folder you click, the status of the nodes contained in the subfolders also changes. In short, you can switch the selection status of all nodes contained in a tree by clicking the root.

Update automatically

When you select this check box, the agent status and the health check status displayed in the navigation frame are automatically updated. This check box is selected by default.

Display separately by business group

Displayed when the business group access control functionality is enabled, and Products is set for Indication Settings. If you select this item, agent trees are displayed separately by business group. By default, this check box is cleared.

Text box

Use this text box to filter agents by keywords. Specify a character string of 1 to 1,024 characters to filter the agents that will be displayed. To perform a multi-keyword search by using AND or OR, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters agents by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

AND

Select this option button to perform an AND search.

OR

Select this option button to perform an OR search.

Agents tree:

The display differs depending on whether you select Products or User Agents in Display format:

When Products is selected in Display format

The root is Products. On the second level of the hierarchy, folders with the product names of PFM - Agent or PFM - RM are displayed in alphabetical order. The agents are displayed on the third level of the hierarchy. For each agent, its service ID is displayed. In the case of a product with multiple data model versions, service-ID + (data model version) is displayed.

For details about service IDs, see the section that explains the naming rules of services in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

When User Agents is selected in Display format

The root is User Agents (login-user-name). Levels 2 through n of the hierarchy display the folders created by the login user. Each monitoring agent is displayed at its applicable hierarchical level. The name of each agent is shown as service-ID + (data-model-version).

For details about service IDs, see the section that explains the naming rules of services in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

When Products is selected in Display format, if PFM - Agent or PFM - RM has not been registered with a monitoring agent for which a PFM - Agent or PFM - RM other than PFM - Agent for Platform has been installed (the jpcconf agent setup command has not been executed), that agent is displayed under the folder named Unknown. When you add a new PFM - Agent or PFM - RM product, you must restart the Performance Management service. After the restart, product information is acquired again when PFM - Web Console is accessed.

Icons

An icon is displayed to the left of each component of the Agents tree. For details about icons, see Table 1-9 Configuration component icons and their meaning.

These icons have the following meanings:

: Indicates the root.

: Indicates a folder.

: Indicates a monitoring agent.

: Indicates the Remote Monitor Collector service.

: Indicates a remote agent.

: Indicates a group agent.

Icons also indicate each agent's status.

: Normal status

: Warning status

: Abnormal status

: Monitoring suspended status

: Indicates that the status of the agent is either of the following, and that there is no substance:

- Agent service information was deleted, after which PFM - Web Console was updated by the jpctool service sync command.

- Because of configuration changes in a business group, the user's reference privilege for agents was deleted.

This icon is displayed only when User Agents is selected in Indication Settings. You cannot perform any agent operation for an agent with a translucent icon.

A health check status icon is displayed to the left of folder icons and agent icons. Note that group agents and agents without substance are not included in health checks. Therefore, the Not Supported icon is always displayed as the health check status for them.

For details about the health check status, see the chapter that explains error detection of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

: Not Supported

: Running

: Monitoring suspended

: Incomplete

: Stopped

: Unconfirmed

: Host Not Available

The status of a folder icon reflects the status of all the lower-level agents. As the health check status, only the status with the highest priority in a lower level of the folder appears. The display order by priority is as follows:

Host Not Available > Unconfirmed > Stopped > Incomplete > Monitoring suspended > Running > Not Supported

You can use config.xml to change the priority of the lower-level status propagated to a folder. For details about config.xml, see E. Initialization File (config.xml).

The displayed statuses are updated at the following times:

When Refresh is clicked in the navigation frame.

When a monitoring agent is clicked in the agents tree.

When the results of the operation selected in the method frame are displayed.

If Update automatically was selected, the statuses are refreshed automatically.

Note

For PFM - RM or PFM - Agent other than PFM - Agent for Platform, if you have not used the jpcwagtsetup command to register PFM - Agent or PFM - RM, icons for the reports will not be correctly displayed. To correctly display the icons, use the jpcwagtsetup command to register PFM - Agent or PFM - RM, and then restart PFM - Web Console.

Method frame

The agent name selected in the navigation frame is displayed as the title of the method frame.

When multiple agents are selected, the agents are displayed in the order in which they were selected. When four or more agents are selected, the number of selected agents is displayed instead of the agent names. If some agent names are duplicated, the number of unique agent names is displayed. Clicking the link for the number of agents opens the List of Selected Agents window as a new window.

Figure 1‒13: List of Selected Agents window

The following describes the items in the List of Selected Agents window:

List of Selected Agents

Lists the agent names selected in the navigation frame.

Close button

Closes the List of Selected Agents window.

The following describes the items displayed in the method frame of the Agents window. Displays the operations that can be executed on each agent in the agents tree. The operation items that are displayed depend on the selected object.

Display Summary

Lists the operating statuses of the agents selected in the navigation frame.

Quick Guide

Enables you to create brief reports or set up alarms.

Display Reports

Displays reports related to the selected monitoring agent. This item is displayed when a monitoring agent is selected in the navigation frame. You can select multiple agents of the same product.

When you choose this item, the View Report window appears. By switching the reports tree and the bookmarks tree in the information frame, you can display the report of a specific bookmark or combination bookmark. However, note that if you select a report from the bookmarks tree, the monitoring agent selected in the navigation frame is ignored.

Display Alarm Status

Displays the alarm status in the alarm table bound to (associated with) the selected monitoring agent. This item is displayed when only one monitoring agent is selected in the navigation frame. Choosing this item displays the Alarm Status window.

Properties

Displays the selected monitoring agent service (Agent Collector and Remote Monitor Collector services) or the properties of the remote agent or group agent. This item is displayed when only one monitoring agent is selected in the navigation frame. Choosing this item displays the Service Properties window, which displays the same information that is displayed in the Service Properties window displayed from the Services window. However, when the Properties window is displayed from this item, properties cannot be changed.

Event History

Displays event log information for the monitoring agents. Choosing this item displays the Event History window. If a monitoring agent is selected in the Navigation frame, event log information for the selected monitoring agent is displayed; if no agent is selected, event log information for all the monitoring agents is displayed.

Alarm Table Bind Settings (When the functionality for binding multiple alarm tables is enabled)

Binds (associates) or unbinds (releases the association between) an alarm table and monitoring agents when PFM - Web Console 09-00 or later is used. This item is displayed when a monitoring agent is selected in the Navigation frame. This item is displayed only when the login user has the administrator user permission.

You can select multiple agents for the same product. You can bind or unbind multiple alarm tables to one monitoring agent.

Choosing this item displays the Alarm Table Bind Settings [Select Alarm Tables] window.

Bind Alarm Table (When the functionality for binding multiple alarm tables is disabled)

Binds (associates) an alarm table and monitoring agents. This item is displayed when a monitoring agent is selected in the Navigation frame. This item is displayed only when the login user has the administrator user permission.

You can select multiple agents of the same product. Note that only one alarm table can be bound to a monitoring agent.

If this operation is executed on an agent to which an alarm table has already been bound, the more recent alarm table binding takes effect.

Choosing this item switches to the Bind Alarm Table [Select Alarm Tables] window.

UnBind Alarm Table

Unbinds (releases association between) an alarm table and monitoring agents. This item is displayed when a monitoring agent is selected in the Navigation frame. This item is displayed only when the login user has the administrator user permission.

You can select multiple agents for the same product. Choosing this item displays a message box for confirming execution of the unbinding operation.

Edit Agent Tree

Edits the agents tree. Choosing this item displays the Edit Agent Tree window, in which you can create new components and copy, delete, and rename folders in the Agents tree.

Register Bookmark

Registers a report located in the agent tree as a bookmark. Choosing this item opens the Regist Bookmark > Select Report window, in which clicking a report opens the Bookmark window.

Process Monitoring Settings

Specifies the process monitoring settings for PFM - Agent for Platform and PFM - RM for Platform. Choosing this item switches to the Process Monitoring Settings window.

Monitoring Suspension Settings

Suspends or resumes monitoring. Choosing this item switches to the Monitoring Suspension Settings window.

Information frame

Displays the results of the operation selected in the method frame on the object(s) selected in the Navigation frame.

Immediately after you log in, the operation status is listed for all agents displayed when User Agents is selected in Display format (Display Summary).

1.4.1 Transitions from the Agents window

The following shows the window transitions from the Agents window:

Figure 1‒14: Window transitions from the Agents window

The following figure shows the window transitions from the Quick Guide window.

Figure 1‒15: Window transitions from the Quick Guide window

The following figure shows the window transitions from the View Report window.

Figure 1‒16: Window transitions from the View Report window

The following figure shows the window transitions from the Edit Agents window.

Figure 1‒17: Window transitions from the Edit Agents window

The following shows the window transitions from the Process Monitoring Settings window.

Figure 1‒18: Window transitions from the Process Monitoring Settings window

Figure 1‒19: Window transitions from the Monitoring Suspension Settings window

1.4.2 Display Summary window

The System Operational Status Summary window lists the operating status of the agents selected in the navigation frame. To display this window in the information frame, click the Display Summary button in the method frame in the Agents window.

The following figure shows the System Operational Status Summary window.

Figure 1‒20: Display Summary window

The System Operational Status Summary window consists of the following four areas:

Server Operational Status area

Agent Operational Status area

Agent Alarm Status area

Event area

The following describes the displayed items:

Refresh

Refreshes the System Operational Status Summary page.

Stop

Clicking this switches the menu to Print.

Print

Clicking this opens a separate window for printing a summary. The following shows the System Operational Status Summary Print window.

Figure 1‒21: System Operational Status Summary Print window

Display the Operational Status from the result of the refine search

From the results of filtering in the navigation frame, specify whether to include hidden agents in the summary display. When the system operational status summary functionality stops, this check box is no longer available. However, its selection state remains the same.

When selected:

Displays a summary of the operating status of the agents displayed in the navigation frame. Hidden agents are not included.

When cleared:

Displays a summary of the operating status of all agents under the directory selected in the navigation frame. Hidden agents are included.

Each area is described below.

(1) Server Operational Status area

This area shows in a graph the operational statuses of the servers (the number of servers running, stopped, unknown, and monitoring suspended) under the selected directory. Also, the number of running and stopped servers are listed in a table.

Clicking the Server Operational Status menu expands or closes the display.

Server operational status (pie graph)

The operating statuses of servers are shown for the following items:

Running

Stopped

Unknown

Monitoring suspended

Server operational status (list)

The operating statuses of servers are listed for the following items:

Running

Stopped

Total

Running rate

If Stopped is 1 or more, clicking the number displays the Stopped Host List window. This enables you to check the host name of the stopped server. The following figure is an example of the Stopped Host List window.

Figure 1‒22: Stopped Host List window

The following describes the displayed items in the Stopped Host List window:

Stopped Host List

Lists the host names of servers that have stopped.

Close button

Closes the Stopped Host List window.

(2) Agent Operational Status area

This area shows in a graph the operational statuses of the agents (the number of agents running, stopped, unknown, and monitoring suspended) under the selected directory. Also, the number of running and stopped agents are listed in a table.

Clicking the Agent Operational Status menu expands or closes the display.

User tree view

If you select this check box, the operating status will be displayed for each folder that was created in the agents tree by the login user.

If in the agents tree of the navigation frame, Products is selected in Display format, this check box is not displayed and, in the Agent operational status list, the operating status is displayed for the products tree only.

Product type view

If you select this check box, the operating status will be displayed for each group of folders that was grouped together for each PFM - Agent or PFM - RM product.

If in the agents tree of the navigation frame, Products is selected in Display format, this check box is not displayed and, in the Agent operational status list, the operating status is displayed for the products tree only.

Agent operational status (pie graph)

The operating statuses of agents are shown for the following items:

Running

Stopped

Unknown

Monitoring suspended

Agent operational status (list)

The operating statuses of agents are listed for the following items:

Running

Stopped

Total

Running rate

(3) Agent Alarm Status area

This area shows in a graph and table the alarm monitoring statuses of the agents (the numbers of normal, warning, abnormal, and monitoring suspended statuses) under the selected directory. The alarms for which Always notify is not selected are subject to agent alarm monitoring.

Clicking the Agent Alarm Status menu expands or closes the display.

Agent Alarm Status (pie graph)

The alarm monitoring statuses of agents are shown for the following items:

Normal

Warning

Abnormal

Monitoring suspended

Agent Alarm Status (list)

The alarm monitoring statuses of agents are listed for the following items:

Normal count

Warning count

Abnormal count

State ratio

(4) Event page

Lists outstanding agent events and alarm events only, under the selected directory.

The displayed items of the list are shown below. For details about the meanings of displayed icons, see 1.3.2 Event Monitor window.

Icon indicating the event type

Date and time

Agent

Report

Alarm

Message text

1.4.3 Quick Guide window

This window enables you to create brief reports or set up alarms. To display this window, from the method frame in the Agents window, click the Quick Guide button.

The following figure shows the Quick Guide window.

Figure 1‒23: Quick Guide window

The following describes the displayed items:

Refresh

Refreshes the information displayed in the Quick Guide window.

Keywords to find:

Entering a maximum of 64 characters for the search keywords (including spaces used as delimiters) and then clicking the Search Fields button opens the Quick Guide > Search Fields window with the keywords search result displayed. For details about search fields, see (1) Quick Guide > Search Fields window.

However, when the data model description file has not been stored, the Search Fields button is not displayed. If the data model description file has not been stored, see the setup procedure for PFM - Web Console to register PFM - Agent or PFM - RM. For details, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Search Fields button

Displays the Quick Guide > Search Fields window.

List of records

Displays a list of records in alphabetical order. The following items are displayed.

Record name

Displays the record name.#

Clicking a record name or to the left of the record name expands the list of fields. The following figure shows the Quick Guide window with the expanded field list.

Figure 1‒24: Quick Guide window (with the expanded field list)

The following shows the items that can be expanded.

Table 1‒10: Items displayed in the field list

Item

Value that is displayed

This is a single-instance record or This is a multi-instance record

Displays the field name.

This is a single-instance record

Displayed when the corresponding record is a single-instance record.

This is a multi-instance record

Displayed when the corresponding record is a multi-instance record.

Field name and Description are also displayed as a list of ODBC key fields.

Field name

Displays the field name (excluding the ODBC key field).

Action

Displays the type of report or alarm by using an icon. If there is no icon to be displayed, n/a is displayed.

: Realtime report

This icon is displayed if the field is not Fields added only when data is stored in the Store database.#

Clicking this icon opens the applicable View Report window as a new window.

: Historical report

This icon is displayed if any of the corresponding records of all the specified agents include Yes for Log, and the field is not Fields added only when data is stored in the Store database.

Note that this icon is always displayed if false is specified for quickGuideHideReportIcon in the initialization file (config.xml).

Clicking this icon opens the applicable View Report window as a new window.

: Alarm

This icon is displayed if the connection user is an administrator user, the field is not Fields added only when data is stored in the Store database, and the field is not any of the following: KeyDate type, DateTime type, or time_t type.

Clicking this icon displays the Quick Guide > Create Alarm window in the information frame.

For details , see 1.4.3(2) Quick Guide > Create Alarm window.

Format

Displays the attribute of the corresponding field by using an icon.

: Numeric attribute

: String attribute

Description

Displays a description of the corresponding field.

If there is no description, (No explanation provided) is displayed.

Close button

Closes the list of the expanded fields.

#

If realtime reports are set to be displayed in the re-schedule mode, records whose property value for Over 10 Sec Collection Time is set to Yes cannot be displayed in the realtime reports, and a message that indicates the information is displayed below the relevant record names.

At this time, if the value for quickGuideHideReportIcon in the initialization file (config.xml) is true (or this parameter is not specified), the realtime report icon is not displayed for Action in the field list. For details about the re-schedule mode, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Record ID

Displays the record ID of the corresponding record.

Information stored in record

Displays the description of the corresponding record.

If there is no description, (No explanation provided) is displayed.

Log

Displays whether the corresponding record of the agent is set to record to the Agent Store database service.

Yes: Record

If multiple agents are specified and the recording is set for any of the agents, Yes is displayed.

No: Do not record

n/a: Information cannot be obtained (such as when a connection to the specified agent server is not available).

If JP1/ITSLM is linked, the recording setting is displayed as shown in the following table according to the combination of the JP1/ITSLM settings and the Performance Management settings.

JP1/ITSLM setting

Performance Management setting

Content of Log

Starting monitoring

Recording performance data

Recording the Store database

Performed

Performed

Yes

Performed

Not performed

Yes

Performed

Not performed

Performed

Yes

Performed

Not performed

Not performed

No

Not performed

Performed

Yes

Not performed

Not performed

No

(1) Quick Guide > Search Fields window

In this window, you can search fields. You can search a maximum of 50 fields by default.

You can set the maximum limit of fields to search, in searchLimit of the initialization file (config.xml). For details about the initialization file (config.xml), see E. Initialization File (config.xml).

The following figure shows the Quick Guide > Search Fields window.

Figure 1‒25: Quick Guide > Search Fields window

The following describes the displayed items:

Cancel button

Displays the Quick Guide window again.

Keywords to find

Enter no more than 64 characters for the search keywords (including spaces as delimiters). Observe the following precautions related to a search:

To perform a multi-keyword search by using AND, delimit keywords by using a single-byte or two-byte space.

An OR search cannot be performed.

Wildcard characters cannot be used.

A keyword search that consists only of spaces cannot be specified.

Spaces entered at the beginning and ending of a keyword are excluded.

If the search keyword includes spaces, the search will not be performed as intended.

The search is not case sensitive.

In the search keyword, a two-byte character and a single-byte character are recognized as different characters.

A search keyword that includes a line feed code cannot be entered.

After entering the search keyword, click the Search button. The search results will be displayed.

Search results are displayed, depending on the selection in the Records to search pull-down menu, in the following different windows:

If --All records-- is selected in Records to search

The search results are displayed in the "Search results: number-of-records record(s)" window.

If --Records where Log=Yes-- is selected in Records to search

The search results are displayed in the "Search results: number-of-records record(s)" window.

If a record name is selected in Records to search

The search results are displayed in the "Search results: List of number-of-fields field(s) found in record record-name" window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records to search. By default, --All records-- is displayed.

In the pull-down menu, the following items are displayed:

--All records--

Select this item to search all records.

--Records where Log=Yes--

Select this item to search records in which Yes is set for the Log property. This item is displayed in the pull-down menu if the agent is running when this window opens.

List of record names of the selected agent

Displays a list of record names of the selected agent in alphabetical order.

(a) Search results: number-of-records record(s) window

This window displays the number of fields found by a search for each record when --All records-- was selected in Records to search in the Quick Guide > Search Fields window. In the search results, the record names are displayed in alphabetical order. The following figure shows the Search Results: number-of-records record(s) window.

Figure 1‒26: Search Results: number-of-records record(s) window

The following describes the displayed items:

Cancel button

Returns to the Quick Guide window.

Keywords to find

Enter search keywords. For details, see 1.4.3(1) Quick Guide > Search Fields window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records that you want to search. For details, see 1.4.3(1) Quick Guide > Search Fields window.

Record name

A record name is followed by the following information:

Number of fields that correspond to the search result

Description of the record

If there is no description, (No explanation provided) is displayed.

Instance type

(This record is a single-instance record.) or (This record is a multi-instance record.) is displayed.

Clicking the menu of a record name lists the corresponding fields of the selected record in the "Search results: List of number-of-fields field(s) found in record record-name" window.

(b) Search results: List of number-of-fields field(s) found in record record-name window

A list of fields is displayed as a search result. The following figure shows the Search results: List of number-of-fields field(s) found in record record-name window.

Figure 1‒27: Search results: List of number-of-fields field(s) found in record record-name window

The following describes the displayed items:

Cancel button

Returns to the Quick Guide window.

Keywords to find

Enter search keywords. For details, see 1.4.3(1) Quick Guide > Search Fields window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records that you want to search. For details, see 1.4.3(1) Quick Guide > Search Fields window.

Go to Record List button

Displays the "Search results: number-of-records record(s)" window again. This button is displayed only if you moved to this window from the "Search results: number-of-records record(s)" window.

Field name

The field names are listed in alphabetical order. The search keyword portion is displayed in bold.

Action

The following information is displayed. If there is no icon to be displayed, n/a is displayed.

Table 1‒11: Icons displayed in the Action field

Icon

Meaning

Display condition

Action taken when the icon is clicked

Realtime report

The field is not Fields added only when data is stored in the Store database.

Note that, if all of the following conditions are met, this icon is not displayed:

The value for quickGuideHideReportIcon in the initialization file (config.xml) is true (or this parameter is not specified).

All of the specified agents are set to display realtime reports in the re-schedule mode.

The value for the Over 10 Sec Collection Time property is Yes.

The applicable View Report window opens as a new window.

Historical report

At least one of the corresponding records of all the specified agents includes Yes for Log.

Note that this icon is always displayed if false is specified for quickGuideHideReportIcon in the initialization file (config.xml).

The applicable View Report window opens as a new window.

Alarm

All of the following conditions are satisfied:

The connection user is an administrator user.

The field is not Fields added only when data is stored in the Store database.

The field is not one of the following:

KeyDate type

DateTime type

time_t type

The Quick Guide > Create Alarm window is displayed in the information frame.

For details, see 1.4.3(2) Quick Guide > Create Alarm window.

Format

Displays the attribute of the corresponding field by using the following icons:

: Numeric attribute

: String attribute

Description

Displays description of the field. Bold characters indicate the characters that match with the search keyword.

(2) Quick Guide > Create Alarm window

This window, which is displayed when you click the icon in the Quick Guide window, enables you to create alarms.

The following figure shows the Quick Guide > Create Alarm window.

Figure 1‒28: Quick Guide > Create Alarm window

The following describes the displayed items:

Cancel button

Clears the information area. If the information in the Quick Guide > Create Alarm window has been changed, a dialog box appears, confirming whether the settings can be discarded.

< Back button

Returns to the Quick Guide window. If you made changes in the Quick Guide > Create Alarm window, a dialog box asking if it is OK to discard the settings appears.

Finish button

Creates an alarm table and completes the alarm creation. You can click the Finish button only if all necessary information has been entered in the Quick Guide > Create Alarm window.

When there is a problem with the entered information:

An error message is displayed on top of the window.

When there is no problem with the entered information:

A dialog box appears, confirming whether to bind the alarm table. Clicking the OK button registers the alarm, binds the alarm table, and opens the Quick Guide > Create Alarm > View Results window.

General settings

Alarm table name

Specify the alarm table name by a character string of no more than 64 bytes. Character types that can be specified are shown below. You cannot specify a name that begins with PFM (in both upper case and lower case).

Two-byte characters

Alphanumeric characters

The following single-byte characters: % - ( ) _ . / @ [ ] and blank spaces

The following character string is displayed by default:

product-name Alarms 1

Alarm name

Specify the alarm name by a character string of no more than 20 bytes. Character types that can be specified are shown below. If you specify an invalid character for the alarm name, that character will be replaced with an underscore (_).

Two-byte characters

Alphanumeric characters

The following single-byte signs: % - ( ) _ . / @ [ ] and blank spaces

By default, the field name displayed in the Quick Guide window is displayed. In a character string that is more than 20 bytes, only the characters in the first 20 bytes are used, and the following characters are omitted.

Alarm message

Specify the message you want to display in the Event Monitor window by a character string that consists of single-byte or two-byte characters and that is no more than 255 bytes.

The following character string is displayed by default:

field-name is %CVS

Alarm-message preview

Displays the message you specified in Alarm message after its variable section is replaced with a string.

Record

Displays the record name specified in the Quick Guide window. You cannot edit the record name.

Description

Clicking this menu displays or hides the description of the record.

This menu is not displayed when the data model description file has not been stored for the product to which the corresponding record belongs.

Field

Displays the field name specified in the Quick Guide window. You cannot edit the field name.

Description

Clicking this menu displays or hides the description of the field.

This menu is not displayed when the data model description file has not been stored for the product to which the corresponding field belongs.

Alarm conditions

Realtime Reports or Historical Reports

Clicking the icon opens the View Report window as a new window in which reference values for creating an alarm are displayed. If no agent is operating, no reports are displayed.

: Realtime report. Note that, if the value for quickGuideHideReportIcon in the initialization file (config.xml) is true (or this parameter is not specified), and all of the specified agents are set to display realtime reports in the re-schedule mode, this icon is not displayed for the records where the value for the Over 10 Sec Collection Time property is Yes.

: Historical report. This icon is not displayed if Log, No, or n/a is displayed for all the records of all agents.

However, if false is specified for quickGuideHideReportIcon in the initialization file (config.xml), this icon is always displayed.

Abnormal condition

Specify when to report an abnormal alarm by using a conditional expression.

Item

Value that is displayed

Field name

Displays the field name specified in the Quick Guide window.

You cannot edit this name.

Operator

Select an operator to use in the conditional expression from the followings:

=

<

<=

>

>=

<>

Threshold value

In the text box, enter the threshold value that is used for evaluation of an abnormal (red) alarm. You cannot omit this entry.

Character types that can be specified:

Integer and decimal fraction using two-byte or single-byte characters (excluding control characters)

Character string length that can be specified:

The length of this string or PQL byte (created from the combination of this value and the threshold value set in Warning condition) must be no more than 749 bytes.

Input format of the threshold value

Displays the data format of the threshold value that can be input according to the field name.

Warning condition

Specify when to report a warning alarm by using a conditional expression.

Item

Value that is displayed

Field name

Displays the field name specified in the Quick Guide window.

You cannot edit this name.

Operator

Displays an operator specified in Abnormal condition.

You cannot edit this item.

Threshold value

In the text box, enter the threshold value that is used for evaluation of a warning (yellow) alarm. You cannot omit this entry.

Character types that can be specified:

Integer and decimal fraction using two-byte or single-byte characters (excluding control characters)

Character string length that can be specified:

The length of this string or PQL byte (created from the combination of this value and the threshold value set in Abnormal condition) must be no more than 749 bytes.

Input format of the threshold value

Displays the data format of the threshold value that can be input according to the field name.

1.4.4 Display Reports > Select Report window

The Select Reports window is used to select from the reports tree a report that is to be displayed. To display this window, from the method frame in the Agents window, choose Display Reports.

The information displayed in the window varies according to whether Reports or Bookmarks is selected in Tree type. By default, Reports is selected. The following describes the details of each selection.

(1) When Reports is selected in Tree type

The following figure shows the Display Reports > Select Report window when Reports is selected for Tree type.

Figure 1‒29: Display Reports > Select Report window (When Reports is selected for Tree type)

The following describes the displayed items:

Refresh

Refreshes the information displayed in the contents area. Refreshing the information does not change the selection status in the Reports tree.

OK button:

This button is not available when Multi select is selected. The button is activated when you select a report in the reports tree in the contents area. Choosing this button displays the report selected in the reports tree in the contents area in a separate window. If multiple reports are selected, each report is displayed in a separate window.

Tree type

You can select the information to be displayed in the contents area from the pull-down menu.

Multi select

Selecting this check box enables you to select multiple reports from the reports tree. By clicking the root or a folder, you can select all the reports under the root or folder. By default, this check box is cleared.

Note that the check box is not displayed if multiple monitoring agents are selected in the navigation frame in the Agents window.

Tip

If you click the root or a folder when Multi select is selected, you can select or clear all nodes under the root or selected folder. If you click a folder in which all or some nodes are cleared, all nodes under the folder are selected. However, if you click a folder that contains only selected nodes, all of the nodes under the folder are cleared. If there are any subfolders under the folder you click, the status of the nodes contained in the subfolders also changes. In short, you can switch the selection status of all nodes contained in a tree by clicking the root.

Text box

Use this text box to filter reports by keywords. Specify a character string of 1 to 1,024 characters to filter the reports that will be displayed. To perform a multi-keyword AND or OR search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters reports by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

AND

Select this option button to perform an AND search.

OR

Select this option button to perform an OR search.

Contents area

Displays the Reports tree. The default is that System Reports is displayed as the root. Under System Reports, a folder for each PFM - Agent or PFM - RM program is displayed. Each folder contains the reports provided as the monitoring template. If the logged-on user has created his or her own reports, two levels, User Reports and System Reports, are displayed. The created folders and reports are displayed under User Reports.

(2) When Bookmarks is selected in Tree type

The following figure shows the Display Reports > Select Report window when Bookmarks is selected in Tree type.

Figure 1‒30: Display Reports > Select Report window (when Bookmarks is selected in Tree Type)

The following describes the displayed items:

Refresh

Updates the information displayed in the contents area to the latest status. Updating the displayed information does not change the selection status in the reports tree.

Tree type

You can select the information to be displayed in the contents area from the pull-down menu.

Filter selected agents

To filter displayed bookmarks by the agents selected in the navigation frame, select Filter selected agents. Bookmarks that contain an agent name selected in the navigation frame at that time are displayed. To cancel filtering, clear Filter selected agents.

Text box

Use this text box to filter bookmarks by keywords. Specify a character string of 1 to 1,024 characters to filter the bookmarks that will be displayed. To perform a multi-keyword AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters bookmarks by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Contents area

The bookmarks tree appears. By default, Bookmarks is displayed as the root. The bookmarks or the combination bookmarks created by the logged-on user are displayed under Bookmarks.

When you select bookmarks from the bookmarks tree in the contents area, the reports that are registered as bookmark destinations are displayed in separate windows.

1.4.5 View Report window

The View Report window displays a report. The window is displayed when you perform any of the operations below. Note that if you log in as an ordinary user or a business group ordinary user when off is specified for editReportByOrdinaryUser in the initialization file (config.xml), Baseline, Bookmarks, and Save Report Definition are not displayed. For details about the initialization file (config.xml), see E. Initialization File (config.xml).

Select the Display Reports method in the Agents window, select Reports from Tree Type, and then click the report name in the Display Reports > Select Report window.

Select the Display Reports method in the Agents window, select Bookmarks from Tree Type, and then click the bookmark or the report name in the Regist Bookmark > Select Report window. Note that if you click a combination bookmark in the Regist Bookmark > Select Report window, a combination report is displayed.

Select the Display Alarm Status method in the Agents window, and then click the report icon in the Alarm Status window.

In the navigation frame of the Bookmarks window, select a report name and then choose the Display Reports method.

In the Event Monitor window, click a report icon.

Click the report icon in the Event area list in the System Operational Status Summary window.

Click the Display Reports link menu item while a drilldown report in the drilldown report selection list is selected.

The View Report window consists of the following four pages:

View report page

Properties page

Edit Report Definition page

Show Options page

The following describes the items that are common to all four pages:

Baseline

Baseline appears in the upper right corner of the View Report window only for reports that are not realtime reports, reports without graphs, or reports specified with the display key fields.

A baseline refers to a report that covers a period in the past that has been saved as a reference value. A baseline can be overlaid as the reference value on a combination report. See 1.4.5(1) Baseline window.

Bookmark

The Bookmark window that is used to register a bookmark or combination bookmark opens as a new window. See 1.4.14(2) Bookmark window.

Save Report Definition

Displays a separate Save Report Definition window, where you can specify the location for storing reports. See 1.4.5(2) Save Report Definition window.

Description

For each data model version of each applicable product, the Description of Record and Fields window is displayed as a new window. See 1.4.5(3) Description of Record and Fields window.

Close

Closes the Display Reports window.

The following describes the windows and pages.

(1) Baseline window

The Baseline window is used to register the baseline.

The following figure shows the Baseline window.

Figure 1‒31: Baseline window

The following describes the displayed items:

Refresh

Updates the display of the Baseline window to the latest status.

Text box

Use this text box to filter bookmarks by keywords. Specify a character string of 1 to 1,024 characters to filter the bookmarks that will be displayed. To perform a multi-keyword AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters bookmarks by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Bookmarks tree

Specify the location for storing the baseline.

Specify the baseline name

Enter 1 to 64 single-byte or two-byte characters for the baseline name.

OK button

Depending on the selected object, either of the following applies:

When a combination bookmark is selected

A baseline is added under the selected combination bookmark.

When a baseline is selected

The selected baseline is updated.

Cancel button

Discards the definitions specified in the Baseline window, and closes the window.

(2) Save Report Definition window

The Save Report Definition window saves the report definitions. You can use the initialization file (config.xml) to specify whether to display the Save Report Definition menu for a user who logs in with an account that has general user permissions only. For details about the initialization file (config.xml), see E. Initialization File (config.xml).

The following figure shows the Save Report Definition window.

Figure 1‒32: Save Report Definition window

The following describes the displayed items:

Refresh

Refreshes the information displayed in the Save Report Definition window.

OK button

Saves the report according to the definition specified in the Save Report Definition window, and then closes the window.

An error message is displayed in the following cases:

If the report name entered in the text box is the same as an existing report name

If the report to be overwritten does not exist

Cancel button

Discards the specified definition and closes the Save Report Definition window.

Save (and overwrite) radio button

Overwrites the existing report definition. This item is not displayed in the following cases:

For an instant report

When a registered report is displayed

If the report to be overwritten has been deleted

For the report definition of the monitoring template

Save as... radio button

Displays the reports tree that specifies the location for storing the report.

Text box

Use this text box to filter the locations for storing report definitions by keywords. Specify a character string of 1 to 1,024 characters to filter the locations for storing the report definitions that will be displayed. To perform a multi-keyword AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

New Folder

Filters the locations by using the string specified in the text box.

Cancel

Clears the filtering status and the filtering condition.

Reports tree

Specify the folder for storing the report definitions.

Specify a report name

Enter a report name within the range of 1 to 64 characters by using single-byte or two-byte characters.

You can enter a value in this text box only when a folder has been selected in the reports tree.

New Folder button

Displays the Save Report Definition (for entering a folder name) window.

In this window, a text box is displayed only if a folder has been selected in the reports tree.

Figure 1‒33: Save Report Definition (for entering a folder name) window

Enter a report folder name by using 1 to 64 single-byte or two-byte characters.

When you click the OK button after entering the name, the Save Report Definition (for entering a folder name) window closes, and a report folder is created.

If you click the Cancel button, the entered name is discarded, and the Save Report Definition (for entering a folder name) window closes.

(3) Description of Record and Fields window

The Description of Record and Fields window displays information about a record and the fields in the record. The same window is displayed for the Reports window and the Alarms window.

The following figure shows the Description of Record and Fields window.

Figure 1‒34: Description of Record and Fields window

The following describes the displayed items:

Record name

Displays record names in a hierarchical structure. If you click a link for a record name, you can jump to the record information section in a list.

Field name index

Lists the initial characters of the fields in the applicable record. If you click the link, you can jump to the applicable field information section in a list.

Record

Displays the record name.

Description (for Record)

Displays a description of the record.

Field

Lists the field names in the applicable record in alphabetical order.

Description (for Field)

Displays field descriptions.

(4) View report page

This page displays the specified report. It displays performance data collected by each agent as a graphical report in graph or table format.

The following figure shows the View Report window (View report page).

Figure 1‒35: View Report window (View report page) (when only a graph is displayed)

The following describes the displayed items:

Check boxes

Graph

Displays the report's data as a graph. This check box is selected as a default.

If there is no applicable data or no applicable settings in the report definition, this check box is disabled.

List

Displays a listing of the report's data. This check box is selected as a default.

If there is no applicable data or no applicable settings in the report definition, this check box is disabled.

Table

Displays the report's data as a table. This check box is selected as a default.

If there is no applicable data or no applicable settings in the report definition, this check box is disabled.

Data group buttons

A data group is data grouped by record collection time.

button

Displays the first data or data group.

button

Displays the previous data or data group.

button

Displays the next data or data group.

button

Displays the last data or data group.

Drilldown report selection list

Enables you to select a drilldown report from a pull-down menu. This item appears only when a drilldown report is defined for the displayed report, bookmark, or combination bookmark.

When you move the mouse pointer to the selection list, the name of the currently selected report appears in the tool tips, allowing you to check the complete report name if it is too long to fit in the selection list box.

Link menu

Display Reports

Clicking this item while a drilldown report is selected from the drilldown report selection list displays a new View Report window.

Refresh

Acquires data again and refreshes the display.

Export

Exports to a CSV text file the data acquired for displaying the report. This item is not displayed for automatically refreshed realtime reports. To display this item in this case, first choose Stop to stop automatic refreshing. Choosing Export displays a dialog box for downloading files.

Print

Displays the Print Reports window as a new window.

This item is not displayed in a realtime report that is being updated automatically. If you want to display this item during an automatic update, choose the Stop menu item to stop the update.

For details about the Print Reports window, see 1.4.6 Print Reports window.

Stop

Stops automatic refreshing of realtime reports.

Button for changing the report display period:

For a historical report, you can move data of the same period of time as that in the currently displayed report forward or backward by using any of the buttons below. Note that on the Show Options page, you can change the setting for the report display period in finer detail.

button

Displays a report after moving the period backward for the same period of time as the displayed period.

button

Displays a report after moving the period backward by one-half the time of the currently displayed period.

button

Displays a report after moving the period forward by one-half the time of the currently displayed period.

button

Displays a report after moving the period forward for the same period of time as the currently displayed period.

For example, if the data for one hour from 10:00 to 11:00 is displayed, the following data is displayed:

button: The data from 9:00 to 10:00

button: The data from 9:30 to 10:30

button: The data from 10:30 to 11:30

button: The data from 11:00 to 12:00

Also, if data for 30 days from January 1 to January 30 is displayed, the following data is displayed:

button: The data from December 2 to December 31

button: The data from December 17 to January 15

button: The data from January 16 to February 14

button: The data from January 31 to March 1

Message display icon ( )

This icon is displayed if a message related to automatic refresh is generated when a realtime report is displayed. Clicking displays the message.

Name of operation mode for realtime reports

If a realtime report is displayed while the setting is configured so that collecting history data takes priority over displaying realtime reports, either the re-schedule mode or temporary log mode is displayed, depending on the setting.

For details about the settings for prioritizing collecting history data over displaying realtime reports, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Graph display area

Displays the graph area.

button

Displays the first page when a graph field spans multiple pages.

button

Displays the pervious page when a graph field spans multiple pages.

button

Displays the next page when a graph field spans multiple pages.

button

Displays the last page when a graph field spans multiple pages.

Zoom

Zooms the graph display. Available magnifications are 100%, 200%, 400%, 600%, and 800%.

List display area

Displays a list of field values for each agent or instance. In the list, if a field name has a link, clicking the link displays a drilldown report (field level).

button

Displays data for the first agent or instance in the same data group.

button

Displays data for the previous agent or instance in the same data group.

button

Displays data for the next agent or instance in the same data group.

button

Displays data for the last agent or instance in the same data group.

Table display area

Displays accumulated time-series historical data in table format. If a table value has a link, clicking the link displays a drilldown report (field level).

First Instance

Displays the first page.

Previous Instance

Displays the previous page.

Data number

first-data-number-on-displayed-page - last-page-number-of-displayed-page OF total-number-of-data-items is displayed.

Example: 5-24 OF 50

Next Instance

Displays the next page.

Last Instance

Displays the last page.

(5) Properties page

This page displays the report definitions displayed on the View report page. The information that is displayed is the settings you specified in the window for creating a new report definition or the window for editing definitions.

The following figure shows the View Report window (Properties page).

Figure 1‒36: View Report window (Properties page)

If you click the link at the top of the window on the Properties page, you can jump to the area that displays the applicable information. For details about the items displayed in each area, see 1.5.3 Windows for creating and editing report definitions.

The following describes the items displayed on this page:

Name and type

This area displays the information set in the New Report > Name and Type or Edit > Name and Type window for report definitions.

Field

This area displays the information set in the New Report > Field or Edit > Field window for report definitions.

Indication settings(Realtime) or Indication settings (Historical)

For a realtime report

The Indication settings(Realtime) area displays the information set in the New Report > Indication Settings(Realtime) or Edit > Indication Settings(Realtime) window for report definitions.

For a historical report

The Indication settings (Historical) area displays the information set in the New Report > Indication Settings (Historical) or Edit > Indication Settings (Historical) window for report definitions.

Components

This area displays the information set in the New Report > Indication Settings or Edit > Indication Settings window for report definitions.

Graph

This area displays the information set in the New Report > Graph or Edit > Graph window for report definitions.

Drilldown

This area displays the information set in the New Report > Drilldown or Edit > Drilldown window for report definitions.

(6) Edit Report Definition page

This page enables you to edit the definitions for the report displayed on the View report page.

The following figure shows the View Report window (Edit Report Definition page).

Figure 1‒37: View Report window (Edit Report Definition page)

If you click the link at the top of the Edit Report Definition page, you can jump to the display area of the applicable information. For details about the display items and settings in each area, see 1.5.3 Windows for creating and editing report definitions.

The following describes the displayed items:

OK button

Saves the settings and returns to the View Report window.

Cancel button

Discards the definitions in the Edit Report Definition window and returns to the View report page.

Name and type

This area displays the information set in the New Report > Name and Type or Edit > Name and Type window for report definitions.

Field

This area displays the information set in the New Report > Field or Edit > Field window for report definitions. You can edit information other than the record name.

Filter

By default, no value is displayed in the Filter area. You can add definitions in this area.

Indication settings(Realtime) or Indication settings (Historical)

For a realtime report

The Indication settings(Realtime) area displays the information set in the New Report > Indication Settings(Realtime) or Edit > Indication Settings(Realtime) window for report definitions. You can edit definitions in this area.

For a historical report

The Indication settings (Historical) area displays the information set in the New Report > Indication Settings (Historical) or Edit > Indication Settings (Historical) window. You can edit definitions in this area.

Components

This area displays the information set in the New Report > Indication Settings or Edit > Indication Settings window for report definitions. You can edit definitions in this area.

Graph

This area displays the information set in the New Report > Graph or Edit > Graph window for report definitions. You can edit definitions in this area.

Drilldown

This area displays the information set in the New Report > Drilldown or Edit > Drilldown window for report definitions. You cannot edit definitions in this area.

(7) Show Options page

You can specify the display settings for the report displayed in the View report page.

The display items on the Show Options page vary according to the report type (either realtime report or historical report). The following describes each case.

(a) Show Options page (For a realtime report)

The following figure shows the Show Options page (for a realtime report) of the View Report window.

Figure 1‒38: Show Options page of the View Report window (for a realtime report)

The following describes the items displayed on this page:

OK button

Applies the settings. Clicking this button displays the View report page again.

Cancel button

Discards the settings and returns to the View report page.

Indicate delta value

Displays the report in terms of delta values. When this item is selected and delta values have been collected in a field of the corresponding record, the amount of change in the performance data from the previously collected delta value to the most recently collected delta value is displayed.

Note that this setting is disabled if realtime reports are set to be displayed in temporary log mode, and realtime reports are always displayed by using the amount of change in the performance data from the previously collected value.#

Refresh interval

Do not refresh automatically

Does not automatically refresh the View Report window.

Refresh interval

Specifies the interval (in seconds) at which the View Report window is to be refreshed automatically. The maximum value is 3,600 seconds

Note that this setting is disabled if realtime reports are set to be displayed in temporary log mode, and realtime reports are automatically refreshed according to the value set for the Collection Interval property for the records.#

Display by ranking

Specifies that there is to be a limit on the higher- or lower-order data that is displayed in the report. This item is displayed for multi-instance records.

Field

Specifies a field that is to be used as the reference for displaying the number of higher- or lower-order data items specified in Display number.

Display number

Specifies the number of higher- or lower-order data items to be displayed, in the range of 1 to 100. This item is enabled only when a field is selected in Field.

In descending order

Specifies that the data is to be displayed in descending order.

Graph options

Show 3D graph

Specifies that a 3-dimensional graph is to be displayed.

Show gridlines

Specifies that gridlines are to be displayed on the graph.

Show AutoLabel

Select this check box to display the value for the corresponding data as a tool tip when you move the cursor onto the plot in a graph.

Manually set the max. and min. values of the vertical axis

Specifies that maximum and minimum values to be displayed on the vertical axis are to be set. When you select this item, specify desired values in Max. value and Min. value.

Max. value

This item is enabled when Manually set the max. and min. values of the vertical axis is selected. Specify a desired value as the maximum value to be displayed on the graph's vertical axis.

Min. value

This item is enabled when Manually set the max. and min. values of the vertical axis is selected. Specify a desired value as the minimum value to be displayed on the graph's vertical axis.

#:

For details about temporary log mode for realtime reports, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

(b) Show Options page (for a historical report)

The following figure shows the Show Options page of the View Report window (for a historical report).

Figure 1‒39: Show Options page of the View Report window (for a historical report)

The following describes the items displayed on this page:

OK button

Applies the settings. Clicking this button displays the View report page again.

Cancel button

Discards the settings and returns to the Display report page.

Settings for the report display period

Specifies a report display period.

Date range

From the pull-down menu, select the display period for the report.

You can select from the following values:

Specify when displayed

Within the past hour

Within the past 24 hours

Within the past 7 days

Within the past month

Within the past year

If a value other than Specify when displayed is selected, the appropriate dates and times are set automatically in Start time and End time.

Start time and End time

When you selected Specify when displayed in Date range, enter a start date and time and an end date and time for event display.

Specify Start time and End time in the format YYYY MM DD hh:mm (YYYY: year, MM: month, DD: date, hh: hour, mm: minute).

The permitted date and time range is from 01-01-1971 00:00 to 12-31-2035 23:59. The date and time set in End time must be later than the date and time set in Start time.

If you selected a date range other than Specify when displayed, the appropriate dates and times are set automatically. If you change an automatically set date and time, the Date range setting changes to Specify when displayed.

Report interval

Set the interval for displaying data in the report. This item is enabled for records of the PI record type.

When this item is set, average values (summarized) over the specified period are displayed in the report.

Available values are as follows:

Minute: Displays the report based on 1-minute intervals.

Hour: Displays the report based on 1-hour intervals.

Day: Displays the report based on 1-day intervals.

Week: Displays the report based on 1-week intervals.

Month: Displays the report based on 1-month intervals.

Year: Displays the report based on 1-year intervals.

If you specified an interval other than Minute, then in the window with the View report page, in the display area of the table, click the value in Date and Time to display drilldown reports.

Display the start time data and Display the end time data

Switches between displaying and hiding the data that matches the date and time you specified in Start time or End time for the data that will be displayed in a report. By default, these check boxes are selected. You can set the default selection status in excludeTerminalData (under the <vsa> tag) of the initialization file (config.xml). For details about the initialization file (config.xml), see E. Initialization File (config.xml).

If both check boxes are selected, data that matches the date and time you specified in Start time or End time is displayed.

If both check boxes are cleared, data that matches the date and time you specified in Start time or End time is not displayed.

Maximum number of records

Specifies the maximum number of records to be displayed in the report, in the range of 1 to 1,440.

You can specify in PFM - Web Console's initialization file (config.xml) the maximum number of records (maxFetchCount) in the range of 1 to 2,147,483,647. In this case, you can only specify in Maximum number of records a value that is within the range specified in the config.xml file.

Peak time

Specifies that the display is to be of only the data at the time at which the field specified in Field contains its maximum value for the day (the peak time).

Field

From the pull-down menu, select the field on which the peak-time display is to be based on. This item is enabled for a single-instance record (single-row record) when Hour is selected in Report interval.

Graph options

Show 3D graph

Specifies that a 3-dimensional graph is to be displayed.

Show gridlines

Specifies that gridlines are to be displayed on the graph.

Show AutoLabel

Select this check box to display the value for the corresponding data as a tool tip when you move the cursor onto the plot in a graph.

Manually set the max. and min. values of the vertical axis

Specifies that maximum and minimum values to be displayed on the vertical axis are to be set. When you select this item, specify desired values in Max. value and Min. value.

Max. value

This item is enabled when Manually set the max. and min. values of the vertical axis is selected. Specify a desired value as the maximum value to be displayed on the graph's vertical axis.

Min. value

This item is enabled when Manually set the max. and min. values of the vertical axis is selected. Specify a desired value as the minimum value to be displayed on the graph's vertical axis.

1.4.6 Print Reports window

The Print Reports window allows you to print and save reports. The window appears when you do one of the following:

In the View report page of the View Report window, you click Print.#

In the View report page of the Combination Report window, you click Print.

In the View report page of the Event History window, you click Print.

#

You can perform the same actions for a registered report stored under a bookmark.

The following shows the Print Reports window.

Figure 1‒40: Print Reports window (report)

Figure 1‒41: Print Reports window (combination report)

Figure 1‒42: Print Reports window (event history report)

The graph display area, list display area, or table display area might not appear depending on the contents of the report to be displayed. The following table shows which items are displayed for each report type.

Table 1‒12: Difference of displayed items among report types

View Report window displayed

Report header displayed

Graph displayed

List displayed

Table displayed

Report

Always

Maybe

Maybe

Maybe

Combination report

Always

Always

Never

Never

Event history report

Always

Never

Never

Always

Legend:

Always: The item is always displayed.

Maybe: A graph, a list, or a table is always displayed (this status is the same display status as in the View Report window when the Print Reports window is opened from it).

Never: The item is not displayed.

The format of output in the Print Reports window depends on the status of the check boxes (Graph, List, Table) in the menu bar frame in the View Report window. The items that appear in the Print Reports window are those that are displayed in the report when the print window appears. The display magnification for the graphs is the magnification selected in the Print Reports window.

Each time you click Print in the View Report window or other windows while the Print Reports window is displayed, a new window opens. A Print Reports window that is already open is not updated.

The following describes each item:

Report header display area:

The following items are displayed in the report header display area:

Title:

For a report, the report definition name is displayed.

For a combination report, the combination bookmark name is displayed.

For an event history report, the character string Event History Report is displayed.

Parent Folder:

For a report, the full path for the folder that stores the report definition is displayed.

For a combination report, the full path for the bookmarks tree is displayed.

If you have not saved the report definition of the report displayed in Quick Guide, / is displayed.

Nothing is displayed for an event history report.

Agents:

Agent names are displayed. When multiple agents exist, they are delimited with commas.

Nothing is displayed for a combination report.

Time:

The time that the data output to the Print Reports window was acquired is displayed.

Graph display area:

Displays the graph image of the displayed report when the print window is displayed. The image is in PNG format.

List display area:

The following items are displayed in the list display area:

List:

Displays the contents of the table display area displayed in the View Report window. Data that is not displayed in the report is not output.

Instance number:

The instance number of the displayed list appears in the lower right corner of the list in instance-number OF total-number-of-instances format.

Table display area:

Displays all the data in the table displayed in the View Report window in one window.

Note 1:

If you want to print the list display area and the table display area in color, you need to set up the Web browser to print the background color and the image.

Note 2:

If you display multiple Print Reports window and then perform one of the following actions for an old Print Reports window, a KAVJS4012-E message indicating expiration of the cache might appear:

Save the Print Reports window.

Print the Print Reports window.

Reload the Print Reports window by using the Web browser update function.

If the message appears, close the Print Reports window and then redisplay the print window from the parent report.

Note 3:

When the report series paging functionality is enabled, the page displayed in the View Report window is displayed in the Print Reports window. To include all fields in a single HTML file, disable the report series paging functionality. For details about the report series paging functionality, see the chapter that explains installation and setup of Performance Management in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Note 4:

If the number of lines in the report to be displayed as the table data in the Print Reports window exceeds the specified value, a message indicating that output of the table data has stopped is displayed. Then, only the data up to and including the specified value is displayed. If you want to increase the number of lines that can be output, edit the value for printTableMaxRowSize in the initialization file (config.xml).

1.4.7 Combination Report window

The Combination Report window displays combination reports. To display the window, do one of the following:

In the Agents window, select the Display Reports method, select Bookmarks from Tree Type, and then click a combination bookmark in the Regist Bookmark > Select Report window.

In the Bookmarks window, select a combination bookmark in the navigation frame and choose the Display Reports method.

Click the Display Reports link menu item while a drilldown report in the drilldown report selection list is selected.

The Combination Report window consists of the following three pages:

View report page

Properties page

Show Options page

The following describes each page.

(1) View report page

This page displays the specified combination report. The page displays performance data collected by each agent as a report in graph or table format.

The following figure shows the Combination Report window (View report page).

Figure 1‒43: Combination Report window (View report page)

The following describes the items displayed on this page:

Close

Closes the Combination Report window.

Registered report selection list:

Enables you to select a registered report from a pull-down menu. This item displays all the reports that are registered as combination bookmark destinations. When you move the mouse pointer to the selection list, the name of the currently selected registered report appears in the tool tips, allowing you to check the complete report name if it is too long to fit in the selection list box.

Link menu:

Display Reports

When a registered report is selected in the registered report selection list, click this item to display the View Report window as a separate window.

Refresh

Acquires data again and refreshes the display.

Print

Displays the Print Reports window as a new window.

For details about the Print Reports window, see 1.4.6 Print Reports window.

Button for changing the report display period:

For a historical report, you can move data of the same period of time as that in the currently displayed report forward or backward by using any of the buttons below. Note that on the Show Options page, you can change the setting for the report display period in finer detail.

button

Displays a report after moving the period backward for the same period of time as the currently displayed period.

button

Displays a report after moving the period backward by one-half the time of the currently displayed period.

button

Displays a report after moving the period forward by one-half the time of the currently displayed period.

button

Displays a report after moving the period forward for the same period of time as the currently displayed period.

Graph display area:

Area for displaying graphs.

Zoom

Zooms the display. Available magnifications are 100%, 200%, 400%, 600%, and 800%.

Legend area:

Displays the legend for a graph for each series group.

The series group name appears as series-group-name.

For a registered report, registered-report-name:record-name:instance-identifier:field-name#1 appears.

For a baseline, Baseline:baseline-name:instance-identifier#2:field-name#1 appears.

If display data is not acquired or there is no data to be displayed, a legend is not displayed.

#1

The display name appears if the display name of the field is set. If the display name of the field is not set, the default field name appears.

#2

An instance identifier consists of ODBC key fields separated by angle brackets (< >). A blank appears if no instance identifier exists.

(2) Properties page

This page displays the definition of the combination report that is displayed on the View report page. The page displays the settings that were specified in the Edit Combination Bookmarks window.

The following figure shows the Combination Report window (Properties page).

Figure 1‒44: Combination Report window (Properties page)

For details about the display items in each area, see 1.6.3 Edit window.

The following describes the items displayed on this page:

Close

Closes the Combination Report window.

Settings for the report display period

Enables you to specify a period and a display interval for the report.

Graph display settings

Displays the title of the graph, the character string to be displayed as the label for the X axis of the report, and the graph options.

Series group settings

A series group indicates a collection of reports that are registered as combination bookmark destinations and grouped based on the display formats of the graphs in the reports.

(3) Show Options page

You can specify the display settings for the combination report displayed on the View report page.

The following figure shows the Combination Report window (Show Options page).

Figure 1‒45: Combination Report window (Show Options page)

The following describes the items displayed on this page:

Close

Closes the Combination Report window.

OK button

Accepts the specified settings and returns to the View report page. The View report page displays the combination reports with the specified display conditions.

Cancel button

Discards the specified settings and returns to the View report page.

Settings for the report display period

Enables you to specify a period and a display interval for the report.

Date range

From the pull-down menu, select the display period for the report.

Available values are as follows:

Specify when displayed

Within the past hour

Within the past 24 hours

Within the past 7 days

Within the past month

Within the past year

When you select an option other than Specify when displayed, the time and date for Start time and End time are automatically set.

Start time and End time

When you select Specify when displayed in Date range, you need to set the start time and date, and the end time and date period for displaying events.

Specify Start time and End time in YYYY MM DD hh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minute).

The specifiable range is from 00:00 on January 1, 1971 to 23:59 on December 31, 2035. For End time, specify a time and date later than Start time.

Note that the format specified for Start time and End time differs depending on Report interval. Accordingly, follow the entry format displayed on the right. When you select an option other than Specify when displayed, the corresponding time and date are set automatically. If you change the time and date that are displayed automatically, the setting of Date range becomes Specify when displayed.

Report interval

Sets the display interval for reports. The value specified for this item is applied to all the records of the PI record type that are contained in combination reports.

When you specify this item, averaged (summarized) values within the specified period appear in the reports.

Available values are as follows:

Minute: Displays reports at 1-minute intervals.

Hour: Displays reports at 1-hour intervals.

Day: Displays reports at 1-day intervals.

Week: Displays reports at 1-week intervals.

Month: Displays reports at 1-month intervals.

Year: Displays reports at 1-year intervals.

The Peak time specification in the report definition is enabled only when you select Hour.

When you change Report interval, Start time and End time are set automatically to match the change.

Display the start time data and Display the end time data

Switches between displaying and hiding the data that matches the date and time you specified in Start time or End time for the data that will be displayed in a report. By default, these check boxes are selected. You can set the default selection status in excludeTerminalData (under the <vsa> tag) of the initialization file (config.xml). For details about the initialization file (config.xml), see E. Initialization File (config.xml).

If both check boxes are selected, data that matches the date and time you specified in Start time or End time is displayed.

If both check boxes are cleared, data that matches the date and time you specified in Start time or End time is not displayed.

Settings for the baseline display period

Start time

Sets the start time and date for the baseline.

Specify Start time in YYYY MM DD hh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minute).

When you change Date range, Start time changes accordingly.

1.4.8 Alarm Status window

The Alarm Status window displays the status of the alarms in the alarm table that is bound to (associated with) the selected monitoring agent. To display this window, from the method frame in the Agents window, choose Display Alarm Status.

The following shows the Alarm Status window.

Figure 1‒46: Alarm Status window

The following describes the displayed items:

Refresh

Updates the agent and alarm statuses to the latest information.

If a message such as A connection to the agent cannot be established. appears while the agent is running, or alarm information appears while the agent is not running, the information might be old. Click Refresh to update the information to the latest information, and then check whether the symptom has disappeared.

Contents area

Displays a list of alarms in the alarm table that is bound to (associated with) the selected monitoring agent. If the functionality for binding multiple alarm tables is enabled, statuses of multiple alarm tables are displayed. Clicking an alarm table name displays or hides the list of alarms in the alarm table.

If the functionality for binding multiple alarm tables is disabled, the status of one alarm table is displayed.

Health check status

Displays a message indicating the status of the health check.

For details about the health check status, see the chapter that explains error detection of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

Icons used for displaying status of an alarm table

To the left of an alarm table name, an icon is displayed, which indicates the highest severity level among the alarms in that alarm table. Clicking the icon displays or hides the list of alarms in the alarm table.

: Indicates that the alarm table is expanded (the definition is displayed).

: Indicates that the alarm table is closed (the definition is not displayed).

(green): Indicates a normal status.

(yellow): Indicates a warning status.

(red): Indicates an abnormal status.

: Indicates a monitoring suspended status.

The table below lists the relationship between the status of the alarm table and the status of alarms. This example assumes that the alarm table has alarm A and alarm B. Icons inside the table shows the status of the alarm table. For example, if the status of alarm A is (red: Abnormal) and the status of alarm B is (green: Normal), the status of the alarm table is indicated as (red: Abnormal), which is the higher severity status between alarm A and alarm B.

Table 1‒13: Relationship between the status of the alarm table and the status of alarms

Status of alarm A

Status of alarm B

(red)

(yellow)

(green)

(gray)

(always report an alarm)

(red)

(red)

(red)

(red)

(red)

(red)

(yellow)

(red)

(yellow)

(yellow)

(yellow)

(yellow)

(green)

(red)

(yellow)

(green)

(green)

(green)

(gray)

(red)

(yellow)

(green)

(green)

(green)

(always report an alarm)

(red)

(yellow)

(green)

(green)

(green)

Report icons

A report icon (such as , depending on the PFM - Agent or PFM - RM in use) is displayed to the left of an alarm icon with which a report is associated. Clicking this icon opens a related report as a new window.

Alarm icons

An alarm icon is displayed to the left of each alarm name. The color of the icon indicates the alarm's status, as follows:

(gray): Indicates an inactive status.

(green): Indicates a normal status.

(yellow): Indicates a warning status.

(red): Indicates an abnormal status.

#: Indicates that this alarm is set to always report an alarm.

: Indicates a monitoring suspended status.

#: This icon can be displayed only if Always notify was selected in the alarm definition.

1.4.9 Service Properties window

The Service Properties window displays the properties of the selected monitoring agent service (Agent Collector service, Remote Monitor Collector service, or each remote agent and group agent). To display this window, from the method frame in the Agent window, choose Properties. Note that the property settings cannot be changed in this window.

The following figure shows the Service Properties window.

Figure 1‒47: Service Properties window

The following describes the displayed items:

Contents area

Displays hierarchically the properties of the selected monitoring agent service (Agent Collector service, Remote Monitor Collector service, or each remote agent and group agent). The properties of the monitoring agent service depend on the PFM - Agent or PFM - RM in use. For details, see the appropriate PFM - Agent or PFM - RM manuals.

Property list area

Displays a list of properties when a node is selected in the contents area. The following items are displayed for each property:

Name

Displays the name of the property item.

Value

Displays system information, such as the OS, and the existing setting.

Description

Displays a description of the property.

1.4.10 Event History window

The Event History window displays event log information for the monitoring agent. To display this window, from the method frame in the Agents window, choose Event History.

The Event History window consists of two pages:

View report page

Show Options page

If in the method frame of the Agents window, you select the Event History method, the Show Options page will be displayed. In the Show Options page, set display conditions, such as the event display period and the maximum number of events to be displayed, and then click the OK button. The Show Options page will be displayed.

The following describes each page.

(1) View report page

This page displays the event log information for the monitoring agent selected in the navigation frame in the Agents window. Event history is displayed in accordance with the display conditions set on the Show Options page.

The following figure shows the Event History window (View report page).

Figure 1‒48: Event History window (View report page)

The following describes the displayed items:

Close

Closes the Event History window.

Check boxes

Graph

Select this check box to view the graph data of a report. The check box is not available if it is not set in the report definition.

List

Select this check box to view listed data of a report. The check box is not available if the viewing of data is not set in the report definition.

Table

Select this check box to view the table data of a report. The check box is not available if the viewing of data is not set in the report definition.

Data Group button

A data group is data grouped by the record collection time.

button

Displays the most recent (newest) data or data group.

button

Displays the immediately previous (newer) data or data group.

button

Displays the next (older) data or data group.

button

Displays the oldest data or data group.

Link menu

Refresh

Refreshes the information displayed in the table frame.

Export

Exports to a CSV text file the data acquired for displaying the event history. Choosing this item displays a dialog box for file downloading.

Print

Displays the Print Reports window as a new window.

For details about the Print Reports window, see 1.4.6 Print Reports window.

Button for changing the report display period:

You can move data of the same period of time as that of the currently displayed report forward or backward by using any of the buttons below. Note that on the Show Options page, you can change the setting for the report display period in finer detail.

button

Displays a report after moving the period backward for the same period of time as the currently displayed period.

button

Displays a report after moving the period backward by one-half the time of the currently displayed period.

button

Displays a report after moving the period forward by one-half the time of the currently displayed period.

button

Displays a report after moving the period forward for the same period of time as the currently displayed period.

Table frame

Displays a list of events that have occurred at the monitoring agent selected in the navigation frame in the Agents window.

The following describes the items displayed in the table frame:

Date and Time

Displays the system date and time at the host of the monitoring agent where the event occurred.

Agent

Displays the service ID of the monitoring agent.

Host

Displays the host name of the monitoring agent.

StateEx

Displays the event's status. For an alarm event for which State changes for each record instance is selected, this column displays an icon that indicates the status of the record instance that caused the alarm event.

One of the following is displayed:

OK: Normal event

Exception: Abnormal event

Warning: Warning event

Inactive: Inactive event or event whose status is unknown

Suspended: Monitoring suspended event

Resumed: Monitoring resumed event

Not Supported: Not Supported

Running: Running

Incomplete: Incomplete

Stopped: Stopped

Unconfirmed: Unconfirmed

Host Not Available: Host Not Available

For details about the health check status, see the chapter that explains error detection of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

Alarm Name

Displays the name of the alarm resulting in the event. For agent events and health check events, n/a appears.

Alarm Table

Displays the name of the alarm table to which the alarm resulting in the event belongs. For agent events and health check events, n/a appears.

Message

Displays the message output by the monitoring agent or the message defined in the New Alarm method in the Alarms window. The following lists the principal messages that are displayed:

For agent events:

Startup: PFM - Agent or PFM - RM has started.

Shutdown: PFM - Agent or PFM - RM has stopped.

State change: The status of PFM - Agent or PFM - RM has changed.

State change(Unconfirmed): PFM - Manager could not confirm the agent alarm status, but it inferred the status of PFM - Agent or PFM - RM from the received alarm event.

State information: PFM - Manager correctly confirmed the agent alarm status.

State information(Unconfirmed): PFM - Manager could not confirm the agent alarm status.

Heartbeat timeout:

The Agent Collector or Remote Monitor Collector service is busy or inactive.

Heartbeat detected:

The Agent Collector or Remote Monitor Collector service has recovered from the busy or inactive status.

Monitored System Unavailable: Operating information could not be collected because the monitored system had stopped.

Monitored System Available: The monitoring system recovered from not being able to collect operating information because the monitored system had stopped.

Suspend: Monitoring has been suspended.

Resume: Monitoring has been resumed.

Other than those mentioned above, a message that begins with KAV might be displayed.

If Heartbeat timeout is displayed, check the status of the PFM - Agent or PFM - RM. If a message that begins with KAV is displayed, see the chapter that explains messages in the PFM - Agent or PFM - RM manuals. There is no need to take any action for other messages because they are not error messages.

For alarm events:

The meaning of messages depends on the setting of alarmCompatibleMode, an item in the initialization file (config.xml) used to set the PFM - Web Console operating environment:

Alarm updated/deleted

Alarm deactivated

For details about alarmCompatibleMode, see E. Initialization File (config.xml).

When alarmCompatibleMode does not exist:

Alarm updated/deleted: Alarm definition was updated or deleted.

Alarm deactivated: The alarm is no longer active.

When alarmCompatibleMode is true:

Alarm updated/deleted: The alarm definition was deleted.

Alarm deactivated: The alarm is no longer active, or the alarm was updated and the previous alarm status was initialized.

When alarmCompatibleMode is false:

The meaning of the messages depends on the PFM - Manager version.

When the PFM - Manager version is 09-10-19 or later:

Alarm updated/deleted: The alarm definition was deleted.

Alarm deactivated: The alarm is no longer active, or the alarm was updated and the previous alarm status was initialized.

When the PFM - Manager version is earlier than 09-10-19:

Alarm updated/deleted: The alarm definition was updated or deleted.

Alarm deactivated: The alarm is no longer active.

State changed(No instance data): The status of an instance changed, but there is no data on the instance.

In the case of multi-instance records, the following processing occurs:

When a value in the abnormal or warning range is detected for at least one of the target instances:

The user-defined message set in the alarm definition is displayed in Message . If a performance data measurement value is set to be displayed in the message text, the value of the instance exceeding the threshold is set.

When the status recovers from abnormal or warning to normal:

If the function for measurement value output at alarm recovery is enabled, the user-defined message set during alarm definition is displayed in Message. In addition, if you set that the measurement value of performance data is to be displayed in Message, the current measurement value of the instance that triggered issuance of the last error or warning alarm is set.

If this functionality is disabled, a normal event is issued, but all instance values are in the normal range, and the value that triggered issuance of the event cannot be identified. As a result, nothing is displayed in Message.

For details about the function for measurement value output at alarm recovery, see the chapter that explains operation monitoring by using alarms in the Job Management Partner 1/Performance Management User's Guide.

For health check events:

Message text is displayed in HC: health-check-status format.

In addition, message text indicating the operating status of the service is displayed after the operating status of the agent. For details about display rules and examples of message texts, see the section that explains the health check agent in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

First button

Displays the first page. If there are no preceding pages, this button is disabled.

Previous button

Displays the previous page. If there are no preceding pages, this button is disabled.

Data number

Displays the page identifier in the format first-data-number-on-the-current-page - last-data-number-on-the-current-page OF total-number-of-data-items.

Example: 5-24 OF 50

Next button

Displays the next page. If there are no following pages, this button is disabled.

Last button

Displays the last page. If there are no following pages, this button is disabled.

(2) Show Options page

This page is used to set the display conditions for the displays on the View report page, such as the event history display period and the maximum number of event histories to be displayed. The display conditions set on this page remain in effect only for as long as the Event History window is displayed, and cannot be saved.

The following figure shows the Event History window (Show Options page).

Figure 1‒49: Event History window (Show Options page)

The following describes the items displayed on this page:

Close

Closes the Event History window.

OK button

Sets the specified settings and returns to the View report page. Event histories are displayed on the View report page according to the display conditions you have specified.

Cancel button

Discards the specified settings and returns to the View report page.

Settings for the report display period

Specifies the period for which data is to be displayed as the event history in the View report page. The available settings are as follows:

Date range

From the pull-down menu, select the period for displaying events.

Available values are as follows:

Specify when displayed

Within the past hour

Within the past 24 hours

Within the past 7 days

Within the past month

Within the past year

The default is Within the past 24 hours.

If a value other than Specify when displayed is selected, the appropriate dates and times are set automatically in Start time and End time.

Start time and End time

When you selected Specify when displayed in Date range, enter a start date and time and an end date and time for event display.

Specify Start time and End time in the format MM DD YYYY hh:mm (YYYY: year, MM: month, DD: date, hh: hour, mm: minute).

The permitted date and time range is from 01-01-1971 00:00 to 12-31-2035 23:59. The date and time set in End time must be later than the date and time set in Start time.

If you selected a date range other than Specify when displayed, the appropriate dates and times are set automatically. If you change an automatically set date and time, the Date range setting changes to Specify when displayed.

Display the start time data and Display the end time data

Switches between displaying and hiding the data that matches the date and time you specified in Start time or End time for the data that will be displayed in a report. By default, these check boxes are selected. You can set the default selection status in excludeTerminalData (under the <vsa> tag) of the initialization file (config.xml). For details about the initialization file (config.xml), see E. Initialization File (config.xml).

If both check boxes are selected, data that matches the date and time you specified in Start time or End time is displayed.

If both check boxes are cleared, data that matches the date and time you specified in Start time or End time is not displayed.

Maximum number of records

Specify the maximum number of events to be displayed as the event history in the View report page, in the range of 1 to 1440. The default is 1000.

You can specify in PFM - Web Console's initialization file (config.xml) the maximum number of records (maxFetchCount) in the range of 1 to 2,147,483,647. In this case, you can only specify in Maximum number of records a value that is within the range specified in the config.xml file.

Filter

You can set conditions for displaying event history items. The available settings are as follows:

Alarm Name

Specify the alarm name of the event to be displayed by a character string that consists of single-byte or two-byte characters and that is no more than 2,048 bytes. For any alarm name specified by this item, all events resulting in the specified alarm are displayed.

As a default, * (asterisk) is set as a wildcard.

Alarm Table

Specify the alarm table name of the event to be displayed by a character string that consists of single-byte or two-byte characters and that is no more than 2,048 bytes. For any alarm table name specified by this item, all events resulting in any of the alarms in the specified alarm table are displayed.

As a default, * (asterisk) is set as a wildcard.

Message

Specify the message text of the event to be displayed by a character string that consists of single-byte or two-byte characters and that is no more than 2,048 bytes. For any message text specified for this item, all events that output the specified message text are displayed.

As a default, * (asterisk) is set as a wildcard.

1.4.11 Alarm Table Bind Settings [Select Alarm Tables] window

This window is displayed when the functionality for binding multiple alarm tables is enabled. This window is used to bind (associate) or unbind multiple alarm tables and the monitoring agents. To display this window, in the Agents window, on the method frame, choose the Alarm Table Bind Settings method.

The following figure shows the Alarm Table Bind Settings [Select Alarm Tables] window.

Figure 1‒50: Alarm Table Bind Settings [Select Alarm Tables] window

The following describes the displayed items:

Refresh

Updates the Alarm Table Bind Settings [Select Alarm Tables] window to the latest status.

OK button

Associates the monitoring agent selected in the navigation frame of the Agents window with the alarm tables selected in the Contents area, or releases their association.

This button is enabled once you change the selection of alarm tables from the default selection.

Cancel button

Cancels the operation.

Selected alarm tables are displayed when a filter is performed

Use this check box to specify whether to display the selected alarm table when the next filtering is performed.

Selected

The selected alarm table continues to be displayed regardless of whether it satisfies the filtering conditions. The only alarm tables that are displayed are those that are not selected, but satisfy the filtering conditions.

Cleared

Only alarm tables that satisfy the filtering conditions are displayed.

Text box

Use this text box to filter alarm tables by keywords. Note that this functionality cannot be used if the PFM - Manager version is 09-00 or earlier. Specify a character string of 1 to 1,024 characters to filter the alarm tables that will be displayed. To perform a multi-keyword AND or OR search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters alarm tables by using the string specified in the text box. When filtering is performed, the Show User Alarms or Show Template Alarms check box is no longer available.

Clear button

Clears the filtering status and the filtering condition.

AND

Select this option button to perform an AND search.

OR

Select this option button to perform an OR search.

Select All button

Selects all check boxes in the displayed Select column.

UnSelect All button

Clears all check boxes in the displayed Select column.

Show User Alarms

Displayed when the functionality to display separately an alarm table created by the user and an alarm table of the monitoring template is enabled.

Select this check box to view the alarm table created by the user.

Show Template Alarms

Displayed when the functionality to display separately an alarm table created by the user and an alarm table of the monitoring template is enabled.

Select this check box to view the alarm table of the monitoring template.

Contents area

A list of alarm tables is displayed. From these alarm tables, you can select an alarm table you want to bind (associate) or unbind.

Select

Select the applicable check box for an alarm table you want to bind with the monitoring agent. Clear this check box for an alarm table you want to unbind.

Alarm table

Displays alarm table names.

1.4.12 Bind Alarm Table [Select Alarm Tables] window

This window is displayed when the functionality for binding multiple alarm tables is disabled. This window is used to bind (associate) an alarm table and monitoring agents. To display this window, in the Agent window, from the method frame, choose Bind Alarm Table.

The following figure shows the Bind Alarm Table [Select Alarm Tables] window.

Figure 1‒51: Bind Alarm Table [Select Alarm Tables] window

The following describes the displayed items:

Refresh

Updates the Bind Alarm Table [Select Alarm Tables] window to the latest status.

OK button

Binds the monitoring agent selected in the navigation frame in the Agent window to the alarm table selected in the contents area.

This button is enabled only when an alarm table is selected in the alarm table hierarchy.

Cancel button

Cancels the operation.

Text box

Use this text box to filter alarm tables by keywords. Note that this functionality cannot be used if the PFM - Manager version is 09-00 or earlier. Specify a character string of 1 to 1,024 characters to filter the alarm tables that will be displayed. To perform a multi-keyword AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters alarm tables by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Contents area

Displays the alarm table hierarchy. From the alarm table hierarchy displayed here, select the alarm table you want to bind (associate).

1.4.13 Edit Agent Tree window

The Edit Agent Tree window is used to edit agents in the Agents tree. To display this window, from the method frame in the Agents window, choose Edit Agent Tree.

Note that you can use the Edit Agent Tree window only for the agents tree that appears when User Agents is selected in Display format. When Products is selected, the Agents tree cannot be edited.

The following figure shows the Edit Agent Tree window.

Figure 1‒52: Edit Agent Tree window

The following describes the displayed items:

Refresh

Updates the Edit Agent Tree window to the latest status.

Copy button

Copies the selected monitoring agent or folder. This button is enabled only when a monitoring agent or folder has been selected from the Agents tree in the contents area.

Clicking this button displays the Edit Agent Tree > Copy [Select Copy Place] window. If a folder is selected, all of its subfolders and monitoring agents will also be copied.

Delete button

Deletes the selected monitoring agent or folder. This button is enabled only when a monitoring agent or folder has been selected from the Agents tree in the contents area.

Clicking this button displays a message box for confirming your deletion intent. If a folder is selected, all of its subfolders and monitoring agents will also be deleted.

New Folder button

Creates a new management folder for monitoring agents. This button is enabled only when the root or a folder is selected from the Agents tree in the contents area.

Clicking this button displays the Edit Agent Tree > New Folder window.

New Agent button

Creates a new monitoring agent. This button is enabled only when the root or a folder is selected from the Agents tree in the contents area. Clicking this button displays the Edit Agent Tree > New Agent window.

Rename button

Renames the selected folder. This button is enabled only when a folder is selected from the Agents tree in the contents area.

Clicking this button displays the Edit Agent Tree > Rename window.

Text box

Use this text box to filter agents by keywords. Specify a character string of 1 to 1,024 characters to filter the agents that will be displayed. To perform a multi-keyword search by using AND, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters agents by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Contents area

Displays the Agents tree created by the login user. You can edit the Agents tree displayed here.

(1) Edit Agent Tree > Copy [Select Copy Place] window

The Edit Agent Tree > Copy [Select Copy Place] window is used to select the copy destination for the object selected in the contents area of the Edit Agent Tree window. To display this window, in the Edit Agent Tree window click the Copy button.

The following figure shows the Edit Agent Tree > Copy [Select Copy Place] window.

Figure 1‒53: Edit Agent Tree > Copy [Select Copy Place] window

The following describes the displayed items:

Refresh

Updates the Edit Agent Tree > Copy [Select Copy Place] window to the latest status.

OK button

Copies the monitoring agent or folder selected as the copy source to the root or folder selected as the copy destination.

If any of the following is applicable to the folder at the copy destination, the copy operation will be disabled:

The copy destination already contains a folder with the same name as the copy source folder.

Copying the source will exceed the maximum number of hierarchies.

Copying the source will exceed the maximum number of elements per node.

The maximum number of hierarchies is 8. In the root or a folder, the maximum number of folders is 64, and the maximum number of the agents is 128.

Cancel button

Cancels the operation.

Contents area

Displays the Agents tree created by the login user. From the Agents tree displayed here, select the copy destination. The root or a folder can be selected.

(2) Edit Agent Tree > New Folder window

The Edit Agent Tree > New Folder window is used to create a new folder under the object selected in the contents area of the Edit Agent Tree window. To display this window, in the Edit Agent Tree window, click the New Folder button.

The following figure shows the Edit Agent Tree > New Folder window.

Figure 1‒54: Edit Agent Tree > New Folder window

The following describes the displayed items:

OK button

Adds a folder with the name entered in New folder name under the object selected in the Edit Agent Tree window.

If any of the following is applicable to the target folder, the new folder cannot be created:

A folder with the name entered in New folder name already exists.

Adding the folder will exceed the maximum number of hierarchies.

Adding the folder will exceed the maximum number of folders that can be placed in the root or a folder.

The maximum number of hierarchies is 8. The maximum number of folders is 64.

Cancel button

Cancels the operation.

New folder name

Enter a folder name by using 1 to 64 single-byte or two-byte characters.

You can enter both single-byte and two-byte characters for a folder name.

(3) Edit Agent Tree > New Agent window

The Edit Agent Tree > New Agent window is used to create a new agent under the object selected in the contents area of the Edit Agent Tree window. To display this window, in the Edit Agent Tree, click the New Agent button.

The following figure shows the Edit Agent Tree > New Agent window.

Figure 1‒55: Edit Agent Tree > New Agent window

The following describes the displayed items:

Refresh

Updates the Edit Agent Tree > New Agent window to the latest status.

OK button

Adds under the object selected in the Edit Agent Tree window the monitoring agent selected in the contents area.

The maximum number of agents in the root or a folder is 128.

Cancel button

Cancels the operation.

Destination Folder

Displays the path to the folder in the User Agents tree to which the agent selected in this window is added.

Display separately by business group

Displayed when the business group access control functionality is enabled.

If you select this check box, the tree for each business group is displayed.

Display only unregistered agents

Select this check box if you want to display only agents that are not registered in the User Agents tee. To display all agents, clear this check box.

Text box

Use this text box to filter agents by keywords. Specify a character string of 1 to 1,024 characters to filter the agents that will be displayed. To perform a multi-keyword search by using AND or OR, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters agents by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

AND

Select this option button to perform an AND search.

OR

Select this option button to perform an OR search.

Contents area

Displays the Agents tree for products (the root is Products). From this Agents tree, select a monitoring agent that is to be managed in the desired Agents tree. You can select only a monitoring agent.

Tip

If you click the root or a folder, you can select or clear all nodes under the selected folder. If you click a folder in which all or some nodes are cleared, all nodes under the folder are selected. However, if you click a folder that contains only selected nodes, all nodes under the folder are cleared. If there are any subfolders under the folder you click, the status of the nodes contained in the subfolders also changes. In short, you can switch the selection status of all nodes contained in a tree by clicking the root.

(4) Edit Agent Tree > Rename window

The Edit Agent Tree > Rename window is used to rename the folder selected in the contents area of the Edit Agent Tree window. To display this window, in the Edit Agent Tree window, click the Rename button.

The following figure shows the Edit Agent Tree > Rename window.

Figure 1‒56: Edit Agent Tree > Rename window

The following describes the displayed items:

OK button

Renames the folder selected in the Edit Agent Tree window.

If a folder with the same name as the one you entered in New folder name already exists, you cannot change the folder name.

Cancel button

Cancels the operation.

Current folder name

Displays the selected folder's current name. You cannot make an entry in this field.

New folder name

Enter a new folder name by using 1 to 64 single-byte or two-byte characters.

You can enter both single-byte and two-byte characters for a folder name.

1.4.14 Register Bookmark window

The Register Bookmark window enables you to select a report in the agents tree to be registered as a bookmark destination or a combination bookmark destination.

(1) Regist Bookmark > Select Report window

This window is displayed when you select the Regist Bookmark method in the method frame of the Agents window. Note that realtime reports, reports without graphs, and reports specified with display key fields cannot be registered as combination bookmark destinations.

The following figure shows the Regist Bookmark > Select Report window.

Figure 1‒57: Register Bookmark > Select Report window

The following describes the displayed items:

Refresh

Updates the display information in the contents area to the latest status. If you update the display, the selection status of the contents area does not change.

Text box

Use this text box to filter reports by keywords. Specify a character string of 1 to 1,024 characters to filter the reports that will be displayed. To perform a multi-keyword search by using AND, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters reports by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Contents area

Displays the reports tree. By default, System Reports is displayed in the root. When there is a report created by the login user, two trees (User Reports and System Reports) are displayed. Folders and reports you have created are displayed under System Reports or User Reports. Clicking a report opens the Bookmark window as a new window.

(2) Bookmark window

The Bookmark window registers a bookmark for the selected report. You can open this window by clicking Bookmarks at the upper right of the View Report window.

The following figure shows the Bookmark window.

Figure 1‒58: Bookmark window

The following describes the displayed items:

Refresh

Updates the display information of the bookmarks tree to the latest status. If you update the display information, the selection status in the bookmarks tree does not change.

Text box

Use this text box to filter bookmarks by keywords. Specify a character string of 1 to 1,024 characters to filter the bookmarks that will be displayed. To perform a multi-keyword search by using AND, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters bookmarks by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Bookmarks tree

Specifies the locations for storing bookmarks.

An icon is displayed to the left of each component in the bookmarks tree.

The meaning of the icons is as follows:

: Indicates the root.

: Indicates a bookmark folder.

: Indicates a bookmark.

: Indicates a combination bookmark.

: Indicates a registered report. The icon depends on the PFM - Agent or PFM - RM in use.

: Indicates a baseline.

Type a name of the bookmark

When you select the root or a bookmark folder, the specified bookmark name or combination bookmark name is added to the bookmarks tree.

Enter a new bookmark or combination bookmark name by using 1 to 64 single-byte or two-byte characters.

Bookmark type

Use a radio button to select one bookmark or combination bookmark. Available radio buttons vary depending on the report type to be registered (realtime report or historical report) and the bookmarks tree to be selected as follows:

For realtime reports:

When a report is selected from the root or a bookmark folder:

You can use a radio button to select one bookmark only.

When a report is selected from bookmarks or registered reports:

You cannot use a radio button for selection.

For historical reports:

When a report is selected from the root or a bookmark folder:

You can use a radio button to select one bookmark or combination bookmark. The default is Bookmarks.

When a report is selected from bookmarks, combination bookmarks, or registered reports:

You cannot use a radio button for selection.

Note that operation is the same for realtime reports and historical reports when historical reports either are not specified to display graphs in fields or are specified with display key fields. Also note that you cannot select combination bookmarks and registered reports under combination bookmarks for realtime reports, historical reports not specified to display graphs in fields, and historical reports specified with display key fields.

OK button

Operation changes as follows depending on the object selected in the bookmarks tree:

When the root or a bookmark folder is selected:

The report is registered as the destination of the specified bookmark or combination bookmark. When multiple agents are bound to the report, the agent names are delimited with commas (,) when the report is bookmarked.

When a bookmark or a combination bookmark is selected:

The report is added under the selected bookmark or combination bookmark.

When a registered report is selected:

The selected registered report is updated.

Cancel button

Discards the specified settings and closes the Bookmark window.

New Folder button

Creates a new bookmark folder under the selected object. This button is activated only when the root or a bookmark folder is selected in the bookmarks tree. Clicking this button switches to the Bookmark (the folder name entry) window.

(3) Bookmark (the folder name entry) window

The Bookmark window enables you to create a new bookmark folder.

The following figure shows the Bookmark (the folder name entry) window.

Figure 1‒59: Bookmark (the folder name entry) window

The following describes the displayed items:

New Name of the bookmark folder

Enter a folder name by using 1 to 64 single-byte or two-byte characters. You can enter both single-byte and two-byte characters for a folder name.

OK button

Closes the Bookmark (the folder name entry) window and creates a bookmark folder.

Cancel button

Discards the definitions of the Bookmark (the folder name entry) window and closes the window.

1.4.15 Process Monitoring Settings window

The Process Monitoring Settings window is used to set process monitoring in PFM - Agent for Platform and PFM - RM for Platform. The window is opened by selecting PFM - Agent for Platform and PFM - RM for Platform in the Agents window, and then selecting the Process Monitoring Settings method in the method frame.

The following figure shows the Process Monitoring Settings window.

Figure 1‒60: Process Monitoring Settings window

The following describes the displayed items:

Refresh

Updates the Process Monitoring Settings window to the latest status.

Create, Edit, or Delete Applications Definitions and Hide App Definition Templates

Switches between displaying and hiding the application definition template.

Application definitions

Specifies the application definition that will be used. You cannot select multiple definitions.

button

Adds the selected application definition template to Application definitions.

Templates

Use to select a template for the application definition. Depending on the template that is selected, a description is displayed in the area at the bottom.

Edit Templates

Use to edit a template for the application definition. The Process Monitoring Settings > Application Definition Templates window opens.

Create button

Use to create a new application definition. The Process Monitoring Settings > Create a New Application Definition window opens.

If multiple agents are selected in the navigation frame of the Agents window, a new application definition for all the agents you selected is created.

Edit button

Use to edit the selected application definition. The Process Monitoring Settings > Edit an Application Definition window opens.

When multiple agents are selected in the navigation frame of the Agents window, the Process Monitoring Settings > Edit an Application Definition window for the agent at the highest position in the agents tree opens. The definition after the edit is then used to update all agents that have a definition with the same name. In addition, if one or more selected agents stop after the Process Monitoring Settings window appears, you will not be able to edit the definition.

Delete button

Use to delete the application definition you selected. The Process Monitoring Settings > Delete an Application Definition window opens. If multiple agents are selected in the navigation frame of the Agents window, the Process Monitoring Settings > Delete an Application Definition window does not appear. Instead, a dialog box asking if you want to delete the definition appears.

Note that when multiple agents are selected in the navigation frame of the Agents window, the definition is deleted from all the agents you selected. If one or more agents stop after the Process Monitoring Settings window appears, only the application definition on the agents that are running is deleted.

Process monitoring alarm settings

Start button

Binds the alarm table to be used for process monitoring to the agent you selected in the Agents window. If alarm tables are already bound to all the selected agents, this button is not available.

When multiple agents are selected in the navigation frame of the Agents window, the alarm table is bound to all the selected agents.

Stop button

Unbinds the alarm table to be used for process monitoring from the agent you selected in the Agents window. If the alarm table has already been unbound from all the selected agents, this button is not available.

When multiple agents are selected in the navigation frame of the Agents window, the alarm table is unbound from all the selected agents.

(1) Process Monitoring Settings > Create a New Application Definition window or Process Monitoring Settings > Edit an Application Definition window

The Process Monitoring Settings > Create a New Application Definition window is used to select programs, commands, or services for monitoring in order to create new application definitions. The Process Monitoring Settings > Edit an Application Definition window is used to select programs, commands, or services for monitoring in order to edit application definitions.

The following figure shows the Process Monitoring Settings > Create a New Application Definition window.

Figure 1‒61: Process Monitoring Settings > Create a New Application Definition window

The following describes the displayed items:

Cancel button

Discards the settings you specified in this window and returns to the Process Monitoring Settings window.

OK button

Creates a new application definition with the settings you specified in this window. When a definition is edited, the changes you made in this window are applied to the applicable application definition. If one or more selected agents stop when multiple agents have been selected in the navigation frame of the Agents window, processing continues only for the running agents.

Monitoring Targets

Specify the settings for the application you want to monitor.

Load Template button

Use this button to use a template to create a new application definition or to edit an existing application definition. Clicking the Load Template button opens the Process Monitoring Settings > Create a New Application Definition > Input Using Application Definition Template window or the Process Monitoring Settings > Edit an Application Definition > Input Using Application Definition Template window.

Application definitions Name

If you are creating a new application definition, specify the application definition name. If you are editing an existing definition, the application definition name that has been set is displayed. For details about character strings you can specify, see the sections that explain how to collect active and inactive state information or processes in the following manuals: Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, and Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference.

If you specify the same name as an application definition registered on another selected agent when you have selected multiple agents in the navigation frame of the Agents window, a message requesting a different name appears. If this message appears, specify an application definition name that will be unique among the selected agents.

Virtual environment ID

Specify the virtual environment ID. This item is displayed if the selected agent is PFM - Agent for Platform (UNIX) or PFM - RM for Platform.

Agent

Use to select agents for which you want to display a service list registered in the running program, on the active command line, or in the OS.

Add button

Lists the programs running on the agent selected in Agents in the Process Monitoring Settings > Create a New Application Definition > Add from Running Processes or Process Monitoring Settings > Edit an Application Definition > Add from Running Processes window.

Check box

Select those programs that will be subject to the Clear button.

No.

Displays sequence numbers. You cannot edit this item.

Name

If you creating a new application definition, specify the name of a program, command, or service that will be used for execution. If you are editing a definition, the information for the program, command, or service set in the selected application definition is displayed. Change any information that needs to be changed.

For details about specifiable character strings, see the sections that explain how to collect active and inactive state information of processes in the manual Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, the manual Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, and the manual Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference.

Label

If you are creating a new application definition, specify a label for the item. If you are editing a definition, the information about the label for the item set for the selected application definition is displayed. Change any information that needs to be changed. You can specify a maximum of 31 single-byte characters.

Type

Select a type for the item. You can select Program, Command Line, or Services.

To create a template for monitoring agents for Windows, select Program, Command Line, or Services. To create a template for monitoring agents for UNIX, select either Program or Command Line.

Reference note

If you load a template whose type is Services when PFM - Agent for Platform (UNIX) is selected, Type becomes No selection. You will need to specify Program or Command Line for Type.

Minimum

If you are creating a new application definition, specify the lower limit value for the number of programs, commands, or services. If you are editing a definition, the lower limit value for the number of programs, commands, or services, obtained from the entity that will be edited, is displayed.

The initial value is 0. You can change the value, if necessary, to a value from 0 to 65535.

Maximum

If you are creating a new application definition, specify the upper limit value for the number of programs, commands, or services. If you are editing a definition, the upper limit value for the number of processes, obtained from what will be edited, is displayed.

The initial value is 0. You can change the value, if necessary, to a value from 0 to 65535. Note that you must specify a value that is equal to or greater than the value specified in Minimum for Maximum.

Clear button

Clears the value set for the item whose check box is selected to the value listed in the table below. You can use this button when at least one check box is selected.

Table 1‒14: Initial state when the Clear button is clicked

Item in the window

Initial state

Name

The information you entered is cleared.

Label

Monitoringxx#

Type

No selection is displayed.

Minimum

0 is set.

Maximum

0 is set.

#: Where xx is the same value as the value set in No..

Notes on editing application definitions when multiple agents are selected:

If an application definition that has the same name as the selected application definition is on multiple agents, all the applicable application definitions are updated. Make sure that only those agents whose application definition you want to edit are selected.

Note:

If you click the OK button in the window used to create or edit an application definition, an error described in messages from KAVJS2614-E to KAVJS2619-E might occur. If one of these errors occurs, you cannot create or update the application definition. However, the Process Monitoring Settings > Save an Application Definition Template window opens, and you can save the current state of the application definition settings as a template. For details, see 1.4.15(10) Process Monitoring Settings > Save an Application Definition Template window.

(2) Inputs from an application definition template

You can define a process that you want to monitor from a template. To do so, click the Load Template button in the Process Monitoring Settings > Create a New Application Definition or Process Monitoring Settings > Edit an Application Definition window to open the following windows:

For the Process Monitoring Settings > Create a New Application Definition window

The Process Monitoring Settings > Create a New Application Definition > Input Using Application Definition Template window opens.

For the Process Monitoring Settings > Edit an Application Definition window

The Process Monitoring Settings > Edit an Application Definition> Input Using Application Definition Template window opens.

The following figure shows the Process Monitoring Settings > Create a New Application Definition > Input Using Application Definition Template window.

Figure 1‒62: Process Monitoring Settings > Create a New Application Definition > Input Using Application Definition Template window

The following describes the displayed items:

Cancel button

Discards the settings specified in the window and returns to the Process Monitoring Settings > Create a New Application Definition or Process Monitoring Settings > Edit an Application Definition window.

Select button

Applies the selected template and returns to the Process Monitoring Settings > Create a New Application Definition or Process Monitoring Settings > Edit an Application Definition window.

Application Definition Templates

Displays the defined application template.

Select

Selects the template you want to use.

Template Name

Displays the registered template name.

Description

Displays a description of the template.

(3) Adding application definitions from a list of running programs, a list of active command lines, or a list of services

You can add monitoring target processes from a list in any of the following windows:

When creating a new application definition

The following three types of windows are available. You can open these windows by clicking the Add button in the Process Monitoring Settings > Create a New Application Definition window:

The Process Monitoring Settings > Create a New Application Definition > Add from Running Processes window

This window is displayed by default. It is also displayed when Running programs is selected from the pull-down menu.

The Process Monitoring Settings > Create a New Application Definition > Add from Running Processes (Command Lines) window

This window is displayed when Running command lines is selected from the pull-down menu.

The Process Monitoring Settings > Create a New Application Definition > Add from Services window

This window is displayed when Services is selected from the pull-down menu. In PFM - Agent for Platform (UNIX), this window is not displayed.

When editing an application definition

The following three types of windows are available. You can open these windows by clicking the Add button in the Process Monitoring Settings > Edit an Application Definition window:

The Process Monitoring Settings > Edit an Application Definition > Add from Running Processes window

This window is displayed by default. It is also displayed when Running programs is selected from the pull-down menu.

The Process Monitoring Settings > Edit an Application Definition > Add from Running Processes (Command Lines) window

This window is displayed when Running command lines is selected from the pull-down menu.

The Process Monitoring Settings > Edit an Application Definition > Add from Services window

This window is displayed when Services is selected from the pull-down menu. In PFM - Agent for Platform (UNIX), this window is not displayed.

With the exception of a few items, these six windows are almost the same. The following figure shows the Process Monitoring Settings > Create a New Application Definition > Add from Running Processes window.

Figure 1‒63: Process Monitoring Settings > Create a New Application Definition > Add from Running Processes window

The following describes the displayed items. Any differences in display items for a specific window are described.

Cancel button

Returns to the Process Monitoring Settings > Create a New Application Definition or Process Monitoring Settings > Edit an Application Definition window without applying the setting you specified in the window.

OK button

Adds programs, command lines, and services you set in this window as monitored processes and returns to the Process Monitoring Settings > Create a New Application Definition or Process Monitoring Settings > Edit an Application Definition window.

Running Processes

Select the information you want to monitor from the pull-down menu. By default, Running programs is selected. Select either Running command lines or Services if necessary. In PFM - Agent for Platform (UNIX), you cannot select Services.

Display button

Use this button to display a list of information items for Running programs, Running command lines, or Services.

"Running Processes" on the target host

Lists the services registered in running programs, running command lines, or the OS on the monitored host. The name of this item varies depending on the item you selected from the pull-down menu in Running Processes.

Text box

Use this text box to the filter services running on the monitored host, running command lines, or services registered in the OS by keywords. Specify a character string of 1 to 512 characters to filter the services that will be displayed. You cannot perform a multi-keyword search by using AND or OR. Note that this item is not displayed if filtering is not performed, and there are no running programs on the monitored host, there are no running command lines, or there are no services registered in the OS.

Filter button

Filters services by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Data acquisition date

Displays the date the data in the list was acquired. The date is displayed based on the time zone of the monitoring console server.

Select

Use to select programs, command lines, or services you want to update in the Process Monitoring Settings > Create a New Application Definition or Process Monitoring Settings > Edit an Application Definition window. Check boxes are not displayed for items that were entered in the source window.

Process Name, Command Line Name, or Service Name

Displays process names, command line names, or service names. These names are displayed in bold for items entered in the source window.

Instances or Displayed Service Name

When running programs or running command lines are listed, the number of programs or the number of command lines is displayed. Also, when services are listed, the display service name is displayed. These names are displayed in bold for items entered in the source window.

Status

Lists the status of services registered in the OS. This item is displayed only when Services is selected from the pull-down menu. These names are displayed in bold for items entered in the source window. Depending on the value in the State field of the PD_ASVC record for a monitoring agent, either of the following is displayed.

Value in the State field

Displayed value

Running

Active

Other than Running

Inactive

(4) Process Monitoring Settings > Delete an Application Definition window

This window is used to select monitored processes whose application definitions you want to delete.

The following figure shows the Process Monitoring Settings > Delete an Application Definition window.

Figure 1‒64: Process Monitoring Settings > Delete an Application Definition window

The following describes the displayed items:

Cancel button

Discards the settings you specified in the window and returns to the Process Monitoring Settings window.

OK button

Deletes the selected application definition.

Monitoring Targets

Application definition name

Displays the application definition name you set. You cannot edit this item.

Virtual environment ID

When the selected agent is PFM - Agent for Platform (UNIX) or PFM - RM for Platform, the virtual environment ID is displayed. You cannot edit this item.

Agent

Displays the agent name you selected. You cannot edit this item.

Check box

You cannot edit this item.

No.

Displays sequence numbers. You cannot edit this item.

Name

Displays the name of a program, command, or service set in the selected application definition used for execution. You cannot edit this item.

Label

Displays information about the label for the item set in the selected application definition.

Type

Displays the type obtained from the item to be edited. You cannot edit this item.

Minimum

Displays the lower limit value for the number of programs, commands, or services obtained from the item to be monitored. You cannot edit this item.

Maximum

Displays the upper limit value for the number of programs, commands, or services obtained from the item to be monitored. You cannot edit this item.

(5) Process Monitoring Settings > Application Definition Templates window

This window is used to set templates for the application definitions. It is displayed if you select Edit Templates in the Process Monitoring Settings window. From this window, you can create, edit, and delete templates for the application definitions.

The following figure shows the Process Monitoring Settings > Application Definition Templates window.

Figure 1‒65: Process Monitoring Settings > Application Definition Templates window

The following describes the displayed items:

OK button

Accepts the settings and returns to the Process Monitoring Settings window.

Select

Use to select a template for editing or deletion.

Template Name

Lists the templates registered on the selected agent.

Description

Lists the descriptions of the templates registered on the selected agent.

Create button

Use this button to create a new template. The Process Monitoring Settings > Create a New Application Definition Template window opens.

Edit button

Use this button to edit the selected template. The Process Monitoring Settings > Edit an Application Definition Template window opens.

Delete button

Use to delete the selected template. Clicking this button opens the Process Monitoring Settings > Delete an Application Definition Template window.

(6) Process Monitoring Settings > Create a New Application Definition Template window or Process Monitoring Settings > Edit an Application Definition Template window

This window is used to create or edit an application definition template. The following figure shows the Process Monitoring Settings > Create a New Application Definition Template window.

Figure 1‒66: Process Monitoring Settings > Create a New Application Definition Template window

The following describes the displayed items:

Cancel button

Discards the settings you specified in the window and returns to the Process Monitoring Settings > Application Definition Templates window.

OK button

If you are creating a new template, a new template is created with the settings you specified in the window. If you are editing a template, changes you make in the window are applied to the definition.

Monitoring Targets

Specify the settings for the application to be monitored.

Load Template button

Use this button to create a new template from an existing template. This button opens the Process Monitoring Settings > Create a New Application Definition Template > Input Using Application Definition Template or Process Monitoring Settings > Edit an Application Definition Template > Input Using Application Definition Template window.

Template Name

If you are creating a new template, specify the template name. If you are editing a template, the template name that has been set is displayed. For details about specifiable character strings, see the sections that explain how to collect active and inactive state information of processes in the following manuals: Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, and Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference.

Description

If you are creating a new template, enter a description of the template. If you are editing a template, a description of the set template is displayed. You can specify a maximum of 127 single-byte characters or 63 two-byte characters for the description. Note that a linefeed character is treated as two single-byte characters.

Agents

Select the agent for which you want to list running programs.

Add button

Displays the list of running programs you selected in Agents in the Process Monitoring Settings > Create a New Application Definition Template > Add from Running Processes or Process Monitoring Settings > Edit an Application Definition Template > Add from Running Processes window.

Check box

Use to select the programs that will be subject to the Clear button.

No.

Displays sequence numbers. You cannot edit this item.

Name

If you are creating a new template, specify the name of a program, command, or service that will be used for execution. If you are editing a template, information about the selected program, command, or service name you set is displayed. Change any information that needs to be changed.

For details about specifiable character strings, see the sections that explain how to collect active and inactive state information or processes in the following manuals: Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, and Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference.

Label

If you are creating a new template, specify a label for the item. If you are editing a template, information about the label of the item set for the selected template is displayed. Change any information that needs to be changed. You can specify a maximum of 31 single-byte characters for the label.

Type

Select a type of item. You can select Program, Command Line, or Services.

To create a template for monitoring agents for Windows, select Program, Command Line, or Services. To create a template for monitoring agents for UNIX, select either Program, or Command Line.

Minimum

Specify the lower limit value for the number of programs, commands, or services. You can specify a value from 0 to 65535. The initial value is 0.

Maximum

Specify the upper limit value for the number of programs, commands, or services. You can specify a value from 0 through 65535. The initial value is 0. Specify a value equal to or greater than the value specified in Minimum for Maximum.

Clear button

Clears the value set for the item whose check box is selected to the value shown in the table below. You can use this button when at least one check box is selected.

Table 1‒15: Initial state when the Clear button is clicked

Item in the window

Initial state

Name

The information you entered is cleared.

Label

Monitoringxx#

Type

No selection is displayed.

Minimum

0 is set.

Maximum

0 is set.

#: Where xx is the same value as the value set in No..

(7) Inputs from an application definition template

You can define processes that are to be monitored from a template. To do so, click the Load Template button in the Process Monitoring Settings > Create a New Application Definition Template or Process Monitoring Settings > Edit an Application Definition Template window to open the following windows:

For the Process Monitoring Settings > Create a New Application Definition Template window

The Process Monitoring Settings > Create a New Application Definition Template > Input Using Application Definition Template window opens.

For the Process Monitoring Settings > Edit an Application Definition Template window

The Process Monitoring Settings > Edit an Application Definition Template> Input Using Application Definition Template window opens.

For details about these windows, see 1.4.15(2) Inputs from an application definition template. Note that when a window is accessed, application definition in the window name should be replaced with application definition template.

(8) Adding application definition templates from a list of running programs, a list of active command lines, or a list of services

You can add monitoring target processes from a list in any of the following windows:

When creating a new template

The following three types of windows are available. You can open these windows by clicking the Add button in the Process Monitoring Settings > Create a New Application Definition Template window:

The Process Monitoring Settings > Create a New Application Definition Template > Add from Running Processes window

This window is displayed by default. It is also displayed when Running programs is selected from the pull-down menu.

The Process Monitoring Settings > Create a New Application Definition Template > Add from Running Processes (Command Lines) window

This window is displayed when Running command lines is selected from the pull-down menu.

The Process Monitoring Settings > Create a New Application Definition Template > Add from Services window

This window is displayed when Services is selected from the pull-down menu. In PFM - Agent for Platform (UNIX), this window is not displayed.

When editing a template

The following three types of windows are available. You can open these windows by clicking the Add button in the Process Monitoring Settings > Edit an Application Definition Template window.

The Process Monitoring Settings > Edit an Application Definition Template > Add from Running Processes window

This window is displayed by default. It is also displayed when Running programs is selected from the pull-down menu.

Process Monitoring Settings > Edit an Application Definition Template > Add from Running Processes (Command Lines) window

This window is displayed when Running command lines is selected from the pull-down menu.

The Process Monitoring Settings > Edit an Application Definition Template > Add from Services window

This window is displayed when Services is selected from the pull-down menu. In PFM - Agent for Platform (UNIX), this window is not displayed.

With the exception of a few items, these six windows are almost the same. For details about these windows, see 1.4.15(3) Adding application definitions from a list of running programs, a list of active command lines, or a list of services. Note that when a window is accessed, application definition in the window name should be replaced with application definition template.

(9) Process Monitoring Settings > Delete an Application Definition Template window

This window is used to delete an application definition template.

The following figure shows the Process Monitoring Settings > Delete an Application Definition Template window.

Figure 1‒67: Process Monitoring Settings > Delete an Application Definition Template window

The following describes the displayed items:

Cancel button

Discards the settings you specified in the window and returns to the Process Monitoring Settings > Application Definition Templates window.

OK button

Deletes the template you selected.

Monitoring Targets

Template Name

Displays the template name that has been set. You cannot edit this item.

Description

Displays a description of the template. You cannot edit this item.

Agents

Displays the agent name you selected. You cannot edit this item.

Check box

You cannot edit this item.

No.

Displays sequence numbers. You cannot edit this item.

Name

Displays the name used for execution of a program, command, or service set in the selected template. You cannot edit this item.

Label

Displays information about the label for the item set in the selected template. You cannot edit this item.

Type

Displays the type obtained from the item to be edited. You cannot edit this item.

Minimum

Displays the lower limit value for the number of programs, commands, or services obtained from the item to be monitored. You cannot edit this item.

Maximum

Displays the upper limit value for the number of programs, commands, or services obtained from the item to be monitored. You cannot edit this item.

(10) Process Monitoring Settings > Save an Application Definition Template window

This window is used to save the templates for application definitions. The window opens if updating of an application definition in the Process Monitoring Settings > Create a New Application Definition or Process Monitoring Settings > Edit an Application Definition window fails.

The following figure shows the Process Monitoring Settings > Save an Application Definition Template window.

Figure 1‒68: Process Monitoring Settings > Save an Application Definition Template window

The following describes the displayed items:

Cancel button

Discards the settings you specified in the window, and clears the information area.

OK button

Saves the template.

Monitoring Targets

Template Name

Displays the application definition name that was set in the window immediately before updating of the application definition failed. This item is used as a template name.

Description

If the virtual environment ID was set in the window immediately before application definition updating failed, the virtual environment ID is displayed in the following format:

virtual-environment-id:virtual-environment-id-set-in-previous-window

You cannot edit this item.

Agent

Displays the agent name you selected. You cannot edit this item.

Check box

You cannot edit this item.

No.

Displays sequence numbers. You cannot edit this item.

Name

Displays the name used for execution of the program, command, or service specified as the item to be edited. You cannot edit this item.

Label

Displays information about the label for the item to be edited. You cannot edit this item.

Type

Displays the type specified as the item to be edited. You cannot edit this item.

Minimum

Displays the lower limit value for the number of programs, commands, or services specified as items to be edited. You cannot edit this item.

Maximum

Displays the upper limit value for the number of programs, commands, or services specified as items to be edited. You cannot edit this item.

1.4.16 Monitoring Suspension Settings window

The Monitoring Suspension Settings window allows you to check the monitoring status of hosts and monitoring agents, and to configure the settings to suspend or resume monitoring. To display this window, from the method frame in the Agents window, choose Monitoring Suspension Settings.

The following figure shows the Monitoring Suspension Settings window.

Figure 1‒69: Monitoring Suspension Settings window

The following describes the displayed items:

Refresh

Refreshes the information displayed in the Monitoring Suspension Settings window.

Change Settings button

Displays the Monitoring Suspension Settings > Change Settings window. In this window, you can configure the settings to suspend or resume monitoring.

This button is disabled in the following cases:

The processing to suspend or resume monitoring has been performed.

You have logged in as a role other than the administrator role.

In a multiple-monitoring environment, the PFM-Manager for connection destination is on the secondary host.

Display target

Enables you to select from the pull-down menu the type of agents to be displayed in the table frame. The following types are available:

All agents (default)

Agents in the monitored state

Agents in the suspended state

Agents in the unknown state

Table frame

Displays a list of hosts and agents based on the items selected in the navigation frame and Display target.

The following describes the items displayed in the table frame:

Open All button

Displays hosts and agents.

Close All button

Displays hosts only.

List of hosts and agents

Lists the hosts where the agents selected in the navigation frame are installed, and the hosts that are monitored by the agents selected in the navigation frame.

As the agents under each host, agents installed on the host and remote agents that monitor the host are displayed.

The following describes the displayed items:

Host line

Displays the icon indicating a host () and the host name. Clicking this expands or closes the agent lines.

Agent line

Displays the icon indicating each agent and the agent name. If the product name display functionality is enabled, the name is displayed in the product name format.

Agents that are not selected in the navigation frame are displayed as disabled.

For Remote Monitor, clicking the agent name expands or closes the list of remote agents under Remote Monitor. The remote agents under Remote Monitor are displayed by the icons that indicate the following monitoring status and the agent names.

: Remote agent in the monitored state

: Remote agent in the monitoring suspended state

Monitoring status

Displays the monitoring status. The following describes the displayed items:

Host line

Displays the monitoring status of the host and agents under the host.

: Indicates that all the agents under the host are in the monitored state.

: Indicates that the host or all the agents under the host are in the monitoring suspended state.

: Indicates that some of the agents under the host are in the monitored state, and some are in the monitoring suspended state.

, , : Indicates that there are one or more agents where it is unknown whether the monitoring status has been changed.

Agent line

Displays the monitoring status of the agent.

: Indicates that the agent is in the monitored state.

: Indicates that the agent is in the monitoring suspended state, and storage of operating information is also suspended.

: Indicates that the agent is in the monitoring suspended state, but operating information is continuously stored.

, , : Indicates an agent where it is unknown whether the monitoring status has been changed.

Settings - Monitoring suspension

Displays whether monitoring is suspended by specifying hosts or agents

Host line

: Indicates that this host is specified to configure the settings to suspend monitoring.

Blank: Indicates that this host is not specified to configure the settings to suspend monitoring.

, : Indicates that there are one or more agents where it is unknown whether the monitoring status has been changed.

Agent line

: Indicates that this agent is specified to configure the settings to suspend monitoring.

Blank: Indicates that this agent is not specified to configure the settings to suspend monitoring.

, : Indicate an agent where it is unknown whether the monitoring status has been changed.

Settings - DB storage continuation

When monitoring is suspended, this item displays whether the settings are configured so that storage of operating information is continued and monitoring is suspended by selecting Continue recording performance data to StoreDB.

Host line

: Indicates that the settings are configured so that storage of operating information is continued and monitoring is suspended.

Blank: Indicates that the settings are configured so that storage of operating information is also suspended.

, : Indicates that there are one or more agents where it is unknown whether the monitoring status has been changed.

Agent line

: Indicates that the settings are configured so that storage of operating information is continued and monitoring is suspended.

Blank: Indicates that the settings are configured so that storage of operating information is also suspended.

, : Indicates an agent where it is unknown whether the monitoring status has been changed.

(1) Monitoring Suspension Settings > Change Settings window

The Monitoring Suspension Settings > Change Settings window allows you to configure the settings to suspend or resume monitoring for hosts and monitoring agents.

The following figure shows the Monitoring Suspension Settings > Change Settings window.

Figure 1‒70: Monitoring Suspension Settings > Change Settings window

The following describes the displayed items:

Cancel button

Cancels the operation, and displays the Monitoring Suspension Settings window.

Next > button

Displays the Monitoring Suspension Settings > Check Changes window.

This button is enabled when the target to set is selected from the initial display.

Settings types (the Select the processing type for the setup. field)

Suspend monitoring

Select this radio button to suspend monitoring. The radio button is selected by default.

Resume monitoring

Select this radio button to resume monitoring.

Continue recording performance data to StoreDB

Select this check box to continue storage of operating information while monitoring is suspended.

The check box is enabled only if Suspend monitoring is selected.

Settings unit (the Select the processing unit for the setup. field)

Hosts

Select this radio button to suspend or resume monitoring by selecting hosts. The radio button is selected by default.

Agents

Select this radio button to suspend or resume monitoring by selecting agents.

Target to set (the Select the targets to setup. field)

Displays the same information as that displayed in the table frame of the Monitoring Suspension Settings window. The following describes the items that are different from those in the Monitoring Suspension Settings window.

Select All button

Selects all of the displayed check boxes

UnSelect All button

Clears all of the displayed check boxes

Check box (for the host line)

Select this check box if you want to suspend or resume monitoring of all the agents under the host.

The check box appears only if Hosts is selected as the settings unit. The check box is not selected by default.

Check box (for the agent line)

Select the check box for the agent for which you want to suspend or resume monitoring.

The check box appears only if Agents is selected as the settings unit. By default, the check boxes are selected as follows:

If you select agents in the navigation frame, the check boxes for the agents are selected.

If you select the root or a folder in the navigation frame, the check boxes for all agents under the root or the folder are selected.

(2) Monitoring Suspension Settings > Check Changes window

The Monitoring Suspension Settings > Check Changes window allows you to check the items you set in the Monitoring Suspension Settings > Change Settings window.

The following figure shows the Monitoring Suspension Settings > Check Changes window.

Figure 1‒71: Monitoring Suspension Settings > Check Changes window

The following describes the displayed items:

Cancel button

Cancels the operation, and displays the Monitoring Suspension Settings window

< Back button

Displays the Monitoring Suspension Settings > Change Settings window

Execute button

Executes the processing to suspend or resume monitoring, and display the Monitoring Suspension Settings > Check Results window.

Table frame

Displays the same information as that in the table frame of the Monitoring Suspension Settings window. The following describes the items that are different from those in the Monitoring Suspension Settings window.

Check box (for the host line)

The settings specified in the Monitoring Suspension Settings > Change Settings window are displayed as disabled.

The check box is displayed only if you select Hosts as the settings unit in the Monitoring Suspension Settings > Change Settings window.

Check box (for the agent line)

The settings specified in the Monitoring Suspension Settings > Change Settings window are displayed as disabled.

The check box is displayed only if you select Agents as the settings unit in the Monitoring Suspension Settings > Change Settings window.

Monitoring status

For the hosts and agents whose monitoring status will be changed based on the settings specified in the Monitoring Suspension Settings > Change Settings window, the background color is changed and the icon indicating the monitoring status after the status change is displayed.

Settings - Monitoring suspension

For the hosts or agents whose check box is selected in the Monitoring Suspension Settings > Change Settings window, the background color is changed and the following is displayed based on the settings.

: Displayed if you select Suspend monitoring as the settings type.

Blank: Displayed if you select Resume monitoring as the settings type.

Settings - DB storage continuation

For the hosts or agents whose check box is selected in the Monitoring Suspension Settings > Change Settings window, the background color is changed and the following is displayed based on the settings.

: Displayed if you select Suspend monitoring as the settings type, and Continue recording performance data to StoreDB.

Blank: Displayed if you select Suspend monitoring as the settings type, but do not select Continue recording performance data to StoreDB, or if you select Resume monitoring as the settings type.

(3) Monitoring Suspension Settings > Check Results window

The Monitoring Suspension Settings > Check Results window displays the execution results of configuring the settings to suspend or resume monitoring.

The following figure shows the Monitoring Suspension Settings > Check Results window.

Figure 1‒72: Monitoring Suspension Settings > Check Results window

The following describes the displayed item:

OK button

Displays the Monitoring Suspension Settings window.

This button is not displayed while the settings are taking time.

1.5 Reports window

The Reports window is used to create, copy, and edit reports. To display this window, in the navigation frame in any PFM - Web Console window, choose the Reports tab.

If, in the initialization file (config.xml), there is a setting so that the Reports window will not be displayed, the Reports window will not be displayed when you log in with an account that has general user permissions only. For details about the initialization file (config.xml), see E. Initialization File (config.xml).

The following figure shows the Reports window.

Figure 1‒73: Reports window

The following describes the displayed items:

Menu bar frame

Displays a menu that is common to all windows.

For details, see the description of the menu bar frame in 1.3 Main window.

Navigation frame

Displays report definitions hierarchically.

Except for the following items, the display items are the same as the items in the navigation frame of the Main window. For details, see 1.3 Main window.

Text box

Use this text box to filter reports by keywords. Specify a character string of 1 to 1,024 characters to filter the reports that will be displayed. To perform a multi-keyword search by using AND, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filter reports by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Reports tree

The roots are User Reports and System Reports#. The report folders and reports are displayed in alphabetical order beginning on the second level of the hierarchy. The following describes the two roots:

User Reports

Displays hierarchically the report folders and reports created by the user.

System Reports

Displays hierarchically the report folders and reports of the monitoring template installed at the PFM - Agent or PFM - RM installation.

#

When the path to the reports tree is displayed, User Reports and System Reports may be represented as Reports.

Icons

An icon is displayed to the left of each component of the reports tree. For details about icons, see Table 1-9 Configuration component icons and their meaning.

These icons have the following meanings:

: Indicates the root.

: Indicates a report folder.

: Indicates a report. The icon depends on the PFM - Agent or PFM - RM in use.

Note

For PFM - RM or PFM - Agent other than PFM - Agent for Platform, if you have not used the jpcwagtsetup command to register PFM - Agent or PFM - RM, icons for the reports will not be correctly displayed. To correctly display the icons, use the jpcwagtsetup command to register PFM - Agent or PFM - RM, and then restart PFM - Web Console.

Method frame

Displays the operations that can be executed on the reports tree. The operation items that are displayed depend on the selected object.

Show Report Properties

Displays the properties of the selected report definition. When you choose this item, a new window opens and the Properties window appears for the selected report definition.

Copy

Copies the selected report definition. This item is displayed when a report definition is selected in the navigation frame. Selecting this item displays the Copy window. Note that only one report definition can be selected as the copy source.

Delete

Deletes the selected report folder or report definition. This item is displayed when a report folder or a report definition under User Reports is selected in the navigation frame. When a report folder is selected as the deletion target, all the report folders and report definitions under it are also deleted.

When this item is selected, a message box for confirming the deletion intent is displayed.

Edit

Edits the selected report definition. This item is displayed when a report definition under User Reports is selected in the navigation frame. Choosing this item displays the Edit > Name and Type window.

New Folder

Creates a new report folder under the selected object. This item is displayed when User Reports or a report folder under it is selected in the navigation frame. Choosing this item displays the New Folder window.

New Report

Creates a new report under the selected object. This item is displayed when User Reports or a report folder under User Reports is selected in the navigation frame. Choosing this item displays the New Report > Name and Type window.

Rename

Renames the selected report folder or report definition. This item is displayed when a report folder or report definition under User Reports is selected in the navigation frame. Choosing this item displays the Rename window.

Export

Exports the selected report folder or report definition.

If you select User Reports, all definitions are exported.

This item is displayed when User Reports, a report folder, or a report definition is selected in the navigation frame.

Choosing this item executes the export operation and saves the export results in a specified folder.

The export operation executes even when User Reports is selected but there are no reports or report folders defined under User Reports.

Import

Imports the definitions in a specified import file.

Choosing this item displays the Import window.

Information frame

Displays the results of the operation selected in the method frame on the object selected in the navigation frame.

1.5.1 Transitions from the Reports window

The following shows the window transitions from the Reports window:

Figure 1‒74: Window transitions from the Reports window

The following shows the transitions of the transitions of the windows for creating and editing report definitions in wizard format. The following figure shows the transitions from the New Report > Name and Type or Edit > Name and Type window.

Figure 1‒75: Window transitions for creating and editing report definitions

1.5.2 New Folder window

The New Folder window is used to create a new report folder directly under User Reports or under a selected report folder. To display this window, in the Reports window, from the method frame, choose New Folder.

The following figure shows the New Folder window.

Figure 1‒76: New Folder window

The following describes the displayed items:

OK button

Adds a folder with the name entered in Name of new folder under the object selected in the navigation frame. However, if a report folder or a report with the same name already exists at the same hierarchical level, the folder cannot be created.

Cancel button

Cancels the operation and clears the information frame.

Name of new folder

Enter a folder name by using 1 to 64 single-byte or two-byte characters. You can enter both single-byte and two-byte characters for a folder name.

1.5.3 Windows for creating and editing report definitions

The windows for creating and editing report definitions are used to create a new report definition and to change an existing report definition. To display these windows, in the Reports window, from the method frame, choose either New Report or Edit.

The following describes each window.

(1) New Report > Name and Type window or Edit > Name and Type window

The New Report > Name and Type window or Edit > Name and Type window is used to specify a name for a report definition, the product to be reported on, and the type of report.

The following figure shows the New Report > Name and Type window.

Figure 1‒77: New Report > Name and Type window

The following describes the items displayed in these windows:

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

Next > button

Displays the New Report > Field window or Edit > Field window. When a new report is being created, this button is enabled only when entries have been made in Report name and Product.

Finish button

For creating a new report

This button is displayed only when a value has been set in the window displayed by clicking the Next > button. Clicking the Finish button saves the settings.

For editing an existing report

Clicking the Finish button saves the settings.

Report name

For creating a new report

Enter a report definition name by using 1 to 64 single-byte or two-byte characters. You can enter both single-byte and two-byte characters for a report definition name.

For editing an existing report

Displays the report name. This name cannot be changed.

Product

For creating a new report

Select the type (product) of PFM - Agent or PFM - RM for which the report is set. If multiple data model versions are installed for a single product, also select the data model version to be used.

For editing an existing report

This information cannot be changed.

Report type

Select one of the following as the report's type:

Realtime (Single Agent)

Select this to display, as a realtime report, the performance data of one instance of PFM - Agent or PFM - RM.

Historical (Single Agent)

Select this to display, as a historical report, the performance data accumulated by one instance of PFM - Agent or PFM - RM.

Historical (Multiple Agents)

Select this to display in one window, as a historical report, the performance data accumulated by multiple instances of PFM - Agent or PFM - RM. If you select this item, you cannot select a multi-instance record in the New Report > Field window or the Edit > Field window.

(2) New Report > Field window or Edit > Field window

The New Report > Field window or Edit > Field window is used to specify the fields that you want to display in reports.

The following figure shows the New Report > Field window.

Figure 1‒78: New Report > Field window

The following describes the items displayed in these windows:

Description (next to the window title)

Displays the Description of Record and Fields window, which describes the record selected in Record in the New Report > Field or Edit > Field window and its fields, as a separate window.

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

< Back button

Returns to the New Report > Name and Type window or the Edit > Name and Type window.

Next > button

Displays the New Report > Filter window or the Edit > Filter window.

When a new report is being created, this button is enabled only when there is at least one field set in Selected fields.

Finish button

For creating a new report

This button is displayed only when a value has been set in the window displayed by clicking the Next > button. Clicking the Finish button saves the settings.

For editing an existing report

Clicking the Finish button saves the settings.

Record

From the pull-down menu, select a record to be reported. The text box displays the selected record's type ((This is a single-instance record.) or (This is a multi-instance record.)). A single-instance record is a record consisting of a single row, and a multi-instance record is a record consisting of multiple rows.

If in the New Report > Name and Type window or the Edit > Name and Type window, Historical (Multiple Agents) is selected for Report type, only single-instance records are displayed in the pull-down menu.

Description button

Displays the Description of Record and Fields window, which describes the record selected in Record and its fields, as a separate window.

Search Fields button

Displays the New Report > Field > Search Fields or Edit > Field > Search Fields window. This button is not displayed if the data model description file has not been stored. If the data model description file has not been stored, see the PFM - Web Console setup procedure to register PFM - Agent or PFM - RM. For details, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

For details about the New Report > Field > Search Fields or Edit > Field > Search Fields window, see 1.5.3(3) New Report > Field > Search Fields or Edit > Field > Search Fields window.

All fields

Displays a list of the fields in the record that was selected in Record. Use the and buttons to move into Selected fields the fields that you wish to display in the report.

You can use the Shift and Ctrl keys to select multiple fields.

button

Moves the fields selected in All fields to Selected fields.

button

Moves the fields selected in Selected fields back to All fields.

Selected fields

Displays a list of the fields that you wish to have displayed in the report. In the case of a report in table or list format, the fields are displayed in the order they are displayed here. You can use the and buttons to change the order of fields.

button

Moves the field selected in Selected fields so that it precedes the field immediately above it. You can move multiple fields together.

button

Moves the field selected in Selected fields so that it is below the field located immediately below it. You can move multiple fields together.

Explanation of fields:

Displays an explanation of the fields selected in either All fields or Selected fields.

(3) New Report > Field > Search Fields or Edit > Field > Search Fields window

This window can be used to search fields by their characters. You can search a maximum of 50 fields by default. The fields found by the search can be set for Selected fields in the New Report > Field or the Edit > Field window, from which this window was displayed.

The maximum search number can be set in searchLimit of the initialization file (config.xml). For details about the initialization file (config.xml), see E. Initialization File (config.xml).

Note that if you select a record here that is different from the one selected in the New Report > Field or the Edit > Field window, from which this window is opened, the fields selected in that previous window will be cleared.

The following figure shows the New Report > Field > Search Fields window.

Figure 1‒79: New Report > Field > Search Fields window

The following describes the displayed items:

Cancel button

Displays the New Report > Field > Search Fields window or the Edit > Field > Search Fields window again.

Keywords to find

Enter a maximum of 64 characters for the search keywords (including spaces as delimiters). Observe the following precautions related to a search:

To perform a multiple keywords search by using AND, delimit keywords by using a single-byte or two-byte space.

An OR search cannot be performed.

Wildcard characters cannot be used.

A keyword search that consists only of spaces cannot be specified.

Spaces entered at the beginning and ending of a keyword are excluded.

If the search keyword includes spaces, the search will not be performed as intended.

The search is not case sensitive.

In the search keyword, a two-byte character and a single-byte character are recognized as different characters.

A search keyword that includes a line feed code cannot be entered.

After entering the search keyword, click the Search button. The search results will be displayed.

Search results are displayed, depending on the selection in the Records to search pull-down menu, in the following different windows:

If --All records-- is selected in Records to search

The search results are displayed in the "Search results: number-of-records record(s)" window.

If a record name is selected in Records to search

The search results are displayed in the "Search results: List of number-of-fields field(s) found in record record-name" window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records to search. By default, the records selected in Record: in the New Report > Field window or the Edit > Field window are displayed.

In the pull-down menu, the following items are displayed:

--All records--

Select this item to search all records.

List of record names of the selected agent

Displays a list of record names of the selected agent in alphabetical order.

(a) Search results: number-of-records record(s) window

This window displays the number of fields found by the search for each record when --All records-- was selected in Records to search in the New Report > Field > Search Fields or the Edit > Field > Search Fields window. In the search results, the record names are displayed in alphabetical order.

Cancel button

Returns to the New Report > Field or Edit > Field window.

Keywords to find

Enter search keywords. For details, see 1.5.3(3) New Report > Field > Search Fields or Edit > Field > Search Fields window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records you want to search. For details, see 1.5.3(3) New Report > Field > Search Fields or Edit > Field > Search Fields window.

Record name

A record name is followed by the following information:

Number of fields that correspond to the search result

Description of the record

If there is no description, (No explanation provided) is displayed.

Instance type

(This record is a single-instance record.) or (This record is a multi-instance record.) is displayed.

Clicking the menu of a record name lists the corresponding fields of the selected record in the "Search results: List of number-of-fields field(s) found in record record-name" window.

(b) Search results: List of number-of-fields field(s) found in record record-name window

A list of fields is displayed as the search result.

Cancel button

Returns to the New Report > Field or Edit > Field window.

Keywords to find

Enter search keywords. For details, see 1.4.3(1) Quick Guide > Search Fields window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records you want to search. For details, see 1.4.3(1) Quick Guide > Search Fields window.

Go to Record List button

Displays the "Search results: number-of-records record(s)" window again. This button is displayed only if you moved to this window from the "Search results: number-of-records record(s)" window.

OK button

Displays the New Report > Field window or the Edit > Field window again, and the selected fields are displayed in Selected fields.

Check boxes

Select one or more fields.

If you select fields and then click the OK button, you will return to the New Report > Field or Edit > Field window, and the selected fields will appear in Selected fields.

Note that if you return to the "Search results: number-of-records record(s)" window by clicking the Go to Record List button, the check boxes are cleared.

Field name

Displays field names in alphabetical order. Bold characters indicate the characters that match with the search keyword.

Format

Displays the attribute of the corresponding field by using the following icons:

: Numeric attribute

: String attribute

Description

Displays a description of the field. Bold characters indicate the characters that match with the search keyword.

(4) New Report > Filter window or Edit > Filter window

The New Report > Filter window or Edit > Filter window is used to set a filtering condition.

The following figure shows the New Report > Filter window.

Figure 1‒80: New Report > Filter window

The following describes the items displayed in these windows:

Description

Displays the Description of Record and Fields window, which describes the record selected in Record in the New Report > Field or Edit > Field window and its fields, as a separate window.

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

< Back button

Returns to the New Report > Field window or the Edit > Field window.

Next > button

Displays one of the following windows, depending on the circumstances:

When Realtime (Single Agent) is selected

Clicking this button displays the New Report > Indication Settings (Realtime) window or the Edit > Indication Settings (Realtime) window.

Other

Clicking this button displays the New Report > Indication Settings (Historical) window or the Edit > Indication Settings (Historical) window.

Finish button

When creating a new report

This button is displayed only when a value has been set in the window displayed by clicking the Next > button. Clicking the Finish button saves the settings.

When editing an existing report

Clicking the Finish button saves the settings.

Field

From the pull-down menu, select the fields to be filtered.

Condition

From the pull-down menu, select the operator to be used for the conditional expression. The following table lists and describes the operands that can be selected:

Operand

Description

=

The value in Field is equal to the value in Value.

<

The value in Field is smaller than the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

<=

The value in Field is smaller than or equal to the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

>

The value in Field is greater than the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

>=

The value in Field is greater than or equal to the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

<>

The value in Field is any value other than the value in Value.

Value

Specify the value to be compared by using an integer value, a decimal value, or a character string consisting of no more than 2,048 bytes of single-byte or two-byte characters. The permissible values depend on the field. The permitted values are displayed to the right of the text box.

By selecting Specify when displayed, you can omit this value specification.

Specify when displayed

Specifies that a conditional expression value will be specified when a report is displayed. This option applies to each individual conditional expression, not to the entire filter. Therefore, this option is enabled only when a conditional expression is added or updated.

AND

Joins with AND the conditional expression set in Field, Condition, and the target of comparison (Value or Field) and the conditional expressions displayed in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

OR

Joins with OR the conditional expression set in Field, Condition, and the target of comparison (Value or Field) and the conditional expressions displayed in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

Add button

Adds to Conditional expression the conditional expression set in Field, Condition, and Value or Specify when displayed.

Update button

Replaces the conditional expression selected in Conditional expression with the conditional expression set in Field, Condition, and Value or Specified when displayed. This option is enabled only when at least one conditional expression is set in Conditional expression.

Conditional expression

Displays the conditional expressions that have been created. The value in a conditional expression for which Specify when displayed was selected is displayed in the format prompt ("value").

Simple

Handles the conditional expression selected in Conditional expression as a simple expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

Complex

Handles the conditional expressions selected in Conditional expression as a compound expression. However, if it is not possible to handle them as a compound expression, they are handled as simple expressions. This option is enabled only when at least two conditional expressions are set in Conditional expression.

AND <--> OR button

Toggles between AND and OR for the conditional expression selected in Conditional expression. This option is enabled only when the conditional expression selected in Conditional expression is not on the first line and Simple is selected.

Edit button

Displays in Field, Condition, and Value or Specify when displayed the conditional expression selected in Conditional expression to enable it to be edited. This option is enabled only when at least one conditional expression is set in Conditional expression.

Delete button

Deletes the conditional expression selected in Conditional expression. This option is enabled only when a conditional expression is selected in Conditional expression. When Simple is selected, clicking this button executes deletion. When Complex is selected, a message box for confirming your intention to delete all the compound conditions is displayed.

Delete All button

Deletes all conditional expressions set in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

(5) New Report > Indication Settings window or Edit > Indication Settings window

The New Report > Indication Settings window and the Edit > Indication Settings window are used to specify conditions for displaying a field in a realtime report. The window that is displayed depends on the report type selected in Report type in the New Report > Name and Type window or the Edit > Name and Type window.

When Realtime (Single Agent) is selected

The New Report > Indication Settings (Realtime) window or the Edit > Indication Settings (Realtime) window is displayed.

When Historical (Single Agent) or Historical (Multiple Agents) is selected

The New Report > Indication Settings (Historical) window or the Edit > Indication Settings (Historical) window is displayed.

The following describes each window.

(a) New Report > Indication Settings (Realtime) window or Edit > Indication Settings (Realtime) window

The New Report > Indication Settings (Realtime) window and the Edit > Indication Settings (Realtime) window are used to set conditions for displaying a field in a realtime report.

The following figure shows the New Report > Indication Settings (Realtime) window.

Figure 1‒81: New Report > Indication Settings (Realtime) window

The following describes the items displayed in these windows:

Description

Displays the Description of Record and Fields window, which describes the record selected in Record in the New Report > Field or Edit > Field window and its fields, as a separate window.

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

< Back button

Returns to the New Report > Filter window or the Edit > Filter window.

Next > button

Displays the New Report > Indication Settings window or the Edit > Indication Settings window.

Finish button

Saves the settings.

Specify when displayed

Select this option to specify settings when a report is displayed.

Indicate delta value

Specifies that data displayed in a report is to be changed to delta values.

The data displayed in a report differs according to the following conditions:

Whether or not Indicate delta value is selected

Whether or not delta values are collected in the field of the record displayed in the report

Whether or not delta values are collected in a record field depends on the field. For details about delta values and whether or not delta values are to be collected in the record's fields, see the chapter in the PFM - Agent or PFM - RM manuals that describes the records (list of fields in each record).

The following table shows the correspondence between the conditions and the value that is displayed in the report:

Conditions

Displayed value

Indicate delta value check box

Field to be displayed in report

Selected

Delta values are collected

Amount of change from the previously collected performance data to the currently collected performance data

Delta values are not collected

Most recently collected value

Cleared

Delta values are collected

Accumulated value since collection of performance data began#

Delta values are not collected

Most recently collected value

#

In PFM - Agent for Oracle, the amount of change is displayed, not the accumulated value.

Refresh interval

Specify whether or not the displayed realtime report is to be refreshed automatically; if so, specify the refresh interval (the default is 60 (seconds)).

Do not refresh automatically

Specifies that the displayed report is not to be refreshed automatically.

Initial value

If the displayed report is to be refreshed automatically, specify the refresh interval for the report. You can also change this value when the View Reports window is displayed. You must specify an integer in the range from the value set in Minimum value to 3600 (seconds). The default is 60 seconds. When Do not refresh automatically is selected, this option is disabled.

Minimum value

Set as an integer the minimum value that can be specified in Initial value, in the range 10 to 3600 (seconds). The default is 60 seconds. The value set here is also applied to the minimum value for Refresh interval in the Show Options page of the View Report window.

If Do not refresh automatically is selected, this option is disabled.

Display by ranking

Specifies that data is to be arranged in the report in an ascending or a descending order.

This item is displayed when both of the following conditions are satisfied:

Multi-row (multi-instance) records are displayed.

A numeric input field is selected in Field in the New Report > Filter window or the Edit > Filter window.

Field

Select the field on which arranging in ascending or descending order is to be based.

Display number

Specify the number of data items to be displayed, as an integer in the range 1 to 100. Only as many items as specified here will be displayed in the arranged order. This option is enabled only when a field is selected in Field.

In descending order

Specifies that the data is to be arranged in descending order of the values in the field specified in Field. When this option is selected, data is arranged in descending order from higher- to lower-order data. The default is ascending order, in which case data is arranged from lower- to higher-order data.

(b) New Report > Indication Settings (Historical) window or Edit > Indication Settings (Historical) window

The New Report > Indication Settings (Historical) window and Edit > Indication Settings (Historical) window are used to set conditions for displaying a field in a historical report.

The following figure shows the New Report > Indication Settings (Historical) window.

Figure 1‒82: New Report > Indication Settings (Historical) window

The following describes the items displayed in these windows:

Description

Displays a new window containing the description of the record selected in Record in the New Report > Field window or the Edit > Field window and the fields that belong to that record.

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

< Back button

Returns to the New Report > Filter window or the Edit > Filter window.

Next > button

Displays the New Report > Indication Settings window or the Edit > Indication Settings window.

Finish button

Saves the settings.

Specify when displayed

Select this option to specify settings when a report is displayed.

Settings for the report display period

Specifies the period for which data is to be displayed in the report.

Date range

Select the date range for the performance data that is to be collected for display in the report. The default is Specify when displayed.

The following table lists and describes the periods that can be selected as the date range for collecting performance data:

Value

Description

Specify when displayed

Specifies that a date range will be specified when a report is displayed.

Within the past hour

Displays data collected within the past hour.

Within the past 24 hours

Displays data collected within the past 24 hours.

Within the past 7 days

Displays data collected within the past 7 days.

Within the past month

Displays data collected within the past month.

Within the past year

Displays data collected within the past year.

Report interval

Select the report display interval. This item is displayed only for records of the PI record type.

If you select any interval other than Minute, you can display a drilldown report by clicking the location where the time is displayed on the table in the View Report window.

The following table lists and describes the intervals that can be selected as the report display interval and the drilldown reports that can be displayed:

Item

Description

Value displayed in report

Displayed drilldown report

Minute

Displays reports at 1-minute intervals.

The summary result of the data collected between XX:YY:00 and XX:YY:59 is displayed as the data for XX:YY:00. (XX is a value between 0 and 23 and YY is a value between 0 and 59.)

(Not displayed)

Hour

Displays reports at 1-hour intervals.

The summary result of the data collected between XX:00:00 and XX:59:00 is displayed as the data for XX:00:00. (XX is a value between 0 and 23.)

Report with a report interval of Minute covering minute 0 to 59 of the time that is selected by clicking

Day

Displays reports at 1-day intervals

The summary result of the data collected between 00:00 and 23:59 on a day is displayed as the data for 00:00:00 of that date.

Report with a report interval of Hour covering 00:00 to 23:00 of the date that is selected by clicking

Week

Displays reports at 1-week intervals.

The summary result of the data collected between Monday and Sunday is displayed as the data for Monday at 00:00:00.

Report with a report interval of Day covering Monday through Sunday of the week that is selected by clicking

Month

Displays reports at 1-month intervals.

The summary result of the data collected each month is displayed as the data for the 1st of that month at 00:00:00.

Report with a report interval of Week covering the 1st through the 31st of the month that is selected by clicking

Year

Displays reports at 1-year intervals.

The summary result of the data collected each year is displayed as the data for January 1st of that year at 00:00:00.

Report with a report interval of Month covering January through December of the year that is selected by clicking

For details about summary of data, see the chapter that explains the Performance Management functionality in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Note

If the data collection interval (Collection Interval) at the agent is greater than the interval selected in Report interval, the actual display interval will be the data collection interval (Collection Interval) at the agent.

Peak time

Specifies that the display is to be of only the data at the time at which the field specified in Field contains its maximum value for the day (the peak time).

Field

Select the field whose peak-time data is to be displayed.

The record displayed for a day will report the data for the selected field at the time the field's value reached its peak. This item is enabled when all the following conditions are satisfied:

When a single-row record is selected in Record in the New Report > Field window or the Edit > Field window

When a numeric input field is selected in Field in the New Report > Field window or the Edit > Field window

When Hour is selected in Report interval

Maximum number of records

Specify the maximum number of records to be displayed in a report, as an integer in the range of 1 to 2,147,483,647.

For creating a new report, the default is 1,440.

(6) New Report > Components window or Edit > Components window

The New Report > Components window and Edit > Components window are used to specify the report display format.

The following figure shows the New Report > Components window.

Figure 1‒83: New Report > Components window

The following describes the items displayed in these windows:

Description

Displays the Description of Record and Fields window, which describes the record selected in Record in the New Report > Field or Edit > Field window and its fields, as a separate window.

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

< Back button

Displays one of the following windows according to the circumstances:

When Realtime (Single Agent) is selected

Clicking this button displays the New Report > Indication Settings (Realtime) window or the Edit > Indication Settings (Realtime) window.

Other

Clicking this button displays the New Report > Indication Settings (Historical) window or the Edit > Indication Settings (Historical) window.

Next > button

When at least one Graph is selected

Clicking this button displays the New Report > Graph window or the Edit > Graph window.

When no Graph is selected

Clicking this button displays the New Report > Drilldown window or the Edit > Drilldown window.

Finish button

Saves the settings.

Fields

Displays the field selected in the New Report > Field window or the Edit > Field window.

Table

Specifies that the report containing the selected field is to be displayed in table format.

In a table-format report, data for each field is displayed in time series.

List

Specifies that that report containing the selected field is to be displayed as a list per agent or instance.

In a list-format report, field values for each agent or instance are displayed in units of data groups.

Reference

A data group is a set of data for different agents or instances that is grouped by time.

Graph

Select to display the selected numeric field in a graph format. Select only one in the following cases:

When you select Historical (Multiple Agents) for Report type in the New Report > Name and Type or Edit > Name and Type window, and you want to select Line, Area, or Stacked area for Graph types in the New Report > Graph or Edit > Graph window

When you select multi-row records (multi-instance records) for Record in the New Report > Field or Edit > Field window, and you want to select Line, Area, or Stacked area for Graph types in the Graph window

Display name

Specify the name that you want to use as a column name in a table or a list, or the title of a graph by using 0 to 24 single-byte or two-byte characters.

If nothing is specified, the field name is displayed in the report.

Display key

Sets the field to be used as the key for sorting data in multi-row records (multi-instance records).

This option is disabled in the following cases:

The type of this report is Historical (Multiple Agents).

A Line, Area, or Stacked area graph is to be displayed.

Field

From the pull-down menu, select the field to be used as a key for sorting and displaying data.

In descending order

Specifies that data is to be sorted in descending order. This option is enabled when a value other than (none) is selected in Field.

Notes:

When a display key is set, a report takes longer to display. Therefore, if a large number of records are to be displayed, a timeout error might occur. If an error occurs, consider reducing the number of records to be displayed.

The sort order of records that have the same display key is not determined.

If you want to display records for certain instances in chronological order, filter the fields.

(7) New Report > Graph window or Edit > Graph window

The New Report > Graph window and Edit > Graph window are used to specify the type and format of a graph.

The following figure shows the New Report > Graph window.

Figure 1‒84: New Report > Graph window

The following describes the items displayed in these windows:

Description

Displays the Description of Record and Fields window, which describes the record selected in Record in the New Report > Field or Edit > Field window and their fields, as a separate window.

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

< Back button

Returns to the New Report > Indication Settings window or the Edit > Indication Settings window.

Next > button

Displays the New Report > Drilldown window or the Edit > Drilldown window.

Finish button

Saves the settings.

Graph types

Select a graph type. Line, Area, and Stacked area cannot be selected in the following cases:

The type of this report is Historical (Multiple Agents) and more than one field is to be displayed.

The report is for multi-row records (multi-instance records) and more than one field is to be displayed.

In the New Report > Components window or the Edit > Components window, a value is selected in Field under Display key.

Available graph types are as follows:

Column

Displays vertical bar graphs. Graphs for the most recent data group are displayed in snapshot form.#

Stacked column

Displays stacked vertical bar graphs, in which bars that indicate multiple items are stacked on top of each other. Graphs for the most recent data group are displayed in snapshot form.#

Bar

Displays horizontal bar graphs. Graphs for the most recent data group are displayed in snapshot form.#

Stacked bar

Displays stacked horizontal bar graphs, in which bars that indicate multiple items are stacked on the right of each other. A graph for the most recent data group is displayed in snapshot form.#

Pie

Displays pie graphs. Graphs for the most recent data group are displayed in snapshot form.#

Line

Displays line graphs, in which lines show the data change. The horizontal axis indicates time.

Area

Displays area graphs, in which areas show the data change. The horizontal axis indicates time.

Stacked area

Displays stacked area graphs, in which areas that indicate multiple items are stacked on top of each other. The horizontal axis indicates time.

#: For a historical report, the most recent data group within the collection time is displayed. You can also display a past data group by clicking the data group button in the View Report window.

Show areas of missing data

Select in the situation where some data is missing for a reason such as the agent was not active and you want the areas of missing data to be included in the graph.

This option is applicable only when Line, Area, or Stacked area is selected in Graph types.

A graph with areas for missing data can be displayed when all the following conditions are satisfied:

The target to be reported is multi-row records (multi-instance records) or multiple agents.

There is data for other lines or agents covering each time period for which data is missing.

Depending on the type of a graph, some data in a graph might be lost for the following reasons:

For a line graph

A line for missing data is hidden.

For an area graph or a stacked area graph

Assuming a value of 0 for the missing data, the missing data point and the point where the data exists are connected with a straight line to create the display area. If there is missing data for multiple intervals, connect the next previous point where data exists and the point of the last missing data (the value is 0) with a straight line. This will create a display area.

Series direction

Specify the unit used to display data.

By row

Displays a graph by row (record).

By column

Displays a graph by column (field).

Axis labels

Sets character strings to be displayed as the labels for the X and Y axes in the report.

This option is disabled when Pie is selected in Graph types.

X-axis

Specify a string consisting of 0 to 40 single-byte or two-byte characters for the title of the X axis. A two-byte character is counted as one word.

Y-axis

Specify a string consisting of 0 to 40 single-byte or two-byte characters for the title of the Y axis. A two-byte character is counted as one word.

Data label

Sets a maximum of two fields whose data values are to be displayed in the graph.

Data label 1

From the pull-down menu, select the data value of the first field to be displayed in the graph.

When this option is not specified, the first ODBC key field will be set as Data label 1. In this case, if there are multiple ODBC key fields, the second ODBC key field will be set as Data label 2; if there are no ODBC fields, Data label 1 will not be set.

Data label 2

From the pull-down menu, select the data value of the second field to be displayed in the graph. A value for the field selected in Data label 2 is displayed in parentheses following the corresponding value for the field selected in Data label 1.

To set this item, you must set Data label 1 first.

(8) New Report > Drilldown window or Edit > Drilldown window

The New Report > Drilldown window and the Edit > Drilldown window are used to set the drilldown reports at the report and field level that can be accessed from the View Report window.

The following figure shows the New Report > Drilldown window.

Figure 1‒85: New Report > Drilldown window

The following describes the items displayed in these windows:

Description

Displays the Description of Record and Fields window, which describes the records selected in Record in the New Report > Field or Edit > Field window and its fields, as a separate window.

Cancel button

Displays a message box for confirming your intention to cancel the operation. Clicking the OK button in the message box cancels the processing and clears the information frame.

< Back button

When at least one graph is selected in the New Report > Indication Settings window or the Edit > Indication Settings window

Clicking this button returns to the New Report > Graph window or the Edit > Graph window.

Other

Clicking this button returns to the New Report > Indication Settings window or the Edit > Indication Settings window.

Finish button

Saves the settings.

Report drilldown

Sets the drilldown reports for the report level. Select the drilldown reports from existing report definitions or bookmarks.

Report

Lists the drilldown reports that have been added by using the Add button. The reports or bookmarks that are added here are set as drilldown reports.

You can select multiple drilldown reports.

Add button

Adds a drilldown report to Report.

Clicking this button displays the New Report > Drilldown > Select Report window or the Edit > Drilldown > Select Report window.

Change button

Changes the drilldown report selected in Report to become a drilldown report for another report.

Clicking this button displays the New Report > Drilldown > Select Report window or the Edit > Drilldown > Select Report window.

Delete button

Deletes the drilldown report selected in Report.

Field drilldown

Sets a drilldown report at the field level. A drilldown report is selected from the existing report definitions.

Bind button

Sets (binds) the drilldown report in the field selected in Select. Clicking this button displays the New Report > Drilldown > Select Report window or the Edit > Drilldown > Select Report window.

Unbind button

Releases the drilldown report set in the field selected in Select. Clicking this button releases the binding between field and report and displays (No report is selected.) in Report.

Edit Expression button

Sets a filtering condition for the drilldown report that is bound to the field selected in Select. Clicking this button displays the New Report > Drilldown > Select Report > Edit Conditional Expression for Drilldown window or the Edit > Drilldown > Select Report > Edit Conditional Expression for Drilldown window.

Select

Selects a field for which a drilldown report is to be set or released.

Field

Displays the field in the report being defined that has been selected as the target for a drilldown report.

Report

Displays the name of the drilldown report set for the field. If no drilldown report is set, (No report is selected.) is displayed.

(9) New Report > Drilldown > Select Report window or Edit > Drilldown > Select Report window

The New Report > Drilldown > Select Report window and the Edit > Drilldown > Select Report window are used to select a report that is to be bound as a drilldown report to the field selected in the New Report > Drilldown window or the Edit > Drilldown window.

The display of the New Report > Drilldown > Select Report window or the Edit > Drilldown > Select Report window differs depending on the operation you perform in the New Report > Drilldown window or the Edit > Drilldown window:

When you click the Bind button in Field drilldown:

The following figure shows the New Report > Drilldown > Select Report window.

Figure 1‒86: New Report > Drilldown > Select Report window (when you click the Bind button in Field drilldown)

When you click the Add or Change button in Report drilldown:

The following figure shows the New Report > Drilldown > Select Report window.

Figure 1‒87: New Report > Drilldown > Select Report window (when you click the Add or Change button in Report drilldown)

The following describes the items displayed in these windows:

Refresh

Updates the information displayed in the contents area to the latest status. The selection in the contents area remains the same even though the display is updated.

OK button

Applies the specified settings and returns to the New Report > Drilldown window or the Edit > Drilldown window.

Cancel button

Discards the specified settings and returns to the New Report > Drilldown window or the Edit > Drilldown window.

Tree type

This item is displayed only when the Add or Change button in Report drilldown is clicked.

You can select the information to be displayed in the contents area from the pull-down menu. The information that is displayed differs according to whether you select Reports or Bookmarks. By default, Reports is set.

Text box

Use this text box to filter reports or bookmarks by keywords. Specify a character string of 1 to 1,024 characters to filter the reports or bookmarks that will be displayed. To perform a multi-keyword search by using AND, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters reports or bookmarks by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Contents area

When you click the Bind button in Field drilldown, the window displays the reports tree.

If you click the Add or Change button in Report drilldown when Reports is displayed for Tree Type, the window displays the reports tree.

When Bookmarks is selected, the bookmarks tree appears.

In the contents area, from the reports tree or the bookmarks tree, select a report or a bookmark you want to bind as a drilldown report. You can select only one report or bookmark.

(10) New Report > Drilldown > Edit Conditional Expression for Drilldown window or Edit > Drilldown > Select Report > Edit Conditional Expression for Drilldown window

This window sets the filtering conditions for a drilldown report.

The following figure shows the New Report > Drilldown > Edit Conditional Expression for Drilldown window.

Figure 1‒88: New Report > Drilldown > Edit Conditional Expression for Drilldown window

The following describes the items displayed in these windows:

Description

Displays the Description of Record and Fields window, which describes the record selected in Record in the New Report > Field or Edit > Field window and its fields, as a separate window.

OK button

Applies the specified settings and returns to the New Report > Drilldown window or the Edit > Drilldown window.

Cancel button

Discards the specified settings and returns to the New Report > Drilldown window or the Edit > Drilldown window.

Field

From the pull-down menu, select a field to be filtered in the drill down report.

Description button

Displays the Description of Record and Fields window, which describes the field selected in Field and its records, as a separate window.

Condition

From the pull-down menu, select an operator to be used for setting the conditional expression for the selected field. This item is enabled when a field is selected in Field.

For details about the available operators, see 1.5.3(4) New Report > Filter window or Edit > Filter window.

Either a value or a field can be specified as the target of the comparison in the condition.

Value (radio button)

Specifies that a value is to be specified as the target of the comparison.

Value (text box)

Specify the value to be compared by using an integer value, a decimal value, or a character string consisting of no more than 2,048 bytes of single-byte or two-byte characters. The permissible values depend on the field. The permitted values are displayed to the right of the text box.

By selecting Specify when displayed, you can omit this value specification.

Specify when displayed

Specifies that a conditional expression value will be specified when a report is displayed.

This item is enabled only when Value is selected as the target of the comparison with the conditional expression.

Field (radio button)

Specifies that a field is to be selected as the target of the comparison.

Field (pull-down menu)

From the pull-down menu, select a field as the target of the comparison.

The fields displayed in the pull-down menu vary depending on the report type.

For Realtime (Single Agent)

The Record Time field is displayed. If a multi-row record (multi-instance record) is selected, the Instance field is also displayed.

For Historical (Single Agent)

The Date and Time field is displayed. If a multi-row record (multi-instance record) is selected, the Instance field is also displayed.

For Historical (Multiple Agents)

The Date and Time, Agent Host, and Agent Instance fields are displayed.

AND

Joins with AND the conditional expression set in Field, Condition, and the target of comparison (Value or Field) and the conditional expressions displayed in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

OR

Joins with OR the conditional expression set in Field, Condition, and the target of comparison (Value or Field) and the conditional expressions displayed in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

Add button

Adds to Conditional expression the conditional expression set in Field, Condition, and the target of comparison (Value or Field). This button is enabled only when the Value text box or the Field pull-down menu is set.

Update button

Replaces the conditional expression selected in Conditional expression with the new conditional expression set in Field, Condition, and the target of comparison (Value or Field). This option is enabled only when at least one conditional expression is set in Conditional expression.

Conditional expression

Displays a list of conditional expressions that have been created. The value in a conditional expression for which Specify when displayed was selected is displayed in the format prompt ("value").

Simple

Handles the conditional expression selected in Conditional expression as a simple expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

Complex

Handles the conditional expressions selected in Conditional expression as a complex expression. However, if it is not possible to handle them as a complex expression, they are handled as simple expressions. This option is enabled only when at least two conditional expressions are set in Conditional expression.

AND <--> OR button

Toggles between AND and OR for the conditional expression selected in Conditional expression. This option is enabled only when the conditional expression selected in Conditional expression is not on the first line and Simple is selected.

Edit button

Displays the conditional expression selected in Conditional expression in Field, Condition, and Value, and selects the Specify when displayed check box clicking this button also enables you to edit the conditional expression. This button is activated when one or more conditional expressions are set in Conditional expression.

Delete button

Deletes the conditional expression selected in Conditional expression. This option is enabled only when a conditional expression is selected in Conditional expression. When Simple is selected, clicking this button executes deletion. When Complex is selected, a message box for confirming your intention to delete all the compound conditions is displayed.

Delete All button

Deletes all conditional expressions set in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

1.5.4 Import window

The Import window is used to import report folders and report definitions. To display this window, in the Reports window, from the method frame, choose Import. You can import files that were exported from PFM - Web Console.

The following figure shows the Import window.

Figure 1‒89: Import window

The following describes the displayed items:

OK button

Imports the report folders or report definitions from the file specified in Import file name.

Clicking this button displays a message box for confirming the overwrite operation. You must click the OK button in this dialog box to execute the import operation.

Note that the import operation is disabled in the following cases:

The format of the specified file is not supported by PFM - Web Console.

The specified file contains report definitions for an agent that has not been set up by PFM - Manager or PFM - Web Console.

Cancel button

Cancels the operation and clears the information frame.

Import file name

Displays the name of the file that was selected in the dialog box for selecting an import file.

Browse button

Displays a dialog box for selecting the file to be imported.

1.5.5 Properties window

This window displays properties of the selected report definition. To display this window, in the method frame of the Reports window, select the Properties method. This window displays the Properties page only.

The following describes the Properties page.

(1) Properties page

This page displays the report definitions selected in the navigation frame. The displayed information is the settings you specified in the window for creating a new report definition or the window for editing report definitions.

The following figure shows the Properties window (Properties page).

Figure 1‒90: Properties window (Properties page)

Clicking the link displayed at the top of the Properties page jumps to the area in which the applicable information is displayed. For details about the items displayed in each area, see 1.5.3 Windows for creating and editing report definitions.

The following describes the items displayed on this page.

Description

Displays the Description of Record and Fields window as a new window.

Close

Closes the Properties window.

Name and type

This area displays the information set in the New Report > Name and Type or Edit > Name and Type window for report definitions.

Field

This area displays the information set in the New Report > Field or Edit > Field window for report definitions.

Indication settings(Realtime) or Indication settings (Historical)

For a realtime report:

The Indication settings(Realtime) area displays the information set in the New Report > Indication settings(Realtime) or Edit > Indication settings(Realtime) window for report definitions.

For a historical report:

The Indication settings (Historical) area displays the information set in the New Report > Indication settings (Historical) or Edit > Indication settings (Historical) window for report definitions.

Components

This area displays the information set in the New Report > Indication Settings or Edit > Indication Settings window for report definitions.

Graph

This area displays the information set in the New Report > Graph or Edit > Graph window for report definitions.

Drilldown

This area displays the information set in the New Report > Drilldown or Edit > Drilldown window for report definitions.

1.5.6 Copy window

The Copy window is used to copy a selected report definition into a specified report folder. To display this window, in the Reports window, from the method frame, choose Copy.

The following figure shows the Copy window.

Figure 1‒91: Copy window

The following describes the displayed items:

Refresh

Refreshes the information (Reports tree) displayed in the contents area. Refreshing the information does not change the selection status in the Reports tree.

OK button

Executes copying of the selected report definition. If a report folder with the same name already exists at the same hierarchical level, an error results.

If the report folder at the copy destination already contains a report definition with the same name, the copy operation is handled as follows:

When the folders at both the copy source and the target have the same name

The system copies the report definition by automatically appending Copy of to the beginning of the report definition name.

When the folders at the copy source and the copy destination are different

The system displays a message box asking whether the existing data at the copy destination is to be overwritten. When the OK button is clicked in the message box, the system overwrites the existing definition at the copy destination with the definition from the copy source.

Cancel button

Cancels the operation and clears the information frame.

Contents area

Displays the report folders under User Reports that can be selected as the copy destination. You can select only one report folder.

1.5.7 Rename window

The Rename window is used to rename a report folder under User Reports or a report definition. To display the Rename window, in the Reports window, from the method frame, choose Rename.

The following figure shows the Rename window when a report has been selected.

Figure 1‒92: Rename window

The following describes the displayed items:

OK button

Changes the report folder or report definition name. If a report folder or report definition with the same name already exists at the same hierarchical level, the name cannot be changed.

Cancel button

Cancels the operation and clears the information frame.

Current folder name or Current name of the report

Displays the report folder name or report definition name that is to be changed.

Name of new folder or New name of the report

Enter the name of a new report folder or report definition by using 1 to 64 single-byte or two-byte characters. The default is the existing folder name or report definition name (before the change). You can enter both single-byte and two-byte characters for the name.

1.6 Bookmarks window

The Bookmarks window displays the bookmarks tree. By registering reports as bookmark destinations, you can display them with less effort the next time. In addition, you can edit combination bookmarks to specify the display method for combination reports. To display this window, in the navigation frame in any PFM - Web Console window, choose the Bookmarks tab.

The following figure shows the Bookmarks window.

Figure 1‒93: Bookmarks window

The following describes the displayed items:

Menu bar frame

Displays a menu that is common to all windows.

For details, see the description of the menu bar frame in 1.3 Main window.

Navigation frame

Displays the bookmarks tree.

Except for the following items, the display items are the same as the items in the navigation frame of the Main window. For details, see 1.3 Main window.

Text box

Use this text box to filter bookmarks or combination bookmarks by keywords. You cannot filter them by registered reports or baselines. Specify a character string of 1 to 1,024 characters to filter the bookmarks that will be displayed. To perform a multi-keyword search by using AND, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters bookmarks or combination bookmarks by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Bookmarks tree

The root is Bookmarks. At each subsequent level, bookmark folders, bookmarks, and combination bookmarks are displayed in ascending order. Under a bookmark, the registered reports are displayed in ascending order. Under a combination bookmark, the registered reports and the baselines are displayed in ascending order.

Icons

An icon is displayed to the left of each component of the bookmarks tree. For details about icons, see Table 1-9 Configuration component icons and their meaning.

These icons have the following meanings:

: Indicates the root.

: Indicates a bookmark folder.

: Indicates a bookmark.

: Indicates a combination bookmark.

: Indicates a registered report. The icon depends on the PFM - Agent or PFM - RM in use.

: Indicates a baseline.

Method frame

Displays the operations that can be executed on the bookmarks tree. The operation items that are displayed depend on the selected object. Note that if the initialization file (config.xml), editReportByOrdinaryUser is set to off and you log in with an account that has general user permissions only, Delete, New Folder, Rename, and Edit are not displayed. For details about the initialization file (config.xml), see E. Initialization File (config.xml).

Delete

Deletes the selected bookmark folder, bookmark, combination bookmark, registered report, or baseline. This item appears when you select an object below Bookmarks in the navigation frame. Choosing this item displays a message box for confirming the deletion.

When you select a bookmark folder, a bookmark, or a combination bookmark for deletion, all the bookmarks, registered reports, and baselines under the selected object are deleted. When you delete all the registered reports for a bookmark (including cases when only the baselines for combination bookmarks are left), the bookmark itself is automatically deleted.

Display Reports

Displays the selected registered report, bookmark, or combination bookmark. If you select a registered report or a bookmark, the View Report window opens. If you select a combination bookmark, the Combination report window opens. For details about the View Report window, see 1.4.5 View Report window. For details about the Combination report window, see 1.4.7 Combination Report window.

New Folder

Creates a new bookmark folder under the selected object. This item is displayed when Bookmarks or a bookmark folder under Bookmarks is selected in the navigation frame.

Choosing this item displays the New Folder window.

Properties

Displays the properties of the selected bookmark. This item is displayed when a bookmark or a combination bookmark is selected in the navigation frame.

Choosing this item displays the Properties window.

Rename

Changes the name of the selected bookmark folder or bookmark. This item is displayed when a bookmark folder, a bookmark, a combination bookmark, or a baseline is selected in the navigation frame.

Choosing this item displays the Rename window.

Edit

Changes the definition of the selected combination bookmark. This item is displayed when a combination bookmark is selected in the navigation frame. Choosing this item displays the Edit window for combination bookmarks in the information frame.

Tiling Display

Displays side-by-side (tiling display) graphs for historical reports under the selected bookmark folder.

Selecting an item displays the Tiling Display window in the information frame.

Information frame

Displays the results of the operation selected in the method frame on the object selected in the navigation frame.

1.6.1 Transitions from the Bookmarks window

The following shows the window transitions from the Bookmarks window:

Figure 1‒94: Window transitions from the Bookmarks window

1.6.2 New Folder window

The New Folder window is used to create a new bookmark folder under the root or the selected bookmark folder. To display this window, in the Bookmarks window, from the method frame, choose New Folder.

The following figure shows the New Folder window.

Figure 1‒95: New Folder window

The following describes the displayed items:

OK button

Adds a folder with the name specified in Name of new folder under the object selected in the navigation frame. If a bookmark folder or bookmark with the same name already exists at the same level in the hierarchy, the new folder cannot be created.

Any leading and trailing spaces in the entered folder name are deleted automatically.

Cancel button

Cancels the operation and clears the information frame.

Name of new folder

Enter a folder name by using 1 to 64 single-byte or two-byte characters.

You can enter both single-byte and two-byte characters for the folder name.

1.6.3 Edit window

The Edit window enables you to change the display method for the selected combination report. To display this window, in the Bookmarks window, select a combination bookmark. Then, from the method frame, choose the Edit method.

The following figure shows the Edit window.

Figure 1‒96: Edit window

The following describes the displayed items:

OK button

Accepts the specified settings and clears the information frame.

Cancel button

Cancels the operation and clears the information frame.

Settings for the report display period

Enables you to specify a period and a display interval for the report.

Specify when displayed

Select this to display the Show Options page by default when the combination report window is displayed.

This item is inactive if you selected Specify when displayed in Date range.

Date range

From the pull-down menu, select the period for which performance data is to be displayed on the combination report. The default is Specify when displayed.

Available values are as follows:

Specify when displayed

Within the past hour

Within the past 24 hours

Within the past 7 days

Within the past month

Within the past year

Report interval

Sets the display interval reports.

When you specify this item, averaged (summarized) values within the specified period appear in the report.

Available values are as follows:

Minute: Displays reports at 1-minute intervals.

Hour: Displays reports at 1-hour intervals.

Day: Displays reports at 1-day intervals.

Week: Displays reports at 1-week intervals.

Month: Displays reports at 1-month intervals.

Year: Displays reports at 1-year intervals.

When you change the value of Date range, the report interval is set automatically to match the change.

Graph display settings

Sets the title of the graph, the character string to be displayed as the label of the X axis in the report, and the graph options.

Graph title and axis label

Graph title

Enter the name to be used as the graph title set for the combination bookmark by using 1 to 64 single-byte or two-byte characters.

X-axis label

Specify a string consisting of 0 to 40 single-byte or two-byte characters for the title of the X axis.

Graph Options

Show 3D graph

Select this check box to display a 3-dimensional graph.

Show gridlines

Select this check box to display gridlines in the graph.

Gridlines appear only for the series group that has the smallest number displayed in the combination report.

Show AutoLabel

Select this check box to display the value for the corresponding data as a tool tip when you move the cursor onto the plot in a graph.

Series group settings

Sets the format used to display a report registered as a bookmark as a graph. The settings are as follows:

Registered reports

Displays the reports and baselines that are registered as combination bookmarks.

Select a registered report or baseline to be displayed as a series group and use the button and the button to move it to Displayed items.

The names of the registered reports appear in ascending order.

The names of the baselines appear in ascending order following the displayed registered reports.

The registered reports and the baselines displayed in Registered reports do not appear in the graph.

button

Adds the registered report or baseline selected in Registered reports to Displayed items.

button

Returns the registered report or baseline selected in Displayed items to Registered reports.

Series group

From the pull-down menu, select series groups to group the reports registered in the combination bookmark. The default is Series group 1. You can use a maximum of five series groups.

Displayed items

Displays the registered reports and baseline moved from Registered reports. To change the order of the items, use the button and the button.

If no registered reports or baselines are listed in Displayed items, no graph appears in the combination reports whose group is specified in Series group.

Note:

Since Registered reports and Displayed items have a fixed width, you might not be able to view the complete name of a registered report or baseline if it is too long. If the name is too long, check the navigation tree at the left. Note that the order of objects in Registered reports is the same as the order in the navigation tree.

button

Moves the registered report or baseline selected in Displayed items up one position. You can move multiple registered reports or baselines at the same time.

button

Moves the registered report or baseline selected in Displayed items down one position. You can move multiple registered reports or baselines at the same time.

Graph type

Select the types of graphs to be displayed for each series group that is specified.

The following shows the graph types you can select. The default is Line.

Column#

Chronologically displays the data of all fields in the registered reports set for the series group as vertical bar graphs.

Stacked column#

Chronologically displays the data of all fields in the registered reports set for the series group as stacked vertical bar graphs.

Line

Chronologically displays the data of all fields in the registered reports set for the series group as line graphs.

Area

Chronologically displays changes to the data of all fields in the registered reports set for the series group as area graphs.

Stacked area

Chronologically displays the data of all fields in the registered reports set for the series group as stacked area graphs.

#

When you want to display a column or a stacked column graph in 3D form, select Show 3D for Graph options. When doing so, the following conditions must be satisfied. If they are not satisfied, the graph might not be displayed correctly when it is displayed in 3D form.

The graph types for the series group to be displayed must be one of the following combinations:

- Column or stacked column (one series)

- Column or stacked column and line (two series)

- Column or stacked column, and area or stacked area (two series)

Series group name

The name specified here is displayed as the title of the legend or the label of the Y axis. Specify 0 to 40 single-byte or two-byte characters for the series group name.

Manually set the Y-axis value

Select this check box to manually set the Y axis for the specified series group. When this check box is selected, you can specify values in Max. value and Min. value for the Y axis of the series group.

Max. value

Activated when Manually set the Y-axis value is selected. Specify the maximum value for the Y axis of the graph.

Min. value

Activated when Manually set the Y-axis value is selected. Specify the minimum value for the Y axis of the graph.

Y-axis display position

Specify the position for displaying the Y axis of the specified series group. By default, Left side is selected.

Left side

Displays the Y axis of the series group on the left side of a graph.

Right side

Displays the Y axis of the series group on the right side of a graph.

(1) Drawing sequence of graphs in combination reports

The graphs in combination reports can be drawn as follows:

1. By overlaying series groups (in order from series group 1 to series group n)

2. Within a series group, by overlaying registered reports in the same sequence in which they are registered in the series group

3. Within a registered report, by overlaying fields in the same sequence as the sequence in the registered report

When you define a combination bookmark, you can set types 1 and 2 by specifying the drawing sequence of graphs in Series group settings. Set the graphs so they are not hidden when they are drawn. You can set type 3 in the window for creating a new report definition or the window for editing an existing report definition.

Note that either a series group that contains a 3D column or 3D stacked column graph, or a series group that contains a line graph is displayed in the foreground regardless of the order of the series groups. To specify the graph so that it is displayed in the foreground, use the <foregroundCombinationGraph> tag in the initialization file (config.xml). For details, see E. Initialization File (config.xml).

Although you can always set graph options for Show Grid, they are valid only for the foreground graph.

(2) Horizontal axis (X axis) and vertical axis (Y axis) of graphs in a combination report

You cannot specify general settings for an entire combination report.

For the Y axis in a combination report, you can scale automatically for each series group (adjust to the maximum and minimum values of the actual data) or scale manually for each series group (specify the maximum and minimum values). You can select the left side or the right side for the axis label.

The X axis in a combination report is fixed at one time unit.

If the date range and the collection interval do not match, values are considered missing and the data is corrected, resulting in imperfect drawing of the graph. Note that the time unit is not uniform for PD records, since the unit for the collection interval is seconds. Accordingly, using a line graph for PD records is recommended.

The display order of Y-axis scales in a combination report is determined by the graph drawing order.

Of the series groups contained in a combination report, the Y-axis scale of the frontmost series group is drawn at the innermost position (the position closest to the graph). Accordingly, the Y-axis scale of a series group further back is drawn outside the scales of any previous series groups.

(3) Number of fields in a combination report

For combination reports, there is no limit on the number of fields in a report. However, if there are too many fields, a part or all of a graph or a legend might not be visible. If this happens, change the magnification or use one of the following methods to limit the number of fields. The recommended number of fields for display is about 20.

Decrease the number of reports to be displayed in the Edit window for combination bookmarks.

Decrease the number of fields in the Edit window for each report definition, and re-create the registered report.

Add filtering conditions in the Edit window for each report definition, and re-create the registered report.

Set shorter display names for the fields than the default field names in the Edit window for each report definition, and re-create the registered report.

In the following cases, some or all of a graph or a legend might become invisible, or a legend might be displayed in two or more columns.

The magnification is 100% and the legend contains about 20 lines.

The magnification is 200% and the legend contains about 30 lines.

The magnification is 400% and the legend contains about 50 lines.

The magnification is 600% and the legend contains about 50 lines.

The magnification is 800% and the legend contains about 70 lines.

For combination reports, if there are too many characters in a legend, part of the legend might not be visible. If this happens, change the magnification or use one of the following methods to change the number of characters in the legend:

Shorten the report name and re-create the registered report.

Decrease the number of agents to be bound, and re-create the registered report.

In the Edit window for each report definition, set display names for fields that are shorter than the default field names, and re-create the registered report.

In the following cases, part of a legend might become invisible:

The magnification is 100%, and the number of characters is about 50 (two-byte characters) or 80 (single-byte characters).

The magnification is 200%, and the number of characters is about 80 (two-byte characters) or 120 (single-byte characters).

The magnification is 400%, and the number of characters is about 110 (two-byte characters) or 160 (single-byte characters).

The magnification is 600%, and the number of characters is about 140 (two-byte characters) or 200 (single-byte characters).

The magnification is 800%, and the number of characters is about 160 (two-byte characters) or 230 (single-byte characters).

(4) Series group settings in a combination report

For a series group, set at least one registered report. If no registered reports are set for any of the series groups, no graphs are displayed. Graphs are also not displayed when only baselines are set.

For a combination report, if too many characters are set for a series group name, the series group name and the characters for a legend might overlap. To remove the overlap, increase the graph magnification, or reduce the number of characters for the series group name.

For example, if a series group name in a graph has about 25 two-byte or 30 single-byte characters and a legend has about 10 lines, characters might overlap at a graph magnification of 100%. You can avoid any overlap by increasing the magnification to 200%.

(5) Baseline display period for a combination report

The baseline display period (Start time) is determined automatically from the current date and time at which the combination report was started based on the report display period set in Date range and Report interval. If you change the report display period setting (Date range and Report interval), the value is reset to the report display period setting (Start time).

In the View Report window, if you execute Refresh, the report display period settings (Start time and End time) might change due to the setting in Date range, but the baseline display period setting (Start time) does not change.

The start point and the end point of the graph in a combination report are not affected when the start time setting for the baseline display period or the data in the baseline is changed. However, if there is only one piece of data (data in which the start point and the end point are the same) in a registered report to be displayed together with the baseline, the start point and the end point of the graph in the report might be within the range collected in the baseline. In addition, the start point and the end point of the actual graph display period are determined based on the data that exists within the range of the report display period settings (Start time and End time).

The start time setting for the baseline display period is in effect for each baseline. If a baseline has multiple fields and the start time of each field differs, the oldest field data in the time series data is drawn as the start point based on the start time setting for the baseline display period. The start time of other fields is drawn by using the data in effect when the baseline was saved as the start point.

If you register a baseline with multiple fields with different start times, the oldest field data in the time series data is drawn as the start point based on the start time setting for the baseline display period. In this case, the relative start point of each field is kept.

(6) Length of graph titles for a combination report

A maximum of 64 single-byte and two-byte characters can be displayed for a graph title. However, if you display 61 or more two-byte characters for a graph title when the graph magnification is 100%, a line feed might be inserted. No line feed is inserted if single-byte characters are used.

(7) Notes on displaying records of the PD record type in a combination report

In PFM - Web Console version 10-00 or later, if you display records of the PD record type as a column or stacked column graph in a combination report, the following might occur:

The width of a column might be narrower if the interval for collecting records deviates from the normal interval.

When the interval for collecting records is set to one hour or longer, the display positions of columns might not be the same as the display positions in PFM - Web Console version 09-00 or earlier.

Accordingly, when you display PD-record type records in a combination report in PFM - Web Console version 10-00 or later, we recommend that you use line graphs.

1.6.4 Properties window

The Properties window displays the properties of the selected bookmark or combination bookmark. To display this window, in the Bookmarks window, select a bookmark or a combination bookmark. Then, from the method frame, choose the Properties method. When you select a combination bookmark, the information about baselines as well as the registered reports is displayed in the same format. Note that you cannot change the settings of properties in the Properties window.

The following figure shows the Properties window.

Figure 1‒97: Properties window

The following describes the displayed items:

Bookmark name

Displays the name of the selected bookmark.

Registered report name

Displays the name of the report registered in the selected bookmark.

Original report name

Displays the name of the original report for the report that is displayed in Registered report name.

Bound agents

Displays the agent name for the report registered in the selected bookmark.

Conditional expression

Displays the conditional expression registered in the selected bookmark.

Business group name

Displays the name of the business group to which the agent displayed in Bound agents belongs. This item is displayed when the business group access control functionality is enabled.

1.6.5 Rename window

The Rename window enables you to change the name of the selected bookmark folder, bookmark, combination bookmark, or baseline. To display this window, in the Bookmarks window, select a bookmark folder or a bookmark, and then from the method frame, choose Rename.

The following figure shows the Rename window.

Figure 1‒98: Rename window

The following describes the displayed items:

OK button

Renames the selected bookmark folder or bookmark.

If a bookmark folder or bookmark with the same name already exists at the same hierarchical level, the bookmark folder or bookmark cannot be renamed. Any leading and trailing spaces in the entered name are deleted automatically.

Cancel button

Cancels the operation and clears the information frame.

Current folder name or Current name of the bookmark folder

Displays the name of the selected bookmark folder or bookmark before the change.

Name of new folder or New name of the bookmark folder

Enter the name of a new bookmark folder or a bookmark by using 1 to 64 single-byte or two-byte characters. The default is the existing bookmark folder name or bookmark name (before the change). You can enter both single-byte and two-byte characters for the name.

1.6.6 Tiling Display window

The Tiling Display window displays, side by side, the graphs for historical reports managed by the selected bookmark.

However, a tiling display cannot display the following reports:

Realtime reports, and historical reports without graphs

Icons are displayed by tiling display.

Combination reports, baselines

Not displayed by tiling display.

This window is displayed if, in the Bookmarks window, a bookmark folder or bookmark is selected and, in the method frame, the Tiling Display method is selected.

The following figure shows the Tiling Display window.

Figure 1‒99: Tiling Display window

The following describes the displayed items:

Refresh

Refreshes the tiling display in the information frame. It also refreshes the date displayed next to Refresh date.

Save Layout

Saves the layout information of the graphs. This menu is not displayed in the sort mode (When Arrange tile order is selected).

The following layout information is saved:

The number of columns set in the Display layout area of the Tiling Display Settings window

The positions of the graphs moved in the sort mode

Clicking this menu displays a dialog box that confirms you really want to save the layout. Clicking the OK button saves the layout information.

If you click the Cancel button in the confirmation dialog box, processing to save the layout will stop.

Note

If you delete or add a report, the saved layout information is disabled, and then the display returns to the default layout (order: in the order of graph names, number of columns: three).

Display Settings

Switches the display in the information frame to the Tiling Display Settings window. This menu is not displayed in the sort mode.

In the Tiling Display Settings window, you can set the display period for the report. For details about the Tiling Display Settings window, see 1.6.6(1) Tiling Display Settings window.

Arrange tile order

Selecting this check box switches to the sort mode, in which you can change the display position of a graph.

Clearing this check box switches to the display mode.

By default, this check box is cleared (display mode).

After you switch to the sort mode, grids are displayed, which you can select for the destination of a graph. To move a graph, click the graph you want to move and then the grid for the destination.

Figure 1‒100: Arranging graphs in the sort mode

If you want to save the arrangement of a graph after it is moved, clear the Arrange tile order check box to switch to the display mode, and then click Save Layout.

Refresh date

Displays the refresh date of the tiling display. Clicking the Refresh button refreshes the tiling display and the refresh date.

You can specify the display format of the date and time in the initialization file (config.xml). For details about the date-and-time display format, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Tiling Display area

Displays graphs for historical reports side by side. By default, graphs are displayed in alphabetical order of their names from left to right.

In the sort mode (when Arrange tile order is selected), the grid indicating the destination is displayed. In the display mode, clicking a graph separately displays the report.

You can change the layout of the graphs by using the following methods:

Moving the positions of the graphs

Select Arrange tile order, switch to the sort mode, and then move the positions.

Changing the number of columns

In the Display layout area of the Tiling Display Settings window, which is launched by clicking the Display Settings menu, specify the number of graphs that can be displayed in rows in the range from 2 to 4.

The maximum number of graphs in the tiling display is 50 by default. If the number of the graphs is more than the maximum number, a notification message is sent.

You can change this maximum number in maxTileReports in the initialization file (config.xml). Note that if the maximum number is set to 50 or more, the workload of the server increases. For details about the initialization file (config.xml), see E. Initialization File (config.xml).

Reference note

When the report series paging functionality is enabled, a graph field might be divided into multiple pages. If you want to tile these reports, the graphs on the first page are tiled.

For details about how to set the report series paging functionality and items that can be set, see the chapter that explains installation and setup of Performance Management in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

(1) Tiling Display Settings window

To display the Tiling Display Settings window, in the Tiling Display window, choose the Tiling Display Settings menu. The following figure shows the Tiling Display Settings window.

Figure 1‒101: Tiling Display Settings window

OK button

Clicking this button applies the settings specified in the Tiling Display Settings window.

Settings for the report display period

Displays the following information.

Date range

From the pull-down menu, select the date range shown below. By default, Within the past 24 hours is selected.

- Specify when displayed

- Within the past hour

- Within the past 24 hours

- Within the past 7 days

- Within the past month

- Within the past year

- If you select one of the above, other than Specify when displayed, the corresponding date and time are automatically set in Start time and End time.

Start time

If you select an item other than Specify when displayed in Date range, the start time is displayed depending on the selected date range.

To change the start time, specify the time in the format displayed in the right of the input field of Start time. The meanings of the elements in the time format are as follows:

- YYYY: Year

- MM: Month

- DD: Day

- hh: Hour

- mm: Minute

You can specify the time in the range from 00:00, January 1, 1971 to 23:59, December 31, 2035.

End time

If you select an item other than Specify when displayed in Date range, the end time is displayed depending on the selected date range.

To change the end time, specify the time in the format displayed in the right of the input field of End time. The meanings of the elements in the time format are as follows:

- YYYY: Year

- MM: Month

- DD: Day

- hh: Hour

- mm: Minute

You can specify the time in the range from 00:00, January 1, 1971 to 23:59, December 31, 2035.

For End time, specify the time that comes after the time specified for Start time.

Report interval

From the pull-down menu, select the report interval as shown below. The default interval is displayed depending on the period selected in Date range.

- Minute

- Hour

- Day

- Week

- Month

- Year

Target reports

Apply to all reports

Use this check box to define how the settings specified in Settings for the report display period are applied. By default, this check box is cleared.

If this check box is selected, settings are applied to all reports regardless of the report definitions. If it is cleared, settings are applied only to those reports for which Specify when displayed is set for Date range.

Display the start time data and Display the end time data

Use these check boxes to switch between displaying and hiding the data that matches the date and time you specified in Start time or End time for the data that will be displayed in a report. By default, these check boxes are selected. You can set the default selection status in excludeTerminalData (under the <vsa> tag) of the initialization file (config.xml). For details about the initialization file (config.xml), see E. Initialization File (config.xml).

When both check boxes are selected, data that matches the date and time you specified in Start time or End time is displayed.

When they are cleared, data that matches the date and time you specified in Start time or End time is not displayed.

Display layout

Specify the maximum number of graphs that can be displayed in a row in the Tiling Display window. The specifiable values are shown below. If you increase the number to be displayed, each of the displayed graphs will be smaller.

The default number is three.

- Number of columns: 2

- Number of columns: 3

- Number of columns: 4

If you change the value for Display layout, the order of the graphs changes to the default (alphabetical order by name).

1.7 Alarms window

The Alarms window is used to create, copy, and edit alarm tables and alarms. To display this window, in the navigation frame of any PFM - Web Console window, choose the Alarms tab.

Only a login user with the administrator user permission can display this window.

The following figure shows the Alarms window.

Figure 1‒102: Alarms window

The following describes the displayed items:

Menu bar frame

Displays a menu that is common to all windows.

For details, see the description of the menu bar frame in 1.3 Main window.

Navigation frame

Displays the alarm hierarchically.

Except for the following items, the display items are the same as the items in the navigation frame of the Main window. For details, see 1.3 Main window.

Text box

Use this text box to filter alarm tables or alarms by keywords. Note that you cannot use the filtering function for PFM - Manager version 09-00 or earlier.

Specify a character string of 1 to 1,024 characters to filter the alarm tables or alarms that will be displayed. To use multiple conditions for an AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters alarm tables or alarms by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Alarms tree

The root differs depending on whether the functionality for displaying alarm trees separately is enabled or disabled.

When enabled

User Alarms and Template Alarms.

When disabled

Alarms

The following objects are displayed in the second and lower levels of the hierarchy:

Second level of the hierarchy

Displays alarm folders for each PFM - Agent or PFM - RM program that has been set up.

Third level of the hierarchy

Displays alarm tables prepared as monitoring templates for each PFM - Agent or PFM - RM, and alarm tables optionally created by users. The monitoring templates are prepared for each data model version.

Fourth level of the hierarchy

Displays the alarms defined in each alarm table.

Icons

An icon is displayed to the left of each component of the alarms tree. For details about icons, see Table 1-9 Configuration component icons and their meaning.

These icons have the following meanings:

: Indicates the root.

: Indicates an alarm folder.

: Indicates an alarm table.

: Indicates an alarm.

Method frame

Displays the operations that can be executed on the alarms tree. The operation items that are displayed depend on the selected object.

Properties

Displays the properties (definition) of the selected alarm. This item is displayed when an alarm is selected in the navigation frame. Choosing this item displays the Service Properties window.

New Alarm Table

Creates a new alarm table under the selected alarm folder. This item is displayed only when the following item is selected in the navigation frame:

When the functionality for displaying alarm trees separately is enabled

An alarm folder under User Alarms

When the functionality for displaying alarm trees separately is disabled

An alarm folder created by a user

Choosing this item displays the New Alarm Table > Main Information window.

New Alarm

Creates a new alarm under the selected alarm table. This item is displayed only when the following item is selected in the navigation frame:

When the functionality for displaying alarm trees separately is enabled

An alarm table under User Alarms

When the functionality for displaying alarm trees separately is disabled

An alarm folder created by a user

Choosing this item displays the New Alarm > Main Information window.

Copy

Copies the selected alarm table or alarm. This item is displayed only when the following item is selected in the navigation frame:

When the functionality for displaying alarm trees separately is enabled

An alarm table or an alarm under User Alarms

When the functionality for displaying alarm trees separately is disabled

An alarm table or an alarm created by a user

Selecting this item displays the Copy window. If the functionality for displaying alarm trees separately is enabled, the alarm table or alarm you selected is copied to the applicable alarm folder under the User Alarms folder. If the functionality is disabled, the alarm table or alarm you selected is copied to the same location as the copy source alarm table.

Edit

Edits the selected alarm's definition. This item is displayed only when the following item is selected in the navigation frame:

When the functionality for displaying alarm trees separately is enabled

An alarm under User Alarms

When the functionality for displaying alarm trees separately is disabled

An alarm created by a user

Choosing this item displays the Edit > Main Information window.

Delete

Deletes the selected alarm table or alarm. This item is displayed only when the following item is selected in the navigation frame:

When the functionality for displaying alarm trees separately is enabled

An alarm table or an alarm under User Alarms

When the functionality for displaying alarm trees separately is disabled

An alarm table or an alarm created by a user

When this item is selected, a message box for confirming the deletion intent is displayed. If an alarm table is selected as the deletion target, all the alarms under it are also deleted.

Activate

Enables the active setting to be specified for the selected alarm table or alarm. This item is displayed when an alarm table or alarm is selected in the navigation frame.

Choosing this item displays the Active Setting window.

Show Bound Agents

Lists the monitoring agents that are bound to (associated with) the selected alarm table. This item is displayed when you select an alarm table in the navigation frame.

Choosing this item displays the Show Bound Agents window.

Export

Exports the definitions under the selected alarm folder or alarm table.

This item is displayed when the root, an alarm folder, or an alarm table is selected in the navigation frame. If you select the root, all definitions under the root folder are exported.

Choosing this item displays a dialog box for selecting the file output destination, enabling you to save the export results in a desired folder.

Import

Imports alarm definitions from a specified import file.

Choosing this item displays the Import window.

Information frame

Displays the results of the operation selected in the method frame on the object selected in the navigation frame.

1.7.1 Transitions from the Alarms window

The following shows the window transitions from the Alarms window:

Figure 1‒103: Window transitions from the Alarms window

The following shows the transitions of the windows for creating a new alarm table, for creating a new alarm, and for editing an existing alarm transition in wizard format. The following figure shows the transitions from the New Alarm Table > Main Information window and the New Alarm > Main Information window and Edit > Main Information window.

Figure 1‒104: Window transitions for creating a new alarm table and for creating a new alarm or editing an existing alarm

1.7.2 Import window

The Import window is used to import alarm folders, alarm tables, and alarms. To display this window, in the Alarms window, from the method frame, choose Import.

You can import the following files:

Files exported from PFM - Web Console

Alarm definition files included in the agent's setup file

The following figure shows the Import window.

Figure 1‒105: Import window

The following describes the displayed items:

OK button

Imports the alarm folders, alarm tables, and alarms in the file set in Import file name.

Clicking this button displays a message box for confirming the overwrite operation. Clicking the OK button in this message box executes the import operation.

Note that an import operation will be disabled in the following cases:

Format of the specified file is not supported by PFM - Web Console.

The specified file contains alarms for an agent that has not been set up by PFM - Manager or PFM - Web Console.

The specified file contains the settings items that are not supported by the version of PFM - Web Console.

Cancel button

Cancels the operation and clears the information frame.

Import file name

Displays the file name you selected in the dialog box for selecting an import file.

Browse button

Displays a dialog box for selecting an import file.

Important note

If importing an alarm table overwrites the alarm table already bound by the monitoring agent, the binding is released. Bind the alarm table again, as necessary.

1.7.3 Window for creating a new alarm table definition

This window is used to create a new alarm table definition. To display this window, in the Alarms window, from the method frame, choose New Alarm Table. The New Alarm Table > Main Information window is displayed.

The following figure shows the New Alarm Table > Main Information window.

Figure 1‒106: New Alarm Table > Main Information window

The following describes the displayed items:

Cancel button

Cancels creation of an alarm table.

Next > button

Displays the next window. This button is enabled when Product, Alarm table name, and Alarm name are specified.

For details, see 1.7.4(1) New Alarm > Main Information window or Edit > Main Information window.

For details , see 1.7.4(1) New Alarm > Main Information window or Edit > Main Information window.

Finish button

Saves the settings, and ends creation of the alarm table.

This button is available when values are entered in Product, Alarm table name, and Alarm name, and values are set in the New Alarm Table > Alarm Conditions window, which opens next.

General settings

Explains the definition items for an alarm table. Except for the following items, the items in the window are alarm definition items. For details about the alarm definition items, see 1.7.4(1) New Alarm > Main Information window or Edit > Main Information window. Make sure to replace New Alarm, a window name in the reference section, with New Alarm Table.

Product

From the pull-down menu, select the type of PFM - Agent or PFM - RM product for which an alarm table is to be created. In the pull-down menu, the PFM - Agent or PFM - RM products are displayed. If multiple data model versions are installed on PFM - Agent or PFM - RM, the version is displayed in parentheses.

This item can be set only when a new alarm table is to be created. It cannot be changed when alarms are added or edited.

Alarm table name

Specify the alarm table name by using no more than 64 bytes of two-byte characters, single-byte alphanumeric characters, the single-byte symbols % - ( ) _ . / @ [ ], and spaces. This name cannot begin with PFM, whether upper case or lower case.

This item can be set only when a new alarm table is to be created. It cannot be changed when alarms are added or edited.

Advanced settings

These are alarm definition items. For details, see 1.7.4(1) New Alarm > Main Information window or Edit > Main Information window.

1.7.4 Windows for creating new alarm definitions and editing existing alarm definitions

These windows create a new alarm definition or edit an existing alarm definition. Selecting New Alarm or Edit in the method frame of the Alarms window switches to the window for creating a new alarm definition or the window for editing an alarm definition.

The following describes each window.

(1) New Alarm > Main Information window or Edit > Main Information window

The New Alarm > Main Information window and the Edit > Main Information window are used to set basic alarm information.

The following figure shows the New Alarm > Main Information window.

Figure 1‒107: New Alarm > Main Information window

The following describes the items displayed in these windows:

Cancel button

Cancels alarm creation or editing.

Next > button

Displays one of the following windows, depending on the circumstances:

When Monitor whether the value exists is selected

Clicking this button displays the New Alarm > Alarm Conditions window or the Edit > Alarm Conditions window (for setting the value to be monitored for).

When Monitor whether the value exists is not selected

Clicking this button displays the New Alarm > Alarm Conditions window or the Edit > Alarm Conditions window (for setting the alarm conditional expression).

This button is enabled when Product, Alarm table name, and Alarm name are specified.

Finish button

Saves the settings and finishes alarm creation or editing.

This button is enabled when Product, Alarm table name, and Alarm name have been set and values have been set in the next window (either the New Alarm > Alarm Conditions window or the Edit > Alarm Conditions window).

(a) General settings

Product

Displays the type of PFM - Agent or PFM - RM product for which an alarm is to be created.

This setting cannot be changed.

Alarm table name

Displays the name of the alarm table for which an alarm is to be created.

This setting cannot be changed.

Alarm name

Specify the alarm name by using no more than 20 bytes of two-byte characters, single-byte alphanumeric characters, the one-byte symbols % - ( ) _ . / @ [ ], and spaces.

Alarm message

Specify the message to be displayed in the Event Monitor window if an alarm occurs, or the message to be sent for an SNMP trap by using no more than 255 bytes of single-byte or two-byte characters. This item is optional.

Specifying variables enables you to display alarm-related information.

The following table lists and describes the variables that can be specified.

Variable

Description

%AIS

Represents the alarm name set in Alarm name.

%ANS

Represents the name of the agent to which this alarm table is bound.

%ATS

Represents the name of the alarm table for which this alarm is defined.

%CVS[n][.p]#1,#2,#3,#5

Represents the measurement value that triggered the alarm report (that satisfied the conditional expression).

n#4

Specifies the position of the field as 1 or a greater numeric value when more than one conditional expression is specified in the New Alarm > Alarm Conditions window or the Edit > Alarm Conditions window. If 0 or a value greater than the number of conditional expressions is specified, the measurement value in the first field is displayed.

p#4

For a field that is replaced with an integer or a decimal value

Specifies the number of decimal places to be displayed (rounded).

For a field whose measurement value is replaced with a string

Specifies the position of a string that is to be displayed from the strings whose measurement value can be delimited by a single-byte space. If you want to specify the position, specify 1 or a larger value. If you specify 0, the measurement value is displayed as is. If you specify a value greater than the number of strings that can be delimited by the single-byte space, a 0-byte string replaces the variable.

If the alarm conditions are as below and you want to evaluate Mbytes Free % by using %CVS, %CVS2 must be used:

(Mbytes Free % < "5"

AND File System <> "/usr")

AND Available Space % < "10"

In this case, the evaluation is performed in the following order:

(Mbytes Free % < "5" Second

AND File System <> "/usr") Third

AND Available Space % < "10" First

To evaluate from the top by using %CVS, change the alarm conditions to as follows:

Mbytes Free % < "5"

(AND File System <> "/usr"

AND Available Space % < "10")

In this case, the evaluation is performed in the following order:

Mbytes Free % < "5" First

(AND File System <> "/usr" Second

AND Available Space % < "10") Third

%HNS

Represents the name of the host where the agent to which this alarm table is bound is running.

%PTS

Represents the product name set in Product.

%SCS

Represents the alarm condition that triggered output of the message. OK, WARNING, or EXCEPTION is displayed. Their meanings are as follows:

OK: Normal

WARNING: Warning

EXCEPTION: Abnormal

%SCT

Represents the system time at the host where the agent whose alarm was evaluated is running.

#1: If the alarm status changes from Abnormal or Warning to Normal for an alarm definition that uses multiple instance records, the value stored in the %CVS variable will be as follows:

If the function for measurement value output at alarm recovery is enabled

The current measurement value of the instance that triggered the last issued abnormal or warning alarm is stored until the alarm status returns to normal.

If this function is disabled

Because the measurement value that satisfies the condition expression does not exist, the <OK> string is stored. Accordingly, if a value of 2 or more is specified for p in %CVSn.p, %CVS is replaced with a zero-byte string.

For details about the function for measurement value output at alarm recovery, see the chapter that explains operation monitoring by using alarms in the Job Management Partner 1/Performance Management User's Guide.

#2: The maximum length of the character string generated after the variable %CVS is substituted with its value is 79 bytes.

If multiple alarm conditions exist, the total of "the total length of replaced characters for all conditional expressions" and "the number of alarm conditions minus 1" must be no more than 79 bytes.

The following shows an example where three alarm conditions are defined:

Mbytes Free % < "5"

(AND File System <> "/usr"

AND Available Space % < "10")

In this case, %CVS for each conditional expression is replaced as follows:

Evaluation results of Mbytes Free % < "5" => %CVS1

Evaluation results of File System <> "/usr" => %CVS2

Evaluation results of AND Available Space % < "10" => %CVS3

In this example, the total length of the replaced characters for all conditional expressions can be calculated as follows:

Therefore, if three conditional expressions are defined, a maximum of 77 (79 minus 2) bytes can be replaced.

If the result of replacement is more than 79 bytes, only the characters in the first 79 bytes are used and the following characters are discarded.

For example, assume that as the result of replacement of the above conditional expressions, the total length of the string is more than 79 bytes while %CVS2 is replaced with its values. In this case, the total length of replaced characters for all conditional expressions becomes as follows:

All of the replacement string for %CVS1 is included, but the end of the replacement string for %CVS2 is omitted.

As for %CVS3, the total character string is 79 or more bytes before the replacement of %CVS3, so the replacement of %CVS3 is performed according to the following rule: if zero or a value greater than the number of conditional expressions is specified, the measurement value of the first field is displayed. This means that %CVS3 is replaced with %CVS1, which is the measurement value for the first field.

Therefore, the final replacement result is as follows:

#3: If the character string generated by replacing the variable %CVS contains the value |, the characters following | will be omitted.

#4: Only a maximum of five digits can be specified for the value. If you specify six or more digits, only the first five digits are used and displayed in the alarm notification message.

#5: The following are notes on %CVS for #1 to #3:

When two or more of the same field are used in a condition expression, the value of the %CVS variable is aggregated as the value specified for the first field. As a result, the number specified for %CVS becomes the position that excludes the overlapping fields.

For example, when the condition expression is A and ( A and B ), the value for A is %CVS1, and the value for B is %CVS2.

Similarly, when the condition expression is A and ( B and A ), the value for A is %CVS1, and the value for B is %CVS2.

The following are condition expression examples:

Line 1: Free Mbytes <>"0"

Line 2: AND (Free Mbytes % = "10.000"

Line 3: AND (Free Mbytes % <= "20.000"

Line 4: AND ID = "*"))

In this case, the following result is output:

For %CVS1, the evaluation result of Free Mbytes in line 1

For %CVS2, the evaluation results of Free Mbytes % in lines 2 and 3

For %CVS3, the evaluation result of the ID in line 4

Note

If the length of the message text is more than 255 bytes after the values are substituted in for the variables, the Agent Collector or Remote Monitor Collector service outputs the KAVE00184-W message when the alarm is reported.

If this message is displayed, adjust the character string to be specified in the message text and the number of digits to be specified for %CVS so the message text length is no more than 255 bytes.

Alarm message preview

Displays the message you specified in Alarm message after its variable section is replaced with a string.

Monitor whether the value exists

Specifies that a given field is to be monitored for presence of a value and the alarm is to be issued when it is detected that no value exists in the field. With this function, an alarm can be issued when a critical program is not running (whether or not the processing is being executed can be monitored). This option can be used for all products. The default is that this option is not selected.

This option is can be selected only when a new alarm is being created.

(b) Advanced settings

Enable alarm

Specifies that the alarm is to become active immediately after it has been created. The default is that this box is selected.

Alarm notification

Allows you to specify the content of the alarm to be reported.

Notify when the state changed

If selected, specifies that the alarm is to be reported when the alarm or instance status changes.

By default, this item is selected.

Notification target

Specifies the target of alarm notification.

State changes for the alarm

Specifies, when selected, that the alarm is to be reported when the alarm status changes.

For single-instance records:

The status of the instance is treated as the alarm status.

For multi-instance records:

The status of the instance in the worst status is treated as the alarm status.

By default, this item is selected.

Evaluate all data

Select this item to evaluate all collected data for multi-instance records.

If this item is not selected, the alarm is reported only for the data that was evaluated first in the record in the worst status. By default, this item is selected.

State changes for each record instance

Specifies, when selected, that the alarm is to be reported when the status of an instance changes.

For multi-instance records, the alarm is reported every time the status of an instance changes. By default, this item is not selected.

This item is active only if all the following conditions are met:

The connected PFM - Manager is version 10-10 or later.

Monitor whether the value exists is not selected.

The abnormal condition and warning condition of the alarm consist of a single type of record, or these conditions have not been specified.

Always notify

Specifies, when selected, that the alarm is always to be reported when a conditional expression is satisfied.

If this item is selected, whether any conditional expression is satisfied is monitored each time the alarm is evaluated. If a conditional expression specified as Abnormal condition or Warning condition is satisfied, the alarm is issued. If no conditional expressions are satisfied (that is, the conditions are all normal), the alarm is not issued.

If this item is selected, changes to the agent's status are not monitored, so that no agent events are issued.

By default, this item is not selected.

Evaluate all data

Select this item to evaluate all collected data for multi-instance records.

When this box is not selected, the alarm is issued only for the first data evaluated by the record that has the worst status. The default is that this box is not selected.

For the differences in alarm evaluations due to the combination of alarm conditions, see the section that explains the differences in alarm evaluations due to the combination of alarm conditions in the Job Management Partner 1/Performance Management User's Guide.

Monitoring time range

Specifies the time range during which the collected data is to be monitored.

If State changes for each record instance is selected, the value set for Damping is cleared and an alarm event (Alarm Expired) is issued once when the time exceeds the range specified for Monitoring time range. When the time returns to the range specified for Monitoring time range again, evaluation starts again in the same way as the initial evaluation when the alarm was bound.

If State changes for each record instance is not selected, even if the time exceeds the specified range, the value of Damping is not cleared, and the alarm event (Alarm Expired) is not issued.

Always monitor

Specifies that alarms are always to be monitored 24 hours a day.

The default is that this box is selected.

Start

Specify an alarm monitoring start time.

This option can be specified when Always monitor is not selected.

The default is that the current time is displayed.

The permitted value range is 00:00 to 23:59.

End

Specifies an alarm monitoring end time.

This option can be specified when Always monitor is not selected.

The default is that the current time is displayed.

The permitted value range is 00:00 to 23:59.

Damping

Specifies, in relation to alarm evaluation, the number of times alarms are to be evaluated and the number of times the threshold is to be exceeded before the alarm is issued.

Evaluation is skipped if no instance can be collected and no record can be generated, even though collection was executed at the collection time. In such a case, the value set for Damping is stored. The value of Damping is cleared when one of the following occurs:

The alarm definition is changed (by unbinding or by a definition change).

The agent stops.

The time exceeds the range specified for Monitoring time range.

The value of Damping is cleared when the time exceeds the range specified for Monitoring time range only if State changes for each record instance is selected. In other monitoring methods, the value is not cleared when the time exceeds the range. For this reason, the timing to issue an alarm event after the time returns to the range specified for Monitoring time range again might be different between the monitoring method where an alarm is reported when the status of each record instance changes and other monitoring methods.

Report alarm when the following damping condition is reached.

Specifies that the alarm is to be issued when alarms occur at least as often as the specified occurrence frequency.

The default is that this box is not selected.

occurrence(s) during and interval(s)

Specify the number of times alarms are to be evaluated and the number of times the threshold is to be exceeded before the alarm is issued. Use the and buttons to set in occurrence(s) during the number of times the threshold is to be exceeded and in interval(s) the number of times alarms are to be evaluated. These items can be specified only when Report alarm when the following damping condition is reached. is selected. The default is 1 for both fields.

The permitted values are an integer in the range from 1 to 32,767.

Depending on whether or not Always notify is selected, an alarm is issued as follows:

When Always notify is not selected

Alarms are evaluated according to their occurrence frequency and the alarm is issued whenever the condition is satisfied. Because the result of the evaluated occurrence frequency is in the alarm state, the notified alarm state and the data threshold may differ.

When Always notify is selected

Data in the warning or abnormal state is reported in an alarm when the occurrence frequency meets the warning or abnormal conditions. The state according to occurrence frequency is not reflected in the alarm status. Also, if occurrence(s) during and interval(s) are set with the same value, the timing of alarm notification changes.

The following table shows the occurrence frequency and alarm notification timing:

Occurrence frequency

Alarm notification timing

n/m

If during interval m the threshold is exceeded n times, the alarm is issued. Thereafter, the alarm is issued every mth time alarms are evaluated and the threshold is exceeded n times.

n/n#

The alarm is issued every n times that the threshold is exceeded.

#: If Always notify is selected and the threshold is exceeded at the first collection since collection of data began, the alarm will be issued regardless of the interval.

The following table shows the differences between the specifications of Always notify and Evaluate all data when the occurrence frequency is specified.

Always notify

Evaluate all data

Alarm evaluation (notification)

N

N

Specifies whether or not the alarm status is to be changed when the threshold is exceeded the specified number of times while evaluating alarms for the specified number of times.

The alarm is issued only when the alarm status has changed from the previously notified alarm status.

The alarm status of the data satisfying the highest severity condition of the data collected when an alarm was issued is reported in an alarm.

Note

Because the alarm status is the status of the result of the evaluated occurrence frequency, the alarm status and the threshold of the reported data may differ.

N

Y

Specifies whether or not the alarm status is to be changed when the threshold is exceeded the specified number of times while evaluating alarms for the specified number of times.

The alarm is issued only when the alarm status has changed from the previously notified alarm status.

If the alarm status is Warning or Abnormal, the alarm status of all data satisfying the alarm condition at the time the alarm is issued is reported.

Note

Because the alarm status is the status of the result of the evaluated occurrence frequency, the alarm status and the threshold of the reported data may differ.

Y

N

Specifies whether or not the alarm is to be issued when the threshold is exceeded the specified number of times while evaluating alarms for the specified number of times. You can use this combination of settings to suppress the occurrence frequency of alarms.

The data satisfying the highest severity condition of the data collected when an alarm was issued is reported in the alarm.

Y

Y

Specifies whether or not the alarm is to be issued when the threshold is exceeded the specified number of times while evaluating alarms for the specified number of times. You can use this combination of settings to suppress the occurrence frequency of alarms.

All data satisfying the Warning or Abnormal conditions at the time an alarm is issued is reported in the alarm.

Legend:

Y: Selected

N: Not selected

If State changes for each record instance is selected, the data in the warning or abnormal status is reported when an instance satisfies the warning or abnormal condition set under Damping. Also, if the same value is specified as the number of times the threshold is exceeded and the number of intervals for occurrence(s) during and interval(s), the timing of alarm report changes.

Because the instances that are collected might vary depending on the environment, a record might not contain the same instance values that were collected the previous time. For example, in process monitoring, the instances that are collected change if the application definition changes. Then, data is not collected because no instance values are displayed for the record. Status monitoring continues, assuming that uncollected instance values are within the normal range. Note that, if you want to be informed of an abnormality when the data of a specific instance is not displayed, select Monitor whether the value exists. The following table describes the values of Damping and the timing of the alarm report:

Damping#

Timing of the alarm report

n/m

Assume that the value of damping is n/m (n <= m). An alarm event is issued by changing the instance status to the abnormal (or warning) status when the abnormal (or warning) status has occurred n times during the past m times of collection, including the current collection.

Although the data on the past m times of collection cannot be obtained until the number of times of collection reaches m, an alarm event is issued when the number of abnormal status or warning status occurrences reaches n.

n/n

Same as above.

#: The value of Damping is counted as follows:

- If the instance value is within the abnormal range, the instance is assumed to be in both the abnormal status and warning status, the occurrence of an abnormal status is counted also as an occurrence of a warning status.

- If the instance value is within the warning range, the occurrence of a warning status is counted only as an occurrence of a warning status.

- If the instance value is within the normal range, nothing is counted.

(2) New Alarm > Alarm Conditions window or Edit > Alarm Conditions window

The New Alarm > Alarm Conditions window and the Edit > Alarm Conditions window are used to set an alarm conditional expression. The settings differ depending on whether Monitor whether the value exists is selected in the New Alarm > Main Information window or the Edit > Main Information window.

The following describes the items displayed in the window for each case.

(a) When "Monitor whether the value exists" is selected

The window is used to set the value whose existence is to be monitored.

The following figure shows the New Alarm > Alarm Conditions window when Monitor whether the value exists is selected.

Figure 1‒108: New Alarm > Alarm Conditions window (when monitoring whether the value exists)

The following describes the displayed items:

Cancel button

Cancels creation of a new alarm or the editing of an alarm.

< Back button

Returns to the New Alarm > Main Information or Edit > Main Information window.

Although you return to the previous window, the settings you specified in this window are not discarded.

Next > button

Switches to the New Alarm > Action or Edit > Action window.

Finish button

Applies the settings, and ends creation of a new alarm or the editing of an alarm.

Definition of conditional expression

Record

From the pull-down menu, select the target record. In the pull-down menu, only multi-instance records are displayed.

Description button (to the right of Record)

Displays the Description of Record and Fields window, which describes the record selected in Record and its fields, as a separate window.

Search Fields button

Displays the New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window. This button is not displayed if the data model description file is not stored. If the data model description file has not been stored, see the setup procedure for PFM - Web Console for registering PFM - Agent or PFM - RM. For details, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

For details about the Search Fields window, see 1.7.4(3) New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window.

Field

From the pull-down menu, select the target field.

This item is enabled when a selection is made in Record.

The default is the first field in the record selected in Record.

Description button (on the right of Field)

Displays the Description of Record and Fields window, which describes the field selected in Field and its records, as a separate window.

Value

Specify the value whose existence you want to monitor by using an integer value, a decimal value, or a character string consisting of no more than 127 bytes of two-byte or single-byte characters. This value is case sensitive. However, you cannot use the following characters: ( ) [ ] < > = ". To specify these characters, use a wildcard character to specify the conditional expression.

If a program name is specified, the extension is not needed.

The values that can be specified depend on the field. For details about the values that can be specified, see the chapter that explains records (list of fields for each record) in the PFM - Agent or PFM - RM manuals.

(b) When "Monitor whether the value exists" is not selected

This window is used to set conditional expressions for the alarm to be monitored.

The following figure shows the New Alarm > Alarm Conditions window when Monitor whether the value exists is not selected.

Figure 1‒109: New Alarm > Alarm Conditions window (when not monitoring whether the value exists)

The following describes the displayed items:

Cancel button

Discards the settings and cancels alarm creation or editing.

< Back button

Returns to the New Alarm > Main Information window or the Edit > Main Information window.

The settings specified in this window remain intact when you return to the previous window.

Next > button

Displays the New Alarm > Action window or the Edit > Action window.

Finish button

Applies the settings and finishes alarm creation or editing.

Record

From the pull-down menu, select the target record for which the conditional expressions are specified.

Description button (to the right of Record)

Displays the Description of Record and Fields window, which describes the record selected in Record and its fields, as a separate window.

Search Fields button

Displays the New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window. This button is not displayed if the data model description file is not stored. If the data model description file has not been stored, see the setup procedure for PFM - Web Console for registering PFM - Agent or PFM - RM. For details, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

For details about the Search Fields window, see 1.7.4(3) New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window.

Field

From the pull-down menu, select the target field for which the conditional expressions are specified. This item is enabled when a selection is made in Record.

The fields whose data type is time_t, timeval, or utime are not displayed in the pull-down menu because they cannot be specified for the alarm conditions.

The default is the first field in the record selected in Record.

Description button (to the right of Field)

Displays the Description of Record and Fields window, which describes the fields selected in Field and the record to which the fields belong, as a separate window.

Condition

From the pull-down menu, select an operator you want to use for specifying the conditional expression.

This item is enabled when a selection is made in Record.

The following table lists and describes the operands that can be selected:

Operand

Description

=

The value in Field is equal to the value in Value.

<

The value in Field is smaller than the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

<=

The value in Field is smaller than or equal to the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

>

The value in Field is greater than the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

>=

The value in Field is greater than or equal to the value in Value. For a character string field, comparisons are made in ascending order of the ASCII codes.

<>

The value in Field is any value other than the value in Value.

The default is =.

Abnormal value

Specify the threshold value that is to be used as the reference for determining an Abnormal-condition alarm during alarm evaluation by using an integer value, a decimal value, or a character string consisting of no more than 750 bytes of single-byte or two-byte characters. However, you cannot use the following characters: ( ) [ ] < > = ". To specify these characters, use a wildcard character to specify the conditional expression. This is the value in the abnormal conditional expression. The values that can be specified depend on the field. For details about the values that can be specified, see the chapter that explains records (list of fields for each record) in the PFM - Agent or PFM - RM manuals.

You can specify the wildcard character in a character string. For example, if you specify item-name="*AAA*", monitoring would be of all character strings that contain internally AAA.

Warning value

Specify the threshold value that is to be used as the reference for determining a Warning-condition alarm during alarm evaluation by using an integer value, a decimal value, or a character string consisting of no more than 750 bytes of single-byte or two-byte characters. However, you cannot use the following characters: ( ) [ ] < > = ". To specify these characters, use a wildcard character to specify the conditional expression. This is the value in the warning conditional expression. The values that can be specified depend on the field. For details about the values that can be specified, see the chapter that explains records (list of fields for each record) in the PFM - Agent or PFM - RM manuals.

You can specify the wildcard character in a character string. For example, if you specify item-name="*AAA*", monitoring would be for all character strings that contain internally AAA.

Add button

Adds the conditional expression specified in Record, Field, Condition, and Abnormal value and Warning value to Abnormal condition and Warning condition.

Both Abnormal value and Warning value must be specified for the specified conditional expression to be added. If a conditional expression already exists in Abnormal condition and Warning condition, the conditional expressions are linked with AND.

Update button

If an existing conditional expression was edited, clicking this button updates the conditional expression selected in Abnormal condition or Warning condition with the conditional expression set in Record, Field, Condition, and Abnormal value and Warning value.

Both Abnormal value and Warning value must be specified for the updating to take place.

Abnormal condition

Lists the abnormal conditional expressions that have been set. To add conditional expressions here, set Record, Field, Condition, Abnormal value, and Warning value and then click the Add button. To change a conditional expression, select it and then click the Update button.

If you select an existing condition expression and then click the Add button, the selected condition expression and the added condition expression are enclosed in parentheses ( ( and ) ).

A maximum of five abnormal conditional expressions with a maximum length of 749 bytes each can be stored.

Warning condition

Lists the warning conditional expressions that have been set. To add conditional expressions here, set Record, Field, Condition, Abnormal value, and Warning value and then click the Add button. To change a conditional expression, select it and then click the Update button.

If you select an existing condition expression and then click the Add button, the selected condition expression and the added condition expression are enclosed in parentheses ( ( and ) ).

A maximum of five warning conditional expressions can be stored if the number of specified characters for each warning conditional expression is no more than 749 bytes.

Edit button

Displays the conditional expression selected in Abnormal condition and Warning condition in Record, Field, Condition, Abnormal value, and Warning value for editing. You cannot select multiple conditional expressions at the same time. This button is enabled only when at least one conditional expression is set in Abnormal condition and Warning condition.

Delete button

Deletes selected conditional expressions from Abnormal condition and Warning condition.

Delete All button

Deletes all conditional expressions from Abnormal condition and Warning condition.

Note:

When an alarm condition expression contains <, <=, >=, or >, whether the warning conditions are satisfied is determined during the first stage of alarm evaluation.

If the warning conditions are not satisfied, alarm evaluation terminates at that point.

If the warning conditions are satisfied, whether the abnormal conditions are satisfied is determined next. If the abnormal conditions are not satisfied, a warning alarm is issued. If the abnormal conditions are satisfied, an abnormal alarm is issued.

Accordingly, if you want to generate an alarm that contains <, <=, >=, or > in the alarm condition expression, specify the abnormal condition so that it is within a more abnormal range as a system than the warning condition specification (the warning condition is contained within the abnormal condition).

The following are specification examples:

Example 1:

When the value of CPU% (CPU usage) is greater than 0 and less than 100

(A larger value is the abnormal value for a system.)

Alarm condition expression that is evaluated correctly

Abnormal > 90

Warning > 80

Alarm condition expression that is not evaluated correctly

Abnormal > 50

Warning > 80

Note: If you want to issue an alarm only for an abnormal status, use the same condition for abnormal and warning:

Abnormal > 90

Warning > 90

Example 2:

When the value of % Free Space (available disk space) is greater than 0 and less than 100

(A smaller value is the abnormal value for a system.)

Alarm condition expression that is evaluated correctly

Abnormal < 10

Warning < 30

Alarm condition expression that is not evaluated correctly

Abnormal < 60

Warning < 30

Note: If you want to issue an alarm only for an abnormal status, use the same condition for abnormal and warning:

Abnormal < 10

Warning < 10

(3) New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window

In this window, you can search fields. You can search a maximum of 50 fields by default. The fields found in the search result can be set in the Field: pull-down menu in the New Alarm > Alarm Conditions or the Edit > Alarm Conditions window, which was the previous window.

You can set the maximum limit of fields to be searched, in searchLimit of the initialization file (config.xml). For details about the initialization file (config.xml), see E. Initialization File (config.xml).

Note that if you select a record here that is different from the one selected in the previous New Alarm > Alarm Conditions or Edit > Alarm Conditions window, from which this window is opened, the fields selected in that previous window will be cleared.

The following figure shows the New Alarm > Alarm Conditions > Search Fields window.

Figure 1‒110: New Alarm > Alarm Conditions > Search Fields window

The following describes the displayed items:

Cancel button

Returns to the New Alarm > Alarm Conditions or Edit > Alarm Conditions window.

Keywords to find

Enter a maximum of 64 characters for the search keywords (including spaces as delimiters). Observe the following precautions related to a search:

To perform a multiple keywords search by using AND, delimit keywords by using a single-byte or two-byte space.

An OR search cannot be performed.

Wildcard characters cannot be used.

A keyword search that consists only of spaces cannot be specified.

Spaces entered at the beginning and ending of a keyword are excluded.

If the search keyword includes spaces, the search will not be performed as intended.

The search is not case sensitive.

In the search keyword, a two-byte character and a single-byte character are recognized as different characters.

A search keyword that includes a line feed code cannot be entered.

After entering the search keyword, click the Search button. The search results will be displayed.

Search results are displayed, depending on the selection in the Records to search pull-down menu, in the following different windows:

If --All records-- is selected in Records to search

The search results are displayed in the "Search results: number-of-records record(s)" window.

If a record name is selected in Records to search

The search results are displayed in the "Search results: List of number-of-fields field(s) found in record record-name" window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records to search. By default, the records selected in Record: in the New Alarm > Alarm Conditions or the Edit > Alarm Conditions window are displayed.

In the pull-down menu, the following items are displayed:

--All records--

Select this item to search all records.

List of record names of the selected agent

Displays a list of record names of the selected agent in alphabetical order.

(a) Search results: number-of-records record(s) window

This window displays the number of fields found by a search for each record when --All records-- was selected in Records to search in the New Alarm > Alarm Conditions > Search Fields or the Edit > Alarm Conditions > Search Fields window. In the search results, the record names are displayed in alphabetical order.

Cancel button

Returns to the New Alarm > Alarm Conditions or Edit > Alarm Conditions window.

Keywords to find

Enter search keywords. For details, see 1.7.4(3) New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records you want to search. For details, see 1.7.4(3) New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window.

Record name

A record name is followed by the following information:

Number of fields that correspond to the search result

Description of the record

If there is no description, (No explanation provided) is displayed.

Instance type

(This record is a single-instance record.) or (This record is a multi-instance record.) is displayed.

Clicking the menu of a record name lists the corresponding fields of the selected record in the "Search results: List of number-of-fields field(s) found in record record-name" window.

(b) Search results: List of number-of-fields field(s) found in record record-name window

A list of fields is displayed as a search result.

Keywords to find

Enter search keywords. For details, see 1.7.4(3) New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window.

Search button

Performs a search.

Records to search

From the pull-down menu, select the records you want to search. For details, see 1.7.4(3) New Alarm > Alarm Conditions > Search Fields or Edit > Alarm Conditions > Search Fields window.

Go to Record List button

Returns to the Search Results: number-of-records record(s) window. This button is displayed only when you have switched to this window from the Search Results: number-of-records record(s) window.

OK button

Returns to the New Alarm > Alarm Conditions or Edit > Alarm Conditions window. The selected field is in the status selected in the Field pull-down menu.

Radio buttons

Select a field. You cannot select multiple fields.

Selecting this item and clicking the OK button returns to the New Alarm > Alarm Conditions or Edit > Alarm Conditions window, and Field is updated to the selected field.

Note that when you return to the "Search results: number-of-records record(s)" window by clicking the Go to Record List button, the selection of the radio button is cleared.

Field name

Displays field names in alphabetical order. Bold characters indicate the characters that match with the search keyword.

Format

Displays the attribute of the corresponding field by using the following icons:

: Numeric attribute

: String attribute

Description

Displays a description of the field. Bold characters indicate the characters that match with the search keyword.

(4) New Alarm > Action window or Edit > Action window

The New Alarm > Action window and the Edit > Action window are used to set information about the actions that are to be executed when an alarm's status changes and to set the report that is to be associated with the alarm.

The following figure shows the New Alarm > Action window.

Figure 1‒111: New Alarm > Action window

The following describes the items displayed in these windows:

Cancel button

Discards the settings and cancels alarm creation or editing.

< Back button

Returns to the New Alarm > Alarm Conditions window or the Edit > Alarm Conditions window. The settings specified in this window remain intact when you return to the previous window.

Next > button

Displays the New Alarm > Action Definitions window or the Edit > Action Definitions window.

This button is enabled when Email or Command is set as the action.

Finish button

Applies the settings and finishes alarm creation or editing.

This button is disabled when Email or Command is set as the action.

Actions to be executed

Sets the action to be executed for each status (abnormal, warning, and normal).

Email

Specifies that a notification email is to be sent as the action.

You must set for each status (abnormal, warning, and normal) whether or not this action is to be taken.

Abnormal

Select this box to send email notification when an abnormal alarm occurs.

Warning

Select this box to send email notification when a warning alarm occurs.

This box is disabled if Monitor whether the value exists is selected in General settings in the New Alarm > Main Information window or the Edit > Main Information window.

Normal

Select this box to send email notification when a normal alarm occurs.

This box is disabled if Always notify is selected in Advanced settings in the New Alarm > Main Information window or the Edit > Main Information window.

Note

The following settings must have been specified in advance in order for a notification email to be sent:

In the Services window, in the navigation frame, select the Action Handler service (service beginning with PH), choose the Properties method, then specify the following settings:

Email in Capabilities: Yes

SMTP Host in Mail: SMTP host name or IP address

SMTP Sender in Mail: Recipient's email address

Mail Subject in Mail: Subject of the email

Command

Specifies that a command is to be executed as the action.

You must set for each status (abnormal, warning, and normal) whether or not this action is to be taken.

Abnormal

Select this box to execute a command when an abnormal alarm occurs.

Warning

Select this box to execute a command when a warning alarm occurs.

This box is disabled if Monitor whether the value exists is selected in General settings in the New Alarm > Main Information window or the Edit > Main Information window.

Normal

Select this box to execute a command when a normal alarm occurs.

This box is disabled if Always notify is selected in Advanced settings in the New Alarm > Main Information window or the Edit > Main Information window.

Note

The following setting must have been specified in advance in order for a command to be executed:

In the Services window, in the navigation frame, select the Action Handler service (service beginning with PH), choose the Properties method, then specify the following setting:

Script in Capabilities: Yes

SNMP

Specifies that an SNMP trap is to be notified as the action.

You must set for each status (abnormal, warning, and normal) whether or not this action is to be taken.

Abnormal

Select this box to send an SNMP trap when an abnormal alarm occurs.

Warning

Select this box to send an SNMP trap when a warning alarm occurs. This box is disabled if Monitor whether the value exists is selected in General settings in the New Alarm > Main Information window or the Edit > Main Information window.

Normal

Select this box to send an SNMP trap when a normal alarm occurs. This box is disabled if Always notify is selected in Advanced settings in the New Alarm > Main Information window or the Edit > Main Information window.

Note:

If you want to report an SNMP trap, the following setting is required beforehand:

In the Services window, in the navigation frame, select the Trap Generator service (service beginning with PC), choose the Properties method, then specify the following setting:

Add a destination in Add or delete a trap destination: Host name or IP address of the SNMP trap destination

Reference note:

SNMP traps are issued from the server running PFM - Manager (Trap Generator service) that is to be logged on to.

Report to be displayed

Displays a report, which you select from the reports tree by clicking the Browse button. The report you select is displayed here and is set as the alarm-associated report.

Browse button

Enables selection of a report that is to be associated with the alarm; the selected report is displayed in Report to be displayed. Clicking this button displays the New Alarm > Action > Select a report window or the Edit > Action > Select a report window.

Delete button

Deletes the report name displayed in Report to be displayed.

This button is enabled when a report name is set in Report to be displayed.

(5) New Alarm > Action > Select a report window or Edit > Action > Select a report window

The New Alarm > Action > Select a report window and the Edit > Action > Select a report window are used to select a report to be associated with the alarm; the selected report is displayed in Report to be displayed in the New Alarm > Action window or the Edit > Action window.

The following figure shows the New Alarm > Action > Select a report window.

Figure 1‒112: New Alarm > Action > Select a report window

The following describes the items displayed in these windows:

Refresh

Refreshes the Reports tree displayed in the contents area. Refreshing the display does not change the selection status in the contents area.

Cancel button

Disregards the specified settings and returns to the New Alarm > Action window or the Edit > Action window.

Finish button

Applies the specified settings and returns to the New Alarm > Action window or the Edit > Action window.

Text box

Use this text box to filter reports by keywords. Specify a character string of 1 to 1,024 characters to filter the reports that will be displayed. To use multiple conditions for an AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters reports by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Contents area

Displays the reports tree. Select a report to be associated with the alarm

You can select only one report for an alarm.

(6) New Alarm > Action Definitions window or Edit > Action Definitions window

The New Alarm > Action Definitions window and the Edit > Action Definitions window are used to set details about an email or command that is set as an action.

The following figure shows the New Alarm > Action Definition window.

Figure 1‒113: New Alarm > Action Definition window

The following describes the items displayed in these windows:

Cancel button

Discards the settings, and cancels creation of a new alarm or the editing of an alarm.

< Back button

Returns to the New Alarm > Action or Edit > Action window.

Although you return to the previous window, the settings you specified in this window are not discarded.

Finish button

Applies the settings, and ends creation of a new alarm or the editing of an alarm.

If you set both Email notification and command execution in the New Alarm > Action or Edit > Action window, you cannot select this button without setting information in both Email settings and Command definition.

(a) Email Settings

Sets information needed for email notification. The settings in Email Settings are displayed only when email notification is set as an action in the New Alarm > Action window or the Edit > Action window.

Email address

Specify the email addresses of the parties to be notified by using no more than 127 bytes of alphanumeric characters.

If you specify multiple e-mail addresses, separate them with the comma (,).

Action handler

Text box

Use this text box to filter action handlers by keywords. Specify a character string of 1 to 1,024 characters to filter the action handlers that will be displayed. To use multiple conditions for an AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters action handlers by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Pull-down menu

From the pull-down menu, select the Action Handler service that sends an email. The Action Handler service name (service ID) that is displayed is the default.

If the Action Handler to be used is not included in the drop-down list, display the desired Action Handler's properties in the Services window, and in Capabilities set the property value for Email to Yes.

Variables

Displays variables that you can select to be set in the message text of the notification email. Select the desired variables from the displayed list, and then click the Add Variable button to add the selected variables to Email body as the message text for the email.

The following table lists and describes the variables that are displayed in Variables:

Item name

Variable name

Description

Date/Time

%SCT

Sets the system time at the host where the agent whose alarm was evaluated is running.

Agent name

%ANS

Sets the name of the agent to which the alarm table is bound.

Host name

%HNS

Sets the name of the host where the agent to which the alarm table is bound is running.

Status

%SCS

Sets the alarm condition that triggered output of the message.

Alarm name

%AIS

Sets the alarm name that was set in Alarm name in the New Alarm > Main Information window or the Edit > Main Information window.

Alarm table name

%ATS

Sets the alarm table name that was set in Alarm table name in the New Alarm > Main Information window or the Edit > Main Information window.

Message

%MTS#1

Sets the message text that was set in Message in the New Alarm > Main Information window or the Edit > Main Information window.

Product

%PTS

Sets the product name that was set in Product in the New Alarm > Main Information window or the Edit > Main Information window.

Measurement value

%CVS[n][.p]#2,#3,#4

Sets the measurement value that triggered the alarm issuance (that satisfied a conditional expression).

n#5

Specifies as an integer the position of the field when more than one conditional expression is specified in the New Alarm > Alarm Conditions window or the Edit > Alarm Conditions window. 1 is specified for the first field. If 0 or a value greater than the number of conditional expressions is specified, the measurement value of the first field is displayed.

p#5

For a field that is replaced with an integer or a decimal value

Specifies the number of decimal places to be displayed (rounding).

For a field whose measurement value is replaced with a string

Specifies the position of a string that is to be displayed from the strings whose measurement value can be delimited by a single-byte space. If you want to specify the position, specify 1 or a larger value. If you specify 0, the measurement value is displayed as is. If you specify a value greater than the number of strings that are delimited by the single-byte space, a 0-byte string replaces the variable.

#1: If the alarm status changes from Abnormal or Warning to Normal for an alarm definition that uses multiple instance records, the value stored in the %MTS variable will be as follows:

If the function for measurement value output at alarm recovery is enabled

The alarm message text of the instance that triggered the last issued abnormal or warning alarm is stored until the alarm status returns to normal.

If this function is disabled

Because the value that triggered issuance of the event cannot be determined, the value is blank.

For details about the function for measurement value output at alarm recovery, see the chapter that explains operation monitoring by using alarms in the Job Management Partner 1/Performance Management User's Guide.

#2: If the alarm status changes from Abnormal or Warning to Normal for an alarm definition that uses multiple instance records, the value stored in the %CVS variable will be as follows:

If the function for measurement value output at alarm recovery is enabled

The current measurement value of the instance that triggered the last issued abnormal or warning alarm is stored until the alarm status returns to normal.

If this function is disabled

Because the measurement value that satisfies the condition expression does not exist, the <OK> string is stored. Accordingly, if a value of two or more is specified for p in %CVSn.p, %CVS is replaced with a zero-byte string.

For details about the function for measurement value output at alarm recovery, see the chapter that explains operation monitoring by using alarms in the Job Management Partner 1/Performance Management User's Guide.

#3: The maximum length of the character string generated by replacing the variable %CVS is 79 bytes.

#4: If the character string generated by replacing the variable %CVS contains |, the strings following the | will be omitted.

#5: Only a maximum of five digits can be specified for the value. If you specify six or more digits, only the first five digits are used and displayed in the message of the alarm notification.

Add Variable button

Adds the variables selected from Variables to Email body.

Email body

Specify the reply email message text by using no more than 1,000 bytes of single-byte or two-byte alphanumeric characters. The following text is already set as a standard in Email body:

Date/Time:%SCT
Host name:%HNS

Product:%PTS
Agent name:%ANS

Alarm name:%AIS(%ATS)
Status:%SCS

Message:%MTS

Note:

If the length of the message text that replaces the variable is more than 1,000 bytes, the Agent Collector or Remote Monitor Collector service outputs the KAVE00184-W message when the alarm is reported.

If this message appears, adjust the character string to be specified in the message string and the number of digits specified for %CVS so the message text length is no more than 1,000 bytes.

(b) Command Definition

Sets information needed for command execution. The settings in Command Definition are displayed only when command execution is set as an action in the New Alarm > Action window or the Edit > Action window.

Command name

Specify the name of the command (script) to be executed by using no more than 511 bytes of alphanumeric characters. For commands (scripts) other than the ones in the following directories, specify the absolute path or the relative path of the current directory of the service:

Action Handler service installation directory

Path set in the PATH environment variable

To specify a relative path, use the Services window to check the current directory of the Action Handler service.

Reference note:

In the Command name field, you can specify a command name that includes arguments. If the command path or command name to be specified includes at least one single-byte space character, enclose the command path or command name in double quotation marks (" ").

JP1 Event Settings button

Specifies that an event issuance command is to be specified.

Clicking this button displays the New Alarm > Action Definitions > JP1 Event Settings window or the Edit > Action Definitions > JP1 Event Settings window.

Action handler

Text box

Use this text box to filter action handlers by keywords. Specify a character string of 1 to 1,024 characters to filter the action handlers that will be displayed. To use multiple conditions for an AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters action handlers by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Pull-down menu

From the pull-down menu, select the Action Handler service that executes commands (scripts). LOCAL is displayed as the default, and it represents the host at which the agent to which the alarm table is bound is running.

To issue JP1 events for Performance Management monitoring by JP1/IM integrated scope, select the Action Handler service that is installed on the same host as the PFM - Manager. To issue JP1 events, note that JP1/Base is required on the same host as the Action Handler that issues the events. For details about Performance Management monitoring by JP1/IM, see the chapter that explains operation monitoring linking with the integrated management product (JP1/IM) in the Job Management Partner 1/Performance Management User's Guide.

If the service name (service ID) of the Action Handler to be used is not included in the drop-down list, use the Services window to display the properties of the desired Action Handler service, and then set Yes in Script under Capabilities.

Variables

Displays the variables that you can select to be set as command arguments.

Select desired variables from the displayed list of variables and then click the Add Variable button to add the variables to Command arguments as the command arguments.

The variables that can be set are the same ones that are described in Variables under Email Settings.

Add Variable

Adds the variables selected from Variables to Command arguments.

Command arguments

Specify no more than 2,047 bytes of single-byte alphanumeric characters or two-byte characters for a parameter to be passed to the command (script) that is to be executed.

To issue JP1 events to a logical host in a logical host environment, add the -r logical-host-name option. If the -r option is omitted, JP1 events will be registered in the physical host.

Note:

If the length of the command argument that replaces the variable is more than 2,047 bytes, the Agent Collector or Remote Monitor Collector service outputs the KAVE00184-W message when the alarm is reported.

If this message appears, adjust the character string to be specified in the command argument and the number of digits specified for %CVS so the command argument length is no more than 2,047 bytes.

(7) New Alarm > Action Definitions > JP1 Event Settings window or Edit > Action Definitions > JP1 Event Settings window

The New Alarm > Action Definitions > JP1 Event Settings window and the Edit > Action Definitions > JP1 Event Settings window are used to specify event issuance commands. Clicking the OK button in this window sets the jpcimevt command and parameters for issuing a UP1 event in the New Alarm > Action Definitions window or the Edit > Action Definitions window. Clicking also sets the action-executing host in the logged-in PFM - Manager. For details, see the description of the jpcimevt command in 2. Commands.

To execute an action at a host other than PFM - Manager, specify settings in this window and then change Action handler in Command Definition.

When you link to JP1/IM to display the reports of Performance Management, do not delete or change the variables and values that are automatically set in Command arguments in Command Definition.

If you change a report associated with an alarm, reset the command in this window.

The following figure shows the New Alarm > Action Definitions > JP1 Event Settings window.

Figure 1‒114: New Alarm > Action Definitions > JP1 Event Settings window

The following describes the displayed items:

OK button

Applies the settings and then returns to the New Alarm > Action Definitions window or the Edit > Action Definitions window.

Cancel button

Discards the settings and then returns to the New Alarm > Action Definitions window or the Edit > Action Definitions window.

Event ID

Specify an event ID, as a hexadecimal number in the range from 0 to 1fff or 7fff8000 to 7fffffff.

This event ID is set in Command arguments under Command Definition in the New Alarm > Action Definitions window or the Edit > Action Definitions window.

Message

Specify the event message text by using 1 to 1,023 bytes of single-byte or two-byte characters. However, if either of the following cases applies, specify 0 to 128 bytes of single-byte or two-byte characters.

When either PFM - Manager or PFM - Web Console is version 09-00 or earlier

When you specify a version 09-00 or earlier PFM - Base host as the action execution destination

You can also set variables.

This character string is set in Command arguments under Command Definition in the New Alarm > Action Definitions window or the Edit > Action Definitions window.

The default is %MTS.

For details about the variables that can be set, see 1.7.4(6) New Alarm > Action Definitions window or Edit > Action Definitions window.

Note:

If the length of a message text after replacement of the variable with a value exceeds 1,023 bytes, the KAVE05418-W message is output when the action is executed, and the message text is truncated to 1,023 bytes or less. If this message is output, adjust the number of characters specified for the message or the number of digits specified for %CVS so that it does not exceed 1,023 bytes.

Note the following when the host specified as the location for the execution of an action uses PFM - Base version 09-00 or earlier: If the length of the message text after replacement of the variable with a value exceeds 128 bytes, the KAVE05223-E message is output when the action is executed, and the event message text is truncated to 128 bytes or less. If this message is output, adjust the number of characters specified for the message or the number of digits specified for %CVS so that it does not exceed 128 bytes.

Message preview

Displays the text specified in Message after replacement of the variable with a string.

Convert the alarm level to the severity level

Select to specify that the alarm status is to be converted to JP1's corresponding event severity level.

This check box is selected as a default.

The following table shows each alarm status and the corresponding JP1 event severity level:

Alarm status

Description

JP1 event severity level

"OK"

The alarm status is normal (green)

"Information"

"WARNING"

The alarm status is warning (yellow)

"Warning"

"EXCEPTION"

The alarm status is abnormal (red)

"Error"

1.7.5 Properties window

The Service Properties window displays the properties (definition) of a selected alarm. To display this window, in the Alarms window, from the method frame, choose Properties.

The following figure shows the Properties window.

Figure 1‒115: Properties window

If you click the link displayed at the top of the window, you can jump to the area where the applicable information is displayed. For details about the display items in each area, see 1.7.4 Windows for creating new alarm definitions and editing existing alarm definitions.

The following describes the displayed items:

Close

Closes the Properties window.

Main Information

Displays the General settings and Advanced settings that were set in the New Alarm > Main Information window or the Edit > Main Information window.

Alarm Conditions

Displays the Alarm Conditions settings that were set in the New Alarm > Alarm Conditions window or the Edit > Alarm Conditions window.

Actions

Displays the Actions to be executed and Report to be displayed settings that were set in the New Alarm > Action window or the Edit > Action window.

Action Definitions

Displays the Email Settings and Command Definition settings that were set in the New Alarm > Action Definitions window or the Edit > Action Definitions window.

1.7.6 Copy > Input Name [Alarm Table] or Copy > Input Name [Alarm Table] window

The Copy window is used to copy an alarm table or alarm. To display this window, in the Alarms window, in the method frame, choose Copy.

The following figure shows the Copy > Input Name [Alarm Table] window.

Figure 1‒116: Copy window

The following describes the displayed items:

OK button

Executes copying of the alarm table or alarm. If an alarm table or alarm with the same name already exists, an error results.

Cancel button

Cancels the operation and clears the information frame.

Source alarm table name or Source alarm name

Displays the source alarm table name or alarm name.

New alarm table name or New alarm name

Specify a new name for the alarm table or alarm.

For an alarm table name

Specify the alarm table name by using no more than 64 bytes of alphanumeric characters, the space, and the symbols % - ( ) _ . / @ [ ]. This name cannot begin with PFM (regardless of case). An alarm table cannot be copied to a different alarm folder.

For an alarm name

Specify the alarm name by using no more than 20 bytes of two-byte characters, single-byte alphanumeric characters, the single-byte symbols % - ( ) _ . / @ [ ], and spaces. An alarm cannot be copied to a different alarm table.

1.7.7 Active Setting window

The Active Setting window is used to specify whether defined alarms are to be enabled or disabled. To display this window, in the Alarms window, from the method frame, choose the Activate method.

The following figure shows the Activate Setting window.

Figure 1‒117: Active Setting window

The following describes the displayed items:

OK button

Saves the specified settings.

Cancel button

Cancels the operation and clears the information frame.

Text box

Use this text box to filter alarms by keywords. Specify a character string of 1 to 1,024 characters to filter the alarms that will be displayed. To use multiple conditions for an AND or OR search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters alarms by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

AND

Select this option button to perform an AND search.

OR

Select this option button to perform an OR search.

Select All button

Selects all displayed Activate check boxes.

UnSelect All button

Clears all displayed Activate check boxes.

Alarm name

Displays the alarm names defined in the selected alarm table. If an alarm has been selected, all alarm names defined in the same hierarchy are displayed.

Activate

When selected, specifies that that alarm definition is to be enabled.

To disable an alarm definition, clear its check box.

When this check box is selected for an alarm, agent monitoring begins in accordance with the defined settings.

1.7.8 Show Bound Agents window

The Show Bound Agents window displays the monitoring agents that are bound to (associated with) the selected alarm table. To display this window, in the Alarms window, from the method frame, choose the Show Bound Agents method.

The following figure shows the Show Bound Agents window.

Figure 1‒118: Show Bound Agents window

The following describes the displayed items:

Refresh

Updates the information displayed in the information frame to the latest status.

Contents area

Lists the monitoring agents that are bound to (associated with) the selected alarm table. The format of each line in the list is an icon, a service ID, and a data model version. Note that the icon is different for PFM - Agent and PFM - RM. For details about the service ID, see the section that explains the naming rules for the services in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

1.8 Services window

The Services window is used to manage the programs of the Performance Management products. It enables you to check service status, display and edit properties, and stop services. To display this window, in the navigation frame of any PFM - Web Console window, choose the Services tab.

Only a login user with the administrator user permission can display this window.

The following figure shows the Services window.

Figure 1‒119: Services window

The following describes the displayed items:

Menu bar frame

Displays a menu that is common to all windows.

For details, see the description of the menu bar frame in 1.3 Main window.

Navigation frame

Displays the services of the Performance Management system hierarchically.

Except for the following items, the display items are the same as the items in the navigation frame of the Main window. For details, see 1.3 Main window.

Display separately by business group

This item is displayed when the business group access control functionality is enabled. If you select this item, service trees are displayed separately by business group. By default, this item is cleared.

Text box

Use this text box to filter services by keywords. Specify a character string of 1 to 1,024 characters to filter the services that will be displayed. To use multiple conditions for an AND search, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters services by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

Services tree

When the business group access control functionality is enabled, and Display separately by business group is selected, the business group becomes the root directory. In all other cases, System is the root directory.

The root is System. On the second level of the hierarchy, the Machines or the PFM-Manager folder is displayed; these indicate the same information but in different units.

When the Machines folder is displayed at the second level of the hierarchy

The names of the hosts on which the Performance Management services are installed are displayed on the third level of the hierarchy and each machine's services are displayed on the fourth level. Service IDs are displayed for the service names.

When the PFM-Manager folder is displayed at the second level of the hierarchy

The PFM - Manager services are displayed on the third level of the hierarchy.

Service IDs are displayed for the service names.

Icons:

An icon is displayed to the left of each component in the services tree. For details about icons, see Table 1-9 Configuration component icons and their meaning.

These icons have the following meanings:

: Indicates the root.

: Indicates a service folder.

The icons representing services differ depending on the service.

Method frame

Displays the operations that can be executed on each service. The operations applicable to a service are displayed only when that service is selected in the navigation frame.

Properties

Displays the properties of the selected service. Choosing this item displays the Service Properties window.

Service status

Displays the status of the selected service.

Choosing this item displays the Service status window.

Stop service

Stops the selected service.

Choosing this item displays a message box for confirming your intention to stop the service. If abnormal termination occurs when you click the OK button in this message, another message box is displayed asking whether or not forced termination is to be executed.

Distribute Property

Distributes the value of the selected property to a destination service.

Selecting this item switches to the Distribute Property > Select Service window.

Information frame

Displays the results of the operation selected in the method frame.

1.8.1 Transitions from the Services window

The following shows the window transitions from the Services window:

Figure 1‒120: Window transitions from the Services window

1.8.2 Service Properties window

The Service Properties window displays the properties of the selected service. In this window, you can change some of the displayed values. To display the window, in the Services window, in the method frame, choose Properties.

The following figure shows the Service Properties window.

Figure 1‒121: Service Properties window

The following describes the displayed items:

Contents area

Displays hierarchically the properties of the service selected in the navigation frame of the Services window.

When you select a node, the setting appears in the property list area.

Finish button

After making changes to the property settings, use this button to apply the changes. The information displayed in the information frame is cleared.

Cancel button

Discards the settings.

Apply button

After making changes to the property settings, use this button to apply the changes. The information displayed in the information frame is updated to the latest status.

Note that if you have not made any changes to the property settings, this button is not available.

Tip

When you click the Apply button, the properties are displayed again after the changes are applied, and information displayed in the contents area remains. Accordingly, it is easy to edit those properties that require changes to be registered before they are actually used, for example, properties whose number of nodes increases or decreases dynamically when properties are added or deleted.

Area for displaying the properties list

Displays the properties of the nodes selected in the contents area.

The property settings that can be changed depend on the selected node. For details about properties that are displayed, see 1.8.2(1) Information displayed in the properties list.

Note that changes made to properties are retained even when a new node is selected in the contents area. This makes batch operation possible when the Finish or Apply button is clicked.

The following are the display items for properties:

Name

Displays the item names of properties.

Value

Displays OS system information or existing setting values.

Description

Displays a description of each property.

(1) Information displayed in the properties list

The tables below list and describe the information that is displayed as the properties of each service.

(a) Name Server [<Name Server> or PN*]

Node name

Property name

Description

--

First Registration Date

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date

Displays the most recent date and time the service was recognized by PFM - Manager.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current directory where the service is running.

Host Name

Displays the name of the host where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Name Server service.

INI File

Displays the name of the directory containing the jpcns.ini file.

Network Services

Service

--

Stores the information about the service. You cannot change the properties of this node.

Description

Displays additional service information, such as host name and service type

Local Service Name

Displays the service ID.

Legend: --: Not applicable

(b) Master Manager [<Master Manager> or PM*]

Node name

Property name

Description

--

First Registration Date

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date

Displays the most recent date and time the service was recognized by PFM - Manager.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current directory where the service is running.

Host Name

Displays the name of the host where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Master Manager service.

INI File

Displays the name of the directory containing the jpcns.ini file.

Network Services

Service

--

Stores the information about the service. You cannot change the properties of this node.

Description

Displays additional service information, such as host name and service type

Local Service Name

Displays the service ID.

Remote Service Name

Displays the service ID of the Master Store service at the connection target PFM - Manager host.

JP1 Event Configurations

Service name#1

Specify whether to issue JP1 events for each service. Select one of the values shown below. You cannot directly enter the value.

Yes

No

JP1 Event Send Host#2

Specify the event server name to connect to JP1/Base. However, you can specify only the event server that is running on the logical host or physical host on which the Action Handler service is running. You can specify the value in alphanumeric characters, periods, and hyphens in the range from 0 to 255 bytes. If the specified value is outside the range, the system assumes that a value was not entered. If the value is omitted, the host on which the Action Handler service is running is used as the host from which events are issued. If localhost is specified, the system assumes that a physical host is specified.

Monitoring Console Host#2

Specify the PFM - Web Console host to be started if you want to start the PFM - Web Console at JP1/IM - Manager monitor startup. You can specify the value in alphanumeric characters, periods, and hyphens in the range from 0 to 255 bytes. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, the PFM - Manager host for the connection destination is assumed.

Monitoring Console Port#2

Specify the port number (http request port number) of the PFM - Web Console to be started. You can specify a value in the range from 1 to 65535. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, 20358 is set for the value.

JP1 Event Configurations

Alarm

JP1 Event Mode#2

Specify the JP1 event#3 type for alarm events. Select the values from the list below. You cannot directly enter the value.

JP1 User Event

As the event ID, any specified value is output.

JP1 System Event

As the event ID, a value in the range from 00004800 to 00004850 is output.

System

Monitoring Suspend

Specify whether to issue a JP1 system event when suspending or resuming monitoring. The default is No.

Yes: Issue a JP1 system event.

Yes (Primary): Issue a JP1 system event only on the primary host in a multiple-monitoring environment.

No: Do not issue a JP1 system event.

Restart Configurations

Restart when Abnormal Status#2

Specify whether to use the automatic restart functionality in the Abnormal status#4. The set value is applied to all the services on the host. The default is Yes.

Yes: Perform automatic restarts.

No: Do not perform automatic restarts.

Restart when Single Service Running#2

Specify whether to use the automatic restart functionality in the Single Service Running status#5. The set value is applied to all the services on the host. The default is No.

Yes: Perform automatic restarts.

No: Do not perform automatic restarts.

Restart Configurations

Service name#6

Auto Restart

Specify whether to use the automatic restart functionality for the target service. The default is No.

Yes: Perform automatic restarts.

No: Do not perform automatic restarts.

Auto Restart - Interval(Minute)

Specify the interval (in minutes) for checking the operating status of the service if the automatic restart functionality is used. Specify an integer value in the range from 1 to 1,440. The default is 10 (minutes).

Auto Restart - Repeat Limit

Specify the number of successive attempts of a restart operation if the automatic restart functionality is used. Specify an integer value in the range from 1 to 10. The default is 5 (times).

Scheduled Restart

Specify whether the scheduled restart functionality is used for the target service. The default is No.

Yes: Use the scheduled restart functionality.

No: Do not use the scheduled restart functionality.

Scheduled Restart - Interval

Specify the interval for performing a restart operation if the scheduled restart functionality is used. Specify the integer value in the range from 1 to 1,000. The default is 1. Specify the unit in Scheduled Restart - Interval Unit.

Scheduled Restart - Interval Unit

Specify the unit for the restart interval in Month, Week, Day, or Hour if the scheduled restart functionality is used. The default is Month.

Month

Week

Day

Hour

Scheduled Restart - Origin - Year

Specify the origin year for the restart interval if the scheduled restart functionality is used. Specify the integer value in the range from 1971 to 2035#7. The default is the current year#8.

Scheduled Restart - Origin - Month

Specify the origin month for the restart interval if the scheduled restart functionality is used. Specify the integer value in the range from 1 to 12#7. The default is the current month#8.

Scheduled Restart - Origin - Day

Specify the origin day for the restart interval if the scheduled restart functionality is used. Specify the integer value in the range from 1 to 31#7. The default is the current day#8.

Scheduled Restart - Origin - Hour

Specify the origin time (hour) for the restart interval if the scheduled restart functionality is used. Specify the integer value from 0 to 23. The default is the current hour#8.

Scheduled Restart - Origin - Minute

Specify the origin time (minutes) for the restart interval if the scheduled restart functionality is used. Specify the integer value in the range from 0 to 59. The default is the current minute#8.

ITSLM Coordination Configuration

--

Stores information about JP1/ITSLM linkage.

ITSLM Coordination Configuration

ITSLM Coordination

--

Stores information about JP1/ITSLM linkage. You cannot change the properties of this node.

ITSLM Host

Displays the name of the linked JP1/ITSLM host.

This property is displayed only when there is a linked JP1/ITSLM host.

MANAGE ITSLM COORDINATION

--

Stores host information when JP1/ITSLM linkage is applied.

RELEASE ITSLM COORDINATION

Specify the linkage you want to cancel.

To cancel a linkage, select the name of the applicable JP1/ITSLM host from the list.

ASSIGN ITSLM COORDINATION

Specify the linkage you want to create.

For the linkage, type the applicable JP1/ITSLM host name. You can specify 0 to 63 bytes of one-byte alphanumeric characters, underscores, and hyphens.

SYNCHRONIZE ALL ITSLM CONNECTION

Specify the synchronization of linkages.

To synchronize linkages, select ALL from the list.

Legend: --: Not applicable

#1

The PFM - Manager service, the Action Handler service, and the Status Server service are displayed. For the Action Handler service and the Status Server service, the same setting is shared in all setting locations throughout a host.

#2

The same setting is shared in all setting locations throughout a host.

#3

For details about the JP1 event for alarm events, see the chapter that explains operation monitoring linking with the integrated management product (JP1/IM) in the Job Management Partner 1/Performance Management User's Guide.

#4

When the Status Server service cannot correctly acquire the status of the target PFM service (for example, when the target PFM service was terminated abnormally because of an exception or some other reason).

#5

When only one of the PFM - Agent and PFM - RM services is running.

#6

The PFM - Manager service and the Action Handler service are displayed.

#7

If a date that does not actually exist (such as 2007-2-30) is specified, the last day of the month is used.

#8

Displays the date and time when the property is displayed in the local time of the host where the target service is running.

(c) Master Store [<Master Store> or PS*]

Node name

Property name

Description

--

First Registration Date

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date

Displays the most recent date and time the service was recognized by PFM - Manager.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current directory where the service is running.

Host Name

Displays the name of the host where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Master Store service.

INI File

Displays the name of the directory containing the jpcns.ini file.

Network Services

Service

--

Stores the information about the service. You cannot change the properties of this node.

Description

Displays additional service information, such as host name and service type.

Local Service Name

Displays the service ID.

Remote Service Name

Displays the service ID of the Master Manager service at the connection target PFM - Manager host.

EP Service Name

Displays the service ID of Correlator on the same host.

Retention

--

Sets the data retention period. For details, see the chapter that explains the management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide.

Product Alarm - PA

Sets the maximum number of records to be saved for the event data of each agent or each Remote Monitor Collector service. An integer between 0 and 2,147,483,647 may be specified.#

Note

If a numeric value outside this range, or characters such as letters are specified, an error message is displayed.

Disk Usage

--

Stores the disk space used by each database. The properties of this node show the disk space at the point at which the properties are displayed.

Product Interval

Displays the disk space used by records of the PI record type.

Product Detail

Displays the disk space used by records of the PD record type.

Product Alarm

Displays the disk space used by records of the PA record type.

Product Log

Displays the disk space used by records of the PL record type.

Total Disk Usage

Displays the total amount of disk space used by the entire database.

Legend: --: Not applicable

#

For details about estimating the maximum number of records to be saved, see the section that explains the amount of disk space that is consumed in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

(d) Correlator [<Correlator> or PE*]

Node name

Property name

Description

--

First Registration Date

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date

Displays the most recent date and time the service was recognized by PFM - Manager.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current directory where the service is running.

Host Name

Displays the name of the host where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Correlator service.

INI File

Displays the name of the directory containing the jpcns.ini file.

Network Services

Service

--

Stores the information about the service. You cannot change the properties of this node.

Description

Displays additional service information, such as host name and service type.

Local Service Name

Displays the service ID.

Remote Service Name

Displays the service ID of the Master Manager service at the connection target PFM - Manager host.

Legend: --: Not applicable

(e) Trap Generator [<Trap Generator> or PC*]

Node name

Property name

Description

--

First Registration Date

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date

Displays the most recent date and time the service was recognized by PFM - Manager.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current directory where the service is running.

Host Name

Displays the name of the host where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Trap Generator service.

INI File

Displays the name of the directory containing the jpcns.ini file.

Network Services

Service

--

Stores the information about the service. You cannot change the properties of this node.

Description

Displays additional service information, such as host name and service type.

Local Service Name

Displays the service ID.

Remote Service Name

Displays the service ID of the Master Manager service at the connection target PFM - Manager host.

Trap Destinations

--

Specifies information for the trap destination.

Trap Destinations

Trap-destination-host-name-or-IP-address

--

Specifies information for the trap destination for each host.

Retry Count

Specifies the retry count. An integer between 1 and 32,767 can be specified.

Note

If a numeric value outside this range, or characters such as letters are specified, an error message is displayed.

Retry Interval

Specifies the retry interval in seconds. An integer between 1 and 32,767 can be specified.

Note

If a numeric value outside this range, or characters such as letters are specified, an error message is displayed.

Trap Port

Specifies the destination port number. An integer between 1 and 32,767 can be specified.

Note

If a numeric value outside this range, or characters such as letters are specified, an error message is displayed.

Enabled

Specifies whether to enable the destination. One of the following values must be selected; direct input is not possible:

Yes

No

ADD OR DELETE A TRAP DESTINATION

--

Adds or deletes the trap destination.

ADD A DESTINATION

Specifying a destination host name and clicking the OK button adds the trap destination setting for the specified host to Trap Destinations. You can use no more than 75 bytes of alphanumeric characters and hyphens (-) to specify a destination host name.

Note

If you specify a character string that is more than 75 bytes, an error message appears.

DELETE A DESTINATION

Specifying a destination host name and clicking the OK button deletes the settings for the selected destination host. Using the ADD A DESTINATION property, a host name (or IP address) already specified as the trap destination can be selected.

Legend: --: Not applicable

(f) Action Handler [<Action Handler> or PH*]

Node name

Property name

Description

--

First Registration Date

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date

Displays the most recent date and time the service was recognized by PFM - Manager.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current directory where the service is running.

Host Name

Displays the name of the host where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Action Handler service.

INI File

Displays the name of the directory containing the jpcns.ini file.

Network Services

Service

--

Stores information about the service. The properties stored in this folder cannot be changed.

Description

Displays additional service information, such as host name and service type.

Local Service Name

Displays the service ID.

Remote Service Name

Displays the service ID of the Master Manager service at the connection target PFM - Manager host.

JP1 Event Configurations

Service name#1

Specify whether to issue JP1 events for each service. Select one of the values shown below. You cannot directly enter the value.

Yes

No

JP1 Event Send Host#2

Specify the event server name to connect to JP1/Base. However, you can specify only the event server that is running on the logical host or physical host on which the Action Handler service is running. You can specify the value in alphanumeric characters, periods, and hyphens in the range from 0 to 255 bytes. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, the host on which the Action Handler service is running is used as the host from which events are issued. If localhost is specified, the system assumes that a physical host is specified.

Monitoring Console Host#2

Specify the PFM - Web Console host to be started if you want to start the PFM - Web Console at JP1/IM - Manager monitor startup. You can specify the value in alphanumeric characters, periods, and hyphens in the range from 0 to 255 bytes. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, the PFM - Manager host for the connection destination is assumed.

Monitoring Console Port#2

Specify the port number (http request port number) of the PFM - Web Console to be started. You can specify the value in the range from 1 to 65535. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, 20358 is set for the value.

JP1 Event Configurations

Alarm

JP1 Event Mode#2

Specify the JP1 event#3 type for alarm events. Select the values from the list below. You cannot directly enter the value.

JP1 User Event

As the event ID, any specified value is output.

JP1 System Event

As the event ID, 00004840 is output.

Capabilities

--

Stores the information about the service. You cannot change the properties of this node.

Email

Specifies whether or not the action handler for sending emails is to be specified during alarm definition. One of the following values must be selected; direct input is not possible:

Yes

No

Script

Specifies whether or not the action handler for executing commands is to be specified during alarm definition. One of the following values must be selected; direct input is not possible:

Yes

No

Mail

--

Specifies various information for sending email.

SMTP Host

Displays the SMTP (send email) server host name (or IP address). You can use no more than 100 bytes of alphanumeric characters and hyphens (-) to specify the host name.

SMTP Sender

Displays the name of the sender of the email. You can use no more than 100 bytes of symbols and alphanumeric characters to specify the server name.

Mail Subject

Displays the email subject. You can use no more than 100 bytes of two-byte or single-byte characters.#4

Charset

Displays the character set (language) of the email to be sent. For the character set (language), you can select ISO-2022-JP, UTF-8, and GB18030. These character sets provide support for sending email in a variety of languages.

Multiple Manager Configuration

Primary Manager

Displays the host name of the manager specified as the primary manager. You cannot change this property.

Secondary Manager

Displays the host name of the manager specified as the secondary manager. You cannot change this property.

Legend: --: Not applicable

#1

The Action Handler service and the Status Server service are displayed. For the Action Handler service and the Status Server service, the same setting is shared in all setting locations throughout a host.

#2

The same setting is shared in all setting locations throughout a host.

#3

For details about the JP1 event for alarm events, see the chapter that explains operation monitoring linking with the integrated management product (JP1/IM) in the Job Management Partner 1/Performance Management User's Guide.

#4

If the length of the Mail Subject that replaces the variable is more than 100 bytes, the Agent Collector or Remote Monitor Collector service outputs the KAVE00184-W message when the alarm is reported.

If this message appears, adjust the character string specified for Mail Subject and the number of digits specified for %CVS so the subject length is not more than 100 bytes.

(g) Agent Store (health check agent) [*<HealthCheck>(Store) or 0S*]

Node name

Property name

Description

--

First Registration Date

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date

Displays the most recent date and time the service was recognized by PFM - Manager.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current folder where the service is running.

Host Name

Displays the host name where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Agent Store service.

INI File

Displays the name of the folder containing the jpcns.ini file.

Network Services

Service

--

Stores the information about the service. You cannot change the properties of this node.

Description

Displays additional service information, such as the host name and service type.

Local Service Name

Displays the service ID.

Remote Service Name

Displays the service ID of the Master Manager service at the connection target PFM - Manager host.

EP Service Name

Displays the service ID of the Correlator service at the connection target PFM - Manager host.

Retention

--

Sets the data retention period. For details, see the chapter that explains the management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide.

Product Interval - Minute Drawer

Sets the retention period for minute-by-minute records of the PI record type. You can select an option from the following list:

Minute

Hour

Day

2 Days

3 Days

4 Days

5 Days

6 Days

Week

Month

Year

Product Interval - Hour Drawer

Sets the retention period for hourly records of the PI record type. You can select an option from the following list:

Hour

Day

2 Days

3 Days

4 Days

5 Days

6 Days

Week

Month

Year

Product Interval - Day Drawer

Sets the retention period for daily records of the PI record type. You can select an option from the following list:

Day

2 Days

3 Days

4 Days

5 Days

6 Days

Week

Month

Year

Product Interval - Week Drawer

Sets the retention period for weekly records of the PI record type. You can select an option from the following list:

Week

Month

Year

Product Interval - Month Drawer

Sets the retention period for monthly records of the PI record type. You can select an option from the following list:

Month

Year

Product Interval - Year Drawer

Retention period for yearly records of the PI record type. The option is fixed to Year.

Product Detail - Record ID of the PD record type

Sets the number of retained records of each PD record type. You can specify an integer from 0 to 2,147,483,647.

Note

If you specify a number outside the range or a character such as an alphabetic character, an error message appears.

RetentionEx

--

Sets the data retention period when the Store version is 2.0. For details, see the chapter that explains the management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide.

RetentionEx

Product Interval - Record ID of the PI record type

--

Sets the retention period for the records of the PI record type.

Period - Minute Drawer (Day)

Sets the retention period for minute-by-minute data for each record ID of the PI record type.

You can specify an integer from 0 to 366 as the retention period (number of days).

Period - Hour Drawer (Day)

Sets the retention period for hourly data for each record ID of the PI record type.

You can specify an integer from 0 to 366 as the retention period (number of days).

Period - Day Drawer (Week)

Sets the retention period for daily data for each record ID of the PI record type.

You can specify an integer from 0 to 522 as the retention period (number of weeks).

Period - Week Drawer (Week)

Sets the retention period for weekly data for each record ID of the PI record type.

You can specify an integer from 0 to 522 as the retention period (number of weeks).

Period - Month Drawer (Month)

Sets the retention period for monthly data for each record ID of the PI record type.

You can specify an integer from 0 to 120 as the retention period (number of months).

Period - Year Drawer (Year)

Displays the retention period for yearly data for each record ID of the PI record type.

Product Detail - Record ID of the PD record type

Period (Day)

Sets the data retention period for each record ID of the PD record type.

You can specify an integer from 0 to 366 as the retention period (number of days).

Disk Usage

--

Stores the disk space used by each database. The properties of this node show the disk space at the point at which the properties are displayed. You cannot change the properties of this node.

Product Interval

Displays the disk space used by records of the PI record type.

Product Detail

Displays the disk space used by records of the PD record type.

Product Alarm

Displays the disk space used by records of the PA record type.

Product Log

Displays the disk space used by records of the PL record type.

Total Disk Usage

Displays the total amount of disk space used by all the databases.

Configuration

--

Displays the properties of the Agent Store service.

Store Version

Displays the version of the Store database.

For the Store database version 1.0:

1.0

For the Store database version 2.0:

2.0

Multiple Manager Configuration

Primary Manager

Displays the host name of the manager specified as the primary manager. You cannot change this property.

Secondary Manager

Displays the host name of the manager specified as the secondary manager. You cannot change this property.

Legend: --: Not applicable

(h) Agent Collector (health check agent) [*<HealthCheck> or 0A*]

Node name

Property name

Description

--

First Registration Date#1

Displays the first date and time the service was recognized by PFM - Manager.

Last Registration Date#1

Displays the most recent date and time the service was recognized by PFM - Manager.

DataModelVersion

Displays the version of the data model.

General

--

Stores information such as a host name and a directory. You cannot change the properties of this node.

Directory

Displays the name of the current folder where the service is running.

Host Name

Displays the host name where the service is running.

Process ID

Displays the service's process ID.

Physical Address

Displays the IP address and port number of the host where the service is running when the IPv6 communication functionality is disabled.

Physical Address(IPv4)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv4) of the host where the service is running.

Physical Address(IPv6)

When the IPv6 communication functionality is enabled. Displays the IP address (IPv6) of the host where the service is running.

Port Number

When the IPv6 communication functionality is enabled. Displays the number of the port where the service is running.

User Name

Displays the user name of the user who executed the service process.

Time Zone

Displays the time zone in which the service is running.

System

--

Stores the information about the OS on which the service is started. You cannot change the properties of this node.

CPU Type

Displays the CPU type.

Hardware ID

Displays the hardware ID.

OS Type

Displays the type of operating system.

OS Name

Displays the name of the operating system.

OS Version

Displays the version of the operating system.

Network Services

--

Stores the information about the Performance Management communication common library. You cannot change the properties of this node.

Build Date

Displays the creation date of the Agent Collector service.

INI File

Displays the name of the folder containing the jpcns.ini file.

Network Services

Service

--

Stores the information about the service. You cannot change the properties of this node.

Description

Displays additional service information, such as the host name and service type.

Local Service Name

Displays the service ID.

Remote Service Name

Displays the service ID of the Agent Store service to which the Agent Collector service is connected.

EP Service Name

Displays the service ID of the Correlator service on the PFM - Manager host for the connection destination.

AH Service Name

Displays the service ID of the Action Handler service on the same host.

JP1 Event Configurations

--

Stores the properties relating to the conditions for issuing JP1 events.

Each service

Specify Yes or No from the list items for the Agent Collector service, the Agent Store service, the Action Handler service, and the Status Server service to specify whether each service is to issue JP1 system events.

JP1 Event Send Host

Specify the event server name to which JP1/Base is to be connected. However, you can specify only the event server that is running on the logical host or physical host on which the Action Handler service is running. You can specify the value in alphanumeric characters, periods, and hyphens in the range from 0 to 255 bytes. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, the host on which the Action Handler service is running is used as the host from which events are issued. If localhost is specified, the system assumes that a physical host is specified.

Monitoring Console Host

Specify the PFM - Web Console host to be started if you want to start the PFM - Web Console at JP1/IM - Manager monitor startup. You can specify the value in alphanumeric characters, periods, and hyphens in the range from 0 to 255 bytes. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, the PFM - Manager host for the connection destination is assumed.

Monitoring Console Port

Specify the port number (http request port number) of the PFM - Web Console to be started. You can specify the value in the range from 1 to 65535. If the specified value is outside the range, the system assumes that a value was not entered. If a value is not entered, 20358 is set for the value.

JP1 Event Configurations

Alarm

JP1 Event Mode

Specify whether the JP1 system event is to be issued or the JP1 user event is to be issued when the alarm status changes.

JP1 User Event: The JP1 user event is to be issued.

JP1 System Event: The JP1 system event is to be issued.

Detail Records

--

Stores the properties of the records of the PD record type. The record IDs of the collected records are displayed in bold.

Detail Records

Record ID

--

Stores the properties of the record.

Description

Displays the description of the record. You cannot change this property.

Log

Select Yes or No from the listed items to specify whether to record the record in the Agent Store database. If this value is Yes (or No, and the value for Log(ITSLM) is Yes) and the value of Collection Interval is greater than 0, the record is recorded in the database.

Log(ITSLM)

Displays the setting in JP1/ITSLM for whether to record the record in the Agent Store database. You cannot change this property.

If this value is Yes (or No, and the value for Log is Yes), and the value of Collection Interval is greater than 0, the record is recorded in the database.

Monitoring(ITSLM)

Displays the setting in JP1/ITSLM for whether to send the record to JP1/ITSLM. You cannot change this property.

If this value is Yes, and the value of Collection Interval is greater than 0, the record is sent to JP1/ITSLM.

Collection Interval

Specifies the data collection interval. You can specify a value, in seconds, from 0 to 2,147,483,647. If you specify 0 (meaning 0 seconds), no data is collected.

Collection Offset

Specifies the offset value for starting data collection. You can specify a value, in seconds, from 0 to 32,767 that is within the value range specified for Collection Interval. Note that the time recorded for data collection is the same as Collection Interval and does not depend on the value of Collection Offset.

Over 10 Sec Collection Time

Displayed only when collecting history data takes priority over displaying realtime reports.#2

This property displays whether it might take 10 seconds or more to collect records.

Yes: It might take 10 seconds or more.

No: It takes less than 10 seconds.

You cannot change this property.

Realtime Report Data Collection Mode

Displayed only when collecting history data takes priority over displaying realtime reports.#2

This property specifies the display mode for realtime reports.

Reschedule: Specifies the re-schedule mode.

Temporary Log: Specifies temporary log mode.

Note that you need to specify temporary log mode (Temporary Log) for records for which the value for Over 10 Sec Collection Time is set to Yes.

LOGIF

Specifies the conditions for recording records in the database. Only records matching the specified conditions are recorded in the database. This property displays a condition expression (string) created in the LOGIF Expression Editor window that is opened by clicking LOGIF in the lower frame of the Service Properties window that is displayed on the Services page of PFM - Web Console.

Interval Records

--

Stores the properties of the records of the PI record type. The record IDs of the collected records are displayed in bold.

Interval Records

Record ID

--

Stores the properties of the record.

Description

Displays the description of the record. You cannot change this property.

Log

Select Yes or No from the listed items to specify whether to record the record in the Agent Store database. If this value is Yes (or No, and the value for Log(ITSLM) is Yes) and the value of Collection Interval is greater than 0, the record is recorded in the database.

Log(ITSLM)

Displays the setting in JP1/ITSLM for whether to record the record in the Agent Store database. You cannot change this property.

If this value is Yes (or No, and the value for Log is Yes), and the value of Collection Interval is greater than 0, the record is recorded in the database.

Monitoring(ITSLM)

Displays the setting in JP1/ITSLM for whether to send the record to JP1/ITSLM. You cannot change this property.

If this value is Yes, and the value of Collection Interval is greater than 0, the record is sent to JP1/ITSLM.

Collection Interval

Specifies the data collection interval. You can specify a value, in seconds, from 0 to 2,147,483,647. If you specify 0 (meaning 0 seconds), no data is collected.

Collection Offset

Specifies the offset value for starting data collection. You can specify a value, in seconds, from 0 to 32,767 that is within the value range specified for Collection Interval. Note that the time recorded for data collection is the same as Collection Interval and does not depend on the value of Collection Offset.

Over 10 Sec Collection Time

Displayed only when collecting history data takes priority over displaying realtime reports.#2

This property displays whether it might take 10 seconds or more to collect records.

Yes: It might take 10 seconds or more.

No: It takes less than 10 seconds.

You cannot change this property.

Realtime Report Data Collection Mode

Displayed only when collecting history data takes priority over displaying realtime reports.#2

This property specifies the display mode for realtime reports.

Reschedule: Specifies the re-schedule mode.

Temporary Log: Specifies temporary log mode.

Note that you need to specify temporary log mode (Temporary Log) for records for which the value for Over 10 Sec Collection Time is set to Yes.

LOGIF

Specifies the conditions for recording records in the database. Only records matching the specified conditions are recorded in the database. This property displays a condition expression (string) created in the LOGIF Expression Editor window that is opened by clicking LOGIF in the lower frame of the Service Properties window that is displayed on the Services page of PFM - Web Console.

Log Records

--

Stores the properties of the records of the PL record type. This item is not used since the health check agent does not support this record type.

Restart Configurations

--

Specify the conditions of PFM service automatic restart. For details about the PFM service automatic restart functionality, see the chapter that explains the Performance Management functionality in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Restart when Abnormal Status

Specify whether the services are automatically started when the Status Server service cannot correctly acquire the status of the Action Handler service, the Agent Collector service, and the Agent Store service.

Restart when Single Service Running

Specify whether the service is automatically started when either the Agent Store service or the Agent Collector service is running.

Restart Configurations

Action Handler

Auto Restart

Specify whether the automatic restart functionality is used for the Action Handler service.

Auto Restart - Interval (Minute)

Specify the interval (in minutes) for checking the operating status of the service if the automatic restart functionality is used.

Auto Restart - Repeat Limit

Specify the number of successive attempts of restart operation if the automatic restart functionality is used.

Scheduled Restart

Specify whether the scheduled restart functionality is to be used for the Action Handler service.

Scheduled Restart - Interval

Specify the interval for performing restart operation if the scheduled restart functionality is used.

Scheduled Restart - Interval Unit

Specify the unit for the restart interval if the scheduled restart functionality is used.

Scheduled Restart - Origin - Year

Specify the year for restarting as an integer value in the range from 1971 to 2035.

Scheduled Restart - Origin - Month

Specify the month for restarting as an integer value in the range from 1 to 12.

Scheduled Restart - Origin - Day

Specify the date for restarting as an integer value in the range from 1 to 31.

Scheduled Restart - Origin - Hour

Specify the time (hour) for restarting as an integer value in the range from 0 to 23.

Scheduled Restart - Origin - Minute

Specify the time (minutes) for restarting as an integer value in the range from 0 to 59.

Agent Collector

Auto Restart

Specify whether the automatic restart functionality is to be used for the Agent Collector service.

Auto Restart - Interval (Minute)

Specify the interval (in minutes) for checking the operating status of the service if the automatic restart functionality is used.

Auto Restart - Repeat Limit

Specify the number of successive attempts of restart operation if the automatic restart functionality is used.

Scheduled Restart

Specify whether the scheduled restart functionality is to be used for the Agent Collector service.

Scheduled Restart - Interval

Specify the interval for performing restart operation if the scheduled restart functionality is used.

Scheduled Restart - Interval Unit

Specify the unit for the restart interval if the scheduled restart functionality is used.

Scheduled Restart - Origin - Year

Specify the year for restarting as an integer value in the range from 1971 to 2035.

Scheduled Restart - Origin - Month

Specify the month for restarting as an integer value in the range from 1 to 12.

Scheduled Restart - Origin - Day

Specify the date for restarting as an integer value in the range from 1 to 31.

Scheduled Restart - Origin - Hour

Specify the time (hour) for restarting as an integer value in the range from 0 to 23.

Scheduled Restart - Origin - Minute

Specify the time (minutes) for restarting as an integer value in the range from 0 to 59.

Agent Store

Auto Restart

Specify whether the automatic restart functionality is to be used for the Agent Store service.

Auto Restart - Interval (Minute)

Specify the interval (in minutes) for checking the operating status of the service if the automatic restart functionality is used.

Auto Restart - Repeat Limit

Specify the number of successive attempts of restart operation if the automatic restart functionality is used.

Scheduled Restart

Specify whether the scheduled restart functionality is to be used for the Agent Store service.

Scheduled Restart - Interval

Specify the interval for performing restart operation if the scheduled restart functionality is used.

Scheduled Restart - Interval Unit

Specify the unit for the restart interval if the scheduled restart functionality is used.

Scheduled Restart - Origin - Year

Specify the year for restarting as an integer value in the range from 1971 to 2035.

Scheduled Restart - Origin - Month

Specify the month for restarting as an integer value in the range from 1 to 12.

Scheduled Restart - Origin - Day

Specify the day for restarting as an integer value in the range from 1 to 31.

Scheduled Restart - Origin - Hour

Specify the time (hour) for restarting as an integer value in the range from 0 to 23.

Scheduled Restart - Origin - Minute

Specify the time (minutes) for restarting as an integer value in the range from 0 to 59.

ITSLM Connection Configuration

--

Displays information about the linked JP1/ITSLM.

ITSLM Connection Configuration

ITSLM Connection

--

Displays information about the destination JP1/ITSLM.

ITSLM Host

Displayed only when there is a connected JP1/ITSLM host.

ITSLM Port

Displayed only when there is a connected JP1/ITSLM host.

MANAGE ITSLM CONNECTION

--

Sets whether to end the JP1/ITSLM connection.

DISCONNECT ITSLM CONNECTION

Specify the connection you want to end.

To end a connection, select the applicable JP1/ITSLM host name from the list.

Health Check Configurations#1

--

Stores the properties of the health check agent.

Monitoring Level#3

Specifies the monitoring level. To monitor the operating status of the service, specify Service. To monitor the operating status of the agent host, specify Host.

You cannot specify this property if there is a host or agent for which monitoring is suspended.

Polling Interval

Displays the polling cycle. This value is synchronized with Collection Interval of the PD_HC record.

Incl Action Handler

Specifies whether to include the Action Handler service as a monitoring target when you monitor the operation of services.

Yes: Include the service as a monitoring target.

No: Do not include the service as a monitoring target.

Busy as Inactive

Specifies whether to treat an agent service as inactive when the status of the agent service is busy for a long time. Note that the Time to Busy as Inactive setting is enabled only when you specify Yes.

Yes: Treat the service as inactive.

No: Do not treat the service as inactive.

To check the status of an agent service, execute the jpctool service list command and check the value displayed for Status.

Time to Busy as Inactive Collector

Specifies the length of time, in seconds, before the system starts to treat the busy Agent Collector service as inactive.

Time to Busy as Inactive Store

Specifies the length of time, in seconds, before the system starts to treat the busy Agent Store service as inactive.

Time to Busy as Inactive AH

Specifies the length of time, in seconds, before the system starts to treat the busy Action Handler service as inactive.

JP1 Event

Specifies whether to issue a JP1 event as a health check event. Select either of the following values. You cannot type a value.

Yes

No

By default, No is set.

JP1 Event - Not supported

Specifies the event level for the Not Supported status. You can select a value from the following list:

None

Information

Warning

Error

By default, None is set.

JP1 Event - Running

Specifies the event level for the Running status. You can select a value from the following list:

None

Information

Warning

Error

By default, Information is set.

JP1 Event - Incomplete

Specifies the event level for the Incomplete status. You can select a value from the following list:

None

Information

Warning

Error

By default, Warning is set.

JP1 Event - Stopped

Specifies the event level for the Stopped status. You can select a value from the following list:

None

Information

Warning

Error

By default, Error is set.

JP1 Event - Unconfirmed

Specifies the event level for the Unconfirmed status. You can select a value from the following list:

None

Information

Warning

Error

By default, Error is set.

JP1 Event - Host Not Available

Specifies the event level for the Host Not Available status. You can select a value from the following list:

None

Information

Warning

Error

By default, Error is set.

Parallel Confirmation Mode

Specifies whether to enable parallel confirmation mode for multiple hosts. Select either of the following values. You cannot type a value.

Enable

Disable

By default, Enable is set.

Parallel Confirmation Count

Specifies an integer from 1 to 50 for the number of parallel confirmation hosts in parallel confirmation mode. By default, 10 is set.

Minimum Period per Host

Specifies an integer from 0 to 60 for the minimum confirmation period (in seconds) for each host in parallel confirmation mode. By default, 0 (seconds) is set.

Timeout Period per Host

Specify an integer from 2 to 60 for the timeout period (in seconds) for each host in parallel confirmation mode. By default, 30 (seconds) is set.

Multiple Manager Configuration

Primary Manager

Displays the host name of the manager specified as the primary manager. You cannot change this property.

Secondary Manager

Displays the host name of the manager specified as the secondary manager. You cannot change this property.

Legend: --: Not applicable

#1

When you change the Health Check Configurations setting, the new setting is applied starting with the next polling cycle.

#2

For details, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

#3

When you change the Monitoring Level setting, in the realtime reports of the health check agent, the health check result to be displayed differs depending on whether the polling after the change is completed at the point at which the reports are displayed.

Monitoring agent

Health check result to be displayed

Monitoring agent for which the polling with the new setting has been completed

Latest health check result with the new setting

Monitoring agent for which the polling with the new setting has not been performed

Latest health check result with the previous setting

Note, therefore, that both the old and new settings can appear temporarily.

(i) Agent Store and Remote Monitor Store [*<*>(Store) or ?S*]

The properties of the Agent Store and Remote Monitor Store services differ depending on the PFM - Agent or PFM - RM in use. For details about the properties of the Agent Store and Remote Monitor Store services, see the properties of the Agent Store and Remote Monitor Store services that are described in the appendix of the PFM - Agent or PFM - RM manuals.

(j) Agent Collector and Remote Monitor Collector [*<*> or ?A*]

The properties of the Agent Collector and Remote Monitor Collector services depending on the PFM - Agent or PFM - RM in use, are different. For details about the properties of the Agent Collector and Remote Monitor Collector services, see the properties of the Agent Collector and Remote Monitor Collector services that are described in the appendix of the PFM - Agent or PFM - RM manuals.

(k) Remote agent and group agent [*<*> or ?A*]

The properties of the remote agent and the group agent, depending on the PFM - RM in use, are different. For details about the properties of the remote agent and the group agent, see the properties of the remote agent and the group agent that are described in the appendix of the PFM - RM manuals.

(2) LOGIF Expression Editor window

The LOGIF Expression Editor window is used to set LOGIF expressions. To display this window, in the Service Properties window for the Agent Collector or Remote Monitor Collector service, click the LOGIF text box.

The following figure shows the LOGIF Expression Editor window.

Figure 1‒122: LOGIF Expression Editor window

The following describes the displayed items:

Close

Closes the LOGIF Expression Editor window.

Field

From the pull-down menu, select the target field for which the conditional expressions are specified.

Condition

From the pull-down menu, select the operator you want to use for specifying the conditional expression.

This item is enabled when a selection is made in Field.

Value

Specifies the value that is to be used as the reference for determining a condition expression. You can specify an integer, a decimal number, or single-byte or two-byte characters. The value cannot exceed 2,048 bytes.

The permissible values depend on the field.

AND

Sets the AND operation between existing conditional expressions and the conditional expression set in Field, Condition, and Value. This option is enabled only when at least one conditional expression is set in Conditional expression.

OR

Sets the OR operation between existing conditional expressions and the conditional expression set in Field, Condition, and Value. This option is enabled only when at least one conditional expression is set in Conditional expression.

Add button

Adds the conditional expression set in Field, Condition, and Value to Conditional expression. This option is enabled when Value is set.

Update button

Replaces the conditional expression selected in Conditional expression with the new conditional expression set in Field, Condition, or Value. This option is enabled only when at least one conditional expression is set in Conditional expression.

Description button

Displays the Description of Record and Fields window for a record and its fields as a separate window.

Conditional expression

Displays the conditional expressions that have been specified in Field, Condition, and Value. If the length of the defined conditional expressions is more than 511 bytes, an error message is displayed.

The length of the character string for one conditional expression

PFM - Manager-name=["specified-value"]

PFM - Web Console specifies a field as a View name. This name must be converted to a PFM - Manager name. The format of the PFM - Manager name here is as follows:

record-ID_PFM - Manager-name-of-the-field

For example, the Program field of PD_PDI is expressed as PD_PDI_INSTANCE.

For details about the PFM - Manager name, see the chapter that explains records in the PFM - Agent or PFM - RM manual.

The character string that is added when multiple conditional expressions are joined

To join multiple conditions, join the conditions expressed by the above format with " OR " or " AND ". When you specify a condition expressed by two or more conditional expressions, they are enclosed by parentheses ((, )), so these parentheses must be also counted in.

The length of the character string for LOGIF

The length of the LOGIF conditional expression can be calculated by using the following formula:

the-length-of-LOGIF-character-string = the-total-length-of-conditional-expressions#1 + the-number-of-OR-operators * 4 + the-number-of-AND-operators * 5 + the-number-of-"("s + the-number-of-")"s#2

the-length-of-the-character-string = the-length-of-the-PFM - Manager-name + the-length-of-the-specified-character-string + 5

#1: the-total-length-of-conditional-expressions is the total length of all the character strings, each of which is calculated for each specified conditional expression.

#2: These parentheses must be used if two or more conditional expressions are added. The number of required parentheses is expressed by the following formula: 2 * (the-number-of-conditional-expressions - 1).

According to the above condition, you can calculate the length of the LOGIF character string as follows:

(1) If there are 20 conditional expressions, the-length-of-all-the-conditional-expressions = 15 + 10 + 5 = 30, and only OR is used as the operator:

the-length-of-LOGIF-character-string = 30 * 20 + (20 - 1) * 4 + 0 * 5 + (20 - 1) * 2
                            =  600 + 76 + 0 + 38 = 712

(2) If there are 12 conditional expressions, the-length-of-all-the-conditional-expressions = 15 + 10 + 5 = 30, and only OR is used as the operator:

the-length-of-LOGIF-character-string = 30 * 12 + (12 - 1) * 4 + 0 * 5 + (12 - 1) * 2
                            = 360 + 44 + 0 + 22 = 426

After performing the calculations shown above, adjust so that the length of the LOGIF character string is less than 512 bytes.

AND <--> OR button

Toggles between AND and OR for the conditional expression. This option is enabled only when the conditional expression selected in Conditional expression is not on the first line.

Edit button

Use this button to edit a condition expression that you selected in Conditional expression and that is displayed in Field, Condition, and Value. This button is displayed only when at least one condition expression is set in Conditional expression.

Delete button

Deletes the conditional expression selected in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

Delete All button

Deletes all conditional expressions displayed in Conditional expression. This option is enabled only when at least one conditional expression is set in Conditional expression.

OK button

Applies the settings, and closes the LOGIF Expression Editor window.

Cancel button

Discards the settings, and closes the LOGIF Expression Editor window.

1.8.3 Service status window

The Service status window is used to display the status of a selected service. To display this window, in the Services window, in the method frame, choose Service status.

The following figure shows the Service status window.

Figure 1‒123: Service status window

The following describes the displayed items:

Service

Displays the service ID of the selected service.

Status

Displays the status of the selected service.

1.8.4 Distribute Property window

The Distribute Property window is used to distribute properties.

(1) Distribute Property > Select Service window

To display this window, in the Services window, from the navigation frame, choose the Collector service or Store service of the monitoring agent, and then from the method frame, choose the Distribute Property method. Nodes of the remote agent or group agent are also displayed, and their properties can be distributed.

This window displays different items when the business group access control functionality is enabled and when it is disabled. The following figure shows the Distribute Property > Select Service window when the business group access control functionality is enabled.

Figure 1‒124: Distribute Property > Select Service window (when the business group access control functionality is enabled)

The following describes the displayed items:

Cancel button

Cancels the operation, and clears the information frame.

Next > button

Choosing this button displays the Distribute Property > Select Property window.

The button is activated when you select at least one distribution destination service whose product and data model version are the same as the distribution source service.

Finish button

Applies the settings, and distributes the property values selected in the navigation frame to the destination service you selected in this window. When distribution starts, the Distribute Property > Progress Reports window opens.

This button is available only when at least one distribution destination service is selected in this window, and properties are selected for distribution in the Distribute Property > Select Property window, which opens next.

Filter of services for distribution

Pull-down menu

Specify this item when you want to filter the distribution destination services displayed in Candidate services for distribution by business group. This item is not displayed when the business group access control functionality is disabled. The following are the items displayed in the pull-down menu:

All business groups

Select this item to display all agent services you can select as destinations for distribution.

Business group name

Select this item to display the agent services to which you assigned business groups from among the agent services that can be selected as destinations for distribution. Only business groups with the reference privilege are displayed.

Unassigned

Select this item to display the agent services to which you did not assign business groups from among the agent services that can be selected as destinations for distribution. This item is displayed only when the user has logged in as a system user.

Text box

Use this text box to filter services by keywords. Specify keywords when you want to filter the distribution destination services that are displayed in Candidate services for distribution. Specify a character string of 1 to 1,024 characters to filter the services that will be displayed. To perform a multi-keyword search by using AND or OR, delimit keywords by using a single-byte space, a two-byte space, or a tab. A delimiter is counted as one word. The maximum number of words that can be entered as filtering keywords is 100.

Filter button

Filters services by using the string specified in the text box.

Clear button

Clears the filtering status and the filtering condition.

AND

Select this option button to perform an AND search.

OR

Select this option button to perform an OR search.

Candidate services for distribution

Displays services (services for which the source service, product, and data model version for distribution are the same) that can be specified as a destination for distribution within the business group specified in Filter of services for distribution.

If there are no services that can be selected as a destination for distribution in the business groups you specified, an empty list is displayed.

Arrow buttons (///)

Use these buttons to move the displayed services between Candidate services for distribution and Selected services for distribution.

button

Moves the selected service from Candidate services for distribution to Selected services for distribution.

button

Moves the selected service from Selected services for distribution to Candidate services for distribution.

button

Moves all services from Candidate services for distribution to Selected services for distribution.

button

Moves all services from Selected services for distribution to Candidate services for distribution.

Selected services for distribution

Displays all services added from Candidate services for distribution. The services displayed here are not affected by Filter of services for distribution.

Area for displaying details about the selected service

Displays detailed information about the service from among those selected in Candidate services for distribution or Selected services for distribution that was displayed last. Information is displayed only when one service is selected.

(2) Distribute Property > Select Property window

The Distribute Property > Select Property window is used to select the properties to be distributed.

The following figure shows the Distribute Property > Select Property window.

Figure 1‒125: Distribute Property > Select Property window

The following describes the displayed items:

Contents area:

Displays hierarchically the properties of the Collector service or Store service of the monitoring agent selected as the distribution source.

Select All button

Selects all check boxes in the Apply column.

UnSelect All button

Clears all check boxes in the Apply column.

Cancel button

Cancels the operation, and clears the information frame.

< Back button

Returns to the Distribute Property > Select Service window.

Finish button

Applies the settings, and distributes the property values selected in the navigation frame to the destination service selected in the Distribute Property > Select Service window. When distribution starts, the Distribute Property > Progress Reports window opens.

This button is available only when at least one distribution service is selected in the Distribute Property > Select Service window, and properties are selected for distribution in the Distribute Property > Select Property window.

Property list area:

When you select a node in the contents area, this area lists the properties of the node. The properties that are displayed are described after the following reference note.

Reference note

When you select properties that are specific to an agent, the display items differ. For details about the items displayed when an agent specific property is selected, see 1.8.4(4) Distribute Property > Select Property window (distributing properties for which the number of nodes change).

Apply

Distributes properties of the selected service to multiple destination services.

When this check box is selected, the corresponding property is distributed to the services.

Name

Displays the names of properties.

Value

Displays the values set for the properties.

Description

Displays the description of a property.

Reference note

If you use the navigation frame or the method frame in the Services window while using the window for distributing properties, a confirmation message appears.

(3) Distribute Property > Progress Reports window

The Distribute Property > Progress Reports window is used to display the progress of the distribution processing.

The following figure shows the Distribute Property > Progress Reports window.

Figure 1‒126: Distribute Property > Progress Reports window

The following describes the displayed items:

OK button

Completes the distribution processing and clears the information frame. This button is inactive when batch processing starts. The button is activated in either of the following cases:

When the distribution processing has been completed

When the processing is canceled (the Stop button is clicked, after which distribution to the current service is completed)

Stop button

Stops the processing after completing distribution to the current service. The properties are not distributed to the next service.

This button is deactivated once it is clicked.

Message

The following character strings are displayed depending on the processing status.

Processing status

Line 1

Line 2

Distribution in progress

Now distributing properties...(number-of-distributed-services/number-of-services-to-be-distributed)

From distribution-source-service to distribution-target-service

Distribution canceled

Property distribution was stopped. (number-of-distributed-services/number-of-services-to-be-distributed)

Distribution completed

Property distribution has finished.

--#

#

Not displayed.

Progress bar:

The bar displays the progress of batch distribution for each service.

Distribution result list:

Displays the service names of the destination services to which property distribution has been completed, and the results. When property distribution is successful, Done appears in Property Distribution. If property distribution fails, Not done appears in Property Distribution.

Each time a distribution is completed, the corresponding service is displayed at the top of the list. The first service to which property distribution was completed is therefore displayed at the bottom of the list.

Reference note

While using the window for distributing properties, if you use the navigation frame or the method frame in the Services window, the process stops after distribution to a running service is completed, and a confirmation message appears.

(4) Distribute Property > Select Property window (distributing properties for which the number of nodes change)

Depending on the Performance Management product, there are properties for which the number of nodes might dynamically increase or decrease due to the addition or deletion of nodes in the Service Properties window. Such properties can also be distributed in the Distribute Property > Select Property window.

Depending on the Performance Management product, there are properties for which the number of nodes might dynamically increase or decrease due to the addition or deletion of nodes in the Service Properties window.

When you distribute, in a batch, properties for which the number of nodes change, the Distribute Property > Select Property window is displayed for distributing the tree structure.

Reference note

To distribute, in a batch, properties for which the number of nodes change, the versions of PFM - Manager and PFM - Web Console must be 08-11 or later.

The following figure shows an example of the Distribute Property > Select Property window when the number of nodes changes dynamically for the distribution of properties.

Figure 1‒127: Distribute Property > Select Property window (distributing properties for which the number of nodes change)

The following describes the displayed items:

Contents area:

Displays hierarchically the properties of the Agent Collector and Remote Monitor Collector services selected as the distribution source.

Cancel button

Cancels the operation, and clears the information frame.

< Back button

Returns to the Distribute Property > Select Service window.

Finish button

Applies the settings, and distributes the nodes and the properties selected in the navigation frame to the destination service selected in the Select Service window. When distribution starts, the Distribute Property > Progress Reports window opens.

This button is available only when a destination service is selected, and any of the following conditions is satisfied:

Properties for which Apply is selected exist.

Add or Delete is selected in Operation.

Delete nodes that only exist at the distribution destination is selected.

Property list area:

When you select a node in the contents area, nodes that can be added or removed from under that node are listed. The display items are as follows:

Name

Displays the names of nodes.

Operation

Use one of the following radio buttons to select the operation you want to perform on the node:

Update

Updates the properties of a node when the node exists in both the distribution source agent and the distribution destination agent, and the Apply check box is selected for properties in the Select Property window.

Add

Adds a node that exists in the distribution source agent, but does not exist in the distribution destination agent. For a node that exists in both the distribution destination agent and the distribution source agent, the selection status of the Apply check box in the Select Property window is ignored and all the properties of the node are updated.

Delete

Deletes a node that exists in both the distribution source agent and the distribution destination agent.

Delete nodes that only exist at the distribution destination

Deletes nodes that exist only in the distribution destination agent.

Reference note

Properties to be added to a node or to be updated or deleted can be manipulated in the same way as properties that are common to the agents.

1.9 Users window

The Users window is used to manage the Performance Management users. It enables you to create user accounts and to change account information. To display this window, in the navigation frame of any PFM - Web Console window, choose the Users tab.

Only a login user with the administrator user permission can display this window.

The following figure shows the Users window for PFM - Web Console.

Figure 1‒128: Users window

The following describes the displayed items:

Menu bar frame

Displays a menu that is common to all windows.

For details, see the description of the menu bar frame in 1.3 Main window.

Navigation frame

Displays hierarchically the user accounts registered as Performance Management users.

Except for the following items, the display items are the same as the items in the navigation frame of the Main window. For details, see 1.3 Main window.

Users tree

The root is Users. The second level contains the Management users, Ordinary users, and Business group ordinary users folders. The Business group ordinary users folder is displayed when the business group access control functionality is enabled.

Management users

This folder manages user accounts that have been registered as Performance Management users. When the Management users folder is expanded, the user accounts with administrator user permissions are displayed.

The Management users folder cannot be changed.

Ordinary users

This folder manages user accounts that have been registered as Performance Management users. When the Ordinary users folder is expanded, the user accounts with the general user permissions are displayed.

The Ordinary users folder cannot be changed.

Business group ordinary users

This folder manages the user accounts registered as Performance Management users. When the Business group ordinary users folder is expanded, the Business group ordinary users user accounts are displayed.

You cannot change the Business group ordinary users folder.

User account name

This is a user account that has been registered as a Performance Management user. It displays the user name in Performance Management. When a user account name is selected, a check mark appears.

Icons

An icon is displayed to the left of each component of the Users tree. For details about icons, see Table 1-9 Configuration component icons and their meaning.

These icons have the following meaning:

: Indicates the root.

: Indicates a user folder.

: Indicates a user.

Method frame

Displays the operations that can be executed on the users tree. The operation items that are displayed depend on the selected object.

New User

Creates a new user account. Choosing this item displays the New User window.

Copy

Copies an existing user account. Selecting this item displays the Copy window. To execute this operation, you must select a target user account in the navigation frame.

Edit

Edits existing user account information. Choosing this item displays the Edit window. The user account information that can be edited includes the password and the user permissions. To execute this operation, you must select a target user account in the navigation frame.

Delete

Deletes an existing user account. When this item is selected, a message box for confirming the deletion intention is displayed. To execute this operation, you must select a target user account in the navigation frame.

Information frame

Displays the results of the operation selected in the method frame.

1.9.1 Transitions from the Users window

The following shows the window transitions from the Users window:

Figure 1‒129: Window transitions from the Users window

1.9.2 New User window

The New User window is used to create a new Performance Management user. To display this window, in the Users window, in the method frame, choose New User.

The following shows the New User window.

Figure 1‒130: New User window

The following describes the displayed items:

OK button

Saves the settings you specified.

Cancel button

Cancels the operation, and clears the information frame.

User name

Specify a name for the new user account with 1 to 16 characters. The permitted characters are alphabetic characters (upper and lower case), numeric characters, and symbols (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ] \ ^ _ ` { | } ~ space). The alphabetic characters are not case sensitive.

Any leading and trailing spaces that are specified are deleted.

Password and Confirm password

Specify a new password by using 1 to 16 single-byte characters. The permitted characters are alphabetic characters (upper and lower case), numeric characters, and symbols (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ] \ ^ _ ` { | } ~ space). The alphabetic characters are case sensitive.

Any leading and trailing spaces that are specified are deleted.

Selection of authority and Assignment of business groups

Select the privilege you to set for the user account you create. Business group ordinary user is displayed when the business group access control functionality is enabled.

Management user

Ordinary user

Business group ordinary user

All business groups

This area is displayed when the business group access control functionality is enabled. It becomes available when Business group ordinary user is selected for Selection of authority and Assignment of business groups. The business groups to be assigned to the user account you create are listed.

Arrow buttons (/)

Use these buttons to move the displayed business groups between All business groups and Assigned business groups.

button

Moves a business group from All business groups to Assigned business groups.

button

Moves a business group from Assigned business groups to All business groups.

Assigned business groups

This area is displayed when the business group access control functionality is enabled. It becomes available when Business group ordinary user is selected for Selection of authority and Assignment of business groups. The business groups to be assigned to the user account you created are listed.

Important note

For Performance Management, it is recommended that a password consist of at least six characters and include a mixture of alphabetic characters, numeric characters, and symbols. If the password you enter is not consistent with these recommendations, such as a password consisting of only alphabetic characters, only numeric characters, or fewer than six characters, a confirmation message will be displayed. A message will also be displayed if the entered password is the same as your user name.

1.9.3 Copy window

The Copy window is used to create a copy of an existing user account. To display this window, in the Users window, in the method frame, choose Copy.

The following figure shows the Copy window.

Figure 1‒131: Copy window

The following describes the displayed items:

OK button

Saves the settings you specified.

Cancel button

Cancels the operation, and clears the information frame.

Copy-source user name

Displays the name of the copy source user account. You cannot edit this item.

User name

Specify a name for the new user account with 1 to 16 characters. The permitted characters are alphabetic characters (upper and lower case), numeric characters, and symbols (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ] \ ^ _ ` { | } ~ space). The alphabetic characters are not case sensitive.

Any leading and trailing spaces that are specified are deleted.

Password and Confirm password

Specify a new password by using 1 to 16 single-byte characters. The permitted characters are alphabetic characters (upper and lower case), numeric characters, and symbols (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ] \ ^ _ ` { | } ~ space). The alphabetic characters are case sensitive.

Any leading and trailing spaces that are specified are deleted.

Selection of authority and Assignment of business groups

Select the privilege you want to set for the user account you create. Business group ordinary user is displayed when the business group access control functionality is enabled.

Management user

Ordinary user

Business group ordinary user

All business groups

This area is displayed when the business group access control functionality is enabled. It becomes available when Business group ordinary user is selected for Selection of authority and Assignment of business groups. The business groups to be assigned to the user account you created are listed.

Arrow buttons (/)

Use these buttons to move the displayed business groups between All business groups and Assigned business groups.

button

Moves a business group from All business groups to Assigned business groups.

button

Moves a business group from Assigned business groups to All business groups.

Assigned business groups

This area is displayed when the business group access control functionality is enabled. It becomes available when Business group ordinary user is selected for Selection of authority and Assignment of business groups. The business groups assigned to the user account you created are listed.

Important note

For Performance Management, it is recommended that a password consist of at least six characters and include a mixture of alphabetic characters, numeric characters, and symbols. If the password you enter is not consistent with these recommendations, such as a password consisting of only alphabetic characters, only numeric characters, or fewer than six characters, a confirmation message will be displayed. A message will also be displayed if the entered password is the same as your user name.

1.9.4 Edit window

The Edit window is used to change information about an existing user account. To display this window, in the Users window, in the method frame, choose Edit.

The following figure shows the Edit window.

Figure 1‒132: Edit window

The following describes the displayed items:

OK button

Saves the settings you specified.

Cancel button

Cancels the operation, and clears the information frame.

User name

The name of a user account cannot be changed.

Password and Confirm password

Specify a new password by using 1 to 16 single-byte characters. The permitted characters are alphabetic characters (upper and lower case), numeric characters, and symbols (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ] \ ^ _ ` { | } ~ space). The alphabetic characters are case sensitive.

Any leading and trailing spaces that are specified are deleted.

Selection of authority and Assignment of business groups

You can change the privilege (see the following list) set for the user account. Business group ordinary user is displayed when the business group access control functionality is enabled.

Management user

Ordinary user

Business group ordinary user

All business groups

This area is displayed when the business group access control functionality is enabled. It becomes available when Business group ordinary user is selected for Selection of authority and Assignment of business groups. The business groups to be assigned to the user account you are editing are listed.

Arrow buttons (/)

Use these buttons to move the displayed business groups between All business groups and Assigned business groups.

button

Moves a business group from All business groups to Assigned business groups.

button

Moves a business group from Assigned business groups to All business groups.

Assigned business groups

This area is displayed when the business group access control functionality is enabled. It becomes available when Business group ordinary user is selected for Selection of authority and Assignment of business groups. The business groups assigned to the user account you are editing are listed.

Important note

For Performance Management, it is recommended that a password consist of at least six characters and include a mixture of alphabetic characters, numeric characters, and symbols. If the password you enter is not consistent with these recommendations, such as a password consisting of only alphabetic characters, only numeric characters, or fewer than six characters, a confirmation message will be displayed. A message will also be displayed if the entered password is the same as your user name.

2 Commands

This chapter describes the Performance Management commands.

The descriptive format and syntax rules for Performance Management commands are the same for both Windows and UNIX.

In Windows, a command is executed from the command prompt.

In UNIX, a command is executed from a control terminal.

Command specification method and the notations used in explaining the command syntax

This section describes the command descriptive format, including the command specification method and the notations used in explaining the command syntax.

Command specification method

The command specification format is shown as follows:

The items indicated by (1) and (2) are called options and arguments, respectively.

Notations used in command syntax explanations

The following table shows the notations used in the command syntax explanations:

Table 2‒1: Notations used in command syntax explanations

Notation

Explanation and example

|

(stroke)

Separates multiple items, any of which can be selected.

Example:

A|B|C means "A or B or C".

{ }

(curly braces)

Indicates that one of the items enclosed in the curly braces must be selected. The items are separated by the stroke (|)

Example:

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

[ ]

(square brackets)

Indicates optional items (items whose specification may be omitted).

Example:

[A] means that "A" may be specified if needed ("A" may be omitted if not required).

[B|C] means that "B" or "C" may be specified as needed or that "B" and "C" may both be omitted.

...

(ellipsis)

The item preceding the ellipsis can be specified as many times as needed. When an item is specified multiple times, the blank is used as the delimiter.

Example:

A B... means that "B" may be specified as many times as necessary following "A".

_

(underline)

Indicates the default value that is assumed by the system if all of the items surrounded by square brackets are omitted.

Example:

[A|B] means that the system will use "A" if neither A nor B is specified.

Wildcard characters

You can use wildcard characters in a command to specify multiple services or host names. The following two wildcard characters are supported:

*: Indicates a character string consisting of any number of any characters (including no characters).

?: Indicates any single character.

In UNIX, a wildcard character must be enclosed in double-quotation marks (such as "*"), so that it will not be analyzed by the shell.

About service IDs specified in commands

For details about service IDs specified in commands, see the appendix that describes service naming conventions in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Notes on commands

Notes common to all commands

Before executing a command, the current directory must be changed to the command's installation directory. For details about a command's installation directory, see the explanation for each command.

Notes about specifying the host and lhost options in a jpctool db command or jpctool service command

The following shows the specifications for the -host and -lhost options, and the corresponding target range when this command is executed:

jpctool db backup

jpctool db clear

jpctool db dump

jpctool service

When executing the command at a PFM - Manager host

If you execute the jpctool db command or jpctool service command at a PFM - Manager host and the PFM - Manager is in a logical host environment, you must specify that logical host in the -lhost option. For example, in the case of the system configuration shown in the figure below, the jpctool db command or jpctool service command is executed at logical host C, so -lhost C is specified. Note that if you omit the -lhost option, the command will be executed at physical host A.

To execute the jpctool db command or jpctool service command that targets a service on a specific host, specify the -host option. In this example, to execute the command on host D, you would specify -host D -lhost C.

When executing the command at a PFM - Agent or PFM - RM host

If you execute the jpctool db command or jpctool service command on a PFM - Agent or PFM - RM host, and the PFM - Agent or PFM - RM host is in a logical host environment, you must specify that logical host in the -lhost option. For example, for the system configuration shown in the figure below, the jpctool db command or jpctool service command is executed at logical host C, so -lhost C is specified.

Notes on execution of jpctool alarm commands

Event

The jpctool alarm inactive and jpctool alarm unbind commands that the manager executes to stop the monitoring that uses alarms are not synchronized with the completion of monitoring stoppage on the monitoring target agent.

Therefore, if you stop the monitoring that uses alarms and then stop the monitoring target system, JP1/PFM might detect the stoppage of the monitoring target system before detecting the completion of monitoring stoppage, and issue an unintended alarm.

How to avoid this event

If you want to stop the monitoring that uses alarms and then stop the monitoring target system, wait about 60 seconds# before stopping the monitoring target system, or ignore the alarm that might be issued when the monitoring target system is stopped.

Example:

Execute the jpctool alarm inactive or jpctool alarm unbind command to stop the monitoring that uses alarms.

Make the process pause for 60 seconds.

Stop the system being monitored by JP1/PFM.

#

This is a standard pause duration, so it may have to be varied depending on the system environment. If an unintended alarm is issued even with a pause, extend the length of the pause.

You must be careful about also the following jpctool alarm commands, because processing is not synchronized with the completion of the processing on the target agent.

jpctool alarm active

jpctool alarm bind

jpctool alarm copy

jpctool alarm delete

jpctool alarm import

Commands that cannot be executed with alarm commands

You cannot execute any alarm commands (commands beginning with jpctool alarm) on a machine on which the following commands are running:

List of commands that cannot be executed with alarm commands

jpcconf acc setup

jpcconf acc unsetup

jpcconf agent setup

jpcconf ha

jpcconf hc

jpcconf inst setup

jpcconf inst unsetup

jpcconf mgrhost

jpcconf stat

jpcspm start

jpcspm stop

jpctool alarm

jpctool db

jpc_start (executed when the OS starts)

jpc_stop (executed when the OS starts)

If you execute an alarm command in such a situation, the return value 4 is returned and the subsequent processing is not performed. Even if these commands target different hosts (a physical host and a logical host), if you execute the commands concurrently, the same result occurs.

For PFM - Manager 10-10-10 or later, if you execute an alarm command when the setting to suspend execution of the alarm command (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), the alarm command is executed after other executing commands finish.

For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini). Note that, when you set Alarm Command Wait Mode in a logical host environment, you must enable Alarm Command Wait Mode in the startup information file (jpccomm.ini) on both the active and standby physical hosts, instead of enabling Alarm Command Wait Mode in the startup information file under the environment directory.

Notes on commands that are executed in PFM - Web Console

This section describes the prerequisites, input format, and output format of the following commands that are executed in PFM - Web Console:

jpcrdef create

jpcrdef delete

jpcrdef output

jpcasrec update

jpcasrec output

jpcaspsv update

jpcaspsv output

jpcrpt

jpcmkkey

jpcprocdef create

jpcprocdef delete

jpcprocdef list

jpcprocdef output

Prerequisites for command execution

The following prerequisites apply to command execution:

Creating a parameter file to be specified in a command

To execute a command that requires a parameter file as an argument, you must have created the parameter file in advance.

For details about how to specify a parameter file, see Command input method. For details about the parameters that are specified in a parameter file, see the description of the parameter file format in the explanations of the applicable commands.

Checking the <logging> and <vsa> tags that are set in the config.xml# file

Make sure that the <logging> and <vsa> tags are set in the config.xml# file. These tags are required. To set the tags, see the sample config.xml# file.

Checking the operating status of PFM - Manager

PFM - Manager must be running when a command executes.

Checking the operating status of PFM - Agent or PFM - RM

To execute a command related to the Store database or a command that outputs report results, the appropriate PFM - Agent or PFM - RM must be running.

Command execution permissions

To execute commands, the OS user must have the Administrators permissions.

Creating an authentication key file

Before you can execute commands, you must create an authentication key file for PFM - Manager. You use the jpcmkkey command to create the authentication key file.

#

For an example of a config.xml file, see E. Initialization File (config.xml).

Command input method

This subsection explains how to describe a parameter file that is specified in a command.

How to describe a parameter file

The following explains how to describe a parameter file that is specified in a command argument:

Create the parameter file in XML format.

After specifying the XML version and encoding, enclose the parameters in <pr-cli-parameters> tags.

For details about the parameters to be specified, see the parameter format for each applicable command.

To use an XML-format control character (such as <) as part of a value, the syntax rules stipulated in the XML specifications must be observed.

For example, < and > must be coded as &lt; and &gt;, respectively.

In the case of a value that is specified by selecting from a specified token that is stipulated in the command parameter file specifications, such as a field ID, record ID, date-range, or report-interval, you may use all upper-case letters or all lower-case letters unless otherwise restricted explicitly. For details about the definitions of values that are specified in parameters, see the description of the parameter file format or DTD file for each applicable command.

A parameter that accepts TRUE also accepts true, and a parameter that accepts FALSE also accepts false.

An element or attribute whose value is blank is treated as being omitted. Leading and trailing spaces in an element or attribute value are ignored.

An error results if a non-printable character is specified as an element or attribute.

The DOCTYPE declaration is fixed in a parameter file. Make sure that the DOCTYPE declaration in the parameter file contains the name of the DTD file that defines the parameter descriptions. The following is an example of a DOCTYPE declaration:

<!DOCTYPE pr-cli-parameters SYSTEM "DTD-file-name">

The following table lists the DTD files supported by the commands:

Table 2‒2: DTD files supported by commands

Command name

DTD file name

jpcrdef create

rdef_create_params.dtd

rdef_params.dtd

jpcrdef delete

rdef_create_params.dtd

rdef_delete_params.dtd

rdef_output_params.dtd

rdef_params.dtd

jpcrdef output

rdef_create_params.dtd

rdef_output_params.dtd

rdef_params.dtd

jpcasrec update

asrec_params.dtd

jpcasrec output

asrec_params.dtd

jpcaspsv update

aspsv_params.dtd

jpcaspsv output

aspsv_params.dtd

jpcrpt

rpt_params.dtd

jpcprocdef create

processmonitoring_params.dtd

jpcprocdef output

processmonitoring_params.dtd

You can specify the root directory by specifying / in the parent-folder attribute. To specify a directory under the root directory, specify a forward slash immediately before the directory name, such as /Directory1. Similarly, to specify a directory under Directory1, specify a directory path that uses / to connect each directory name, such as /Directory1/Directory2.... Specifying User Reports or System Reports in the / root directory results in an error.

If a specified value is outside the range denoted in Parameter file format, a parameter file error results.

The following table describes pr-cli-parameters:

Table 2‒3: Description of pr-cli-parameters

Type

Description

Description

Root tag for PFM - Web Console command input

Specifiable value

None

Omissible

No

Attribute

ver

DTD file version. If the value is outside the supported range, a parameter file error results. If the specification is omitted, an error results. For details about the supported range, see each DTD file.

Parent element

None

Child element

report-definitions

Root tag for report definition

agent-store-db-record-definition

Root tag for Store database recording method change definition information

agent-store-db-preserve-definition

Root tag for the Store database storage condition change definition information

launch-report

Root tag for the report output definition information

launch-registration-report

Root tag for the registered report output definition information

launch-combination-bookmark

Root tag for the combination bookmark output definition information

application-definition

Root tag for the application definition information

An example of the coding for a parameter file is shown below. Specify the report definition in the portion that is between the sections shown in bold type.

Coding example of parameter file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rdef_params.dtd">
<pr-cli-parameters ver="0110">
<report-definitions>
<report-definition> ....report-definition....</report-definition>
<report-definition> ....report-definition....</report-definition>
</report-definitions>
</pr-cli-parameters >

Command output method

Detailed information about a command's processing is output to the standard output, standard error output, and trace log file. The following table describes the output destinations for this detailed information:

Table 2‒4: Output of detailed information

Item

Output destination

Execution results

Standard output

Messages

Standard error output

Trace log

command-name_processing-type_log#.log ( where # is the log file number [from 1 to the number of generated log files]) is output under the log output directory specified in the initialization file. For example, the log name is jpcrdef_create_log1.log for the report creation command.

For the jpcrpt command, command-name_process-ID_log#.log (where # is the log file number [from 1 to the number of generated log files]) is output under the log output directory specified in the initialization file. When the process ID is 100, the log name is jpcrpt_100_log1.log.

Each time the command is executed, the total size of the log files is calculated. When the upper limit is exceeded, the file with the oldest update date is deleted. Note, however, that only those files updated previous to the number of days specified for logFileRetention in the initialization file after the command is started are deleted. The upper limit for size is determined by multiplying logFileSize by logFileNumber in config.xml.

For the jpcmkkey command, jpcmkkey_log#.log (where # is the log file number [from 1 to the number of generated log files]) is output under the log output directory specified in the initialization file.

Example of standard output

The command name, host name/IP address of PFM - Manager for the connection destination, PFM - Manager connection time, and PFM - Manager disconnection time are added as title and end rows common to all commands.

The example shown below shows the standard output when three reports are defined with the jpcrdef create command, two reports definitions are created, and one report definition result in an error.

Example of execution results output

jpcrdef create connected to hostname at yyyy MM dd HH:MM:SS.mmm
create result OK  : report-definition-directory-path-1/report-definition-name-1
create result OK  : report-definition-directory-path-2/report-definition-name-2
create result ERR : report-definition-directory-path-3/report-definition-name-3
cause-of-error
jpcrdef create disconnected at yyyy MM dd HH:MM:SS.mmm

Legend:

yyyy MM dd

Year, month, and day.

The display format changes according to the locale. For details, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

HH:MM:SS.mmm

Hour, minute, second, and millisecond.

report-definition-directory-path-1 through report-definition-directory-path-3

Names of the directories containing the report definitions set in the parent-folder attribute of the report-definition parameter.

report-definition-name-1 through report-definition-name-3

Names of the report definitions set in the name attribute of the report-definition parameter.

For details about the log specifications, see 3. Log Information Output by Performance Management.

Help reference option

Specifying the -h option in a command displays a Help for the command. For example, to view the Help for the jpcrdef command, enter the following:

jpcrdef   -h

The following shows the Help that is provided for the jpcrdef command:

Usage: jpcrdef <subcmd> [ <option>... ] <parameter file>
    <subcmd> Mandatory. Specify one of subcommands listed below:
        create          Creates report definition(s)
        delete          Deletes report definition(s)
        output          Outputs report definition(s)
    <option> Specify optionals after each extension listed below.
        -o <outputfile> Output file is required only if <subcmd>
                        is 'output'
        -mx             Specify maximum heap size from 1 to
                        1024 MB
                        Example: -mx 64. Default for both is 64MB.
        -ms             Specify minimum heap size from 1 to
                        1024 MB
                        Example: -ms 32. Default for both is 32MB.
        -y              Only used 'delete' <subcmd>. Assume a
                        yes response to
                        all questions asked by jpcrdef.
        -dateformat <pattern>
                        Specifiable when <subcmd> is 'create' or
                        'output'.
                        The specified <pattern> entry determines
                        the date format
                        for I/O in the <expression> tag.
                        Specifiable <pattern> entries are
                        'pattern-ddMMyyyy', 'pattern-MMddyyyy',
                        or 'pattern-yyyyMMdd'.
                        -dateseparator <pattern>
                        Specifiable when <subcmd> is 'create' or
                        'output'.
                        The specified <pattern> entry determines
                        the date separator
                        for I/O in the <expression> tag.
                        Specifiable <pattern> entries are
                        'space', 'slash', 'hyphen', or 'period'.
    <parameter file>    Mandatory. Specify parameter file

If a command's first argument is the -h option, the system ignores the remainder of the specification and displays the command's Help. A command's Help is also displayed when the command line includes an invalid specification.

Concurrent command execution

The following commands (that is, commands other than the jpcrpt command) cannot be executed at the same time as another instance of the same command or as other commands:

jpcrdef create

jpcrdef delete

jpcrdef output

jpcasrec update

jpcasrec output

jpcaspsv update

jpcaspsv output

jpcmkkey

jpcprocdef create

jpcprocdef delete

jpcprocdef list

jpcprocdef output

Performance Management user permissions required for command execution

To use the GUI to change report definitions and collection items, you must first log into PFM - Manager (authenticated). This authentication is also required to execute commands. This authentication is also required to execute commands. Authentication determines whether the user has permissions to execute commands in the Performance Management system.

For command authentication, you must have created an authentication key file in advance and the key file is read during command execution; you do not enter a user name or password during command execution. You use the jpcmkkey command to create the key file. One key file is created for each host. Command execution from the host is permitted on the basis of the user names/passwords set in the key file. One key file is used by all commands executed from the host.

The following table shows the Performance Management user permissions required for command execution:

Table 2‒5: Performance Management user permissions required for command execution

Command

Required Performance Management user permissions#

jpcrdef create

General user permission or administrator user permission

jpcrdef delete

General user permission or administrator user permission

jpcrdef output

General user permission or administrator user permission

jpcasrec update

Administrator user permission

jpcasrec output

Administrator user permission

jpcaspsv update

Administrator user permission

jpcaspsv output

Administrator user permission

jpcrpt

General user permission or administrator user permission

jpcmkkey

None

jpcprocdef create

Administrator user permission

jpcprocdef delete

Administrator user permission

jpcprocdef list

Administrator user permission

jpcprocdef output

Administrator user permission

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Commands

The Performance Management commands can be classified into the following types: commands that can be executed from PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base, and commands that can be executed from PFM - Web Console.

The individual commands are described in detail in this section, in alphabetical order of the command names.

List of Performance Management commands (PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base)

The following table lists and describes the Performance Management commands:

Table 2‒6: Performance Management commands (PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base)

Command name

Function

Hosts that can execute the command

Required execution permission

Windows

UNIX

jpccfgbackup

Create a backup file of the definition information for the Performance Management program on the local host.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Backup Operators#4

Root user

jpcconf acc display

Displays the settings of the common account information.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf acc setup

Creates and updates the common account information.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf acc unsetup

Deletes the common account information.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf agent setup

Executes the additional setup of a new PFM - Agent or PFM - RM.#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf agttree export

Exports the Agents tree definition to a file.

PFM - Manager

Administrators

Root user

jpcconf agttree import

Imports the Agents tree definition from a file.

PFM - Manager

Administrators

Root user

jpcconf bgdef check

Checks the contents of the business group definition file.

PFM - Manager

Administrators

Root user

jpcconf bgdef delete

Deletes business group definition information.

PFM - Manager

Administrators

Root user

jpcconf bgdef display

Displays business group definitions.

PFM - Manager

Administrators

Root user

jpcconf bgdef export

Exports business group definition information to a file.

PFM - Manager

Administrators

Root user

jpcconf bgdef import

Imports business group definition information from a file.

PFM - Manager

Administrators

Root user

jpcconf bgdef list

Displays a list of business group names.

PFM - Manager

Administrators

Root user

jpcconf ha export

Exports to a file the logical host environment settings for a Performance Management program.#1

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf ha import

Imports to the standby node a logical host environment information file for a Performance Management program.#1

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf ha list

Displays logical host environment settings for a Performance Management program.#1

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf ha setup

Creates a logical host environment for a Performance Management program.#1

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf ha unsetup

Deletes a logical host environment for a Performance Management program.#1

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf hc disable

Disables the health check function.

PFM - Manager

Administrators

Root user

jpcconf hc display

Displays the status of the health check function.

PFM - Manager

Administrators

Root user

jpcconf hc enable

Enables the health check function.

PFM - Manager

Administrators

Root user

jpcconf host hostmode

Updates or displays the method for acquiring the physical host name for the Performance Management program.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf host hostname

Changes the host name information for the operating environment of the Performance Management program.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf im disable

Disables the JP1/IM monitored object linkage function.#1

PFM - Manager

Administrators

Root user

jpcconf im enable

Enables the JP1/IM monitored object linkage function.#1

PFM - Manager

Administrators

Root user

jpcconf inst list

Displays the names of instances set up by a PFM - Agent or PFM - RM that can start multiple services on a single host.#1

PFM - Agent

PFM - RM

None

None

jpcconf inst setup

Creates or updates an instance environment for a PFM - Agent or PFM - RM that can start multiple services on a single host.#1

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf inst unsetup

Deletes an instance environment for a PFM - Agent or PFM - RM that can start multiple services on a single host.#1

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf ipv6 disable

Disables the IPv6 usage settings.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf ipv6 display

Displays the IPv6 usage settings.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf ipv6 enable

Enables the IPv6 usage settings.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf mgrhost define

Sets or changes the host name of PFM - Manager for the connection destination (Name Server service).#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators#2

root user#2

jpcconf mgrhost display

Displays the host name of PFM - Manager for the connection destination (Name Server service).#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators#2

Root user#2

jpcconf ov enable

Sets up the NNM linkage facility.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf ov disable

Performs unsetup of the NNM linkage facility setup.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf port define

Sets port numbers used with Performance Management.#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf port list

Displays port numbers used with Performance Management.#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf primmgr notify

Specifies the PFM - Manager on the execution host as the primary host, and notifies all the hosts in the PFM system of the host name of the primary PFM - Manager host.

PFM - Manager

Administrators

Root user

jpcconf prodname disable

Disables settings for the product name display functionality.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf prodname display

Displays settings for the product name display functionality.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf prodname enable

Enables settings for the product name display functionality.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf stat disable

Disables the status management function.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf stat display

Displays the status of the status management function.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf stat enable

Enables the status management function.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcconf target display

Displays the monitoring target settings.

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Administrators

Root user

jpcconf target list

Displays a list of monitoring targets.

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Administrators

Root user

jpcconf target setup

Creates or updates a monitoring target.

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Administrators

Root user

jpcconf target unsetup

Deletes a monitoring target.

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Administrators

Root user

jpcimevt

Registers a JP1 event in the event server and sends the registered event to JP1/IM.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

None

None

jpcparamdump

Collects the setting information of the Performance Management program on the local host.

PFM - Manager

PFM - Base

Administrators

Root user

jpcras

Collects information about PFM - Manager, PFM - Agent, PFM - RM, or PFM - Base, as well as OS information.#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcspm start

Starts the service of a Performance Management program at the local host.#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpcspm stop

Stops the service of a Performance Management program at the local host.#1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpctool alarm active

Enables a disabled alarm.

PFM - Manager

Administrators

Root user

jpctool alarm bind

Binds an alarm table to an agent.

PFM - Manager

Administrators

Root user

jpctool alarm check

Checks the validity of the syntax and definitions in the alarm definition file.

PFM - Manager

Administrators

Root user

jpctool alarm copy

Copies an alarm table or alarm.

PFM - Manager

Administrators

Root user

jpctool alarm delete

Deletes an alarm table or alarm.

PFM - Manager

Administrators

Root user

jpctool alarm export

Exports an alarm definition file.

PFM - Manager

Administrators

Root user

jpctool alarm import

Imports an alarm definition file.

PFM - Manager

Administrators

Root user

jpctool alarm inactive

Disables an enabled alarm.

PFM - Manager

Administrators

Root user

jpctool alarm list

Displays alarm table definition information.

PFM - Manager

Administrators

Root user

jpctool alarm unbind

Unbinds an alarm table.

PFM - Manager

Administrators

Root user

jpctool config mgrexport

Exports the definition information files of the PFM - Manager in a multiple-monitoring environment.

PFM - Manager

Administrators

Root user

jpctool config mgrimport

Imports the definition information files of the PFM - Manager in a multiple-monitoring environment.

PFM - Manager

Administrators

Root user

jpctool config sync

Synchronizes configuration information among the PFM - Manager, PFM - Agent, and PFM - RM hosts.

PFM - Manager

Administrators

Root user

jpctool db backup

Creates a backup file for the data stored in the Master Store, Agent Store, or Remote Monitor Store service database.#1, #3

PFM - Manager

PFM - Agent (can only be executed when the -alone option or -direct option is specified)

PFM - Base (can only be executed when the -direct option is specified)

PFM - RM (can only be executed when the -alone option or -direct option is specified)

Administrators

Backup Operators#4

Root user

jpctool db clear

Deletes the data stored in the Master Store, Agent Store, or Remote Monitor Store service database.#1

PFM - Manager

Administrators

Backup Operators#4

Root user

jpctool db dump

Exports data from the Master Store, Agent Store, or Remote Monitor Store service database to a text file.#1, #3

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

None

None

jpctool db restore

Restores the Master Store, Agent Store, or Remote Monitor Store service database that was backed up by the jpctool db backup command.#1

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Backup Operators#4

Root user

jpctool monitor list

Displays the monitoring suspension statuses and settings for the entire Performance Management system

PFM - Manager

Administrators

Root user

jpctool monitor resume

Resumes monitoring.

PFM - Manager

Administrators

Root user

jpctool monitor status

Displays the current monitoring suspension statuses and settings for the command execution host.

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Administrators

Root user

jpctool monitor suspend

Suspends monitoring.

PFM - Manager

Administrators

Root user

jpctool service delete

Deletes the service information for an agent registered in Performance Management.#1

PFM - Manager

Administrators

Backup Operators#4

Root user

jpctool service list

Displays the service configuration and status of a Performance Management program.#1, #3

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

None

None

jpctool service register

Re-registers into Performance Management the service information for a deleted Performance Management program.#1

PFM - Manager

Administrators

Backup Operators#4

Root user

jpctool service sync

Synchronizes the service information registered in PFM - Manager with the service information registered in PFM - Web Console.

PFM - Manager

Administrators

Root user

Legend:

The column headed Hosts that can execute the command assumes the following product installations on the host:

PFM - Manager host

A host on which only PFM - Manager is installed, or host on which PFM - Manager and PFM - Agent or PFM - RM are installed

PFM - Agent host

A host on which PFM - Base and PFM - Agent are installed

PFM - Base host

Only PFM - Base is installed on the host.

PFM - RM host

A host on which PFM - Base and PFM - RM are installed

#1

If this command's execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

#2

No execution permission is required to simply display the host name of PFM - Manager for the connection destination (Name Server service).

#3

Some functions and options are unavailable when the command is executed in a network environment that uses both IPv6 and IPv4.

#4

In Windows Server 2008 or Windows Server 2012, there are commands that can be executed by members of the Backup Operators group.

List of commands that correspond to Store 2.0 functions (PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base)

The following table lists the commands that correspond to the functions of Store 2.0.

Table 2‒7: Commands corresponding to the functions of Store 2.0 (PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base)

Command name

Function

Hosts that can execute the command

Required execution permission

Windows

UNIX

jpcconf db define

Changes and displays the settings of the Store service.

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpcconf db display

Displays information about the Store service or the backup data.

Checks the version of Store (1.0 or 2.0).

PFM - Manager

PFM - Agent

PFM - Base(executable only when the -d option is specified)

PFM - RM

Administrators

Root user

jpcconf db vrset

Changes the Store database version.

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpctool db dmconvert

Converts the data model of the backup data.

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

jpctool db import

Imports backup data to the Store database.

PFM - Manager

PFM - Agent

PFM - RM

Administrators

Root user

List of Performance Management commands (PFM - Web Console)

The following table lists and describes the Performance Management commands:

Table 2‒8: Performance Management commands (PFM - Web Console)

Command name

Function

Hosts that can execute the command

Required execution permission

Windows

UNIX

jpcaspsv output

Outputs definition information for the Store database storage conditions.

PFM - Web Console

Administrators

Root user

jpcaspsv update

Changes definition information for the Store database storage conditions.

PFM - Web Console

Administrators

Root user

jpcasrec output

Outputs definition information for the Store database recording method.

PFM - Web Console

Administrators

Root user

jpcasrec update

Changes definition information for the Store database recording method.

PFM - Web Console

Administrators

Root user

jpcmkkey

Creates an authentication key file required for command execution in PFM - Web Console.

PFM - Web Console

Administrators

Root user

jpcprocdef create

Creates or edits application definitions in the process monitoring settings.

PFM - Web Console

Administrators

Root user

jpcprocdef delete

Deletes application definitions in the process monitoring settings.

PFM - Web Console

Administrators

Root user

jpcprocdef list

Lists the names of application definitions in the process monitoring settings.

PFM - Web Console

Administrators

Root user

jpcprocdef output

Outputs the contents of the application definitions in the process monitoring settings.

PFM - Web Console

Administrators

Root user

jpcrdef create

Registers new report definitions.

PFM - Web Console

Administrators

Root user

jpcrdef delete

Deletes existing report definitions.

PFM - Web Console

Administrators

Root user

jpcrdef output

Outputs existing report definitions.

PFM - Web Console

Administrators

Root user

jpcrpt

Outputs a report displayed on PFM - Web Console to a batch report in CSV or HTML format.

PFM - Web Console

Administrators

Root user

jpcwagtsetup

Registers a new PFM - Agent or PFM - RM in PFM - Web Console.

PFM - Web Console

Administrators

Root user

jpcwbackup

Creates a backup file of PFM - Web Console definition information.

PFM - Web Console

Administrators

Backup Operators

Root user

jpcwras

Collects PFM - Web Console information.

PFM - Web Console

Administrators

Root user

jpcwstart

Starts the PFM - Web Console service.

PFM - Web Console

Administrators

Root user

jpcwstop

Stops the PFM - Web Console service.

PFM - Web Console

Administrators

Root user

Command installation directories

The commands to be used for operating Performance Management are classified into the types described below, and the directories to install the commands vary by the command type.

Table 2‒9: PFM - Manager and PFM - Base commands

OS

Command installation directory

Windows

PFM-Manager-or-PFM-Base-installation-folder\tools\

UNIX

/opt/jp1pc/tools/

Table 2‒10: PFM - Web Console commands

OS

Command installation directory

Windows

PFM-Web-Console-installation-folder\tools\

UNIX

/opt/jp1pcwebcon/tools/

For details on which type is applicable to each command, see the description of the command.

jpcaspsv output

Format

jpcaspsv output     [-mx maximum-heap-size]
                    [-ms initial-heap-size]
                     -o output-file
                     service-ID

Function

The jpcaspsv output command connects to an agent to acquire definitions related to the storage conditions of the Store database and outputs the definitions in XML format. You can specify the obtained output file as an input file for the jpcaspsv update command.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-o output-file

Specifies the name of an XML-format file to which the execution results are to be output. This can be an absolute file path name, relative file path name, or file name. If the specified file name is not the absolute file path name, the command assumes the current directory as the reference directory (if the specified directory does not exist, an error results).

service-ID

Specifies the service ID of the target agent. Wildcard characters cannot be used. Conditions for the specified value are as follows:

4 to 258 characters

The first character specifies the product ID of the agent (for details about product IDs, see the PFM - Agent or PFM - RM manuals).

The second character specifies S (Agent Store or Remote Monitor Store).

Notes

The command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication. For details about the service ID, see the PFM - Agent or PFM - RM manuals.

If the specified service ID is not for an agent product, an error results.

Definition information that cannot be updated is output as comments in the output file.

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

Creation of the output file failed.

5

The parameters cannot be analyzed because they do not match the DTD file.

10

Updating of at least one Store database definition failed.

11

Authentication processing for login to PFM - Manager failed. Alternatively, the user specified at authentication does not have execution permission.

100

The environment is invalid.

200

A memory error occurred.

202

A file access error occurred.

222

A communication processing error occurred.

255

An unexpected error occurred.

Usage example

This example outputs to a parameter file (aspsv_output.xml) definition information for the Store database recording method for the PFM - Agent whose service ID is TS1host1:

jpcaspsv  output  -o aspsv_output.xml  TS1host1

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

An example of the standard output is shown below. It displays the execution results (OK or ERR) for the service ID specified in the argument.

Example of standard output

jpcaspsv output connected to hostname at yyyy MM dd HH:MM:SS.mmm
output result  OK  : TS1host1
jpcaspsv output disconnected at yyyy MM dd HH:MM:SS.mmm

Output file

An example of a file output by this command is shown below.

Example of output file

Output file example (when the Store version is 1.0)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "aspsv_params.dtd">
<pr-cli-parameters ver="0110">
<agent-store-db-preserve-definition>
    <service id="TS1host1">
        <product-interval>
            <minute-drawer>month</minute-drawer>
            <hour-drawer>month</hour-drawer>
            <day-drawer>month</day-drawer>
            <week-drawer>month</week-drawer>
            <month-drawer>month</month-drawer>
            <!-- year-drawer : Year -->
        </product-interval>
        <product-detail>
            <detail-record id="PD" max-rec="20000"/>
            <detail-record id="PD_THRD" max-rec="20000"/>
            <detail-record id="PD_ADRS" max-rec="20000"/>
            <detail-record id="PD_PDI" max-rec="20000"/>
            <detail-record id="PD_PEND" max-rec="20000"/>
            <detail-record id="PD_THD" max-rec="20000"/>
            <detail-record id="PD_IMAG" max-rec="20000"/>
            <detail-record id="PD_PAGF" max-rec="20000"/>
            <detail-record id="PD_GEND" max-rec="20000"/>
            <detail-record id="PD_SVC" max-rec="20000"/>
            <detail-record id="PD_DEV" max-rec="20000"/>
            <detail-record id="PD_ELOG" max-rec="20000"/>
        </product-detail>
        <product-log>
            <log-record id="PL" max-rec="20000"/>
            <log-record id="RM" max-rec="20000"/>
        </product-log>
    </service>
</agent-store-db-preserve-definition>
</pr-cli-parameters>

Output file example (when the Store version is 2.0)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "aspsv_params.dtd">
<pr-cli-parameters ver="0110">
<agent-store-db-preserve-definition>
    <service id="TS1host1">
        <ex-product-interval>
            <ex-interval-record id="PI">
                <minute-drawer-days period="10"/>
                <hour-drawer-days period="10"/>
                <day-drawer-weeks period="10"/>
                <week-drawer-weeks period="10"/>
                <month-drawer-months period="10"/>
                <!-- year-drawer-years period="10" -->
            </ex-interval-record>
            <ex-interval-record id="PI_LOGD">
                <minute-drawer-days period="10"/>
                <hour-drawer-days period="10"/>
                <day-drawer-weeks period="10"/>
                <week-drawer-weeks period="10"/>
                <month-drawer-months period="10"/>
                <!-- year-drawer-years period="10" -->
            </ex-interval-record>
        </ex-product-interval>
        <ex-product-detail>
            <ex-detail-record id="PD" period="10"/>
            <ex-detail-record id="PD_THRD" period="10"/>
            <ex-detail-record id="PD_ADRS" period="10"/>
            <ex-detail-record id="PD_PDI" period="10"/>
            <ex-detail-record id="PD_PEND" period="10"/>
        </ex-product-detail>
        <ex-product-log>
            <ex-log-record id="PL" period="10"/>
            <ex-log-record id="RM" period="10"/>
        </ex-product-log>
    </service>
</agent-store-db-preserve-definition>
</pr-cli-parameters>

jpcaspsv update

Format

jpcaspsv update      [-mx maximum-heap-size]
                     [-ms initial-heap-size]
                      input-file

Function

The jpcaspsv update command connects to an agent and changes the definitions related to the storage conditions of the Store database. The command acquires the new storage condition definition information from the XML-format parameter file that is specified as a command line argument.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

input-file

Specifies the XML-format parameter file that is to be used to change the Store database storage condition definition information. This parameter file must be created according to the Parameter file format described below. You can specify the absolute file path name, relative file path name, or file name. When the name is not the absolute file path, the command assumes the current directory.

Parameter file format

XML tag specifications

agent-store-db-preserve-definition

Type

Description

Description

Root tag for the Store database storage condition change definition information

Specifiable value

None

Omissible

No

Attribute

None

Parent element

pr-cli-parameters

Child element

service (can be specified more than once)

service

Type

Description

Description

Specifies the service that identifies the agent.

Specifiable value

None

Omissible

No

Attribute

id

Service ID (4 to 258 characters)

The first character specifies the product ID of the agent. For details about the product ID, see the PFM - Agent or PFM - RM manuals.

The second character specifies S (Agent Store or Remote Monitor Store).

Parent element

agent-store-db-preserve-definition

Child element#

product-interval (can be specified only once per service or can be omitted)

product-detail (can be specified only once per service or can be omitted)

product-log (can be specified only once per service or can be omitted)

ex-product-interval (can be specified only once per service or can be omitted)

ex-product-detail (can be specified only once per service or can be omitted)

ex-product-log (can be specified only once per service or can be omitted)

#

If you specify child elements, specify them in the order listed above.

product-interval

Type

Description

Description

Specifies the PI record retention period.

The condition for the target Store database is either of the following:

Version 08-00 or earlier

Version 08-11 or later and Store 1.0

Specifiable value

None

Omissible

Yes (when omitted, product-interval is not updated)

Attribute

None

Parent element

service

Child element#

minute-drawer (can be specified only once per product-interval or can be omitted)

hour-drawer (can be specified only once per product-interval or can be omitted)

day-drawer (can be specified only once per product-interval or can be omitted)

week-drawer (can be specified only once per product-interval or can be omitted)

month-drawer (can be specified only once per product-interval or can be omitted)

#

If you specify child elements, specify them in the order listed above.

minute-drawer

Type

Description

Description

Specifies the PI record retention period in minutes.

Specifiable value

Alphanumeric characters that are not case sensitive.

Permitted values are as follows:

minute: 1 minute

hour: 1 hour

day: 1 day

n days: n days (n: 2 to 6)

week: 1 week

month: 1 month

year: 1 year

Omissible

Yes (when the parameter is omitted, minute-drawer is not updated)

Attribute

None

Parent element

product-interval

Child element

None

hour-drawer

Type

Description

Description

Specifies the PI record retention period in hours.

Specifiable value

Alphanumeric characters that are not case sensitive.

Permitted values are as follows:

hour: 1 hour

day: 1 day

n days: n days (n: 2 to 6)

week: 1 week

month: 1 month

year: 1 year

Omissible

Yes (when the parameter is omitted, hour-drawer is not updated)

Attribute

None

Parent element

product-interval

Child element

None

day-drawer

Type

Description

Description

Specifies the PI record retention period in days.

Specifiable value

Alphanumeric characters that are not case sensitive.

Permitted values are as follows:

day: 1 day

n days: n days (n: 2 to 6)

week: 1 week

month: 1 month

year: 1 year

Omissible

Yes (when the parameter is omitted, day-drawer is not updated)

Attribute

None

Parent element

product-interval

Child element

None

week-drawer

Type

Description

Description

Specifies the PI record retention period in weeks.

Specifiable value

Alphanumeric characters that are not case sensitive.

Permitted values are as follows:

week: 1 week

month: 1 month

year: 1 year

Omissible

Yes (when the parameter is omitted, week-drawer is not updated)

Attribute

None

Parent element

product-interval

Child element

None

month-drawer

Type

Description

Description

Specifies the PI record retention period in months.

Specifiable value

Alphanumeric characters that are not case sensitive.

Permitted values are as follows:

month: 1 month

year: 1 year

Omissible

Yes (when the parameter is omitted, month-drawer is not updated)

Attribute

None

Parent element

product-interval

Child element

None

product-detail

Type

Description

Description

Specifies the number of PD records that can be stored.

The condition for the target Store database is either of the following:

Version 08-00 or earlier

Version 08-11 or later and Store 1.0

Specifiable value

None

Omissible

Yes (when the parameter is omitted, product-detail is not updated)

Attribute

None

Parent element

service

Child element

detail-record (can be specified only once per PD record or can be omitted)

detail-record

Type

Description

Description

Specifies the maximum number of PD records that can be stored.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, detail-record is not updated)

Attribute

id

PD record ID (for the record ID, see the PFM - Agent or PFM - RM manuals. This attribute cannot be omitted.)

max-rec

0 to 2,147,483,647 (cannot be omitted)

Parent element

product-detail

Child element

None

product-log

Type

Description

Description

Specifies the maximum number of PL records that can be stored.

The condition for the target Store database is either of the following:

Version 08-00 or earlier

Version 08-11 or later and Store 1.0

Specifiable value

None

Omissible

Yes (when the parameter is omitted, product-log is not updated)

Attribute

None

Parent element

service

Child element

log-record (can be specified only once per PL record or can be omitted)

log-record

Type

Description

Description

Specifies the maximum number of PL records that can be stored.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, log-record is not updated)

Attribute

id

PL record ID (for the record ID, see the PFM - Agent or PFM - RM manuals. This attribute cannot be omitted.)

max-rec

0 to 2,147,483,647 (cannot be omitted)

Parent element

product-log

Child element

None

ex-product-interval

Type

Description

Description

Specifies the PI record retention period.

The condition for the target Store database is as follows:

Version 08-11 or later and Store 2.0

Specifiable value

None

Omissible

Yes (when the parameter is omitted, ex-product-interval is not updated)

Attribute

None

Parent element

service

Child element

ex-interval-record (can be specified only once per PI record or can be omitted)

Note: When you specify this tag, set the ver attribute of pr-cli-parameters to 0110 or later.

ex-interval-record

Type

Description

Description

Specifies the PI record retention period.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, ex-interval-record is not updated)

Attribute

id

PI record ID

For details about the PI record ID, see the PFM - Agent or PFM - RM manuals.

You cannot omit id.

Parent attribute

ex-product-interval

Child attribute#

minute-drawer-days (can be specified only once per ex-interval-record or can be omitted)

hour-drawer-days (can be specified only once per ex-interval-record or can be omitted)

day-drawer-weeks (can be specified only once per ex-interval-record or can be omitted)

week-drawer-weeks (can be specified only once per ex-interval-record or can be omitted)

month-drawer-months (can be specified only once per ex-interval-record or can be omitted)

# If you specify child elements, specify them in the order listed above.

minute-drawer-days

Type

Description

Description

Specifies the PI record retention period in minutes.

Specify the number of days. You can specify a maximum of 366 days (one year).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, minute-drawer-days is not updated)

Attribute

period

0 to 366 (cannot be omitted)

Parent element

ex-interval-record

Child element

None

hour-drawer-days

Type

Description

Description

Specifies the PI record retention period in hours.

Specify the number of days. You can specify a maximum of 366 days (a year).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, hour-drawer-days is not updated)

Attribute

period

0 to 366 (cannot be omitted)

Parent element

ex-interval-record

Child element

None

day-drawer-weeks

Type

Description

Description

Specifies the PI record retention period in days.

Specify the number of weeks. You can specify a maximum of 522 weeks (10 years).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, day-drawer-weeks is not updated)

Attribute

period

0 to 522 (cannot be omitted)

Parent element

ex-product-interval

Child element

None

week-drawer-weeks

Type

Description

Description

Specifies the PI record retention period in days.

Specify the number of weeks. You can specify a maximum of 522 weeks (10 years).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, week-drawer-weeks is not updated)

Attribute

period

0 to 522 (cannot be omitted)

Parent element

ex-product-interval

Child element

None

month-drawer-months

Type

Description

Description

Specifies the PI record retention period in months.

Specify the number of months. You can specify a maximum of 120 months (10 years).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, month-drawer-months is not updated)

Attribute

period

0 to 120 (cannot be omitted)

Parent element

ex-product-interval

Child element

None

ex-product-detail

Type

Description

Description

Specifies the PD record retention period.

The condition for the target Store database is as follows:

Version 08-11 or later and Store 2.0

Specifiable value

None

Omissible

Yes (when the parameter is omitted, ex-product-detail is not updated)

Attribute

None

Parent element

service

Child element

ex-detail-record (can be specified only once per PD record or can be omitted)

Note: When you specify this tag, set the ver attribute of pr-cli-parameters to 0110 or later.

ex-detail-record

Type

Description

Description

Specifies the PD record retention period.

Specify the number of days. You can specify a maximum of 366 days (a year).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, ex-detail-record is not updated)

Attribute

id

PD record ID (for the record ID, see the PFM - Agent or PFM - RM manuals. You cannot omit this attribute.)

period

0 to 366 (cannot be omitted)

Parent element

ex-product-detail

Child element

None

ex-product-log

Type

Description

Description

Specifies the PL record retention period.

The condition for the target Store database is as follows:

Version 08-11 or later and Store 2.0

Specifiable value

None

Omissible

Yes (when the parameter is omitted, ex-product-log is not updated)

Attribute

Yes

Parent element

service

Child element

ex-log-record (can be specified only once per PL record or can be omitted)

ex-log-record

Type

Description

Description

Specifies the PL record retention period.

Specify the number of days. You can specify a maximum of 366 days (a year).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, ex-log-record is not updated)

Attribute

id

PL record ID (for the record ID, see the PFM - Agent or PFM - RM manuals. You cannot omit this parameter.)

period

0 to 366 (cannot be omitted)

Parent element

ex-product-log

Child element

None

The following are examples of the parameter file.

Parameter file example (when the Store version is 1.0)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "aspsv_params.dtd">
<pr-cli-parameters ver="0110">
<agent-store-db-preserve-definition>
    <service id="TS1host1">
        <product-interval>
            <minute-drawer>day</minute-drawer>
            <hour-drawer>day</hour-drawer>
            <day-drawer>week</day-drawer>
            <week-drawer>month</week-drawer>
            <month-drawer>year</month-drawer>
            <!-- year-drawer : Year -->
        </product-interval>
        <product-detail>
            <detail-record id="PD" max-rec="30000"/>
            <detail-record id="PD_THRD" max-rec="30000"/>
            <detail-record id="PD_ADRS" max-rec="30000"/>
            <detail-record id="PD_PDI" max-rec="30000"/>
            <detail-record id="PD_PEND" max-rec="30000"/>
        </product-detail>
        <product-log>
           <log-record id="PL" max-rec="30000"/>
           <log-record id="RM" max-rec="30000"/>
        </product-log>
    </service>
</agent-store-db-preserve-definition>
</pr-cli-parameters>

Parameter file example (when the Store version is 2.0)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "aspsv_params.dtd">
<pr-cli-parameters ver="0110">
<agent-store-db-preserve-definition>
    <service id="TS1host1">
        <ex-product-interval>
            <ex-interval-record id="PI">
                <minute-drawer-days period="10"/>
                <hour-drawer-days period="10"/>
                <day-drawer-weeks period="10"/>
                <week-drawer-weeks period="10"/>
                <month-drawer-months period="10"/>
                <!-- year-drawer-years period="10" -->
            </ex-interval-record>
            <ex-interval-record id="PI_LOGD">
                <minute-drawer-days period="10"/>
                <hour-drawer-days period="10"/>
                <day-drawer-weeks period="10"/>
                <week-drawer-weeks period="10"/>
                <month-drawer-months period="10"/>
                <!-- year-drawer-years period="10" -->
            </ex-interval-record>
        </ex-product-interval>
        <ex-product-detail>
            <ex-detail-record id="PD" period="10"/>
            <ex-detail-record id="PD_THRD" period="10"/>
            <ex-detail-record id="PD_ADRS" period="10"/>
            <ex-detail-record id="PD_PDI" period="10"/>
            <ex-detail-record id="PD_PEND" period="10"/>
        </ex-product-detail>
        <ex-product-log>
            <ex-log-record id="PL" period="10"/>
            <ex-log-record id="RM" period="10"/>
        </ex-product-log>
    </service>
</agent-store-db-preserve-definition>
</pr-cli-parameters>

Notes

The command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication. For the specification value for each tag, see the notes on Settings for performance data collection in the PFM - Agent or PFM - RM manuals.

For details about the service ID and record ID, see the PFM - Agent or PFM - RM manuals.

If the specified service ID is not for an agent product, an error results.

If the same service ID is specified more than once, an error results.

If the same record ID is specified more than once, an error results.

If multiple Store database storage condition definitions are registered consecutively and the registration of any of the definitions fails, the command cancels the registration of that definition and registers the next definition, if any.

The specifications of retention periods (minute-drawer through month-drawer) simply use different units; these specifications have no mutual relationships.

When the Store version is 1.0, the ex-product-interval tag, the ex-product-detail tag, and the ex-product-log tag are ignored if they are specified. When the Store version is 2.0, the product-interval tag, the product-detail tag, and the product-log tag are ignored if they are specified.

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

Return values

0

The command ended normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

Creation of the output file failed.

5

The parameters cannot be analyzed because they do not match the DTD file.

10

Updating of at least one Store database definition failed.

11

Authentication processing for login to PFM - Manager failed. Alternatively, the user specified at authentication does not have execution permission.

100

The environment is invalid.

200

A memory error occurred.

202

A file access error occurred.

222

A communication processing error occurred.

255

An unexpected error occurred.

Usage example

This example specifies a parameter file (aspsv_update.xml) that contains definition information about the Store database storage conditions:

jpcaspsv  update  aspsv_update.xml

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

In this example, three service IDs are specified and one of them results in an error, as shown in the standard output below. It displays the execution results (OK or ERR) for each service ID specified in the service tag.

Example of standard output

jpcaspsv update connected to hostname at yyyy MM dd HH:MM:SS.mmm
update result  OK  : TS1host1
update result  OK  : TS1host2
update result  ERR : TS1host3
jpcaspsv update disconnected at yyyy MM dd HH:MM:SS.mmm

jpcasrec output

Format

jpcasrec output     [-mx maximum-heap-size]
                    [-ms initial-heap-size]
                     -o output-file
                     service-ID

Function

The jpcasrec output command outputs the definition regarding the recording method of the Store database in XML format. You can specify the obtained output file as an input file for the jpcasrec update command.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-o output-file

Specifies the name of an XML-format file to which the execution results are to be output. This can be an absolute file path name, relative file path name, or file name. If the specified file name is not the absolute file path name, the command assumes the current directory as the reference directory (if the specified directory does not exist, an error results).

service-ID

Specifies the service ID of the target agent. Wildcard characters cannot be used. Conditions for the specified value are as follows:

4 to 258 characters

The first character specifies the product ID of the agent (for details about product IDs, see the PFM - Agent or PFM - RM manuals).

The second character specifies A (Agent Collector or Remote Monitor Collector).

Notes

The command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication. For the permitted range of service IDs and record IDs, see the PFM - Agent or PFM - RM manuals.

Definition information that cannot be updated is output as comments in the output file.

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

Return values

0

The command ended normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

Creation of the output file failed.

5

The parameters cannot be analyzed because they do not match the DTD file.

10

Updating of at least one Store database definition failed.

11

Authentication processing for login to PFM - Manager failed. Alternatively, the user specified at authentication does not have execution permission.

100

The environment is invalid.

200

A memory error occurred.

202

A file access error occurred.

222

A communication processing error occurred.

255

An unexpected error occurred.

Usage example

This example outputs to a parameter file (asrec_output.xml) definition information for the Store database recording method for the PFM - Agent whose service ID is TA1host1:

jpcasrec  output  -o asrec_output.xml  TA1host1

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

An example of the standard output is shown below. It displays the execution results (OK or ERR) for the service ID specified in the argument.

Example of standard output

jpcasrec output connected to hostname at yyyy MM dd HH:MM:SS.mmm
output result  OK  : TA1host1
jpcasrec output disconnected at yyyy MM dd HH:MM:SS.mmm

Output file

An example of a file output by this command is shown below.

Example of output file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "asrec_params.dtd">
<pr-cli-parameters ver="0110">
<agent-store-db-record-definition>
    <service id="TA1host1">
        <record id="PD_CIND">
            <!-- Description : Content Index Detail -->
            <log>Yes</log>
            <collection-interval>600</collection-interval>
            <collection-offset>0</collection-offset>
            <!--Over 10 Sec Collection Time : No -->
            <realtime-report-data-collection-mode>Temporary Log</realtime-report-data-collection-mode>
            <logif></logif>
              <and>
                <or>
                  <expression>RECORD_TIME&lt;"01:23:45"</expression>
                  <expression>INTERVAL&lt;"2000"</expression>
                </or>
                <expression>INSTANCE&lt;"INST"</expression>
              </and>
            </logif>
        </record>
        <record id="PD_CINF">
            <!-- Description : Content Index Filter Detail -->
            <log>No</log>
            <collection-interval>60</collection-interval>
            <collection-offset>0</collection-offset>
            <!--Over 10 Sec Collection Time : Yes -->
            <realtime-report-data-collection-mode>Temporary Log</realtime-report-data-collection-mode>
            <logif> </logif>
        </record>
        <record id="PD_DEV">
            <!-- Description : Devices Detail -->
            <log>Yes</log>
            <collection-interval>480</collection-interval>
            <collection-offset>60</collection-offset>
            <!--Over 10 Sec Collection Time : No -->
            <realtime-report-data-collection-mode>Temporary Log</realtime-report-data-collection-mode>
            <logif> </logif>
        </record>
      :
      :
      :
    </service>
</agent-store-db-record-definition>
</pr-cli-parameters>

jpcasrec update

Format

jpcasrec update     [-mx maximum-heap-size]
                    [-ms initial-heap-size]
                     input-file

Function

The jpcasrec update command connects to an agent and changes the definition related to the recording method of the Store database. The command acquires the new recording method definition information from the XML-format parameter file that is specified as a command line argument. You can specify multiple Store database definition information items in a single parameter file to make changes in batch mode.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

input-file

Specifies the XML-format parameter file that is to be used to change the Store database recording method definition information. This parameter file must be created according to the Parameter file format described below. You can specify the absolute file path name, relative file path name, or file name. When the name is not the absolute file path, the command assumes the current directory.

Parameter file format

XML tag specifications

agent-store-db-record-definition

Type

Description

Description

Root tag for the Store database recording method change definition information

Specifiable value

None

Omissible

No

Attribute

None

Parent element

pr-cli-parameters

Child element

service (can be specified more than once)

service

Type

Description

Description

Specifies the service that identifies the agent.

Specifiable value

None

Omissible

No

Attribute

id

Service ID (4 to 258 characters)

The first character specifies the product ID of the agent. For details about the product ID, see the PFM - Agent or PFM - RM manuals.

The second character specifies A (Agent Collector or Remote Monitor Collector).

Parent element

agent-store-db-record-definition

Child element

record (cannot be omitted and can be specified more than once)

record

Type

Description

Description

Specifies the record ID to be changed.

Specifiable value

None

Omissible

No

Attribute

id

Record ID (1 to 8 characters). This is a record ID described in the PFM - Agent or PFM - RM manuals.

Parent element

service

Child element#

log (can be specified only once per record or can be omitted)

collection-interval (can be specified only once per record or can be omitted)

collection-offset (can be specified only once per record or can be omitted)

logif (can be specified only once per record or can be omitted)

#

If the child elements are omitted, the corresponding item is not updated. If you specify child elements, specify them in the order listed above.

log

Type

Description

Description

Specifies whether or not the information is to be recorded in the Store database.

Specifiable value

Alphabetic characters

Yes: Record in the Store database

No: Do not record in the Store database

This value is not case sensitive.

Omissible

Yes (when the parameter is omitted, log is not updated.)

Attribute

None

Parent element

record

Child element

None

collection-interval

Type

Description

Description

Specifies the performance data collection interval (in seconds).

Specifiable value

Numeric value

0 to 2,147,483,647 (when 0 is specified, performance data is not collected)

Omissible

Yes (when the parameter is omitted, collection-interval is not updated)

Attribute

None

Parent element

record

Child element

None

collection-offset

Type

Description

Description

Specifies the delay in seconds for starting collection of performance data.

Specifiable value

Numeric value

0 to 32,767 (when 0 is specified, collection of performance data is started at the same time)

Omissible

Yes (when the parameter is omitted, collection-offset is not updated)

Attribute

None

Parent element

record

Child element

None

realtime-report-data-collection-mode

Type

Description

Description

Specifies the operation mode when the collection of historical data will be prioritized over the processing to display realtime reports#.

Specifiable value

Alphabetic characters

Reschedule: The re-schedule mode

Temporary Log: Temporary log mode

This value is not case sensitive.

Omissible

Yes (when the parameter is omitted, realtime-report-data-collection-mode is not updated)

Attribute

None

Parent element

Record

Child element

None

#: For agents that are not configured to prioritize the collection of historical data, an error occurs if you specify this tag. For details on how to prioritize the collection of historical data over the processing to display realtime reports, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

logif

Type

Description

Description

Specifies the checking condition for recording performance data in the Store database.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, logif is not updated)

Attribute

delete

"yes" (When this attribute is specified, the command ignores the specified child elements and deletes the registered expression. If this attribute is omitted, the command registers the checking condition according to the specified child elements.)

Parent element

record

Child element

expression (can be specified more than once and can be omitted)

and (can be specified more than once if there is more than one expression, or can be omitted)

or (can be specified more than once if there is more than one expression, or can be omitted)

expression

Type

Description

Description

Specifies the checking condition for storing performance data in the Store database.

Specifiable value

Specifies the conditional expression in field condition"value" format. You cannot use a space as a delimiter for field, condition, and value.

You cannot specify a field on the right side.

If you want to specify multiple expression attributes, enclose only two of them at a time between <and> tags or <or> tags, which represent logical operators, and specify the attributes as a binomial. Nesting of binomials is allowed. You cannot specify a polynomial.

If you want to use an equality sign or an inequality sign other than in a condition, insert \ before the sign. If you want to use \, specify \ twice (\\).

field

Specify a field in the record. For field, specify the PFM - Manager name. For details about the PFM - Manager name, see the description of records in the applicable PFM - Agent or PFM - RM manuals.

condition

Specify one of the following as the condition value:

=: Field value is equal to "value".

<: Field value is less than "value".

<=: Field value is equal to or less than "value".

>: Field value is greater than "value".

>=: Field value is equal to or greater than "value".

<>: Field value is any value other than "value".

In XML, specify &lt; for < and &gt; for >.

Character string fields are compared in ascending order of ASCII codes.

"value"

Specify the value according to the field format described in the PFM - Agent or PFM - RM manuals. The permitted values are as follows:

Characters (specify as is)

Integer (specify a value in the range permitted for Integer)

Decimal value (specify a value in the range permitted for Double; more than 4 decimal places must be rounded to 4 decimal places according to the IEEE754 Rounding to nearest specification standards#)

Date (specify time in the format "HH:mm:ss")

The value cannot contain any control character or any of the symbols ( ) [ ] < > = ". If a control character or any of these symbols is specified, an error results.

Omissible

No

Attribute

None

Parent element

logif

and

or

Child element

None

#

The IEEE754 Rounding to nearest specification standards are as follows:

The target value is compared with two approximate values and rounded to one of the approximate values, whichever is closer to the target value.

If the target value is exactly in the middle of the two approximate values, the approximate values are represented in binary and the target value is rounded to one of the approximate values, whichever ends with 0.

and

Type

Description

Description

Specifies the AND operation of the logical expression specified in expression.

Specifiable value

None

Omissible

Yes

Attribute

None

Parent element

logif

and

or

Child element

expression (can be specified more than once or can be omitted)

and (can be specified more than once if there is more than one expression, or can be omitted)

or (can be specified more than once if there is more than one expression, or can be omitted)

or

Type

Description

Description

Specifies the OR operation of the logical expression specified in expression.

Specifiable value

None

Omissible

Yes

Attribute

None

Parent element

logif

and

or

Child element

expression (can be specified more than once or can be omitted)

and (can be specified more than once if there is more than one expression, or can be omitted)

or (can be specified more than once if there is more than one expression, or can be omitted)

An example of a parameter file is shown below.

Example of parameter file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "asrec_params.dtd">
<pr-cli-parameters ver="0110">
<agent-store-db-record-definition>
    <service id="TA1host1">
        <record id="PD_CIND">
            <log>Yes</log>
            <collection-interval>60</collection-interval>
            <collection-offset>0</collection-offset>
            <realtime-report-data-collection-mode>Temporary Log</realtime-report-data-collection-mode>
            <logif>
                <and>
                    <and>
                        <expression>RECORD_TIME="10:26:50"</expression>
                        <expression>UNIQUE_KEYS&gt;="40"</expression>
                    </and>
                    <or>
                        <expression>INSTANCE="abc"</expression>
                        <expression>INSTANCE="xyz"</expression>
                    </or>
                </and>
            </logif>
        </record>
        <record id="PD_CINF">
            <log>Yes</log>
            <collection-interval>300</collection-interval>
            <collection-offset>10</collection-offset>
            <logif delete="yes"/>
        </record>
        <record id="PD_DEV">
            <log>No</log>
        </record>
    </service>
</agent-store-db-record-definition>
</pr-cli-parameters>

Notes

The command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication. For the specification value for each tag, see the notes on Settings for performance data collection in the PFM - Agent or PFM - RM manuals.

For details about the service ID, record ID, field names for each record ID, and permitted value ranges, see the PFM - Agent or PFM - RM manuals.

The parameters that can be changed depend on the service ID and record ID. For details, see the PFM - Agent or PFM - RM manuals.

Depending on the specified service ID or record ID, Sync Collection With applies to the record. In this case, neither Collection interval nor Collection offset can be specified. For details, see the PFM - Agent or PFM - RM manuals.

If the specified service ID is not for an agent product, an error results.

If the same service ID is specified more than once, an error results.

If the same record ID is specified more than once, an error results.

If multiple Store database recording method definitions are registered consecutively by service ID and the registration of any of the definitions fails, the command cancels the registration of that definition and registers the next definition by service ID, if any.

Only two elements can be specified under <and> and <or> tags in the <logif> tag.

The following shows an example:

  <and>
     <expression>expression-1</expression>
     <or>
        <expression>expression-2</expression>
        <or>
           <expression>expression-3</expression>
           <or>
              <expression>expression-4</expression>
              <expression>expression-5</expression>
           </or>
        </or>
     </or>
  </and>

The following shows examples of expressions specified in the <expression> tag:

<expression>SEGMENTS_RETRANSMITTED_PER_SEC&gt;"100"</expression>
<expression>RECORD_TIME&gt;"11:22:33"</expression>

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

Creation of the output file failed.

5

The parameters cannot be analyzed because they do not match the DTD file.

10

Updating of at least one Store database definition failed.

11

Authentication processing for login to PFM - Manager failed. Alternatively, the user specified at authentication does not have execution permission.

100

The environment is invalid.

200

A memory error occurred.

202

A file access error occurred.

222

A communication processing error occurred.

255

An unexpected error occurred.

Usage example

This example specifies a parameter file (asrec_update.xml) that contains definition information about the Store database recording method:

jpcasrec  update  asrec_update.xml

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

If three service IDs are specified and one of them results in an error, the standard output shown below is obtained. It displays the execution results (OK or ERR) for each service ID specified in the service tag.

Example of standard output

jpcasrec update connected to hostname at yyyy MM dd HH:MM:SS.mmm
update result  OK  : TA1host1
update result  OK  : TA1host2
update result  ERR : TA1host3
jpcasrec update disconnected at yyyy MM dd HH:MM:SS.mmm

jpccfgbackup

Format

jpccfgbackup backup-destination-directory

Function

The jpccfgbackup command creates a backup file for the Performance Management program definition information on the local host.

To execute this command on UNIX, the environment must allow the use of the Korn shell (ksh). For details about the applicable package, see the Release Notes for PFM - Manager and PFM - Base.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

User with Backup Operators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

backup-destination-directory

Specifies the name of the directory that will contain backup files for the definition information. For backup-destination-directory, specify a string of 1 to 35 bytes, consisting of single-byte alphanumeric characters and symbols. You cannot specify a relative path. Always specify an absolute path. Note that you cannot use the following symbols in the path specification:

; , * ? ' " < > | & ^ `

If the directory name that you want to specify contains spaces, enclose the entire name in double quotation marks ("). If you specify any of the following symbols, enclose it in double quotation marks (") in order to prevent it from being analyzed by the shell or the command prompt:

( )

Make sure that you specify a directory that is not the installation directory for Performance Management.

Also make sure that you specify an empty directory that contains no files or directories.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

100

The Performance Management environment is invalid.

105

Current directory is not the directory that contains the jpccfgbackup command.

210

A disk space shortage occurred.

230

Execution of an internal command failed.

235

An attempt to back up one or more files failed.

255

An unexpected error occurred.

Usage example

This example backs up definition information to the /tmp/pfmbackup directory.

jpccfgbackup /tmp/pfmbackup

Notes

Before you execute the jpccfgbackup command, change the current directory to the directory that contains that command.

Do not execute two or more instances of the jpccfgbackup command concurrently.

Before you back up definition information, make sure that there is sufficient free disk space. To determine a sufficient amount of free disk space, make a guess from the disk space requirements for installing the product.

If an error occurs during backup processing, only files that were successfully backed up remain in the backup destination directory.

If the command fails to copy a file, the command does not terminate, and attempts to copy the next file. If a file copy error occurs more than once, the information about the last error will be reported as the return value.

jpcconf acc display

Format

jpcconf acc display    -type{pfmhost|wmi|ssh}
                       [-lhost logical-host-name]

Function

Displays the settings of the specified common account information.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-type {pfmhost|wmi|ssh}

Specifies the type of the common account information to be displayed. The following table shows details of each type.

Common account information type

Description

pfmhost

Common account information for instance environments (for each PFM - RM host)

wmi

Common account information for monitoring targets (for remote connections via WMI)

ssh

Common account information for monitoring targets (for remote connections via SSH)

-lhost logical-host-name

Specifies the logical host name of the host on which this command is to be executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If you omit this option, the command assumes that the physical host is specified.

Notes

The version of PFM - RM for Platform and the version of a required program (PFM - Manager or PFM - Base) on the same PFM - RM for Platform device must be 10-50 or later.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

In a logical host environment, this command cannot run on the standby logical host.

The value specified for Password is not displayed.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

10

The command is now running.

11

The user canceled the processing.

24

The common account information has not been set.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example

This example displays the common account information for the instance environments of a PFM - RM host, in Windows.

jpcconf acc display -type pfmhost
User              : user1
Password          :
Domain            : domain1
KAVE05471-I The common account information was displayed successfully. (type=pfmhost)

jpcconf acc setup

Format

Format 1

jpcconf acc setup    -type {pfmhost|wmi|ssh}
                     [-lhost logical-host-name]
                     [-input definition-file-name]
                     [-noquery]

Format 2

jpcconf acc setup    -type {pfmhost|wmi|ssh}
                     -template definition-file-name
                     [-noquery]

Function

Format 1

Newly creates and updates the specified common account information.

Format 2

By specifying the -template option, a template file that contains all labels to be set in the common account information also can be output.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-type {pfmhost|wmi|ssh}

Specifies the type of the common account information to be created. The following table shows details of each type.

Common account information type

Description

pfmhost

Common account information for instance environments (for each PFM - RM host)

wmi

Common account information for monitoring targets (for remote connection via WMI)

ssh

Common account information for monitoring targets (for remote connection via SSH)

-lhost logical-host-name

Specifies the logical host name of the host on which this command is to be executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If you omit this option, the command assumes that the physical host is specified.

This option cannot be specified with the -template option (in Format 2).

-input definition-file-name

Specify this option to read the values to be set in the common account information from a definition file. For definition-file-name, specify a string of 1 to 250 bytes. The common account information is automatically created or updated by using the values in the specified definition file.

If you specify a string that contains spaces or parentheses (( )) for this option, enclose the entire string in double quotation marks (").

If you omit this option, the command runs in interactive mode.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode. Note that the behaviors while the command is running are as follows:

If the common account information has been already configured:

A KAVE05478-I message is output and the settings of the common account information are updated.

If the file with the same name as that of the file specified for the -template option already exists:

A KAVE05399-I message is output and the file is updated.

-template definition-file-name

Specify this option to output the definition file template. For definition-file-name, specify a string of 1 to 245 bytes. The definition file consisting of the sections and labels that correspond to the type of the target common account information is output. Note that the labels of the [Account Definitions] section remain blank.

You can edit the output definition file according to environment requirements, and can specify the edited definition file as an input file for the -input option.

If you specify a string that contains spaces or parentheses (( )) for this option, enclose the entire string in double quotation marks (").

Format of the definition file (pfmhost and wmi)

The definition file is a text file consisting of the sections and labels below. The label names and values are specified in name=value format. The format of the definition file differs depending on the type of the common account information. The following shows the definition file format for pfmhost and wmi:

[Common Definitions] section

Specifies the basic information in the definition file.

Definition Type label

Specifies the type of the common account information. Specify pfmhost if the type of the common account information is pfmhost. Specify wmi if the type of the common account information is wmi.

[Account Definitions] section

Specifies the values to be set in the common account information.

User label

Specify the user name as a string of 1 to 256 bytes, consisting of single-byte alphabetic characters with no tab characters. You cannot omit this label.

Password label

Specify the password as a string of 1 to 256 bytes, consisting of single-byte alphabetic characters with no tab characters. You cannot omit this label.

Domain label

Specify the domain name as a string of 0 to 256 bytes, consisting of single-byte alphabetic characters with no tab characters. You can omit this label.

Example of specifying settings in a definition file for pfmhost:

[Common Definitions]
Definition Type=pfmhost

[Account Definitions]
User=Administrator
Password=aaa
Domain=bbb

Example of specifying settings in a definition file for wmi:

[Common Definitions]
Definition Type=wmi

[Account Definitions]
User=Administrator
Password=aaa
Domain=bbb

Format of the definition file (ssh)

The definition file is a text file consisting of the sections and labels below. The label names and values are specified in name=value format.

[Common Definitions] section

Specifies the basic information in the definition file.

Definition Type label

Specifies the type of the common account information. Specify ssh if the type of the common account information is ssh.

[Account Definitions] section

Specifies the values to be set in the common account information.

User label

Specify the user name as a string of 1 to 256 bytes, consisting of single-byte alphabetic characters with no tab characters. You cannot omit this label.

Private_Key_File label

Specify the name of the private key file to be used in the SSH public key method with the absolute path. Specify a string of 1 to 256 bytes, consisting of single-byte alphabetic characters.

Even if you specify a string that contains spaces, you do not need to enclose the entire string in double quotation marks ("). However, tab characters cannot be specified.

Note that you cannot omit this label.

Example of specifying settings in a definition file for ssh:

[Common Definitions]
Definition Type=ssh

[Account Definitions]
User=root
Private_Key_File=/opt/jp1pc/agt7/.ssh/agt7

Notes

The versions of PFM - RM for Platform and the version of a required program (PFM - Manager or PFM - Base) on the same PFM - RM for Platform device must be 10-50 or later.

If the definition file includes confidential information such as passwords, save the file in a secure and safe place, and delete the file when the file is no longer needed. If you need to transfer the definition file between hosts, we recommend that you use SFTP communications (FTP communications through an SSH tunnel) or other safe means that are secure against sniffing.

This command cannot run concurrently with a startup or termination command, or other setup command, on the same host.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

If the common account information is updated while the Remote Monitor Collector service is running, the update timing of the common account information differs depending on the type of the common account information.

To apply the updated common account information for pfmhost to instance environments, you need to restart the Remote Monitor Collector service.

The updated common account information for wmi or ssh is applied during the first processing to collect the performance information after the common account information was updated. Therefore, you do not need to restart the Remote Monitor Collector service.

When you execute the command with the -input option specified, the command execution is interrupted if the definition file does not contain necessary labels or if invalid values are specified for necessary labels. If you specify the -noquery option to automatically execute the command in a batch or a script file, verify that the settings in the definition file are correct beforehand. Check the output message or return value to confirm that the command execution was complete normally.

In a logical host environment, the command in Format 1 cannot run on the standby logical host.

If ssh is specified for the -type option, the command checks whether the file specified for the Private_Key_File label exists. If the file is not found, a KAVE05489-W message is output and the command continues the subsequent processing.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

6

The definition file contains errors.

10

The command is now running.

11

The user canceled the processing.

26

An incorrect value might be specified.#

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

#

This value is returned when the specified file is not found.

Usage example 1

This example specifies the definition file to be read for the -input option and creates or updates the common account information in interactive mode. In this example, pfmhostTemplate.txt is read as the input file. The values in pfmhostTemplate.txt are displayed as the values of User, Password, and Domain. The values entered for Password and Re-enter are not displayed.

jpcconf acc setup -type pfmhost -input pfmhostTemplate.txt
KAVE05477-Q The common account information is already configured (type=pfmhost). Do you want to update it? (Y/N) Y
User                                          : Administrator
Password                                      :
                                     Re-enter :
Domain                   []                   : bbb
KAVE05473-I The common account information was configured successfully. (type=pfmhost)

Usage example 2

This example outputs the template specified for the -template option, in interactive mode. In this example, the template file pfmhostTemplate.txt is output.

jpcconf acc setup -type pfmhost -template pfmhostTemplate.txt
KAVE05146-Q The file already exists. Do you want to update the file? (Y/N) Y
KAVE05481-I The input definition file template was exported successfully. (type=pfmhost)

Usage example 3

This example creates the common account information for pfmhost, in interactive mode. The values entered for Password and Re-enter are not displayed.

jpcconf acc setup -type pfmhost
User                                          : Administrator
Password                                      :
                                     Re-enter :
Domain                   []                   : bbb
KAVE05473-I The common account information was configured successfully. (type=pfmhost)

Usage example 4

This example updates the common account information for pfmhost, in interactive mode. The values entered for Password and Re-enter are not displayed.

jpcconf acc setup -type pfmhost
KAVE05477-Q The common account information is already configured (type=pfmhost). Do you want to update it? (Y/N) Y
User                     [Administrator]      :
Password                                      :
                                     Re-enter :
Domain                   [bbb]                :
KAVE05473-I The common account information was configured successfully. (type=pfmhost)

Usage example 5

This example reads the definition file pfmhostTemplate.txt specified for the -input option and creates the common account information. Because the -noquery option is specified in this example, if the definition file with the same file name already exists, the common account information is automatically updated.

jpcconf acc setup -type pfmhost -input pfmhostTemplate.txt -noquery
KAVE05478-I The common account information is being updated. (type=pfmhost)
User                                          : Administrator
Password                                      :
                                     Re-enter :
Domain                   []                   : bbb
KAVE05473-I The common account information was configured successfully. (type=pfmhost)

Usage example 6

This example outputs the template file pfmhostTemplate.txt specified for the -template option. Because the -noquery option is specified in this example, if the template file with the same file name already exists, the existing template file is automatically updated.

jpcconf acc setup -type pfmhost -template pfmhostTemplate.txt -noquery
KAVE05399-I The existing file will be updated. (file=C:\Program Files\Hitachi\jp1pc\tools\pfmhostTemplate.txt)
KAVE05481-I The input definition file template was exported successfully. (type=pfmhost)

jpcconf acc unsetup

Format

jpcconf acc unsetup    -type {pfmhost|wmi|ssh}
                       [-lhost logical-host-name]
                       [-noquery]

Function

Deletes the specified common account information.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-type {pfmhost|wmi|ssh}

Specifies the type of the common account information to be deleted. The following table shows details of each type.

Common account information type

Description

pfmhost

Common account information for instance environments (for each PFM - RM host)

wmi

Common account information for monitoring targets (for remote connection via WMI)

ssh

Common account information for monitoring targets (for remote connection via SSH)

-lhost logical-host-name

Specifies the logical host name of the host on which this command is to be executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If you omit this option, the command assumes that the physical host is specified.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option to execute the command in non-interactive mode.

Notes

The version of PFM - RM for Platform and the version of a required program (PFM - Manager or PFM - Base) on the same PFM - RM for Platform device must be 10-50 or later.

This command cannot run concurrently with a startup or termination command, or other setup command, on the same host.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

In a logical host environment, this command cannot run on the standby logical host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

10

The command is now running.

11

The user canceled the processing.

24

The common account information has not been set.

25

An environment that uses the common account information exists.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example

This example deletes the common account information for the instance environments of a PFM - RM host, in Windows.

jpcconf acc unsetup -type pfmhost
KAVE05479-Q The common account information will be deleted (type=pfmhost). Are you sure you want to delete this information? (Y/N) Y
KAVE05475-I The common account information was deleted successfully. (type=pfmhost)

jpcconf agent setup

Format

Format 1

jpcconf agent setup      -key service-key
                        [-noquery]

Format 2

jpcconf agent setup      -key service-key
                        [-register]

Function

The jpcconf agent setup command adds a new instance of PFM - Agent or PFM - RM to Performance Management systems. Information about the PFM - Agent or PFM - RM instance is registered in PFM - Manager and PFM - Base. For version 09-00 or later of PFM - Manager, since PFM - Agent and PFM - RM information is automatically registered with PFM - Manager, this command does not normally need to be executed.

To have new information about instances of PFM - Agent or PFM - RM registered with PFM - Manager displayed in the PFM - Web Console, start the newly registered PFM - Agent or PFM - RM instance. The information is applied upon login to PFM - Web Console. However, for instances of PFM - Agent or PFM - RM released after PFM - Manager, manual registration might be necessary. In this case, execute the jpcconf agent setup command using Format 1. To display the information in PFM - Web Console without starting PFM - Agent or PFM - RM, execute the jpcconf agent setup command in Format 2.

Execute this command in the following case:

Format 1

When registering an instance of PFM - Agent or PFM - RM released after PFM - Manager#1

When registering an instance of PFM - Agent or PFM - RM with PFM - Base#2

Format 2

When registering information about an instance of PFM - Agent or PFM - RM with PFM - Manager without starting the instance, and displaying it in PFM - Web Console

#1

For details about whether registration is necessary, see the PFM - Manager release notes.

#2

This is necessary when the NNM linkage facility is used and PFM - Base is installed on the host on which NNM is installed.

If logical host settings have been set up for PFM - Manager, information about the new PFM - Agent or PFM - RM instance is registered for the set logical host and physical host.

Hosts that can execute the command

Format 1

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Format 2

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console if Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key for the new instance of PFM - Agent or PFM - RM for which additional setup is to be executed. A product name can also be specified when the product name display functionality is enabled.

Assume that you set up a product not described in Appendix Registration information for the JP1/PFM - Agent in JP1/PFM - Manager in the Release Notes for PFM - Manager on the PFM - Manager installed in the host on which you want to execute the jpcconf agent setup command. In such cases, specify a service key instead of the product name of the product.

Format 1

The service key that can be specified here can only be from an instance of PFM - Agent or PFM - RM for which a setup file has been copied to the following directory:

In Windows: installation-folder\setup\

In UNIX: /opt/jp1pc/setup/

For details about setup files, see the chapter describing installation and setup in the relevant PFM - Agent or PFM - RM manuals.

If all is specified in service-key, the setup is executed for all setup files that have been copied to this folder.

Format 2

Unlike Format 1, there is no need to copy a setup file. all cannot be specified for the service key.

-register

Displays the instance of PFM - Agent or PFM - RM specified by the service key, in the PFM - Web Console. If PFM - Manager is running on a cluster system, this can only be executed on the executing node.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

Note, however, that if there are Performance Management services that are running, command execution is interrupted with a KAVE05143-E message. If this message is output, stop all Performance Management services that are running on the local host, and then re-execute the command.

Notes

The log information for when this command is executed is output to the common message log on the physical host, even when the setup destination is on the logical host.

If this command's execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

For version 09-00 or later of PFM - Web Console, information about the registered instance of PFM - Agent or PFM - RM is applied upon login. For version 08-11 or earlier of PFM - Web Console, registration is applied once PFM - Web Console is restarted.

Cautions regarding execution using Format 1

Before executing this command, copy the setup file for the new instance of PFM - Agent or PFM - RM for which information is to be registered in the following directory on the execution host:

In Windows: installation-folder\setup\

In UNIX: /opt/jp1pc/setup/

When performing additional setup of a new instance of PFM - Agent or PFM - RM on a host separate from that on which the original instance of PFM - Agent or PFM - RM was installed, make sure that the setup file for the new instance of PFM - Agent or PFM - RM is copied to these directories on the execution host. When using FTP to copy (transfer) files between a Windows host and UNIX host, make sure that binary mode is used.

Before executing this command, stop all Performance Management services running on the local host. If you execute this command without stopping the services, the command will attempt to stop them. However, if the command cannot stop the services completely, an error will result. If this occurs, make sure that the services have stopped completely, and then re-execute the command. After the setup is completed, manually start the services.

To check the startup status for the service, execute the jpctool service list command.

When an attempt is made to set up an instance of PFM - Agent or PFM - RM already supported by PFM - Manager, the KAVE05944-W message is output, and setup for PFM - Manager is skipped. In this case, setup for PFM - Manager is not necessary.

Cautions regarding execution using Format 2

It is not necessary to stop the Performance Management service.

Registration in Format 2 cannot be performed for instances of PFM - Agent or PFM - RM released after PFM - Manager. Use Format 1 for setup.

This command cannot be executed outside of a PFM - Manager host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

Services have not been stopped on the local host.

10

The command is executing in another session.

11

The user canceled the processing (by entering N at the prompt).

100

The Performance Management environment is invalid.

101

Acquisition of a port number failed.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred (IP address could not be acquired).

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example 1

This example sets up an instance of PFM - Agent for Oracle released after PFM - Manager.

jpcconf agent setup -key Oracle

Usage example 2

This example displays the information about a newly added instance of PFM - Agent for Oracle in PFM - Web Console before it starts.

jpcconf agent setup -key Oracle -register

jpcconf agttree export

Format

Format 1

jpcconf agttree export    -owner user-name
                          [-lhost logical-host-name]
                          [-noquery]
                          -f export-file-name

Format 2

jpcconf agttree export    -template
                          [-noquery]
                          -f export-file-name

Function

The jpcconf agttree export command exports Agents tree definition information to the specified file as an Agents tree definition information file. This command can also generate the template file for Agents tree definition information files, rather than the Agents tree definition information file that contains the current definition information.

An exported Agents tree definition information file can be specified in the jpcconf agttree import command as an input file.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-owner user-name

Specifies the name of the user whose Agents tree definition information the command will export.

For user-name, specify a string of 1 to 16 bytes, consisting of single-byte alphanumeric characters, spaces, and the symbols listed below. Alphabetic characters are not case sensitive.

! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

Interpretation of the specified value follows the command line specifications of the OS and shell. You might need to make sure that the character encoding settings are appropriate beforehand, or add escape characters.

-template

Specify this option to output the template file for Agents tree definition files.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

If the Agents tree definition file specified for the -f option already exists, the file will be overwritten by the new file.

If a file with the same name as the specified file name already exists, a KAVE05399-I message is output and the file is updated.

-f export-file-name

Specifies the name of the Agents tree definition file to be exported. You can specify an absolute file path, a relative file path from the current directory, or the name of a file in the current directory.

Format of Agents tree definition files

See Format of Agents tree definition files in the description of the jpcconf agttree import command.

Notes

You can execute this command only when the View Server service is running.

The value of the LANG environment variable for the shell that is used to execute the command determines the encoding of the Agents tree definition file and the encoding value in the XML declaration part of that file. If the Agents tree information that you want to export includes non-ASCII characters, make sure that the value of the relevant LANG environment variable is appropriate before you execute this command.

The following table describes the encoding of the file and the encoding value in the XML declaration for each value of the LANG environment variable. If the value of the LANG environment variable is not described in the following table, the encoding attribute in the XML declaration will be set to UTF-8, and the file will be encoded with UTF-8.

The LANG environment variable in the shell that executed the command and the output character code of the agent hierarchy definition file are sometimes different. In such cases, when editing the exported the agent hierarchy definition file, confirm that the character code matches the encoding value in the definition file before importing the file. If an agent hierarchy definition file whose character code does not match the encoding value in the definition file is imported, the folder name for the agent hierarchy might be garbled. In such cases, correct the agent hierarchy definition file to match the character code and the encoding value in the definition file, and import the file again.

OS

LANG value

Encoding

Value of encoding in XML declaration

Windows

--

UTF-8

UTF-8

Linux

ja_JP.UTF-8

UTF-8

UTF-8

ja_JP.utf8

C

ASCII#

zh_CN.gb18030

GB18030

GB18030

zh_CN.UTF-8

UTF-8

UTF-8

zh.CN.utf8

Solaris

ja_JP.PCK

Shift-JIS

Shift_JIS

ja

EUC

EUC-JP

japanese

C

ASCII#

UTF-8

zh_CN.GB18030

GB18030

GB18030

zh_CN.GB18030@pinyin

zh_CN.GB18030@radical

zh_CN.GB18030@stroke

zh.UTF-8

UTF-8

UTF-8

zh_CN.UTF-8

zh_CN.UTF-8@pinyin

zh_CN.UTF-8@radical

zh_CN.UTF-8@stroke

AIX

Ja_JP.IBM-932

Shift-JIS

Shift_JIS

Ja_JP

ja_JP.IBM-eucJP

EUC

EUC-JP

ja_JP

C

ASCII#

UTF-8

Zh_CN

GB18030

GB18030

Zh_CN.GB18030

ZH_CN

UTF-8

UTF-8

ZH_CN.UTF-8

Legend:

--: Not applicable

#

If the Agents tree information to be exported includes non-ASCII characters, the file will be encoded with UTF-8.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

An attempt was made to execute the command on the PFM - Base host, but the command can only be executed on the PFM - Manager host.

6

The specified user does not exist.

11

Processing was canceled by the user (N was returned as the response to a query).

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Usage example

This example exports the Agents tree definition information for the user pfm-user.

# jpcconf agttree export -owner pfm-user -f agttree_def.xml

jpcconf agttree import

Format

jpcconf agttree import    [-nocheck]
                          [-noquery]
                          [-lhost logical-host-name]
                          -f Agents-tree-definition-file-name

Function

The jpcconf agttree import command imports Agents tree definition information from the specified file, and creates or updates the Agents tree with the imported information. The imported Agents tree definition information is applied at the following times:

When the Agents tree of PFM - Web Console is refreshed

When the user logs in to PFM - Web Console again

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-nocheck

Specify this option to skip checking whether the agents specified in the Agents tree definition file are recognized by Performance Management. If this option is omitted and an unrecognized agent is detected, the command processing stops.

After agents have been installed and set up, Performance Management recognizes them when they connect to PFM - Manager. Recognized agents are displayed under the Products node in the Agents tree.

Before agents are recognized by Performance Management, their data model version is assumed to be 3.0. The actual data model version will be applied after these agents are recognized.

Performance Management might have not yet recognized all of agents specified in the Agents tree definition file when, for example, the system is being built. In such a case, specify this option.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

Note that if the user specified in the Agents tree definition file has already created his or her Agents tree, the tree will be overwritten.

If the Agents tree of the specified user already exists, a KAVE06073-I message is output and the Agents tree is updated.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

-f Agents-tree-definition-file-name

Specifies the name of the Agents tree definition file to be imported. The file must be an XML file. The format of this file is described in Format of Agents tree definition files below. You can specify an absolute file path, a relative file path from the current directory, or the name of a file in the current directory.

Format of Agents tree definition files

An example of the Agents tree definition file is shown below. Note that you can generate the template file for the Agents tree definition file by executing the jpcconf agttree export command with the -template option. The template file is useful when you create your Agents tree definition file.

Example of an Agents tree definition file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tree SYSTEM "agttree_param.dtd">

<tree owner="pfm-user">
    <folder name="Test Company">
        <folder name="Business Department">
            <agent name="7A1inst_BD[tHOST_01@host_111]"/>
        </folder>
        <folder name="Development Department">
            <agent name="7A1inst_DD[tHOST_02@host_111]"/>
            <agent name="7A1inst_DD[tHOST_03@host_111]"/>
        </folder>
        <agent name="TA1host_111"/>
    </folder>
    <agent name="TA1host_999"/>
</tree>

With the above example file, the following Agents tree is created:

Descriptive conventions

The following provides the descriptive conventions for the Agents tree definition file:

The tree can have a maximum of eight hierarchical levels. In the root level and each folder, you can create a maximum of 64 folders and a maximum of 128 agents.

Element names and attribute values consisting of only spaces are assumed to be omitted. Any spaces before and after element names and attribute values are ignored.

If nonprintable characters are used in an element name or attribute value, an error occurs.

The DOCTYPE declaration in the file is fixed. In the declaration, always specify the name of the DTD file that contains file descriptive definitions. This command supports the following DTD file:

agttree_param.dtd

In XML, a less-than (<) sign and other characters have special meanings. If you use these characters as ordinary characters, you must follow the notations prescribed by the XML specifications.

For example, to use a less-than sign (<), specify &lt;. To use a greater-than sign (>), specify &gt;.

XML tag specifications

tree

Item

Description

Description

The tree element indicates a top (root) node in an Agents tree.

Specifiable value

None

Omissible

No

Attribute

owner

Specifies the name of the user who owns the Agents tree settings. This attribute is required.

You can specify a string of 1 to 16 bytes, consisting of single-byte alphanumeric characters, spaces, and the symbols listed below. Alphabetic characters are not case sensitive.

! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

Parent element

None

Child element

folder (Multiple instances can be specified.)

agent (Multiple instances can be specified.)

folder

Item

Description

Description

The folder element indicates a folder node in an Agents tree.

Specifiable value

None

Omissible

Yes

Attribute

name

Specifies a folder name. This attribute is required.

The name can have 1 to 64 double-byte and/or single-byte characters.

Parent element

tree, folder

Child element

folder (Multiple instances can be specified.)

agent (Multiple instances can be specified.)

agent

Item

Description

Description

The agent element indicates an agent node in an Agents tree.

Specifiable value

None

Omissible

Yes

Attribute

name

Specifies a service ID as an agent name. This attribute is required. The value of this attribute must be 1 to 258 bytes long.

For the product ID part, specify the product ID of PFM - Agent or PFM - RM. For the function ID part, specify A.

Parent element

tree, folder

Child element

None

Notes

You can execute this command only when the View Server service is running.

If the Agents tree definition file includes PFM - Agent or PFM - RM products that PFM - Manager cannot recognize, the command processing is interrupted regardless of whether the -nocheck option is specified. If the command processing is interrupted for this reason, make sure that the PFM - Agent or PFM - RM products specified in the file are registered in PFM - Manager. For details about the registration procedure, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Reference note

The terms PFM - Agent or PFM - RM products that PFM - Manager cannot recognize refer to agents whose product ID does not exist. Therefore, if the host TA1hostA is specified in the Agents tree definition file, the command does not fail in an environment in which that host does not exist even when the -nocheck option is specified. This is because the product ID of T is correct.

If you want to include non-ASCII characters in the Agents tree definition file, use only UTF-8, Shift-JIS, EUC-JP, or GB180030 encoding. In this case, in the XML declaration part in that file, set the encoding attribute to UTF-8, Shift_JIS, EUC-JP, or GB180030. Note that, if the Agents tree definition file includes only ASCII characters, specify UTF-8, Shift_JIS, EUC-JP, or GB180030 as the value of the encoding attribute in the XML declaration.

The following table describes specifiable encoding values for each encoding type of the Agents tree definition file.

Encoding of file

Specifiable values for the encoding attribute

UTF-8

Shift_JIS

EUC-JP

GB180030

ASCII

Y

Y

Y

Y

UTF-8

Y

N

N

N

Shift-JIS

N

Y

N

N

EUC-JP

N

N

Y

N

GB180030

N

N

N

Y

Legend:

Y: Specifiable

N: Not specifiable

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

An attempt was made to execute the command on the PFM - Base host, but the command can only be executed on the PFM - Manager host. Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The definition file contains errors.

11

Processing was canceled by the user (N was returned as the response to a query).

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Usage example

This example imports Agents tree definition information to the View Server service.

# jpcconf agttree import -f agttree_def.xml

jpcconf bgdef check

Format

jpcconf bgdef check     {-f business-group-definition-file-name
                         [-lhost logical-host-name | -syntax]
                         | -im directory-name}

Function

The jpcconf bgdef check command checks the contents of the business group definition file. This command checks the following items:

Whether there are syntax errors

Whether there are already business groups with the same names as specified business groups

Whether specified hosts already belong to other business groups in the Performance Management system

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f business-group-definition-file-name

Specifies the name of the business group definition file to be checked. You can specify either a relative path or absolute path for the file.

The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ / @ [ ]

If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

Note, however, that you do not need to specify this option even when the host on which this command is executed belongs to a logical host if the -syntax or -im option is specified.

-syntax

Specify this option to check only for syntax errors.

-im directory-name

Specify this option to check the business groups defined in JP1/IM. For directory-name, specify the output destination directory name that was specified for the -o option when the jcfexport command was executed to output the business group definition information in JP1/IM 10-00 or later. If the -im option is specified, the command checks only for syntax errors.

You can specify either a relative path or absolute path of the directory. Note that if the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks (").

Format of business group definition files

See Format of business group definition files in the description of the jpcconf bgdef import command.

Notes

PFM - Manager must be running when you execute this command except when you specify the -syntax or -im option.

Access control by business group must be enabled when you execute this command except when you specify the -syntax or -im option.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

A startup or termination command, or other setup command, has been executed on the same machine.

5

The command was executed on a host that was not the PFM - Manager host.

6

The business group definition file contains errors.

11

Processing was interrupted by a user or the system.

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running (when the -syntax or -im option is not specified).

102

The specified logical host has not been set up.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

254

Access control by business group is disabled (when the -syntax or -im option is not specified).

255

An unexpected error occurred.

Usage example

This example checks a business group definition file.

#jpcconf bgdef check -f C:\tmp\bgdef.cfg

jpcconf bgdef delete

Format

jpcconf bgdef delete     -group business-group-name
                         [-lhost logical-host-name]
                         [-noquery]

Function

The jpcconf bgdef delete command deletes the definition information of a business group or business groups.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-group business-group-name

Specifies the name of the business group whose definition information is to be deleted.

For business-group-name, specify a string of 1 to 255 bytes, consisting of double-byte characters, single-byte characters, and the symbols below. Alphabetic characters are case sensitive.

! " # $ % & ' ( ) + - . : ; < = > @ [ \ ] ^ _ ` { | } ~

If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols.

You can use wildcard characters to specify multiple business group names.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

Note

You can execute this command only when PFM - Manager is running.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

A startup or termination command, or other setup command, has been executed on the same machine.

5

The command was executed on a host that was not the PFM - Manager host. Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

One or more specified business groups do not exist.

11

Processing was interrupted by a user or the system.

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

254

Access control by business group is disabled.

255

An unexpected error occurred.

Usage example

This example deletes all business groups whose names begin with group.

#jpcconf bgdef delete -group group*

jpcconf bgdef display

Format

jpcconf bgdef display     -group business-group-name
                          [-lhost logical-host-name]

Function

The jpcconf bgdef display command displays the definition information of a business group or business groups.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-group business-group-name

Specifies the name of the business group for which definition information is to be displayed.

For business-group-name, specify a string of 1 to 255 bytes, consisting of double-byte characters, single-byte characters, and the symbols below. Alphabetic characters are case sensitive.

! " # $ % & ' ( ) + - . : ; < = > @ [ \ ] ^ _ ` { | } ~

If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols.

You can use wildcard characters to specify multiple business group names.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

Note

You can execute this command only when PFM - Manager is running.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

A startup or termination command, or other setup command, has been executed on the same machine.

5

The command was executed on a host that was not the PFM - Manager host.

6

One or more specified business groups do not exist.

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

254

Access control by business group is disabled.

255

An unexpected error occurred.

Usage example 1

This example is a command that you can execute when accounts are managed in PFM authentication mode.

#jpcconf bgdef display -group group*

The following shows an example of the command execution results.

KAVE05444-I Business group definitions will now be displayed.
Business Group Name:groupA
Host Name:
  HostA
  HostB

Business Group Name:groupB
Host Name:
  HostC

Business Group Name:groupC
Host Name:

KAVE05445-I Business group definitions were successfully displayed.

Usage example 2

This example is a command that you can execute when accounts are managed in JP1 authentication mode.

#jpcconf bgdef display -group group*

The following shows an example of the command execution results.

KAVE05444-I Business group definitions will now be displayed.
Business Group Name    :groupA
JP1 Resource Group Name:resourceA
Host Name:
  HostA
  HostB

Business Group Name    :groupB
JP1 Resource Group Name:
Host Name:
  HostC

Business Group Name    :groupC
JP1 Resource Group Name:resourceC
Host Name:

KAVE05445-I Business group definitions were successfully displayed.

jpcconf bgdef export

Format

jpcconf bgdef export   -f business-group-definition-file-name
                       {-group business-group-name [-lhost logical-host-name]
                        | -template}
                       [-noquery | -skip]

Function

The jpcconf bgdef export command exports the definition information of a business group or business groups to the specified file as a business group definition file. This command can also generate the template file for business group definition files, rather than the business group definition file that contains the current definition information.

An exported business group definition file can be specified in the jpcconf bgdef import command as an input file.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f business-group-definition-file-name

Specifies the name of the business group definition file to be exported. You can specify either a relative path or absolute path for the file.

The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ / @ [ ]

If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols.

-group business-group-name

Specifies the name of the business group for which definition information is to be exported.

For business-group-name, specify a string of 1 to 255 bytes, consisting of double-byte characters, single-byte characters, and the symbols below. Alphabetic characters are case sensitive.

! " # $ % & ' ( ) + - . : ; < = > @ [ \ ] ^ _ ` { | } ~

If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols.

You can use wildcard characters to specify multiple business group names.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

Note, however, that you do not need to specify this option even when the host on which this command is executed belongs to a logical host if the -template option is specified.

-template

Specify this option to generate the template file for business group definition files. In the template file, all lines are commented out with hash marks (#). Edit this file according to your needs.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

If the business group definition file specified for the -f option already exists, that file will be overwritten by the new file.

-skip

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

If the business group definition file specified for the -f option already exists, the command skips the updating of the file.

Format of business group definition files

See Format of business group definition files in the description of the jpcconf bgdef import command.

Note that although the generated template file includes all label names, any exported business group definition file includes only the names of labels whose values exist in the business group definition information.

Notes

PFM - Manager must be running when you execute this command except when you specify the -template option.

Access control by business group must be enabled when you execute this command except when you specify the -template option.

The value of the LANG environment variable for the shell that is used to execute the command determines the encoding of the business group definition file and the Business Group Definition File Code label's value in that file. If the business group definitions that you want to export include non-ASCII characters, make sure that the value of the relevant LANG environment variable is appropriate before you execute this command.

The following table describes the encoding of the file and the value of the Business Group Definition File Code label for each value of the LANG environment variable. If the value of the LANG environment variable is not described in the following table, the command assumes that LANG environment variable is set to C.

OS

Language

LANG value

Encoding

Value of Business Group Definition File Code

Windows

Japanese

--

Shift-JIS

Shift_JIS

English

ASCII

C

Chinese(Simplified Chinese)

GB18030

GB18030

Linux

Japanese

ja_JP.UTF-8

UTF-8

UTF-8

ja_JP.utf8

English

C

ASCII

C

Chinese(Simplified Chinese)

zh_CN.gb18030

GB18030

GB18030

zh_CN.UTF-8

UTF-8

UTF-8

zh.CN.utf8

Solaris

Japanese

ja_JP.PCK

Shift-JIS

Shift_JIS

ja

EUC-JP

EUC-JP

japanese

English

C

ASCII

C

Chinese(Simplified Chinese)

zh_CN.GB18030

GB18030

GB18030

zh_CN.GB18030@pinyin

zh_CN.GB18030@radical

zh_CN.GB18030@stroke

zh.UTF-8

UTF-8

UTF-8

zh_CN.UTF-8

zh_CN.UTF-8@pinyin

zh_CN.UTF-8@radical

zh_CN.UTF-8@stroke

AIX

Japanese

Ja_JP.IBM-932

Shift-JIS

Shift_JIS

Ja_JP

ja_JP.IBMeucJP

EUC-JP

EUC-JP

ja_JP

English

C

ASCII

C

Chinese(Simplified Chinese)

Zh_CN

GB18030

GB18030

Zh_CN.GB18030

ZH_CN

UTF-8

UTF-8

ZH_CN.UTF-8

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

A startup or termination command, or other setup command, has been executed on the same machine.

5

The command was executed on a host that was not the PFM - Manager host.

6

One or more specified business groups do not exist.

11

Processing was interrupted by a user or the system.

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running (when the -template option is not specified).

102

The specified logical host has not been set up.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

254

Access control by business group is disabled (when the -template option is not specified).

255

An unexpected error occurred.

Usage example 1

This example exports the definition information for business group groupA.

#jpcconf bgdef export -f C:\tmp\bgdef.cfg -group groupA

Usage example 2

This example generates the template file for business group definition files.

#jpcconf bgdef export -f C:\tmp\bgdef.cfg -template

jpcconf bgdef import

Format

jpcconf bgdef import     {-f business-group-definition-file-name
                         [-noquery | -skip] | -im directory-name}
                         [-lhost logical-host-name]

Function

The jpcconf bgdef import command imports business group definition information from the specified file, and defines business groups with the imported information.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f business-group-definition-file-name

Specifies the name of the business group definition file to be imported. You can specify either a relative path or absolute path for the file.

The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ / @ [ ]

If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

If business groups whose names are specified in the file have already been created, the definition information of these business groups will be updated. If business groups whose names are specified in the file have not been created, the definition information of these business groups will be created.

-skip

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

If business groups whose names are specified in the file have already been created, the definition information of these business groups will not be updated. The business groups that have not been created yet will not be created, either.

-im directory-name

Specify this option to import the business groups defined in JP1/IM. For directory-name, specify the output destination directory name that was specified for the -o option when the jcfexport command (with the -a or -g option specified) was executed to output the business group definition information in JP1/IM 10-00 or later.

You can specify either a relative path or absolute path of the directory. Note that if the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks (").

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

Format of business group definition files

The format of business group definition files is described below. Lines in this file can be commented out by prefixing a hash mark (#) to them.

The template file for business group definition files can be generated by executing the jpcconf bgdef export command with the -template option. The template file is useful when you create your business group definition file.

Items that can be specified

Business Group Definition File Version label

Specifies the version of the business group definition file. This label must be specified at the beginning of the file.

Table 2‒11: Business Group Definition File Version label

Item

Description

Description

The version of the business group definition file

Specifiable value

0001

Omissible

No

Business Group Definition File Code label

Specifies the encoding of the business group definition file. This label must immediately follow the Business Group Definition File Version label.

Table 2‒12: Business Group Definition File Code label

Item

Description

Description

Encoding of the business group definition file

Specifiable value

One of the following values can be specified according to the characters contained in the file:

Shift_JIS

Specify this value if the file contains double-byte Shift-JIS characters and single-byte ASCII characters.

EUC-JP

Specify this value if the file contains double-byte EUC characters and single-byte ASCII characters.

UTF-8

Specify this value if the file contains double-byte UTF-8 characters and single-byte ASCII characters.

C

Specify this value if the file contains single-byte ASCII characters.

GB18030

Specify this value if the file contains double-byte GB18030 characters and single-byte ASCII characters.

Do not add the byte order mark (BOM) when you use the UTF-8 encoding. If you do so, an error occurs.

Omissible

No

Business Group Data section

Specifies the definition of a business group. To define multiple business groups, create a Business Group Data section and specify a definition for each business group. At least one Business Group Data section must be specified.

Table 2‒13: Business Group Name label

Item

Description

Description

The name of a business group

Specifiable value

You can specify a string of 1 to 255 bytes, consisting of double-byte characters, single-byte characters, and the following symbols:

! " # $ % & ' ( ) + - . : ; < = > @ [ \ ] ^ _ ` { | } ~

Alphabetic characters are case sensitive. Heading and trailing single-byte spaces are ignored. If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks (").

If you specify double-byte characters, make sure that you use the same encoding that is specified for the Business Group Definition File Code label.

Omissible

No

Table 2‒14: JP1 Resource Group Name label

Item

Description

Description

The name of a JP1 resource group

Note:

You do not need to specify this label if the user account is authenticated in PFM authentication mode. If you specify this label in PFM authentication mode, the specification is ignored. However, if the label is specified in an incorrect format, an error occurs.

Specifiable value

You can specify a string of 1 to 64 bytes, consisting of single-byte alphanumeric characters and the following single-byte symbols:

! # $ % & ' ( ) * - . @ \ ^ _ ` { } ~

Note that you cannot specify the following strings:

The string JP1_PFM

An asterisk (*)

Alphabetic characters are case sensitive. Heading and trailing single-byte spaces are ignored.

Omissible

Yes

Table 2‒15: Host Name label

Item

Description

Description

The names of hosts that belong to a business group

Specifiable value

You can specify a string of 1 to 128 bytes, consisting of single-byte alphanumeric characters and the following single-byte symbols:

! $ + - @ [ ] _ ` { } ~

Note that you cannot specify the following strings:

The string localhost (regardless of the case)

Any string in IP address format

Any string that begins with a hyphen (-)

Alphabetic characters are case sensitive. Heading and trailing single-byte spaces are ignored.

To specify two or more host names, use commas (,) to separate them. Single-byte spaces before and after a comma (,) are ignored. Do not add a comma (,) at the end of the last entry. If you do so, an error occurs.

Note that a host cannot belong to two or more business groups. Specify hosts that do not belong to any business groups in the Performance Management system.

Omissible

Yes

The following shows an example of specifying settings in a business group definition file.

Example of specifying settings in a business group definition file:

Business Group Definition File Version=0001
Business Group Definition File Code=EUC-JP

[Business Group Data]
Business Group Name=Group A
JP1 Resource Group Name=resourceA
Host Name=win01,win02,win03

[Business Group Data]
Business Group Name=Group B
JP1 Resource Group Name=resourceB
Host Name=sun01,sun02,sun03

[Business Group Data]
Business Group Name=Group C
JP1 Resource Group Name=resourceC
Host Name=win04

Notes

You can execute this command only when PFM - Manager is running.

If multiple business groups are defined in the specified business group definition file, the definition information of these business groups is collectively imported. If the file contains at least one error, importing of definition information for all business groups will be canceled.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

A startup or termination command, or other setup command, has been executed on the same machine.

5

The command was executed on a host that was not the PFM - Manager host. Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The business group definition file contains errors.

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

254

Access control by business group is disabled.

255

An unexpected error occurred.

Usage example 1

This example imports a business group definition file.

jpcconf bgdef import -f C:\tmp\bgdef.cfg

Usage example 2

This example imports the business groups that are defined in JP1/IM.

jpcconf bgdef import -im C:\tmp

jpcconf bgdef list

Format

jpcconf bgdef list       [-lhost logical-host-name]

Function

The jpcconf bgdef list command lists business group names.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. If this option is omitted, the command will be executed on the physical host.

Note

You can execute this command only when PFM - Manager is running.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

A startup or termination command, or other setup command, has been executed on the same machine.

5

The command was executed on a host that was not the PFM - Manager host.

100

The Performance Management environment is invalid.

101

A service that is prerequisite for executing this command is not running.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

254

Access control by business group is disabled.

255

An unexpected error occurred.

Usage example

This example lists business group names.

#jpcconf bgdef list

The following shows an example of the execution results of the above command.

groupA
groupB
groupC

jpcconf db define

Format

jpcconf db define    -key service-key
                    [-inst instance-name]
                    [-lhost logical-host-name]
                    [{-sd|-bd|-bs|-pbd|-dd|-id}
                     setting-value[-move]]

Function

The jpcconf db define command changes and displays the settings of the Store service.

You can use this command to change the storage directory for the Store database of the Agent Store or Remote Monitor Store service or to change the maximum generation number and other settings if you back up the Store database.

To change the settings of the Store service, specify -sd, -bd, -bs, -pd, -pbd, -dd, or -id. If you do not specify any of these options, the command displays the settings of the Store service.

The following settings can be displayed:

StoreDir:

Displays the Store directory.

BackupDir:

Displays the backup directory.

BackupSave:

Displays the maximum number of generations for the backup directory.

PartialBackupDir:

Displays the partial backup directory.

DumpDir:

Displays the dump directory.

ImportDir:

Displays the import directory.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the Store service whose settings are to be changed or displayed. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-inst instance-name

Specifies the instance name of the Store service whose settings are to be changed or displayed. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

You cannot specify this option when the Store service whose settings you want to change or display is on a single-instance agent.

-lhost logical-host-name

Specifies the logical host name of the Store service whose settings are to be changed or displayed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

When you omit this option, the settings of the Store service on the physical host are changed or displayed.

-sd|-bd|-bs|-pbd|-dd|-id

Use one of these options to specify the Store service settings you want to change. The options correspond to the label names in the jpcsto.ini file as shown below. By executing the jpcconf db define command, you can change the value of the corresponding label name in the jpcsto.ini file.

Option name

Corresponding label name in jpcsto.ini file

Description

-sd

Store Dir

Changes the Store directory for the Store database.

-bd

Backup Dir

Changes the backup directory for the Store database.

-bs

Backup Save

Changes the number of generations for the backup directory for the Store database.

-pbd

Partial Backup Dir

Changes the partial backup directory for the Store database.

-dd

Dump Dir

Changes the dump directory for the Store database.

-id

Import Dir

Changes the import directory for the Store database.

For setting-value, you can specify only a directory on a logical disk.

The value you can specify for setting-value differs as shown below, depending on the Store version of the target Store service:

Option name

Store version

1.0

2.0

-sd

The string can be a maximum of 127 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < > |

Specify the full path or a relative path.

The string can be a maximum of 214 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < > |

Specify the full path or a relative path.

You must specify an existing directory.

-bd

The string can be a maximum of 127 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < > |

Specify the full path or a relative path.

The string can be a maximum of 211 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < >

Specify the full path or a relative path.

You must specify an existing directory.

-bs

Integer from 1 to 9

Integer from 1 to 9

-pbd

Cannot be specified.

The string can be a maximum of 214 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < >

Specify the full path or a relative path.

You must specify an existing directory.

-dd

The string can be a maximum of 127 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < > |

Specify the full path or a relative path.

The string can be a maximum of 127 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < >

Specify the full path or a relative path.

-id

Cannot be specified.

The string can be a maximum of 222 bytes long and can consist of single-byte alphanumeric characters, spaces, and symbols. However, the following symbols cannot be used:

; , * ? ' " < >

Specify the full path or a relative path.

You must specify an existing directory.

-move

Specifies whether to copy the contents of the current directory to the new directory when you change the settings of a Store service directory. The -move option cannot be specified together with certain options, as shown below:

Option

Whether -move option can be specified

-sd

Yes

-bd

Yes

-bs

No

-pbd

Yes

-dd

No

-id

Yes

Legend:

Yes: The -move option can be specified.

No: The -move option cannot be specified.

When you omit the -move option, only the settings of the current directory are changed.

If the -move option is specified, the following restrictions are placed on the directory that you specify:

The directory must be empty.

A subdirectory of the directory that is currently set cannot be specified.

Note

Before you change the Store service settings, make sure that the PFM - Agent or PFM - RM service specified by service-key has stopped. However, you do not need to stop that service when you only display the Store service settings.

Return values

0

The command ended normally.

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

4

The specified service has not stopped.

5

The specified PFM - Agent or PFM - RM has not been installed.

12

Importing is disabled for the specified version of the Store service.

100

The environment for Performance Management is invalid.

102

The specified logical host or instance is not set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The file or directory cannot be accessed.

255

An unexpected error occurred.

Usage example 1

The following example changes the settings of the Store service:

> jpcconf db define -key Windows -sd d:\store
KAVE05856-I Updating the configuration information of the Store database ended normally. (servicekey=Windows, label=Store Dir)

jpcconf db display

Format

Format 1

jpcconf db display   [-key service-key[-inst instance-name]]
                     [-lhost logical-host-name]

Format 2

jpcconf db display    -d backup-directory

Function

The jpcconf db display command displays information about the Store service or backup data.

This command can also check whether the Store version is 1.0 or 2.0.

The following describes the functional differences between Format 1 and Format 2. For Format 1, Store service information is displayed. For Format 2, information about the specified backup data is displayed. The information displayed for each format is as follows.

Format 1

Contents displayed

Description

service-key

Indicates the service key of the agent.

instance-name

Indicates an instance name for multi-instance agents.

This element is "" (empty string) for single-instance agents.

data-model-version

Displays a hyphen (-) when the target agent is 07-00 or earlier.

Displays the data model version of the target Store service when the target agent is 08-00 or later.

Store-version

Indicates the Store version.

If the information displayed in the data section is less than the following specified length, the remaining length is created by spaces.

service-key: 6 bytes

instance-name: 15 bytes

data-model-version: 14 bytes

Store-version: 9 bytes

Format 2

Contents displayed

Description

service-key

Indicates the service key of the agent.

data-model-version

Displays a hyphen (-) when the Store version is 1.0.

Displays the data model version of the specified backup data when the Store version is 2.0.

Store-version

Indicates the Store version.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base#

PFM - RM

#

This can only be executed when the -d option is specified.

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the Store service whose information you want to display. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-inst instance-name

Specifies the instance name of the Store service whose information you want to display. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

This option must be specified when the target Store service is on a multi-instance agent. You cannot specify this option for single-instance agents.

-lhost logical-host-name

Specifies the logical host name of the Store service whose information you want to display. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

If you omit this option, setup is performed for the Store service on the physical host.

-d backup-directory

Specifies the name of the backup directory containing the backup data whose information you want to display. You cannot specify the following characters in the backup directory name:

; , * ? ' " < > |

Use 1 to 214 bytes (but none of the above characters) to specify a relative path or the full path. When you specify a relative path, specify the path from the directory that is the current directory when the command is executed.

Notes

When the target instance of PFM - Agent is 07-00 or earlier, the data model version is not displayed.

When you execute this command on the standby server in a logical host environment to display the information about the Store service, a hyphen (-) is displayed for the Store version and the data model version.

Return values

0

The command ended normally.

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

5

The specified PFM - Agent or PFM - RM has not been installed.

100

The environment for Performance Management is invalid.

102

The specified logical host or instance is not set up.

104

The specified Store service is being backed up or is exporting data.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The file or directory cannot be accessed.

254

The command ended normally. As a result of command execution, the Store version was 1.0 for at least one of the specified services.

255

An unexpected error occurred.

Usage example 1

The following example displays information about all the services on the physical host:

> jpcconf db display

Key Instance Name DataModel Ver Store Ver

----------- --------------- -------------- ---------

EAP inst1 4.0 2.0

EAP inst2 4.0 1.0

EAP inst3 4.0 2.0

Windows 5.0 1.0

SR 4.0 2.0

#

In the above example, EAP is a multi-instance agent whose version is 08-11, Windows is a single-instance agent whose version is 08-11, and SR is a single-instance agent whose version is 08-50.

Usage example 2

The following example displays information about the backup data of Store 1.0 in the backup directory:

> jpcconf db display -d "d:\backup01"

Key DataModel Ver Store Ver

----------- --------------- ---------

EAP - 1.0

Usage example 3

The following example displays information about the backup data of Store 2.0 in the backup directory:

> jpcconf db display -d "d:\backup02"

Key DataModel Ver Store Ver

----------- --------------- ---------

EAP 5.0 2.0

jpcconf db vrset

Format

jpcconf db vrset [-ver 2.0|1.0]

-key service-key

[-inst instance-name]

                   [-lhost logical-host-name]
                   [-force]

Function

The jpcconf db vrset command changes the version of the Store database. When this command is executed, Store database data is converted to the specified Store version format. Note that the data retention period is converted to the specified Store version setting.

The Store version is specified by -ver Store-version. Either 2.0 or 1.0 can be specified for Store-version.

When the -ver 2.0 option is specified

Setup is performed with Store version 2.0 functionality.

When you execute this command, the setting for all records of the PD and Pl record types for the deletion period become 10 days.

The retention period for the PI database after setup changes as follows according to the retention period that existed before setup:

Retention period before setup

Retention period after setup

Summary type

Minute-by-minute

(unit: days)

Hourly

(unit: days)

Daily

(unit: weeks)

Weekly

(unit: weeks)

Monthly

(unit: months)

1 minute

1

--

--

--

--

1 hour

1

1

--

--

--

1 day

1

1

1

--

--

2 days

2

2

1

--

--

3 days

3

3

1

--

--

4 days

4

4

1

--

--

5 days

5

5

1

--

--

6 days

6

6

1

--

--

1 week

7

7

1

1

--

1 month

31

31

5

5

1

1 year

366

366

54

54

12

Legend: --: Cannot be specified.

Note that for PFM - Agent 08-11 or later, this is the specified value for each instance of PFM - Agent. For details about the specified value, see the corresponding PFM - Agent manuals.

When the -ver 1.0 option is specified

The Store version is reverted from 2.0 to 1.0.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the Store service. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-inst instance-name

Specifies the instance name of the Store service whose information you want to display. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. This option must be specified when the target Store service is on a multi-instance agent. You cannot specify this option for single-instance agents.

-lhost logical-host-name

Specifies the logical host name of the Store service. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. If you omit this option, setup is performed for the Store service on the physical host.

-force

When this option is specified, no confirmation message is displayed. Note that this option can only be specified, when the -ver 1.0 option is specified.

Notes

When the -ver 2.0 option is specified

Before this command is executed, only the PFM - Agent or PFM - RM service to be set up needs to be stopped. As such, stop the PFM - Agent or PFM - RM service before executing this command.

You should back up data before you execute this command.

Executing this command requires the same amount of free disk space as that being used by the Store database before the command is executed.

Check the retention period after the command is executed. Note that the retention period is changed to 10 days for all the records of the PD and PL record types.

When the -ver 1.0 option is specified

When this command is executed, data is initialized. If any data exists, a confirmation message such as the following is displayed before data is initialized:

KAVE05873-Q If you continue the processing, the Store database will be initialized. Do you want to continue? (Y/N)

Processing continues only when you enter y or Y. However, when the -force option is specified, the command is executed without displaying the confirmation message.

The import directory is not deleted even if this command is executed.

For PFM - Agent or PFM - RM hosts for which Store version 2.0 is a prerequisite, if the -ver 1.0 option is specified and this command is executed, the KAVE05882-E message is displayed and the command terminates. In this case, the Store version cannot be changed from 2.0 to 1.0.

Return values

0

The command ended normally.

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

4

The specified service has not stopped.

5

The specified PFM - Agent or PFM - RM has not been installed.

10

The command is being executed.

11

The user canceled the processing.

12

Version setup or restoration is disabled for the specified version of the Store service.

100

The Performance Management environment is invalid.

102

The specified logical host or instance is not set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The file or directory cannot be accessed.

255

An unexpected error occurred.

jpcconf ha export

Format

jpcconf ha export   -f logical-host-environment-definition-file-name
                    [-noquery]

Function

The jpcconf ha export command exports to a specified file the settings of a Performance Management logical host environment.

This command can be executed only for a Performance Management product that supports logical host operation. PFM - Manager supports logical host operation. For details about logical host operation of a particular PFM - Agent or PFM - RM, see the chapter in the relevant PFM - Agent or PFM - RM manuals that describes cluster system operations.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f logical-host-environment-definition-file-name

Specifies the name of the file to which the settings of the logical host environment are to be exported. If the file name contains spaces, enclose the entire name in double quotation marks (").

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

If a file with the same name as the specified file name already exists, a KAVE05399-I message is output and the file is updated.

Notes

To synchronize the environments of the executing node and the standby node in a cluster system, you execute this command at the executing node to export the environment definition file of the logical host environment in the following cases:

The logical host environment has just been set up or settings have been changed.

Setup of the logical host environment was removed.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

You do not need to stop Performance Management program services on the logical host when you execute this command.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

10

The command is being executed.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Other values

The command terminated abnormally.

Usage example

This example exports the settings of a configured logical host environment to a logical host environment definition file (jp1-ha1.conf):

jpcconf ha export -f jp1-ha1.conf

jpcconf ha import

Format

jpcconf ha import   -f logical-host-environment-definition-file-name
                    [-noquery]

Function

The jpcconf ha import command imports to the standby node a logical host environment definition file exported from the executing node.

This command can be executed only for a Performance Management product that supports logical host operation. PFM - Manager supports logical host operation. For details about logical host operation of a particular PFM - Agent or PFM - RM, see the chapter in the relevant PFM - Agent or PFM - RM manuals that describes cluster system operations.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f logical-host-environment-definition-file-name

Specifies the name of a logical host environment definition file that was exported by the executing node. If the file name contains spaces, enclose the entire name in double quotation marks (").

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

The command behavior changes in various situations, as described below:

If logical host environments other than the ones specified in the import file exist on the import destination logical host:

A KAVE05400-I message is output. The command continues processing without deleting the existing logical host environments.

If new logical host environments have been added to the import file:

A KAVE05401-I message is output. The command creates the new logical host environments.

If the services file includes port numbers that are not specified in the import file:

A KAVE05402-I message is output. The command continues processing without deleting those port numbers from the services file.

If new port numbers have been added to the import file:

A KAVE05403-I message is output. The command adds those port numbers to the services file.

If port numbers for services specified in the import file are different from the port number of those services in the services file:

A KAVE05404-I message is output. The command changes the port numbers in the services file.

Notes

To synchronize the environments of the executing node and the standby node in a cluster system, you execute this command at the standby node to import the environment definition file of the logical host environment in the following cases:

The logical host environment at the executing node has just been set up or its settings have been changed.

Setup of the logical host environment was removed at the executing node.

Note that if executing this command imports an environment definition file of a logical host environment whose settings have been removed, any differences in the previous environment definition from the imported environment definition are deleted from the logical host settings of the executing node.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

If you want to use the health check function, you must enable the status management function of the host that imports the definition file for the logical host environment.

When the functionality for setting monitoring-host names is used (the value of Get Host Mode in the Common Section section of the jpccomm.ini file is 1 or 2), the same name as the host name set for the monitoring host name cannot be set for the logical host name.

Before you execute this command, stop Performance Management program services on the logical host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

10

The command is being executed.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Other values

The command terminated abnormally.

Usage example

This example imports to the standby machine a logical host environment definition file (jp1-ha1.conf) that was exported by the executing machine:

jpcconf ha import -f jp1-ha1.conf

jpcconf ha list

Format

jpcconf ha list    -key service-key
                  [-lhost logical-host-name]

Function

The jpcconf ha list command displays the settings for a Performance Management logical host environment.

This command can be executed only for a Performance Management product that supports logical host operation. PFM - Manager supports logical host operation. For details about logical host operation of a particular PFM - Agent or PFM - RM, see the chapter in the relevant PFM - Agent or PFM - RM manuals that describes cluster system operations.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the Performance Management program whose logical host environment settings are to be displayed. A product name can also be specified when the product name display functionality is enabled.

You can specify the following in service-key:

all: Specifies all Performance Management services set up on the specified logical host.

Manager or mgr: Specifies the PFM - Manager services (including the Action Handler service).

Service key of a PFM - Agent or PFM - RM service: Displays a particular PFM - Agent or PFM - RM service (including the Action Handler service). For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

AH or act (service key of the Action Handler service) cannot be specified.

When one of the following values is specified for the service key, the logical host environment settings for the Performance Management program service are displayed:

Manager or mgr

Service key of the PFM - Agent service

Service key of the PFM - RM service

Specifying all in service-key displays the logical host environment settings for all Performance Management services set up on the specified logical host. Specifying the service key of a Performance Management service that does not support logical host operation results in an error.

-lhost logical-host-name

Specifies the host name of the logical host environment. You can omit this option.

Specifying a logical host name displays only the information about the specified logical host. If you omit this option, the command displays information about all logical hosts. If the specified logical host name has not been set up, an error results.

Notes

This command can display information about logical hosts even for standby nodes or when the shared disk cannot be accessed.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

10

The command is being executed.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Other values

The command terminated abnormally.

Usage example

This example displays a list of logical hosts that have been set up:

jpcconf ha list -key all

The following is an output example:

jpcconf ha setup

Format

jpcconf ha setup    -key service-key
                    -lhost logical-host-name
                   [-d environment-directory-name]

Function

The jpcconf ha setup command creates a Performance Management logical host environment.

Executing this command sets up a logical host environment.

This command can be executed only for a Performance Management product that supports logical host operation. PFM - Manager supports logical host operation. For details about the logical host operation of a particular PFM - Agent or PFM - RM, see the chapter in the relevant PFM - Agent or PFM - RM manuals that describes cluster system operations.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the Performance Management program for which a logical host environment is to be created. A product name can also be specified when the product name display functionality is enabled.

You can specify the following in service-key:

all: Specifies all Performance Management services installed on the current node that support logical host operation.

Manager or mgr: Specifies the PFM - Manager services (including the Action Handler service).

Service key of a PFM - Agent or PFM - RM service: Specifies a particular PFM - Agent or PFM - RM service (including the Action Handler service). For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

AH or act (service key of the Action Handler service) cannot be specified.

When one of the following values is specified for the service key, the logical host environment settings for the Performance Management program service are displayed:

Manager or mgr

Service key of the PFM - Agent service

Service key of the PFM - RM service

Specifying all in service-key creates a logical host environment for all Performance Management services installed on the current node that support logical host operation. Specifying the service key of a Performance Management service that does not support logical host operation results in an error.

Executing this command creates automatically a logical host environment in which there is one Action Handler service for each logical host.

-lhost logical-host-name

Specifies a logical host name for the logical host environment being created.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. The space character and the following symbols cannot be specified:

/ \ : ; * ? ' " < > | & = ,

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

The specified logical host name is used as the host name when a Performance Management service on the logical host is communicating.

-d environment-directory-name

Specifies the directory in which the execution environment of the logical host is to be created. This is the name of the directory that will store the files of the logical host environment. Specify a directory on a shared disk that manages the cluster software for inheriting files when a failover occurs. If the specified directory is not on the shared disk managed by the cluster software, no processing will be executed. You must always specify this directory name when you create a new logical host environment. You can omit this option when you are adding services to an existing logical host environment.

For environment-directory-name, specify a string 1 to 80 bytes, consisting of alphanumeric characters and symbols. However, the following symbols cannot be specified:

; , * ? ' " < > |

A relative path cannot be used; you must use the absolute path.

Executing this command creates the jp1pc directory in the specified directory and creates a logical host environment file in that directory.

Only one environment directory can be specified on a logical host. To set up multiple Performance Management services on a single logical host, you must use the same directory.

In a UNIX environment, space characters cannot be specified. To specify a directory name that contains spaces in a Windows environment, enclose the entire directory name in double quotation marks (").

Notes

Because the logical host environment file is created on a shared disk, before you execute this command to create a new logical host environment you must place the shared disk online (mount the disk in UNIX). If the command cannot access the shared disk, it will result in an error and the creation request will be cancelled. In this case, the logical host environment will not be created.

Before you execute this command, stop all Performance Management services, including the physical host and each logical host on the node.

In a Windows environment, the upper-directory access permissions are passed to the jp1pc directory created in the environment directory and all files in the logical host environment.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

When you create a logical host environment for PFM - Manager, the health check function of PFM - Manager in the logical host environment is disabled (default) regardless of the setting of the health check function (enabled or disabled) specified for PFM - Manager in the physical host environment. If you want to use the health check function of PFM - Manager in the logical host environment, you must set up the health check function again for that environment.

When the functionality for setting monitoring-host names is used (the value of Get Host Mode in the Common Section section of the jpccomm.ini file is 1 or 2), the same name as the host name set for the monitoring host name cannot be set for the logical host name.

If you will create a logical host environment for PFM - Manager when the monitoring suspension function is enabled, before you execute this command, resume the monitoring by all Performance Management programs, including the Performance Management programs for the physical and logical hosts on the node.

If you create a logical host environment for PFM - Agent when the monitoring suspension function is enabled, the monitoring suspension settings for the physical host environment are not inherited.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

10

The command is being executed.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Other values

The command terminated abnormally.

Usage example

This example sets up a logical host environment for PFM - Manager, with jp1-ha1 as the logical host name and S:\jp1 as the environment directory name:

jpcconf ha setup -key Manager -lhost jp1-ha1 -d S:\jp1

jpcconf ha unsetup

Format

jpcconf ha unsetup  -key service-key
                    -lhost logical-host-name

Function

The jpcconf ha unsetup command deletes a Performance Management logical host environment.

This command can be executed only for a Performance Management product that supports logical host operation. PFM - Manager supports logical host operation. For details about the logical host operation of a particular PFM - Agent or PFM - RM, see the chapter in the relevant PFM - Agent or PFM - RM manuals that describes cluster system operations.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the Performance Management program whose logical host environment is to be deleted. A product name can also be specified when the product name display functionality is enabled.

You can specify the following in service-key:

all: Specifies all Performance Management services set up on the specified logical host.

Manager or mgr: Specifies the PFM - Manager services (including the Action Handler service).

Service key of a PFM - Agent or PFM - RM service: Deletes a particular PFM - Agent or PFM - RM service (including the Action Handler service). For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

act (service key of the Action Handler service) cannot be specified.

When one of the following values is specified for the service key, the logical host environment settings for the Performance Management program service are displayed:

Manager or mgr

Service key of the PFM - Agent service

Service key of the PFM - RM service

Specifying all in service-key deletes the logical host environment for all Performance Management services set up on the specified logical host. Specifying the service key of a Performance Management product that does not support logical host operation results in an error.

If this command is executed to delete all Performance Management services that have been set up on the specified logical host, the logical host environment including the Action Handler service is deleted automatically.

-lhost logical-host-name

Specifies the host name of the logical host environment to be deleted.

If the specified logical host name has not been set up, an error results.

To check the logical host environments that have been set up, use jpcconf ha list -key all.

Notes

Because the logical host environment file is deleted from a shared disk, before you execute this command to delete a logical host environment you must place the shared disk online (mount the disk in UNIX). If the command cannot access the shared disk, it will delete only the logical host settings information and the Windows service.

Before you execute this command, stop all Performance Management services, including the physical host and each logical host on the node.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

When you delete the logical host environment of PFM - Manager, the setting of the health check function (enabled or disabled) of PFM - Manager in the physical host environment inherits the setting that existed before the logical host environment was created.

When you delete the logical host environment of PFM - Manager, the monitoring suspension settings for the physical host environment inherit the settings that existed before the logical host environment was created.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

10

The command is being executed.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Other values

The command terminated abnormally.

Usage example

This example deletes the logical host environment for the PFM - Manager whose logical host name is jp1-ha1:

jpcconf ha unsetup -key Manager -lhost jp1-ha1

jpcconf hc disable

Format

jpcconf hc disable

Function

The jpcconf hc disable command disables the health check function. When a logical host environment has been created for PFM - Manager, the command disables the health check function of PFM - Manager in the logical host environment.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Notes

You cannot execute this command if a Performance Management service is running on the physical host or a logical host.

If you have disabled the health check function, the health check agent does not start when PFM - Manager starts.

If the health check function is disabled for PFM - Manager on the logical host environment, the jpcconf ha export command needs to be used to export the logical host environment definition, and the jpcconf ha import command needs to be used to import it to the standby host.

Return values

0

The command ended normally.

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

4

The services on the PFM - Manager host have not stopped.

5

The command was executed on a host that is not the PFM - Manager host.

10

The command is being executed.

11

Processing was canceled by the user or the system.

100

The environment for Performance Management is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The file or directory cannot be accessed.

230

Execution of an internal command failed.

231

Registration of a health check agent service failed (Windows only).

232

Deletion of a health check agent service failed (Windows only).

233

Setting up dependencies among services failed (Windows only).

234

Rollback of the processing failed.

255

An unexpected error occurred.

Usage example

The following example disables the health check function:

jpcconf hc disable

jpcconf hc display

Format

jpcconf hc display

Function

The jpcconf hc display command displays the status of the health check function. When a logical host environment is created for PFM - Manager, the command displays the status of the health check function of PFM - Manager in a logical host environment.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Return values

0

The command ended normally (the health check function is disabled).

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

5

The command is executed on a host that is not the PFM - Manager host.

10

The command is being executed.

11

Processing was canceled by the user or the system.

100

The environment for Performance Management is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The file or directory cannot be accessed (the command was executed on the standby node).

254

The command terminated normally (the health check function is enabled).

255

An unexpected error occurred.

Usage example

The following example displays the status of the health check function:

jpcconf hc display

Output examples

When the health check function is enabled

available

When the health check function is disabled

unavailable

jpcconf hc enable

Format

jpcconf hc enable

Function

The jpcconf hc enable command enables the health check function. When a logical host environment has been created for PFM - Manager, the command enables the health check function of PFM - Manager in the logical host environment.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Notes

You cannot execute this command if a Performance Management service is running on the physical host or a logical host.

You cannot enable the health check function when the status management function is not enabled on the physical host on which you execute the command.

If you enable the health check function, the health check agent starts at the same time that PFM - Manager starts.

If the health check function is enabled for PFM - Manager on the logical host environment, the jpcconf ha export command needs to be used to export the logical host environment definition, and the jpcconf ha import command needs to be used to import it to the standby host.

If the monitoring is suspended, the health check function can be enabled but the monitoring remains suspended.

Return values

0

The command ended normally.

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

4

The services on the PFM - Manager host have not stopped.

5

The command is executed on a host that is not the PFM - Manager host.

10

The command is being executed.

11

Processing was canceled by the user or the system.

100

The Performance Management environment is invalid.

101

The status management function is not enabled.

200

A memory shortage occurred.

211

The file or directory cannot be accessed.

230

Execution of an internal command failed.

231

Registration of a health check agent service failed (Windows only).

232

Deletion of a health check agent service failed (Windows only).

233

Setting up dependencies among services failed (Windows only).

234

Rollback of the processing failed.

255

An unexpected error occurred.

Usage example

The following example enables the health check function:

jpcconf hc enable

jpcconf host hostmode

Format

Format 1

jpcconf host hostmode   -mode {uname|hostname|alias
                        -aliasname alias-name}
                        -d backup-directory-name
                        [-dbconvert {convert|delete}]

Format 2

jpcconf host hostmode     -display

Function

The following explains each format for the jpcconf host hostmode command.

Format 1

This changes the method for acquiring the monitoring host name on the physical host environment. Note that when this command is executed, all definition information and performance information is carried over.

Format 2

This displays the monitoring host name and the method for acquiring the monitoring host name.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-mode {uname|hostname|alias}

Specifies the method for acquiring the monitoring host name on the physical host environment. The following table shows the correspondence between the specified option and the method for acquiring the monitoring host name.

Table 2‒16: Method for acquiring the monitoring host name

-mode option

Description

uname

The uname -n command is used to obtain the monitoring host name.

hostname

The hostname command is used to obtain the monitoring host name.

alias

The alias name is used for the monitoring host name.

-aliasname alias-name

This specifies the alias name. This option can be specified when alias is specified for the -mode option. For alias-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. localhost, IP addresses, and a logical host name on the same device cannot be specified.

-d backup-directory-name

This specifies the backup destination directory. Specify an existing directory. Note that you cannot specify a subdirectory of the directory that contains the Store database for Agent Store or RM Store. For backup-directory-name, specify a string 1 to 130 bytes, consisting of alphanumeric characters, symbols, and space characters. However, the following symbols cannot be specified:

; , * ? ' " < > |

If the file name contains spaces, enclose the entire name in double quotation marks (").

In directory-name, specify an empty directory that contains no files or directories.

-dbconvert {convert|delete}

Specifies how performance data is carried over. If nothing is specified, convert is set.

If convert is specified, the host name information for the key field is converted to a new host name, and data is carried over.

If delete is specified, the Store database is deleted, and data is not carried over. However, information about event data managed by PFM - Manager is not deleted, and carried over.

-display

Specifies that the method for acquiring the monitoring host name and information about the host name are to be displayed.

Notes

When the jpcconf host hostmode command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later, and the version of all instances of PFM - Agent must be 08-00 or later.

If PFM - Agent 07-00 or earlier is installed, the settings for the function for setting monitoring-host names must be reverted beforehand. The following shows how to revert the settings for each OS:

In Windows:

Execute the jpcconf host hostmode -mode hostname -d d:\backup# command.

In UNIX:

Execute the jpcconf host hostmode -mode uname -d /home/backup# command.

#

The backup destination directory is optional.

The following table shows the required version combinations for PFM - Manager, PFM - Base, and PFM - Agent on the execution host, for executing the jpcconf host hostmode command.

Table 2‒17: Whether the jpcconf host hostmode command can be used based on product combination on the execution host

Version of PFM - Manager and PFM - Base

Version of PFM - Agent

No PFM - Agent

08-00 or later

07-00 or earlier

PFM - Manager

08-11 or earlier

No

No

No

09-00 or later

Yes

No

Yes

PFM - Base

08-11 or earlier

No

No

No

09-00 or later

Yes

No

Yes

Legend:

Yes: The jpcconf host hostmode command can be executed.

No: The jpcconf host hostmode command cannot be executed.

When the jpcconf host hostmode command is executed in Format 1, all services for the specified host need to be stopped.

The directory specified for the -d option of the jpcconf host hostmode command must have free space that is as large as the total size of the following databases: The Store databases for PFM - Agent and PFM - RM on the specified host and the database in the import directory. If the directories that contain these databases have been changed from the default directories, use the sizes of the databases in the directories actually used for calculation.

Do not execute any other commands while the jpcconf host hostmode command is executing. If another command is executed, the jpcconf host hostmode command or the other command might fail to execute.

If the jpcconf host hostmode command fails with a KAVE05183-E message, use the following procedure to correct the error:

Check the message that was output immediately before the above message, and remove the cause of the error.

Check whether a KAVE05172-I message was output when the command failed.

If the message was output, use the backup data in the backup directory to restore the backup source data.

The table below shows the types of data that are backed up. Restore these types of data from the data in the backup destination directories. In Windows, replace a slash (/) with a backslash (\) in the table.

Category

Backup source

Backup destination

Store database

The Store directory of the Agent product

For a multi-instance agent:

backup-directory/agtX#1/instance/store

For a single-instance agent:

backup-directory/agtX#1/store

Definition file

installation-directory/jpcns.ini

backup-directory/jpcns.ini

installation-directory/jpcns_backup.ini

backup-directory/jpcns_backup.ini

installation-directory/jpccomm.ini

backup-directory/jpccomm.ini

installation-directory/agtX#1/agent/agtlist.ini#2

backup-directory/agtX#1/agent/agtlist.ini#2

installation-directory/agtX#1/store/stolist.ini#2

backup-directory/agtX#1/store/stolist.ini#2

installation-directory/bin/statsvr/restart.ini

backup-directory/bin/statsvr/restart.ini

installation-directory/sys/jp1sysEvent.ini

backup-directory/sys/jp1sysEvent.ini

#1: The agtX item indicates the Agent product's service key. For the service key of an Agent product, see any manual of that Agent product.

#2: This data is backed up only for a multi-instance agent.

Re-execute the command.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The Performance Management service is running at the executing host.

10

The command is being executed.

11

The user or the system canceled processing.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

223

A communication processing timeout error occurred.

255

An unexpected error occurred.

Usage example 1

This example changes the method for acquiring the monitoring host name so that it is acquired by using the hostname command.

jpcconf host hostmode -mode hostname -d d:\backup -dbconvert convert

Usage example 2

This example changes the method for acquiring the monitoring host name so that the alias name is used.

jpcconf host hostmode -mode alias -aliasname aliasA -d d:\backup -dbconvert convert

Usage example 3

This example displays the monitoring host name and the method for acquiring the monitoring host name. The method for acquiring the monitoring host name is shown for the displayed hostmode, and the monitoring host name is shown for the displayed hostname. The alias name is shown for the displayed aliasname.

jpcconf host hostmode -display

Display examples

When using the hostname command as the method for acquiring the monitoring host name :

hostmode  : hostname
hostname  : hostA

When using the alias name for the monitoring host name:

hostmode  : alias
aliasname : aliasA

jpcconf host hostname

Format

jpcconf host hostname    [-lhost logical-host-name] -newhost new-host-name
                         -d backup-directory-name
                         [-dbconvert {convert|delete}]

Function

The jpcconf host hostname command changes the monitoring host name for a Performance Management system. When changing the real host name, use this command to change the monitoring host name, and then change the real host name. The monitoring host name for the physical host and logical host can be changed.

This command does not change the method for acquiring the monitoring host name. Note that when this command is executed, all definition information and performance information is carried over.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-lhost logical-host-name

Specifies the logical host name to be changed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

-newhost new-host-name

Specifies a new host name. The following table contains cautions about host name types and input values, for each condition.

Table 2‒18: Cautions regarding specified host name types and input values

Condition

Specified host name

Cautions regarding the input value

Specified -lhost option

Method for acquiring the monitoring host name #1

Not specified

hostname

Physical host name (value displayed by the hostname command)

Specify 1 to 255 bytes of alphanumeric characters.

Host names starting with localhost or an IP address cannot be specified.

uname -n

Physical host name (value displayed by the uname -n command)

alias

Alias name (optional host name)#2

Specify 1 to 32 bytes of alphanumeric characters.

Host names starting with localhost or an IP address cannot be specified.

Specified

--

Logical host name

Specify 1 to 32 bytes of alphanumeric characters or hyphens (-).

Host names starting with localhost, an IP address, or a hyphen (-) cannot be specified.

Legend:

--: Not applicable

#1

The method for acquiring the monitoring host name is set by using the jpcconf host hostmode command.

The jpcconf host hostmode -display command can be used to check the current setting of the method for acquiring the monitoring host name.

#2

For details about alias names, see the chapter describing installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-d backup-directory-name

Specifies the backup destination directory. Specify an existing directory. Note that you cannot specify a subdirectory of the directory that contains the Store database for Agent Store or RM Store. For backup-directory-name, specify a string of 1 to 130 bytes, consisting of alphanumeric characters, symbols, and space characters. However, the following symbols cannot be specified:

; , * ? ' " < > |

If the file name contains spaces, enclose the entire name in double quotation marks (").

In directory-name, specify an empty directory that contains no files or directories.

-dbconvert {convert|delete}

Specifies how performance data is carried over. If nothing is specified, convert is set.

When convert is specified, the host name information for the Store database is converted to a new host name, and data is carried over.

If delete is specified, the Store database is deleted, and data is not carried over. However, information about event data managed by PFM - Manager is not deleted, and carried over.

Notes

When the jpcconf host hostname command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

When the jpcconf host hostname command is executed, all services on the specified host must be stopped.

The directory specified for the -d option of the jpcconf host hostname command must have about the same amount of free disk space as the capacity of the Store database for PFM - Agent and PFM - RM on the specified host. The directory specified for the -d option of the jpcconf host hostname command must have free space that is as large as the total size of the following databases: The Store databases for PFM - Agent and PFM - RM on the specified host and the database in the import directory. If the directories that contain these databases have been changed from the default directories, use the sizes of the databases in the directories actually used for calculation.

Do not execute any other commands while the jpcconf host hostname command is executing. If another command is executed, the jpcconf host hostname command or other command might fail to execute.

If the jpcconf host hostname command fails with a KAVE05181-E or KAVE05182-E message, use the following procedure to correct the error:

Check the message that was output immediately before the above message, and remove the cause of the error.

Check whether a KAVE05172-I message was output when the command failed.

If the message was output, use the backup data in the backup directory to restore the backup source data.

The table below shows the types of data that are backed up. Restore these types of data from the data in the backup destination directories. In Windows, replace a slash (/) with a backslash (\) in the table.

Types of data backed up if the physical host name cannot be changed:

Category

Backup source

Backup destination

Store database

The Store directory of the Agent product

For a multi-instance agent:

backup-directory/agtX#1/instance/store

For a single-instance agent:

backup-directory/agtX#1/store

Definition file

installation-directory/jpcns.ini

backup-directory/jpcns.ini

installation-directory/jpcns_backup.ini

backup-directory/jpcns_backup.ini

installation-directory/jpccomm.ini

backup-directory/jpccomm.ini

installation-directory/agtX#1/agent/agtlist.ini#2

backup-directory/agtX#1/agent/agtlist.ini#2

installation-directory/agtX#1/store/stolist.ini#2

backup-directory/agtX#1/store/stolist.ini#2

installation-directory/bin/statsvr/restart.ini

backup-directory/bin/statsvr/restart.ini

installation-directory/sys/jp1sysEvent.ini

backup-directory/sys/jp1sysEvent.ini

#1: The agtX item indicates the Agent product's service key. For the service key of an Agent product, see any manual of that Agent product.

#2: This data is backed up only for a multi-instance agent.

Types of data backed up if the logical host name cannot be changed:

Category

Backup source

Backup destination

Store database

The Store directory of the Agent product

For a multi-instance agent:

backup-directory/agtX#1/instance/store

For a single-instance agent:

backup-directory/agtX#1/store

Definition file

environment-directory/jp1pc/jpcns.ini

backup-directory/jpcns.ini

environment-directory/jp1pc/jpcns_backup.ini

backup-directory/jpcns_backup.ini

environment-directory/jp1pc/jpccomm.ini

backup-directory/jpccomm.ini

environment-directory/jp1pc/agtX#1/agent/agtlist.ini#2

backup-directory/agtX#1/agent/agtlist.ini#2

environment-directory/jp1pc/agtX#1/store/stolist.ini#2

backup-directory/agtX#1/store/stolist.ini#2

environment-directory/jp1pc/bin/statsvr/restart.ini

backup-directory/bin/statsvr/restart.ini

environment-directory/jp1pc/sys/jp1sysEvent.ini

backup-directory/sys/jp1sysEvent.ini

#1: The agtX item indicates the Agent product's service key. For the service key of an Agent product, see any manual of that Agent product.

#2: This data is backed up only for a multi-instance agent.

Re-execute the command.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The Performance Management service is running at the executing host.

10

The command is being executed.

11

The user or the system canceled processing.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

223

A communication processing timeout error occurred.

255

An unexpected error occurred.

Usage example 1

This example changes the physical host name to hostB.

jpcconf host hostname -newhost hostB -d d:\backup

Usage example 2

This example changes the logical host name lhostA to lhostB.

jpcconf host hostname -lhost lhostA -newhost lhostB -d d:\backup -dbconvert delete

Output example

This example shows the standard output when backup deletion is successful.

Example of standard output

KAVE05166-I Host name change has started.
KAVE05172-I Host information backup was successful.
KAVE05174-I Deletion of host information backup was successful.
KAVE05167-I Host name change has terminated normally.

This example shows the standard output when backup deletion fails.

Example of standard output

KAVE05166-I Host name change has started.
KAVE05172-I Host information backup was successful.
KAVE05175-W Deletion of host information backup failed.
KAVE05167-I Host name change has terminated normally.

jpcconf im disable

Format

jpcconf im disable

Function

The jpcconf im disable command disables the JP1/IM monitored object linkage function.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Note

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

5

The command was executed on a host that is not the PFM - Manager host.

100

The Performance Management environment is invalid.

150

The user does not have execution permission for the command.

151

An argument specification is invalid.

155

The registry file cannot be accessed.

156

Information needed to enable or disable the JP1/IM monitored object linkage function cannot be acquired.

157

The internal command settings file cannot be deleted.

158

The internal command settings directory was not found.

159

An internal command was not found.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

jpcconf im enable

Format

jpcconf im enable

Function

The jpcconf im enable command enables the JP1/IM monitored object linkage function.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Notes

If this command's execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

5

The command was executed on a host that is not the PFM - Manager host.

100

The Performance Management environment is invalid.

150

The user does not have execution permission for the command.

151

An argument specification is invalid.

155

The registry file cannot be accessed.

156

Information needed to enable or disable the JP1/IM monitored object linkage function cannot be acquired.

157

The internal command settings file cannot be deleted.

158

The internal command settings directory was not found.

159

An internal command was not found.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

jpcconf inst list

Format

jpcconf inst list    -key service-key
                    [-lhost logical-host-name]

Function

The jpcconf inst list command displays the instance names that have been set up by a PFM - Agent or PFM - RM that can start multiple services on a single host.

Hosts that can execute the command

PFM - Agent

PFM - RM

Execution permission

In Windows:

None

In UNIX:

None

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM service that set up the instance names you wish to display. A product name can also be specified when the product name display functionality is enabled. Only the service keys of PFM - Agents or PFM - RMs that have instance environments can be specified. For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-lhost logical-host-name

Specifies the host name of the logical host whose instance names are to be displayed.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters and no periods (.).

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

Notes

If the specified PFM - Agent or PFM - RM does not have an instance environment, nothing is output, even if this command is executed.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

5

The specified service has not been installed.

10

The command is executing in another session.

100

The Performance Management environment is invalid.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example1

This example displays the instance names of PFM - Agent for Oracle:

jpcconf inst list -key Oracle

If there are instances named SDA and SDC, the following is displayed:

Usage example 2

This example outputs the instance names of an instance of PFM - Agent for Oracle on a logical host (host name: jp1-ha1):

jpcconf inst list -key Oracle -lhost jp1-ha1

jpcconf inst setup

Format

Format 1

jpcconf inst setup    -key service-key
                     [-lhost logical-host-name]
                      -inst instance-name
                     [-input definition-file-name]
                     [-noquery]

Format 2

jpcconf inst setup    -key service-key
                      -template definition-file-name
                     [-noquery]

Function

The jpcconf inst setup command creates or updates an instance environment for a PFM - Agent or PFM - RM that can start multiple services on a single host. In the case of a PFM - Agent or PFM - RM that can start an instance, execution of this command is required.

Executing this command creates or updates the following directories that contain, among other items, the setup file for the instance environment:

In Windows:

installation-folder\xxxx#\agent\instance-name\

installation-folder\xxxx#\store\instance-name\

In UNIX:

/opt/jp1pc/xxxx#/store/instance-name/

/opt/jp1pc/xxxx#/agent/instance-name/

#

xxxx denotes the service key of a PFM - Agent or PFM - RM. For details about the service key, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Hosts that can execute the command

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM service for which you want to create or update the execution environment. A product name can also be specified when the product name display functionality is enabled. Only the service keys of PFM - Agents or PFM - RMs that have instance environments can be specified. For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-lhost logical-host-name

Specifies the host name of the logical host whose instance environment is to be added.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters and no periods (.).

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

-inst instance-name

Specifies the instance name for which an execution environment is to be created or updated. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond.

To execute this command in non-interactive mode, specify this option and the -input option together.

The command behavior changes in various situations, as described below:

If the target PFM - Agent or PFM - RM service is active:

A KAVE05143-E message is output. The command terminates without stopping the service. Stop the service, and then re-execute the command.

If an existing instance environment is specified:

A KAVE05407-I message is output. The command updates the instance environment.

If a file with the same name as the file specified for the -template option already exists:

A KAVE05399-I message is output. The command updates the file.

-input definition-file-name

Specifies the name of a definition file from which the instance environment settings will be loaded. For definition-file-name, specify a string of 1 to 250 bytes. The instance environment will be automatically set up or updated with the settings in the specified definition file.

If the string that you want to specify contains spaces, enclose the entire string in double quotation marks (").

To execute this command in non-interactive mode, specify this option and the -noquery option together.

-template definition-file-name

Specifies a path name of the definition file for which the template file will be generated. For definition-file-name, specify a string of 1 to 245 bytes. In the generated template file, sections and labels will be output according to the setting items for the target PFM - Agent or PFM - RM instance. Note that the values for the labels in the [Instance Definitions] section will be blank.

The generated file can be edited according to the environment requirements, and the edited file can be specified as an input file for the -input option.

If the string that you want to specify contains spaces, enclose the entire string in double quotation marks (").

Format of the definition file (for the jpcconf inst setup command)

The definition file is a text file consisting of sections and labels described below. The label names and values are specified in name=value format.

All the described sections and labels are required. If values are not specified, the command will assume that they are omitted. Invalid section and label names are ignored.

[Common Definitions] section

Specifies the basic information in the definition file.

Definition File Version label

Specifies the version of the definition file. Specify the constant 0001.

[Product Information] section

Specifies the information about the target product (PFM - Agent or PFM - RM).

Product ID label

Specifies the product ID of the target product (PFM - Agent or PFM - RM). For the product ID to be specified, see the Appendix that describes file name extensions in any manual of the relevant PFM - Agent or PFM - RM product.

[Instance Definitions] section

Specifies the settings of the instance environment.

Store Version label

Specifies the Store version of the instance environment. Specify either 1.0 or 2.0.

If the version of the target PFM - Agent product is 07-00 or earlier or if the target product is PFM - RM, you do not need to specify this label. If this label is specified, it is ignored in this case.

Product-specific labels

In addition to the labels described above, you can specify instance setting items that are specific to the target product (PFM - Agent or PFM - RM). For the labels that can be specified, see the chapter on installation and setup in any manual for the relevant PFM - Agent or PFM - RM product. Note that when you specify settings such as the password in interactive mode, you might be prompted to enter the same values again for confirmation. However, you only have to specify these values once in the definition file.

The following shows an example of specifying settings in the definition file.

[Common Definitions]
Definition File Version=0001

[Product Information]
Product ID=O

[Instance Definitions]
Store Version=2.0
oracle_sid=ORCL
oracle_home=/home/oracle
 ...

Notes

You must specify the arguments in the order they appear in Format.

If the service with the specified instance name is active when you update the instance environment, stop the service and then execute this command. After the update processing is completed, manually start the service.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

If the definition file includes confidential information such as passwords, save the file in a secured and safe place, and delete the file when the file is no longer needed. If you need to transfer the definition file between hosts, use SFTP communication (FTP communication through an SSH tunnel) or other safe means that are secure against sniffing.

When you execute the command with the -input option, the command execution is interrupted if the definition file does not contain all necessary labels or invalid values are specified for necessary labels in the definition file. If you add the -noquery option to automatically execute the command in a batch or script file, confirm that the settings in the definition file are correct beforehand. If the command is automatically executed, you can check whether the command terminates normally with a message or return value that is output.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The specified service has not been stopped.

5

The specified service has not been installed.

6

The definition file contains errors.

10

The command is executing in another session.

11

The user canceled the processing (by entering N at the prompt).

100

The Performance Management environment is invalid.

101

Acquisition of a port number failed.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred (IP address could not be acquired).

230

Execution of an internal command failed.

231

Registration of Windows service failed (applicable to the Windows versions only).

255

An unexpected error occurred.

Usage example

This example creates an execution environment for the instance named SDC:

jpcconf inst setup -key Oracle -inst SDC

Example of executing the command in non-interactive mode

If the -noquery, -input, and -template options are specified, setup can be performed without any queries output from Performance Management. The following shows usage examples.

Example 1

This example outputs the OracleTemplate01.txt file as the template file for the PFM - Agent for Oracle definition file.

# jpcconf inst setup -key Oracle -template OracleTemplate01.txt

Example 2

This example automatically generates inst01 through inst03 as new PFM - Agent for Oracle instance environments.

This example assumes that the user has prepared definition files OracleInst01.txt, OracleInst02.txt, and OracleInst03.txt by editing the OracleTemplate01.txt template file output in Example 1 according to the individual instance environments.

# jpcconf inst setup -key Oracle -inst inst01 -input OracleInst01.txt -noquery
# jpcconf inst setup -key Oracle -inst inst02 -input OracleInst02.txt -noquery
# jpcconf inst setup -key Oracle -inst inst03 -input OracleInst03.txt -noquery

jpcconf inst unsetup

Format

jpcconf inst unsetup    -key service-key
                       [-lhost logical-host-name]
                        -inst instance-name
                       [-noquery]

Function

The jpcconf inst unsetup command deletes an instance environment for a PFM - Agent or PFM - RM that can start multiple services on a single host.

Executing this command deletes the following directories that contain, among other items, the setup file for the instance environment:

In Windows:

installation-folder\xxxx#\agent\instance-name\

installation-folder\xxxx#\store\instance-name\

In UNIX:

/opt/jp1pc/xxxx#/store/instance-name/

/opt/jp1pc/xxxx#/agent/instance-name/

#

xxxx denotes the service key of a PFM - Agent or PFM - RM. For details about the service key, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Hosts that can execute the command

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM service for which you want to delete an execution environment. A product name can also be specified if product name display functionality is enabled. Only the service keys of PFM - Agents or PFM - RMs that have instance environments can be specified. For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-lhost logical-host-name

Specifies the host name of the logical host whose instance environment is to be deleted.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters and no periods (.).

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

-inst instance-name

Specifies the instance name for which an execution environment is to be deleted. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

Note that if the service with the specified instance name is running, a KAVE05143-E message is output, and the command execution is interrupted. In this case, stop the service, and then re-execute the command.

Notes

You must specify the arguments in the order they appear in Format.

If the service with the specified instance name is active, the command first stops this service and then deletes its instance environment.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

If you delete an instance environment of an agent, check whether alarm tables are bound to the instance environment. If alarm tables are bound, unbind all of them, and then delete the instance environment.

After executing this command, an unnecessary agent remains under the User Agents node in the Agents tree in PFM - Web Console. If you do not want that agent to be displayed, delete it manually.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The specified service has not been stopped.

5

The specified service has not been installed.

10

The command is executing in another session.

11

The user canceled the processing (by entering N at the prompt).

100

The Performance Management environment is invalid.

101

Acquisition of a port number failed.

102

The specified instance was not found.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred (IP address could not be acquired).

230

Execution of an internal command failed.

232

Deletion of the Windows service failed (applicable to the Windows versions only).

255

An unexpected error occurred.

Usage example

This example deletes the instance execution environment named SDC:

jpcconf inst unsetup -key Oracle -inst SDC

jpcconf ipv6 disable

Format

jpcconf ipv6 disable

Function

The jpcconf ipv6 disable command disables the IPv6 usage settings on the host on which the command is executed.

In a cluster environment, you must execute this command on both the active node (the disk is online) and the standby node (the disk is offline).

If the IPv6 usage settings on a host are disabled, all Performance Management services and commands running on the host will use IPv4 for communication.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (If Windows UAC functionality is enabled, this command must be executed from the administrator console.)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Notes

This command cannot be executed if even one Performance Management service is running on a physical host or on the logical host.

To execute this command on a host, the version of PFM - Manager or PFM - Base on the host must be 10-00 or later.

This command cannot run concurrently with a startup or termination command, or other setup command, on the same host.

This command is supported on the following OSs only: Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Linux.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

Services are still running on a physical host or on the logical host.

10

A command is running.

11

The user canceled the processing.

100

There are problems with the environment.

200

A memory shortage occurred.

211

A file access error occurred.

255

An unexpected error occurred.

Usage example

This example disables the IPv6 usage settings on the host on which the command is executed.

jpcconf ipv6 disable

Output example

KAVE05932-I The function for IPv6 communication will now be set up. (disable)
KAVE05933-I The function for IPv6 communication was successfully set up. (disable)

jpcconf ipv6 display

Format

jpcconf ipv6 display

Function

The jpcconf ipv6 display command displays the IPv6 usage settings that are specified on the host on which the command is executed.

If the IPv6 communication function is enabled

This command displays available, and returns 254.

If the IPv6 communication function is disabled

This command displays unavailable, and returns 0.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (If Windows UAC functionality is enabled, this command must be executed from the administrator console.)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Notes

To execute this command on a host, the version of PFM - Manager or PFM - Base on the host must be 10-00 or later.

This command cannot run concurrently with a startup or termination command, or other setup command, on the same host.

This command is supported on the following OSs only: Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Linux.

Return values

0

The IPv6 usage settings are disabled.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

10

A command is running.

11

The user canceled the processing.

100

There are problems with the environment.

254

The IPv6 usage settings are enabled.

255

An unexpected error occurred.

Usage example

This example displays the IPv6 usage settings that are specified on the host on which the command is executed.

jpcconf ipv6 display

Output example

If the IPv6 usage settings are enabled:

available

If the IPv6 usage settings are disabled:

unavailable

jpcconf ipv6 enable

Format

jpcconf ipv6 enable

Function

The jpcconf ipv6 enable command enables the IPv6 usage settings on the host on which the command is executed.

In a cluster environment, you must execute this command on both the active node (the disk is online) and the standby node (the disk is offline).

If the IPv6 usage settings on a host are enabled, all Performance Management services and commands running on the host will use IPv6 for communication.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (If Windows UAC functionality is enabled, this command must be executed from the administrator console.)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Notes

This command cannot be executed if even one Performance Management service is running on a physical host or on the logical host.

To execute this command on a host, the version of PFM - Manager or PFM - Base on the host must be 10-00 or later.

This command cannot run concurrently with a startup or termination command, or other setup command, on the same host.

This command is supported on the following OSs only: Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Linux.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

Services are still running on a physical host or on the logical host.

10

A command is running.

11

The user canceled the processing.

100

There are problems with the environment.

200

A memory shortage occurred.

211

A file access error occurred.

255

An unexpected error occurred.

Usage example

This example enables the IPv6 usage settings on the host on which the command is executed.

jpcconf ipv6 enable

Output example

KAVE05932-I The function for IPv6 communication will now be set up. (enable)
KAVE05933-I KAVE05933-I The function for IPv6 communication was successfully set up. (enable)

jpcconf mgrhost define

Format

Format 1

jpcconf mgrhost define    -host host-name[,host-name]|-localhost
                         [-lhost logical-host-name]
                         [-noquery]

Format 2

jpcconf mgrhost define -shift
                             [-lhost logical-host-name]

Function

The jpcconf mgrhost define command sets and changes the host name of the PFM - Manager host for the connection destination (Name Server service).

Execute this command in the following cases:

Format 1

When setting or changing the host name of the PFM - Manager host for the connection destination

Format 2

When switching the PFM - Manager host for the connection destination between the primary and secondary hosts for multiple monitoring

To set or change the PFM - Manager host for the connection destination in a logical host environment, you must specify the -lhost option.

To set the host name of the PFM - Manager host for the connection destination for multiple monitoring, you must specify the two hosts in the -host option in Format 1.

To switch the PFM - Manager host for the connection destination between the primary and secondary hosts, for multiple monitoring, you must specify the -shift option as shown in Format 2.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

To only display the host name of the PFM - Manager host for the connection destination (Name Server service), no execution permission is required.

Only the following users can set or change (with an argument specified) the PFM - Manager host:

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-host host-name

Specifies the host name of the PFM - Manager host that is to be set as the connection destination. For host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. An IP address cannot be specified.

To set the host name of the PFM - Manager host for the connection destination for multiple monitoring, you must specify two hosts by separating them by a comma (,). Specify two host names so that the host name before the comma indicates the primary host.

When two hosts are specified as described above, the status management function must be enabled. If the status management function is disabled, an error message will be output when the command is executed.

This argument can be executed on the PFM - Base, PFM - Agent, or PFM - RM host. Also, a command with this argument can be executed even if that PFM - Agent or PFM - RM is installed on a physical host and PFM - Manager is installed on a logical host. In this configuration, however, only the PFM - Manager host that is on a logical host can be specified as the connection destination.

If PFM - Manager is installed on the local host, specifying this option results in an error. If PFM - Manager is installed on the PFM - Agent or PFM - RM host, the PFM - Manager for the connection destination is the PFM - Manager of the local host. You cannot specify a PFM - Manager on the remote host as the PFM - Manager host for the connection destination.

If two or more host names are set for the PFM - Manager host, the name to be specified as the connection-destination PFM - Manager host name differs depending on the situation, as shown below:

If an actual host name is used as the PFM - Manager monitoring host name:

In Windows, specify the host name displayed by the hostname command. In UNIX, specify the host name displayed by the uname -n command.

If an alias is used as the PFM - Manager monitoring host name:

Specify the alias.

If the execution host is a PFM - Manager host, the PFM - Manager host for the connection destination can be changed only when the following three conditions are met:

The status management function is enabled.

Two host names are specified.

One of the specified hosts is localhost.

-localhost

Specifies that the local host is to be set for the connection destination.

-lhost logical-host-name

Specifies the host name in the logical host environment for which the PFM - Manager for the connection destination host is to be set or changed.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters and no periods (.).

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

Note, however, that if there are Performance Management services that are running, command execution is interrupted with a KAVE05143-E message. If this message is output, stop all Performance Management services that are running on the local host, and then re-execute the command.

-shift

Switches the primary and secondary hosts to reverse their roles.

This option registers the host name of the current primary host as that of the secondary host and the host name of the current secondary host as that of the primary host.

If two PFM - Manager hosts for the connection destinations have not been registered, an error message will be output when the command is executed.

Notes

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Notes on command execution using Format 1

Before you execute this command, stop all Performance Management program services on the host. When you finish setting the host name, start the services manually.

To use the ODBC driver from the host, execute this command.

Note on command execution using Format 2

To execute this command, both the multiple-monitoring environment and status management function must be enabled.

Return values

0

The command terminated normally. (When only one PFM - Manager host for the connection destination is registered)

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

Services have not been stopped at the executing host.

10

The command is executing in another session.

11

The user canceled the processing (by entering N at the prompt).

12

The status management function is disabled.

Two hosts have not been registered for PFM - Manager hosts for the connection destinations.

100

The Performance Management environment is invalid.

101

Acquisition of a port number failed.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred (IP address could not be acquired).

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example 1

This example changes the PFM - Manager host for the connection destination to hostmgr:

jpcconf mgrhost define -host hostmgr

Usage example 2

This example changes the PFM - Manager host for the connection destination from a logical host (host name: jp1-ha1) to hostmgr:

jpcconf mgrhost define -host hostmgr -lhost jp1-ha1

Usage example 3

This is an example of executing the command in a multiple-monitoring environment when the execution host is a PFM - Manager host.

Examples of command setting assuming that the primary host is Hostname1 and the secondary host is Hostname2:

When the PFM - Manager host (execution host) is the primary host

jpcconf mgrhost define -host localhost,Hostname2

When the PFM - Manager host (execution host) is the secondary host

jpcconf mgrhost define -host Hostname1,localhost

Usage example 4

This example changes the destination connection PFM - Manager hosts to Hostname1 and Hostname2 in a multiple-monitoring environment when the execution host is not a PFM - Manager host.

jpcconf mgrhost define -host Hostname1,Hostname2

Usage example 5

This example switches the primary host and secondary host, reversing roles, in a multiple-monitoring environment.

jpcconf mgrhost define -shift

jpcconf mgrhost display

Format

jpcconf mgrhost display      [-lhost logical-host-name]

Function

The jpcconf mgrhost display command displays all host names of PFM - Manager hosts for the connection destinations (Name Server services).

To display the PFM - Manager host for the connection destination in a logical host environment, you must specify the -lhost option.

When two PFM - Manager hosts for the connection destination have been registered, the host names are displayed in order of primary host name and secondary host name.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

To only display the host name of the PFM - Manager host for the connection destination (Name Server service), execution permission is not required.

Only the following users can set or change (with an argument specified) the PFM - Manager host:

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-lhost logical-host-name

Specifies the host name in the logical host environment for which the PFM - Manager for the connection destination host is to be displayed, set, or changed.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters and no periods (.).

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

Notes

To use the ODBC driver from the host, execute this command.

If this command's execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally. (When only one PFM - Manager host for the connection destination is registered)

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

10

The command is executing in another session.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

254

The command terminated normally. (When two PFM - Manager hosts for the connection destinations are registered)

255

An unexpected error occurred.

Usage example 1

This example displays the PFM - Manager host for the connection destination:

jpcconf mgrhost display

Usage example 2

This example displays the PFM - Manager host for the connection destination specified in the logical host (host name: jp1-ha1):

jpcconf mgrhost display -lhost jp1-ha1

jpcconf ov disable

Format

jpcconf ov disable

Function

The jpcconf ov disable command performs unsetup of the NNM linkage facility.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Return values

0

The command terminated normally.

1

The command terminated abnormally.

5

The command was executed on a host that was not the PFM - Manager host.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

jpcconf ov enable

Format

jpcconf ov enable             [-mkhtml]

Function

The jpcconf ov enable command sets up the NNM linkage facility. Specify the -mkhtml option to create a PFM - Manager selection window HTML file, without performing a setup.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-mkhtml

Creates a PFM - Manager selection window HTML file. When a PFM - Manager selection window HTML file is created, the PFM - Manager for the connection destination can be selected when a report or PFM - Web Console are opened from NNM.

Notes

Execute this command while the NNM service is running, and the NNM window is closed.

Return values

0

The command terminated normally.

1

The command terminated abnormally.

5

The command was executed on a host that was not the PFM - Manager host.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

jpcconf port define

Format

Format 1

jpcconf port define    -key service-key
                      [-lhost logical-host-name]
                      [-inst instance-name]
                      [-input definition-file-name]
                      [-noquery]

Format 2

jpcconf port define    -key service-key
                      [-lhost logical-host-name]
                      [-inst instance-name]
                       -template definition-file-name
                      [-noquery]

Function

The jpcconf port define command sets the port numbers that are used with Performance Management.

Because port numbers are assigned automatically to the programs and services of the Performance Management products each time the services are restarted, the current port numbers may not be the same as the ones assigned in the previous session, except for the port numbers listed below, which are always used when port numbers are set automatically:

Service name#

Parameter

Port number

Usage

Name Server

jp1pcnsvr

22285

Used when each service communicates with the Name Server service.

OpenView (between NNM and NNM Object Manager)

jp1pcovsvr

22292

Used to link to NNM.

Status Server

jp1pcstatsvr

22350

Used to check the service status.

View (between PFM - Web Console and View Server)

jp1pcvsvr

22286

Used to log into PFM - Manager or operate PFM - Manager via PFM - Web Console.

#: The command sometimes displays names that are different from the actual service names. For these services, the displayed names are indicated in the above table.

You use this command to indicate that you will set different port numbers from the ones listed above.

A specifiable port number is any integer in the range from 1024 to 65535 that is not in use as a port number in the system. If you do not specify a port number, the system uses the port number assigned by Performance Management. If you press the return key without specifying a port number, the system uses the displayed port number.

You should use the port number assigned by Performance Management unless that port number is already in use in the system. For details about the port numbers assigned by Performance Management, see C. Port Numbers.

Each number that is specified must be unique on the same device.

If a service of a Performance Management series program exists on both the logical host and the physical host of the same device, a unique port number must be assigned to the service on each host.

To indicate that you are not specifying a port number (so that the port number will be assigned automatically each time the service is restarted), enter the value 0. For the following services, the following port numbers are set:

Service name#

Parameter

Port number

Name Server

jp1pcnsvr

22285

OpenView (between NNM and NNM Object Manager)

jp1pcovsvr

22292

Status Server

jp1pcstatsvr

22350

View (between PFM - Web Console and View Server)

jp1pcvsvr

22286

#: The command sometimes displays names that are different from the actual service names. For these services, the displayed names are indicated in the above table.

To penetrate a firewall between PFM - Manager and PFM - Web Console, PFM - Manager and PFM - Agent, or between PFM - Manager and PFM - RM, you must set the port number to a fixed value. For details about the settings for penetrating these firewalls, see C. Port Numbers.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the service whose port numbers are to be the subject of this execution of the command. You can also specify the following in service-key:

all: Specifies the port numbers of all programs of the Performance Management products.

Manager or mgr: Specifies the port numbers that are used with the PFM - Manager services (excluding the Status Server and Action Handler services), the NNM Object Manager service, and between PFM - Web Console and the View Server service.

Product name or agtX: Specifies the port numbers that are used with the specified PFM - Agent or PFM - RM service, and the Name Server service.

AH or act: Specifies the port numbers that are used with the Action Handler service and the Name Server service.

View or view: Specifies the port numbers that are used between the PFM - Web Console and View Server services.

StatSvr or stat: Specifies the port numbers that are used with the Status Server service and the Name Server service.

Product name or agtX indicates the service key for the particular PFM - Agent or PFM - RM. For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-lhost logical-host-name

When the command targets a logical environment, specify the host name of a logical host.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters and no periods (.).

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

-inst instance-name

Specifies the instance name of the instance whose port numbers are to be the subject of this execution of the command. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. This option is applicable only to a PFM - Agent or PFM - RM that has an instance environment.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond.

To execute this command in non-interactive mode, specify this option and the -input option together.

The command behavior changes in various situations, as described below:

If there are Performance Management services that are running:

The command execution is interrupted with a KAVE05143-E message. Stop the services, and then re-execute the command.

If there is already a file with the same name as the file specified for the -template option:

A KAVE05399-I message is output and the file is updated.

-input definition-file-name

Specifies the path name of the definition file from which port numbers will be loaded. For definition-file-name, specify a string of 1 to 250 bytes. The port numbers set in the specified file will be set.

If the string that you want to specify contains spaces, enclose the entire string in double quotation marks (").

To execute this command in non-interactive mode, specify this option and the -noquery option together.

-template definition-file-name

Specifies the path name of the definition file to which port numbers that are set will be output. For definition-file-name, specify a string of 1 to 245 bytes. The labels of all services indicated by the specified service key will be output to the definition file. Note that in [component-name] sections, the port numbers that are set or 0 will be output as the label values.

If the string that you want to specify contains spaces, enclose the entire string in double quotation marks (").

Format of the definition file (for the jpcconf port define command)

The definition file is a text file consisting of sections and labels described below. The label names and values are specified in name=value format. Invalid section and label names are ignored.

[Common Definitions] section

Specifies the basic information in the definition file. This section and all labels in this section are required.

Definition File Version label

Specifies the version of the definition file. Specify the constant 0001.

[component-name] section

Use this section to specify the port numbers that you want to set.

For component-name, specify the name of a component that contains the services for which you want to set port numbers. You can specify multiple [component-name] sections (with different component-name values).

If you specify multiple [component-name] sections with the same component-name value, only the section specified first takes effect.

The values that can be specified for component-name are as follows:

Common

Specify Common when you want to set the port numbers that will be used by the Name Server, Status Server, Action Handler, and NNM Object Manager services.

Manager

Specify Manager when you want to set the port numbers that will be used by PFM - Manager services.

PFM - Agent or PFM - RM product name

Specify the name of a PFM - Agent or PFM - RM product when you want to set the port number that will be used by a PFM - Agent or PFM - RM product. For product names that can be specified, see the chapter on the Performance Management functionality in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Subsection with an instance name

To specify port numbers that will be used in a PFM - Agent or PFM - RM instance environment, specify them in this subsection. You can specify this subsection only if the specified component is a PFM - Agent or PFM - RM that has multiple instances.

If you specify multiple subsections with the same name in a [component-name] section, the subsection specified first takes effect.

Label with a service name

Specify a label with the name of a service for which you want to set a port number.

If you specify multiple labels with the same name in a section or subsection, the label specified first takes effect.

If you want a port number to be dynamically assigned each time the service is restarted, specify 0 as the value.

However, for the Name Server, OpenView (between NNM and NNM Object Manager), Status Server, and View (between PFM - Web Console and View Server) services, fixed port numbers will be assigned even if you specify 0.

To use the default port numbers that are assigned by Performance Management, specify auto as the values. However, if the default port numbers are already in use, available port numbers will be assigned automatically.

Note that there are services for which you must not specify auto and must specify fixed port numbers. These services are listed in the following table.

Service name#

Port number

Name Server

22285

OpenView (between NNM and NNM Object Manager)

22292

Status Server

22350

View (between PFM - Web Console and View Server)

22286

#: The command sometimes displays names that are different from the actual service names. For these services, the displayed names are indicated in the above table.

When you specify port numbers, select port numbers that are in the range from 1024 through 65535 and are not currently used within the system.

If you do not change port numbers, specify nothing for these values.

If you specify a value that is outside the range from 1024 through 65535 or specify a value that includes non-numeric characters (except auto), the processing for the relevant services will be skipped.

The following table lists and describes component names, service names, and values that can be specified for [component-name] sections and service-name labels.

Component name

Service name

Value

Common

Name Server

Name Server port number

Status Server

Status Server port number

Action Handler

Action Handler port number

OpenView

NNM Object Manager port number (for linkage with NNM)

Manager

Master Manager

Master Manager port number

Master Store

Master Store port number

Correlator

Correlator port number

Trap Generator

Trap Generator port number

View Server

View Server port number

View

View Server port number (between PFM - Web Console and View Server services)

PFM - Agent or PFM - RM product name

Collector

Port number to be used by PFM - Agent Collector or Remote Monitor Collector

Store

Port number to be used by Agent Store or Remote Monitor Store

The following shows an example of specifying settings in the definition file.

[Common Definitions]
Definition File Version=0001

[Common]
Name Server=22285
Status Server=22350
Open View=22292
[Manager]
Master Manager=auto
Master Store=auto
Correlator=auto
 ...
[Windows]
Collector=0
Store=0
 ...
[Oracle]
[[oracle1]]
Collector=0
Store=0

Notes

If you want to set port numbers for a service of a Performance Management program that is active, you must first terminate the service and then execute this command. When you finish setting the port numbers, start the service manually.

If you terminate this command during execution by pressing the Ctrl + C keys, the port numbers will not be set correctly. In this case, re-execute the command to set the port numbers again.

Make sure that you set the same port number for the Name Server service on all hosts in the Performance Management system.

Similarly, for the Status Server service, make sure that you set the same port number on all hosts in the Performance Management system.

Also, for other PFM services, use the same correspondence between port numbers and service names throughout the Performance Management system to avoid confusion.

This command automatically edits the services file of the operating system.

This command edits only the local services file at the host where the command is executed. For UNIX, if you are managing the services file using NIS or NIS+, you must manually apply to the NIS server a port number added to the local services file.

When you enter a port number, the command displays the value that is contained in the services file at the host where the command is executed. In an NIS or NIS+ environment, if the port number information managed by the NIS server does not match the information in the services file of the NIS client, the displayed information may not be the actual value used by the service.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

When you execute the command with the -input option, the command execution is interrupted if the definition file does not contain all necessary labels or an invalid value is specified for Definition File Version. If you add the -noquery option to automatically execute the command in a batch or script file, confirm that the settings in the definition file are correct beforehand. If the command is automatically executed, you can check whether the command terminates normally with a message or return value that is output.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The specified service has not been stopped.

5

The specified service key was not found.

6

The definition file contains errors.

7

The specified service key was not found at the logical host.

10

The command is executing.

11

The user canceled the processing (by entering N at the prompt).

13

Setting was skipped for one or more services because values could not be set as specified in the definition file.

100

The Performance Management environment is invalid.

101

Acquisition of a port number failed.

102

The specified instance was not found.

106

Port number has not been registered in the services file.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

File cannot be accessed.

222

A communication error occurred (IP address could not be acquired).

224

There is no available port number to set in the services file.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example

This example specifies that the port numbers for all services of Performance Management programs will be set to fixed values:

jpcconf port define -key all

Example of executing the command in non-interactive mode

If the -noquery, -input, and -template options are specified, setup can be performed without any queries output from Performance Management. The following shows usage examples.

Example 1

This example generates the files AgentPort01.txt and AgentPort02.txt. The AgentPort01.txt file is the template file for the file that defines the port numbers that must be set in PFM - Agent for Platform (Windows). The AgentPort02.txt file is the template file for the file that defines the port numbers that must be set in PFM - Agent for Oracle.

# jpcconf port define -key Windows -template AgentPort01.txt
# jpcconf port define -key Oracle -template AgentPort02.txt

Example 2

This example sets port numbers that are used in PFM - Agent for Platform (Windows) and PFM - Agent for Oracle.

This example assumes that the user has prepared the definition files AgentPort01.txt and AgentPort02.txt by editing the template files generated in Example 1.

# jpcconf port define -key Windows -input AgentPort01.txt -noquery
# jpcconf port define -key Oracle -input AgentPort02.txt -noquery

jpcconf port list

Format

jpcconf port list     -key service-key
                     [-lhost logical-host-name]
                     [-inst instance-name]

Function

The jpcconf port list command displays the port numbers that are used with Performance Management.

The following information is displayed:

Table 2‒19: Displayed information

Item

Description

Component

Service name. The displayed names indicate the following:

Status Server: Status Server service

Name Server: Name Server service

Master Manager: Master Manager service

Master Store: Master Store service

Correlator: Correlator service

Trap Generator: Trap Generator service

View Server: View Server service

Action Handler: Action Handler service

Agent Store and Remote Monitor Store: Agent Store and Remote Monitor Store service

Agent Collector and Remote Monitor Collector: Agent Collector and Remote Monitor Collector service

View: View Server (between PFM - Web Console and View Server service)

OpenView: NNM Object Manager service

ServiceID

Service ID

Services

Name of the service that uses the port number. If this information is undefined, undef is displayed.

Port

Port number. If this information is undefined, undef is displayed.

Host Name

Host name

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the service whose port numbers are to be the subject of this execution of the command. You can specify the following in service-key:

all: Specifies the port numbers of all programs of the Performance Management products.

Manager or mgr: Specifies the port numbers that are used with the PFM - Manager services (excluding the Status Server and Action Handler services), the NNM Object Manager service, and between PFM - Web Console and the View Server service.

Product name or agtX: Specifies the port numbers that are used with the specified PFM - Agent or PFM - RM service, and the Name Server service.

AH or act: Specifies the port numbers that are used with the Action Handler service and the Name Server service.

View or view: Specifies the port numbers that are used between the PFM - Web Console and View Server services.

StatSvr or stat: Specifies the port numbers that are used with the Status Server service and the Name Server service.

Product name or agtX indicates the service key for the particular PFM - Agent or PFM - RM. For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-lhost logical-host-name

Specifies the host name of the logical host whose logical environment port numbers are to be displayed.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters and no periods (.).

For logical-host-name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

-inst instance-name

Specifies the instance name of the instance whose port numbers are to be displayed. This option is applicable only to a PFM - Agent or PFM - RM that has an instance environment. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

You can use the jpcconf inst list command to check the instance names that can be specified.

Notes

Services do not need to be stopped when this command is executed.

To avoid confusion during operations, you should use consistent conventions for the correspondence between port numbers and service names over the entire Performance Management system.

If this command's execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The specified service key was not found.

7

The specified service key was not found at the logical host.

10

The command is being executed.

100

The Performance Management environment is invalid.

102

The specified instance was not found.

106

Port number has not been registered in the services file.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

File cannot be accessed.

255

An unexpected error occurred.

Usage example

This example displays the information about the port numbers for all services of Performance Management programs:

jpcconf port list -key all

The following shows an example of the output:

jpcconf primmgr notify

Format

jpcconf primmgr notify      [-noprogress]

Function

The jpcconf primmgr notify command sets the PFM - Manager on the execution host as the primary host, and notifies all the hosts in the PFM system that the PFM - Manager on the execution host will operate as the primary host. This command sends the host name of the PFM - Manager to be the primary host to only the notification destination hosts where the Status Server service is running, and sets the host name in those notification destination hosts.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Argument

-noprogress

If this option is specified, the command does not output the information on the progress of notification processing.

Output of notification result file

When the jpcconf primmgr notify command terminates, the command outputs a CSV-format notification result file for every host to which the notification was sent. The following table provides an overview of the notification result file.

Table 2‒20: Overview of the notification result file

Item

OS

Description

File name

--

primnotifyresult.csv

File path

Windows

installation-folder\log

UNIX

/opt/jp1pc/log

Permission and owner

Windows

Permissions for installation-folder\log are inherited.

UNIX

666 [rw-rw-rw-]

owner/group:

Other than AIX

root(0)/sys(3)

AIX

root(0)/system(0)

Creation timing

--

A new file is created each time the command is executed.#

File size

--

Less than 1 megabyte

#

If a notification result file already exists, the existing file is discarded.

Output example of a notification result file

The following shows an output example of a notification result file:

DateTime=YYYY/MM/DD HH:MM:SS
Hostname,Primary Notify Result,Message
hostA,Success,
hostB,Failure,Host not available
hostC,Failure,Communication failure

The following table describes the details of the output content of the notification result file.

Table 2‒21: Output content of notification result file

Item

Output format

Output content

Output position

Execution date and time

DateTime=YYYY/MM/DD HH:MM:SS

(YYYY = year, MM = month, DD = day, HH = hour, MM = minute, SS = second)

Outputs the date and time when the command processing started in the time zone set.

First line

Label

HostName,Primary Notify Result,Message

Outputs the labels shown on the left.

Second line

Information on synchronization result for each service

host-name,setting-result,reason-message

Outputs the host name of the notification destination service as host-name.

For the output contents of the setting result and reason message, see the table below.

Third line and after

(This set of information is output as many times as the number of the hosts for which notification was executed.)

Legend:

: Single-byte space

The table below lists the messages output under the Primary Notify Result and Message labels in the notification result file when notification of the host name of the PFM - Manager to be the primary host has succeeded or failed. The following table also describes the corrective action to be taken for each failure message.

Table 2‒22: Output contents of notification result file and corrective actions

No.

Notification result

Output content

Corrective action

Primary Notification Result

Message

1

Notification succeeded.

Success

--

--

2

Notification failed because the notification destination host had not started or for other reasons.

Failure

Host not available

Perform switching between the primary and secondary hosts individually for the host to which notification failed.

3

Notification sent to the notification destination host failed because of a reason other than the above.

Failure

Communication failure

Perform switching between the primary and secondary hosts individually for the host to which notification failed.

Legend:

--: None

Notes

The following services must be running on the PFM - Manager on the execution host:

Status Server service

Name Server service

Master Manager service

This command must be executed in a multiple-monitoring environment.

Even if the PFM - Manager on the execution host has already been set as the primary host, this command updates settings and reports the host name.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

An attempt was made to execute the command on the PFM - Base host, but the command can only be executed on the PFM - Manager host.

10

The command is now running.

12

The command was not executed in a multiple-monitoring environment.

100

The Performance Management environment is invalid.

101

Not all the services required to execute the command are running.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file access error occurred.

222

A communication processing error occurred.

237

Notification to one or more hosts failed.

255

An unexpected error occurred.

Usage example

This example specifies the PFM - Manager on the execution host as the primary host, and notifies all the hosts in the PFM system of the host name of the primary PFM - Manager host.

jpcconf primmgr notify

Output examples

The following shows an example of messages output to the standard output when the notification of the host name of the PFM - Manager to be the primary host has succeeded:

Example of standard output

KAVE06145-I The primary PFM - Manager settings were successfully specified.
KAVE06147-I The program will now start notifying hosts of the primary host name.
[50/50]
KAVE06150-I The program successfully notified all hosts of the primary host name.
KAVE06148-I The program has finished notifying hosts of the primary host name.

The following shows an example of messages output to the standard output when the notification of primary manager settings has failed:

Example of standard output

KAVE06145-I The primary PFM - Manager settings were successfully specified.
KAVE06147-I The program will now start notifying hosts of the primary host name.
KAVE06149-E The program failed to notify all hosts of the primary host name. (host=HostA)
[50/50]
KAVE06151-W The program failed to notify at least one host of the primary host name.
KAVE06148-I The program has finished notifying hosts of the primary host name.

jpcconf prodname disable

Format

jpcconf prodname disable     [-lhost logical-host-name]

Function

The jpcconf prodname disable command disables the product name display functionality. If the functionality is already disabled, this command terminates normally.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. If you omit this specification, the physical host is assumed.

Notes

When the jpcconf prodname disable command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

When this is executed on a logical host environment, the logical host environment does not need to be exported or imported.

If a logical host environment is created after this is executed on a physical host environment, the physical host environment settings are carried over to the logical host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The Performance Management service is running at the executing host.

10

The command is being executed.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Usage example

This example disables product name display functionality for logical host lhost1.

jpcconf prodname disable -lhost lhost1

jpcconf prodname display

Format

jpcconf prodname display     [-lhost logical-host-name]

Function

The jpcconf prodname display command displays settings for the product name display functionality.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. If you omit this specification, the physical host is assumed.

Notes

When the jpcconf prodname display command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

Return values

0

The command terminated normally (when the product name display functionality is disabled).

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

10

The command is being executed.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

254

The command terminated normally (when the product name display functionality is enabled).

255

An unexpected error occurred.

Usage example

This example checks the current settings for product name display functionality on the physical host.

jpcconf prodname display

Output example

When the product name display functionality is currently enabled:

available

When the product name display functionality is currently disabled:

unavailable

jpcconf prodname enable

Format

jpcconf prodname enable     [-lhost logical-host-name]

Function

The jpcconf prodname enable command enables the product name display functionality. If the functionality is already enabled, this command terminates normally.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. If you omit this specification, the physical host is assumed.

Notes

When the jpcconf prodname enable command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

When this is executed on a logical host environment, the logical host environment does not need to be exported or imported.

If a logical host environment is created after this is executed on a physical host environment, the physical host environment settings are carried over to the logical host.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The Performance Management service is running at the executing host.

10

The command is being executed.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Usage example

This example enables product name display functionality on a physical host.

jpcconf prodname enable

jpcconf stat disable

Format

jpcconf stat disable

Function

The jpcconf stat disable command disables the status management function.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Notes

This command cannot be executed if even one Performance Management service is running on the physical or logical host.

During execution of this command, service start and stop processing is not performed automatically.

Information about the physical host and all logical hosts is updated.

You cannot disable the status management function when the health check function is enabled on the physical host or in a logical host environment.

You cannot disable the status management function when performing multiple monitoring.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

Service has not been stopped on either physical or logical host.

10

The command is being executed.

11

The user or the system canceled processing.

100

The Performance Management environment is invalid.

101

A function dependent on the status management function is enabled.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

231

Registration of the Status Server service failed (Windows version only).

232

Deletion of the Status Server service failed (Windows version only).

233

Service dependency setting failed (Windows version only).

234

Rollback processing failed.

255

An unexpected error occurred.

Usage example

This example disables the status management function:

jpcconf stat disable

jpcconf stat display

Format

jpcconf stat display

Function

The jpcconf stat display command displays the status of the status management function.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Return values

0

Status management function is disabled.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

10

The command is being executed.

11

The user or the system canceled processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

254

The system management function is enabled.

255

An unexpected error occurred.

Usage example

This example displays the status of the status management function:

jpcconf stat display

Output example

When the status management function is enabled

available

When the status management function is disabled

unavailable

jpcconf stat enable

Format

jpcconf stat enable

Function

The jpcconf stat enable command enables the status management function.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

None

Notes

This command cannot be executed if even one Performance Management service is running on the physical or logical host.

During execution of this command, service start and stop processing is not performed automatically.

Information about the physical host and all logical hosts is updated.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

Service has not been stopped on either physical or logical host.

10

The command is being executed.

11

The user or the system canceled processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

231

Registration of the Status Server service failed (Windows version only).

232

Deletion of the Status Server service failed (Windows version only).

233

Service dependency setting failed (Windows version only).

234

Rollback processing failed.

255

An unexpected error occurred.

Usage example

This example enables the status management function:

jpcconf stat enable

jpcconf target display

Format

jpcconf target display     -key service-key
                           -inst instance-name
                           -target monitoring-target-name
                          [-lhost logical-host-name]

Function

The jpcconf target display command displays settings for the monitoring targets monitored by each PFM - RM instance.

Hosts that can execute the command

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the PFM - RM service key set for the monitoring target to be displayed. A product name can also be specified when the product name display functionality is enabled.

-inst instance-name

Specifies the PFM - RM instance name set for the monitoring target to be displayed. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

-target monitoring-target-name

Specifies the monitoring target to be displayed, as created within the PFM - RM instance. For monitoring-target-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters or hyphens (-). Names starting with a hyphen (-) or the name All cannot be specified.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

Notes

When the jpcconf target display command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

This cannot be executed on a standby node when a PFM - RM monitoring target running on a logical host environment is displayed.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The specified service key was not found.

10

The command is being executed.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example

This example displays the settings for the monitoring target targetname1 set for instance inst1 in the PFM - RM for Platform.

jpcconf target display -key RMPlatform -inst inst1 -target targetname1

jpcconf target list

Format

jpcconf target list     -key service-key
                        -inst instance-name
                       [-lhost logical-host-name]

Function

The jpcconf target list command displays a list of monitoring targets monitored by PFM - RM within the instance.

Hosts that can execute the command

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the PFM - RM service key set for the monitoring target to be displayed. A product name can also be specified when the product name display functionality is enabled.

-inst instance-name

Specifies the PFM - RM instance name set for the monitoring target to be displayed. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. If you omit this specification, the physical host is assumed.

Notes

When the jpcconf target list command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

This cannot be executed on a standby node when a list of PFM - RM monitoring targets running on a logical host environment is displayed.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The specified service key was not found.

10

The command is being executed.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example

This example displays a list of monitoring targets set for instance inst1, in the PFM - RM for Platform running on logical host lhost1.

jpcconf target list -key RMPlatform -inst inst1 -lhost lhost1

jpcconf target setup

Format

Format 1

jpcconf target setup     -key service-key
                         -inst instance-name
                         -target monitoring-target-name
                        [-lhost logical-host-name]
                        [-input definition-file-name]
                        [-noquery]

Format 2

jpcconf target setup     -key service-key
                         -template definition-file-name
                        [-noquery]

Function

The jpcconf target setup command creates monitoring targets monitored by PFM - RM instances, and updates the settings.

Hosts that can execute the command

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the PFM - RM service key for performing monitoring target settings. A product name can also be specified when the product name display functionality is enabled.

-inst instance-name

Specifies a PFM - RM instance name for performing monitoring target settings. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

-target monitoring-target-name

Specifies an identifier used by PFM - RM to identify the monitoring target within the instance. For monitoring-target-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters or hyphens (-).

To create a new monitoring target name, specify a unique name within target PFM - RM instance. Names starting with a hyphen (-) or the name All cannot be specified. If the same name already exists, update the settings.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond.

To execute this command in non-interactive mode, specify this option and the -input option together.

The command behavior changes in various situations, as described below:

If specified monitoring targets already exist:

A KAVE05405-I message is output. The command updates the settings of the existing monitoring targets.

If there is already a file with the same name as the file specified for the -template option:

A KAVE05399-I message is output and the file is updated.

-input definition-file-name

Specifies the path name of the definition file from which the settings for monitoring targets will be loaded. For definition-file-name, specify a string of 1 to 250 bytes. Monitoring targets will automatically be created or updated according to the settings in the specified definition file.

If the string that you want to specify contains spaces, enclose the entire string in double quotation marks (").

To execute this command in non-interactive mode, specify this option and the -noquery option together.

-template definition-file-name

Specifies a path name of the definition file for which the template file will be generated. For definition-file-name, specify a string of 1 to 245 bytes. In the generated template file, sections and labels will be output according to the setting items for the target PFM - RM instance. Note that the values for the labels in the [Target Definitions] section will be blank. The generated file can be edited according to the environment requirements, and the edited file can be specified as an input file for the -input option.

If the string that you want to specify contains spaces, enclose the entire string in double quotation marks (").

Format of the definition file (for the jpcconf target setup command)

The definition file is a text file consisting of sections and labels described below. The label names and values are specified in name=value format.

All the described sections and labels are required. If values are not specified, the command will assume that they are omitted. Invalid section and label names are ignored.

[Common Definitions] section

Specifies the basic information in the definition file.

Definition File Version label

Specifies the version of the definition file. Specify the constant 0001.

[Product Information] section

Specifies the target PFM - RM instance.

Product ID label

Specifies the product ID of the target PFM - RM instance. For the product ID to be specified, see the Appendix that describes file name extensions in any manual of the relevant PFM - RM product.

[Target Definitions] section

Specifies the settings for the monitoring target.

Target Host label

Specifies the host name of the monitoring target.

Product-specific labels

In addition to the labels described above, you can specify instance setting items that are specific to the target product (PFM - RM). For the labels that can be specified, see the chapter on installation and setup in any manual for the relevant PFM - RM product. Note that when you specify settings such as the password in interactive mode, you might be prompted to specify the same values again for confirmation. However, you only have to specify these values once in the definition file.

The following shows an example of specifying settings in the definition file.

[Common Definitions]
Definition File Version=0001

[Product Information]
Product ID=7

[Target Definitions]
Target Host=hostname
User=Administrator
Password=aaa
 ...

Notes

When the jpcconf target setup command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

This cannot be executed on a standby node when a PFM - RM monitoring target running on a logical host environment is set.

The maximum number of monitoring targets depends on the PFM - RM instance. If a monitoring target is added when the maximum number of monitoring targets is reached, the KAVE05397-E message is output. For details about the maximum number of monitoring targets for an instance of PFM - RM, see the PFM - RM manuals.

If the definition file includes confidential information such as passwords, save the file in a secured and safe place, and delete the file when the file is no longer needed. If you need to transfer the definition file between hosts, use SFTP communication (FTP communication through an SSH tunnel) or other safe means that are secure against sniffing.

When you execute the command with the -input option, the command execution is interrupted if the definition file does not contain all necessary labels or invalid values are specified for necessary labels in the definition file. If you add the -noquery option to automatically execute the command in a batch or script file, confirm that the settings in the definition file are correct beforehand. If the command is automatically executed, you can check whether the command terminates normally with a message or return value that is output.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The specified service key was not found.

6

The definition file contains errors.

10

The command is being executed.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

109

An attempt to report monitoring target settings to PFM - RM failed.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example

This example adds the new monitoring target targetname1 to the PFM - RM for Platform instance inst1.

jpcconf target setup -key RMPlatform -inst inst1 -target targetname1

Example of executing the command in non-interactive mode

If the -noquery, -input, and -template options are specified, setup can be performed without any queries output from Performance Management. The following shows usage examples.

Example 1

This example outputs the RMPlatformTemplate.txt file as the template file for the PFM - RM for Platform definition file.

# jpcconf target setup -key RMPlatform -template RMPlatformTemplate.txt

Example 2

This example automatically creates target01 through target03 as new monitoring targets in PFM - RM for platform.

This example assumes that the user has prepared definition files RMPlatformTarget01.txt, RMPlatformTarget02.txt, and RMPlatformTarget03.txt by editing the RMPlatformTemplate.txt file output in Example 1 according to the individual instance environments.

# jpcconf target setup -key RMPlatform -inst inst01 -target target01 -input RMPlatformTarget01.txt -noquery
# jpcconf target setup -key RMPlatform -inst inst01 -target target02 -input RMPlatformTarget02.txt -noquery
# jpcconf target setup -key RMPlatform -inst inst01 -target target03 -input RMPlatformTarget03.txt -noquery

jpcconf target unsetup

Format

jpcconf target unsetup     -key service-key
                           -inst instance-name
                           -target monitoring-target-name
                          [-lhost logical-host-name]

Function

The jpcconf target unsetup command deletes a monitoring target monitored by a PFM - RM instance.

Hosts that can execute the command

PFM - Manager (can only be executed on a host on which PFM - RM is installed)

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the PFM - RM service key set for the monitoring target to be deleted. A product name can also be specified when the product name display functionality is enabled.

-inst instance-name

Specifies the PFM - RM instance name set for the monitoring target to be deleted. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

-target monitoring-target-name

Specifies the monitoring target to be deleted, as created within the PFM - RM instance. For monitoring-target-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters or hyphens (-). Names starting with a hyphen (-) or the name All cannot be specified.

-lhost logical-host-name

Specifies the logical host name of the host on which this command is executed. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

Notes

When the jpcconf target unsetup command is executed, the version of PFM - Manager or PFM - Base on the execution host must be 09-00 or later.

This cannot be executed on a standby node when a PFM - RM monitoring target running on a logical host environment is deleted.

If you delete a monitoring target, check whether alarm tables are bound to the monitoring target agent. If alarm tables are bound, unbind all of them, and then delete the monitoring target.

After executing this command, an unnecessary agent remains under the User Agents node in the Agents tree in PFM - Web Console. If you do not want that agent to be displayed, delete it manually.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The specified service key was not found.

10

The command is being executed.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

109

An attempt to report monitoring target deletion to PFM - RM failed.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

Usage example

This example deletes monitoring target targetname1 from PFM - RM for Platform instance inst1.

jpcconf target unsetup -key RMPlatform -inst inst1 -target targetname1

jpcimevt

Format

jpcimevt   [-i event-ID]
           [-m message]
           [-s alarm-status]
           [[-e extended-attribute-name=extended-attribute-value]...]
           [-r event-server-name]

Function

The jpcimevt command registers a JP1 event in the event server and sends the registered event to JP1/IM.

This command can be used when issuing a JP1 event as an alarm action. For details about how to issue a JP1 event as an alarm action, see the chapter describing alarm definitions and manipulation in the Job Management Partner 1/Performance Management User's Guide.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

None

In UNIX:

None

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-i event-ID

Specifies the event ID of the JP1 event to be registered, as a hexadecimal number in the range from 0 to 1fff or 7fff8000 to 7fffffff. If you omit this argument, 0 is assumed.

-m message

Specifies a message text for the JP1 event that is to be registered. For message, specify a string of 1 to 1023 bytes. Note that if you issue a JP1 event with the Action Handler service whose version is 09-00 or earlier, the length of the message text must be from 0 through 128 bytes.

If the message contains spaces, enclose the entire message in double quotation marks ("). If this argument is omitted, no message text is recorded. In the New Alarm > Action Definitions window or the Edit > Action Definitions window, if you specify %MTS for Command Definition, you can send the message text set in the alarm to JP1/IM.

-s alarm-status

Specifies an alarm status. This alarm status is converted to a JP1 event level. To convert the value of the -s option to a JP1 event, specify %SCS for Command Definition in the New Alarm > Action Definitions window or the Edit > Action Definitions window. The following table shows the values that can be specified in the -s option and the values after conversion:

Specifiable value

Description

JP1 event level

"OK"

Alarm status is normal (green)

"Information"

"WARNING"

Alarm status is warning (yellow)

"Warning"

"EXCEPTION"

Alarm status is abnormal (red)

"Error"

If you specify both the -s and -e options to define the event level, the -s option takes precedence. If you omit both the -s and -e options, nothing is set for the JP1 event level.

-e extended-attribute-name=extended-attribute-value

Specifies an extended attribute to be registered in the JP1 event. You can specify multiple sets of -e extended-attribute-name=extended-attribute-value. If a specified extended attribute name or extended attribute value contains a space, enclose the entire name or value in double quotation marks ("). There must be no spaces immediately before or after the equal sign (=).

The operation cannot be guaranteed if the same extended attribute is specified more than once.

-r event-server-name

Specifies the name of the event server in which the JP1 event is to be registered. For event-server-name, specify a string from 1 to 255 bytes.

Only an event server that is running at the local host can be specified. You specify this option when you are using JP1/Base in a cluster system.

If this option is omitted, the same event server name as the local host is assumed.

Notes

JP1/Base must be installed on the host that issues the JP1 event as an alarm action.

To issue JP1 events, you must first start the JP1/Base event server.

If the length of the message text exceeds 1,023 bytes, the message text will be truncated so that the length does not exceed 1,023 bytes. If truncation occurs, a KAVE05418-W message is output. Note that in the Action Handler service whose version is 09-00 or earlier, if the message text is longer than 128 bytes, an error occurs and no JP1 event is issued. At this time, a KAVE05223-E message is output.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

200

A memory shortage occurred.

211

The file cannot be accessed.

250

An attempt to send a JP1 event failed.

255

An unexpected error occurred.

Usage example

This example registers an event whose event ID is 111, alarm status is OK, extended attribute name is EXTATTR, and extended attribute value is Extend Value:

jpcimevt -i 111 -s OK -e EXTATTR="Extend Value"

jpcmkkey

Format

jpcmkkey
               -user user-name
               [-password password]
               [-mx maximum-heap-size]
               [-ms initial-heap-size]
               [-y]
               [-nocheck]

Function

The jpcmkkey command creates a key file for authentication. The key file is required to execute the following commands on the host on which PFM - Web Console is installed:

jpcasrec update

jpcasrec output

jpcaspsv update

jpcaspsv output

jpcprocdef create

jpcprocdef delete

jpcprocdef list

jpcprocdef output

jpcrdef create

jpcrdef delete

jpcrdef output

jpcrpt

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-user user-name

Specifies the Performance Management user name used for logon authentication for execution of a command that requires the key file for authentication.

For user-name, specify a string of 1 to 16 bytes, consisting of single-byte alphanumeric characters, single-byte spaces, and the following symbols:

! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

If the string that you want to specify contains single-byte spaces, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols. Exceptionally, if you want to use a backslash (\) at the end of a string, specify four backslashes (\\\\). Any leading and trailing spaces in the input character string are ignored.

-password password

Specifies the password for the Performance Management user specified in the -user option.

For password, specify a string of 1 to 16 bytes, consisting of single-byte alphanumeric characters, single-byte spaces, and the following symbols:

! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

If this option is omitted, the command assumes a password with a length of 0 bytes. If you want to specify a 0-byte string or a string that contains single-byte characters, enclose the entire string in double quotation marks ("). Note that you might need to add escape characters when specifying single-byte symbols. Exceptionally, if you want to use a backslash (\) at the end of a string, specify four backslashes (\\\\). Any leading and trailing spaces in the input character string are ignored.

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). Normally, you do not need to specify this option.

The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). Normally, you do not need to specify this option.

The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-y

Specifies that if the key file already exists, the command is to overwrite it without asking for confirmation. If this option is omitted and the key file already exists, the command displays a confirmation message asking if the file is to be overwritten. If the user enters y or Y as a response to the message, the command overwrites the file. If the user enters any other value, the command cancels creation of the authentication key file.

-nocheck

Specifies whether the validity of the specified user name and password is to be checked. Validity is determined based on whether the user can log into PFM - Manager (View Server service). If you specify this option, validity is not checked. If you omit this option, validity is checked. Note that the system checks the character string length and the validity of characters even when it does not perform the check for the user name and password.

Note

Execute this command while PFM - Manager (View Server service) is running. If you execute the command in JP1 authentication mode, make sure that authentication is possible on the PFM - Manager side.

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

Creation of authentication key file failed.

11

The specified user name or password resulted in a PFM - Manager authentication error.

80

The user canceled creation of the authentication key file.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

202

File access error occurred.

222

A communication error occurred (IP address could not be acquired).

255

An unexpected error occurred.

Usage example

This example creates a key file for authentication with ADMINISTRATOR and xxxxx specified as the user name and password, respectively, to be used for login authentication during command execution:

jpcmkkey -user "ADMINISTRATOR" -password "xxxxx"

jpcparamdump

Format

jpcparamdump    -d output-destination-directory

Function

The jpcparamdump command outputs the setting information of the Performance Management program on the command execution host into a text file. The jpcparamdump command can collect the setting information of the following products:

PFM - Manager (10-10-10 and later)

PFM - Base (10-10-10 and later)

PFM - Agent for Platform (Windows and UNIX) (10-00 and later)

PFM - RM for Platform (10-00 and later)

PFM - RM for VM (10-00 and later)

Hosts that can execute the command

PFM - Manager

PFM - Base

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-d output-destination-directory

Specifies the directory to which the setting information file is to be output, with the absolute path that is 35 bytes or less. The directory specified for this option must satisfy the following conditions:

It does not exist before the command runs.

It is not under the Performance Management installation directory.

The name consists of single-byte alphanumeric characters or single-byte symbols.

However, the following single-byte symbols cannot be specified:

" & ' * , ; < > ? ^ ` |

If you specify a string that contains single-byte spaces or parentheses (( )), enclose the entire string in double quotation marks (").

In addition, you cannot specify a directory name that ends with a backslash (\).

Notes

Before executing the command, verify that the character encoding for the command execution environment matches the character encoding used when Performance Management service starts up. If not, a file that uses multiple character encodings might be output.

If the command fails, half-created files and directories remain under the specified path. Before you re-execute the command, delete these files and directories.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Output information

When you execute the jpcparamdump command, files are created under the directory that is specified for the -d option and then the setting information of the target products is output to the files. If a logical environment has been configured on the command execution host, this command outputs the setting information for the logical host, in addition to the setting information for the physical host.

For details on the configuration of the directory created by the jpcparamdump command and the files, see I. Information Output by the jpcparamdump Command.

jpcprocdef create

Format

jpcprocdef create     -agent service-ID
                      -f input-file-name
                      [-removeOthers]
                      [-noquery]

Function

The jpcprocdef create command is used to set new application definitions for the specified agent. This command is also used to edit the existing application definitions of the specified agent. The definitions to be applied to the agent are provided by an XML file specified as the application definition file on the command line. Because the file can contain multiple application definitions, these definitions can be applied all at once by specifying the file.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Before you can execute this command, you must create an authentication key file as a user account with the administrator user permission for Performance Management#. For details, see jpcmkkey.

#

Any Performance Management users or JP1 users who want to operate Performance Management must have this permission level.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-agent service-ID

Specifies the service ID of the Agent Collector service or a remote agent to identify the agent for which application definitions will be set. Wildcard characters cannot be used.

The service ID to be specified differs depending on the monitoring agent being used, as shown in the following table.

Monitoring agent being used

Service ID to be specified

PFM - Agent for Platform (Windows)

Service ID of the Agent Collector service

PFM - Agent for Platform (UNIX)

PFM - RM for Platform

Service ID of the remote agent

The following service IDs cannot be specified:

Service ID of the Agent Store service, Remote Monitor Collector service, Remote Monitor Store service, or a group agent

Service ID of a product that is not PFM - Agent for Platform or PFM - RM for Platform

-f input-file-name

Specifies the name of the application definition file. You can specify an absolute path or relative path.

-removeOthers

Specifies whether to delete any definitions with names that are not specified in the application definition files.

The following describes the command behavior when this option is specified and when it is not specified.

When this option is specified:

All application definitions on the target agent are updated with the definitions specified in the application definition file. If there are application definitions whose names are not specified in the file, the command asks the user whether to delete the definitions.

When this option is not specified:

Only the application definitions specified in the application definition file are added or updated.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

The command behavior changes in various situations, as described below:

If application definitions with the same names as application definitions specified in the application definition file already exist on the target agent:

The existing application definitions will be updated with the corresponding application definitions in the application definition file.

If the -removeOthers option is specified:

Application definitions with names that are not specified in the application definition file will be deleted.

Format of the application definition file

XML tag specifications

application-definition

Item

Description

Description

The root tag for the settings in one application definition

Specifiable value

None

Omissible

No

Attribute

None

Parent element

pr-cli-parameters

Child element

name (One application-definition element must have only one name child element. This child element cannot be omitted.)

virtual-env-id (One application-definition element can have only one virtual-env-id child element. This child element can be omitted.)

process01, process02, ..., process15 (One application-definition element must have these 15 child elements. These child elements cannot be omitted.)

name

Item

Description

Description

The name of an application definition

Specifiable value

For details about the character string that can be specified, see the section that describes active and inactive state information for processes in one of the following manuals: (1) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, (2) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, (3) Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

Note that although you can use spaces or line brakes within an element, you must not include unintended spaces or line breaks between the start and end tags of an element.

Omissible

No

Attribute

None

Parent element

application-definition

Child element

None

virtual-env-id

Item

Description

Description

The virtual environment ID

Note:

If the target agent is PFM - Agent for Platform (Windows), the value of this element is ignored.

Specifiable value

For details about the character string that can be specified, see the section that describes active and inactive state information for processes in one of the following manuals: (1) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, (2) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, (3) Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

Note that although you can use spaces or line brakes within an element, you must not include unintended spaces or line breaks between the start and end tags of an element.

Omissible

Yes (If this element is omitted, the command assumes that a blank is specified.)

Attribute

None

Parent element

application-definition

Child element

None

process01, process02, ..., process15

Item

Description

Description

The elements that specify the processes that make up an application definition (each element specifies one process).

The processXX elements correspond to the MonitoringXX properties of the agent.

Specifiable value

The run-time name of a program, command, or service to be monitored (value of MonitoringXX Condition).

For details about the character string that can be specified, see the section that describes active and inactive state information for processes in one of the following manuals: (1) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, (2) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, (3) Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

Note that although you can use spaces or line brakes within an element, you must not include unintended spaces or line breaks between the start and end tags of an element.

Omissible

No

Attribute

label

Specifies the label of a monitoring condition. (The value to be specified for a MonitoringXX Label property of the agent. This attribute is required.)

For details about the character string that can be specified, see the section that describes active and inactive state information for processes in one of the following manuals: (1) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems, (2) Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems, (3) Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

Note that although you can use spaces or line brakes within an element, you must not include unintended spaces or line breaks between the start and end tags of an element.

type

Specifies the field to be monitored. (The value specified for a MonitoringXX Field property of the agent. This attribute is required.)

One of the following eight values can be specified:

none or NONE: Nothing is selected.

program or PROGRAM: Program

commandline or COMMANDLINE: Command line

service or SERVICE#: Service

min

Specifies the minimum number of monitoring targets. (The value specified on the left of the hyphen (-) for a MonitoringXX Range property of the agent. This attribute is required.)

An integer from 0 through 65,535 can be specified. Note that the min value must not be greater than the max value.

max

Specifies the maximum number of monitoring targets. (The value specified on the right of the hyphen (-) for a MonitoringXX Range property of the agent. This attribute is required.)

An integer from 0 through 65,535 can be specified. Note that the min value must not be greater than the max value.

Parent element

application-definition

Child element

None

#

If the target agent is PFM - Agent for Platform (UNIX), service or SERVICE cannot be specified. If service or SERVICE is specified in this case, the command assumes that none is specified.

Examples of specifying settings in the application definition file are shown below. In addition to these examples, a sample application definition file is provided. This sample file might be useful when you create your application definition file. The location of the sample file is as follows.

In Windows:

installation-folder\sample\processmonitoringcommand\

In UNIX:

/opt/jp1pcwebcon/sample/processmonitoringcommand/

Example of specifying settings in the application definition file (when defining one application for Windows monitoring-target hosts):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE pr-cli-parameters SYSTEM "processmonitoring_params.dtd">
<pr-cli-parameters ver="0100">
<application-definition>
<name>PFM - Agent</name>
<virtual-env-id></virtual-env-id>
<process01 label="Health Check" type="program" max="1" min="0">jpcagt0*</process01>
<process02 label="How many agents" type="commandline" max="65535" min="1">*\jp1pc\agt*\agent\jpcagt*</process02>
<process03 label="RM service" type="service" max="1" min="0">JP1PCAGT_7A_*</process03>
<process04 label="Monitoring04" type="none" max="0" min="0"></process04>
<process05 label="Monitoring05" type="none" max="0" min="0"></process05>
<process06 label="Monitoring06" type="none" max="0" min="0"></process06>
<process07 label="Monitoring07" type="none" max="0" min="0"></process07>
<process08 label="Monitoring08" type="none" max="0" min="0"></process08>
<process09 label="Monitoring09" type="none" max="0" min="0"></process09>
<process10 label="Monitoring10" type="none" max="0" min="0"></process10>
<process11 label="Monitoring11" type="none" max="0" min="0"></process11>
<process12 label="Monitoring12" type="none" max="0" min="0"></process12>
<process13 label="Monitoring13" type="none" max="0" min="0"></process13>
<process14 label="Monitoring14" type="none" max="0" min="0"></process14>
<process15 label="Monitoring15" type="none" max="0" min="0"></process15>
</application-definition>
</pr-cli-parameters>

Example of specifying settings in the application definition file (when defining one application that monitors processes that run in a specific virtual environment for UNIX monitoring-target hosts):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE pr-cli-parameters SYSTEM "processmonitoring_params.dtd">
<pr-cli-parameters ver="0100">
<application-definition>
<name>PFM - Agent</name>
<virtual-env-id>1</virtual-env-id>
<process01 label="Health Check" type="program" max="1" min="0">jpcagt0*</process01>
<process02 label="How many agents" type="commandline" max="65535" min="1">jpc*/jp1pc/agt*/agent*</process02>
<process03 label="Monitoring03" type="none" max="0" min="0"></process03>
<process04 label="Monitoring04" type="none" max="0" min="0"></process04>
<process05 label="Monitoring05" type="none" max="0" min="0"></process05>
<process06 label="Monitoring06" type="none" max="0" min="0"></process06>
<process07 label="Monitoring07" type="none" max="0" min="0"></process07>
<process08 label="Monitoring08" type="none" max="0" min="0"></process08>
<process09 label="Monitoring09" type="none" max="0" min="0"></process09>
<process10 label="Monitoring10" type="none" max="0" min="0"></process10>
<process11 label="Monitoring11" type="none" max="0" min="0"></process11>
<process12 label="Monitoring12" type="none" max="0" min="0"></process12>
<process13 label="Monitoring13" type="none" max="0" min="0"></process13>
<process14 label="Monitoring14" type="none" max="0" min="0"></process14>
<process15 label="Monitoring15" type="none" max="0" min="0"></process15>
</application-definition>
</pr-cli-parameters>

Example of specifying settings in the application definition file (when defining two applications that monitor PFM - Manager and PFM - Web Console processes for Windows monitoring-target hosts):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "processmonitoring_params.dtd">
<pr-cli-parameters ver="0100">
<application-definition>
<name>PFM - Manager</name>
<virtual-env-id></virtual-env-id>
<process01 label="jpcah" max="65535" min="1" type="program">jpcah.exe</process01>
<process02 label="jpcagt0" max="65535" min="1" type="program">jpcagt0.exe</process02>
<process03 label="jpcep" max="65535" min="1" type="program">jpcep.exe</process03>
<process04 label="jpcmm" max="65535" min="1" type="program">jpcmm.exe</process04>
<process05 label="jpcnsvr" max="65535" min="1" type="program">jpcnsvr.exe</process05>
<process06 label="jpcstatsvr" max="65535" min="1" type="program">jpcstatsvr.exe</process06>
<process07 label="jpcsto" max="65535" min="2" type="program">jpcsto.exe</process07>
<process08 label="jpctrap" max="65535" min="1" type="program">jpctrap.exe</process08>
<process09 label="jpcvsvr" max="65535" min="1" type="program">jpcvsvr.exe</process09>
<process10 label="Monitoring10" max="0" min="0" type="none"></process10>
<process11 label="Monitoring11" max="0" min="0" type="none"></process11>
<process12 label="Monitoring12" max="0" min="0" type="none"></process12>
<process13 label="Monitoring13" max="0" min="0" type="none"></process13>
<process14 label="Monitoring14" max="0" min="0" type="none"></process14>
<process15 label="Monitoring15" max="0" min="0" type="none"></process15>
</application-definition>
<application-definition>
<name>PFM - Web Console</name>
<virtual-env-id></virtual-env-id>
<process01 label="jpcwebcon" max="65535" min="1" type="program">jpcwebcon.exe</process01>
<process02 label="cjstartweb" max="65535" min="1" type="program">cjstartweb.exe</process02>
<process03 label="cprfd" max="65535" min="1" type="program">cprfd.exe</process03>
<process04 label="httpsd" max="65535" min="2" type="program">httpsd.exe</process04>
<process05 label="rotatelogs2" max="65535" min="4" type="program">rotatelogs2.exe</process05>
<process06 label="Monitoring06" max="0" min="0" type="none"></process06>
<process07 label="Monitoring07" max="0" min="0" type="none"></process07>
<process08 label="Monitoring08" max="0" min="0" type="none"></process08>
<process09 label="Monitoring09" max="0" min="0" type="none"></process09>
<process10 label="Monitoring10" max="0" min="0" type="none"></process10>
<process11 label="Monitoring11" max="0" min="0" type="none"></process11>
<process12 label="Monitoring12" max="0" min="0" type="none"></process12>
<process13 label="Monitoring13" max="0" min="0" type="none"></process13>
<process14 label="Monitoring14" max="0" min="0" type="none"></process14>
<process15 label="Monitoring15" max="0" min="0" type="none"></process15>
</application-definition>
</pr-cli-parameters>

Notes

The user who executes this command must be authenticated by PFM - Manager when executing this command. If an authentication key file has not been created, before executing this command, use the jpcmkkey command to create that file. When specifying values for tags, follow the notes on the performance data collection settings in any manual of the relevant PFM - Agent product or any manual of PFM - RM.

For the same agent, do not edit application definitions concurrently by using the jpcprocdef create command and by using the Process Monitoring Settings window of PFM - Web Console. If you do so, both of the changes attempted by the two methods might be applied incompletely. If this problem occurs, re-execute the jpcprocdef create command to update the application definitions.

When you execute this command, make sure that the PFM - Manager service and the target PFM - Agent or PFM - RM service are running.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

4

There are invalid command arguments.

5

The input XML file is formatted incorrectly.

10

The definitions in the input file are invalid.

11

Authentication by PFM - Manager failed. Alternatively, the user that was specified when the authentication key file was created by using the jpcmkkey command does not have permission to execute the command.

80

When the command was executed without the -noquery option and the user was asked whether to continue processing, the processing was interrupted because the user made a reply that was not Y or y.

100

The Performance Management environment is invalid.

141

The number of application definitions exceeds 64.

144

Command execution failed.

As a result, the application definitions in the input file were applied incompletely.

200

A memory shortage occurred.

202

The input file cannot be accessed.

222

An error occurred during communication processing.

224

Connection to the agent is impossible.

225

The agent does not exist.

226

The agent is not supported.

227

The PFM - Manager host for the connection destination is not supported.

228

The target agent is not set up on the PFM - Manager host for the connection destination.

255

An unexpected error occurred.

Usage example 1

The following example applies the definitions that are specified in the application definition file appdef.xml to the agent TA1hostpfm.

jpcprocdef create -agent TA1hostpfm -f appdef.xml

Usage example 2

The following example overwrites the application definitions that exist on the agent TA1hostpfm with the definitions that are specified in the application definition file appdef.xml, deleting all existing definitions that are not specified in the file.

jpcprocdef create -agent TA1hostpfm -f appdef.xml -removeOthers -noquery

Output example

When this command is executed, detailed information about the command processing is output to the standard output, standard error output, and operation status log file. For the logging specifications, see 3. Log Information Output by Performance Management.

An example of information that is output to the standard output when the processing in Usage example 2 above succeeds is shown below. In this example, OK has been output as the command execution result for the agent specified by a service ID (if the processing fails, ERR is output).

Example of standard output

jpcprocdef create connected to localhost at yyyy MM dd HH:MM:SS.mmm
KAVJK6518-I Multiple application definitions to be overwritten exist.
KAVJK6521-I Multiple application definitions to be deleted exist.
KAVJK6504-I Processing to update application definitions will now continue.
create result OK : TA1hostpfm
jpcprocdef create disconnected at yyyy MM dd HH:MM:SS.mmm

jpcprocdef delete

Format

jpcprocdef delete     -agent service-ID
                      {-name application-definition-name
                      [-name application-definition-name]... | -all}
                      [-noquery]

Function

The jpcprocdef delete command deletes application definitions from the specified agent.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Before you can execute this command, you must create an authentication key file as a user account with the administrator user permission for Performance Management#. For details, see jpcmkkey.

#

Any Performance Management users or JP1 users who want to operate Performance Management must have this permission level.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-agent service-ID

Specifies the service ID of the Agent Collector service or a remote agent to identify the agent from which application definitions will be deleted. Wildcard characters cannot be used.

The service ID to be specified differs depending on the monitoring agent being used, as shown in the following table.

Monitoring agent being used

Service ID to be specified

PFM - Agent for Platform (Windows)

Service ID of the Agent Collector service

PFM - Agent for Platform (UNIX)

PFM - RM for Platform

Service ID of the remote agent

The following service IDs cannot be specified:

Service ID of the Agent Store service, Remote Monitor Collector service, Remote Monitor Store service, or a group agent

Service ID of a product that is not PFM - Agent for Platform or PFM - RM for Platform

-name application-definition-name

Specifies the name of an application definition that is to be deleted from the agent specified by the -agent option. Wildcard characters cannot be used.

To delete multiple application definitions at one time, specify multiple -name options. The command ignores -name options that specify application definitions that do not exist on the agent.

-all

Specify this option to delete all application definitions from the agent specified by the -agent option.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

Notes

The user who executes this command must be authenticated by PFM - Manager when executing this command. If an authentication key file has not been created, before executing this command, use the jpcmkkey command to create that file. When specifying values for tags, follow the notes on the performance data collection settings in any manual of the relevant PFM - Agent product or any manual of PFM - RM.

When you execute this command, make sure that the PFM - Manager service and the target PFM - Agent service are running.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

4

There are invalid command arguments.

11

Authentication by PFM - Manager failed. Alternatively, the user that was specified when the authentication key file was created by using the jpcmkkey command does not have permission to execute the command.

80

When the command was executed without the -noquery option and the user was asked whether to continue processing, the processing was interrupted because the user made a reply that was not Y or y.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

222

An error occurred during communication processing.

224

Connection to the agent is impossible.

225

The agent does not exist.

226

The agent is not supported.

227

The PFM - Manager host for the connection destination is not supported.

228

The target agent is not set up on the PFM - Manager host for the connection destination.

255

An unexpected error occurred.

Usage example

This example deletes the application definition named PFM - Manager from the agent TA1hostpfm.

jpcprocdef delete -agent TA1hostpfm -name "PFM - Manager"

Output example

When this command is executed, detailed information about the command processing is output to the standard output, standard error output, and operation status log file. For the logging specifications, see 3. Log Information Output by Performance Management.

An example of information that is output to the standard output when the processing in Usage example above succeeds is shown below. In this example, OK has been output as the command execution result for the agent specified by a service ID (if the processing fails, ERR is output).

Example of standard output

jpcprocdef delete connected to localhost at yyyy MM dd HH:MM:SS.mmm
KAVJK8605-Q Do you want to delete the application definition "PFM - Manager" of the agent "TA1hostpfm"? [y/n] (y is entered)
delete result OK : TA1hostpfm
jpcprocdef delete disconnected at yyyy MM dd HH:MM:SS.mmm

jpcprocdef list

Format

jpcprocdef list     -agent service-ID

Function

The jpcprocdef list command lists the names of application definitions that exist on the specified agent. Before you execute the jpcprocdef delete command or jpcprocdef output command, you can check an application definition name that can be specified for the -name option by using the jpcprocdef list command. The agent definitions are listed in the order in which they are set on the agent.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Before you can execute this command, you must create an authentication key file as a user account with the administrator user permission for Performance Management#. For details, see jpcmkkey.

#

Any Performance Management users or JP1 users who want to operate Performance Management must have this permission level.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-agent service-ID

Specifies the service ID of the Agent Collector service or a remote agent to identify the agent whose application definitions will be listed. Wildcard characters cannot be used.

The service ID to be specified differs depending on the monitoring agent being used, as shown in the following table.

Monitoring agent being used

Service ID to be specified

PFM - Agent for Platform (Windows)

Service ID of the Agent Collector service

PFM - Agent for Platform (UNIX)

PFM - RM for Platform

Service ID of the remote agent

The following service IDs cannot be specified:

Service ID of the Agent Store service, Remote Monitor Collector service, Remote Monitor Store service, or a group agent

Service ID of a product that is not PFM - Agent for Platform or PFM - RM for Platform

Notes

The user who executes this command must be authenticated by PFM - Manager when executing this command. If an authentication key file has not been created, before executing this command, use the jpcmkkey command to create that file. When specifying values for tags, follow the notes on the performance data collection settings in any manual of the relevant PFM - Agent product or any manual of PFM - RM.

When you execute this command, make sure that the PFM - Manager service and the target PFM - Agent service are running.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

4

There are invalid command arguments.

11

Authentication by PFM - Manager failed. Alternatively, the user that was specified when the authentication key file was created by using the jpcmkkey command does not have permission to execute the command.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

222

An error occurred during communication processing.

224

Connection to the agent is impossible.

225

The agent does not exist.

226

The agent is not supported.

227

The PFM - Manager host for the connection destination is not supported.

228

The target agent is not set up on the PFM - Manager host for the connection destination.

255

An unexpected error occurred.

Usage example

This example lists the names of application definitions that exist on the agent TA1hostpfm.

jpcprocdef list -agent TA1hostpfm

Output example

When this command is executed, detailed information about the command processing is output to the standard output, standard error output, and operation status log file. For the logging specifications, see 3. Log Information Output by Performance Management.

An example of information that is output to the standard output is shown below.

Example of standard output

"PFM - Manager"
"PFM - Web Console"

jpcprocdef output

Format

jpcprocdef output     -agent service-ID
                      {-name application-definition-name
                      [-name application-definition-name]... | -all}
                      -f export-file-name
                      [-noquery]

Function

The jpcprocdef output command exports application definitions that exist on the specified agent to a file in XML format. The exported file can be used to check the current contents of application definitions. The exported file can also be used as an input file for the jpcprocdef create command.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Before you can execute this command, you must create an authentication key file as a user account with the administrator user permission for Performance Management#. For details, see jpcmkkey.

#

Any Performance Management users or JP1 users who want to operate Performance Management must have this permission level.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-agent service-ID

Specifies the service ID of the Agent Collector service or a remote agent to identify the agent whose application definitions will be exported. Wildcard characters cannot be used.

The service ID to be specified differs depending on the monitoring agent being used, as shown in the following table.

Monitoring agent being used

Service ID to be specified

PFM - Agent for Platform (Windows)

Service ID of the Agent Collector service

PFM - Agent for Platform (UNIX)

PFM - RM for Platform

Service ID of the remote agent

The following service IDs cannot be specified:

Service ID of the Agent Store service, Remote Monitor Collector service, Remote Monitor Store service, or a group agent

Service ID of a product that is not PFM - Agent for Platform or PFM - RM for Platform

-name application-definition-name

Specifies the name of an application definition to be exported from the agent specified by the -agent option. Wildcard characters cannot be used.

To export multiple application definitions at one time, specify multiple -name options. In this case, the application definitions will be exported to a file in the order in which they are specified by -name options, rather than in the order in which they are set on the agent. The command ignores -name options that specify application definitions that do not exist on the agent.

-all

Specify this option to export all application definitions that exist on the agent specified by the -agent option. The agent definitions are exported in the order in which they are set on the agent.

-f export-file-name

Specifies the name of the export-destination application definition file. If multiple application definitions are specified, they will be exported collectively to one file. The file name can be specified with either a relative path or an absolute path.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond. Specify this option if you want the command to run in non-interactive mode.

If the application definition file specified for the -f option already exists, the file will be overwritten by the new file.

Format of the application definition file

See Format of the application definition file in the description of the jpcprocdef create command.

Notes

The user who executes this command must be authenticated by PFM - Manager when executing this command. If an authentication key file has not been created, before executing this command, use the jpcmkkey command to create that file. When specifying values for tags, follow the notes on the performance data collection settings in any manual of the relevant PFM - Agent product or any manual of PFM - RM.

When you execute this command, make sure that the PFM - Manager service and the target PFM - Agent service are running.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

An export file could not be created.

4

There are invalid command arguments.

11

Authentication by PFM - Manager failed. Alternatively, the user that was specified when the authentication key file was created by using the jpcmkkey command does not have permission to execute the command.

21

The export file cannot be accessed.

80

When the command was executed without the -noquery option and the user was asked whether to continue processing, the processing was interrupted because the user made a reply that was not Y or y.

100

The Performance Management environment is invalid.

142

Some of the specified application definitions do not exist.

145

All specified application definitions do not exist.

146

No application definitions are set on the agent.

200

A memory shortage occurred.

222

An error occurred during communication processing.

224

Connection to the agent is impossible.

225

The agent does not exist.

226

The agent is not supported.

227

The PFM - Manager host for the connection destination is not supported.

228

The target agent is not set up on the PFM - Manager host for the connection destination.

255

An unexpected error occurred.

Usage example

This example exports the contents of the application definition named PFM - Manager that is set on the agent TA1hostpfm.

jpcprocdef output -agent TA1hostpfm -name "PFM - Manager" -f appdef.xml

Output example

When this command is executed, detailed information about the command processing is output to the standard output, standard error output, and operation status log file. For the logging specifications, see 3. Log Information Output by Performance Management.

An example of information that is output to the standard output is shown below. In this example, OK has been output as the command execution result for the agent specified by a service ID (if the processing fails, ERR is output).

Example of standard output

jpcprocdef output connected to localhost at yyyy MM dd HH:MM:SS.mmm
output result  OK : TA1hostpfm
jpcprocdef output disconnected at yyyy MM dd HH:MM:SS.mmm

Output file

An example of a file output by this command is shown below.

Example of output file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "processmonitoring_params.dtd">
<pr-cli-parameters ver="0100">
<application-definition>
<name>PFM - Manager</name>
<virtual-env-id></virtual-env-id>
<process01 label="jpcah" max="65535" min="1" type="none">jpcah.exe</process01>
<process02 label="jpcagt0" max="65535" min="1" type="program">jpcagt0.exe</process02>
<process03 label="jpcep" max="65535" min="1" type="program">jpcep.exe</process03>
<process04 label="jpcmm" max="65535" min="1" type="program">jpcmm.exe</process04>
<process05 label="jpcnsvr" max="65535" min="1" type="program">jpcnsvr.exe</process05>
<process06 label="jpcstatsvr" max="65535" min="1" type="program">jpcstatsvr.exe</process06>
<process07 label="jpcsto" max="65535" min="2" type="program">jpcsto.exe</process07>
<process08 label="jpctrap" max="65535" min="1" type="program">jpctrap.exe</process08>
<process09 label="jpcvsvr" max="65535" min="1" type="program">jpcvsvr.exe</process09>
<process10 label="Monitoring10" max="0" min="0" type="none"></process10>
<process11 label="Monitoring11" max="0" min="0" type="none"></process11>
<process12 label="Monitoring12" max="0" min="0" type="none"></process12>
<process13 label="Monitoring13" max="0" min="0" type="none"></process13>
<process14 label="Monitoring14" max="0" min="0" type="none"></process14>
<process15 label="Monitoring15" max="0" min="0" type="none"></process15>
</application-definition>
</pr-cli-parameters>

jpcras

Format

jpcras     directory-name
           service-key
          [all|data|dump]
          [lhost=logical-host-name]
          [inst=instance-name]

Function

The jpcras command collects information about PFM - Manager, PFM - Agent, PFM - RM, or PFM - Base, as well as OS information. You use this command when a problem occurs in PFM - Manager, PFM - Agent, PFM - RM, or PFM - Base.

This command collects information about the host where this command executes or maintenance information for the logical host specified in the lhost option. The collected information is stored in a specified directory. In UNIX, the collected information is compressed by a combination of the tar and compress commands or a combination of the tar and gzip commands. In Windows, however, the collected information is stored in uncompressed format. If you want the collected information to be stored in compressed format, compress the information manually.

When a problem occurs, there is other information that is needed, in addition to the information that can be collected by this command. For details on the information to be collected when a problem occurs, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

directory-name

Specifies the name of the directory in which the collected information is to be stored. For directory-name, specify a string of 1 to 127 bytes, consisting of alphanumeric characters and symbols. A relative path cannot be used. The absolute path must be used. Note that the following symbols cannot be specified:

; , * ? ' " < > | & ^ `

If the directory name contains a space, enclose the entire name in double quotation marks ("). If you specify any of the following symbols, enclose it in double quotation marks (") in order to prevent it from being analyzed by the shell or the command prompt:

( )

Do not specify the Performance Management installation directory in directory-name.

A directory name for a removable medium, such as a floppy disk, cannot be specified in this option.

For this option, you cannot specify the directory name of a removable medium such as a floppy disk.

In UNIX, the collected information is saved as a file named jpcrasYYMMDD#.tar.Z (when compressed by the compress command) or jpcrasYYMMDD#.tar.gz (when compressed by the gzip command) in the specified directory.

In Windows, a file for the collected information is copied uncompressed to the folder specified by this option.

#

YYMMDD indicates the file creation date:

YY

Last two digits of the year.

MM

Month, in the range 01 to 12.

DD

Date, in the range 01 to 31.

service-key

Specifies the service key of the service for which information is to be collected. Note that you cannot specify a product name even if the product name display functionality is enabled. You can also specify the following in service-key:

all: Specifies all services of Performance Management programs.

mgr: Specifies the PFM - Manager services (excluding the Action Handler and Status Server services).

act: Specifies the Action Handler service.

stat: Specifies the Status Server service.

For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

[all|data|dump]

Specifies the information that is to be collected. Different information is collected for each of these specifications; normally, all is specified.

The following tables show for both OSs the information that is collected depending on the specification of this option.

Table 2‒23: Information collected by the jpcras command (in Windows)

Information collected

Option

all

data

dump

Omitted

System log

Y

N

N

Y

Common message log

Y

N

N

Y

Service configuration information

Y

N

N

Y

Process information

Y

N

N

Y

Version information

Y

N

N

Y

System file

Y

N

N

Y

Database information

Y

Y

N

Y#

OS information

System information

Y

N

N

Y

Network status

Y

N

N

Y

Host name

Y

N

N

Y

Windows Firewall information

Y

N

N

Y

Dump information

Y

N

Y

N

Legend:

Y: Information is collected.

N: Information is not collected.

#

View Server, Agent Store, and Remote Monitor Store service database information is not collected when specification of the option is omitted. In this case, collected is the database information for the Master Store, Master Manager, and Name Server services.

Table 2‒24: Information collected by the jpcras command (in UNIX)

Information collected

Option

all

data

dump

Omitted

System log

Y

N

N

Y

Common message log

Y

N

N

Y

Service configuration information

Y

N

N

Y

Process information

Y

N

N

Y

Version information

Y

N

N

Y

System file

Y

N

N

Y

Database information

Y

Y

N

Y#

OS information

Patch information

Y

N

N

Y

Kernel information

Y

N

N

Y

Version information

Y

N

N

Y

Network status

Y

N

N

Y

Environment variable

Y

N

N

Y

Host name

Y

N

N

Y

Dump information

Y

N

Y

N

Legend:

Y: Information is collected.

N: Information is not collected.

#

View Server, Agent Store, and Remote Monitor Store service database information is not collected when specification of the option is omitted. In this case, collected is the database information for the Master Store, Master Manager, and Name Server services.

For details about the information that can be collected, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

lhost=logical-host-name

Specifies the host environment in which the command is to be executed. You use this argument when a logical host has been configured on the machine that is used to execute the command. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters.

If this argument is omitted, maintenance information for all host environments is collected. Wildcard characters cannot be used.

inst=instance-name

Specifies an instance name in order to collect information about that instance. This option is applicable only when a PFM - Agent or PFM - RM with an instance environment is specified in service-key. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

If this option is omitted, information is collected for all instances.

Notes

Before you can execute this command, you must make the directory containing the command into the current directory.

When you collect the database information for the Agent Store or Remote Monitor Store service by specifying the all or data option, you do not need to stop that service.

If the value of the JPC_COLIMPORT environment variable is set to 1, the database files in the import directory of the Store service are collected.

If the version of the Store service is 2.0, first execute the two commands listed below to collect the data other than database data, and then collect troubleshooting data from the database. When the Store version is 2.0, the database is large and the collection of data takes time. Depending on the time required, investigation of the problem could be delayed.

jpcras directory-name all

jpcras directory-name all dump

If the database is small, execute the following command to collect data that also includes the data in the database:

jpcras directory-name all all

When you execute the jpcras command, the data in the database of the Store service is collected, but the data in the database in the import directory is not collected. To collect the databases in the import directory, set the value of the JPC_COLIMPORT environment variable to 1.

Depending on the size of the file to be collected and the network environment, it may take some time for the command's processing to execute.

The command cannot collect the specified information in a system in which the syslog file is not output to the default path and file name. In such a system, you must find a different method for collecting the information.

You must specify the arguments in the order they appear in Format.

Do not specify directory-name as a relative path.

Do not specify the Performance Management installation directory in directory-name.

Specify in directory-name an empty directory that contains no file or directory.

Make sure that there is enough disk space available. Estimate the available disk space on the basis of the amount of disk space each product is using.

If this command is executed while there is a disk capacity shortage or memory shortage, an OS message might be output. However, if the KAVE06010-I message is displayed, the maintenance information has been correctly collected and this OS message can be ignored.

If the KAVE05035-E message is output, check the available space on the disk and in memory based on the instructions in the OS message.

If the KAVE05213-E message is displayed, collect a list of the files stored in the Performance Management installation directory, in addition to the collected maintenance information.

If an error occurs during file collection, the file or directory that was being collected remains in the following directory; such remaining files or folders should be deleted as necessary:

In Windows:

Folder specified in directory-name

In UNIX:

Folder specified in directory-name/jpcwk*

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

When you execute the jpcras command, jpctool service list -id "*" -host "*" is executed to acquire a list of PFM services and to check the startup status. If a firewall exists between the host executing the command and the hosts within another PFM system, or if the system configuration is large, executing jpctool service list -id "*" -host "*" might take a long time. In such cases, set the JPC_COLCTRLNOHOST environment variable to 1 to suppress the processing of jpctool service list -id "*" -host "*" and reduce the command execution time.

When you execute the jpcras command on a UNIX environment, regarding free disk space requirements, note the following:

The storage directory specified for the jpcras command must have twice as much free disk space as the amount collected.

Use the /tmp or /var/tmp directory for the tar command processing. Note that the directory used differs depending on the OS environment.

The following shows an execution example for the jpcras command.

jpcras /usr/ras all all

The data collected by the jpcras command is assumed to be 100 MB. In this case, the free disk space required for the /usr/ras directory is 200 MB. Note that 100 MB of free disk space is temporarily needed in the /tmp or /var/tmp directory, for the tar command processing.

Before you execute this command on a PFM - Agent or PFM - RM host, check whether the option for restricting remote operation from Agent hosts is enabled on the PFM - Manager host. If that option is enabled, you can collect only information about the local host.

If PFM is in a cluster environment, information about the shared disk and physical hosts must be collected. If the jpcras command is executed without the lhost option when the shared disk is online, the command collects information about the shared disk and physical hosts. Therefore, use this command to collect information without specifying the lhost option even if PFM is in a cluster environment. The lhost option is a legacy that has been left for compatibility purposes only.

In a cluster system, execute this command at all nodes in the cluster system. Also, if the system is operated in a multiple-monitoring environment, execute this command on both the primary and secondary hosts.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

100

The Performance Management environment is invalid.

102

The specified logical host name or instance has not been set up.

105

Current directory is not the directory that contains the jpcras command.

210

A disk space shortage occurred.

211

Collection target directory cannot be accessed.

255

An unexpected error occurred.

Usage example 1

This example collects all information in a UNIX host and stores the collected information in the /tmp/jp1pc directory:

jpcras /tmp/jp1pc all all

Usage example 2

This example collects dump information for PFM - Agent for Platform (UNIX) in a UNIX host and stores the collected information in the /tmp/jp1pc directory:

jpcras /tmp/jp1pc agtu dump

jpcrdef create

Format

jpcrdef create     [-mx maximum-heap-size]
                   [-ms initial-heap-size]
                   [-dateformat date-format-pattern-name]
                   [-dateseparator date-format-separator-name]
                   input-file

Function

The jpcrdef create command connects to PFM - Manager and creates a new report definition. The command acquires the contents of the definition from the XML-format parameter file specified as a command line argument. Multiple report definitions can be specified and created in one parameter file at the same time.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions or general user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-dateformat date-format-pattern-name

Specifies the name of the date format pattern that is used to identify the format of dates specified in the <expression> tag in the input file. The following date format pattern names can be specified:

pattern-ddMMyyyy

pattern-MMddyyyy

pattern-yyyyMMdd

-dateseparator date-format-separator-name

Specifies the character string that is used to identify the format of separators specified in the <expression> tag in the input file. The following date format separator names can be specified:

space

slash

hyphen

period

input-file

Specifies the XML-format parameter file that is to be used to create the new report(s). This parameter file must be created according to the Parameter file format described below. You can specify the absolute file path name, relative file path name, or file name. When the name is not the absolute file path, the command assumes the current directory.

Parameter file format

XML tag specifications

report-definitions

Type

Description

Description

Root tag for report definition information

Specifiable value

None

Omissible

No

Attribute

None

Parent element

pr-cli-parameters

Child element

report-definition

report-definition

Type

Description

Description

Specifies a single report definition.

Specifiable value

None

Omissible

No

Attribute

name

Specify a report definition name with 1 to 64 double-byte and/or single-byte characters (rather than 1 to 64 bytes). If the report definition name contains \ or /, specify it as \\ or \/, respectively. If the specified report definition name already exists, an error results. If the parent-folder attribute is specified but the name attribute is omitted, an error results. If spaces are specified before and/or after the report definition name, the name is registered without the leading and/or trailing spaces.

parent-folder

Specify the name of the directory that contains the report definition specified in the name attribute. The name that you specify is a slash (/) separated path from the root directory. The path can have 1 to 64 double-byte and/or single-byte characters (rather than 1 to 64 bytes). For a path, specify directories sequentially separated by / starting from the highest-level directory. If the directory name contains \ or /, specify it as \\ or \/, respectively. The report definition directory in the system definition cannot be specified. If the specified directory does not exist, the command creates it. If this attribute is omitted, an error results. An error results if spaces are specified before and/or after the directory name.

For example, to output the report definition named PD define located under the User Reports root directory, specify as follows:

<report-definition name="PD define" parent-folder="/"/>

The following example outputs to a file, all report definitions located in the Dir1 and Dir2 directories under the User Reports root directory:

<report-definition parent-folder="/Dir1/Dir2"/>

id

Ignored, if specified.

read-only

Specify TRUE to cancel creation of the report definition and to process the next report-definition element. When you specify FALSE or you omit this attribute, the command creates the report definition.

Parent element

report-definitions

Child element

product-id

report-type

record

indication-settings

realtime-indication-settings

view-type

drilldown

product-id

Type

Description

Description

Type of product for which report information is to be collected

Specifiable value

Specify a product code that consists of a product ID and a data model version number. A product ID is an upper-case alphabetic character that identifies an agent product. A data model version is a number assigned by an agent. For example, T stands for Windows, U for UNIX, O for Oracle, Q for SQL Server, and M for SAP R/3. The product code is T3.0 for an instance of Windows with data model version 3.0.

When the data model version of report A is equal to or later than the data model version of report B, you can drill down to report B from report A.

Omissible

No

Attribute

None

Parent element

report-definition

Child element

None

report-type

Type

Description

Description

Specifies the report type.

Specifiable value

None

Omissible

No

Attribute

type

Specify one of the following, in all lower-case letters or all upper-case letters:

For a historical (single agent) report

historical-single-agent or

HISTORICAL-SINGLE-AGENT

For a historical (multiple agents) report

historical-multiple-agents or

HISTORICAL-MULTIPLE-AGENTS

For a realtime (single agent) report

realtime-single-agent or

REALTIME-SINGLE-AGENT

Parent element

report-definition

Child element

None

record

Type

Description

Description

Specifies the target record for reports.

Specifiable value

None

Omissible

No

Attribute

id

Specify a record ID. This attribute cannot be omitted. The permitted record attribute depends on the report-type setting. For details, see Table 2-27 Combinations of record attribute and fields that can be specified for reports.

Parent element

report-definition

Child element

fields

condition-expression

fields

Type

Description

Description

Specifies one or more target fields for reports.

Specifiable value

None

Omissible

No

Attribute

None

Parent element

record

Child element

field

field

Type

Description

Description

Specifies one target field for reports.

Specifiable value

Specify a field ID of the selected record. Not all the attributes (table, list, and graph) can be set to FALSE in all field attributes. Make sure that at least one of table, list, or graph is set to TRUE.

If table, list, and graph are all FALSE in all fields, an error results. An error results if the field tag is specified using a duplicate field ID within the same field tag.

Some fields are added, collected, and summed up only when they are recorded in Agent Store and Remote Monitor Store as historical data, such as xxxx(Total). These fields cannot be specified for realtime reports. If specified, an error results. For details, see Table 2-31 Fields that cannot be specified for realtime reports.

Omissible

No

Attribute

table

Specify TRUE to display a table; otherwise, specify FALSE. This attribute cannot be omitted.

list

Specify TRUE to display a list; otherwise, specify FALSE. This attribute cannot be omitted.

graph

Specify TRUE to display a graph; otherwise, specify FALSE. This attribute cannot be omitted.

Specifying TRUE for a text-format field results in an error.

display-name

Specify a user display name with 24 or fewer double-byte and/or single-byte characters.

If this attribute is omitted or the null character (display-name="") or a space (display-name=" ") is specified, the field name is displayed.

Parent element

fields

Child element

None

condition-expression

Type

Description

Description

Specifies a logical operation for the filtering conditional expression.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, it is not set)

Attribute

None

Parent element

record

ref-field

Child element

and

or

expression

expression

Type

Description

Description

Specifies a conditional expression.

Specifiable value

(1) When specified for a filtering condition

Specify a conditional expression in the format field condition ["value"]. Spaces cannot be used to delimit field, condition, and ["value"].

A field whose data type is time_t can be specified only when the value is omitted and specify-when-displayed is set to TRUE.

field

Specify a field in the record expressed as PFM - Manager name. For details about the PFM - Manager name, see the description of records in the applicable PFM - Agent or PFM - RM manuals.

condition

Specify one of the following as the condition value:

=: Field value is equal to ["value"].

<: Field value is less than ["value"].

<=: Field value is equal to or less than ["value"].

>: Field value is greater than ["value"].

>=: Field value is equal to or greater than ["value"].

<>: Field value is any value other than ["value"].

In XML, specify &lt; for < and &gt; for >.

Character string fields are compared in ascending order of ASCII codes.

["value"]

Specify a value enclosed in double quotation marks ("). The permitted maximum length is 2,048 bytes.

The character encoding, data length, and data format depend on the format of the field specified in the left-hand term.

If specify-when-displayed attribute is set to TRUE, this value can be omitted.

The value cannot contain any control character or any of the symbols ( ) [ ] < > = ". If a control character or any of these symbols is specified, an error results.

Specify the value according to the field format described in the PFM - Agent or PFM - RM manuals. The permitted values are as follows:

Characters (specify as is)

Integer (specify a value in the range permitted for Integer)

Decimal value (specify a value in the range permitted for Double; more than 4 decimal places must be rounded to 4 decimal places according to the IEEE754 Rounding to nearest specification standards#)

Date (One of the formats "dd MM yyyy", "MM dd yyyy", or "yyyy MM dd" must be used, depending on a setting in config.xml. For details, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide. The time is always in the format "HH:mm:ss". If you specify -dateformat or -dateseparator during command execution, you must specify the format that corresponds to the specified pattern and separator.)

(2) When specified for the target field for drilldown

Specifies a conditional expression in the format field condition ["value"] or field condition field. Spaces cannot be used to delimit field, condition, and value.

field

Specify a field in the record that was specified for the drilldown report.

condition

See the conditions described in (1) When specified for a filtering condition.

["value"] or field

When specifying a value in the right-hand term

For details about the value to be specified, see ["value"] in (1) When specified for a filtering condition.

When specifying a field in the right-hand term

Specify the field ID of the record, DATETIME field, or ODBC key field. For details about the ODBC key field, see the PFM - Agent or PFM - RM manuals.

Omissible

Yes (if condition-expression is specified, this parameter cannot be omitted)

Attribute

specify-when-displayed

Specify TRUE to set the value during execution; otherwise, specify FALSE. If this attribute is omitted, FALSE is assumed. If you specify FALSE without specifying a value in the logical expression for the element value, an error results.

Parent element

condition-expression

and

or

Child element

None

#

The IEEE754 Rounding to nearest specification standards are as follows:

The target value is compared with two approximate values and rounded to one of the approximate values, whichever is closer to the target value.

If the target value is exactly in the middle of the two approximate values, the approximate values are represented in binary and the target value is rounded to one of the approximate values, whichever ends with 0.

and

Type

Description

Description

Specifies the AND operation of the logical expression specified in expression.

Specifiable value

None

Omissible

Yes (parameter is specified when AND is specified in the conditional expression)

Attribute

None

Parent element

and

or

condition-expression

Child element

expression

and

or

or

Type

Description

Description

Specifies the OR operation of the logical expression specified in expression.

Specifiable value

None

Omissible

Yes (parameter is specified when AND is specified in the conditional expression)

Attribute

None

Parent element

and

or

condition-expression

Child element

expression

and

or

indication-settings

Type

Description

Description

Specifies the report display period, report interval, peak time display, and maximum number of records.

indication-settings can be specified only when report-type is historical-single-agent or historical-multiple-agents. If this parameter is specified when report-type is realtime-single-agent, an error results.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the default is assumed including the child elements)

Attribute

specify-when-displayed

Specify TRUE to specify the value when the report is displayed; otherwise, specify FALSE. If this attribute is omitted, FALSE is assumed.

maximum-number-of-records

Specify the maximum number of records to be displayed in the report, as an integer in the range 1 to 2,147,483,647. If this attribute is omitted, 1,440 is assumed.

Parent element

report-definition

Child element

date-range

report-interval

peak-time

date-range

Type

Description

Description

Specifies the report display period.

Specifiable value

Specify one of the following values:

For the past hour : WITHIN_THE_PAST_HOUR

For the past day (24 hours): WITHIN_THE_PAST_24_HOURS

For the past 7 days: WITHIN_THE_PAST_7_DAYS

For the past month: WITHIN_THE_PAST_MONTH

For the past year: WITHIN_THE_PAST_YEAR

For specifying the value when the report is displayed: SPECIFY_WHEN_DISPLAYED

These values are not case sensitive.

Omissible

Yes (when the parameter is omitted, SPECIFY_WHEN_DISPLAYED is assumed)

Attribute

None

Parent element

indication-settings

Child element

None

report-interval

Type

Description

Description

Specifies the report interval.

Specifiable value

Specify one of the following values (which are not case sensitive):

For minutely: MINUTE

For hourly: HOUR

For daily (every 24 hours): DAY

For weekly: WEEK

For monthly: MONTH

For yearly: YEAR

Specifying a PI record results in an error.

Omissible

Yes (when the parameter is omitted, HOUR is assumed)

Attribute

None

Parent element

indication-settings

Child element

None

peak-time

Type

Description

Description

Displays the report only when a field value reaches its maximum.

Specifiable value

If the record specified in record is a single-instance record, specify one of its field IDs. The system will display the record only as it exists when the field's maximum value for the day occurs. An error results if report-interval is not HOUR, the record is a multiple-instance record, or report-type is HISTORICAL-MULTIPLE-AGENTS.

Omissible

Yes (when the parameter is omitted, no field is set in peak-time)

Attribute

None

Parent element

indication-settings

Child element

None

realtime-indication-settings

Type

Description

Description

Specifies the realtime report refresh interval and display by ranking.

realtime-indication-settings can be specified only when report-type is realtime-single-agent. An error results if this parameter is specified when report-type is not realtime-single-agent.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the defaults are assumed, including for child elements)

Attribute

specify-when-displayed

Specify TRUE to specify the value when the report is displayed; otherwise, specify FALSE. If this attribute is omitted, FALSE is assumed.

indicate-delta-value

Specify TRUE to display delta values; otherwise, specify FALSE. If this attribute is omitted, TRUE is assumed.

Whether or not delta values can be displayed depends on each field that is collected at the agent. For details, see Table 2-30 Delta values in realtime reports and display conditions.

Parent element

report-definition

Child element

refresh-interval

display-by-ranking

refresh-interval

Type

Description

Description

Specifies whether or not the displayed information is to be refreshed automatically, the initial value for the automatic refresh interval (seconds), and the minimum value (seconds).

Specifiable value

None

Omissible

Yes (when the parameter is omitted, automatic updating is assumed)

Attribute

do-not-refresh-automatically

Specify TRUE to not automatically refresh data displayed in the realtime report; otherwise, specify FALSE. If this attribute is omitted, FALSE is assumed.

initial-value

If do-not-refresh-automatically is FALSE, specify the automatic refresh interval for the data displayed in the report, as an integer in the range from the value specified for minimum-value to 3,600 seconds.

If do-not-refresh-automatically is TRUE, specifying initial-value results in an error.

If initial-value and minimum-value are both omitted, the value of initial-value is set to 60 seconds.

If minimum-value is specified but initial-value is omitted, the value of initial-value is set to the value specified for minimum-value.

minimum-value

If do-not-refresh-automatically is FALSE, specify the minimum value permitted as the automatic refresh interval for the data displayed in the report, as an integer in the range 10 to 3,600 seconds.

If do-not-refresh-automatically is TRUE, specifying minimum-value results in an error.

If initial-value and minimum-value are both omitted, the value of minimum-value is set to 60 seconds.

If initial-value is specified but minimum-value is omitted, the value of minimum-value is set to the value specified for initial-value.

Parent element

realtime-indication-settings

Child element

None

display-by-ranking

Type

Description

Description

Specifies that the field specified in the field attribute is to be sorted in ascending or descending order and as many items as are specified in the display-number attribute are to be displayed from the top as ranking data in the report.

This parameter is applicable only to multi-row records (multi-instance records). If it is specified for a single-row record, an error results.

If display-by-ranking and display-key are both specified, the data acquired based on the display-by-ranking condition is displayed according to the display-key condition.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, information is not displayed by ranking)

Attribute

field

Specify the field ID of the field to be used as the basis for display by ranking. Omitting this attribute results in an error.

If the specified field is not permitted for display by ranking, an error results.

For the data types of fields that can be specified for display by ranking, see Table 2-26 Specifiable combinations of parameters (for realtime reports).

display-number

Specify the number of items to be displayed by ranking, as an integer in the range 1 to 100. If this attribute is omitted, 10 is assumed.

in-descending-order

The field used as the basis for display by ranking can be sorted in ascending or descending order and then as many items as specified in the display-number attribute can be displayed from the beginning. Specify

TRUE to sort the field in ascending order and FALSE to sort in descending order. If this attribute is omitted, FALSE is assumed.

Parent element

realtime-indication-settings

Child element

None

view-type

Type

Description

Description

Specifies the report format.

Specifiable value

None

Omissible

Yes (display-key and graph-properties are set to all default values.)

Attribute

None

Parent element

report-definition

Child element

display-key

graph-properties

display-key

Type

Description

Description

Specifies the field for sorting records. If you specify display-key, you cannot specify LINE, AREA, or STACKED_AREA for graph-type.

Specifiable value

Specify the field ID.

Omissible

Yes (when the parameter is omitted, information is displayed in time series)

Attribute

in-descending-order

TRUE: Sort in descending order.

FALSE (or if omitted): Sort in ascending order.

Parent element

view-type

Child element

None

graph-properties

Type

Description

Description

Specifies the graph type and format. If no field is set to graph=true in the <field> tag, specifying the <graph-properties> tag results in an error.

Specifiable value

None

Omissible

Yes

Attribute

show-areas-of-missing-data

Specify TRUE to show areas of missing data, caused by a reason such as an inactive agent; this applies to a graph when the graph type is LINE, AREA, or STACKED_AREA and the data belongs to multiple agents or a multi-instance record. Or, specify FALSE to fill missing data.

If this attribute is omitted, FALSE is assumed.

series-direction

Specify BY_ROW to display graph data by record (row), or specify BY_COLUMN to display graph data by field (column).

If graph-type is LINE, AREA, or STACKED_AREA, this attribute is ignored. If graph-type is LINE, AREA, or STACKED_AREA and the target to be reported is multiple lines of records or multiple agents, BY_COLUMN is assumed; if the target to be reported is neither multiple lines of records nor multiple agents, BY_ROW is assumed.

If this attribute is omitted when graph-type is not LINE, AREA, or STACKED_AREA, BY_ROW is assumed.

Parent element

view-type

Specifies the report display format.

Child element

graph-type

axis-labels

data-label

graph-type

Type

Description

Description

Specifies the type of graph.

Specifiable value

Specify one of the following values:

For a column graph: COLUMN

For a stacked column graph: STACKED_COLUMN

For a bar graph: BAR

For a stacked bar graph: STACKED_BAR

For a pie graph: PIE

For a line graph: LINE

For an area graph: AREA

For a stacked area graph: STACKED_AREA

These values are not case sensitive.

Omissible

Yes (when the parameter is omitted, COLUMN (column graph) is assumed)

Attribute

None

Parent element

graph-properties

Child element

None

axis-labels

Type

Description

Description

Specifies X-axis and Y-axis labels for the graph. If PIE is specified in the <graph-type> tag, specifying an X-axis label or a Y-axis label results in an error.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, neither the X-axis nor Y-axis label is displayed)

Attribute

None

Parent element

graph-properties

Child element

x-axis

y-axis

x-axis

Type

Description

Description

Specifies the X-axis label for the graph.

Specifiable value

A string that is 0 to 40 characters long (a double-byte character is counted as one character)

Omissible

Yes (when the parameter is omitted, the X-axis label is not displayed)

Attribute

None

Parent element

axis-labels

Child element

None

y-axis

Type

Description

Description

Specifies the Y-axis label for the graph.

Specifiable value

A string that is 0 to 40 characters long (a double-byte character is counted as one character)

Omissible

Yes (when the parameter is omitted, the Y-axis label is not displayed)

Attribute

None

Parent element

axis-labels

Child element

None

data-label

Type

Description

Description

Specifies the label display fields. If a single-instance record is specified, or if historical-single-agent is specified in report-type, or if LINE, AREA, or STACKED_AREA is specified in graph-type, specifying data-label results in an error.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the data label is not displayed)

Attribute

None

Parent element

graph-properties

Child element

data-label1

data-label2

data-label1

Type

Description

Description

Specifies the label display field for data label 1. Data label 2 can also be specified. The value for data label 2 is displayed in parentheses to the right of the value of data label 1.

Specifiable value

When report-type is historical-single-agent:

For a single-instance record:

Field ID specified in the fields tag

DATETIME field

For a multi-instance record:

Field ID specified in the fields tag

DATETIME field

Record-specific ODBC key field

When report-type is historical-multiple-agents:

For a single-instance record:

Field ID specified in the fields tag

DATETIME field

DEVICEID field

PROD_INST field

When report-type is realtime-single-agent:

For a single-instance record:

Field ID specified in the fields tag

RECORD_TIME field

For a multi-instance record:

Field ID specified in the fields tag

RECORD_TIME field

Record-specific ODBC key field

For details about the ODBC key field, see the PFM - Agent or PFM - RM manuals.

Omissible

Yes (when the parameter is omitted, data label 1 is not set)

Attribute

None

Parent element

data-label

Child element

None

data-label2

Type

Description

Description

Specifies the label display field for data label 2, expressed as the field ID corresponding to record. Specifying data-label2 without specifying data-label1 results in an error.

Specifiable value

When report-type is historical-single-agent:

For a single-instance record:

Field ID specified in the fields tag

DATETIME field

For a multi-instance record:

Field ID specified in the fields tag

DATETIME field

Record-specific ODBC key field

When report-type is historical-multiple-agents:

For a single-instance record:

Field ID specified in the fields tag

DATETIME field

DEVICEID field

PROD_INST field

When report-type is realtime-single-agent:

For a single-instance record:

Field ID specified in the fields tag

RECORD_TIME field

For a multi-instance record:

Field ID specified in the fields tag

RECORD_TIME field

Record-specific ODBC key field

For details about the ODBC key field, see the PFM - Agent or PFM - RM manuals.

Omissible

Yes (when the parameter is omitted, data label 2 is not set)

Attribute

None

Parent element

data-label

Child element

None

drilldown

Type

Description

Description

Specifies the target field and report for drilldown.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, drilldown is not set)

Attribute

None

Parent element

report-definition

Child element

field-drilldown

report-drilldown

field-drilldown

Type

Description

Description

Specifies the target field for drilldown.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the target field for drilldown is not set)

Attribute

None

Parent element

drilldown

Child element

ref-field

ref-field

Type

Description

Description

Specifies the target field for drilldown.

Specifiable value

None. The field specified in the left-hand term of the conditional expression in expression that can be specified in the condition-expression child element is the field for drilldown report that is specified in the ref-report child element.

Omissible

Yes (when the parameter is omitted, the target field for drilldown is not set)

Attribute

id

Specify the field ID for the record specified in record. If the ref-field element is duplicated by specification of the same id, an error results. If you omit this attribute, you cannot specify condition-expression.

Parent element

field-drilldown

Child element

ref-report

condition-expression

report-drilldown

Type

Description

Description

Specifies the target report for drilldown.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the target report for drilldown is not set)

Attribute

None

Parent element

drilldown

Child element

ref-report

ref-bookmark

ref-report

Type

Description

Description

Specifies a single report definition.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the target report for drilldown is not set)

Attribute

pathname

Specify the directory path and report definition name in the format directory-path/report-definition-name. Specify the directory path sequentially from the root directory. If the directory name contains \ or /, specify it as \\ or \/, respectively. The directory path and report definition name can be specified with 1 to 64 characters (rather than 1 to 64 bytes) respectively. These items can have double-byte characters or single-byte characters, or both. Specifying a non-existent report definition or a report definition specified by report-definition results in an error. If the data model version number of report A is equal to or greater than the data model version number of report B, drilldown from report A to report B is available.

Parent element

ref-field

report-drilldown

Child element

None

ref-bookmark

Type

Description

Description

Specifies one bookmark or combination bookmark.

Specifiable value

None

Omissible

If this tag is omitted, report drilldown is not set.

Attribute

pathname

Specify a folder path and a bookmark name in folder-path/bookmark-name format. For folder-path, specify folder names starting from the root folder and delimit each folder name by using a forward slash (/). If a folder name contains \ or /, write \\ or \/, respectively.

Example: Specifying CPU Trend in the My Bookmark folder under the root directory

/My Bookmark/CPU Trend

When multiple levels exist, specify a folder path by using folder names separated by / (for example, /Folder1/Folder2...).

The folder path and bookmark name can be specified with 1 to 64 characters (rather than 1 to 64 bytes) respectively. These items can have double-byte characters or single-byte characters, or both. If you specify a non-existing bookmark, an error occurs.

Note that the validity of the bookmark itself, such as the associated report definitions and agents, is not checked.

Parent element

report-drilldown

Child element

None

An example of a parameter file for a historical report is shown below.

Example of parameter file (for historical report)

<?xml version="1.0" encoding="UTF-8"?>
<!--  Workload Status (Multi-Agent) report          -->
<!--  displays hourly workload-related data    -->
<!--  for multiple systems over the past 24 hours            -->
<!DOCTYPE pr-cli-parameters SYSTEM "rdef_create_params.dtd">
<pr-cli-parameters ver="0110">
   <report-definitions>
      <report-definition name="Workload Status (Multi-Agent)"
                      parent-folder="/HQ/Monthly/Windows/Operating System/Status Reporting/Daily Trend"
                    read-only="FALSE">
         <product-id>T3.0</product-id>
         <report-type type="historical-multiple-agents"/>
         <record id="PI">
            <fields>
               <field table="true"
                      list="false"
                      graph="true">PROCESSES</field>
               <field table="true"
                      list="false"
                      graph="false">SERVER_SESSIONS</field>
               <field table="true"
                      list="false"
                      graph="false">CONTEXT_SWITCHES_PER_SEC</field>
               <field table="true"
                      list="false"
                      graph="false">SYSTEM_CALLS_PER_SEC</field>
               <field table="true"
                      list="false"
                      graph="false">PCT_TOTAL_PROCESSOR_TIME</field>
               <field table="true"
                      list="false"
                      graph="false">PROCESSOR_QUEUE_LENGTH</field>
               <field table="true"
                      list="false"
                      graph="false">BYTES_TOTAL_PER_SEC</field>
            </fields>
         </record>
         <indication-settings specify-when-displayed="false"
                           maximum-number-of-records="1440">
               <date-range>WITHIN_THE_PAST_24_HOURS</date-range>
               <report-interval>HOUR</report-interval>
               <peak-time/>
         </indication-settings>
         <view-type>
            <graph-properties show-areas-of-missing-data="false"
                                        series-direction="BY_COLUMN">
               <graph-type>LINE</graph-type>
               <axis-labels>
                  <x-axis/>
                  <y-axis>Processes</y-axis>
               </axis-labels>
               <data-label>
                  <data-label1>PROCESSES</data-label1>
                  <data-label2/>
               </data-label>
            </graph-properties>
         </view-type>
      </report-definition>
   </report-definitions>
</pr-cli-parameters>
<!--End of definition for Workload Status (Multi-Agent) report-->

An example of a parameter file for a realtime report is shown below.

Example of parameter file (for realtime report)

<?xml version="1.0" encoding="UTF-8"?>
<!-- CPU Usage - Top 10 Processes report                    -->
<!-- displays top 10 processes in terms of CPU usage in real time-->
<!DOCTYPE pr-cli-parameters SYSTEM "rdef_create_params.dtd">
<pr-cli-parameters ver="0110">
   <report-definitions>
     <report-definition name="CPU Usage - Top 10 Processes"
                      parent-folder="/HQ/Monthly/Windows/Operating System/Troubleshooting/Real-Time"
                      read-only="FALSE">
        <product-id>T3.0</product-id>
        <report-type type="realtime-single-agent"/>
        <record id="PD_PDI">
            <fields>
               <field table="false"
                       list="false"
                      graph="false">INSTANCE</field>
               <field table="true"
                       list="false"
                      graph="false">ID_PROCESS</field>
               <field table="false"
                       list="false"
                      graph="true">PCT_PROCESSOR_TIME</field>
            </fields>
        </record>
        <realtime-indication-settings specify-when-displayed="false"
                                      indicate-delta-value="false">
              <refresh-interval do-not-refresh-automatically="false"
                                      initial-value="30"
                                      minimum-value="10"/>
              <display-by-ranking field="PCT_PROCESSOR_TIME"
                                  display-number="10"
                                  in-descending-order="false"/>
        </realtime-indication-settings>
        <view-type>
            <graph-properties show-areas-of-missing-data="false"
                              series-direction="BY_COLUMN">
               <graph-type>BAR</graph-type>
               <axis-labels>
                  <x-axis>Program(PID)</x-axis>
                  <y-axis>CPU %</y-axis>
               </axis-labels>
               <data-label>
                  <data-label1>INSTANCE</data-label1>
                  <data-label2>ID_PROCESS</data-label2>
               </data-label>
            </graph-properties>
         </view-type>
      </report-definition>
   </report-definitions>
</pr-cli-parameters>
<!--End of definition for CPU Usage - Top 10 Processes report -->

Notes

The command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication.

If an exception occurs while multiple report definitions are being registered, the command cancels registration of that definition and registers the next definition, if any.

Only two elements can be specified under the <and> and <or> tags in the <condition-expression> tag.

The following shows a specification example:

  <and>
     <expression>expression-1</expression>
     <or>
        <expression>expression-2</expression>
        <or>
           <expression>expression-3</expression>
           <or>
              <expression>expression-4</expression>
              <expression>expression-5</expression>
           </or>
        </or>
     </or>
  </and>

The following shows an example of the expression specified in the <expression> tag:

<expression>SEGMENTS_RETRANSMITTED_PER_SEC&gt;"100"</expression>
<expression>RECORD_TIME&gt;"2003 05 31 11:22:33"</expression>

For details about the record, field name, and data type of fields that can be defined, see the PFM - Agent or PFM - RM manuals.

For the parameters for which values are not specified, the command uses the default values to create the report definition. To check all the parameters in a created report definition, execute the output command with the created parameter file specified.

The limitations shown in the following table apply to the combinations of parameters:

Table 2‒25: Specifiable combinations of parameters (for historical reports)

Report type

Record type

Data type of field

Peak time

Field display format

Table

List

Graph

display-key

Historical (single agent) report

Single-instance

string

N

Y

Y

N

Y

char

N

Y

Y

N

Y

time_t

N

Y

Y

N

Y

timeval

N

Y

Y

Y

Y

utime

N

Y

Y

Y

Y

float

Y

Y

Y

Y

Y

ulong

Y

Y

Y

Y

Y

short

Y

Y

Y

Y

Y

double

Y

Y

Y

Y

Y

long

Y

Y

Y

Y

Y

Multi-instance

string

N

Y

Y

N

Y

char

N

Y

Y

N

Y

time_t

N

Y

Y

N

Y

timeval

N

Y

Y

Y

Y

utime

N

Y

Y

Y

Y

float

N

Y

Y

Y

Y

ulong

N

Y

Y

Y

Y

short

N

Y

Y

Y

Y

double

N

Y

Y

Y

Y

long

N

Y

Y

Y

Y

Historical (multiple agents) report

Single-instance

string

N

Y

Y

N

N

char

N

Y

Y

N

N

time_t

N

Y

Y

N

N

timeval

N

Y

Y

Y

N

utime

N

Y

Y

Y

N

float

Y

Y

Y

Y

N

ulong

Y

Y

Y

Y

N

short

Y

Y

Y

Y

N

double

Y

Y

Y

Y

N

long

Y

Y

Y

Y

N

Legend:

Y: Can be specified.

N: Cannot be specified.

Table 2‒26: Specifiable combinations of parameters (for realtime reports)

Report type

Record type

Data type of field

Display by ranking

Field display format

Table

List

Graph

display-key

Realtime (single agent) report

Single-instance

string

N

Y

Y

N

Y

char(n)

N

Y

Y

N

Y

time_t

N

Y

Y

N

Y

timeval

N

Y

Y

Y

Y

utime

N

Y

Y

Y

Y

float

N

Y

Y

Y

Y

ulong

N

Y

Y

Y

Y

short

N

Y

Y

Y

Y

double

N

Y

Y

Y

Y

long

N

Y

Y

Y

Y

Multi-instance

string

N

Y

Y

N

Y

char(n)

N

Y

Y

N

Y

time_t

N

Y

Y

N

Y

timeval

Y

Y

Y

Y

Y

utime

Y

Y

Y

Y

Y

float

Y

Y

Y

Y

Y

ulong

Y

Y

Y

Y

Y

short

Y

Y

Y

Y

Y

double

Y

Y

Y

Y

Y

long

Y

Y

Y

Y

Y

Legend:

Y: Can be specified.

N: Cannot be specified.

The report types include historical (single agent) report and historical (multiple agents) report. The record attributes supported by reports include single-instance and multi-instance. Note that historical (multiple agents) report supports only the single-instance record attribute.

If LINE, AREA, or STACKED_AREA is specified in graph-type, instance and fields cannot both be specified at the same time. The following table shows the combinations of record attribute and field that can be specified for the report:

Table 2‒27: Combinations of record attribute and fields that can be specified for reports

Report type

Record attribute

Single field

Multiple fields

Historical (single agent) report

Single-instance

Y

Y

Multi-instance

Y

N

Historical (multiple agents) report

Single-instance

Y

N

Realtime (single agent) report

Single-instance

Y

Y

Multi-instance

Y

N

Legend:

Y: Can be specified.

N: Cannot be specified.

When display-key is specified, specifying LINE, AREA, or STACKED_AREA in graph-type results in an error.

The following table shows the filter setting conditions for fields of time_t type:

Table 2‒28: Filter setting conditions set in record

specify-when-displayed setting

Conditional expression right-hand term

Field of time_t type other than Date or Time fields

Date field in time_t type

Time field in time_t type

TRUE

Value

Y

Y

Y

Omitted

Y

Y

Y

FALSE

Value

N

N

Y

Omitted

N

N

N

Table 2‒29: Filter setting conditions set in ref-field

specify-when-displayed setting

Conditional expression right-hand term

Field of time_t type other than Date or Time fields

Date field in time_t type

Time field in time_t type

TRUE

Field ID

N

N

N

Value

N

N

Y

Omitted

Y

Y

Y

FALSE

Field ID

Y

Y

Y

Value

N

N

Y

Omitted

N

N

N

Legend:

Y: Can be specified.

N: Cannot be specified.

Delta values in a realtime report depend on the fields of each record that is collected by PFM - Agent or PFM - RM. For details about whether or not delta values are to be collected in the record fields, see the chapter in the PFM - Agent or PFM - RM manuals that describes the records (list of fields in each record).

The table below describes the display conditions for delta values in realtime reports and the values that are displayed. With some PFM - Agents or PFM - RM, the information provided in the table might not be applicable. For details, see the PFM - Agent or PFM - RM manuals.

Table 2‒30: Delta values in realtime reports and display conditions

indicate-delta-value attribute of realtime-indication-settings

Delta value for a field

Value that is displayed

TRUE

Yes

Amount of change from the previously collected performance data to the currently collected performance data

No

Newest collected value

FALSE

Yes

Accumulated value since the collection of performance data started

No

Newest collected value

Legend:

Yes: Delta value is collected.

No: Delta value is not collected.

The following table lists the fields that cannot be specified in realtime reports:

Table 2‒31: Fields that cannot be specified for realtime reports

Name in PFM - Web Console

Manager name

Description

Agent Host

DEVICEID

instance-name[host-name] or host name

Agent Instance

PROD_INST

Agent's instance name

Agent Type

PROD_ID

Agent's product ID (1-byte identifier)

Date

DATE

Record creation date (Greenwich Mean Time)

Date and Time

DATETIME

Combination of Date and Time

Drawer Type

DRAWER_TYPE

Summation type in PI database

GMT Offset

GMD_ADJUST

Difference between Greenwich Mean Time and local time (seconds)

Time

TIME

Record creation time (Greenwich Mean Time)

xxxx (Total)

xxxx_TOTAL

Total value obtained during data summing for PI records

xxxx_TOTAL_SEC(Total)

xxxx_TOTAL_SEC

Total value in the data summing period

xxxx_HI (Max)

xxxx_HI

Maximum value in the data summing period

xxxx_LO (Min)

xxxx_LO

Minimum value in the data summing period

xxxx_OV (OV)

xxxx_OV

Number of times overflow occurred in the calculation of total value during the data summing period

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

For drilldown reports, you can specify only report definitions that have already been created before you execute the command. An attempt to specify new report definitions for drilldown reports will fail with a KAVJK0125-E message.

When performing multiple monitoring, you cannot execute this command from the PFM - Web Console host that is connected to the secondary PFM - Manager host.

Return values

0

The command ended normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

Creation of the output file failed.

5

The parameters cannot be analyzed because they do not match the DTD file.

10

Creation of at least one report definition failed.

11

Authentication processing for logging into PFM - Manager failed.

12

An attempt was made to execute the command from the PFM - Web Console host that is connected to the secondary PFM - Manager host when multiple monitoring is performed.

100

The environment is invalid.

200

A memory error occurred.

202

A file access error occurred.

222

A communication processing error occurred.

255

An unexpected error occurred.

Usage example

This example registers a new parameter file (rdef_create.xml) that contains report definitions:

jpcrdef  create  rdef_create.xml

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

An example is shown below of the standard output when three report definitions were specified and one of them resulted in an error.

Example of standard output

jpcrdef create connected to vserv01 at 2006 03 20 15:00:55.282
create result OK  : report-definition-directory-path-1/report-definition-name-1
create result OK  : report-definition-directory-path-2/report-definition-name-2
create result ERR : report-definition-directory-path-3/report-definition-name-3
Cause of error
jpcrdef create disconnected at 2006 03 20 15:01:06.2

jpcrdef delete

Format

jpcrdef delete     [-y]
                   [-mx maximum-heap-size]
                   [-ms initial-heap-size]
                   input-file

Function

The jpcrdef delete command connects to PFM - Manager and deletes a report definition. When you specify a report definition directory, all the lower-level report definitions and the report definition directory itself are deleted. The command acquires the report definitions and report definition directory to be deleted from the XML-format parameter file specified as a command line argument. You can specify multiple report definitions and report definition directories in order to delete them in batch.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions or general user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-y

Specifies that no deletion confirmation message is to be displayed. When this option is omitted, a deletion confirmation message is displayed for each <report-definition>. When y or Y is entered as the response to the deletion confirmation message, the command deletes the report definition. When any other value is entered, the command does not deletes the report definition and displays a deletion confirmation message for the next <report-definition>.

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

input-file

Specifies the XML-format parameter file that is to be used to delete report definitions. This parameter file must be created according to the Parameter file format described below. You can specify the absolute file path name, relative file path name, or file name. When the name is not the absolute file path, the command assumes the current directory.

Parameter file format

XML tag specifications

report-definitions

Type

Description

Description

Root tag for report definition information

Specifiable value

None

Omissible

No

Attribute

None

Parent element

pr-cli-parameters

Child element

report-definition

report-definition

Type

Description

Description

Specifies a single report definition.

Specifiable value

None

Omissible

No

Attribute

name

Specify a report definition name with 1 to 64 double-byte and/or single-byte characters (rather than 1 to 64 bytes). If the report definition name contains \ or /, specify it as \\ or \/, respectively. If the name attribute is omitted, the command deletes the report definition directory specified in parent-folder and all its subdirectories. If spaces are specified before and/or after the report definition name, the name is registered without the leading and/or trailing spaces.

parent-folder

Specify the name of the directory that contains the report definition specified in the name attribute. The name that you specify is a slash (/) separated path from the root directory. The path can have 1 to 64 double-byte and/or single-byte characters (rather than 1 to 64 bytes). If the name attribute is omitted, the command deletes the report definition directory including its subdirectories. For a path, specify directories sequentially separated by / starting from the highest-level directory. If the directory name contains \ or /, specify it as \\ or \/, respectively. An error results if spaces are specified before and/or after the directory name. If this attribute is omitted, an error results.

For example, to output the report definition named PD define located under the User Reports root directory, specify as follows: <report-definition name="PD define" parent-folder="/"/>

The following example outputs to a file, all report definitions located in the Dir1 and Dir2 directories under the User Reports root directory:

<report-definition parent-folder="/Dir1/Dir2"/>

id

Ignored, if specified.

read-only

Specify TRUE to cancel deletion of the report definition and to process the next report definition. When you specify FALSE or you omit this attribute, the command deletes the report definition.

Parent element

report-definitions

Child element

product

Ignored, if specified.

report-type

record

indication-settings

view-type

drilldown

An example of a parameter file is shown below.

Example of parameter file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rdef_delete_params.dtd">
<pr-cli-parameters ver="0100">
  <report-definitions>
   <report-definition name="Workload Status (Multi-Agent)"
             parent-folder="/"/>
   <report-definition name="daily report"
             parent-folder="/UserReport"
                 read-only="FALSE"/>
   <report-definition name="" parent-folder="/report1"/>
  </report-definitions>
</pr-cli-parameters>

Notes

The command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication.

The monitoring template report definitions and report definition directory cannot be deleted.

If a report definition directory or report definition specified as a deletion target does not exist, the command returns a value indicating successful deletion without returning an error.

When a report definition directory is specified as a deletion target, and deletion of one of the definitions in its subdirectories or deletion of one of the subdirectories fails, the command cancels processing of that report definition directory and processes the next report definition or report definition directory specified in the parameter file.

If multiple report definitions or report definition directories are specified as deletion targets and deletion of one of the definitions or directories results in an exception, the command cancels that processing and processes the next report definition or report definition directory specified in the parameter file.

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

When performing multiple monitoring, you cannot execute this command from the PFM - Web Console host that is connected to the secondary PFM - Manager host.

Return values

0

The command ended normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

Creation of the output file failed.

5

The parameters cannot be analyzed because they do not match the DTD file.

10

Creation of at least one report definition failed.

11

Authentication processing for logging into PFM - Manager failed.

12

An attempt was made to execute the command from the PFM - Web Console host that is connected to the secondary PFM - Manager host when multiple monitoring is performed.

100

The environment is invalid.

200

A memory error occurred.

202

A file access error occurred.

222

A communication processing error occurred.

255

An unexpected error occurred.

Usage example 1

This example deletes the report definitions specified in the parameter file rdef_del.xml:

jpcrdef  delete  -y  rdef_del.xml

Usage example 2

This example deletes each report definition specified in the parameter file rdef_del02.xml after displaying a deletion confirmation message:

jpcrdef  delete  rdef_del02.xml

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

An example is shown below of the standard output format when ten report definitions and five report definition directories were specified and three report definitions resulted in an error.

Example of standard output

jpcrdef delete connected to vserv01 at 2006 03 20 15:00:55.282
delete result OK  : report-definition-directory-path-1/report-definition-name-11
delete result OK  : report-definition-directory-path-2/report-definition-name-21
delete result ERR : report-definition-directory-path-3
           Skipped : report-definition-directory-path-3/report-definition-name-31
Cause of error
              OK  : report-definition-directory-path-3/report-definition-name-32
          Skipped : report-definition-directory-path-3/report-definition-name-33
Cause of error
              OK  : report-definition-directory-path-3/report-definition-name-34
              OK  : report-definition-directory-path-3/report-definition-name-35
delete result ERR : report-definition-directory-path-4/report-definition-name-41
Cause of error
delete result OK  : report-definition-directory-path-5
              OK  : report-definition-directory-path-5/report-definition-name-51
              OK  : report-definition-directory-path-5/report-definition-name-52
jpcrdef delete disconnected at 2006 03 20 15:01:06.2

In this example, report-definition-directory-path-3/report-definition-name-31 and report-definition-directory-path-3/report-definition-name-33 in report-definition-directory-path-3 and report-definition-directory-path-4/report-definition-name-41 were not deleted (they still remain).

jpcrdef output

Format

jpcrdef output     -o output-file
                   [-mx maximum-heap-size]
                   [-ms initial-heap-size]
                   [-dateformat date-format-pattern-name]
                   [-dateseparator date-format-separator-name]
                   input-file

Function

The jpcrdef output command connects to PFM - Manager and outputs the specified report definition to a file in XML format. When you specify a directory, all the report definitions in the directory, including the report definitions in subdirectories, are output to one file. You can specify multiple paths or directories. You can use the output file as the input to the jpcrdef create command.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions or general user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-o output-file

Specifies the output target file. When this option is omitted, an error results. You can specify the absolute file path name, relative file path name, or file name. When the name is not the absolute file path, the command assumes the current directory. If the specified file already exists, the command overwrites the existing file. If the specified directory does not exist, an error results.

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-dateformat date-format-pattern-name

Specifies the name of the date format pattern that is used to identify the format of dates specified in the <expression> tag in the output file. The following date format pattern names can be specified:

pattern-ddMMyyyy

pattern-MMddyyyy

pattern-yyyyMMdd

-dateseparator date-format-separator-name

Specifies the character string that is used to identify the format of separators specified in the <expression> tag in the output file. The following date format separator names can be specified:

space

slash

hyphen

period

input-file

Specifies the XML-format parameter file that specifies the report definitions that are to be output. This parameter file must be created according to the Parameter file format described below. You can specify the absolute file path name, relative file path name, or file name. When the name is not the absolute file path, the command assumes the current directory.

Parameter file format

XML tag specifications

report-definitions

Type

Description

Description

Root tag for report definition information

Specifiable value

None

Omissible

No

Attribute

None

Parent element

pr-cli-parameters

Child element

report-definition

report-definition

Type

Description

Description

Specifies a single report definition.

Specifiable value

None

Omissible

No

Attribute

name

Specify a report definition name with 1 to 64 double-byte and/or single-byte characters (rather than 1 to 64 bytes). If the report definition name contains \ or /, specify it as \\ or \/, respectively. If the name attribute is omitted, the command outputs to a single file the report definition directory specified in parent-folder and all its subdirectories. If spaces are specified before and/or after the report definition name, the name is registered without the leading and/or trailing spaces.

parent-folder

Specify the name of the directory that contains the report definition specified in the name attribute. The name that you specify is a slash (/) separated path from the root directory. The path can have 1 to 64 double-byte and/or single-byte characters (rather than 1 to 64 bytes). If the parent-folder attribute is specified and the name attribute is omitted, the command outputs to a single file all report definitions contained in the report definition directory and its subdirectories. For a path, specify the directories sequentially separated by / starting from the highest-level directory. If the directory name contains \ or /, specify it as \\ or \/, respectively. An error results if spaces are specified before and/or after the directory name. This attribute cannot be omitted.

For example, to output the report definition named PD define located under the User Reports root directory, specify as follows:

<report-definition name="PD define" parent-folder="/"/>

The following example outputs to a file, all report definitions located in the Dir1 and Dir2 directories under the User Reports root directory:

<report-definition parent-folder="/Dir1/Dir2"/>

id

Outputs the identifier of the report definition (or directory for directory output). In the input file, this attribute is ignored if specified.

read-only

Outputs true for system definition and false for other than system definition. In the input file, this attribute is ignored if specified.

Parent element

report-definitions

Child element

product

Ignored, if specified.

report-type

record

indication-settings

view-type

drilldown

An example of a parameter file is shown below.

Example of parameter file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rdef_output_params.dtd">
<pr-cli-parameters ver="0100">
   <report-definitions>
      <report-definition name="Workload Status (Multi-Agent)"
                parent-folder="/"/>
      <report-definition name="CPU Usage Top 10 Processes"
                parent-folder="/" read-only="FALSE"/>
      <report-definition parent-folder="/Windows/Operating System"/>
   </report-definitions>
</pr-cli-parameters>

Notes

The command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication.

If the output target is a report definition directory and an exception occurs while one of the report definitions in a subdirectory is being output, the command skips that report definition and processes the next report definition.

If multiple report definitions or report definition directories are specified as output targets and an exception occurs while one of the report definitions is being output, the command cancels that processing and outputs the next definition.

Normally, you do not need to set the -mx or -ms option. If the KAVJK0401-E message, which reports insufficient memory, is output during command execution, re-execute the command with the -mx option to increase the maximum heap size. At this time, make sure that you specify 64 or a greater value for the -mx option.

Return values

0

The command ended normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

Creation of the output file failed.

5

The parameters cannot be analyzed because they do not match the DTD file.

10

Creation of at least one report definition failed.

11

Authentication processing for logging into PFM - Manager failed.

100

The environment is invalid.

200

A memory error occurred.

202

A file access error occurred.

222

A communication processing error occurred.

255

An unexpected error occurred.

Usage example

This example outputs to the rdef_output.xml file the parameter file rdef_input.xml that contains report definitions:

jpcrdef  output  -o rdef_output.xml  rdef_input.xml

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

An example is shown below of the standard output format when ten report definitions and five report definition directories were specified and three report definitions resulted in an error.

Example of standard output

jpcrdef output connected to vserv01 at 2006 03 20 15:00:55.282
output result OK  : report-definition-directory-path-1/report-definition-name-11
output result OK  : report-definition-directory-path-2/report-definition-name-21
output result ERR : report-definition-directory-path-3
          Skipped : report-definition-directory-path-3/report-definition-name-31
cause-of-error
              OK  : report-definition-directory-path-3/report-definition-name-32
          Skipped : report-definition-directory-path-3/report-definition-name-33
cause-of-error
              OK  : report-definition-directory-path-3/report-definition-name-34
              OK  : report-definition-directory-path-3/report-definition-name-35
output result ERR : report-definition-directory-path-4/report-definition-name-41
cause-of-error
output result OK  : report-definition-directory-path-5
              OK  : report-definition-directory-path-5/report-definition-name-51
              OK  : report-definition-directory-path-5/report-definition-name-52
jpcrdef output disconnected at 2006 03 20 15:01:06.2

Output file format

The specified attributes and the attributes set as the default settings are output to the file. The output command outputs a node ID as the id attribute of the report-definition tag. The create and delete commands ignore the id attribute specification.

You can use the output parameter file as the input file when you create report definitions. The output DTD file that defines the parameter descriptions is the same as the DTD file specified during creation. For examples of a parameter file that is output and a DTD file that defines parameter descriptions, see Example of parameter file (for historical report), and Example of parameter file (for realtime report) in the description of the jpcrdef create command.

jpcrpt

Format

jpcrpt   -o output-file-name
         [ -mx maximum-heap-size]
         [ -ms initial-heap-size]
         [ -y ]
         [ -rc refresh-count]
         [ -ri refresh-interval]
         [ -dateformat date-format-pattern-name]
         [ -dateseparator date-format-separator-name]
         [ -exportseparator
         date-format-separator-name-during-report-output]
         [-agent service-ID [,service-ID]...]
         input-file-name

Function

The jpcrpt command outputs a report to a file in CSV format or HTML format. The command acquires the output definition from the XML-format parameter file specified as a command line argument. In the parameter file, you can specify the report output format, the report to be output, and the items equivalent to the items on the Show Options page in the View Report window or a combination report window. When reports are output in HTML format, the html-output tag needs to be set in the input file.

Note that the types of reports you can output by using the jpcrpt command differ depending on the version of PFM - Web Console. The following table lists which version of PFM - Web Console can output which types of reports.

Table 2‒32: Types of reports that can be output for each version of PFM - Web Console

Item to be output

08-00

08-11 or later

Report

CSV format

Yes

Yes

HTML format

No

Yes

Registered report

CSV format

No

Yes

HTML format

No

Yes

Combination report

HTML format

No

Yes

Legend: Yes: Can be output. No: Cannot be output.

You can specify one report in one parameter file. When the report to be output is a realtime report and you want to output it in CSV format, data is added at the end of the output file for the number of updates specified in the rc option at the update interval specified in the ri option. When you want to output a report in HTML format, an HTML file is output with the latest data available at the time that the command is executed. After the HTML file is output, data is not updated. When you specify output of a report in HTML format, the rc option and the ri option are ignored if specified.

If you specify multiple agents for a single-agent report, an error occurs.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To execute this command, a key file for authentication needs to be created in advance for a user account with administrator user permissions or general user permissions# for Performance Management. For details, see the jpcmkkey command.

#

Execution permissions for Performance Management that are required for a Performance Management user or JP1 user.

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-o output-file-name

Specifies the name of the file to which the report is to be output. If you do not specify an output file name, an error occurs. Do not specify the following characters in the output file name:

# % < > & \

For output-file-name, you can specify the full file path name, a relative file path name, or a file name. For path names other than the full file path name, the current directory is the base. If the specified directory does not exist, an error occurs. If the same file is specified more than once, the system follows the specification of the -y option.

The report output format (CSV or HTML) is specified in the parameter file (XML file) specified as a command line argument. If CSV is specified, a single CSV file will be generated without a file name extension. If HTML is specified, a PNG-format graph image file might be generated in addition to an HTML file. For files generated when HTML is specified, file name extensions are added. When you specify HTML format, be careful that the name of the generated HTML file differs from the output file name that you specify as an argument. The following table describes the differences in the names of generated files between CSV and HTML.

Output format

Specified file name

Output file name

CSV

Output

output

output.csv

output.csv

HTML

output

output.htm

output.png

output.htm

output.htm.htm

output.htm.png

When you output a report in HTML format, if you specify a path containing the following characters for the output file path, the KAVJK0210-E message is displayed and command execution is canceled:

# % < > & \ "

-mx maximum-heap-size

Specifies the maximum heap size for java.exe (in megabytes). The default is 64 MB. The maximum size that can actually be acquired depends on the system. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-ms initial-heap-size

Specifies the initial heap size for java.exe (in megabytes). The default is 32 MB. If the specified value does not satisfy the following conditions, an invalid command line format results:

Integer in the range 1 to 1,024

Value specified in -mx >= value specified in -ms

-y

Specifies that no confirmation message is to be displayed if the output file specified in the -o option already exists.

When the -y option is specified, the command overwrites the existing file without displaying the overwrite configuration message. When this option is omitted, the command displays an overwrite confirmation message. When y or Y is entered as the response to the deletion confirmation message, the command overwrites the existing file. When any other value is entered, the command cancels the processing.

-rc refresh-count

This option is applied to realtime reports. Specify the number of times that the reports are to be updated. You can specify a number from 1 to 2,147,483,647. If you omit this option, 1 is assumed. If you specify a number outside the range, an error occurs. If you specify this option for historical reports or HTML output, the option is ignored.

-ri refresh-interval

This option is applied to realtime reports. Specify the update interval for the reports. You can specify a number in the range from the minimum update interval specified when the report is specified to 3,600 seconds. If you omit this option, the initial update interval specified when the report is defined is assumed. If you specify a number outside the range, an error occurs. When the report display mode for realtime reports is set to the re-schedule mode, if you specify this option for historical reports or HTML output, the option is ignored.

-dateformat date-format-pattern-name

Specifies the name of the date format pattern that is used to identify the format of dates specified in the <expression-value>, <start-time>, <end-time>, and <baseline-start-time> tags in the input file. The specified date format pattern is also used to determine the date format in the output file. The following date format pattern names can be specified:

pattern-ddMMyyyy

pattern-MMddyyyy

pattern-yyyyMMdd

-dateseparator date-format-separator-name

Specifies the character string that is used to identify the format of date separators specified in the <expression-value>, <start-time>, <end-time>, and <baseline-start-time> tags in the input file. The following date format separator names can be specified:

space

slash

hyphen

period

-exportseparator date-format-separator-name-during-report-output

Specifies the separator string used for the date format separator name in the output file. The following date format separator names can be specified:

space

slash

hyphen

period

-agent service-ID

Specifies the report output target agent, using the service ID of the Agent Collector service, remote agent, or group agent. An error will occur if the service ID of the Remote Monitor Collector service is specified. When the report definition report type is Historical (multiple agents), and multiple service IDs are specified, they can be separated with commas. In this case, processing is performed in the order starting from the service ID on the left. If duplicate service IDs are specified, the first one takes effect.

If this option is specified, any <agent> tag specified in the parameter file is ignored.

An error will occur if a non-existent service ID or service ID different from the report definition and product is specified. An error will occur if the report definition report type is not Historical (multiple agents), and multiple service IDs are specified. Note that this is ignored if specified for registration reports or combination reports.

input-file-name

Specifies the name of the input file that contains the definitions for displaying the report. The input file must be an XML-format parameter file created according to the Parameter file format described below. The input file name can be the absolute path or relative path. If the specified input file name is not the absolute path, the command assumes the current directory.

Parameter file format

XML tag specifications

The examples in this subsection show how to write the parameter file. Parameter file samples are stored in the following directories. Use the samples as templates for writing parameter files.

In Windows:

installation-directory\sample\conf\

In UNIX:

/opt/jp1pcwebcon/sample/conf/

Parameter file example (for outputting reports other than registered reports and combination reports)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0210">
  <launch-report>
    <agent>TA1htmprsvr</agent>
    <agent>TA1admin</agent>
    <report-definition name="CPU Trend" parent-folder="/Windows/Operating System/Monthly Trend">
      <launch-options>
        <indication-settings maximum-number-of-records="1440">
          <report-interval>HOUR</report-interval>
          <start-time>2007 08 10 12:00</start-time>
          <end-time>2007 08 11 12:00</end-time>
        </indication-settings>
      </launch-options>
      <html-output>
        <show-graph>
          <graph-options zoom-scale = "100">
            <show-3d/>
            <show-grid/>
            <vertical-axis minvalue="0" maxvalue="100"/>
          </graph-options>
        </show-graph>
        <show-table/>
      </html-output>
    </report-definition>
  </launch-report>
</pr-cli-parameters>

Parameter file example (for outputting registered reports)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0210">
  <launch-registration-report>
    <registration-report-definition report-name="CPU Usage@TA1host01"
      bookmark-name="CPU Usage"
      bookmark-parent-folder="/">
      <launch-options>
        <indication-settings maximum-number-of-records="1440">
          <date-range>WITHIN_THE_PAST_24_HOURS</date-range>
          <report-interval>HOUR</report-interval>
        </indication-settings>
      </launch-options>
      <html-output>
        <show-graph>
          <graph-options zoom-scale = "100">
            <show-grid/>
            <vertical-axis minvalue="0" maxvalue="100"/>
          </graph-options>
        </show-graph>
      <show-table/>
      </html-output>
    </registration-report-definition>
  </launch-registration-report>
</pr-cli-parameters>

Parameter file example (for outputting combination reports)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0210">
  <launch-combination-bookmark>
    <combination-definition bookmark-name="CPU Usage with Baseline" bookmark-parent-folder="/">
      <combination-options><combination-indication-settings>
        <date-range>WITHIN_THE_PAST_24_HOURS</date-range>
        <report-interval>HOUR</report-interval>
      </combination-indication-settings>
     </combination-options>
     <combination-graph-options zoom-scale="100" />
   </combination-definition>
  </launch-combination-bookmark>
</pr-cli-parameters>

launch-report

Type

Description

Description

Specifies the combination of report definitions and agents for output of a report.

Specifiable value

None

Omissible

Yes (launch-report, launch-registration-report, or launch-combination-bookmark must be specified)

Attribute

None

Parent element

pr-cli-parameters

Child element

agent (the element can be specified more than once)

report-definition

agent

Type

Description

Description

Specifies a target agent for report output.

Specifiable value

Specifies the agent's Agent Collector service, or the service ID of a remote agent or a group agent. Note, however, that specifying one of the following service IDs results in an error:

Service ID of the Remote Monitor Collector service

Nonexistent service ID

Service ID that is assigned to multiple products

Service ID of an agent that the user who executes the command is not authorized to view

If duplicate service IDs are specified, the service ID specified first takes effect. An error will occur when the report type specified for report-definition is not multi-agent, and multiple service IDs are specified.

When this command is executed with the -agent option specified for PFM - Web Console 09-00 or later, the value specified for this tag is ignored. Likewise, if this tag is omitted, the -agent option needs to be specified during command execution.

Omissible

No

Attribute

None

Parent element

launch-report

Child element

None

report-definition

Type

Description

Description

Specifies a single report definition for report output.

An error results in the following cases:

The product of the specified agent differs from the product of the specified report definition.

The data model version of the specified agent is not the same as or is newer than the data model version of the report definition.

Specifiable value

None

Omissible

No

Attribute

name

Specify the name of a report definition to be output to a file, with 1 to 64 double-byte and/or single-byte characters (rather than 1 to 64 bytes). If the report definition name contains \ or /, specify it as \\ or \/, respectively.

Specifying a nonexistent report name results in an error. If this attribute is omitted, an error results.

parent-folder

Specify the directory path of the parent directory that contains the report definition specified in the name attribute. The directory path begins with /, followed by directory names arranged sequentially and separated by / starting from the highest-level directory. To specify the root directory, specify only /. If the directory name contains \ or /, specify it as \\ or \/, respectively. Specifying a nonexistent directory results in an error. If this attribute is omitted, an error results. An error also results if the specified directory path name ends in \ or /.

Parent element

launch-report

Child element

launch-options (can be specified only once per report-definition or can be omitted)

html-output (can be specified only once per report-definition or can be omitted)

launch-options

Type

Description

Description

Specifies report acquisition conditions.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the parameter is not set)

Attribute

None

Parent element

report-definition, registration-report-definition

Child element

indication-settings (can be specified only once per launch-options or can be omitted)

realtime-indication-settings (can be specified only once per launch-options or can be omitted)

expression-values (can be specified only once per launch-options or can be omitted)

indication-settings

Type

Description

Description

Specifies the following values:

Report acquisition interval

Report interval

Start date and time

End date and time

Peak time

Maximum number of records

An error results if this parameter is specified when the report type is Realtime (Single Agent) in the record definition.

Specifiable value

None

Omissible

Yes (including the child elements, the values in the report definitions are used)

Attribute

maximum-number-of-records

Specify the maximum number of records to be acquired for the report, with an integer in the range 1 to 2,147,483,647. The permitted maximum is the value specified in maxFetchCount in the <command> tag in config.xml. If the specified value is greater than the maximum, the command uses the value of maxFetchCount. If the value of maxFetchCount in the <command> tag in config.xml is smaller than the value specified in the report definition, the command use the value of maxFetchCount.

If this attribute is omitted, value in the report definition is used.

Parent element

launch-options

Child element

date-range (can be specified only once per indication-settings or can be omitted)

start-time (can be specified only once per indication-settings or can be omitted)

end-time (can be specified only once per indication-settings or can be omitted)

report-interval (can be specified only once per indication-settings or can be omitted)

peak-time (can be specified only once per indication-settings or can be omitted)

exclude-terminal-data (can be specified only once per indication-settings or can be omitted)

date-range

Type

Description

Description

Specifies the report acquisition period.

Specifiable value

Specify one of the following values (which are not case sensitive):

For the past hour : WITHIN_THE_PAST_HOUR

For the past day (24 hours): WITHIN_THE_PAST_24_HOURS

For the past 7 days: WITHIN_THE_PAST_7_DAYS

For the past month: WITHIN_THE_PAST_MONTH

For the past year: WITHIN_THE_PAST_YEAR

For specifying the value when the report is displayed: SPECIFY_WHEN_DISPLAYED

Omissible

Yes (value in the report definition is used)

Attribute

None

Parent element

indication-settings, combination-indication-settings

Child element

None

report-interval

Type

Description

Description

Specifies the report interval.

Specifiable value

Specify one of the following values (which are not case sensitive):

For minutely: MINUTE

For hourly: HOUR

For daily (every 24 hours): DAY

For weekly: WEEK

For monthly: MONTH

For yearly: YEAR

If you specify this parameter when you output a report or a registered report, and the records in the report definition are not PI records, an error occurs. If you specify this parameter for a combination report, no error occurs and only the PI records of the records to be output reference this value. When peak time is set in the report definition, peak time is invalidated for any value you specify other than HOUR.

Omissible

Yes (value in the report definition is used)

Attribute

None

Parent element

indication-settings, combination-indication-settings

Child element

None

start-time

Type

Description

Description

Specifies the start date and time.

There are two ways to specify this: directly as an absolute time, and relatively using the child element <relative-time> tag.

Specifiable value

Specify the value in the format specified in report-interval. For reports for which report-interval cannot be specified, specify the start date and time in the format that is applied when MINUTE is specified for report-interval.

Example 1

If you specify pattern-yyyyMMdd for the -dateformat argument, space for the -dateseparator argument, and MINUTE for report-interval, specify start-time in YYYYMMDDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 2

If you specify pattern-yyyyMMdd for the -dateformat argument, slash for the -dateseparator argument, and MINUTE for report-interval, specify start-time in YYYY/MM/DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 3

If you specify pattern-yyyyMMdd for the -dateformat argument, hyphen for the -dateseparator argument, and MINUTE for report-interval, specify start-time in YYYY-MM-DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 4

If you specify pattern-yyyyMMdd for the -dateformat argument, period for the -dateseparator argument, and MINUTE for report-interval, specify start-time in YYYY.MM.DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

An error occurs in the following cases:

The specified value is invalid.

The format is invalid.

The specified value is greater than end-time.

The specified year is before 1970 or after 2036.

Omissible

Depends on the combination of the date-range and end-time values. For details, see Notes.

Attribute

None

Parent element

indication-settings, combination-indication-settings

Child element

relative-time (this can only be specified once per start-time, and can be omitted.)

Legend:

: A space

end-time

Type

Description

Description

Specifies the end date and time.

There are two ways to specify this: directly as an absolute time, and relatively using the child element <relative-time> tag.

Specifiable value

Specify the value in the format specified in report-interval. For reports for which report-interval cannot be specified, specify the end date and time in the format that is applied when MINUTE is specified for report-interval.

Example 1

If you specify pattern-yyyyMMdd for the -dateformat argument, space for the -dateseparator argument, and MINUTE for report-interval, specify end-time in YYYYMMDDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 2

If you specify pattern-yyyyMMdd for the -dateformat argument, slash for the -dateseparator argument, and MINUTE for report-interval, specify end-time in YYYY/MM/DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 3

If you specify pattern-yyyyMMdd for the -dateformat argument, hyphen for the -dateseparator argument, and MINUTE for report-interval, specify end-time in YYYY-MM-DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 4

If you specify pattern-yyyyMMdd for the -dateformat argument, period for the -dateseparator argument, and MINUTE for report-interval, specify end-time in YYYY.MM.DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

An error occurs in the following cases:

The specified value is invalid.

The format is invalid.

The specified value is smaller than start-time.

The specified year falls before 1970 or after 2036.

Omissible

Depends on the combination of the date-range and start-time values. For details, see Notes.

Attribute

None

Parent element

indication-settings, combination-indication-settings

Child element

relative-time (this can only be specified once per end-time, and can be omitted.)

Legend:

: A space

peak-time

Type

Description

Description

Specifies the peak time.

Specifiable value

Specify the field ID of the field whose peak time value is to be used. If you specify NONE, the field ID specified in the report definition is ignored.

If this parameter is specified when the report definition satisfies any of the following conditions, an error results:

The specified record is not a PI record.

A multi-instance record is specified.

report-interval is not set to HOUR.

Omissible

Yes (value in the report definition is used)

Attribute

None

Parent element

indication-settings

Child element

None

exclude-terminal-data

Type

Description

Description

Specifies whether to exclude the report start and end times in the report to be output.

Specifiable value

One of the values listed below can be specified. Uppercase and lowercase characters are not distinguished.

STARTTIME: The start time is not included in the report.

ENDTIME: The end time is not included in the report.

BOTHTIME: Both the start and end times are excluded from the report.

NONE: Both the start and end times are included in the report.

Omissible

Yes (If this element is omitted, the value of excludeTerminalData under the <command> tag in the config.xml initialization file is used. For details about the config.xml file, see E. Initialization File (config.xml).)

Attribute

None

Parent element

indication-settings, combination-indication-settings

Child element

None

realtime-indication-settings

Type

Description

Description

Specifies display by ranking for a realtime report.

This parameter can be specified when the report type is Realtime (Single Agent) in the record definition. For any other report type, specifying this parameter results in an error.

Specifiable value

None

Omissible

Yes (the value in the report definition is used, including for child elements)

Attribute

indicate-delta-value

Specify TRUE to collect delta values; otherwise, specify FALSE. If this attribute is omitted, the value in the report definition is used.

Parent element

launch-options

Child element

display-by-ranking (can be specified only once per realtime-indication-settings or can be omitted)

display-by-ranking

Type

Description

Description

Specifies the target field for ranking, the number of items to be obtained, and whether the order is descending or ascending.

If this parameter is specified for a report definition for single-instance records, an error results.

Specifiable value

None

Omissible

Values in the report definition

Attribute

field

Specify the field ID to be used as the basis for ranking.

If ranking is not applicable, specify NONE (which is not case sensitive). If this attribute is omitted, an error results.

display-number

Specify the number of items to be obtained for ranking with an integer from 1 to 100. If the specified value is outside this range, an error results. If the field attribute is NONE, specifying display-number results in an error.

If the field attribute is specified and the display-number attribute is omitted in this parameter, and the field attribute is specified in the report definition, the value in the report definition takes effect; if the field attribute is omitted in the report definition, 10 is assumed.

in-descending-order

The field used as the basis for display by ranking can be sorted in ascending or descending order and then as many items as specified in the display-number attribute can be displayed from the beginning.

Specify TRUE to sort the field in ascending order and FALSE to sort in descending order.

If the field attribute is NONE, specifying in-descending-order results in an error.

If the field attribute is specified and the in-descending-order attribute is omitted in this parameter, and the field attribute is specified in the report definition, the value in the report definition takes effect; if the field attribute is omitted in the report definition, NONE is assumed. If the field attribute is omitted, FALSE is assumed.

Parent element

realtime-indication-settings

Child element

None

expression-values

Type

Description

Description

Specifies one or more conditional expressions.

If this parameter is specified for a report that does not contain the conditional expression set in Specify when displayed, an error results.

Specifiable value

None

Omissible

Yes (when the parameter is omitted, the parameter is not set)

Attribute

None

Parent element

launch-options

Child element

expression-value (this element can be specified more than once)

expression-value

Type

Description

Description

Specifies a conditional expression value.

Specifiable value

Specify a value for the expression on the line specified by the pos attribute.

You can specify an integer, a decimal value, or a character string of up to 2,048 bytes.

Omissible

Yes (if expression-values is specified, the parameter cannot be omitted)

Attribute

pos

Specify the order in which the simple expression for which Specify when displayed has been set in the conditional expression appears as an integer beginning at 0. The order of appearance matches the display order in the conditional expression displayed in the Report Display Settings window. The value of pos for the conditional expression displayed first in the Report Display Settings window is 0, and the value of pos for the conditional expression displayed third in the Report Display Settings window is 2.

The permitted value range is from 0 to the number of simple expressions for which Specify when displayed has been set -1.

If pos is omitted in the first expression-value tag, the value of this attribute is 0. If it is omitted in any other expression-value tag, the value of this attribute is the value of the previous pos + 1.

The same value can be specified more than once in pos. In this case, the last value specified takes effect.

If the specified value is outside the permitted range, an error results.

Parent element

expression-values

Child element

relative-time (this can only be specified once per expression-value, and can be omitted.)

html-output

Type

Description

Description

Outputs reports in HTML format. For details on the display format of output reports, see Output files.

When outputting reports in HTML format, one of the following display formats is available by specifying it as a child element:

Graph display

Table display

If a child element is omitted, only the report definition name of the header part is displayed.

Specifiable value

None

Omissible

If this tag is omitted, reports are output in CSV format.

Attribute

None

Parent element

report-definition, registration-report-definition

Child element #

show-graph (can be specified only once per html-output or can be omitted)

show-table (can be specified only once per html-output or can be omitted)

# If you specify child elements, specify them in the order listed above.

show-graph

Type

Description

Description

Displays graphs in the report to be output. To display graphs, set graph display in the report definition and specify this tag. No error occurs if the report definition is invalid or the tag is invalid. However, no graph is displayed in the report. Use the child element to specify the graph options in the report. If you do not specify a child element, graphs are displayed with the default settings.

Specifiable value

None

Omissible

If this tag is omitted, no graph is displayed in the report.

Attribute

None

Parent element

html-output

Child element

graph-options (can be specified only once per show-graph or can be omitted)

graph-options

Type

Description

Description

Changes the settings of the graph options. Depending on the specified child element, you can change the settings of the following items:

Display in 3D

Display of grids

Manual setting of the maximum and minimum values of the vertical axis

Specifiable value

None

Omissible

If this tag is omitted, 3D display is disabled, grids are not displayed, and the maximum and minimum values of the vertical axis are automatically set.

Attribute

zoom-scale

Specify the magnification of graphs. You can select 100, 200, 400, 600, or 800. If you omit this attribute, 100 is assumed. If you specify an invalid value, an error occurs.

Parent element

show-graph

Child element #

show-3d (can be specified only once per graph-options or can be omitted)

show-grid (can be specified only once per graph-options or can be omitted)

vertical-axis (can be specified only once per graph-options or can be omitted)

# If you specify child elements, specify them in the order listed above.

show-3d

Type

Description

Description

Displays graphs in 3D. However, an error results if the graph type is line or area graph. Stacked area graphs are displayed in 2D.

Specifiable value

None

Omissible

If this tag is omitted, graphs are displayed in 2D.

Attribute

None

Parent element

graph-options

Child element

None

show-grid

Type

Description

Description

Displays grids in graphs. However, an error results if the graph type is pie graph.

Specifiable value

None

Omissible

If this tag is omitted, grids are not displayed.

Attribute

None

Parent element

graph-options

Child element

None

vertical-axis

Type

Description

Description

Specifies the range of the vertical axis in a graph displayed in a report. However, an error results if the graph type is pie graph.

Specifiable value

None

Omissible

If this tag is omitted, the range of the vertical axis is automatically set based on the data in the graph.

Attribute

minvalue

Use a real number to specify the minimum value for the vertical axis. You can specify a value from -1.797E308 to 1.797E308. If you omit this attribute or minvalue is greater than maxvalue, an error occurs.

maxvalue

Use a real number to specify the maximum value for the vertical axis. You can specify a value from -1.797E308 to 1.797E308. If you omit this attribute or minvalue is greater than maxvalue, an error occurs.

Parent element

graph-options

Child element

None

show-table

Type

Description

Description

Displays tables in the report to be output. To display tables, set table display in the report definition and specify this tag. No error occurs if the report definition is invalid or this tag is invalid. However, no table is displayed in the report.

Specifiable value

None

Omissible

If this tag is omitted, no table is displayed in the report.

Attribute

None

Parent element

html-output

Child element

None

launch-registration-report

Type

Description

Description

Specifies a registered report under a bookmark (including combination bookmarks) in the bookmarks tree.

Specifiable value

None

Omissible

Yes (launch-report, launch-registration-report, or launch-combination-bookmark must be specified)

Attribute

None

Parent element

pr-cli-parameters

Child element

registration-report-definition

registration-report-definition

Type

Description

Description

Specifies one registered report to be output.

Specifiable value

None

Omissible

Yes (cannot be omitted when launch-registration-report is specified)

Attribute

bookmark-name

Specify the name of the bookmark (including a combination bookmark) storing the registered report to be output to a file. If the bookmark name contains \ or /, specify it as \\ or \/, respectively. If you specify a nonexistent bookmark, or if you omit this attribute, an error occurs.

report-name

Specify the name of the registered report to be output to a file. To include \ or / in the report name, specify it as \\or \/, respectively. If you specify a registered report that does not exist in the bookmark specified in the bookmark-name attribute or if you omit this attribute, an error occurs.

Note: If multiple registered reports that have the same name are defined under the same bookmark, the command outputs the first registered report encountered in the output definition that the command acquires from the parameter file.

bookmark-parent-folder

Use a directory path to specify the parent directory of the bookmark specified in the bookmark-name attribute. The directory path must begin with / and the directory names must be delimited by using /. If you want to specify the root directory, specify / only. If the directory name contains \ or /, specify it as \\ or \/, respectively. If you specify a nonexistent directory or if you omit this attribute, an error occurs. An error also occurs if you write \ or / at the end of the directory path name.

Parent element

launch-registration-report

Child element #

launch-options (can be specified only once per registration-report-definition or can be omitted)

html-output (this can only be specified once per registration-report-definition, and can be omitted.)

# If you specify child elements, specify them in the order listed above.

launch-combination-bookmark

Type

Description

Description

Specifies a combination bookmark in the bookmarks tree.

Specifiable value

None

Omissible

Yes (launch-report, launch-registration-report, or launch-combination-bookmark must be specified)

Attribute

None

Parent element

pr-cli-parameters

Child element

combination-definition

combination-definition

Type

Description

Description

Specifies one combination bookmark that is to be output as a report.

Specifiable value

None

Omissible

Yes (cannot be omitted when launch-combination-bookmark is specified)

Attribute

bookmark-name

Specify the name of the combination bookmark whose registered report is to be output to a file. When the bookmark name contains \ or /, specify it as \\ or \/, respectively. If you specify an nonexistent bookmark or a bookmark that is not a combination bookmark or if you omit this attribute, an error occurs.

bookmark-parent-folder

Use a directory path to specify the parent directory of the bookmark specified in the bookmark-name attribute. The directory path must begin with / and the directory names must be delimited by using /. If you want to specify the root directory, specify / only. If the directory name contains \ or /, specify it as \\ or \/, respectively. If you specify a nonexistent directory or if you omit this attribute, an error occurs. An error also occurs if you write \ or / at the end of the directory path name.

Parent element

launch-combination-bookmark

Child element #

combination-options (can be specified only once per combination-definition or can be omitted)

combination-graph-options (can be specified only once per combination-definition or can be omitted)

# If you specify child elements, specify them in the order listed above.

combination-graph-options

Type

Description

Description

Specifies one of the combination bookmarks to be included in the report.

Specifiable value

None

Omissible

Yes (The graph zoom scale is set to 100 (%).)

Attribute

zoom-scale

Specifies the graph zoom scale. 100, 200, 400, 600, or 800 can be specified as the value. The default is 100. Specifying an invalid value results in an error.

Parent element

combination-definition

Child element

None

combination-options

Type

Description

Description

Specifies options for the output of a combination report. Note that the baseline display setting is specified by the child element.

Specifiable value

None

Omissible

If this tag is omitted, display options for the combination report are not set.

Attribute

None

Parent element

combination-definition

Child element #

combination-indication-settings (can be specified only once per combination-options or can be omitted)

baseline-indication-settings (can be specified only once per combination-options or can be omitted)

# If you specify child elements, specify them in the order listed above.

combination-indication-settings

Type

Description

Description

Specifies the report acquisition period, report interval, start time, and end time for a combination report.

Specifiable value

None

Omissible

If this tag is omitted, the values in the report definition are applied including the values that are specified using the child elements.

Attribute

None

Parent element

combination-options

Child element

date-range (can be specified only once per combination-indication-settings or can be omitted)

start-time (can be specified only once per combination-indication-settings or can be omitted)

end-time (can be specified only once per combination-indication-settings or can be omitted)

report-interval (can be specified only once per combination-indication-settings or can be omitted)

exclude-terminal-data (can be specified only once per combination-indication-settings or can be omitted)

baseline-indication-settings

Type

Description

Description

Specifies the display start position for the baseline in a combination report. Note that the baseline display start position is specified by the child element.

Specifiable value

None

Omissible

If this tag is omitted, the default setting (start date and time of the report) is used as the start position for the baseline.

Attribute

None

Parent element

combination-options

Child element

baseline-start-time

baseline-start-time

Type

Description

Description

Specifies the display start position for the baseline in a combination report.

There are two ways to specify this: directly as an absolute time, and relatively using the child element <relative-time> tag.

Specifiable value

Use the format specified in report-interval to specify the position. For reports for which report-interval cannot be specified, specify the display start position in the format to be applied when MINUTE is specified for report-interval.

Example 1

If you specify pattern-yyyyMMdd for the -dateformat argument, space for the -dateseparator argument, and MINUTE for report-interval, specify baseline-start-time in YYYYMMDDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 2

If you specify pattern-yyyyMMdd for the -dateformat argument, slash for the -dateseparator argument, and MINUTE for report-interval, specify baseline-start-time in YYYY/MM/DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 3

If you specify pattern-yyyyMMdd for the -dateformat argument, hyphen for the -dateseparator argument, and MINUTE for report-interval, specify baseline-start-time in YYYY-MM-DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

Example 4

If you specify pattern-yyyyMMdd for the -dateformat argument, period for the -dateseparator argument, and MINUTE for report-interval, specify baseline-start-time in YYYY.MM.DDhh:mm format (YYYY = year, MM = month, DD = day, hh = hour, mm = minutes).

An error occurs in the following cases:

The specified value is invalid.

The format is invalid.

The specified value is greater than end-time.

The specified year is before 1970 or after 2036.

Omissible

Yes (cannot be omitted when baseline-start-time is specified)

Attribute

None

Parent element

baseline-indication-settings

Child element

relative-time (this can only be specified once per baseline-start-time, and can be omitted.)

Legend:

: A space

relative-time

Type

Description

Description

Specifies a base time or relative time from the base time.

The base time is the local time for the PFM - Web Console host, and is specified by the origin attribute, by selecting the command execution time, or command execution hour, day, week, month, or year from the start time. Since the optional year, month, week, day, hour, and minute attributes can be specified in combination, a relative time from the base time can be specified.

An error will occur if the year of the last calculated time is earlier than 1970 or later than 2036.

Specifiable value

None

Omissible

If this is omitted, the absolute time needs to be specified according to the parent element format.

Attribute

origin

Specifies the base time, command execution time, or hour, day, week, month, or year for the start time.

NOW or now

The time the command is executed

THIS-HOUR or this-hour

The first minute of the hour the command is executed

THIS-DAY or this-day

The first hour and minute of the time the command is executed

THIS-WEEK or this-week

The first hour and minute of the first day of the week the command is executed

THIS-MONTH or this-month

The first minute, hour, and day of the month the command is executed

THIS-YEAR or this-year

The first minute, hour, day, and month of the year the command is executed

An error will occur if a value other than the above is specified, or the value is omitted.

The default start day differs depending on the locale of the environment on which the command is executed. The default start day is Sunday in Japan and the US. The start day can be changed optionally using the firstDayOfWeek parameter in config.xml.

year

Specifies a relative number of years from the base time. This is 0 by default. In attributes indicating a relative value, this is evaluated first. An error will occur if the year of the last calculated time is earlier than 1970 or later than 2036.

month

Specifies a relative number of months from the base time. This can be from -12 to 12. This is 0 by default. This is evaluated after the year attribute.

week

Specifies a relative number of weeks from the base time. This can be from -53 to 53. This is 0 by default. This is evaluated after the month attribute.

day

Specifies a relative number of days from the base time. This can be from -366 to 366. This is 0 by default. This is evaluated after the week attribute.

hour

Specifies a relative number of hours from the base time. This can be from -24 to 24. This is 0 by default. This is evaluated after the day attribute.

minute

Specifies a relative number of minutes from the base time. This can be from -60 to 60. This is 0 by default. This is evaluated after the hour attribute.

Parent element

start-time, end-time, expression-value, baseline-start-time

Child element

None

Notes

This command requires authentication for PFM - Manager during execution. If a key file for authentication has not been created prior to command execution, use the jpcmkkey command to create the key file for authentication.

When multiple reports are output and an output error occurs with one of the reports, the command skips that report and outputs the next report. However, if a syntax error is detected in the parameter file, the command terminates at that point.

An attempt to output an HTML report that displays many records might cause the View Server service to terminate due to insufficient memory. If you do not want this problem to occur, consider whether you should use the report cache filing function. If you choose to use the function, enable it by using the initialization file (config.xml).

For details, see the chapter on Performance Management installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

When the report cache filing function is enabled and HTML reports are output, a subdirectory is created in the directory below each time the command is executed, and a report cache file is stored in that subdirectory:

In Windows:

PFM-Web-Console-installation-folder\reportcache\cmd\

In UNIX:

/opt/jp1pcwebcon/reportcache/cmd/

If this command is forcibly terminated (for example, by pressing Ctrl+C), the report cache file being created remains. Manually delete the file after the command terminates. Note that if you forcibly terminate an instance of the jpcrpt command while other instances of that command are still running, you cannot identify the report cache file that you need to delete. Therefore, make sure that all instances of the jpcrpt command have terminated before deleting any report cache files.

If this command is executed when the report cache filing function is enabled and all agents specified in the report are stopped, the command processing stops with a KAVJK0305-E message. If this message is output, make sure that at least one of those agents is operating, and then re-execute the command. Note that, in this case, an HTML file is not output.

When the report cache filing function is enabled and an attempt is made to output a combination report, if one of the following errors occurs in any reports that make up the combination report, the command processing stops:

An error in communication with PFM - Manager

An I/O error for a report cache file

An unexpected error

If the command processing stops as above, determine the cause of the error from the error message that is output, and take appropriate measures. Note that, in this case, an HTML file is not output.

This note applies when a function that places a limit on the number of data items that can be displayed in graphs is being used. When this function and the report cache filing function are enabled, if the number of data items to be displayed in graphs exceeds the limit, the processing stops with a KAVJK2512-E message. If this occurs, review the value of graphMaxReportData in the initialization file (config.xml).

This note applies when a limit is placed on the maximum number of table rows that can be included in an HTML report. If the number of rows to be included in the report exceeds the limit, a KAVJK6503-I message is output, and the command outputs only the rows before the limit is exceeded. To increase the number of rows that can be output, change the value of cmdHtmlTableOutputMaxRowSize in the initialization file (config.xml).

Note that even when the maximum number of rows that can be output is limited, depending on the number of selected fields, the amount of table data might exceed the maximum, causing a memory shortage. If you think this is likely to occur when executing the command, specify the -mx option to expand the maximum heap size.

If the filtering condition is set to Specify when displayed in the report definition and an initial value has been set, the command uses the initial value whether or not the parameter file contains a setting. If no initial value has been set and no value is set in the parameter file, an error results.

The following table shows the settings during report acquisition that depend on the combination of date-range, start-time, and end-time:

Table 2‒33: Combination of date-range, start-time, and end-time specifications

Whether or not specified in parameter file

Setting during report execution

date-range

start-time

end-time

date-range

start-time

end-time

N

N

N

Value in report definition

Value determined from end-time#1

PFM - Web Console server time during report execution

N

Y

N

Specify when displayed

Value specified in parameter file

#2

N

N

Y

Specify when displayed

#1

Value specified in parameter file

N

Y

Y

Specify when displayed

Value specified in parameter file

Value specified in parameter file

Y

N

N

Value specified in parameter file

#1

PFM - Web Console server time during report execution

Y

Y

N

Specify when displayed

Value specified in parameter file

#2

Y

N

Y

Specify when displayed

#1

Value specified in parameter file

Y

Y

Y

Results in error

Results in error

Results in error

Legend:

Y: Specified

N: Not specified

#1

For the calculation method, see the value of start-time in Table 2-34 Formulas for determining start-time and end-time.

If date-range is set to SPECIFY_WHEN_DISPLAYED, the value is determined by the report-interval setting.

#2

For the calculation method, see the value of end-time in Table 2-34 Formulas for determining start-time and end-time.

If date-range is set to SPECIFY_WHEN_DISPLAYED, the value is determined by the report-interval setting.

Table 2‒34: Formulas for determining start-time and end-time

date-range

report-interval

Value of start-time

Value of end-time

WITHIN_THE_PAST_HOUR

Minute

Value obtained by subtracting 1 hour from end-time

Value obtained by adding 1 hour to start-time

WITHIN_THE_PAST_24_HOURS

Hour

Value obtained by subtracting 1 day from end-time

Value obtained by adding 1 day to start-time

WITHIN_THE_PAST_7_DAYS

Day

Value obtained by subtracting 7 days from end-time

Value obtained by adding 7 days to start-time

WITHIN_THE_PAST_MONTH

Week

Value obtained by subtracting 1 month from end-time. If the resulting date is invalid, the immediately preceding date is assumed. If that date is also invalid, then the last valid date is set.

Value obtained by adding 1 month to start-time. If the resulting date is invalid, the immediately preceding date is assumed. If that date is also invalid, then the last valid date is set.

WITHIN_THE_PAST_YEAR

Month

Value obtained by subtracting 1 year from end-time. If the specification was made on February 29 of a leap year, February 28 of the previous year is set.

Value obtained by adding 1 year to start-time. If the specification was made on February 29 of a leap year, February 28 of the following year is set.

Year

The following table lists the input formats for start-time, end-time, and baseline-start-time:

Table 2‒35: Input formats for start-time, end-time, and baseline-start-time

report-interval

Date format#

[ddMMyyyy]

[MMddyyyy]

[yyyyMMdd]

MINUTE

[ddMMyyyyHH:mm]

[MMddyyyyHH:mm]

[yyyyMMddHH:mm]

HOUR

[ddMMyyyyHH:00]

[MMddyyyyHH:00]

[yyyyMMddHH:00]

DAY

[ddMMyyyy]

[MMddyyyy]

[yyyyMMdd]

WEEK

[ddMMyyyy]

[MMddyyyy]

[yyyyMMdd]

MONTH

[MMyyyy]

[MMyyyy]

[yyyyMM]

YEAR

[yyyy]

[yyyy]

[yyyy]

#

The date format is determined based on the values set in the -dateformat and -dateseparator command line arguments. For details, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

In the above table, represents a space by default. When you specify slash, hyphen, or period as the separator name in the date format, the separator is replaced by a slash (/), a hyphen (-), or a period (.).

Note the following when outputting realtime reports:

An error will occur if PFM - Manager, PFM - Agent, or PFM - RM is stopped during the first connection for the output of a report.

No timeout will occur during report output if the connection destination service is stopped.

The Ctrl + C keys or kill command can be used to stop a command during foreground execution.

Commands executed in the background cannot be stopped. When using background execution, adjust the -rc option is adjusted beforehand, then use background execution.

This command accesses the PFM - Manager View Server service whenever it is executed. If this command is executed concurrently or in succession, this command might fail because the View Server service cannot release memory in a timely manner. As such, if concurrent or successive execution of this command fails, use the sleep command or another method to adjust the command execution interval.

If you execute this command from a program that does not support interactive programs, an error might occur at the confirmation for overwriting the file. Specify the -y option to skip the confirmation for overwriting the file.

Return values

0

The command terminated normally.

1

Command line format is invalid.

2

The user does not have execution permission for the command.

4

The range specified in -rc or -ri option is invalid.

5

A parameter cannot be analyzed because it does not conform to a DTD file.

6

An invalid DTD file was specified.

10

A value specified in the input file is invalid.

11

PFM - Manager authentication processing failed.

21

An output file cannot be accessed.

70

Processing to acquire a report has timed out.

80

The user rejected overwriting.

100

Initialization failed due to invalid Performance Management environment.

200

A memory shortage occurred.

202

An input file cannot be accessed.

220

Access to PFM - Manager failed.

222

Connection to PFM - Manager failed.

223

A communication error occurred.

224

Connection to PFM - Manager or PFM - RM failed.

229

An error occurred at PFM - Manager for the connection destination.

255

An unexpected error occurred.

Usage example

This example outputs to the output.csv file the parameter file param.xml that contains report output definitions:

jpcrpt -o output.csv -y param.xml

Output example

This example outputs the details of the command's processing to the standard output, standard error output, and trace log file. For details about the log specifications, see 3. Log Information Output by Performance Management.

An example is shown below of the standard output format. It displays the execution results of the report output specified in the arguments.

Example of standard output (when the processing is successful)

jpcrpt connected to hostname at dd MM yyyy HH:MM:SS.mmm
result  OK  : report-definition-directory-path/report-definition-name@agent-ID
jpcrpt disconnected at dd MM yyyy HH:MM:SS.mmm

Output files

Outputting the contents of a report in CSV format

The following table describes the information that is displayed in the data header of the file that is output by this command:

Table 2‒36: Information displayed in data header

Data header information

Information that is output

Report:

Absolute path of the report name

Agents:

Agent name. Regardless of the product name display functionality settings, this is always output in a format with the product name display functionality disabled.

Date Format:

Date format and separator

Command:

Option information in the order specified.

null line

None

Column heading

Field's column heading.

This is the schema name of the field. However, if Display name has been set for the field during definition, that Display name is displayed.

For details, see the chapter describing how to create reports to analyze data in the Job Management Partner 1/Performance Management User's Guide.

An example is shown below of a file output by this command. If the resulting count is 0 or the agent is stopped, the data section is not displayed, in which case only the data header section is displayed.

Example of output file when the contents of a report are output in CSV format

Report: /Windows/Troubleshooting/RecentPast/System Overview
Agents: TA1htmprsvr
Date Format: pattern-yyyyMMdd,slash
Command:jpcrpt -input C:\ProgramFiles\Hitachi\jp1pcwebCon\
        param.xml,-o C:\ProgramFiles\Hitachi\jp1pcwebCon\
        output.csv,-y

Agent Host,Agent Instance,Date and Time,CPU %,User CPU %,
Privileged CPU %,Processor Queue Length,Context Switches/sec,
               % Total Interrupt Time,System Calls/sec
htmprsvr,htmprsvr,2006/07/03 09:00:00,10.910626,8.917643,
                1.9929985,4,825.3214,0.040342055,3351.263
htmprsvr,htmprsvr,2006/07/03 10:00:00,10.646775,9.116808,
                1.5356027,5,778.178,0.009959743,3238.7776
htmprsvr,htmprsvr,2006/07/03 11:00:00,11.603203,9.505386,
                2.0978165,3,809.5369,0.036344547,3257.031
htmprsvr,htmprsvr,2006/07/03 12:00:00,2.2210534,0.8610586,
                1.3599948,2,744.3879,0.0121342335,3597.5398
htmprsvr,htmprsvr,2006/07/03 13:00:00,2.2657635,1.1398388,
                1.1259354,3,675.37067,0.024730453,2883.5593
htmprsvr,htmprsvr,2006/07/03 14:00:00,10.394524,8.527414,
                1.8726714,4,817.1143,0.009072154,3453.1233

Outputting the contents of a report in HTML format

A report in HTML format consists of a report header, graphs, and tables.

For details about each part output and the output conditions, see the chapter describing how to create reports to analyze data in the Job Management Partner 1/Performance Management User's Guide.

If there are no items or if the agent is inactive, only the report header is output.

HTML documents are output in UTF-8. The character encoding and linefeed settings in the Export format in config.xml are not applied.

Note that the agent name output in the report header section is always output in a format with the product name display functionality disabled, regardless of the product name display functionality settings.

Example of report execution by relative time specification

By using relative time specifications and creating reports regularly, the efficiency of acquisition periods can be increased. The following shows an example parameter file using relative time specification. Note that relative time specifications can only be used for PFM - Web Console 09-00 or later.

Example 1

The following performs report execution every 24 hours (00:00 to 24:00). Note that the jpcrpt command is executed the next day from 00:00 to 24:00.

Agent: TA1host1

Report definition: /Folder1/ReportA

Acquisition period: One day starting from the day before the jpcrpt command is executed

Sample parameter file name: jpcrpt-parameters-for-scheduled-operation1.xml

Edit the bold characters in the sample parameter file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0220">
  <launch-report>
    <agent>TA1host1</agent>
    <report-definition name="ReportA" parent-folder="/Folder1">
      <launch-options>
        <indication-settings>
          <report-interval>HOUR</report-interval>
           <start-time>
             <relative-time origin="THIS-DAY" day="-1"/>
           </start-time>
           <end-time>
             <relative-time origin="THIS-DAY"/>
           </end-time>
        </indication-settings>
      </launch-options>
    </report-definition>
  </launch-report>
</pr-cli-parameters>

In the above example, THIS-DAY is specified for the origin attribute of both the <start-time> tag and <end-time> tag, and 0:00 of the day of jpcrpt command execution is used as the base time. -1 is specified for the day attribute of the <start-time> tag, and goes back one day from then. This means that the 0:00 of the previous day is specified as the acquisition period start time, and 0:00 of this day is specified as the acquisition period end time. When a PI record is to be output, the interval for which reports are output is specified using the <report-interval> tag.

Example 2

The following performs report execution everyday from 8:30 to the next day at 5:00. Note that the jpcrpt command is executed from 5:00 to 8:30 the next day.

Agent: TA1host1

Report definition: /Folder1/ReportA

Acquisition period: From 8:30 the day before the jpcrpt command is executed until the current day at 5:00

Sample parameter file name: jpcrpt-parameters-for-scheduled-operation2.xml

Edit the bold characters in the sample parameter file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0220">
  <launch-report>
    <agent>TA1host1</agent>
    <report-definition name="ReportA" parent-folder="/Folder1">
      <launch-options>
        <indication-settings>
          <report-interval>MINUTE</report-interval>
           <start-time>
             <relative-time origin="THIS-DAY" day="-1" hour="8" minute="30"/>
           </start-time>
           <end-time>
             <relative-time origin="THIS-DAY" hour="5"/>
           </end-time>
        </indication-settings>
      </launch-options>
    </report-definition>
  </launch-report>
</pr-cli-parameters>

As shown in example 1, settings can be set in detail by using hours and minutes. When the <start-time> is set to 8:30 on the previous day, and the day attribute is not specified, but the hour attribute is set to -15 and the minute attribute is set to -30, the results are the same. However, as shown in this example, setting the day attribute 1 day back and then setting the hour attribute and minute attribute from there helps create an easy-to-read definition. When a PI record is to be output, the interval for which reports are output is specified using the <report-interval> tag.

Example 3

The following performs report execution every week from Monday to Friday (the last day). Note that the jpcrpt command is batch executed on the following Saturday.

Agent: TA1host1

Report definition: /Folder1/ReportA

Acquisition period: From Monday to Friday (including 24:00 on Friday (0:00 on Saturday)), the day of the week that the jpcrpt command is executed

Sample parameter file name: jpcrpt-parameters-for-scheduled-operation3.xml

Edit the bold characters in the sample parameter file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0220">
  <launch-report>
    <agent>TA1host1</agent>
    <report-definition name="ReportA" parent-folder="/Folder1">
      <launch-options>
        <indication-settings>
          <report-interval>DAY</report-interval>
           <start-time>
             <relative-time origin="THIS-WEEK" day="1"/>
           </start-time>
           <end-time>
             <relative-time origin="THIS-WEEK" day="6"/>
           </end-time>
        </indication-settings>
      </launch-options>
    </report-definition>
  </launch-report>
</pr-cli-parameters>

When the origin attribute is set to THIS-WEEK, the base time is the start day for the week, at 0:00. In Japan, the start day of the week is set to Sunday by default. In the above example, therefore, the day attribute under <start-time> is set to +1 so that 0:00 on Monday is set as the start time. Similarly, the day attribute under <end-time> is set to +6 so that 0:00 on Saturday (24:00 on Friday) is set as the end time. This will get the same results as setting the day attribute to +5 and the hour attribute to +24 for the <end-time>.

Note that if execution of the jpcrpt command shifts to Sunday, since the base time will shift into the next week, the week attribute might need to be set to -1.

When a PI record is to be output, the interval for which reports are output is specified using the <report-interval> tag.

Example 4

The following performs monthly report execution every month starting on the 25th at 22:00. However, because the time needed for monthly processing might vary, the end time might cross over to the 26th. As such, execute the jpcrpt command immediately after monthly processing completes.

Agent: TA1host1

Report definition: /Folder1/ReportA

Acquisition period: From 22:00 on the 25th of the month the jpcrpt command is executed, until just before the command is executed

Sample parameter file name: jpcrpt-parameters-for-scheduled-operation4.xml

Edit the bold characters in the sample parameter file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0220">
  <launch-report>
    <agent>TA1host1</agent>
    <report-definition name="ReportA" parent-folder="/Folder1">
      <launch-options>
        <indication-settings>
          <report-interval>MINUTE</report-interval>
           <start-time>
             <relative-time origin="THIS-MONTH" day="24" hour="22"/>
           </start-time>
           <end-time>
             <relative-time origin="NOW"/>
           </end-time>
        </indication-settings>
      </launch-options>
    </report-definition>
  </launch-report>
</pr-cli-parameters>

The following shows an example specification for monthly report execution. The end time is NOW, the command execution time. To keep the start time from shifting, the base time is set to THIS-MONTH instead of THIS-DAY. One thing to keep in mind about specifying THIS-MONTH and the day attribute together is that since THIS-MONTH indicates the first day of the current month, when the 25th day of the current month is specified relatively, the day attribute needs to be set to +24. For the same reason, please pay attention to the month attribute and day attribute values when specified with THIS-YEAR. When a PI record is to be output, the interval for which reports are output is specified using the <report-interval> tag.

Example 5

The following performs quarterly (3-month) report execution. The jpcrpt command is executed the next month after each quarter, in April, July, October, and January.

Agent: TA1host1

Report definition: /Folder1/ReportA

Acquisition period: From 3 months before the jpcrpt command is executed until the month before (including 24:00 on the last day of the previous month (0:00 on day 1 of the current month))

Sample parameter file name: jpcrpt-parameters-for-scheduled-operation5.xml

Edit the bold characters in the sample parameter file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0220">
  <launch-report>
    <agent>TA1host1</agent>
    <report-definition name="ReportA" parent-folder="/Folder1">
      <launch-options>
        <indication-settings>
          <report-interval>MONTH</report-interval>
          <start-time>
            <relative-time origin="THIS-MONTH" month="-3"/>
          </start-time>
          <end-time>
            <relative-time origin="THIS-MONTH"/>
          </end-time>
        </indication-settings>
      </launch-options>
    </report-definition>
  </launch-report>
</pr-cli-parameters>

The following is an example specification for quarterly reports. Since the acquisition period is three months, the month attribute of the <start-time> tag is set to -3. When a PI record is to be output, the interval for which reports are output is specified using the <report-interval> tag.

Example 6

The following performs report execution every day for a 24-hour (from 0:00 to 23:59) report. Note that the jpcrpt command is executed at any point in time from 0:00 to 24:00 on the next day.

Agent: TA1host1

Report definition: /Folder1/ReportA

Acquisition period: The day before execution of the jpcrpt command

Sample parameter file name: jpcrpt-parameters-for-scheduled-operation6.xml

Edit the bold characters in the sample parameter file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pr-cli-parameters SYSTEM "rpt_params.dtd">
<pr-cli-parameters ver="0220">
 <launch-report>
  <agent>TA1host1</agent>
  <report-definition name="ReportA" parent-folder="/Folder1">
   <launch-options>
    <indication-settings>
     <start-time>
      <relative-time origin="THIS-DAY" day="-1"/>
     </start-time>
     <end-time>
      <relative-time origin="THIS-DAY"/>
     </end-time>
     <exclude-terminal-data>ENDTIME</exclude-terminal-data>
    </indication-settings>
   </launch-options>
  </report-definition>
 </launch-report>
</pr-cli-parameters>

In the above example, the origin attributes under the <start-time> and <end-time> tags are set to THIS-DAY so that the base time is set to 0:00 on the day that the jpcrpt command is executed. To set the start day to the day before the day on which the command is executed, -1 is set for the day attribute under the <start-time> tag. To prevent the command from outputting the data at 0:00 on the current day (24:00 on the previous day), ENDTIME is specified in the <exclude-terminal-data> tag. As a result, the acquisition start time is set to 0:00 on the previous day, and the acquisition end time is set to 0:00 on the current day (23:59:59 on the previous day).

jpcspm start

Format

jpcspm start    -key service-key
               [-lhost logical-host-name]
               [-inst instance-name]

Function

The jpcspm start command starts services of Performance Management programs. It cannot start the services of Performance Management programs at a remote host.

You can use the jpctool service list command to check the status of the Performance Management program services. jpcspm start commands cannot be executed concurrently, nor can one be executed simultaneously with the jpcspm stop command.

When the services to be started include PFM - Manager and the health check function is enabled on the PFM - Manager host on which you execute the command, the health check agent also starts as part of the PFM - Manager service. Note that you cannot specify agt0 as the service key.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the service that is to be started. A product name can also be specified when the product name display functionality is enabled. You can also specify the following in service-key:

all: The services of all Performance Management programs. If linkage is set with the start and stop of PFM - Web Console, the PFM - Web Console service also starts at the same time.

jp1pc: All Performance Management services (excluding the PFM - Web Console service).

Manager or mgr: The PFM - Manager services (excluding the Action Handler service).

AH or act: The Action Handler service.

StatSvr or stat: The Status Server service.

WebConsole or wc: The PFM - Web Console service. This can be specified when linkage is set with the start and stop of PFM - Web Console.

For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide. For details about linkage with the start and stop of PFM - Web Console, see the chapter describing start and stop for Performance Management in the Job Management Partner 1/Performance Management User's Guide.

-lhost logical-host-name

Specifies the host environment in which this command is executed. You use this argument if a logical host has been configured on the machine that is used to execute this command. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters.

If this argument is omitted, the physical host is assumed. Wildcard characters cannot be used.

-inst instance-name

If a specific instance of the service is to be started, specifies the instance name. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. This option is applicable only to a PFM - Agent or PFM - RM that has an instance environment. This option is ignored for any other service, if specified.

Notes

If PFM - Manager and PFM - Agent, or PFM - Manager and PFM - RM are installed on the same host, PFM - Manager must be started first in order to start the PFM - Agent, PFM - RM, or Action Handler service. If PFM - Manager and PFM - Agent, or PFM - Manager and PFM - RM are installed on separate hosts, the PFM - Agent, PFM - RM, or Action Handler service can be started in the stand-alone mode while PFM - Manager is not running. However, in the stand-alone mode, the available functions are limited. For details about these limitations, see the chapter describing start and stop for Performance Management in the Job Management Partner 1/Performance Management User's Guide. PFM - Agent version 06-70 does not support startup in the stand-alone mode. To start such a PFM - Agent, you must first start PFM - Manager, regardless of whether or not the PFM - Agent is installed on the same host as the PFM - Manager.

You must specify the arguments in the order they appear in Format.

If command execution returns the return value 103, monitoring of the process for starting the service of a Performance Management program timed out. Wait a while, and then re-execute the jpcspm start command. If this event occurs frequently, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

If command execution returns the return value 212, index creation for the Master Store, Agent Store, Remote Monitor Store service database failed. Check to see if there is enough free disk space. For guidelines for determining the required disk space, see the system estimates described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide or the applicable PFM - Agent or PFM - RM manuals. If there is enough disk space and re-execution of the jpcspm start command results in an index creation error again, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

If the status management function is enabled, and the service with the specified service key supports the status management function, and the Status Server service is not running, the Status Server service is started first. Note that if the status management function is disabled, the Status Server service is not started.

If the status management function is disabled, specifying stat in the service key displays the KAVE06023-E message and the command terminates.

Do not execute this command concurrently with a start or stop command executed from cluster software or the service control manager. Because these commands contend with each other, the start or stop command might not be executed correctly.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

The specified service is already running, or the command was executed while the Store database was being accessed by the Master Store, Agent Store, or Remote Monitor Store service, or a command.

5

The specified service has not been installed.

10

The command is executing in another session.

100

The Performance Management environment is invalid.

101

The PFM - Manager service is not running.

102

The specified logical host name or instance has not been set up.

103

Start process monitoring timed out.

107

Service start or stop processing is being executed by another process, such as Windows Service Control Manager.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

212

Index creation failed.

255

An unexpected error occurred.

Usage example 1

This example starts the services of all Performance Management programs:

jpcspm start -key all

Usage example 2

This example starts only the service of an instance named oracleA in the PFM - Agent for Oracle:

jpcspm start -key Oracle -inst oracleA

jpcspm stop

Format

jpcspm stop      -key service-key
                [-lhost logical-host-name]
                [-inst instance-name]
                [-kill immediate]

Function

The jpcspm stop command stops services of Performance Management programs. It cannot stop the services of Performance Management programs at a remote host.

You can use the jpctool service list command to check the status of the Performance Management program services. jpcspm stop commands cannot be executed concurrently, nor can one be executed simultaneously with the jpcspm start command.

When the services to be stopped include PFM - Manager and the health check function is enabled on the PFM - Manager host on which you execute the command, the health check agent also stops as part of the PFM - Manager service. Note that you cannot specify agt0 as the service key.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the service that is to be stopped. A product name can also be specified when the product name display functionality is enabled. You can also specify the following in service-key:

all: The services of all Performance Management programs. If linkage is set with the start and stop of PFM - Web Console, the PFM - Web Console service also stops at the same time.

jp1pc: All PFM - Manager services (excluding the PFM - Web Console service).

Manager or mgr: The PFM - Manager services (excluding the Action Handler service).

AH or act: The Action Handler service.

StatSvr or stat: The Status Server service.

WebConsole or wc: The PFM - Web Console service. This can be specified when linkage is set with the start and stop of PFM - Web Console.

For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide. For details about linkage with the start and stop of PFM - Web Console, in the Job Management Partner 1/Performance Management User's Guide, see the chapter describing start and stop for Performance Management.

-lhost logical-host-name

Specifies the host environment in which this command is executed. You use this argument if a logical host has been configured on the machine that is used to execute this command. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters.

If this argument is omitted, the physical host is assumed. Wildcard characters cannot be used.

-inst instance-name

If a specific instance of the service is to be stopped, specifies the instance name. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. This option is applicable only for a PFM - Agent or PFM - RM that has an instance environment. This option is ignored for any other service, if specified.

-kill immediate

Specify this option to forcibly stop processes that are running in a cluster system. If all is specified in service-key, the command stops all processes running on the same host. If a service key other than all is specified, the command stops all the processes for the specified service(s). Note that processes cannot be stopped for a particular instance by specifying -inst.

Note

Use this option only for stopping processes forcibly during cluster operation.

Notes

You must specify the arguments in the order they appear in Format.

If command execution returns the return value 103, monitoring of the process for stopping the service of a Performance Management program timed out. Wait a while, and then re-execute the jpcspm stop command. If this event occurs frequently, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Once the jpcspm stop command is issued to stop PFM services, an attempt to stop the command (such as by pressing the Ctrl + C keys or with a signal) will not stop termination processing that has already been started by the command. If the jpcspm stop command is issued again to stop the service, the KAVE05034-E message might be displayed. Check the common message log for termination of the service and then re-execute the jpcspm stop command.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

In the case of a host that supports the status management function, the Status Server service is not stopped unless all or stat is specified in service-key.

If all is specified in service-key and the -lhost option is specified, the Status Server service will not be stopped.

If the status management function is enabled, and the jpcspm stop command with all or stat specified in service-key is executed at the physical host, and at least one service that depends on the Status Server service is running at the logical host (version that supports the status management function), the command will display the KAVE06022-I message and return the return value 108.

Do not execute this command concurrently with a start or stop command executed from cluster software or the service control manager. Because these commands contend with each other, the start or stop command might not be executed correctly.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

The specified service has already been stopped.

5

The specified service has not been installed.

10

The command is executing in another session.

100

The Performance Management environment is invalid.

102

The specified logical host name or instance has not been set up.

103

Stop process monitoring timed out.

107

Service start or stop processing is being executed by another process such as Windows Service Control Manager.

108

Status Server cannot be stopped because a service that depends on the Status Server service is running.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Usage example 1

This example stops all services of the Performance Management programs:

jpcspm stop -key all

Usage example 2

This example stops only the service of an instance named oracleA in the PFM - Agent for Oracle:

jpcspm stop -key Oracle -inst oracleA

jpctool alarm active

Format

jpctool alarm active    -key service-key
                        -table alarm-table-name
                        -alarm alarm-name
                        [-wait number-of-seconds]

Function

The jpctool alarm active command enables a disabled alarm.

Alarms are enabled individually; they cannot be enabled by alarm table in batch mode.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM for which an alarm definition is to be enabled. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-table alarm-table-name

Specifies the name of the alarm table in which the alarm to be enabled is defined.

For alarm-table-name, specify a string of 1 to 64 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-alarm alarm-name

Specifies the name of the alarm to be enabled.

If the specified alarm has already been enabled, this command terminates normally.

For alarm-name, specify a string of 1 to 20 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) that is specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Notes

This command cannot be executed concurrently.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

If arguments of a jpctool alarm command include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

If PFM - Manager is installed on a logical host, execute the command on the executing node.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

It might take several tens of seconds until this command takes effect on the agent after this command has terminated.

For notes on successive stopping of the monitoring using alarms and the monitoring target system, see Notes on execution of jpctool alarm commands.

If the monitoring is suspended, alarms can be enabled but the monitoring remains suspended.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent for which alarms are to be enabled has not been set up.

Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The specified alarm table or alarm is missing.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

This example enables the Disk Service Time alarm defined in the PFM - Agent for Platform (UNIX) monitoring template for PFM UNIX Solution Alarms 8.00.

jpctool alarm active -key UNIX -table "PFM UNIX Solution Alarms 8.00" -alarm "Disk Service Time"

Usage example 2

This example enables the alarm alarm1 that is defined in the alarmtable1 alarm table for PFM - Agent for Platform (UNIX):

jpctool alarm active -key UNIX -table alarmtable1 -alarm alarm1

jpctool alarm bind

Format

jpctool alarm bind -key service-key
                   -table alarm-table-name
                   -id service-ID
                  [-add]
                  [-wait number-of-seconds]

Function

The jpctool alarm bind command binds a defined alarm table to an agent.

If this command is executed on an agent to which an alarm table has already been bound, the alarm table specified in this command is bound to the agent.

In some cases, the alarm table to be bound includes alarms indicating state changes for individual instances. In such cases, the Agent Collector service with the service ID you specify must consist of a PFM - Agent and PFM - Base pair that supports the notification of state changes for each instance. If the Agent Collector service does not consist of a PFM - Agent and PFM - Base pair that supports the notification of state changes for each instance, a KAVE05969-E message will be output.

If multiple service IDs are specified, even if the bind processing for a service terminates abnormally, the alarm table bind processing will continue for other services. If the bind processing for all those services results in errors, this command will return the return value that indicates the last error.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM to which the alarm table is to be bound. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-table alarm-table-name

Specifies the name of the alarm table that is to be bound.

For alarm-table-name, specify a string of 1 to 64 bytes long, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-id service-ID

Specifies the service ID for the agent to which the alarm table is to be bound. For service-ID, specify a string from 1 to 258 bytes. To bind the alarm table to a PFM - RM monitoring target, specify the service ID of the remote agent or group agent corresponding to the monitoring target. If the service ID of the Remote Monitor Collector service is specified, an error will occur.

You can use wildcard characters to specify multiple service IDs. In this case, even when an error occurs for a given Agent Collector service, remote agent, or group agent, processing will continue for the remaining Agent Collector services, remote agents, or group agents. If processing on multiple Agent Collector services, remote agents, or group agents results in an error, the command returns the value for the last error that occurred.

-add

Binds an additional alarm table, for version 09-00 or later. If this is executed for an agent for which another alarm table is already bound, the additional specified alarm table is bound. If this is executed for an agent for which the same alarm table is already bound, nothing will happen. An error will also occur if the functionality for binding multiple alarm tables is not enabled, or if, as a result of the additional binding, the number of tables bound exceeds 50 (the maximum number of bindable alarm tables).

If the specified alarm table is already bound for all specified service IDs, the KAVE05353-W message is displayed, and the command terminates normally.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Notes

This command cannot be executed concurrently.

This command updates a specified bind setting on PFM - Manager. When the bind setting is updated, the PFM - Manager service performs alarm table setting on the relevant running agent.

Therefore, if the alarm table setting on the agent fails because of a failure in agent communication or for other reasons even when this command has been executed successfully, a KAVE00448-E message is output to the common message log.

For details about the service ID, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

If the PFM - Agent or PFM - RM data model version number is smaller than the alarm table data model version number, the alarm table cannot be bound to the PFM - Agent or PFM - RM. If an unsupported alarm table data model version is specified, the command terminates with an error.

If arguments of a jpctool alarm command include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

If PFM - Manager is installed on a logical host, execute the command on the executing node.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

It might take several tens of seconds until this command takes effect on the agent after this command has terminated.

For notes on successive stopping of the monitoring using alarms and the monitoring target system, see Notes on execution of jpctool alarm commands.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running, or there is no PFM - Agent or PFM - RM that corresponds to the specified service ID.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent to which alarms are to be bound has not been set up.

Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The specified alarm table was not found, or the data model version of the specified alarm table cannot be bound.

The maximum number of alarm tables that can be bound was exceeded (09-00 or later).

11

The user canceled the processing.

12

The functionality for binding multiple alarm tables has not been enabled (09-00 or later).

13

The agent to which an alarm table is to be bound does not support the notification of state changes for each instance.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

This example binds the PFM UNIX Solution Alarms 8.00 monitoring template from PFM - Agent for Platform (UNIX), to the agent with host name host01 (service ID: UA1host01).

jpctool alarm bind -key UNIX -table "PFM UNIX Solution Alarms 8.00" -id UA1host01

Usage example 2

This example binds the alarmtable1 alarm table of PFM - Agent for Platform (UNIX) to all agents whose host name beings with host:

jpctool alarm bind -key UNIX -table alarmtable1 -id "UA1host*"

Usage example 3

This example binds the additional alarm table alarmtable3 to the service UA1hostA.

jpctool alarm bind -key UNIX -table alarmtable3 -id UA1hostA -add

jpctool alarm check

Format

jpctool alarm check     -f alarm-definition-file-name
                       [-syntax]
                       [-wait number-of-seconds]

Function

The jpctool alarm check command performs validity checking, such as checking the created alarm definition file for syntax errors, checking the definition information (to determine whether or not specified records and fields are supported), and checking the setup status of the required PFM - Agent or PFM - RM. To check the definition information and the setup status of the PFM - Agent or PFM - RM, the Name Server, Master Manager, and View Server services must be running. To perform only syntax checking without checking the definition information or the PFM - Agent or PFM - RM setup status, specify the -syntax option. When the -syntax option is specified, the command can be executed even when the Name Server, Master Manager, and View Server services are stopped.

If there is an error in the syntax of the alarm definition file or in the definition information, the command displays an error message containing the row number in the file and the nature of the error. If there is more than one error, the command displays an error message for each error.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f alarm-definition-file-name

Specifies the name of the alarm definition file to be checked. The file name can be expressed as a relative path or an absolute path.

The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

-syntax

Specifies that the alarm definition file is to be checked only for syntax errors.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Alarm definition file format

See the description of the alarm definition file format in the jpctool alarm import command.

Notes

This command cannot be executed concurrently.

To check the definition information and the setup status of the PFM - Agent or PFM - RM, the Name Server, Master Manager, and View Server services must be running. To perform only syntax checking without checking the definition information or the PFM - Agent or PFM - RM setup status, specify the -syntax option. When the -syntax option is specified, the command can be executed even when the Name Server, Master Manager, and View Server services are stopped.

If the file name you specify includes double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). Before you execute this command, check the setting of the LANG environment variable for the shell.

You can define a maximum of 250 alarms for an alarm table, including alarms that have already been defined. During validity checking on the information defined in the alarm definition file, the command does not check whether or not the total number of defined alarms exceeds 250.

You can define a maximum of 250 alarms at once by using the jpctool alarm import command. This command is useful when you define alarms on multiple servers in a large-scale system.

Note that the number of alarms that you can define at once cannot exceed 250 even if the import file contains multiple alarm tables.

An import using the following file succeeds:

Import file 1:

100 alarms are defined in alarm table A.

150 alarms are defined in alarm table B.

An import using the following file fails:

Import file 2:

200 alarms are defined in alarm table A.

150 alarms are defined in alarm table B.

In the alarm definition file to be checked, 0001 or 0002 must be specified for the Alarm Definition File Version label. If another version of alarm definition file is specified, a KAVE05305-E message will be output.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

When the -syntax option is omitted, at least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host.

6

There is an error in the contents of the alarm definition file.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

Alarm definition file cannot be accessed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

This example checks the syntax of the alarmtest1.cfg alarm definition file stored in the /tmp directory, and the validity of the definition information:

jpctool alarm check -f /tmp/alarmtest1.cfg

Usage example 2

This example checks only the syntax of the alarmtest2.cfg alarm definition file stored in the /tmp directory:

jpctool alarm check -f /tmp/alarmtest2.cfg -syntax

jpctool alarm copy

Format

jpctool alarm copy  -key service-key
                    -table source-alarm-table-name
                   [-alarm copy-source-alarm-name]
                    -name copy-destination-alarm-table-name-or-
                          copy-destination-alarm-name
                    [-wait number-of-seconds]

Function

The jpctool alarm copy command copies an alarm table or an alarm.

The following table shows what is copied (alarm table or alarm) depending on the combination of the -table and -alarm options that is specified:

Table 2‒37: Copy target (alarm table or alarm) depending on the combination of options that is specified

Option specifications

Information that is copied

-table

-alarm

S

N

The entire alarm table specified in the -table option is copied. If the alarm table contains multiple alarms, all its alarms are copied.

S

S

The alarm specified in the -alarm option in the alarm table specified in the -table option is copied.

Legend:

S: Specified

N: Not specified

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM whose alarm table or alarm is to be copied. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-table source-alarm-table-name

Specifies the name of the source alarm table.

For source-alarm-table-name, specify a string of 1 to 64 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-alarm source-alarm-name

Specifies the name of the source alarm.

For source-alarm-name, specify a string of 1 to 20 bytes long, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

Note that this option cannot be specified if the -table option was used to specify a monitoring template (alarm table with a name starting with PFM).

-name target-alarm-table-name-or-target-alarm-name

Specifies a name for the copy of the alarm table or alarm.

This cannot be the name of an existing alarm table or alarm.

If you specified only the -table option, specify a name for the copy of the alarm table. In this case, specify a string of 1 to 64 bytes long, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

An alarm table name beginning with PFM cannot be specified.

Wildcard characters cannot be used.

If you specified both the -table and -alarm options, specify a name for the copy of the alarm. In this case, specify a string of 1 to 20 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Notes

This command cannot be executed concurrently.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

When the -alarm option is specified, the alarm is copied within the same alarm table (the source alarm table). An alarm cannot be copied to a different alarm table.

A single alarm table can store a maximum of 250 alarms.

If arguments of a jpctool alarm command include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

For notes on successive stopping of the monitoring using alarms and the monitoring target system, see Notes on execution of jpctool alarm commands.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent to which alarms are to be copied has not been set up.

Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The specified alarm table or alarm is missing.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The specified target alarm table cannot be edited.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

This example copies the PFM UNIX Solution Alarms 8.00 monitoring template from PFM - Agent for Platform (UNIX) to the alarm table named alarmtable1.

jpctool alarm copy -key UNIX -table "PFM UNIX Solution Alarms 8.00" -name alarmtable1

Usage example 2

This example copies the alarm1 alarm in the alarmtable1 alarm table for PFM - Agent for Platform (UNIX) and names the copy alarm2:

jpctool alarm copy -key UNIX -table alarmtable1 -alarm alarm1 -name alarm2

jpctool alarm delete

Format

jpctool alarm delete   -key service-key
                       -table alarm-table-name
                      [-alarm alarm-name]
                      [-y]
                      [-wait number-of-seconds]

Function

The jpctool alarm delete command deletes an alarm table or an alarm.

The following table shows what is deleted (alarm table or alarm) depending on the combination of the -table and -alarm options that is specified.

Table 2‒38: Deletion target (alarm table or alarm) depending on the combination of options that is specified

Option specifications

Information that is deleted

-table

-alarm

S

N

The alarm table specified in the -table option and all alarms defined in that alarm table are deleted.

S

S

Only the alarm specified in the -alarm option is deleted.

Legend:

S: Specified

N: Not specified

Note

Monitoring templates (alarm tables with a name starting with PFM) cannot be deleted.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM whose alarm table or alarm is to be deleted. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-table alarm-table-name

Specifies the name of the alarm table to be deleted or from which an alarm is to be deleted.

For alarm-table-name, specify a string of 1 to 64 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-alarm alarm-name

Specifies the name of the alarm to be deleted.

For alarm- name, specify a string of 1 to 20 bytes long, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-y

Specifies that the specified alarm table or alarm is to be deleted forcibly without confirmation.

When -y is specified, the command deletes forcibly the specified alarm table or alarm.

When this option is omitted, the command displays a confirmation message asking whether or not the alarm table or alarm is to be deleted.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Note

This command cannot be executed concurrently.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

If arguments of a jpctool alarm command include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

It might take several tens of seconds until this command takes effect on the agent after this command has terminated.

For notes on successive stopping of the monitoring using alarms and the monitoring target system, see Notes on execution of jpctool alarm commands.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent to which alarms are to be deleted has not been set up.

Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The specified alarm table or alarm is missing.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

Deletion of the alarm table or alarm failed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

This example deletes the alarmtable1 alarm table defined in PFM - Agent for Platform (UNIX):

jpctool alarm delete -key UNIX -table alarmtable1

Usage example 2

This command deletes the alarm1 alarm from the alarmtable1 alarm table in PFM - Agent for Platform (UNIX) without confirmation:

jpctool alarm delete -key UNIX -table alarmtable1 -alarm alarm1 -y

jpctool alarm export

Format

jpctool alarm export    -f target-file-name
                       {-key service-key
                       [-table alarm-table-name[-alarm alarm-name]]|
                        -template}
                       [-y|-n]
                       [-wait number-of-seconds]

Function

The jpctool alarm export command exports alarm definitions to the specified file.

Alarm definition information is exported in accordance with the syntax of the alarm definition file. For details about the syntax of the alarm definition file, see the chapter in the Job Management Partner 1/Performance Management User's Guide that describes operation monitoring by alarms.

The following table shows the range of alarm definition information that is exported depending on the combination of the -key, -table, and -alarm options that is specified:

Table 2‒39: Range of alarm definition information that is exported depending on the combination of options that is specified

Option specifications

Information that is exported

-key

-table

-alarm

S

N

N

All alarm definition information for the alarm tables that are defined for the PFM - Agent or PFM - RM specified in the -key option is exported.

S

S

N

All alarm definition information in the alarm table that is specified in the -table option is exported.

S

S

S

Only the definition information for the alarm specified in the -alarm option is exported.

Legend:

S: Specified

N: Not specified

By specifying the -template option, you can output the template file that contains all the labels that are defined in the alarm definition file.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f target-file-name

Specifies a name for the alarm definition file to which definition information is to be exported. The file name can be expressed as a relative path or an absolute path.

The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM for which alarm definition information is to be exported. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

The -key and -template options are mutually exclusive.

-table alarm-table-name

Specifies the name of the alarm table that contains the alarm definition information to be exported.

For alarm-table-name, specify a string of 1 to 64 bytes long, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

The -table and -template options are mutually exclusive.

-alarm alarm-name

Specifies the name of the alarm whose alarm definition information is to be exported.

For alarm-table, specify a string of 1 to 20 bytes long, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

The -alarm and -template options are mutually exclusive.

-template

Specifies that the template for the alarm definition file is to be output.

This option cannot be specified together with the -key, -table, or -alarm option.

-y|-n

Specifies whether or not the alarm definition file specified in the -f option is to be overwritten forcibly if it already exists.

When -y is specified, the command forcibly overwrites an existing alarm definition file.

When -n is specified, the command skips overwrite processing.

When this option is omitted, the command displays a confirmation message asking whether or not an existing alarm definition file is to be overwritten.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Alarm definition file format

See the description of the alarm definition file format in the jpctool alarm import command.

Notes

This command cannot be executed concurrently.

You must start PFM - Manager (Name Server, Master Manager, and View Server services) before you can export existing alarm definition information with the -key, -table, or -alarm option specified. However, if you are outputting the template (-template option specified), it is not necessary for PFM - Manager to be running.

PFM - Agent and PFM - RM monitoring templates might contain alarms for which conditions for abnormal values and warning values are different. In this case, when a monitoring template is exported, conditions with warning values are given priority for export.

For example, if you export an alarm definition whose conditional expression for an abnormal value is BBB >= 90 and that for a warning value is BBB > 80, the warning value condition (>) is output to the alarm definition file as shown below:

[[Alarm Condition Expressions]]
Condition=BBB>90,80

For details about settings for abnormal value and warning value conditions for monitoring templates, see the chapter describing monitoring templates in the PFM - Agent or PFM - RM manuals.

You can export 251 or more alarm definitions at once. Note, however, that the maximum number of alarms that can be defined in one alarm definition file is 250. An export file containing 251 or more alarm definitions cannot be imported as an alarm definition file. To import these alarm definitions, you must divide the export file into multiple alarm definition files, each of which contains no more than 250 alarm definitions.

For example, assume that you specify the -key option to export alarm tables AlarmTable1 (containing 200 alarm definitions) and AlarmTable2 (containing 100 alarm definitions) that are bound to PFM - Agent or PFM - RM. In this case, 300 alarm definitions will be exported to one file. However, because one alarm definition file can contain a maximum of 250 alarm definitions, the exported file cannot be used as an import file. To import these alarm definitions, you must prepare multiple alarm definition files, each of which contains no more than 250 alarm definitions.

If the alarm definitions you export include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable setting of the shell and PFM - Manager match.

If the file name you specify includes double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). Before you execute this command, check the setting of the LANG environment variable for the shell.

If PFM - Manager is installed on a logical host, execute the command on the executing node.

If you specify an alarm table that includes an alarm for which the notification of state changes for each instance has not been specified, Alarm is set for the Notify State label in the alarm definition file to be exported.

Even if JP1 event issuance is correctly configured in the Command Definition area of the New Alarm > Action Definitions window or the Edit > Action Definitions window, N might be output for the JP1 event label that was exported by using this command (for example, when the value of the -r option is not enclosed in double quotation marks (")). However, JP1 event issuance is actually enabled as the alarm action. There is no problem even if you import the file in which N is output for the JP1 event label because JP1 event issuance is enabled as the alarm action.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent to which alarms are to be exported has not been set up.

6

The specified alarm table or alarm is missing, or the alarm definition was not found at the agent with the specified service key.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A target file cannot be accessed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

In this example, alarm table alarmtable1 is not a monitoring template, but is assumed to be defined for PFM - Agent for Platform (UNIX). Alarm table alarmtable1 is also assumed to have alarm alarm1 defined.

The following command exports all the alarm definitions defined for PFM - Agent for Platform (UNIX) to the alarmtable1.cfg file under the /tmp directory:

jpctool alarm export -f /tmp/alarmtable1.cfg -key UNIX

Output result 1 (alarmtable1.cfg)

Alarm Definition File Version=0002
Alarm Definition File Code=C

[Alarm Data]
[[General]]
Product=U3.0
Alarm Table Name="PFM UNIX Solution Alarms 8.00"
Alarm Name="Disk Service Time"
Message Text="Average disk service time is %CVS secs"
Check Value Exist=N
   :
[Alarm Data]
[[General]]
Product=U4.0
Alarm Table Name=alarmtable1
Alarm Name=alarm1
Message Text=
Check Value Exist=N
   :

Usage example 2

This example exports the Disk Service Time alarm definition to the file alarm2.cfg in the /tmp directory of the alarms defined in the PFM UNIX Solution Alarms 8.00 monitoring template for PFM - Agent for Platform (UNIX).

jpctool alarm export -f /tmp/alarm2.cfg -key UNIX -table "PFM UNIX Solution Alarms 8.00" -alarm "Disk Service Time"

Output result 2 (alarm2.cfg)

Alarm Definition File Version=0002
Alarm Definition File Code=C

[Alarm Data]
[[General]]
Product=U3.0
Alarm Table Name="PFM UNIX Solution Alarms 8.00"
Alarm Name="Disk Service Time"
Message Text="Average disk service time is %CVS secs"
Check Value Exist=N
   :

Usage example 3

This example outputs the alarm definition file template to the template3.cfg file under the /tmp directory:

jpctool alarm export -f /tmp/template3.cfg -template

Output result 3 (template3.cfg)

Alarm Definition File Version=0002
Alarm Definition File Code=

[Alarm Data]
[[General]]
Product=
Alarm Table Name=
Alarm Name=
Message Text=
Check Value Exist=N

[[Advanced Setting]]
Active Alarm=Y
Regular Alarm=Y
Evaluate All Data=N
Notify State=Alarm
Monitoring Regularly=N
Monitoring Time=
Damping=N
Damping Count=

[[Check Value Exist]]
Record=
Field=
Value=

[[Alarm Condition Expressions]]
Condition=

[[Actions]]
Report=
E-mail=Abnormal,Warning,Normal
Command=Abnormal,Warning,Normal
SNMP=Abnormal,Warning,Normal
JP1 Event=N

[[Action Definition E-mail]]
E-mail Address=
Action Handler=
[[[Message Text]]]
Date: %SCT
Host: %HNS

Product: %PTS
Agent: %ANS

Alarm: %AIS (%ATS)
State: %SCS

Message: %MTS
[[Action Definition Command]]
Command Name=
Action Handler=
[[[Message Text]]]

[[Action Definition JP1 Event]]
Event ID=
Action Handler=
Message=%MTS
Switch Alarm Level=Y
Exec Logical Host=

jpctool alarm import

Format

jpctool alarm import    -f alarm-definition-file-name
                       [-y|-n]
                       [-wait number-of-seconds]

Function

The jpctool alarm import command imports alarm definitions from the specified file, and defines and updates an alarm table and alarms.

Definition information is imported in units of alarms. If the alarm definition file contains definitions of multiple alarms and importation of one alarm's definition terminates abnormally, import processing continues for the next alarm definition. If multiple errors occur while the command is importing multiple alarm definitions, the return code set by the command is for the last error that occurred.

Before importing definition information, this command checks the syntax of the alarm definition file and the validity of the definition information. If there is an error in the syntax of the alarm definition file or the validity of the definition information, the command displays an error message containing the row number in the file and the nature of the error only for the first error that occurred.

The following table lists and describes the cause and nature of the errors that can be displayed in the error message:

Table 2‒40: Causes of errors displayed in error messages and nature of errors

Cause of error

Nature of error

The specified entry is invalid

A specified label name or section name is invalid.

The specified value is invalid

A specified value is invalid.

The syntax is invalid

There is a syntax error in the alarm definition file.

The entry (label-name-or-section-name) is not specified

The indicated required label or section is missing.

The specified product is invalid

A specified product ID or data model version is invalid.

The specified field is not defined

A specified record name or field name is not supported by the PFM - Agent or PFM - RM with the specified product ID.

The specified report is not defined

A specified report is not defined in the PFM - Agent or PFM - RM with the specified product ID.

The specified Action Handler is not defined

The specified action handler is missing.

The specified Action Handler does not have capability

The specified action handler has not been set to execute the specified action.

A Character-code is invalid

The specified character encoding is invalid.

The specified definition is too many

The number of alarm definitions exceeds the permitted maximum.

Total length of Abnormal condition definition is too long

The length of an abnormal condition statement in the alarm definition exceeds the permitted maximum length.

Total length of Warning condition definition is too long

The length of a warning condition statement in the alarm definition exceeds the permitted maximum length.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-f alarm-definition-file-name

Specifies the name of the alarm definition file that is to be imported. The file name can be expressed as a relative path or an absolute path.

The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

-y|-n

Specifies whether or not the existing definition information is to be updated forcibly if an alarm definition to be imported already exists.

When -y is specified, the command forcibly updates the existing alarm definition.

When -n is specified, the command skips update processing.

When this option is omitted, the command displays a confirmation message asking whether or not an existing alarm definition is to be overwritten.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of wait alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Alarm definition file format

List of settings values

Alarm Definition File Version label

Specifies the version of the alarm definition file syntax. The specified location is at the beginning of the file.

Table 2‒41: Alarm Definition File Version label

Type

Description

Description

Indicates the version of the alarm definition file syntax.

Specifiable value

0001 or 0002 can be specified.

When 0001 is specified

The file can be imported from all versions of PFM - Manager.

When 0002 is specified

The file can be imported from PFM - Manager 10-10 or later. Also, you can define the alarm for notification of state changes for each instance.

Omissible

No

Alarm Definition File Code label

The encoding for the alarm definition file is specified immediately after the Alarm Definition File Version label.

Table 2‒42: Alarm Definition File Code label

Type

Description

Description

Indicates the encoding for the alarm definition file.

Specifiable value

Shift_JIS

Specify this value if the file is created with double-byte SJIS characters or single-byte characters (7-bit ASCII characters).

EUC-JP

Specify this value if the file is created with double-byte EUC characters or single-byte characters (7-bit ASCII characters).

UTF-8

Specify this value if the file is created with double-byte UTF-8 characters or single-byte characters (7-bit ASCII characters).

C

Specified only when the file was created with single-byte characters (7bit ASCII characters).

GB18030

Specify this value if the file is created with double-byte GB18030 characters or single-byte characters (7-bit ASCII characters).

Omissible

No

Alarm Data section

Specifies the definition for a single alarm. When multiple alarms are defined, an Alarm Data section is created for each alarm definition. The Alarm Data section cannot be omitted.

The subsections that can be specified within the Alarm Data section are as follows.

Table 2‒43: Alarm Data section

Subsection name

Description

Optional

General

Sets basic information such as alarm name.

No

Advanced Setting

Sets the alarm type and options.

Yes

Check Value Exist

Sets the monitored values for alarms that monitor the existence of a value.

Yes (depending on the alarm definition)

Alarm Condition Expressions

Sets an alarm conditional expression for alarms other than those that monitor the existence of a value.

Yes (depending on the alarm definition)

Actions

Sets the executed action and displayed report for an alarm.

Yes

Action Definition E-mail

Specifies the settings for when an email is executed by an alarm.

Yes (depending on the alarm definition)

Action Definition Command

Specifies the settings for when a command is executed by an alarm.

Yes (depending on the alarm definition)

Action Definition JP1 Event

Specifies the settings for when a JP1 event is executed by an alarm.

Yes (depending on the alarm definition)

Legend:

Yes: Can be omitted.

No: Cannot be omitted.

General subsection

Specifies basic alarm information (such as the alarm name and message text). This subsection cannot be omitted.

The labels that can be specified for this subsection are as follows.

Table 2‒44: Product label

Type

Description

Description

Indicates the product and data model version for the alarm.

Specifiable value

<product-ID><data-model-version>

product-ID

Specifies the product ID of the agent for which the alarm is to be defined, in uppercase letters.

data-model-version

Specifies the version and revision in decimal notation, joined by periods (.).

Omissible

No

Table 2‒45: Alarm Table Name label

Type

Description

Description

Indicates the alarm table name.

Specifiable value

A string that is 1 to 64 bytes long and consists of double-byte and/or single-byte characters.

Any spaces after equals signs (=) and before line returns are ignored.

Names starting with PFM (case-insensitive) cannot be specified.

Omissible

No

Table 2‒46: Alarm Name label

Type

Description

Description

Indicates the alarm name.

Specifiable value

A string that is 1 to 20 bytes long and consists of double-byte and/or single-byte characters.

Any spaces after equals signs (=) and before line returns are ignored.

Omissible

No

Table 2‒47: Message Text label

Type

Description

Description

Indicates the message text output when the alarm event occurs.

Specifiable value

A string that is 0 to 255 bytes long and consists of double-byte and/or single-byte characters.

Any spaces after equals signs (=) and before line returns are ignored.

If the equals sign is only followed by spaces, these spaces are treated as not being specified.

Omissible

Yes

Table 2‒48: Check Value Exist label

Type

Description

Description

Indicates whether the alarm monitors the existence of a value.

Specifiable value

Y or N can be specified.

When Y is specified

The alarm is defined as monitoring the existence of the value.

When this is omitted or N is specified

The alarm is defined as a normal alarm.

Omissible

Yes

Advanced Setting subsection

Specifies extended alarm information (such as the alarm type and monitoring time). This subsection can be omitted.

The labels that can be specified for this subsection are as follows.

Note that you can specify the Notify State label only when the value of the Alarm Definition File Version label is 0002.

Table 2‒49: Active Alarm label

Type

Description

Description

Indicates the alarm status.

Specifiable value

Y or N can be specified.

When this is omitted or Y is specified

The alarm is enabled.

When N is specified

The alarm is disabled.

Omissible

Yes

Table 2‒50: Regular Alarm label

Type

Description

Description

Indicates whether the alarm setting Always notify is enabled.

Specifiable value

Y or N can be specified.

When Y is specified

Always notify is enabled.

When this is omitted or N is specified

Always notify is disabled.

Omissible

Yes

Table 2‒51: Evaluate All Data label

Type

Description

Description

Indicates whether the alarm setting Evaluate all data is enabled.

Specifiable value

Y or N can be specified.

When Y is specified

Evaluate all data is enabled.

When this is omitted or N is specified

Evaluate all data is disabled.

Omissible

Yes

Table 2‒52: Notify State label

Type

Description

Description

Indicates whether to enable the notification of a change of status.

Specification format

Notify State=Alarm|Instance

Specifiable value

Alarm or Instance can be specified.

When Alarm is specified

Notification of alarm status changes is carried out.

When Instance is specified

Notification of state changes for each instance is carried out.

Omissible

Yes (When omitted, specification of Alarm is assumed.)

Remarks

When Instance is specified, a syntax error occurs if the value of the Regular Alarm label and Evaluate All Data label is Y.

Table 2‒53: Monitoring Regularly label

Type

Description

Description

Indicates whether the Always monitor alarm setting is enabled.

Specifiable value

Y or N can be specified.

When this is omitted or Y is specified

Always monitor is enabled.

When N is specified

Always monitor is disabled.

Omissible

Yes

Table 2‒54: Monitoring Time label

Type

Description

Description

Indicates the monitoring time when the Always monitor alarm setting is disabled.

Specifiable value

start-time-end-time

This specifies the local time in HH:MM format. start-time and end-time are joined with a hyphen (-).

HH: Specifies the start time hour, from 00 to 23.

MM: Specifies the start time minute, from 00 to 59.

Omissible

Yes (but not when the value of the Monitoring Regularly label is N)

Table 2‒55: Damping label

Type

Description

Description

Indicates whether the Report alarm when the following damping condition is reached alarm setting is enabled.

Specifiable value

Y or N can be specified.

When Y is specified

Report alarm when the following damping condition is reached is enabled.

When this is omitted or N is specified

Report alarm when the following damping condition is reached is disabled.

Omissible

Yes

Table 2‒56: Damping Count label

Type

Description

Description

Indicates the number of times the threshold was exceeded and the measurement interval, when the Report alarm when the following damping condition is reached alarm setting is enabled.

Specifiable value

number-of-times-threshold-exceeded/interval-value

Integers from 1 to 32767 can be specified for number-of-times-threshold-exceeded and interval-value, joined with a slash (/).

If interval-value is less than number-of-times-threshold-exceeded, interval-value is treated for processing as having the same value as number-of-times-threshold-exceeded. This cannot be omitted when the value of the Damping label is Y. If the value of the Damping label is N, or the label is omitted, this specification is ignored.

Omissible

Yes (but not when the value of the Damping label is Y)

Check Value Exist subsection

If the Monitor whether the value exists alarm setting is enabled, this subsection specifies the record and values to be monitored. This subsection can be omitted, except when the Check Value Exist label is set to Y in the General subsection.

The labels that can be specified for this subsection are as follows.

Table 2‒57: Record label

Type

Description

Description

If the Monitor whether the value exists alarm setting is enabled, this shows the records for the target to be monitored.

Specifiable value

This specifies the record ID of the records to monitor, in 1 to 7 single-byte characters.

You can specify only the record ID of a multi-instance record.

For details about record IDs, see the chapter in the PFM - Agent or PFM - RM manuals that describes records.

Omissible

No

Table 2‒58: Field label

Type

Description

Description

If the Monitor whether the value exists alarm setting is enabled, this shows the record fields for the target to be monitored.

Specifiable value

This specifies the PFM - Manager name for the fields to be monitored, in 1 to 50 single-byte characters.

Omissible

No

Table 2‒59: Value label

Type

Description

Description

If the Monitor whether the value exists alarm setting is enabled, this shows the value to monitor for existence.

Specifiable value

The value that can be specified differs depending on the field value. You can specify an integer, a fractional value, or a string that is 1 to 127 bytes long and consists of double-byte and/or single-byte characters.

Control characters and (, ), [, ], <, >, =, or " cannot be specified. To specify these characters, use the wildcard character to specify the values. To use the hash mark (#) in the value to monitor for existence, specify \#. To use the backslash (\) in the value to monitor for existence immediately before a specified wildcard character, use \\.

Omissible

No

Alarm Condition Expressions subsection

This subsection specifies records and values to be monitored by alarms. This subsection can be omitted, except when the Check Value Exist label does not exist in the General subsection, or is set to N.

The labels that can be specified for this subsection are as follows.

Table 2‒60: Condition label

Type

Description

Description

Indicates the conditional expressions for monitoring by using an alarm.

Specifiable value

Conditional expressions for monitoring by using an alarm are specified in the following format:

<monitored-field><condition><abnormal-value>,<warning-value>

<monitored-field>

Specifies the PFM - Manager name of the record ID and field to be monitored, as a string from 1 to 50 single-byte characters joined by an underscore (_).

<condition>

One of the following is specified.

=: The field value is equal to the specified value

<: The field value is less than the specified value

<=: The field value is less than or equal to the specified value

>: The field value is greater than the specified value

>=: The field value is greater than or equal to the specified value

<>: The field value is not equal to the specified value

<abnormal-value>,<warning-value>

Specifies the threshold used as the standard for determining abnormal or warning alarms (values are separated by a comma (,)).

Specify an integer, a fractional value, or a string (consisting of double-byte and/or single-byte characters). The values that can be specified differ depending on the monitored field. Control characters and (, ), [, ], <, >, or = cannot be specified. When a string is specified, the string needs to be enclosed by double quotation marks ("). If the string contains tab symbols (\t), all such symbols will be replaced with spaces.

To set multiple conditions, join each condition with AND. As many as five conditional expressions can be specified together. If multiple conditional expressions are specified, they are evaluated in the order specified (starting with the expression that begins from the left). Note that if measurement values are displayed by using %CVS variables, field locations are determined in the order specified (starting with the expression that begins from the left). If an alarm definition that contains three or more conditional expressions is displayed in PFM - Web Console, these conditional expressions are listed within parentheses (()) in the priority order (the expression with the lowest priority comes first).

Example:

Definition imported by using the jpctool alarm import command: A AND B AND C

Definition displayed in PFM - Web Console: A AND ( B AND C )

When an alarm for which the conditions for the abnormal value and warning value are different (such as abnormal value < 50 and warning value <= 60) is exported, the warning value is given priority for export (or the abnormal value if the warning value does not exist). When an alarm with no abnormal value or warning value is exported, <abnormal-value> or <warning-value> are left blank.

When registered to PFM - Manager, conditional expressions are divided into abnormal conditions and warning conditions. An error will occur and registration will fail when the length of any conditional expression exceeds 749 bytes. The length of conditional expressions that can be registered with PFM - Manager can be calculated by the following formula, where n (1n5) represents the number of conditional expressions specified together using AND (1in). An error will occur if the value calculated by the following formula exceeds 749 bytes.

Length of conditional expression for abnormal values =

Length of conditional expression for warning values =

ai: The length of the ith <monitored-field>, in bytes

bi: The length of the ith <condition>, in bytes

ci: The length of the ith <abnormal-value>, in bytes. When a string is specified, the length does not include quotation marks.

di: The length of the ith <warning-value>, in bytes. When a string is specified, the length does not include quotation marks.

Omissible

No

Actions subsection

This subsection specifies the actions executed and reports displayed when an alarm event occurs. This subsection can be omitted.

The labels that can be specified for this subsection are as follows.

Table 2‒61: Report label

Type

Description

Description

Indicates the name of the displayed report when the alarm event occurs.

Specifiable value

An absolute path of the folder tree (from the Reports/ folder) that is 0 to 1,024 bytes long and consists of double-byte and/or single-byte characters.

If the name contains \ or / (except for the folder separator character), each should be entered as \\ and \/. If the label value or label itself is omitted, this specification is treated as unspecified.

Omissible

Yes

Table 2‒62: E-mail label

Type

Description

Description

Indicates the alarm event for the e-mail execution target of the action executed by the alarm.

Specifiable value

The following values can be specified.

For abnormal value execution: Abnormal

For warning value execution: Warning

For normal value execution: Normal

To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,).

The statuses are in random order, but an error will occur if the same status is specified more than once.

Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection.

Omissible

Yes

Table 2‒63: Command label

Type

Description

Description

Indicates the alarm event used as the command execution target for the action executed by alarm.

Specifiable value

The following values can be specified.

For abnormal value execution: Abnormal

For warning value execution: Warning

For normal value execution: Normal

To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,). The statuses are in random order, but an error will occur if the same status is specified more than once.

Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection.

Omissible

Yes

Table 2‒64: SNMP label

Type

Description

Description

Indicates the kind of statuses for which an alarm performs SNMP trap notification.

Specifiable value

The following values can be specified.

For abnormal value execution: Abnormal

For warning value execution: Warning

For normal value execution: Normal

To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,). The statuses are in random order, but an error will occur if the same status is specified more than once.

Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection.

Omissible

Yes

Table 2‒65: JP1 Event label

Type

Description

Description

Indicates whether JP1 event execution is set for action execution.

Specifiable value

Y or N can be specified.

When Y is specified

A JP1 event is executed for the action.

When this is omitted or N is specified

This is disabled.

If no value is specified for the Command label, this specification is ignored.

Omissible

Yes

Action Definition E-mail subsection

This subsection specifies the settings for executed actions (e-mail) when an alarm event occurs. This subsection can be omitted, except when e-mail execution is specified in the Actions subsection.

The labels and sub-subsections that can be specified for this subsection are as follows.

Table 2‒66: E-mail Address label

Type

Description

Description

Indicates the e-mail recipient.

Specifiable value

The value can be specified in 1 to 127 single-byte characters. Multiple recipients can be specified by separating each with a comma (,). In this case, the total length must be within 127 bytes.

Omissible

No

Table 2‒67: Action Handler label

Type

Description

Description

Indicates the service ID of the action handler for which e-mail is sent.

Specifiable value

The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL.

Omissible

No

Table 2‒68: Message Text sub-subsection

Type

Description

Description

Indicates the message contents sent by e-mail.

Specifiable value

A string that is 0 to 1,000 bytes long and consists of double-byte and/or single-byte characters.

In this sub-subsection, contents until the first line of the next section or subsection, or end of the file (EOF), can be set as the defined value. Note that any comments in the sub-subsection are excluded. Also, valid line return characters in the final line of the sub-subsection are excluded.

Omissible

Yes

Action Definition Command subsection

This subsection specifies settings for executed actions (command) when alarm events occur. This subsection can be omitted, except when command execution is specified in the Actions subsection, and the value of the JP1 Event label is set to N (this is ignored when the JP1 Event label is set to Y).

The labels and sub-subsections that can be specified for this subsection are as follows.

Table 2‒69: Command Name label

Type

Description

Description

Indicates the name of the command (script) executed for the action.

Specifiable value

The value can be specified in 1 to 511 single-byte characters.

When specifying this label, specify an absolute path or relative path from the current service directory when using a command (script) other than those in the following directories:

Action Handler service installation directory

Path set in the PATH environment variable

Omissible

No

Table 2‒70: Action Handler label

Type

Description

Description

Indicates the service ID of the action handler for which the command is executed.

Specifiable value

The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL.

Omissible

No

Note

Depending on the alarm action setting specified in the PFM - Web Console, the load might concentrate on the PFM - Manager host. To prevent this, open the New Alarm > Action Definitions page or the Edit > Action Definitions page, and then, in the Command field, select LOCAL for the command execution action handler. If you want actions to be triggered by alarms in a large-scale system, make sure that you select LOCAL to prevent the PFM - Manager host from being heavily loaded.

Table 2‒71: Message Text sub-subsection

Type

Description

Description

Indicates parameters to pass to executed commands.

Specifiable value

A string that is 0 to 2,047 bytes long and consists of double-byte and/or single-byte characters.

In this sub-subsection, contents until the first line of the next section or subsection, or end of the file (EOF), can be set as the defined value. Note that any comments in the sub-subsection are excluded. Also, valid line return characters in the final line of the sub-subsection are excluded.

Omissible

Yes

Action Definition JP1 subsection

This subsection specifies settings for actions (JP1 events) executed when an alarm event occurs. This subsection can be omitted, except when command execution is specified in the Actions subsection, and the JP1 Event label is set to Y.

The labels that can be specified for this subsection are as follows.

Table 2‒72: Event ID label

Type

Description

Description

Indicates the event ID sent to the JP1 event.

Specifiable value

The event ID is specified as a hexadecimal number. Values from 0 to 1fff and 7fff8000 to 7fffffff can be specified.

Omissible

No

Table 2‒73: Action Handler label

Type

Description

Description

Indicates the action handler to be executed for the JP1 event.

Specifiable value

The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL.

Omissible

No

Table 2‒74: Message label

Type

Description

Description

Indicates the message sent to the JP1 event.

Specifiable value

A string that is 0 to 1,023 bytes long and consists of double-byte and/or single-byte characters.

To issue JP1 events with the Action Handler service in version 09-00 or earlier, specify a string that is 0 to 128 bytes long and consists of double-byte and/or single-byte characters.

Omissible

Yes

Table 2‒75: Switch Alarm Level label

Type

Description

Description

Indicates whether the alarm level is converted to a JP1 event priority.

Specifiable value

Y or N can be specified.

When this is omitted or Y is specified

The action alarm level is converted to an event priority in the JP1 event.

When N is specified

This is disabled.

Omissible

Yes

Table 2‒76: Exec Logical Host label

Type

Description

Description

Indicates the name of the event server registered for the JP1 event. Specified when the event server is operating on a logical host.

Specifiable value

The value can be specified in 0 to 255 single-byte characters. If no value is specified, this is treated as being omitted.

Omissible

Yes

The following shows an example of an alarm definition file.

Example of an alarm definition file

Alarm Definition File Version=0002
Alarm Definition File Code=US_ASCII

[Alarm Data]
[[General]]
Product=T3.0
Alarm Table Name=Example
Alarm Name="CPU Usage"
Message Text="CPU is at %CVS% utilization"
Check Value Exist=N

[[Advanced Setting]]
Active Alarm=Y
Regular Alarm=N
Evaluate All Data=N
Notify State=Alarm
Monitoring Regularly=Y
#Monitoring Time=
Damping=Y
Damping Count=2/3

#[[Check Value Exist]]
#Record=
#Field=
#Value=

[[Alarm Condition Expressions]]
Condition=PI_PCT_TOTAL_PROCESSOR_TIME>90.000000,80.000000

[[Actions]]
Report="Reports/Windows/Operating System/Troubleshooting/Real-Time/CPU Usage - Top 10 Processes"
E-mail=Abnormal,Warning
Command=Abnormal
SNMP=Abnormal,Warning,Normal
JP1 Event=N

[[Action Definition E-mail]]
E-mail Address=administrator@example.com
Action Handler=PH1host01
[[[Message Text]]]
Date: %SCT
Host: %HNS

Product: %PTS
Agent: %ANS

Alarm: %AIS (%ATS)
State: %SCS

Message: %MTS
[[Action Definition Command]]
Command Name=userprogram.exe
Action Handler=LOCAL
[[[Message Text]]]
%CVS
#[[Action Definition JP1 Event]]
#Event ID=
#Action Handler=
#Message=%MTS
#Switch Alarm Level=Y
#Exec Logical Host=

Notes

This command cannot be executed concurrently.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

You can define a maximum of 250 alarms in an alarm definition file.

You can define a maximum of 250 alarms in an alarm table, including alarms that have already been defined. Even if the number of alarms in an imported alarm definition file does not exceed 250, an error results if the total count including the imported alarms will exceed 250.

If the alarm definition file contains a read-only alarm table (whose name begins with PFM), an error results; the command does not overwrite such alarm definitions even if the -y option is specified.

If the alarm definitions you import include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

If the file name you specify includes double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). Before you execute this command, check the setting of the LANG environment variable for the shell.

If PFM - Manager is installed on a logical host, execute the command on the executing node.

You can define a maximum of 250 alarms at once by using the jpctool alarm import command.

This command is useful when you define alarms on multiple servers in a large-scale system.

Note that the number of alarms that you can define at once cannot exceed 250 even if the import file contains multiple alarm tables.

An import using the following file succeeds:

Import file 1:

100 alarms are defined in alarm table A.

150 alarms are defined in alarm table B.

An import using the following file fails:

Import file 2:

200 alarms are defined in alarm table A.

150 alarms are defined in alarm table B.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

If you specify an alarm table bound to an agent that does not support the notification of state changes for each instance, a KAVE05970-E message will be output each time an alarm defined to report state changes for each instance occurs.

In the alarm definition file to be imported, 0001 or 0002 must be specified for the Alarm Definition File Version label. If another version of alarm definition file is specified, an error message will be output.

If an alarm to report state changes for each instance is defined in the alarm definition file to be imported, 0002 must be specified for the Alarm Definition File Version label in the alarm definition file.

To import an alarm definition file exported from PFM - Manager 10-10 or later to PFM - Manager 10-00 or earlier, the alarm definition file must be modified. The following table describes the required modifications of the alarm definition file:

Label to be modified

Setting before modification

Modification

Alarm Definition File Version

0002

Change the setting to 0001.

Notify State

Alarm|Instance

Delete the setting because PFM - Manager 10-00 or earlier does not support the definition of the notification of state changes for each instance.

For notes on successive stopping of the monitoring using alarms and the monitoring target system, see Notes on execution of jpctool alarm commands.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

There is an error in the contents of the alarm definition file.

11

The user canceled the processing.

13

The notification of state changes for each instance cannot be specified because the alarm table is bound to an agent that does not support the notification of state changes for each instance.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

Alarm definition file cannot be accessed, or alarm definition or updating failed because the alarm was being updated.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example

This example imports the alarmtest1.cfg alarm definition file stored in the /tmp directory:

jpctool alarm import -f /tmp/alarmtest1.cfg

jpctool alarm inactive

Format

jpctool alarm inactive     -key service-key
                           -table alarm-table-name
                           -alarm alarm-name
                           [-wait number-of-seconds]

Function

The jpctool alarm inactive command disables an enabled alarm.

The command disables alarms individually. It cannot disable all alarms in an alarm table at once.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM for which an alarm definition is to be disabled. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-table alarm-table-name

Specifies the name of the alarm table in which the alarm to be disabled is defined.

For alarm-table-name, specify a string of 1 to 64 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-alarm alarm-name

Specifies the name of the alarm to be disabled.

The command terminates normally even if the specified alarm has already been disabled.

For alarm-name, specify a string of 1 to 20 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Note

This command cannot be executed concurrently.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

If arguments of a jpctool alarm command include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

If PFM - Manager is installed on a logical host, execute the command on the executing node.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

It might take several tens of seconds until this command takes effect on the agent after this command has terminated.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent for which alarms are to be disabled has not been set up.

Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The specified alarm table or alarm is missing.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

This example disables the Disk Service Time alarm defined in the PFM UNIX Solution Alarms 8.00 monitoring template for PFM - Agent for Platform (UNIX).

jpctool alarm inactive -key UNIX -table "PFM UNIX Solution Alarms 8.00" -alarm "Disk Service Time"

Usage example 2

This example disables the alarm1 alarm that is defined in the alarmtable1 alarm table for PFM - Agent for Platform (UNIX):

jpctool alarm inactive -key UNIX -table alarmtable1 -alarm alarm1

jpctool alarm list

Format

jpctool alarm list    {-key service-key
                      [-table alarm-table-name]| -id service-ID}
                      [-wait number-of-seconds]

Function

The jpctool alarm list command displays the definitions or the bind information of alarm tables and alarms.

The following table shows what is displayed depending on the combination of the -key and -table options that is specified.

Table 2‒77: Information that is displayed depending on the combination of options that is specified

Option specifications

Information that is displayed

-key

-table

-id

S

N

N

A list of the names of the alarm tables defined in the PFM - Agent or PFM - RM specified in the -key option is displayed. The names of the individual alarms are not displayed.

S

S

N

A list of the names of the alarms defined in the alarm table specified in the -table option is displayed with the information of whether each alarm is enabled or disabled, and with a list of the names of the agents to which the alarm table is bound.

N

N

S

A list of alarm tables to which the agent is bound.

Legend:

S: Specified

N: Not specified

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM whose alarm definition information is to be displayed. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-table alarm-table-name

Specifies the name of the alarm table whose alarm definition information is to be displayed.

For alarm-table-name, specify a string of 1 to 64 bytes long, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-id service-ID

Specifies the service ID of the Agent Collector service, Remote Monitor Collector service, remote agent, or group agent. Wildcard characters (asterisks (*) and question marks (?)) cannot be used. For service-ID, specify a string of 1 to 258 bytes of characters. An error will occur if the specified service ID does not exist.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Note

This command cannot be executed concurrently.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

If arguments of a jpctool alarm command include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

If the alarm definitions you display include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent for which alarm definitions are to be displayed has not been set up.

6

The specified alarm table was not found.

11

The user canceled the processing.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Displayed information

The following table lists the information displayed when the jpctool alarm list command is executed.

Table 2‒78: Information displayed when the jpctool alarm list command is executed

No.

Displayed information

Whether or not displayed depending on option specifications

Description

-key

-key, -table

-id

1

Product ID

D

D

N

Product ID indicating the type of PFM - Agent or PFM - RM. For details about the product IDs of PFM - Agents or PFM - RM, see the list of identifiers provided in the appendix of the PFM - Agent or PFM - RM manuals.

2

DataModelVersion

N

D

N

Data model version.

3

Alarm Table Name

D

D

N

Alarm table name.

4

Alarm Name

N

D

N

Alarm name and whether the alarm is enabled or disabled:

active: Alarm is enabled

inactive: Alarm is disabled

5

The Bound Agent

N

D

N

Service ID of the agent to which the alarm table is bound.

6

Service ID

N

N

D

Service ID

7

Bound Alarm Table Name

N

N

D

Name of the bound alarm table.

Legend:

-key: Only the -key option is specified.

-key, -table: The -key and -table options are both specified.

D: Indicated information is displayed.

N: Indicated information is not displayed.

Usage example 1

This example assumes that alarm table alarmtable1 is not a monitoring template, but is to be defined for PFM - Agent for Platform (UNIX).

The following command displays a list of alarm tables defined in PFM - Agent for Platform (UNIX):

jpctool alarm list -key UNIX

Output result 1

Product ID:U
Alarm Table Name:
  alarmtable1
  PFM UNIX Solution Alarms 7.50
  PFM UNIX Solution Alarms 8.00

Usage example 2

This example assumes that the PFM UNIX Solution Alarms 8.00 monitoring template is bound to host hostA and host hostB for PFM - Agent for Platform (UNIX).

The following example displays a list of alarms and list of bound agents defined in the PFM UNIX Solution Alarms 8.00 monitoring template for PFM - Agent for Platform (UNIX).

jpctool alarm list -key UNIX -table "PFM UNIX Solution Alarms 8.00"

Output result 2

Product ID:U
DataModelVersion:6.0
Alarm Table Name:PFM UNIX Solution Alarms 8.00
Alarm Name:
  Disk Service Time   [active]
  I/O Wait Time       [active]
  Kernel CPU          [active]
  Pagescans           [active]
  Run Queue           [active]
  Swap Outs           [active]
  User CPU            [active]

The Bound Agent:
  UA1hostA
  UA1hostB

Usage example 3

This example assumes that the PFM UNIX Solution Alarms 6.70 monitoring template and user-defined alarm table alarmtable1 are bound to host hostA for PFM - Agent for Platform (UNIX).

The following example displays a list of alarms tables bound to hostA.

jpctool alarm list -id UA1hostA

Output result 3

Service ID:UA1hostA
Bound Alarm Table Name:
   alarmtable1
   PFM UNIX Solution Alarms 6.70

jpctool alarm unbind

Format

jpctool alarm unbind    -key service-key
                       {-table alarm-table-name | -all}
                        -id service-ID
                        [-wait number-of-seconds]

Function

The jpctool alarm unbind command unbinds an alarm table that is bound to an agent.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the PFM - Agent or PFM - RM from which an alarm table is to be unbound. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-table alarm-table-name

Specifies the name of the alarm table that is to be unbound.

For alarm-table-name, specify a string of 1 to 64 bytes, consisting of double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . / @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

Wildcard characters cannot be used.

-all

Unbinds all alarm tables. An error will occur if the functionality for binding multiple alarm tables is not set to be enabled. If no alarms are bound for the specified service ID, the KAVE05288-W message is displayed and the command terminates normally.

-id service-ID

Specifies the service ID of the Agent Collector service, Remote Monitor Collector service, remote agent, or group agent for the agent for which alarm tables are to be unbound. For service-ID, specify a string of 1 to 258 bytes.

This command will terminate with an error if the specified service ID belongs to an Agent Collector or Remote Monitor Collector service to which the alarm table specified by the -table option is not bound.

You can use wildcard characters to specify multiple service IDs. In this case, even when an error occurs for a given Agent Collector or Remote Monitor Collector service, processing continues for the remaining Agent Collector or Remote Monitor Collector services. Also, when errors occur from multiple Agent Collector or Remote Monitor Collector services, the return value for the last error that occurred is returned.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see F. Startup Information File (jpccomm.ini).

Notes

This command cannot be executed concurrently.

This command cancels a specified bind setting on PFM - Manager. When the bind setting is canceled, the PFM - Manager service cancels the bind setting on the relevant running agent.

Therefore, if the cancellation of an alarm table setting on the agent fails because of a failure in agent communication or for other reasons, even when this command has been executed successfully, a KAVE00448-E message is output to the common message log.

For details about the service ID, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

This command cannot be executed if any of the Name Server, Master Manager, and View Server services is stopped.

If arguments of a jpctool alarm command include double-byte characters, the LANG environment variable for the shell that is used to execute the command must be set to Japanese (Shift JIS, EUC, or UTF-8) or Simplified Chinese (GB18030 or UTF-8). In addition, the value of that LANG environment variable must be the same as the value of the LANG environment variable that is loaded when PFM - Manager starts. Before you execute this command, make sure that the LANG environment variable settings of the shell and PFM - Manager match.

If PFM - Manager is installed on a logical host, execute the command on the executing node.

When performing multiple monitoring, you cannot execute this command from the secondary PFM - Manager host.

It might take several tens of seconds until this command takes effect on the agent after this command has terminated.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running, or there is no PFM - Agent or PFM - RM that corresponds to the specified service ID.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Alternatively, the agent from which alarms are to be unbound has not been set up.

Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

The specified alarm table was not found.

11

The user canceled the processing.

12

The functionality for binding multiple alarm tables is not set to be enabled (09-00 or later).

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example 1

This example unbinds the PFM UNIX Solution Alarms 8.00 monitoring template for PFM - Agent for Platform (UNIX), from the agent with the host name host01 (service ID: UA1host01).

jpctool alarm unbind -key UNIX -table "PFM UNIX Solution Alarms 8.00" -id UA1host01

Usage example 2

This example assumes that the alarmtable1 alarm table in PFM - Agent for Platform (UNIX) has been bound to all agents whose host names begin with host.

The following command unbinds the alarmtable1 alarm table from all agents:

jpctool alarm unbind -key UNIX -table alarmtable1 -id "UA1host*"

Usage example 3

This example unbinds all alarm tables bound to the UA1hostA service.

jpctool alarm unbind -key UNIX -all -id UA1hostA

jpctool config mgrexport

Format

jpctool config mgrexport    -d export-destination-directory

Function

The jpctool config mgrexport command exports a definition information file from the PFM - Manager in a multiple-monitoring environment to a specified directory.

The definition information that can be exported is as follows:

Alarm information (alarm and action definitions)

Bind information

Report definition

Business group definition

Performance Management user account information (including the information about agent hierarchy [User Agents])

To execute this command on UNIX, the environment must allow the use of the Korn shell (ksh). For details about the applicable package, see the Release Notes for PFM - Manager.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions (When the UAC of Windows is enabled, execute this command from the administrator console.)

In UNIX:

User with root user permissions (user with uid = 0)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Argument

-d export-destination-directory

Specifies the directory to which to export the definition information.

For export-destination-directory, specify a string of 1 to 35 bytes, consisting of single-byte alphanumeric characters, single-byte space characters, and the symbols shown below.

-_#():/\

You cannot specify a relative path. Always specify an absolute path.

If the directory name that you want to specify includes spaces, enclose the entire name in double quotation marks ("). If you specify any of the following symbols, enclose it in double quotation marks (") to prevent it from being analyzed by a shell or command prompt:

( )

Be sure to specify a directory that is not the installation directory for Performance Management. Be sure also to specify an empty directory that contains no files or directories.

Notes

This command requires the version of PFM - Manager on the execution host to be 10-10 or later.

This command cannot be executed together with the start or stop command or any other setup command on the same host.

This command must be executed in a multiple-monitoring environment.

The jpctool config mgrexport command must not be executed concurrently.

Make sure that there is enough disk space available. Estimate the available disk space on the basis of the size of the disk space used for installing each product.

If an error occurs during command execution, an exported file might be left in the export-destination directory.

You cannot specify a network drive as export-destination-directory in the -d option.

You cannot specify a write-protected medium, such as a CD or DVD, as export-destination-directory in the -d option.

If many reports have been defined, it might take a long time to complete the execution of this command (when 1,000 reports are defined, it takes about 30 minutes to 1 hour.).

Do not cancel processing during command execution by pressing Ctrl+C.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

5

The command was executed in a host other than the Performance Management host.

10

The command is now running.

12

The command was not executed in a multiple-monitoring environment.

100

The Performance Management environment is invalid.

105

The current directory is not the directory in which the jpctool config mgrexport command is installed.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The specified file or directory cannot be accessed.

235

Copying of one or more files failed.

255

An unexpected error occurred.

Usage example

This example exports definition information to the /tmp/pfmexport directory.

jpctool config mgrexport -d /tmp/pfmexport

jpctool config mgrimport

Format

jpctool config mgrimport    -d import-source-directory
                            [-noprogress]

Function

The jpctool config mgrimport command imports a definition information file of the PFM - Manager in a multiple-monitoring environment from a specified directory.

The definition information that can be imported is as follows:

Alarm information (alarm and action definitions)

Bind information

Report definition

Business group definition

Performance Management user account information (including the information about agent hierarchy [User Agents])

Before importing the definition information, the jpctool config mgrimport command checks whether the definition information specified by the -d option matches that stored in the import-destination directory. For details about checking the definition information, see H. Checking the Definition Information.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions (When the UAC of Windows is enabled, execute this command from the administrator console.)

In UNIX:

User with root user permissions (user with uid = 0)

Installation directory

In Windows:

\installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-d import-source-directory

Specifies the directory that stores the definition information exported by the jpctool config mgrexport command.

For import-source-directory, specify a string of 1 to 35 bytes, consisting of single-byte alphanumeric characters, single-byte space characters, and the symbols shown below.

-_#():/\

You cannot specify a relative path. Always specify an absolute path.

If the directory name that you want to specify includes spaces, enclose the entire name in double quotation marks ("). If you specify any of the following symbols, enclose it in double quotation marks (") to prevent it from being analyzed by a shell or command prompt:

( )

-noprogress

If this option is specified, the command does not output the information on the progress of import processing.

Notes

This command requires the version of PFM - Manager on the execution host to be 10-10 or later.

This command cannot be executed together with the start or stop command or any other setup command on the same host.

This command must be executed in a multiple-monitoring environment.

The definition information specified by the -d option must match the definition information stored in the import-source directory. If discrepant definition information is found, a KAVE06142-E message will be output. If this occurs, check the error content, and then re-execute this command.

The jpctool config mgrimport command must not be executed concurrently.

Before executing this command, you must execute the jpctool config mgrexport command to export the definition information.

The versions of the PFM - Manager on the primary host and secondary host must be the same.

The PFM - Manager service on the execution host must not be running.

Before executing this command, make sure that there is enough disk space available. As a rule of thumb, each of the following drives must have as much available disk space as the space used for the definition information exported by the jpctool config mgrexport command.

Drive that includes the directory specified by the -d option

Drive that includes the PFM - Manager environment running on the execution host

If the above two drives are located on a single drive, the single drive must have space available that is two times as large as the space used for the definition information to be imported.

If an error occurs during command execution, a backup file might be left in the PFM - Manager installation directory.

If processing is canceled during command execution, the PFM - Manager environment might become invalid.

You cannot specify a write-protected medium, such as a CD or DVD, as import-source-directory in the -d option.

Do not cancel processing during command execution by pressing Ctrl+C.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

4

The PFM - Manager service on the execution host is running.

5

The command was executed in a host other than the Performance Management host.

10

The command is now running.

12

The command was not executed in a multiple-monitoring environment.

100

The Performance Management environment is invalid.

105

The current directory is not the directory in which the jpctool config mgrimport command is installed.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The specified file or directory cannot be accessed.

235

Copying of one or more files failed.

238

The definition information does not match.

239

The definition information has invalid content (the definition information has been changed after it was exported).

255

An unexpected error occurred.

Usage example

This example imports definition information from the /tmp/pfmimport directory.

jpctool config mgrimport -d /tmp/pfmimport

Output examples

The following shows an example of messages output to the standard output when the import of definition information has succeeded:

Example of standard output

KAVE06139-I Import of the multiple monitoring definitions will now start.
KAVE06143-I Import of the definitions will now start. (config=alarm definitions)
KAVE06144-I Import of the definitions ended normally. (config=alarm definitions)
KAVE06143-I Import of the definitions will now start. (config=action definitions)
KAVE06144-I Import of the definitions ended normally. (config=action definitions)
KAVE06143-I Import of the definitions will now start. (config=bind information)
KAVE06144-I Import of the definitions ended normally. (config=bind information)
KAVE06143-I Import of the definitions will now start. (config=report definitions)
KAVE06144-I Import of the definitions ended normally. (config=report definitions)
KAVE06143-I Import of the definitions will now start. (config=tenant group definitions)
KAVE06144-I Import of the definitions ended normally. (config=tenant group definitions)
KAVE06143-I Import of the definitions will now start. (config=PFM user account information)
KAVE06144-I Import of the definitions ended normally. (config=PFM user account information)
KAVE06140-I Import of the multiple monitoring definitions ended normally.

The following shows an example of messages output to the standard output when the import of definition information failed because of a discrepancy in definition information:

Example of standard output

KAVE06142-E The specified definition differs from the PFM - Manager definition. (Configure the health check function)
KAVE06142-E The specified definition differs from the PFM - Manager definition. (jpccomm.ini, section=Common Section, label=Multiple Alarm Table Bind)
KAVE06142-E The specified definition differs from the PFM - Manager definition. (HealthCheck, Property=Detail Records->PD->Log)

jpctool config sync

Format

jpctool  config  sync       [-noprogress]

Function

The jpctool config sync command synchronizes configuration information between the PFM - Manager host and PFM - Agent and PFM - RM hosts when definition information is restored by the PFM - Manager host. The configuration information that is synchronized is as follows:

Service node location information

Information on the locations, such as IP address and port number, of the PFM services on the PFM - Agent and PFM - RM hosts

Alarm information

Information on the alarms that are bound to the PFM - Agent and PFM - RM hosts

Action information

Information on the actions that are to be executed when the alarms bound to the PFM - Agent and PFM - RM hosts are issued

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions (When the UAC of Windows is enabled, execute this command from the administrator console.)

In UNIX:

User with root user permissions (user with uid = 0)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Argument

-noprogress

If this option is specified, the command does not output the information on the progress of synchronization processing.

Output of synchronization result file

When the jpctool config sync command terminates, the command outputs a CSV-format synchronization result file for every host and service for which synchronization has been done. The following table overviews the synchronization result file.

Table 2‒79: Overview of the synchronization result file

Item

OS

Description

File name

--

syncresult.csv

File path

Windows

When PFM - Manager is a physical host

installation-folder\log

When PFM - Manager is a logical host

environment-directory\jp1pc\log

UNIX

When PFM - Manager is a physical host

/opt/jp1pc/log

When PFM - Manager is a logical host

environment-directory/jp1pc/log

Permission and owner

Windows

When PFM - Manager is a physical host

Permissions for installation-folder\log are inherited.

When PFM - Manager is a logical host

Permissions for environment-directory\jp1pc\log are inherited.

UNIX

666 [rw-rw-rw-]

owner/group:

Other than AIX

root(0)/sys(3)

AIX

root(0)/system(0)

Creation timing

--

A new file is created each time the command is executed.#

File size

--

Less than 1 megabyte

#

If a synchronization result file already exists, the existing file is discarded.

Output example of synchronization result file

The following shows an output example of a synchronization result file:

DateTime=YYYY/MM/DD HH:MM:SS
Hostname,Service ID,Sync Result,Message
hostA,0A1hostA,Success,
hostA,0S1hostA,Success,
hostA,PH1hostA,Success,
hostB,PH1hostB,Failure,Unknown service
hostB,TA1hostB,Failure,Unknown service
hostB,TS1hostB,Failure,Unknown service
hostC,7A1inst1[hostC],Failure,Host not available
hostC,7A1inst1[All@hostC],Failure,Host not available
hostC,7A1inst1[target1@hostC],Failure,Host not available
hostC,7A1inst1[target2@hostC],Failure,Host not available
hostC,7S1inst1[hostC],Failure,Host not available
hostC,PH1hostC,Failure,Host not available
hostC,TA1hostC,Failure,Host not available
hostC,TS1hostC,Failure,Host not available

The following table describes the details of the output content of the synchronization result file.

Table 2‒80: Output content of notification result file

Item

Output format

Output content

Output position

Execution date and time

DateTime=YYYY/MM/DD

HH:MM:SS

(YYYY = year, MM = month, DD = day, HH = hour, MM = minute, SS = second)

Outputs the date and time when the command processing started in the set time zone.

First line

Label

HostName,Service ID,Sync Result,Message

Outputs the labels shown on the left.

Second line

Information on synchronization result for each service

host-name,service-ID,

synchronization-result,

reason-message

host-name

Host name of the relevant service

service-ID#

Service ID of the relevant service

For the output contents of synchronization results and reason messages, see the table below.

Third line and after

(This set of information is output as many times as the number of the services for which synchronization was executed.)

Legend:

: Single-byte space

#

If the synchronization processing for a host fails because of a communication error, this command outputs, to said host, as many result records as the number of the services recognized by the PFM - Manager host. In each record, not null characters but a service ID is output under the Service ID label.

The following table lists the messages output under the Sync Result and Message labels in the synchronization result file when synchronization has succeeded or failed. The following table also describes the corrective action to be taken for each failure message.

Table 2‒81: Output contents of synchronization result file and corrective actions

No.

Synchronization result

Output content

Corrective action

Sync Result

Message

1

Synchronization succeeded.

Success

--

--

2

Synchronization with Action Handler service failed because PFM - Base version was earlier than 10-00-10.

Failure

Incompatible version

Restart the Action Handler service indicated in the output message.

3

Synchronization with a target service failed because the target service had been deleted.

Failure

Service not exist

To adjust the environment of PFM - Agent and PFM - RM hosts to the environment recognized by PFM - Manager host, create and start the service indicated in the output message on the PFM - Agent and PFM - RM hosts.

To adjust the PFM - Agent and PFM - RM hosts to the environment recognized by PFM - Manager host to the actual environment of PFM - Agent and PFM - RM hosts, perform the following steps:

If alarm tables are bound to the target service, unbind all the alarm tables with the jpctool alarm unbind command or by an operation from PFM - Web Console.

If an alarm definition specifies the target service as an action execution service, change the specification of the action execution service in the alarm definition with the jpctool alarm import command or by an operation from PFM - Web Console.

Execute the jpctool service delete command on the PFM - Manager host.

4

Synchronization with an added service failed because the added service was not recognized by PFM - Manager.

Failure

Unknown service

To adjust the environment of PFM - Agent and PFM - RM hosts to the environment recognized by PFM - Manager host, delete the service indicated in the output message from the PFM - Agent and PFM - RM hosts.

To adjust the PFM - Agent and PFM - RM hosts to the environment recognized by PFM - Manager host to the actual environment of PFM - Agent and PFM - RM hosts, restart the service indicated in the output message.

5

Synchronization with a target host failed because the target host could not communicate.

Failure

Host not available

To adjust the environment of PFM - Agent and PFM - RM hosts to the environment recognized by PFM - Manager host, restart all services on the host indicated in the output message.

To adjust the PFM - Agent and PFM - RM hosts to the environment recognized by PFM - Manager host to the actual environment of PFM - Agent and PFM - RM hosts, perform the following steps:

If alarm tables are bound to the target service, unbind all the alarm tables with the jpctool alarm unbind command or by an operation from PFM - Web Console.

If an alarm definition specifies the target service as an action execution service, change the specification of the action execution service in the alarm definition with the jpctool alarm import command or by an operation from PFM - Web Console.

Execute the jpctool service delete command on the PFM - Manager host.

6

Synchronization with a target failed for reasons other than those, such as communication error, described in items 2 to 5.

Failure

Synchronization failure

Restart the host or service indicated in the output message.

7

Synchronization result is unknown because the target service did not respond even though it could communicate.

Failure

No response

Restart the service indicated in the output message.

8

Synchronization with a PFM - Agent or PFM - RM host failed because said host was not recognized by the PFM - Manager host when configuration information was restored.

--

--

To identify a host that is not recognized by the PFM - Manager host but exists in the actual environment, compare your own list of PFM - Agent and PFM - RM hosts with the synchronization result files output by the command. Then, restart all services on the identified host.

Legend:

--: None

Notes

This command will terminate normally if it is executed when there are no PFM - Agent and PFM - RM hosts connected to the PFM - Manager host and the PFM - Manager recognizes no services.

If the Name Server or Master Manager service stops while this command is being executed, or if execution of this command is interrupted by a signal or by pressing Ctrl+C, execution of this command stops. If execution of this command stops in the middle of synchronization processing, re-execute this command.

The jpctool config sync command must not be executed concurrently with this command.

The synchronization processing might take a long time if the system environment is large.

A rough rule of thumb for synchronization processing time is 14 seconds for each of the PFM - Agent and PFM - RM hosts that are monitored by the PFM - Manager host.

Provided that the PFM - Manager host is monitoring a total of 1,024 PFM - Agent and PFM - RM hosts (the maximum allowable number of monitored hosts in a system), the rough estimate of total processing time is about 240 minutes.

You can interrupt execution of this command by pressing Ctrl+C or by other methods. If execution of this command is interrupted, a KAVE05227-E message will be output.

Return values

0

The command terminated normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

5

PFM - Manager has not been installed.

12

The command is now running.

100

The Performance Management environment is invalid.

101

Some or all the services, including the Name Server service, required to execute the command are not running.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The specified file or directory cannot be accessed.

222

A communication processing error occurred.

237

Synchronization of one or more items of service information failed.

255

An unexpected error occurred.

Usage example

This example synchronizes configuration information between the PFM - Manager host and PFM - Agent and PFM - RM hosts.

jpctool config sync

Output example

The following shows an example of messages output to the standard output when the synchronization between the PFM - Manager host and PFM - Agent and PFM - RM hosts has failed:

Example of standard output

KAVE06117-I Synchronization of configuration information will now start.
[50/50]
KAVE06121-W A service exists that could not be synchronized because it does not support synchronization.
KAVE06132-I Evaluation of the synchronization results will now start.
KAVE06133-I Evaluation of the synchronization results ended normally.
KAVE06118-I Synchronization of configuration information ended normally.

jpctool db backup

Format

jpctool db backup   -id service-ID
                   [-host host-name]
                   [-lhost logical-host-name]
                   [-d directory]
                   [-partial startday,endday[,[dbid]
                       [,[recname][,[drawer]]]]]
                   [-direct]
                   [-alone]

Function

The jpctool db backup command creates a backup file of the data stored in the Master Store, Agent Store, or Remote Monitor Store service database.

The default execution of this command creates the following files:

For full backup

When backing up the data stored in the Master Store service database

Windows: installation-folder\mgr\store\backup\generation-number#1\database-ID#2.DB

UNIX: /opt/jp1pc/mgr/store/backup/generation-number#1/database-ID#2.DB

When backing up the data stored in the Agent Store service database when Store version 1.0 is used

Windows: installation-folder\xxxx#3\store[\instance-name]#4\backup\generation-number#1\database-ID#2.DB

UNIX: /opt/jp1pc/xxxx#3/store[/instance-name]#4/backup/generation-number#1/database-ID#2.DB

When backing up the data stored in the Agent Store and Remote Monitor Store service database when Store version 2.0 is used

Windows: Under installation-folder\xxxx#3\store[\instance-name]#4\backup\generation-number#1, the following backup files are created:

STPI\summary-separator\year\month-day\generation-number#5\record-name.DB#6

STPI\summary-separator\year\month-day\generation-number#5\record-name.IDX#6

STPD\year\month-day\generation-number#5\record-name.DB#6

STPD\year\month-day\generation-number#5\record-name.IDX#6

STPL\year\month-day\generation-number#5\record-name.DB#6

STPL\year\month-day\generation-number#5\record-name.IDX#6

STAM.DB

STAM.IDX

STDC.DB

STDC.IDX

STDM.DB

STDM.IDX

STPA.DB

STPA.IDX

STPH.DB

STPH.IDX

STPT.DB

STPT.IDX

jpcsto.ini

STDICT.DAT

STRULES.DAT

UNIX: Under /opt/jp1pc/xxxx#3/store[/instance-name]#4/backup/generation-number#1, the following backup files are created:

STPI/summary-separator/year/month-day/generation-number#5/record-name.DB#6

STPI/summary-separator/year/month-day/generation-number#5/record-name.IDX#6

STPD/year/month-day/generation-number#5/record-name.DB#6

STPD/year/month-day/generation-number#5/record-name.IDX#6

STPL/year/month-day/generation-number#5/record-name.DB#6

STPL/year/month-day/generation-number#5/record-name.IDX#6

STAM.DB

STAM.IDX

STDC.DB

STDC.IDX

STDM.DB

STDM.IDX

STPA.DB

STPA.IDX

STPH.DB

STPH.IDX

STPT.DB

STPT.IDX

jpcsto.ini

STDICT.DAT

STRULES.DAT

#1

Generation numbers are assigned sequentially beginning with 01. The maximum generation number is the value specified in Backup Save in the jpcsto.ini file. The default maximum generation number is 05. However, when you directly specify the backup directory, directories with generation numbers are not created. The backup data is written under the specified directory.

#2

The following are the specifiable database IDs:

PI: PI record-type Agent Store and Remote Monitor Store service database

PD: PD record-type Agent Store and Remote Monitor Store service database

PL: PL record-type Agent Store and Remote Monitor Store service database

PA: Master Store service database

#3

xxxx denotes the service key of a PFM - Agent or PFM - RM. For details about the service key, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

#4

A directory with instance names is for a PFM - Agent or PFM - RM that monitors an application program that can start a set of multiple services at the same host.

#5

Either [001] or [002] is assigned.

#6

The record-name item indicates PI_LOGD, PD_PDI, PL_MESS, or other Agent record name.

For partial backup (Store version 2.0 only)

When backing up a part of the data stored in the Agent Store and Remote Monitor Store service database

Backup files are created according to the records being collected and the -partial option specification.

Windows: Under installation-folder\xxxx#1\store\instance-name#2\partial, the following backup files are created:

STPI\summary-separator\year\month-day\generation-number#3\record-name.DB#4

STPI\summary-separator\year\month-day\generation-number#3\record-name.IDX#4

STPD\year\month-day\generation-number#3\record-name.DB#4

STPD\year\month-day\generation-number#3\record-name.IDX#4

STPL\year\month-day\generation-number#3\record-name.DB#4

STPL\year\month-day\generation-number#3\record-name.IDX#4

STAM.DB

STAM.IDX

STDC.DB

STDC.IDX

STDM.DB

STDM.IDX

STPA.DB

STPA.IDX

STPH.DB

STPH.IDX

STPT.DB

STPT.IDX

jpcsto.ini

STDICT.DAT

STRULES.DAT

UNIX: Under /opt/jp1pc/xxxx#1/store/instance-name#2/partial, the following backup files are created:

STPI/summary-separator/year/month-day/generation-number#3/record-name.DB#4

STPI/summary-separator/year/month-day/generation-number#3/record-name.IDX#4

STPD/year/month-day/generation-number#3/record-name.DB#4

STPD/year/month-day/generation-number#3/record-name.IDX#4

STPL/year/month-day/generation-number#3/record-name.DB#4

STPL/year/month-day/generation-number#3/record-name.IDX#4

STAM.DB

STAM.IDX

STDC.DB

STDC.IDX

STDM.DB

STDM.IDX

STPA.DB

STPA.IDX

STPH.DB

STPH.IDX

STPT.DB

STPT.IDX

jpcsto.ini

STDICT.DAT

STRULES.DAT

#1

xxxx denotes the service key of a PFM - Agent or PFM - RM. For details about the service key, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

#2

A directory with instance names is for a PFM - Agent or PFM - RM that monitors an application program that can start a set of multiple services at the same host.

#3

Either [001] or [002] is assigned.

#4

The record-name item indicates PI_LOGD, PD_PDI, PL_MESS, or other Agent record name.

Hosts that can execute the command

PFM - Manager

PFM - Agent#1

PFM - Base#2

PFM - RM#1

#1

The command can be executed only when the -alone or -direct option is specified.

#2

The command can be executed only when the -direct option is specified.

Execution permission

In Windows:

User with Administrators permissions

User with Backup Operators permission

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-id service-ID

Specifies the service ID (whose second character is S) of the Master Store, Agent Store, or Remote Monitor Store service. For service-ID, specify a string of 1 to 258 bytes.

You can use a wildcard character to specify multiple service IDs. Note, however, that when you specify the -d option, you cannot use a wildcard character. When multiple service IDs are specified, if a service results in an error, processing continues for the other services. If errors occur on multiple services, the command returns a value for the last error that occurred.

-host host-name

Specifies a host name if data is to be backed up from a specific host. For host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this option, the local host is assumed.

You can use a wildcard character to specify multiple host names.

When you specify multiple host names, the wildcard character * represents any character string consisting of at least one character and ? represents any single character. Note, however, that when you specify the -d option, you cannot use a wildcard character.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in a logical host environment, not in the physical host environment. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

-d directory

Specifies the backup destination directory. Specify a directory that can be accessed with the following permission:

In Windows: System account

In UNIX: Root user permission

For the directory when the Store version is 1.0, use a maximum of 127 bytes to specify the full path or a relative path. When the Store version is 2.0, use a maximum of 214 bytes to specify the full path or a relative path. When a relative path is specified, it must be within 214 bytes even when converted to an absolute path. When you specify a relative path, the base directory is the environment directory of the specified Store service.

To use this option, only one Store service on the local host can be specified. Therefore, you cannot use wildcard characters for service-ID and host-name. Unlike using the BackupDir label of the jpcsto.ini file to specify a backup directory, directories with generation numbers are not created. Backup data is written under the specified directory.

Any existing file in the specified directory will be overwritten.

-partial startday,endday[,[dbid][,[recname][,[drawer]]]]

Executes partial backup only when the Store version of the specified Store service is 2.0.

startday: Specifies the start day for the backup data as a number of days before the current date in GMT.

endday: Specifies the end day for the backup data as a number of days before the current date in GMT.

dbid: Specifies the database ID. When this item is omitted, all the databases are selected.

recname: Specifies the record type. When this item is omitted, all record types are selected.

drawer: Specifies the summary type. When this item is omitted, all summary types are selected. The following table lists the values that can be specified for the summary type.

Specifiable value

Description

Minute

Specifies a minute-by-minute record.

Hour

Specifies a hourly record.

Day

Specifies a daily record.

Week

Specifies a weekly record.

Month

Specifies a monthly record.

Year

Specifies a yearly record.

The following shows specification examples for the -partial option:

Example 1: Performing a partial backup of records of all record types from three days ago to one day ago

-partial 3,1,

Example 2: Performing a partial backup of the PD_PDI record in the PD database from three days ago to one day ago

-partial 3,1,PD,PDI

Example 3: Performing a partial backup of monthly records in the PI database from three days ago to one day ago

-partial 3,1,PI,,Month

-direct

Specifies that backup processing on the Master Store, Agent Store, or Remote Monitor Store service database is to be executed without going through the Master Manager service. When this option is specified, the command can be executed on a PFM - Agent or PFM - RM host (other than the PFM - Manager host). However, the Name Server and Master Manager services must be running. Additionally, the host where the command is executed must be able to communicate directly with the target Store service.

This option cannot be specified together with the -alone option.

-alone

Specifies that backup processing on the Master Store, Agent Store, or Remote Monitor Store service database is to be executed on the local host. The command cannot execute backup processing on the Master Store, Agent Store, or Remote Monitor Store service database located at a remote host. When this option is specified, the command can execute backup processing even if PFM - Manager is not running. The command can be executed at a PFM - Agent or PFM - RM host (other than the PFM - Manager host).

This option cannot be specified together with the -host or -direct option.

Disk space required to execute this command

This command creates a temporary file during execution. For the amount of disk space that is required to execute this command, see the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

About deletion of unnecessary backup data

The following describes which directories and files you can delete when deleting backup data that is no longer needed.

Note that the following description applies in an environment in which backup data is saved in the system-managed backup directory for the Store database (that is, the -d option is not specified). In an environment in which backup data is saved in a user directory (specified by the -d option), all backup data, including that directory, can be deleted.

For full backup:

Master Store service backup data that can be deleted

Windows: Folders and files under installation-folder\mgr\store\backup\generation-number\

UNIX: Directories and files under /opt/jp1pc/mgr/store/backup/generation-number/

Agent Store service backup data that can be deleted if the Store version is 1.0

Note that this description assumes that the Store database's default backup directory that was set initially has not been changed. If the default backup directory has been changed by using the jpcconf db define command, replace the path before the backup directory with the path of the new default backup directory.

Windows: Folders and files under installation-folder\service-key\store[\instance-name]\backup\generation-number\

UNIX: Directories and files under /opt/jp1pc/service-key/store[/instance-name]/backup/generation-number/

Agent Store and Remote Monitor Store service backup data that can be deleted if the Store version is 2.0

Note that this description assumes that the Store database's default backup directory that was set initially has not been changed. If the default backup directory has been changed by using the jpcconf db define command, replace the path before the backup directory with the path of the new default backup directory.

Windows: Folders and files under installation-folder\service-key\store[\instance-name]\backup\generation-number\

UNIX: Directories and files under /opt/jp1pc/service-key/store[/instance-name]/backup/generation-number/

Partial backup (available only when the Store version is 2.0)

Agent Store and Remote Monitor Store services backup data that can be deleted

Note that this description assumes that the Store database's default backup directory that was set initially has not been changed. If the default backup directory has been changed by using the jpcconf db define command, replace the path before the partial directory with the path of the new default backup directory.

Windows: Folders and files under installation-folder\service-key\store[\instance-name]\partial\

UNIX: Directories and files under /opt/jp1pc/service-key/store[/instance-name]/partial/

Notes

Arguments must be specified in the order that they appear in the description. Otherwise, they will not be recognized correctly.

This command cannot be executed in the following cases:

The Name Server service, Master Manager service, or the specified Master Store service, Agent Store, or Remote Monitor Store service is stopped.

The data in the database of the specified Master Store, Agent Store, or Remote Monitor Store service is currently being backed up.

The data in the database of the specified Master Store, Agent Store, or Remote Monitor Store service is currently being exported.

If you execute multiple instances of the jpctool db backup or jpctool db dump command on separate hosts concurrently, make sure that you specify the -direct or -alone option. To execute backup or export processing more than once, make sure that the current command's processing is completed before executing the next command.

If you execute the jpctool db backup command without specifying the -direct or -alone option, do so on a single host, rather than on multiple hosts.

When you specify service-ID (for the -id option) or host-name (for the -host option) in the jpctool db backup command, you can use wildcard characters. You can execute backup or export processing concurrently on multiple agents by using wildcard characters in the service-ID or -host option.

Example: Execute the jpctool db backup command on multiple agents

This example creates a backup file for all agents on PFM - Agent for Platform (Windows):

jpctool db backup -id "TS*" -host "*"

If the volume of data to be backed up is large, backup processing may take some time.

A historical report cannot be displayed in PFM - Web Console for an Agent Store or Remote Monitor Store service while it is being backed up. Request display of the historical report again after backup processing is completed.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

When you use the -d option to specify a backup directory, do not use the same backup directory for different service keys or different instances, and do not specify the import directory. If you do so, the backup data may be damaged.

Before you execute this command on a PFM - Agent or PFM - RM host, check whether the option for restricting remote operation from Agent hosts is enabled on the PFM - Manager host. If that option is enabled, you can back up only data on the local host. If you specify a remote host by using the -host option, the command fails.

An attempt to execute the jpctool db backup command for the Master Store, Agent Store, or Remote Monitor Store service might fail while one of the following commands and operations is being processed for that service:

jpctool db backup

jpctool db dump

jpctool db clear

jpctool db import

jpctool db restore

Operation to store data of the Agent Store service or the Remote Monitor Store service

Operation to display a historical report

If the jpctool db backup command fails in the above situation, re-execute the command.

This command cannot be executed between hosts that use different types of the Internet protocol.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

One or more of the specified services is not active.

5

PFM - Manager has not been installed.

7

The specified service ID does not belong to an Agent Store service, Remote Monitor Store service, or Master Store service.

12

At least one of the specified services does not support the function (when the -partial or -d option has been specified).

100

The Performance Management environment is invalid.

101

The Name Server service, Master Manager service, Master Store service, or the operation target service is not active.

102

The specified logical host name has not been set up.

104

The specified Master Store, Agent Store, or Remote Monitor Store service is engaged in backup or export processing.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A backup file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

223

A communication processing timeout error occurred.

255

An unexpected error occurred.

Usage example 1

This example backs up all data from the host02 host:

jpctool db backup -id ?S* -host host02

Usage example 2

This example backs up all data from the agt01 host in a logical host environment (host name: jp1-ha1):

jpctool db backup -id ?S* -host agt01 -lhost jp1-ha1

Usage example 3

The following examples execute the command with -alone and -direct specified at the lhost02 host in the logical environment in PFM - Agent for Platform (Windows):

jpctool db backup -id OS* -lhost lhost02  -alone

jpctool db backup -id OS* -lhost lhost02  -direct

Usage example 4

This example backs up the data of all Agent Store and Remote Monitor Store services on the jp1-ha1 logical host when PFM - Agent or PFM - RM is in a logical host environment (host name: jp1-ha1) and PFM - Manager is on the physical host:

jpctool db backup -id "?S*" -host jp1-ha1

Usage example 5

This example backs up the data of all Agent Store and Remote Monitor Store services on the jp1-ha1 logical host when PFM - Agent or PFM - RM is on a logical host (host name: jp1-ha1) and PFM - Manager is on a logical host (host name: jp1-ha2):

jpctool db backup -id "?S*" -host jp1-ha1 -lhost jp1-ha2

jpctool db clear

Format

jpctool db clear   -id service-ID
                  [-host host-name]
                  [-lhost logical-host-name]
                   -dbid database-ID

Function

The jpctool db clear command erases the data stored in the Master Store, Agent Store, or Remote Monitor Store service database.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

User with Backup Operators permission

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-id service-ID

Specifies the service ID (whose second character is S) of the Master Store, Agent Store, or Remote Monitor Store service. For service-ID, specify a string of 1 to 258 bytes. You can use wildcard characters to specify multiple service IDs. In this case, processing of the remaining services continues even if an error occurs on one service. If errors occur on multiple services, the command returns a value for the last error that occurred.

-host host-name

Specifies a host name if data is to be deleted from a specific host. For host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this option, the local host is assumed.

You can use a wildcard character to specify multiple host names.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in a logical host environment, not in the physical host environment. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

-dbid database-ID

Specifies the ID of the database from which the data is to be erased. The following shows the specifiable database IDs:

PI: PI record-type Agent Store and Remote Monitor Store service database

PD: PD record-type Agent Store and Remote Monitor Store service database

PL: PL record-type Agent Store and Remote Monitor Store service database

PA: Master Store service database

You can use a wildcard character to specify multiple database IDs.

Notes

Arguments must be specified in the order that they appear in the description. Otherwise, they will not be recognized correctly.

This command cannot be executed if the Name Server service, Master Manager service, or the specified Master Store, Agent Store, or Remote Monitor Store service is not running.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

One or more of the specified services is not active.

5

PFM - Manager has not been installed.

7

The specified service ID does not match Agent Store, Remote Monitor Store, or Master Store service.

100

The Performance Management environment is invalid.

101

Name Server service, Master Manager service, Master Store service, or the operation target service is not active.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A backup file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

255

An unexpected error occurred.

Usage example 1

This example erases all data from the host01 host:

jpctool db clear -id ?S* -host host01 -dbid *

Usage example 2

This example erases the data of the PI record type of PFM - Agent for Platform (UNIX) from the host03 host. The following command assumes that the PFM - Manager to which PFM - Agent for Platform (UNIX) belongs is in a logical host environment (host01):

jpctool db clear -id "US*" -host host03 -lhost host01 -dbid PI

Usage example 3

This example erases the data of all the Agent Store and Remote Monitor Store services on the jp1-ha1 logical host when PFM - Agent or PFM - RM is in a logical host environment (host name: jp1-ha1) and PFM - Manager is on the physical host:

jpctool db clear -id "?S*" -host jp1-ha1 -dbid *

Usage example 4

This example erases the data of all the Agent Store and Remote Monitor Store services on the jp1-ha1 logical host when PFM - Agent or PFM - RM is on a logical host (host name: jp1-ha1) and PFM - Manager is on a logical host (host name: jp1-ha2):

jpctool db clear -id "?S*" -host jp1-ha1 -lhost jp1-ha2 -dbid *

jpctool db dmconvert

Format

jpctool db dmconvert    -d backup-directory

Function

The jpctool db dmconvert command converts the data model for backup data. When a conversion is performed, the data model version for the backup data becomes the same version as that of the currently installed instance of PFM - Agent or PFM - RM.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-d backup-directory

Specifies the name of the backup directory containing the backup data for which the data model version is to be converted. You cannot specify the following characters in the backup directory name:

; , * ? ' " < > |

Use 1 to 214 bytes (but none of the above characters) to specify a relative path or the full path. When you specify a relative path, specify the path from the directory that is the current directory when the command is executed.

Notes

You cannot downgrade the data model version.

You can execute the jpctool db dmconvert command only when the Store version of the backup data to be specified in the -d option is 2.0.

An error occurs if the agent with the same product ID as the backup data is not installed.

An error will occur when the data model version of the backup data is later than the data model version of the installed agent.

The target backup data must be data that was backed up when the Store version was 2.0.

When this command is executed, twice as much free disk space as the amount of data converted is temporarily required in the directory specified for jpctool db dmconvert -d.

Use the total size of the database stored in the directory specified for the -d option.

For example, if the total size of the database in the directory specified for the -d option is 100 MB, secure at least 200 MB of free disk space, and then execute this command.

If the jpctool db dmconvert command fails with a KAVE05849-E message, use the procedure described below to correct the failure.

Note that the jpctool db dmconvert command backs up data internally. You might need to delete the backup data or need to perform restoration from the backup data, according to the situation.

The following table lists the files that the jpctool db dmconvert command backs up, and the locations in which the backup files are stored.

In Windows, please replace a slash (/) with a backslash (\).

Type

Backup source

Backup destination

Store database

backup-directory

backup-directory/cvtwork

Definition file

backup-directory/jpcsto.ini

backup-directory/jpcsto.ini.bak

backup-directory/STDICT.DAT

backup-directory/STDICT.DAT.bak

backup-directory/STRULES.DAT

backup-directory/STRULES.DAT.bak

Before performing the procedure described below, check whether a KAVE05801-I message has been output.

If a KAVE05801-I message has been output:

Database conversion has been completed.

Unnecessary backup data might remain at the backup destination.

Check the backup destination, and delete data, if any.

If a KAVE05801-I message has not been output:

Database conversion was not completed.

Use the following procedure to troubleshoot the problem:

Check the message that was output immediately before the above message, and remove the cause of the error.

Restore the data from the backup data as described below. If there is no backup data, you do not need to perform restoration.

Before you start restoration, do not use any Performance Management commands or services to manipulate or view the Store database in the backup directory.

How to restore the Store database differs depending on whether a KAVE05800-I message has been output. Check whether a KAVE05800-I message has been output.

If a KAVE05800-I message has been output:

Delete the backup-source STPI, STPD, and STPL directories, and then copy all backup files and directories back to their original locations.

Any remaining source files must be overwritten with the corresponding backup files.

If a KAVE05800-I message has not been output:

Copy all backup files and directories back to their original locations, without deleting the backup-source STPI, STPD, and STPL directories.

Any remaining source files and directories must be overwritten with the corresponding backup files and directories.

For definition files, backup files are saved with different names. After copying files and directories, delete these definition files, and then restore these definition files by renaming their backup files.

Re-execute the command.

Return values

0

The command ended normally.

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

4

The Store service is already running. Alternatively, another command is accessing the Store directory.

5

The specified PFM - Agent or PFM - RM has not been installed.

100

The Performance Management environment is invalid.

102

The specified logical host or instance is not set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The file or directory cannot be accessed.

230

Execution of an internal command failed.

255

An unexpected error occurred.

jpctool db dump

Format

jpctool db dump     -id service-ID
                   [-host host-name]
                   [-lhost logical-host-name]
                    -stime start-date-and-time
                    -etime end-date-and-time
                    -f export-file-name
                    -dbid database-ID
                    -rec record-type
                   [-localtime]
                   [-proxy {y|n}]
                   [-direct]
                   [-alone]

Function

The jpctool db dump command exports data stored in the Master Store, Agent Store, or Remote Monitor Store service database to a text file. You execute an export for each database individually.

The default execution of this command creates the export file in the following dump directory:

When data stored in the Master Store service database is exported:

Windows: installation-folder\mgr\store\dump\

UNIX: /opt/jp1pc/mgr/store/dump/

When data stored in the Agent Store and Remote Monitor Store service database is exported:

Windows: installation-folder\xxxx#1\store[\instance-name]#2\dump\

UNIX: /opt/jp1pc/xxxx#1/store[/instance-name]#2/dump/

#1

xxxx denotes the service key of a PFM - Agent or PFM - RM. For details about the service key, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

#2

A directory with instance names is for a PFM - Agent or PFM - RM that monitors an application program that can start a set of multiple services at the same host.

The export file is created using the file name specified in the export-file-name option.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

None

In UNIX:

None

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-id service-ID

Specifies the service ID (whose second character is S) of the Master Store, Agent Store, or Remote Monitor Store service. For service-ID, specify a string of 1 to 258 bytes.

You can use a wildcard character to specify multiple service IDs. In this case, processing of the remaining services continues even if an error occurs on one service. If errors occur on multiple services, the command returns a value for the last error that occurred.

-host host-name

Specifies the name of the host where the Master Store, Agent Store, or Remote Monitor Store service is running. You use this argument to export data from a specific host. For host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. An export data file is created on the host specified in this option. If you omit this option, the local host is assumed.

You can use a wildcard character to specify multiple host name.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in a logical host environment, not in the physical host environment. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

-stime start-date-and-time

Specifies the start date and time of the data that is to be exported, in the format YYYY/MM/DD hh:mm:

YYYY

Year, in the range 1970 to 2035.

MM

Month, in the range 01 to 12.

DD

Date, in the range 01 to 31.

hh

Hour, in the range 00 to 23.

mm

Minute, in the range 00 to 59.

The permitted range for date and time is from 1970/01/01 00:00 to 2035/12/31 23:59 GMT. If the -localtime option is omitted, the specified value is assumed to be GMT, in which case the permitted value range is from 1970/01/01 00:00 to 2035/12/31 23:59. If the -localtime option is specified, the specified local date and time must be within the equivalent GMT value range. For example, if the local time is Japan Standard time (GMT + 9), the permitted value range is from 1970/01/01 09:00 to 2036/01/01 08:59.

Make sure that the specified start time precedes the specified end time.

-etime end-date-and-time

Specifies the end date and time of the data that is to be exported, in the format YYYY/MM/DD hh:mm:

YYYY

Year, in the range 1970 to 2035.

MM

Month, in the range 01 to 12.

DD

Date, in the range 01 to 31.

hh

Hour, in the range 00 to 23.

mm

Minute, in the range 00 to 59.

The permitted range for date and time is from 1970/01/01 00:00 to 2035/12/31 23:59 GMT. If the -localtime option is omitted, the specified value is assumed to be GMT, in which case the permitted value range is from 1970/01/01 00:00 to 2035/12/31 23:59. If the -localtime option is specified, the specified local date and time must be within the equivalent GMT value range. For example, if the local time is Japan Standard time (GMT + 9), the permitted value range is from 1970/01/01 09:00 to 2036/01/01 08:59.

Make sure that the specified end time is subsequent to the specified start time.

-f export-file-name

Specifies the name of the export file. For export-file-name, specify a string of 1 to 31 bytes, consisting of alphanumeric characters and symbols (not including the directory name). However, the following symbols and the space cannot be specified:

/ \ : ; , * ? ' " < > |

If you specify any of the following symbols, you must enclose it in double quotation marks (") in order to avoid it from being analyzed by the shell or the command prompt:

& ^ ( ) `

If a file with the specified name already exists, it will be overwritten.

-dbid database-ID

Specifies the ID of the database from which the data is to be exported. The following are the specifiable database IDs:

PI: PI record-type Agent Store and Remote Monitor Store service database

PD: PD record-type Agent Store and Remote Monitor Store service database

PL: PL record-type Agent Store and Remote Monitor Store service database

PA: Master Store service database

-rec record-type

Specifies the record type of the data to be exported. For record-type, specify a string of 1 to 8 bytes, consisting of alphanumeric characters with no space characters. You can use a wildcard character to specify multiple record types.

For example, to export data from the Processor Overview (PI_PCSR) record of PFM - Agent for Platform (Windows), specify PCSR. For details about the record types, see the chapter in the PFM - Agent or PFM - RM manuals that describes records (list of records).

If the specified record type does not exist, the command creates an export file with a file size of 0 and then terminates itself normally.

-localtime

Specifies that the export start and end date and time are to be set to the time zone of the host that executes the command.

When this option is omitted, the command sets the export start and end date and time in GMT.

-proxy {y|n}

Specifies whether or not communication is to be through PFM - Manager in the case where a remote host is specified in the -host option in an environment in which direct communication with PFM - Agent or PFM - RM on the remote host cannot be performed.

When y is specified, the command checks the status of the target Store service through PFM - Manager. You use this option when direct communication with the Store service is not available, such as because of a firewall environment.

When n is specified, the command checks the status of the target Store service without going through PFM - Manager.

-direct

Specifies that export processing on the Master Store, Agent Store, or Remote Monitor Store service database is to be executed without going through the Master Manager service. If this option is specified, the Name Server and Master Manager services must be running. Additionally, the host where the command is executed must be able to communicate directly with the target Store service.

This option cannot be specified together with the -proxy or -alone option.

-alone

Specifies that export processing on the Master Store, Agent Store, or Remote Monitor Store service database is to be executed at the local host. The command cannot execute export processing on the Master Store, Agent Store, or Remote Monitor Store service database located at a remote host. When this option is specified, the command can execute export processing even if PFM - Manager is not running.

This option cannot be specified together with the -proxy, -direct, or -host option.

Information that is output to an export file

The following information is output to the export file:

Product information

Field names

Data

The following table describes the PA database fields that are output to the export file:

Field name

Description

PA_NODE_NAME

Sets the service ID of the agent that issued the event.

PA_HOST_NAME

Sets the host name of the agent that issued the event.

PA_CURR_STATE

Sets the event status:

1: Status is OK.

2: Status is Warning.

3: Status is Exception.

PA_ALARM_NAME

Sets an alarm name (n/a if it is not an alarm event).

PA_ALARM_TABLE_NAME

Sets an alarm table name (n/a if it is not an alarm event).

PA_MESSAGE_TEXT

Sets a message text for the event.

For details about other fields, see the chapter in the PFM - Agent or PFM - RM manuals that describes records (list of records). Fields that are not described in the PFM - Agent or PFM - RM manuals are used for internal processing.

Disk space required to execute this command

This command creates a temporary file during execution. For the amount of disk space that is required to execute this command, see the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Notes

Arguments must be specified in the order that they appear in the description. Otherwise, they will not be recognized correctly.

This command cannot be executed in the following cases:

The Name Server service, Master Manager service, or the specified Master Store, Agent Store, or Remote Monitor Store service is stopped.

The data in the database of the specified Master Store, Agent Store, or Remote Monitor Store service is currently being backed up.

The data in the database of the specified Master Store, Agent Store, or Remote Monitor Store service is currently being exported.

If you execute multiple instances of the jpctool db backup or jpctool db dump command on separate hosts concurrently, make sure that you specify the -direct or -alone option. If these options are omitted, these commands cannot be executed concurrently. To execute backup or export processing more than once, make sure that the current command's processing is completed before executing the next command.

If you execute the jpctool db dump command without specifying the -direct or -alone option, do so on a single host, rather than on multiple hosts.

The jpctool db or jpctool service command permits use of wildcard characters in the service-ID and -host options. You can execute backup or export processing concurrently on multiple agents by using wildcard characters in the service-ID or -host option.

Example: Execute the jpctool db backup command on multiple hosts

Of the data stored in the Instance (PD_PDI) record at the lhost02 host of PFM - Agent for Oracle (Windows) in a logical environment, this command specifies -alone and -direct to export to the pcsr.out file data covering the period from 2006-07-25 at 02:00 (GMT) to 2006-07-26 at 02:59 (GMT):

jpctool db dump -id "TS*" -host "*" -stime 2006/07/01 00:00 -etime 2006/07/31 00:00 -f PI.out -dbid PI -rec PCSR

After the command has been executed, if it is re-executed for the same Master Store, Agent Store, or Remote Monitor Store service with the same export file specified, the previous output results will be overwritten.

If the volume of data to be exported is large, export processing may take some time.

When you execute this command, if the temporary file that is created exceeds 2 GB, the data in the file cannot be exported. If the size of the temporary file exceeds 2 GB, export the data at different times or divide the records before exporting.

If the KAVE05234-E message is output, there was too much data to process and a timeout occurred. If this message is displayed often, take one of the following actions:

Narrow the time interval specified by start-date-and-time and end-date-and-time in the jpctool db dump command to reduce the amount of data to be exported.

Specify a specific record type, rather than a wildcard character, in the option of the jpctool db dump command.

If the jpctool db dump command is executed at multiple hosts and the KAVE05234-E message is output, specify the -direct or -alone option when you execute this command.

Historical reports might not be able to be displayed in PFM - Web Console for Agent Store and Remote Monitor Store services being exported. Request display of the historical report again after export processing is completed.

In the case of executing the jpctool db dump command with PA specified in the database-ID option, some of the characters in the export file will be garbled in the display. However, these are codes that are being used in internal processing, and there is no problem in actual operation.

Data items that are output to an export file, such as field names, are delimited by the stroke (|). Consequently, if the data to be output contains a field name or alarm name that contains the stroke character, it cannot be differentiated from the delimiter. Therefore, you should not use the stroke character in a field name or alarm name if you are going to use the jpctool db dump command to export data.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

GMT applies to an export file even when the -localtime option is specified in the jpctool db dump command.

Before you execute this command on a PFM - Agent or PFM - RM host, check whether the option for restricting remote operation from Agent hosts is enabled on the PFM - Manager host. If that option is enabled, you can export only data on the local host. If you specify a remote host by using the -host option, the command fails.

The contents of the export file are not sorted by any key. If the export file is used with a user program, the contents of the file might need to be sorted by date or other key. In such cases, sort the contents as required.

If you want to execute this command between hosts that use different types of Internet protocol, you must execute the command from PFM - Manager, by specifying the -proxy y option. If you do not specify this option, the command cannot export data.

You cannot execute this command with the -direct option between hosts that use different types of Internet protocol.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

3

One or more of the specified services is not active.

7

The specified service ID does not match Agent Store, Remote Monitor Store, or Master Store service.

100

The Performance Management environment is invalid.

101

Name Server service, Master Manager service, Master Store service, or the operation target service is not active.

102

The specified logical host name has not been set up.

104

The specified Master Store, Agent Store, or Remote Monitor Store service is engaged in backup or export processing.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

Export file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

223

A communication processing timeout error occurred.

255

An unexpected error occurred.

Usage example 1

Of the data stored in the Processor Overview (PI_PCSR) record at the host02 host of PFM - Agent for Oracle (Windows), this command exports to the pcsr.out file data covering the period from 2006-07-25 at 02:00 (GMT) to 2006-07-26 at 02:59 (GMT):

jpctool db dump -id TS* -host host02 -stime 2006/07/25 02:00 -etime 2006/07/26 14:59 -f pcsr.out -dbid PI -rec PCSR

Usage example 2

Of the data stored in the Instance (PD_PDI) record at the lhost02 host of PFM - Agent for Oracle (Windows) in a logical environment, this command specifies -alone and -direct to export to the pcsr.out file data covering the period from 2006-07-25 at 02:00 (GMT) to 2006-07-26 at 02:59 (GMT):

jpctool db dump -id OS* -lhost lhost02 -stime 2006/07/25 02:00 -etime 2006/07/26 14:59 -f pcsr.out -dbid PD -rec PDI -alone

jpctool db dump -id OS* -lhost lhost02 -stime 2006/07/25 02:00 -etime 2006/07/26 14:59 -f pcsr.out -dbid PD -rec PDI -direct

Output example

Product information, field names, and data are output to an export file as shown below.

The stroke (|) is used as the delimiter between field names and between data items.

The following shows an output example:

jpctool db import

Format

Format 1

jpctool db import    -key service-key
                     [-inst instance-name]
                     [-lhost logical-host-name]
                     [-force]
                     -d backup-directory[-add]

Format 2

jpctool db import    -key service-key
                     [-inst instance-name]
                     [-lhost logical-host-name]
                     [-force]
                     -clear

Function

The jpctool db import command imports backup data into the Store database.

The jpctool db import command can be used only when the Store version of the target Store service is 2.0.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the Store service into which backup data is imported. A product name can also be specified when the product name display functionality is enabled. You can specify only the service key of PFM - Agent or PFM - RM here. For details about the service key of the PFM - Agent or PFM - RM, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-inst instance-name

Specifies the name of the instance into which backup data is imported. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

This option must be specified when the target Store service is on a multi-instance agent. You cannot specify this option for single-instance agents.

-lhost logical-host-name

Specifies the logical host name of the Store service into which backup data is imported. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters.

If you omit this option, the setup is performed for the Store service on the physical host.

-force

When you specify this option, a confirmation message does not appear.

-d backup-directory

Specifies the name of the backup directory containing the data to be imported. You can specify only a directory on the local disk. You cannot specify the following characters in the backup directory name:

; , * ? ' " < > |

Use 1 to 214 bytes (but none of the above characters) to specify a relative path or the full path. When you specify a relative path, specify the path from the directory that is the current directory when the command is executed.

-add

When you specify this option, new data is imported without affecting existing imported data. If you omit this option, existing import data is deleted when new data is imported.

-clear

Deletes the imported data.

Notes

An error occurs if the product ID or the data model version is not the same for the specified Store service and the backup directory.

When execution of the jpctool db import command attempts to overwrite or delete imported data, the following confirmation message appears:

KAVE05874-Q If you continue the processing, the import data will be initialized. Do you want to continue? (Y/N)

Processing continues only when you enter y or Y. However, when the -force option is specified, the command is executed without displaying a confirmation message.

When this command is executed, the PFM - Agent or PFM - RM service specified by the service key must be running.

Return values

0

The command ended normally.

1

An argument is specified incorrectly.

2

The user does not have execution permission for the command.

3

The specified service is not running.

5

The specified PFM - Agent or PFM - RM has not been installed.

10

The command is being executed.

11

The user canceled the processing.

12

Importing is disabled for the specified version of the Store service.

100

The Performance Management environment is invalid.

102

The specified logical host or instance is not set up.

104

The specified Store service is being backed up or is exporting data.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

The file or directory cannot be accessed.

222

A communication processing error occurred.

255

An unexpected error occurred.

jpctool db restore

Format

jpctool db restore    -key service-key
                      -d directory-name
                     [-lhost logical-host-name]
                     [-inst instance-name]

Function

The jpctool db restore command restores database data for data backed up from the Master Store service, Agent Store service, or Remote Monitor Store service by using the jpctool db backup command.

Data can be restored only if has been backed up at the host where restoration is executed.

The Agent Store and Remote Monitor Store service data can be restored only to a Store database of the same version.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - RM

Execution permission

In Windows:

User with Administrators permissions

User with Backup Operators permission

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-key service-key

Specifies the service key of the data to be restored. A product name can also be specified when the product name display functionality is enabled. To restore data to the Master Store service database, the service key Manager or mgr is used. For details about the service key of the Agent Store or Remote Monitor Store service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-d directory-name

Specifies the name of the directory storing the backup files. For directory-name, specify a string of 1 to 130 bytes, consisting of alphanumeric characters, symbols, and the space character. Note that the following symbols cannot be specified:

; , * ? ' " < > |

If the name contains spaces, enclose the entire name in double quotation marks (").

-lhost logical-host-name

Specifies the host environment in which this command is executed. You use this argument if a logical host has been configured on the machine that is used to execute this command. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters.

If this argument is omitted, the physical host is assumed. Wildcard characters cannot be used.

-inst instance-name

If the data is to be restored to a specific instance of the database, specifies the instance name. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. This option is applicable when the PFM - Agent or PFM - RM specified in the service key has instance environments.

Notes

Before restoration, stop the PFM - Agent, PFM - RM, or PFM - Manager service that is to be restored.

You must specify the arguments in the order they appear in Format.

When restoration executes, the existing data is deleted.

After restoration, the database indexes are rebuilt at the time of service startup, which may cause the restart to take a long time.

Data cannot be restored to a different version of the database from the data model version that was backed up by the jpctool db backup command.

Data cannot be restored when the service key differs from the service key of the data that was backed up by the jpctool db backup command.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

When the Store version is 1.0, indexes are re-created. When the Store version is 2.0, indexes are not re-created because the backup files contain an IDX file.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

Command was executed while the Store database was being accessed by the Master Store, Agent Store, or Remote Monitor Store service, or jpctool db restore command.

5

The specified service has not been installed.

6

A backup file or directory was not found.

100

The Performance Management environment is invalid.

102

The specified logical host name or instance has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A backup file or directory cannot be accessed.

212

Index creation failed.

255

An unexpected error occurred.

Usage example1

This example restores to the Agent Store service in the PFM - Agent for Platform (Windows) data that was backed up at the default location:

jpctool db restore -key Windows -d "c:\program files\hitachi\jp1pc\agtt\store\backup\01"

Usage example 2

This example restores the data in /opt/jp1pc/agto/store/inst1/backup/01 to instance inst1 of the database for PFM - Agent for Oracle on a logical host (host name: jp1-ha1):

jpctool db restore -key Oracle -d /opt/jp1pc/agto/store/inst1/backup/01 -lhost jp1-ha1 -inst inst1

jpctool monitor list

Format

jpctool monitor list    [-group business-group-name
                        |-host host-name
                        |-id service-ID]
                        [-lhost logical-host-name]

Function

The jpctool monitor list command displays the monitoring suspension statuses and settings for the entire Performance Management system.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

If you omit the -group option, the -host option, and the -id option, the command assumes that the local host is specified for the -host option.

-group business-group-name

Specifies the name of the business group for which the monitoring suspension statuses and settings are to be displayed.

For business-group-name, specify a string of 1 to 255 bytes, consisting of double-byte characters, single-byte characters, and the symbols below. Alphabetic characters are case sensitive.

! " # $ % & ' ( ) + - . : ; < = > @ [ \ ] ^ _ ` { | } ~

If you specify a string that contains single-byte spaces, enclose the entire string in double quotation marks ("). If you specify a single-byte symbol, specify an escape character as necessary. You can use wildcard characters to specify multiple business group names.

-host host-name

Specifies the name of the host for which the monitoring suspension statuses and settings are to be displayed.

For host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters. You can use wildcard characters to specify multiple host names.

-id service-ID

Specifies the service ID for which the monitoring suspension statuses and settings are to be displayed.

Specify the service ID (the second character is A) for the Agent Collector service or the Remote Monitor Collector service. You can also specify the health check agent. For service-ID, specify a string of 1 to 258 bytes. You can use wildcard characters to specify multiple service IDs.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in the logical host environment, not in the physical host environment.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters. If you omit this option, the command assumes that the physical host is specified. Wildcard characters cannot be specified.

Targets of each argument

Table 2‒82: Targets of each argument (jpctool monitor list command)

Argument

Target

-group

Displays the monitoring suspension statuses and settings for the hosts that belong to the specified business group and the agents that are installed in the hosts.

If the agents are PFM - RM, the monitoring suspension statuses and settings for the remote agents are also displayed.

-host

Displays the monitoring suspension statuses and settings for the specified host and the agents that are installed in the host.

If the agents are PFM - RM, the monitoring suspension statuses and settings for the remote agents are also displayed.

-id

Displays the monitoring suspension statuses and settings for the agent. If the agent is PFM - RM, the monitoring statuses and settings for the remote agents are also displayed.

Notes

When the monitoring suspension function option is disabled, this command cannot be used.

When the PFM - Manager service (Master Manager and View Server services) is not running, this command cannot be used.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

In a multiple-monitoring environment, if you execute this command on the secondary host, - is displayed for the Status column. In addition, an incorrect value might be displayed for the Status column due to the following reasons:

A terminated agent starts when the jpctool monitor suspend command or the jpctool monitor resume command runs.

The switchover is performed between the primary and secondary hosts even though there are agents whose setting application statuses are unknown.

To display a correct value for the Status column, execute the jpctool monitor resume command on the PFM - Manager for the both primary and secondary hosts to resume the entire monitoring. Then, suspend the monitoring again. However, the jpctool monitor resume command cannot be executed on the PFM - Manager for the secondary host. Therefore, switch over the secondary host to the primary host and then execute the jpctool monitor resume command.

If you suspend or resume the monitoring when there are agents whose versions are 10-00 or earlier, an asterisk (*) is displayed for the setting application statuses of the agents. To remove the asterisk (*), you need to upgrade the versions of the agents to 10-00 or later or delete the services of the agents.

Usually, even if you execute this command, the monitoring suspension statuses and settings for the hosts and agents below are not displayed and are displayed only when the monitoring is suspended by specifying the -force option.

The hosts and agents that have never been connected to PFM - Manager.

The host and agents that have never been started since the host name was changed.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The command was executed on a host that is not the PFM - Manager host.

12

The monitoring suspension function is disabled.

18

The specified business group has not been registered.

19

The specified host has not been registered.

20

The specified service has not been registered.

100

The Performance Management environment is invalid.

101

The service required for this operation does not start.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

222

A communication processing error occurred.

223

A communication processing timeout error occurred.

253

Access control by business group is disabled.

255

An unexpected error occurred.

Displayed information

The following table describes the information that is displayed by executing the jpctool monitor command.

Table 2‒83: Information displayed by the jpctool monitor command

No

Displayed item

Meaning

Format

1

#

Type

Displays one of the following identifiers for each type:

G: Business group#1

H: Host

A: Agent

R: Remote agent

2

Status

-

Monitoring status

Displays the monitoring status for the target.

3

*

Result of changing the monitoring statuses for the agents#2

For the line where the type item is H:

Indicates whether the monitoring statuses for the agents have been changed when the monitoring of the host and its agents is suspended or resumed.

-: The monitoring statuses for all agents have been changed.

*: Unknown whether the monitoring statuses for some agents have been changed.

#: The target host does not have any agents (when the monitoring of the host is suspended by using the jpctool monitor suspend command with the -force option specified, when all agents on the host of which the monitoring was suspended by using the jpctool monitor suspend command are uninstalled, etc.)

For the line where the type item is A or R:

Indicates the result of changing the monitoring statuses for the agent.

-: The monitoring statuses have been changed.

*: Unknown whether the monitoring statuses have been changed.

4

Mon

Monitoring status (monitoring suspension)

Act: The monitoring is activated.

Sus: The monitoring is suspended.

5

Log

Monitoring status (DB storage continuation)

Y: The storage of the operating information continues.

N: The storage of the operating information is suspended.

6

Setting

-

Settings

The monitoring suspension unit, host-based or agent-based.

7

*

Setting application status for the target#2

For the line where the type item is H:

When the monitoring was suspended or resumed by specifying a business group or a host name, indicates the result of changing the monitoring statuses for the agents under the business group or host.

-: The monitoring statuses for all agents have been changed.

*: Unknown whether the monitoring statuses for some agents have been changed.

For the line where the type item A or R:

When the monitoring was suspended by specifying a service ID, indicates the result of changing the monitoring status.

-: The monitoring status has been changed.

*: Unknown whether the monitoring status has been changed.

8

Mon

Setting (monitoring suspension)

For the line where the type item is H:

Indicates whether the monitoring was suspended by specifying a business group or a host name.

Act: Not suspended.

Sus: Suspended.

For the line where the type item is A or R:

Indicates whether the monitoring was suspended by specifying a service ID.

Act: Not suspended.

Sus: Suspended.

9

Log

Setting (DB storage continuation)

Y: The storage of the operating information has been set to continue.

N: The storage of the operating information has been set to be suspended.

10

Name

Business group name#1, host name, or service ID

Displays the grouped business group names#1, host names, or service IDs, in ascending order.

Even if the product name display functionality is enabled, service IDs are displayed.

#1

The jpctool monitor status command does not display the information.

#2

Only the jpctool monitor list command displays the information.

Assumed environment

The usage examples below assume that this command is executed in the environment below.

In the figure, PFM - Agent indicates PFM - Agent for Platform and PFM - RM indicates PFM - RM for Oracle.

Usage example 1

This example displays the monitoring suspension statuses and settings for all hosts whose name begins with Host and their agents.

jpctool monitor list -host Host*

The following shows an example of the command execution results.

  Status    Setting
# * Mon Log * Mon Log Name
- - --- --- - --- --- --------------------------------------------------
H - Act Y   - Act Y   HostA
A - Act Y   - Act Y   1A1hostA[HostA]
A - Act Y   - Act Y   1A1hostA[All@HostA]
R - Act Y   - Act Y   1A1hostA[hostB@HostA]
R - Act Y   - Act Y   1A1hostA[hostC@HostA]
A - Act Y   - Act Y   TA1HostA
H - Act Y   - Act Y   HostB
A - Act Y   - Act Y   1A1hostA[hostB@HostA]
A - Act Y   - Act Y   TA1HostB
H - Act Y   - Act Y   HostC
A - Act Y   - Act Y   1A1hostA[hostC@HostA]
KAVE06180-I The monitoring suspension function was successfully set and the monitoring status was successfully displayed.

Usage example 2

This example displays the monitoring suspension statuses and settings for all hosts whose name begins with Host and their agents.

This example assumes that the monitoring of HostB is suspended by specification of the host.

jpctool monitor list -host Host*

The following shows an example of the command execution results.

  Status    Setting
# * Mon Log * Mon Log Name
- - --- --- - --- --- --------------------------------------------------
H - Act Y   - Act Y   HostA
A - Act Y   - Act Y   1A1hostA[HostA]
A - Act Y   - Act Y   1A1hostA[All@HostA]
R - Sus N   - Act Y   1A1hostA[hostB@HostA]
R - Act Y   - Act Y   1A1hostA[hostC@HostA]
A - Act Y   - Act Y   TA1HostA
H - Sus N   - Sus N   HostB
A - Sus N   - Act Y   1A1hostA[hostB@HostA]
A - Sus N   - Act Y   TA1HostB
H - Act Y   - Act Y   HostC
R - Act Y   - Act Y   1A1hostA[hostC@HostA]
KAVE06180-I The monitoring suspension function was successfully set and the monitoring status was successfully displayed.

jpctool monitor resume

Format

jpctool monitor resume    {-group business-group-name
                          | -host host-name [-force]
                          | -id service-ID}
                          [-lhost logical-host-name]
                          [-noquery]
                          [-wait number-of-seconds]
                          [-verbose]

Function

The jpctool monitor resume command resumes the monitoring.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-group business-group-name

Specifies the name of the business group of which the monitoring is to be resumed.

For business-group-name, specify a string of 1 to 255 bytes, consisting of double-byte characters, single-byte characters, and the symbols below. Alphabetic characters are case sensitive.

! " # $ % & ' ( ) + - . : ; < = > @ [ \ ] ^ _ ` { | } ~

If you specify a string that contains single-byte spaces, enclose the entire string in double quotation marks ("). If you specify a single-byte symbol, specify an escape character as necessary. You can also use wildcard characters to specify multiple business group names.

-host host-name

Specifies the name of the host of which the monitoring is to be resumed.

For host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters. You can use wildcard characters to specify multiple host names.

-force

Specify this option to remove the monitoring suspension setting information for a host that do not have agents (a host whose value of the * column of the Status item is displayed as # in the execution results of the jpctool monitor list command). For example, during the operation to change a host name, if the monitoring suspension setting information for the host with the old name remains, use this option to remove the information.

If you specify a wildcard character or an existing host name for the -host option, this option is ignored.

-id service-ID

Specifies the service ID of which the monitoring is to be started.

Specify the service ID (the second character is A) for the Agent Collector service or the Remote Monitor Collector service. You can also specify the health check agent. For service-ID, specify a string of 1 to 258 bytes. You can use wildcard characters to specify multiple service IDs.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in the logical host environment, not in the physical host environment.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters and no wildcard characters. If you omit this option, the command assumes that the physical host is specified.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond.

-wait number-of-seconds

Specifies the maximum wait time (in seconds) applied when a command that cannot be executed with this command is running. Specify a number in the range from 0 to 3,600 for this option.

If you omit this option, the command assumes that 300 seconds are specified. If you specify 0, the command execution is not suspended.

-verbose

If you specify this option, lists the hosts and agents for which the monitoring status is to be changed to the resume status.

Targets of each argument

Table 2‒84: Targets of each argument (jpctool monitor resume command)

Argument

Target

-group

Resumes the monitoring of the hosts that belong to the specified business group and the agents that are installed in the hosts.

If the agents are PFM - RM, the monitoring of the remote agents is also resumed.

-host

Resumes the monitoring of the specified host and the agents that are installed in the host.

If the agents are PFM - RM, the monitoring of the remote agents is also resumed.

-id

Resumes the monitoring of the specified agent. If the agent is PFM - RM, the monitoring of the remote agents is also resumed.

Notes

If the monitoring suspension function option is disabled, this command cannot be used.

If the PFM - Manager service (Master Manager and View Server services) is not running, this command cannot be used.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

This command cannot be executed with the startup stop command or another setup command on the same machine. By specifying the -wait option, if a command that cannot be executed with this command is running, this command can wait for the command execution to complete for the specified period (in seconds).

Do not add or delete monitoring targets while this command is running. The latest information might not be displayed.

The monitoring of the hosts that have never been connected to PFM - Manager cannot be resumed by using the -group option. Specify the -host option and the -force option to resume the monitoring.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The command was executed on a host that was not the PFM - Manager host.

11

The user canceled the processing.

12

The monitoring suspension function is disabled.

16

This command waited to run because a startup or termination command or other setup command was being executed on the same machine, but a timeout occurred.

17

This command was executed from the secondary PFM - Manager in a multiple-monitoring environment.

18

The specified business group has not been registered.

19

The specified host has not been registered.

20

The specified service has not been registered.

22

Failed to update PFM - Manager.

23

Failed to update PFM - Agent and PFM - RM.

100

The Performance Management environment is invalid.

101

The service required for this operation does not start.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

222

A communication processing error occurred.

223

A communication processing timeout error occurred.

253

Access control by business group is disabled.

255

An unexpected error occurred.

Displayed information

The following table describes the information that is displayed by executing this command.

Table 2‒85: Information displayed by the jpctool monitor resume command

No

Displayed information

Description

1

List of targets

The following information is displayed based on Table 2-83 Information displayed by the jpctool monitor command:

[List of setting changes]

Displays the hosts and agents for which the monitoring suspension setting is to be changed to the resume status.

[List of status changes]

Displays the hosts and agents for which the monitoring status is to be changed to the resume status. This information is displayed only when the -verbose option is specified.

2

Query message

A KAVE06181-Q message asking whether to continue the processing is output.

If you enter Y, the processing continues.

3

Progress display

The progress for the following processing is displayed:

Change of PFM - Manager settings

Change of the monitoring status on PFM - Agent or PFM - RM

Assumed environment

The usage examples below assume that this command is executed in the environment below.

In the figure, PFM - Agent indicates PFM - Agent for Platform and PFM - RM indicates PFM - RM for Oracle.

Usage example 1

This example resumes the monitoring by specification of a business group when the monitoring was suspended by specification of a host.

This example assumes that the monitoring of HostA was suspended by specification of the host.

jpctool monitor resume -group Group1

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
G --- -   --- -   Group1
H Sus N   Sus N   HostA
H Act Y   Act Y   HostB
H Act Y   Act Y   HostC
KAVE06181-Q Monitoring of the displayed host or agent will resume. Do you want to continue? (Y/N) Y
KAVE06191-I Monitoring will resume.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06192-I Monitoring was successfully resumed.

Usage example 2

This example resumes the monitoring by specification of a host when the monitoring was suspended by specification of the host.

This example assumes that the monitoring of HostA was suspended by specification of the host.

jpctool monitor resume -host HostA

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Sus N   Sus N   HostA
KAVE06181-Q Monitoring of the displayed host or agent will resume. Do you want to continue? (Y/N) Y
KAVE06191-I Monitoring will resume.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06192-I Monitoring was successfully resumed.

Usage example 3

This example specifies the -verbose option under the same conditions as those of usage example 2.

jpctool monitor resume -host HostA -verbose

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Sus N   Sus N   HostA

[List of status changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Sus N   Sus N   HostA
A Sus N   Act Y   1A1hostA[HostA]
A Sus N   Act Y   1A1hostA[All@HostA]
R Sus N   Act Y   1A1hostA[hostB@HostA]
R Sus N   Act Y   1A1hostA[hostC@HostA]
A Sus N   Act Y   TA1HostA
KAVE06181-Q Monitoring of the displayed host or agent will resume. Do you want to continue? (Y/N) Y
KAVE06191-I Monitoring will resume.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06192-I Monitoring was successfully resumed.

Usage example 4

This example resumes the monitoring by specification of an agent when the monitoring was suspended by specification of the agent.

This example assumes that the monitoring of TA1HostB was suspended by specification of the agent.

jpctool monitor resume -id TA1HostB

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
A Sus N   Sus N   TA1HostB
KAVE06181-Q Monitoring of the displayed host or agent will resume. Do you want to continue? (Y/N) Y
KAVE06191-I Monitoring will resume.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06192-I Monitoring was successfully resumed.

Usage example 5

This example resumes the monitoring of the agents whose monitoring was suspended by specification of a host and an agent.

This example assumes that the monitoring of HostB was suspended by specification of the host and the monitoring of TA1HostB was suspended by specification of the agent.

First, resume the monitoring of HostB.

jpctool monitor resume -host HostB

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Sus N   Sus N   HostB
KAVE06181-Q Monitoring of the displayed host or agent will resume. Do you want to continue? (Y/N) Y
KAVE06191-I Monitoring will resume.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06192-I Monitoring was successfully resumed.

The monitoring of HostB is now resumed. However, the monitoring of TA1HostB remains suspended because it was suspended by specification of the agent. Therefore, you must resume the monitoring of TA1HostB in the next step.

jpctool monitor resume -id TA1HostB

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
A Sus N   Sus N   TA1HostB
KAVE06181-Q Monitoring of the displayed host or agent will resume. Do you want to continue? (Y/N) Y
KAVE06191-I Monitoring will resume.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06192-I Monitoring was successfully resumed.

jpctool monitor status

Format

jpctool monitor status    [-id service-ID]
                          [-lhost logical-host-name]

Function

The jpctool monitor status command displays the monitoring statuses and settings for the command execution host.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-id service-ID

Specifies the service ID for which monitoring suspension statuses and settings are to be displayed.

Specify the service ID (the second character is A) for the Agent Collector service or the Remote Monitor Collector service. You can also specify the health check agent. For service-ID, specify a string of 1 to 258 bytes. You can use wildcard characters to specify multiple service IDs. If you omit this option, the monitoring statuses and settings of the execution host and its agents are displayed.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in the logical host environment, not in the physical host environment.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters. If you omit this option, the command assumes that the physical host is specified. Wildcard characters cannot be used.

Notes

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

20

The specified service has not been registered.

100

The Performance Management environment is invalid.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Displayed information

For details on the information displayed by executing this command, see Table 2-83 Information displayed by the jpctool monitor command.

Assumed environment

The usage examples below assume that this command is executed in the environment below.

In the figure, PFM - Agent indicates PFM - Agent for Platform and PFM - RM indicates PFM - RM for Oracle.

Usage example 1

This example displays the monitoring suspension statuses and settings for the command execution host HostA and its agents.

jpctool monitor status

The following shows an example of the command execution results.

  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Act Y   Act Y   HostA
A Act Y   Act Y   1A1hostA[HostA]
A Act Y   Act Y   1A1hostA[All@HostA]
R Act Y   Act Y   1A1hostA[hostB@HostA]
R Act Y   Act Y   1A1hostA[hostC@HostA]
A Act Y   Act Y   TA1HostA
KAVE06180-I The monitoring suspension function was successfully set and the monitoring status was successfully displayed.

Usage example 2

This example displays the monitoring suspension statuses and settings for the command execution host HostB and its agents.

This example assumes that the monitoring of HostB was suspended by specification of the host.

jpctool monitor status

The following shows an example of the command execution results.

  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Sus N   Sus N   HostB
A Sus N   Act Y   TA1HostB
KAVE06180-I The monitoring suspension function was successfully set and the monitoring status was successfully displayed.

jpctool monitor suspend

Format

jpctool monitor suspend    {-group business-group-name
                           | -host host-name [-force]
                           | -id service-ID}
                           [-log]
                           [-lhost logical-host-name]
                           [-noquery]
                           [-wait number-of-seconds]
                           [-verbose]

Function

The jpctool monitor suspend command suspends the monitoring.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions (A user whose uid is 0.)

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-group business-group-name

Specifies the name of the business group of which the monitoring is to be suspended.

For business-group-name, specify a string of 1 to 255 bytes, consisting of double-byte characters, single-byte characters, and the symbols below. Alphabetic characters are case sensitive.

! " # $ % & ' ( ) + - . : ; < = > @ [ \ ] ^ _ ` { | } ~

If you specify a string that contains single-byte spaces, enclose the entire string in double quotation marks ("). If you specify a single-byte symbol, specify an escape character as necessary. You can also use wildcard characters to specify multiple business group names.

-host host-name

Specifies the name of the host of which the monitoring is to be suspended.

For host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters. You can use wildcard characters to specify multiple host names.

-force

Specify this option to start the services for a host that is to be newly added or a host whose name was changed when the monitoring of the host is suspended.

If you specify a wildcard character or an existing host name for the -host option, this option is ignored.

-id service-ID

Specifies the service ID of which the monitoring is to be suspended.

Specify the service ID (the second character is A) for the Agent Collector service or the Remote Monitor Collector service. You can also specify the health check agent. For service-ID, specify a string of 1 to 258 bytes. You can use wildcard characters to specify multiple service IDs.

-log

Specify this option to continue the storage of the operating information and suspend the monitoring.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in the logical host environment, not in the physical host environment.

For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters and no wildcard characters. If you omit this option, the command assumes that the physical host is specified.

-noquery

If this option is specified, the command does not output any query messages that interrupt command execution, making it unnecessary for the user to respond.

-wait number-of-seconds

Specifies the maximum wait time (in seconds) applied when a command that cannot be executed with this command. Specify a number in the range from 0 to 3,600 for this option.

If you omit this option, the command assumes that 300 seconds are specified. If you specify 0, the command execution is not suspended.

-verbose

If you specify this option, lists the hosts and agents for which the monitoring status is to be changed to the monitoring suspended status.

Targets of each argument

Table 2‒86: Targets of each argument (jpctool monitor suspend command)

Argument

Target

-group

Suspends the monitoring of the hosts that belong to the specified business group and the agents that are installed in the hosts.

If the agents are PFM - RM, the monitoring of the remote agents is also resumed.

-host

Suspends the monitoring of the specified host and the agents that are installed in the host.

If the agents are PFM - RM, the monitoring of the remote agents is also suspended.

-id

Suspends the monitoring of the agent. If the agent is PFM - RM, the monitoring of the remote agents is also suspended.

Notes

If the monitoring suspension function option is disabled, this command cannot be used.

If the PFM - Manager service (Master Manager and View Server services) is not running, this command cannot be used.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

This command cannot be executed with the startup stop command or another setup command on the same machine. By specifying the -wait option, if a command that cannot be executed with this command is running, execution of this command can wait to complete the command processing for the specified period (in seconds).

Do not add or delete monitoring targets while this command is running. The latest information might not be displayed.

The monitoring of the hosts that have never been connected to PFM - Manager cannot be suspended by using the -group option. Specify the -host option and the -force option to suspend the monitoring.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

5

The command was executed on a host that was not the PFM - Manager host.

11

The user canceled the processing.

12

The monitoring suspension function is disabled.

16

This command waited to run because a startup or termination command or other setup command was being executed on the same machine, but a timeout occurred.

17

This command was executed from the secondary PFM - Manager in a multiple-monitoring environment.

18

The specified business group has not been registered.

19

The specified host has not been registered.

20

The specified service has not been registered.

22

Failed to update PFM - Manager.

23

Failed to update PFM - Agent and PFM - RM.

100

The Performance Management environment is invalid.

101

The service required for this operation does not start.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

211

A file or directory cannot be accessed.

222

A communication processing error occurred.

223

A communication processing timeout error occurred.

253

Access control by business group is disabled.

255

An unexpected error occurred.

Displayed information

The following table describes the information displayed by executing this command.

Table 2‒87: Information displayed by executing the jpctool monitor suspend command

No

Displayed information

Description

1

List of targets

The following information is displayed based on Table 2-83 Information displayed by the jpctool monitor command:

[List of setting changes]

Displays the hosts and agents for which the monitoring suspension setting is to be changed to the monitoring suspended status.

[List of status changes]

Displays the hosts and agents for which the monitoring status is to be changed to the monitoring suspended status. This information is displayed only when the -verbose option is specified.

2

Query message

A KAVE06182-Q message asking whether to continue the processing is output.

If you enter Y, the processing continues.

3

Progress display

The progress for the following processing is displayed:

Change of PFM - Manager settings

Change of the monitoring status on PFM - Agent or PFM - RM

Assumed environment

The usage examples below assume that this command is executed in the environment below.

In the figure, PFM - Agent indicates PFM - Agent for Platform and PFM - RM indicates PFM - RM for Oracle.

Usage example 1

This example suspends the monitoring by specification of a business group.

jpctool monitor suspend -group Group1

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
G --- -   --- -   Group1
H Act Y   Act Y   HostA
H Act Y   Act Y   HostB
H Act Y   Act Y   HostC
KAVE06182-Q Monitoring on the displayed host or agent will be suspended. Do you want to continue? (Y/N) Y
KAVE06193-I Monitoring will be suspended.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06194-I The suspension of monitoring was successful.

Usage example 2

This example suspends the monitoring by specification of a host.

jpctool monitor suspend -host HostA

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Act Y   Act Y   HostA
KAVE06182-Q Monitoring on the displayed host or agent will be suspended. Do you want to continue? (Y/N) Y
KAVE06193-I Monitoring will be suspended.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06194-I The suspension of monitoring was successful.

Usage example 3

This example suspends the monitoring by specification of an agent.

jpctool monitor suspend -id TA1HostB

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
A Act Y   Act Y   TA1HostB
KAVE06182-Q Monitoring on the displayed host or agent will be suspended. Do you want to continue? (Y/N) Y
KAVE06193-I Monitoring will be suspended.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06194-I The suspension of monitoring was successful.

Usage example 4

This example continues the storage of the operating information and suspends the monitoring by specification of a host.

jpctool monitor suspend -host HostA -log

The following shows an example of the command execution results.

[List of setting changes]
  Status  Setting
# Mon Log Mon Log Name
- --- --- --- --- ------------------------------------------------------
H Act Y   Act Y   HostA
KAVE06182-Q Monitoring on the displayed host or agent will be suspended. Do you want to continue? (Y/N) Y
KAVE06193-I Monitoring will be suspended.
KAVE06183-I The settings information for the monitoring suspension function on the monitoring manager was successfully updated.
[100%]
KAVE06186-I The settings information for the monitoring suspension function on the monitoring agent was successfully updated.
KAVE06194-I The suspension of monitoring was successful.

jpctool service delete

Format

jpctool service delete     -id service-ID
                          [-host host-name]
                          [-lhost logical-host-name]
                          [-force]

Function

The jpctool service delete command deletes the service information for an agent registered in Performance Management. You use this command to delete the service information for a product that has been uninstalled.

Note

The service information for the Name Server, Master Manager, Master Store, and Status Server cannot be deleted.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

User with Backup Operators permission

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-id service-ID

Specifies the service ID of the service information to be deleted. For service-ID, specify a string of 1 to 258 bytes. You can use a wildcard character to specify multiple service IDs. In this case, processing of the remaining services continues even if an error occurs on one service. If errors occur on multiple services, the command returns a value for the last error that occurred.

-host host-name

Specifies a host name if service information is to be deleted from a specific host. For host-name, specify a strong of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this option, the local host is assumed.

You can use a wildcard character to specify multiple host names.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in a logical host environment, not in the physical host environment. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

-force

When this option is specified, service information is forcibly deleted, regardless of whether the service specified by the service ID is running.

Notes

Arguments must be specified in the order that they appear in the description. Otherwise, they will not be recognized correctly.

When this command is executed, communication is established from the PFM - Manager host to the PFM - Agent or PFM - RM host to check the startup status of the PFM - Agent or PFM - RM. If communication cannot be established for a physical reason, such as a LAN cable not connected at the PFM - Agent host or PFM - RM host, the command cannot delete the agent's service information. In this case, by executing this command with the -force option specified, you can forcibly delete service information.

If the Name Server and Master Manager services are not running, service information cannot be deleted. Also, if the specified service is engaged in startup processing, its service information cannot be deleted.

When the service information synchronized by the jpctool service sync command is applied varies depending on the version of PFM - Web Console. For details about the jpctool service sync command, see jpctool service sync.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

If an Action Handler service is deleted, action execution is disabled for the alarms that use that Action Handler service.

If you delete service information of an agent, check whether alarm tables are bound to the agent. If alarm tables are bound, unbind all of them, and then delete the service information.

After executing this command, an unnecessary agent remains under the User Agents node in the Agents tree in PFM - Web Console. If you do not want that agent to be displayed, delete it manually.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

The specified service has not been registered.

4

The specified service has not been stopped.

5

PFM - Manager has not been installed.

7

The specified service ID belongs to the Name Server, Master Manager, Master Store, or Status Server service.

100

The Performance Management environment is invalid.

101

Either Name Server service or Master Manager service is not active.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

255

An unexpected error occurred.

Usage example 1

This command deletes service information after PFM - Agent for Platform (Windows) has been uninstalled at the host02 host:

jpctool service delete -id T* -host host02

Usage example 2

This example deletes the service information for PFM - Agent for Platform (UNIX) at the host03 host. The command assumes that the PFM - Manager to which PFM - Agent for Platform (UNIX) belongs is in a logical host environment (host01):

jpctool service delete -id "U*" -host host03 -lhost host01

Usage example 3

This example deletes the service information for all the agents on the jp1-ha1 logical host when PFM - Agent or PFM - RM is in a logical host environment (host name: jp1-ha1) and PFM - Manager is on the physical host:

jpctool service delete -id "?S*" -host jp1-ha1

Usage example 4

This example deletes the service information for all the agents on the jp1-ha1 logical host when PFM - Agent or PFM - RM is on a logical host (host name: jp1-ha1) and PFM - Manager is on a logical host (host name: jp1-ha2):

jpctool service delete -id "?S*" -host jp1-ha1 -lhost jp1-ha2

jpctool service list

Format

Format 1

jpctool service list     -id service-ID
                        [-host host-name]
                        [-lhost logical-host-name]
                        [-proxy {y|n}]
                        [-stat]
                        [-v]

Format 2

jpctool service list     -key service-key
                        [-lhost logical-host-name]
                        [-proxy {y|n}]
                        [-stat]
                        [-v]

Function

The jpctool service list command displays the service configuration and status of a Performance Management program.

When PFM - Manager or PFM - Base and PFM - Web Console are installed on the same host, and start and stop linkage is set, execute the jpctool service list command in Format 2 to display the configuration and status for all Performance Management program services including PFM - Web Console. For details about the start and stop linkage settings for PFM - Manager, PFM - Base, and PFM - Web Console, see the chapter describing Performance Management start and stop in the Job Management Partner 1/Performance Management User's Guide.

Hosts that can execute the command

PFM - Manager

PFM - Agent

PFM - Base

PFM - RM

Execution permission

In Windows:

None

In UNIX:

None

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-id service-ID

Specifies a service ID. Specify a string of 1 to 258 bytes.

You can use a wildcard character to specify multiple service IDs. In this case, processing of the remaining services continues even if an error occurs on one service. If errors occur on multiple services, the command returns a value for the last error that occurred.

-host host-name

Specifies the name of the host whose service configuration and status are to be displayed. You use this argument to display the configuration and status of a Performance Management program running on a specific host. For host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this option, the local host is assumed.

You can use a wildcard character to specify multiple host names.

-lhost logical-host-name

Format 1

Specifies a logical host name if this command is to be executed by a host in a logical host environment, not in the physical host environment. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

Format 2

When PFM - Web Console is running on a logical host environment, specify the name of the startup host (logical host name) for PFM - Web Console. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

-proxy {y|n}

Specifies whether or not communication is to be through PFM - Manager in the case where a remote host is specified in the -host option in an environment in which direct communication with PFM - Agent or PFM - RM on the remote host cannot be performed.

When y is specified, communication is performed through PFM - Manager.

When n is specified, communication is not performed through PFM - Manager.

-stat

Specifies that the status is to be displayed by communicating directly with the Status Server service at the host specified in -host host-name. You specify this option to display remote host information when the PFM - Manager is not running. The command also displays the status of the Status Server service at the remote host.

When this option is specified, wildcard characters cannot be used in -host host-name. This option cannot be specified together with -proxy {y|n}.

This option cannot be used if the status management function is disabled.

-v

When the product name display functionality is enabled, the service name is displayed using the product name. For details about product name display functionality, see the chapter describing Performance Management functionality in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

-key service-key

Specifies the key of the service whose configuration and status are to be displayed. You can specify the following in service-key:

all: Displays the configuration and statuses of all Performance Management program services.

jp1pc: Displays the configuration and statuses of all PFM - Manager program services (excluding the PFM - Web Console service).

Manager or mgr: Displays the configuration and statuses of all PFM - Manager services (excluding the Action Handler service).

AH or act: Displays the configuration and status of the Action Handler service.

StatSvr or stat: Displays the configuration and status of the Status Server service.

WebConsole or wc: Displays the configuration and status of the PFM - Web Console service.

For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Notes

The command cannot display information about the service of a Performance Management program that has never been started. The same applies to a service that has never been started since the host was renamed.

Arguments must be specified in the order that they appear in the description. Otherwise, they will not be recognized correctly.

If the Name Server and Master Manager services are not running, the service configuration and status cannot be displayed for a host other than the local host. In this case, communication does not go through PFM - Manager even if y is specified in the -proxy option.

If the jpctool service list command is executed immediately after a Performance Management program starts, the service status may be displayed as Inactive even though the service process is active. In this case, the corresponding service either may be engaged in startup processing or may be temporarily in the stand-alone mode due to connection wait status. If PFM - Manager is running, wait a while, and then use the jpctool service list command to check the service status.

If PFM - Manager is uninstalled and then re-installed on the same machine, the jpctool service list command may display two different Trap Generator services. In this case, start the PFM - Manager service and use the jpctool service delete command to delete the Trap Generator service whose status is Inactive.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

If the -stat option is omitted, the command does not display the Status Server service at a remote host.

If the status management function is disabled, the Status Server service is not displayed.

In the following cases, the configuration and status is not displayed for remote agents and group agents.

The Master Manager or Name Server service is not running

The -stat option is specified

After either of the following operations has been performed, if the information about the relevant service is not deleted, the service might be displayed when the jpctool service list command is executed:

Uninstallation of PFM - Agent, PFM - RM, or PFM - Base

Unsetup of the PFM - Agent or PFM - RM instance environment

The following table describes the situations in which the service is displayed.

Situations in which the jpctool service list command is executed

Whether service information is deleted

Target host

Whether the -stat option is specified

No

Yes

Local host

--

The service is not displayed.

The service is not displayed.

Remote host

Specified

The service is not displayed.

The service is not displayed.

Not specified

The service is displayed.

The service is not displayed.

Legend:

--: Not applicable

After the information about a service has been deleted, if uninstallation of the service or unsetup of the service's instance environment is not performed, the service might be displayed when the jpctool service list command is executed.

The following table describes the situations in which the service is displayed.

Situations in which the jpctool service list command is executed

Whether uninstallation of the service or unsetup of the service's instance environment is performed

Target host

Whether the -stat option is specified

No

Yes

Local host

--

The service is not displayed.

The service is not displayed.

Remote host

Specified

The service is not displayed.

The service is not displayed.

Not specified

The service is displayed.

The service is not displayed.

Legend:

--: Not applicable

Before you execute this command on a PFM - Agent or PFM - RM host, check whether the option for restricting remote operation from Agent hosts is enabled on the PFM - Manager host. If that option is enabled, you can display only the configurations and statuses of services that are running on the local host (except when the -stat option is specified). If you specify a remote host by using the -host option, the command fails.

If the option for restricting the viewing of service information from Agent hosts is enabled on the host specified by the -host option, you cannot execute this command with the -stat option.

If you want to execute this command between hosts that use different types of Internet protocol, you must execute the command from PFM - Manager, by specifying the -proxy y option. If you execute this command without specifying the -proxy y option, the string Inactive is displayed.

You cannot execute this command with the -stat option between hosts that use different types of Internet protocol.

Cautions regarding execution using Format 2

When anything other than all, wc or WebConsole is specified for the service key argument of the -key option, the configuration and status of the PFM - Web Console service is not displayed.

The -host option cannot be specified to display the configuration and status for remote host services.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

3

The specified service has not been registered.

100

The Performance Management environment is invalid.

101

Name Server service is not active.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

255

An unexpected error occurred.

Displayed information

The following table describes the information that is displayed by executing the jpctool service list command:

Output information

Description

Host Name

Name of the host where the service is running.

ServiceID#1

Service ID. Even when the product name display functionality is enabled, the product name is not displayed. If executed in Format 2, this is not displayed on the output line for PFM - Web Console service information.

Service Name#1

Service name. Even when the product name display functionality is enabled, the product name is not displayed. If executed in Format 2, the fixed string Web Console is displayed in the PFM - Web Console service information.

Service#2

Service name. The service ID is displayed for the product name.

PID

Indicates the service process ID.

When the status management function is enabled:

The process ID is displayed when Status is Active, Busy, S Active, S Busy, Starting, or Stopping.

When the status management function is disabled or the version does not support the status management function:

The process ID is displayed only when Status is Active.

If executed in Format 2, this is not displayed on the output line for PFM - Web Console service information.

Port

Indicates the communication port number used by the service.

For services other than PFM - Web Console

When the status management function is enabled:

The port number is displayed when Status is Active, Busy, S Active, or S Busy.

When the status management function is disabled or the version does not support the status management function:

The port number is displayed only when Status is Active.

For PFM - Web Console

When the Status is Active

-- is displayed.

When the Status is not Active

Nothing is displayed.

Status

Indicates the status of the service.

When the status management function is enabled:

Service status display when the version supports the status management function

Active: Waiting for a request

Inactive: Stopped

Starting: Being started

Busy: Processing a request

S Active: Waiting for a request, stand-alone mode

S Busy: Processing a request, stand-alone mode

Stopping: Being stopped

Service status display when the version does not support the status management function

Active#: Operating

Incomp#: Starting or stopping the service

Inactive#: Unable to connect for communication or is stopped

Comm Err#: Able to connect for communication, but not responding

Timeout#: Communication connection timeout

Error#: An error other than a communication connection timeout error occurred. For details about the error, see the common message log.

However, in the following cases, the service status display of the version supporting the function is the same as in the version not supporting the status management function:

The Status Server service has stopped.

The Status Server service has started, but the status management function cannot correctly recognize the status of the service.#3

When the status management function is disabled or the version does not support the status management function:

Active: Operating

Inactive: Unable to connect for communication or is stopped

Comm Err: Able to connect for communication, but not responding

Timeout: Communication connection timeout

Error: An error other than a communication connection timeout error occurred. For details about the error, see the common message log.

#1

This is displayed when the -v option is not specified.

#2

This is displayed when the -v option is specified.

#3

For the function to correctly recognize the status of the service, the service must be restarted.

Usage example 1

This example displays a list of the services of all Performance Management programs in the system:

jpctool service list -id * -host *

Usage example 2

This example displays a list of the services at the host02 host of PFM - Agent for Platform (Windows):

jpctool service list -id * -host host02

Usage example 3

This example displays the service name for the product name.

jpctool service list -id * -v

Usage example 4

This example displays a list of all Performance Management program services including PFM - Web Console, running on the local host.

jpctool service list -key all

Output example

When the command is executed in Format 1 on a host that does not support status management function (when the -v option is not specified)

When the command is executed in Format 1 on a host that supports status management function (when the -v option is not specified)

When the command is executed in Format 1 on a host that supports status management function (when the -v option is specified)

When the command is executed in Format 2 on a host that supports status management function (when the all argument is specified for the -key option)

jpctool service register

Format

jpctool service register   -id service-ID
                          [-host host-name]
                          [-lhost logical-host-name]

Function

The jpctool service register command re-registers into Performance Management the service information for a deleted Performance Management program.

Normally, the jpctool service delete command, which deletes service information, cannot delete service information that is active. However, such service information can be deleted if the service's activation status cannot be verified because of a communication error, etc. If active service information has been inadvertently deleted because of a communication error, etc., you can use the jpctool service register command to re-register the service's information after the communication error has been corrected.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

User with Backup Operators permission

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-id service-ID

Specifies a service ID. For service-ID, specify a string of 1 to 258 bytes.

You can use a wildcard character to specify multiple service IDs. In this case, processing of the remaining services continues, even if an error occurs on one service. If errors occur on multiple services, the command returns a value for the last error that occurred.

-host host-name

Specifies a host name if service information for a specific host is to be re-registered. For host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this option, the local host is assumed.

You can use a wildcard character to specify multiple host names.

-lhost logical-host-name

Specifies a logical host name if this command is to be executed by a host in a logical host environment, not in the physical host environment. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters. If you omit this specification, the physical host is assumed. Wildcard characters cannot be used.

Notes

Arguments must be specified in the order that they appear in the description. Otherwise, they will not be recognized correctly.

This command cannot be executed if the Name Server service, Master Manager service, or the specified service are stopped.

If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

Service information for the Name Server and Status Server services cannot be registered.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

One or more of the specified services is not active.

5

PFM - Manager has not been installed.

7

The specified service ID belongs to the Name Server or Status Server service.

100

The Performance Management environment is invalid.

101

Name Server service, Master Manager service, or the specified service is not active.

102

The specified logical host name has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

220

A host name specified in the service configuration information file is invalid.

222

A communication error occurred.

255

An unexpected error occurred.

Usage example

This example re-registers the service information of all Performance Management programs at the host03 host:

jpctool service register -id * -host host03

jpctool service sync

Format

jpctool service sync     [-lhost logical-host-name]

Function

The jpctool service sync command synchronizes the service information between PFM - Manager and PFM - Web Console.

After the service information about agents registered in Performance Management is deleted on the PFM - Manager host, the change (deletion) is applied to PFM - Web Console when this command is executed.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

Arguments

-lhost logical-host-name

If you execute this command in a logical host environment rather than in a physical host environment, specify this option to specify the name of the logical host. For logical-host-name, specify a string of 1 to 32 bytes, consisting of single-byte alphanumeric characters with no space characters. If you omit this option, the command will be executed on the physical host. Wildcard characters cannot be used.

Notes

You can execute this command only when PFM - Manager is running.

Agents added to the User Agents tree in PFM - Web Console cannot be deleted by executing this command. The icons of these agents are dimmed when this command is executed. If you do not want these agents to be displayed, delete them manually.

To enable the deletion of service information, execute this command, and then perform one of the following operations:

When the PFM - Web Console version is earlier than 09-10-05:

Restart PFM - Manager and PFM - Web Console.

When the PFM - Web Console version is 09-10-05 or later:

Redisplay the agent hierarchy in the PFM - Web Console window.

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

4

A startup or termination command, or other setup command, has been executed on the same machine.

5

PFM - Manager has not been installed.

100

The Performance Management environment is invalid.

101

The PFM - Manager service has not started.

102

The specified logical host has not been set up.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

A file or directory cannot be accessed.

255

An unexpected error occurred.

Usage example

This example synchronizes agent service information when PFM - Manager is running on a physical host.

jpctool service sync

jpcwagtsetup

Format

jpcwagtsetup

Function

The jpcwagtsetup command is executed when a new PFM - Agent or PFM - RM host is added to the Performance Management system to register the information about that host in PFM - Web Console. Note that you need to execute this command only when the version of PFM - Web Console is earlier than 09-00. If that version is 09-00 or later, the information about PFM - Agent and PFM - RM hosts is automatically registered in PFM - Web Console.

Before you execute this command, copy the setup archive files for the PFM - Agent or PFM - RM to be added to the PFM - Web Console execution environment, to the setup directory under the directory in which PFM - Web Console is installed. After this command has executed, you must restart the PFM - Web Console service.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Notes

Do not specify any arguments in the jpcwagtsetup command. If any argument is specified, the command results in an error.

Return values

0

Processing for all archive files terminated normally.

1

The setup directory or the descriptions directory does not exist.

2

The user does not have execution permission for the command.

3

An error occurred during archive file processing.

4

The destination directory for copying the image file does not exist.

5

No archive file exists.

6

An argument is invalid.

7

A memory shortage occurred.

8

An unexpected error occurred.

jpcwbackup

Format

jpcwbackup      -d backup-data-storage-directory

Function

The jpcwbackup command creates a backup file for the definition information of PFM - Web Console in a specified directory.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

User with Backup Operators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-d backup-data-storage-directory

Specifies the directory in which backed up definition information is to be stored. The directory can be specified with either a relative path or absolute path, but must satisfy the following conditions:

The directory exists on the local disk.

The directory is empty.

The administrator can access the directory.

The path name is not longer than 35 characters (in Windows) or 35 bytes (in UNIX). If a relative path of the directory is specified, this limitation also applies if it is converted to the absolute path of the directory.

The name of the directory does not use any characters other than single-byte alphanumeric characters, single-byte spaces, and the following symbols:

! # $ % + . - / : = @ [ \ ] _ { } ( )

If the name includes spaces and the following symbols, they are enclosed in double quotation marks ("): ( ) ! =

If an exclamation mark (!) is include in a directory name, a caret (^) is added as an escape character immediately before the exclamation mark (!).

Do not specify a network directory.

Notes

Do not execute multiple instances of this command concurrently.

While this command is being executed, do not perform any subsequent operations that change a definition or configuration:

Any CLI operations that require the administrator role

Any GUI operations that can be performed by administrators only

If a definition or configuration is changed during execution of this command, the command might fail with a return value of 235.

If this occurs, re-execute the command, making sure that you do not change a definition or configuration during command execution.

If you save the backup data storage directory to a directory whose path name is long, the path length of files might exceed the maximum (Windows: 255 characters, UNIX: 1,023 bytes). If the path length of files exceeds the maximum, the paths of these files are automatically shortened, making it impossible to restore these files.

The config.xml file is reloaded when the PFM - Web Console service is restarted. Therefore, after the file has been changed, if the file is backed up before that service is restarted, the system might be unable to operate correctly when the file is restored from the backed up file.

If an error occurs during execution of this command and backup processing stops, data might remain in the backup directory. Before you re-execute the command, delete any remaining data from the backup directory.

In a cluster configuration, execute this command on both the executing host and the standby host.

When this command is executed on the standby host, a KAVJT6551-W message is always output because the command cannot access the environment directory. However, the user does not need to take any action.

Assume, in a UNIX environment, that you have changed the path of the directory containing bookmarks and process monitoring templates to a path that includes characters other than 7-bit ASCII codes by changing the specification in the initialization file (config.xml). If you execute the jpcwbackup command in such a case, make the value of the LANG environment variable equal to that set at the startup of the PFM - Web Console service. If character encoding differs between the startup of the PFM - Web Console service and the execution of the jpcwbackup command, the backup operation might be incorrect.

Return values

0

The command terminated normally.

1

Invalid arguments are specified on the command line.

2

The user does not have execution permission for the command.

3

Creation of a directory failed.

4

The specified directory was not empty.

15

An attempt to access the directory that contains template information for monitoring bookmarks or processes failed.

100

The Performance Management environment is invalid.

101

There are problems with the config.xml file.

200

A memory shortage occurred.

202

A file access error occurred.

210

A disk space shortage occurred.

235

An attempt to back up one or more files failed.

255

An unexpected error occurred.

Usage example

This example executes the command by specifying the /tmp/backup_wc_2012 folder with the -d option.

jpcwbackup -d /tmp/backup_wc_2012

Output result (Console)

>jpcwbackup -d /tmp/backup_wc_2012
KAVJT6501-I  The PFM - Web Console backup of definition information will now start.
The backup of definition information for PFM - Web Console service ended.
The backup of bookmarks information ended.
The backup of processMonitoringTemplates information ended.
KAVJT6502-I  The PFM - Web Console backup of definition information ended normally.

jpcwras

Format

jpcwras      directory-name

Function

The jpcwras command collects data about PFM - Web Console. Use this command if a problem occurs during PFM - Web Console execution. The data collected by using this command is stored in the specified directory.

When a problem occurs, there is other information that is needed, in addition to the information collected by this command. For details on the information to be collected when a problem occurs, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

directory-name

Specifies the name of the directory in which the collected information is to be stored.

For directory-name, you can specify alphanumeric characters, the space character, and the following symbols:

: / \

To include a space character, enclose it in double quotation marks ("). If you do not use double quotation marks, the system assumes the characters preceding to the space character indicate a directory.

When you specify any of the following symbols, enclose it in double quotation marks (") so that it will not be analyzed in Command Prompt.

^ ( ) `

Do not specify in this option a directory name for a removable medium, such as a floppy disk.

Notes

If the jpcwras command is executed more than once concurrently from different prompts, information cannot be acquired correctly. Do not execute this command more than once at a time.

You must specify the arguments in the order they appear in Format.

Specify only the indicated argument. If more arguments are specified, an error results. An error results if no argument is specified.

If the specified directory does not exist, a directory is created with the specified directory name.

Make sure that the directory name is not expressed as a relative path.

Do not specify a directory name using the UNC format.

Do not specify a directory at the PFM - Web Console installation target.

Make sure that the specified directory name does not exceed the maximum path length permitted by the OS. If the specified directory name is too long, files will not be copied or created.

Specify an empty directory that contains no files and has no directories under it.

If a disk space shortage occurs on the specified directory during command execution, the command results in an error. Before executing the command, make sure there is enough disk space.

If an error occurs during file collection, the file or directory that was being collected remains. Delete such remaining files and directories as needed.

In a cluster system, execute this command at all nodes in the cluster system. Also, if the system is operated in a multiple-monitoring environment, execute this command on both the primary and secondary hosts.

When executing the jpcwras command on a Windows environment, note the following regarding required free disk space:

The storage directory specified for the jpcwras command must have the same amount of free disk space as the amount of data collected.

About 50 MB of disk space will be used on the system drive (%SystemDrive% ) for a temporary tablespace.

The following shows an execution example for the jpcwras command.

jpcwras  D:\usr\wras

The data collected by the jpcwras command is assumed to be 200 MB. In this case, the free disk space required for the D:\usr\wras folder is 200 MB. Also, 50 MB of free disk space is temporarily required for the system drive (%SystemDrive% or %SYSTEMROOT%).

When executing the jpcwras command on a UNIX environment, keep the following in mind regarding required free disk space:

The storage directory specified for the jpcwras command must have twice as much free space as the data collected.

The amount of data collected by the jpcwras command is used in the /tmp or /var/tmp directory for tar command processing. Note that the directory used differs depending on the OS environment.

The following shows an execution example for the jpcwras command.

jpcwras  /usr/wras

The data collected by the jpcwras command is assumed to be 100 MB. In this case, the free disk space required for the /usr/wras directory is 200 MB. Note that 100 MB of free disk space is temporarily needed in the /tmp or /var/tmp directory, for the tar command processing.

Return values

0

The command ended normally.

1

The command line format is invalid.

2

The user does not have execution permission for the command.

3

A write error occurred.

5

The destination directory for output is not empty.

7

A memory shortage occurred.

8

An unexpected error occurred.

Usage example

This example collects all information and stores it in the c:\tmp\jpcwras folder:

jpcwras  c:\tmp\jpcwras

jpcwstart

Format

jpcwstart

Function

The jpcwstart command starts the PFM - Web Console services.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Note

Do not specify any arguments in the jpcwstart command. If any argument is specified, the command results in an error.

Return values

0

The services have started.

1

The services have already been started.

2

The user does not have execution permission for the command.

4

The services cannot be started.

5

An argument is invalid.

7

A memory shortage occurred.

8

An unexpected error occurred.

jpcwstop

Format

jpcwstop      [-immediate]

Function

The jpcwstop command stops the PFM - Web Console services.

Hosts that can execute the command

PFM - Web Console

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pcwebcon/tools/

Arguments

-immediate

Specifies if the running process is stopped forcibly. An error will occur when the wrong argument is specified.

For example, when the jpcwstop command is executed on the UNIX version of PFM - Web Console, processing to stop the service might take a significant amount of time, causing the jpcwstop command to fail. As such, specify the -immediate option to make sure that services, including cluster operations, have stopped.

Return values

0

The services have stopped.

2

The user does not have execution permission for the command.

3

The services have already stopped.

4

The services cannot be stopped.

5

An argument is invalid.

7

A memory shortage occurred.

8

An unexpected error occurred.

3 Log Information Output by Performance Management

This chapter describes the log information that is output by Performance Management and its output formats.

3.1 Windows event log (limited to Windows)

Each event that is output by Performance Management is displayed as an application log item in Windows' Event Viewer window. The identifier of an event issued by Performance Management is displayed under Source in the Event Viewer window. For details about the Performance Management event identifiers, see 4.5 List of messages output to syslog and the Windows event log.

This subsection describes the formats of the Performance Management information that is output to the Windows event log. For details about the Windows event log, see the applicable OS documentation.

Output format

Description of items

Item

Description

Length

message-id

Shows the message's ID.

11 bytes

message

Shows the text of the message.

1 to 128 bytes

Output example

3.2 syslog (limited to UNIX)

This subsection describes the format of Performance Management information that is output to syslog. For details about syslog, see the OS manual.

Output format

Description of items

Item

Description

Length

log-output-date-and-time

Shows the date and time of output to the log, in the format month DD hh:mm:ss (local time):

month: Month

DD: Date

hh: Hour

mm: Minute

ss: Second

15 bytes

host-name

Shows the host name.

1 to 255 bytes

program-name

Shows the program name.

1 to 15 bytes

process-ID

Shows the process ID (as a decimal number).

1 to 10 bytes

message-ID

Shows the message's ID.

11 bytes

message

Shows the text of the message.

1 to 128 bytes

Output example

3.3 Common message log

The common message log reports on the status of the Performance Management system and its problems.

The language for the common message log is determined by the LANG environment variable that is set during service start or command execution. Therefore, character strings in multiple language codes might exist.

This subsection describes the format of the Performance Management information that is output to the common message log.

Output format

Description of items

Item

Description

Length

log-output-date-and-time

Shows the date and time of output to the log, in the format YYYY/MM/DD hh:mm:ss (local time):

YYYY: Year

MM: Month

DD: Date

hh: Hour

mm: Minute

ss: Second

19 bytes

program-name

Shows the program name.

8 bytes

process-ID

Shows the process ID (as a right-justified decimal number). For example, 1000 would be displayed as 00001000.

8 bytes

thread-ID

Shows the thread ID (as a right-justified decimal number). For example, 1000 would be displayed as 00001000.

8 bytes

source-file-name

Shows the name of the source file (only the first 15 characters are displayed, even if the source file name consists of more than 15 characters).

15 bytes

row-number

Shows the row number (as a right-justified decimal number). For example, row number 100 would be displayed as 0100.

4 bytes

message-ID

Shows the message's ID.

11 bytes

message

Shows the text of the message.

1 to 128 bytes

Output example

3.4 Operation status log

The operation status log consists of log information output by PFM - Web Console.

This subsection describes the format of information that is output to the operation status log.

Output format

Description of items

Item

Description

Length

number

Log serial number

4 bytes

log-output-date-and-

time

Shows the date and time of output to the log, in the format YYYY/MM/DD hh:mm:ss.sss (local time):

YYYY: Year

MM: Month

DD: Date

hh: Hour

mm: Minute

ss: Second.

sss: Millisecond

23 bytes

program-name

Always shows PFM-WebConsole.

Up to 16 bytes

process-ID

Shows the process ID (hash value assigned to a Runtime instance by JavaVM).

8 bytes

thread-ID

Shows the thread ID (hash value of the java/lang/Thread object).

8 bytes

message-ID

Shows the message's ID.

11 bytes

type

Shows the event type code that indicates the timing of output to the log.

The meanings of the event type codes are as follows:

OC : Object creation

OD : Object deletion

FB : Function start

FE : Function termination

EC : Exception

ER : Error message

PB : Call from another program

PE : Return to another program

: Other

4 bytes

message

Shows the message, in the format [PFM####:%%%:$$]&&&&

The meaning of the values are as follows:

[: Indicates the beginning of the message log ID.

####: Log output number.

This is a 4-digit number in the range 0000 to 9999 that is obtained by counting from 0 the number of times log information has been output. When the number reaches 9999, it starts over at 0000.

:: Indicates a separator.

%%%: PFM - Web Console's event type code.

The meanings of the event type codes are as follows:

FBI: Start of main method

FEI: End of main method

FBS: Start of method

FES: End of method

EC: Exception

ER: Error (-E) message

DP: Debugging information

INF: Information (-I, -Q, -K) message

CAL: Call from another program

RET: Return from another program

:: Indicates a separator.

$$: Log level.

This is a 2-digit number that indicates the trace level of the output message.

The levels indicated by the numbers are as follows:

01: FATAL

10: WARN

20: DEBUG

30: TRACE

]: Indicates the end of the message log ID.

&&&&: Message text.

Up to 1,023 bytes

Legend:

: One-byte space

Output example:

4 Messages

This chapter describes message formats and output destinations for PFM - Manager, PFM - Web Console, and the health check agent. This chapter also provides lists of the messages output to syslog and the Windows event log, and describes the messages.

4.1 Message types

The following table lists the manuals that describe various messages. For details about the messages, see the manuals provided with individual products.

Table 4‒1: Message description manuals

Message IDs

Product manual

KAVE00001 to KAVE09999

Job Management Partner 1/Performance Management Reference

KAVJA0001 to KAVJZ9999

KAVL15000 to KAVL15999

KAVF10000 to KAVF10999

Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for UNIX systems

KAVF11000 to KAVF11999

Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference, for Windows systems

KAVF12000 to KAVF12999

Job Management Partner 1/Performance Management - Agent Option for Oracle Description, User's Guide and Reference

KAVF14000 to KAVF14999

Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference

KAVF16000 to KAVF16999

Job Management Partner 1/Performance Management - Agent Option for Service Response Description, User's Guide and Reference

KAVF17000 to KAVF17999

Job Management Partner 1/Performance Management - Agent Option for Job Management Description, User's Guide and Reference

KAVF21000 to KAVF21999

Job Management Partner 1/Performance Management - Agent Option for SQL Server Description, User's Guide and Reference

KAVL16000 to KAVL16999

Job Management Partner 1/Performance Management - Agent Option for Virtual Machine Description, User's Guide and Reference

KAVL17000 to KAVL17999

Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

KAVL18000 to KAVL18999

Job Management Partner 1/Performance Management - Remote Monitor for Oracle Description, User's Guide and Reference

KAVL19000 to KAVL19999

Job Management Partner 1/Performance Management - Remote Monitor for Microsoft(R) SQL Server Description, User's Guide and Reference

KAVL20000 to KAVL20999

Job Management Partner 1/Performance Management - Remote Monitor for Virtual Machine Description, User's Guide and Reference

4.2 Message formats

This section shows the formats of messages issued by PFM - Manager, PFM - Web Console, and the health check agent. It also defines the descriptive notations used in this manual to explain messages.

4.2.1 Message output formats

This subsection describes the output formats of messages issued by PFM - Manager, PFM - Web Console, and the health check agent. Each message consists of a message ID followed by a message text. The message formats are shown and explained below.

(1) Messages issued by PFM - Manager

KAVEnnnnn-Y message-text

The message ID consists of the following elements:

K

Indicates the system identifier.

AVE

Indicates a PFM - Manager message.

nnnnn

Indicates a serial number assigned to the message. PFM - Manager message numbers are in the range 00001 to 09999.

Y

Indicates the type of message:

E: Error

Processing is cancelled.

W: Warning

Processing resumes once the message has been output.

I: Information

Information provided to the user by the system.

Q: Response

The system is prompting the user to enter a response.

The following explains the correspondence between the message types and the syslog priority levels:

-E

Level: LOG_ERR

Description: Error message

-W

Level: LOG_WARNING

Description: Warning message

-I

Level: LOG_INFO

Description: Additional information message

-Q

(Not output)

The following explains the correspondence between the message types and the Windows event log types:

-E

Level: Error

Description: Error message

-W

Level: Warning

Description: Warning message

-I

Level: Information

Description: Additional information message

-Q

(Not output)

(2) Messages issued by PFM - Web Console

KAVJxmnnn-z message-text

The message ID consists of the following elements:

KAVJ

Indicates a PFM - Web Console message.

x

Indicates the package ID, as described in the following table:

Package ID

Package name

Description

A

app

Application

C

cache

Information cache

D

draw

Draw module

E

export

CSV export

F

form

Bean action form

H

desc

Description module

I

init

Initialization

J

jsp

JSP

K

cmd

Command

L

logging

Logging

S

servlets

Servlet

T

tools

Tool

V

vsa

ViewServerAccess

Z

Common

Common to PFM - Web Console that does not depend on packages

m

Indicates the message type:

0 to 4: Error (E)

5 to 7: Information (I) or Warning (W)

8: Response (Q)

9: Under processing (K)

nnn

Indicates a serial number assigned to the message. PFM - Web Console message numbers are in the range 000 to 999.

z

Indicates the type of message (as an alphabetic character):

E: Error (trace level Fatal)

Processing is cancelled.

I: Information (trace level Warn)

Information provided to the user by the system.

W: Warning (trace level Warn)

The system notifies the user of a warning.

Q: Response (trace level Warn)

The system is prompting the user to enter a response.

K: Processing (trace level Warn)

Processing resumes once the message has been output.

(3) Messages issued by the health check agent

KAVLnnnnn-Y message-text

The message ID consists of the following elements:

K

Indicates the system identifier.

AVL

Indicates a health check agent message.

nnnnn

Indicates a serial number assigned to the message. Health check agent message numbers are in the range 15000 to 15999.

Y

Indicates the type of message:

E: Error

Processing is cancelled.

W: Warning

Processing resumes once the message has been output.

I: Information

Information provided to the user by the system.

4.3 Message description format

This subsection describes the notations used in this manual to explain the messages. The portion of a message text that is shown in italics represents variable information that depends on the situation. The manual lists the messages in the order of the message IDs. The following is an example of a message explanation:

message-ID

message-text

Explanation of the message

(S)

Describes the processing performed by the system.

(O)

Describes the action the operator should take when the message is displayed.

Reference note

When a problem occurs during operation, you should collect log information by referring to the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

Start your investigation of the problem by referring to the OS log information (Windows event log for Windows and syslog for UNIX) and the logs that are output by PFM - Manager or PFM - Web Console. In these types of log information, check the details for the time period during which the problem occurred, and take appropriate measures to avoid or correct the problem. Also record the nature of the operations leading up to the problem. Also attempt to determine whether or not the problem recurs.

4.4 Message output destinations

This section contains a list of output destinations for the messages output by PFM - Manager and PFM - Web Console.

4.4.1 Output destinations for PFM - Manager messages

This subsection lists in table format the output destinations for the messages output by PFM - Manager.

The table uses the following notations:

Legend:

Y: Destination to which the indicated messages are output.

blank: Destination to which the indicated messages are not output.

Table 4‒2: Output destinations for PFM - Manager messages

Message IDs

Output destinations

syslog

Windows event log

Common message log

Operation status log

Trace log

Standard output

Standard error output

JP1 system event#1

Agent event#2

KAVE00001 to

KAVE00016

Y

Y

Y

KAVE00017 to

KAVE00020

Y

KAVE00021 to

KAVE00023

Y

Y

Y

KAVE00024 to

KAVE00027

Y

KAVE00028 to

KAVE00105

Y

Y

Y

KAVE00106

Y

KAVE00107 to

KAVE00108

Y

Y

Y

KAVE00109 to

KAVE00111

Y

KAVE00113 to

KAVE00114

Y

KAVE00115 to

KAVE00128

Y

Y

Y

KAVE00131

Y

Y

Y

KAVE00132

Y

KAVE00133 to

KAVE00134

Y

Y

Y

KAVE00135

Y

KAVE00137 to

KAVE00141

Y

Y

Y

KAVE00142 to

KAVE00156

Y

KAVE00157

Y

Y

Y

KAVE00158 to

KAVE00159

Y

KAVE00160 to

KAVE00164

Y

Y

Y

KAVE00165

Y

KAVE00166 to

KAVE00176

Y

Y

Y

KAVE00178 to

KAVE00180

Y

KAVE00181 to

KAVE00182

Y

Y

Y

KAVE00183 to

KAVE00192

Y

KAVE00193 to

KAVE00200

Y

Y

Y

KAVE00201 to

KAVE00202

Y

Y

Y

KAVE00203

Y

Y

KAVE00205 to

KAVE00206

Y

Y

Y

KAVE00207 to

KAVE00216

Y

KAVE00217 to

KAVE00219

Y

KAVE00220 to

KAVE00233

Y

KAVE00234 to KAVE00238

Y

Y

Y

KAVE00239 to

KAVE00251

Y

KAVE00252 to

KAVE00254

Y

Y

Y

KAVE00255 to

KAVE00310

Y

KAVE00311 to KAVE00315

Y

KAVE00316 to KAVE00319

Y

Y

Y

KAVE00320 to KAVE00323

Y

KAVE00324

Y

Y

Y

KAVE00325 to KAVE00327

Y

KAVE00328 to KAVE00330

Y

Y

Y

KAVE00331 to KAVE00332

Y

KAVE00333 to KAVE00337

Y

KAVE00338

Y

KAVE00339

Y

Y

KAVE00342 to KAVE00343

Y

KAVE00344 to KAVE00347

Y

Y

KAVE00348 to KAVE00361

Y

KAVE00363 to KAVE00373

Y

KAVE00374

Y

Y

KAVE00375 to KAVE00381

Y

KAVE00390 to KAVE00425

Y

KAVE00428 to KAVE00429

Y

Y

KAVE00430 to KAVE00483

Y

KAVE00485

Y

Y

Y

KAVE00487

Y

KAVE00493

Y

KAVE00500 to KAVE00508

Y

KAVE00509 to KAVE00512

Y

Y

KAVE00515 to KAVE00531

Y

KAVE00532

Y

Y

Y

KAVE00999

Y

Y

Y

KAVE04902

Y

Y

KAVE05000 to

KAVE05034

Y

Y

KAVE05035

Y

KAVE05036 to

KAVE05038

Y

Y

KAVE05039 to

KAVE05040

Y

KAVE05041 to

KAVE05068

Y

Y

KAVE05069 to

KAVE05070

Y

Y

KAVE05071

Y

Y

KAVE05078 to

KAVE05079

Y

Y

KAVE05080 to

KAVE05081

Y

Y

KAVE05082

Y

Y

KAVE05083 to

KAVE05084

Y

Y

KAVE05085 to

KAVE05086

Y

Y

KAVE05087

Y

Y

KAVE05088

Y

Y

KAVE05089

Y

KAVE05090

Y

Y

KAVE05091 to

KAVE05101

Y

Y

KAVE05102 to

KAVE05105

Y

KAVE05106 to

KAVE05124

Y

Y

KAVE05125 to

KAVE05126

Y

Y

KAVE05127 to

KAVE05135

Y

Y

KAVE05136

Y

Y

KAVE05137 to

KAVE05138

Y

Y

KAVE05139 to

KAVE05140

Y

Y

KAVE05141 to

KAVE05145

Y

Y

KAVE05146

Y

KAVE05147 to

KAVE05149

Y

Y

KAVE05150 to

KAVE05153

Y

KAVE05154

Y

Y

KAVE05155 to

KAVE05158

Y

Y

KAVE05159 to

KAVE05161

Y

Y

KAVE05162

Y

Y

KAVE05163 to KAVE05165

Y

Y

KAVE05166 to KAVE05172

Y

Y

KAVE05173

Y

Y

KAVE05174

Y

Y

KAVE05175 to KAVE05217

Y

Y

KAVE05222 to

KAVE05226

Y

KAVE05227 to

KAVE05232

Y

Y

KAVE05233

Y

Y

KAVE05234 to

KAVE05237

Y

Y

KAVE05238

Y

Y

KAVE05239 to

KAVE05241

Y

KAVE05242 to

KAVE05247

Y

Y

KAVE05248

Y

Y

Y

KAVE05249 to

KAVE05253

Y

Y

KAVE05254 to

KAVE05263

Y

Y

KAVE05264 to

KAVE05314

Y

Y

KAVE05315

Y

KAVE05337

Y

Y

KAVE05338 to KAVE05340

Y

Y

KAVE05342 to KAVE05345

Y

Y

KAVE05346 to KAVE05347

Y

Y

KAVE05348 to KAVE05350

Y

Y

KAVE05351 to KAVE05354

Y

Y

KAVE05355

Y

Y

KAVE05356

Y

Y

KAVE05357

Y

Y

KAVE05358

Y

Y

KAVE05359 to KAVE05362

Y

Y

KAVE05363

Y

Y

KAVE05367 to KAVE05368

Y

Y

KAVE05369

Y

Y

KAVE05373

Y

Y

KAVE05374

Y

Y

KAVE05376 to KAVE05377

Y

Y

KAVE05378

Y

Y

KAVE05382 to KAVE05383

Y

Y

KAVE05385

Y

Y

KAVE05386

Y

Y

KAVE05387

Y

Y

KAVE05390

Y

Y

KAVE05391

Y

KAVE05392 to KAVE05395

Y

Y

KAVE05396

Y

Y

KAVE05397

Y

Y

KAVE05399 to KAVE05408

Y

Y

KAVE05409 to KAVE05410

Y

Y

KAVE05412 to KAVE05415

Y

Y

KAVE05416

Y

Y

KAVE05417

Y

Y

KAVE05418

Y

KAVE05419

Y

Y

KAVE05420 to KAVE05421

Y

Y

KAVE05422

Y

Y

KAVE05423

-

Y

KAVE05424 to KAVE05425

Y

Y

KAVE05426 to KAVE05428

Y

Y

KAVE05429

Y

Y

KAVE05430 to KAVE05434

Y

Y

KAVE05435 to KAVE05436

Y

Y

KAVE05437 to KAVE05440

Y

Y

KAVE05441

Y

Y

KAVE05442

Y

KAVE05443

Y

Y

KAVE05444 to KAVE05445

Y

Y

KAVE05446

Y

Y

KAVE05447 to KAVE05448

Y

Y

KAVE05449

Y

Y

KAVE05450

-

Y

KAVE05451

Y

Y

KAVE05452 to KAVE05454

Y

Y

KAVE05455 to KAVE05459

Y

Y

KAVE05460

Y

Y

KAVE05470

Y

Y

KAVE05471

Y

Y

KAVE05472

Y

Y

KAVE05473

Y

Y

KAVE05474

Y

Y

KAVE05475

Y

Y

KAVE05476

Y

Y

KAVE05477 to KAVE05481

Y

Y

KAVE05482 to KAVE05486

Y

Y

KAVE05487 to KAVE05488

Y

Y

KAVE05489 to KAVE05490

Y

Y

KAVE05491 to KAVE05492

Y

Y

KAVE05801

Y

Y

KAVE05810 to

KAVE05817

Y

Y

KAVE05821

Y

Y

KAVE05822

Y

KAVE05823

Y

Y

KAVE05832 to

KAVE05833

Y

Y

KAVE05834

Y

KAVE05835 to

KAVE05836

Y

Y

KAVE05837

Y

Y

KAVE05838 to

KAVE05839

Y

Y

KAVE05840

Y

Y

KAVE05841 to

KAVE05842

Y

Y

KAVE05843

Y

Y

KAVE05844 to

KAVE05845

Y

Y

KAVE05846

Y

Y

KAVE05847 to

KAVE05848

Y

Y

KAVE05849

Y

Y

KAVE05850

Y

Y

KAVE05851

Y

Y

KAVE05852

Y

Y

KAVE05853

Y

Y

KAVE05854

Y

Y

KAVE05855

Y

Y

KAVE05856

Y

Y

KAVE05857

Y

Y

KAVE05858

Y

Y

KAVE05859 to

KAVE05865

Y

Y

KAVE05867 to

KAVE05868

Y

Y

KAVE05871 to

KAVE05872

Y

Y

KAVE05873 to

KAVE05874

Y

KAVE05875 to

KAVE05882

Y

Y

KAVE05883

Y

KAVE05900 to

KAVE05902

Y

Y

KAVE05904 to

KAVE05905

Y

Y

KAVE05906

Y

Y

KAVE05908 to

KAVE05914

Y

Y

KAVE05915

Y

Y

KAVE05916 to

KAVE05917

Y

Y

KAVE05918 to

KAVE05931

Y

Y

KAVE05944 to KAVE05945

Y

Y

KAVE05946 to KAVE05947

Y

Y

KAVE05948 to KAVE05950

Y

Y

KAVE05951 to KAVE05957

Y

Y

KAVE05958 to KAVE05961

Y

Y

KAVE05962 to KAVE05963

Y

Y

KAVE05964 to KAVE05970

Y

Y

KAVE05971

Y

Y

KAVE05972 to KAVE05973

Y

KAVE05974

Y

Y

KAVE06000 to

KAVE06006

Y

KAVE06007 to

KAVE06008

Y

Y

KAVE06009 to

KAVE06010

Y

KAVE06011

Y

KAVE06013

Y

KAVE06014 to

KAVE06015

Y

Y

KAVE06016

Y

Y

KAVE06017

Y

KAVE06018 to

KAVE06021

Y

Y

KAVE06022

Y

Y

KAVE06023 to

KAVE06024

Y

Y

KAVE06025 to

KAVE06026

Y

Y

KAVE06027 to KAVE06028

Y

Y

KAVE06029 to KAVE06039

Y

KAVE06040 to KAVE06041

Y

KAVE06046

Y

Y

KAVE06047 to KAVE06048

Y

Y

KAVE06049

Y

Y

KAVE06050 to KAVE06051

Y

Y

KAVE06052 to KAVE06056

Y

Y

KAVE06057 to KAVE06058

Y

Y

Y

KAVE06059 to KAVE06062

Y

Y

KAVE06063 to KAVE06064

Y

Y

Y

KAVE06065 to KAVE06067

Y

Y

KAVE06069

Y

Y

KAVE06071 to KAVE06075

Y

Y

KAVE06076

Y

KAVE06077 to KAVE06082

Y

Y

KAVE06083

Y

Y

Y

Y

KAVE06084 to KAVE06096

Y

Y

KAVE06097

Y

Y

Y

Y

KAVE06098

Y

Y

KAVE06117 to KAVE06118

Y

Y

KAVE06119

Y

Y

KAVE06120

Y

Y

KAVE06121 to KAVE06131

Y

Y

KAVE06132 to KAVE06133

Y

Y

KAVE06134 to KAVE06135

Y

Y

KAVE06136 to KAVE06137

Y

Y

KAVE06138

Y

Y

KAVE06139 to KAVE06140

Y

Y

KAVE06141 to KAVE06142

Y

Y

KAVE06143 to KAVE06145

Y

Y

KAVE06146

Y

Y

KAVE06147 to KAVE06148

Y

Y

KAVE06149

Y

Y

KAVE06150

Y

Y

KAVE06151 to KAVE06161

Y

Y

KAVE06171 to KAVE06172

Y

Y

KAVE06173 to KAVE06174

Y

Y

KAVE06175 to KAVE06178

Y

Y

KAVE06180

Y

Y

KAVE06181 to KAVE06182

Y

KAVE06183

Y

Y

KAVE06184 to KAVE06185

Y

Y

KAVE06186

Y

Y

KAVE06187

Y

Y

KAVE06188

Y

KAVE06189

Y

KAVE06190 to KAVE06194

Y

Y

KAVE07000 to

KAVE07999

Y

KAVL15000 to

KAVL15013

Y

Y

Y

KAVL15014 to KAVL15019

Y

KAVL15020 to KAVL15022

Y

KAVL15100 to

KAVL15104

Y

Y

Y

KAVL15105

Y

#1

JP1 system events notify JP1/IM about agent status changes. For details on JP1 system events, see the chapter that explains operation monitoring linked with the integrated management program (JP1/IM) in the Job Management Partner 1/Performance Management User's Guide.

The following table lists the programs that are required to issue JP1 system events.

Table 4‒3: Programs that are required to issue JP1 system events

Host type

Required programs

Version

Monitoring manager

PFM - Manager

09-00 or later

Monitoring console server

PFM - Web Console

08-00 or later

Monitoring agent

PFM - Agent

08-00 or later

(To issue PFM - Agent events, 09-00 or later is required)

PFM - Manager or PFM - Base

09-00 or later

JP1/Base

09-00 or later

#2

Agent events notify PFM - Manager about agent status changes. For details on agent events, see the chapter that describes how to display events in the Job Management Partner 1/Performance Management User's Guide.

The following table lists the programs that are required to issue agent events.

Table 4‒4: Programs that are required to issue agent events

Host type

Required programs

Version

Monitoring manager

PFM - Manager

09-00 or later

Monitoring console server

PFM - Web Console

08-00 or later

Monitoring agent

PFM - Agent

09-00 or later

PFM - Manager or PFM - Base

09-00 or later

4.4.2 Output destinations for PFM - Web Console messages

This subsection lists in table format the output destinations for the messages output by PFM - Web Console.

The table uses the following notations:

Legend:

Y: Destination to which the indicated messages are output.

blank: Destination to which the indicated messages are not output.

Message IDs

Output destinations

syslog/event log

Operation status log

Standard output

Standard error output

KAVJA0001 to

KAVJA5004

Y

KAVJF2501 to

KAVJF2502

Y

Y

KAVJH0001 to

KAVJH0002

Y

Y

Y

KAVJH0003 to

KAVJH0005

Y

Y

KAVJH2501 to

KAVJH2504

Y

KAVJJ0001 to

KAVJJ6611

Y

KAVJJ6612

Y

Y

KAVJJ8001 to KAVJJ8661

Y

KAVJK0001 to

KAVJK0626

Y

Y

KAVJK2501 to

KAVJK2506

Y

KAVJK2507 to

KAVJK2549

Y

Y

KAVJK2550

Y

KAVJK2551 to KAVJK4002

Y

Y

KAVJK5001

Y

KAVJK6503 to KAVJK6523

Y

Y

KAVJK6701 to KAVJK8601

Y

KAVJK8604 to KAVJK8609

Y

Y

KAVJL5001

Y

KAVJS0001 to

KAVJS0009

Y

Y

KAVJS0010

Y

Y

Y

KAVJS0011 to

KAVJS4004

Y

Y

KAVJS4006

Y

Y

KAVJS4007

Y

Y

Y

KAVJS4008 to

KAVJS4015

Y

Y

KAVJS4016

Y

Y

KAVJS4017 to

KAVJS6563

Y

Y

KAVJS6564

Y

KAVJS6565 to KAVJS6570

Y

Y

KAVJS6701 to

KAVJS6702

KAVJS6703 to KAVJS6705

Y

Y

KAVJS6801

Y

KAVJT0003 to

KAVJT0023

Y

KAVJT2501 to

KAVJT2516

Y

KAVJT5001 to

KAVJT5010

Y

KAVJT6501 to

KAVJT6551

Y

KAVJV2501 to

KAVJV2551

Y

KAVJV2552 to KAVJV2564

Y

Y

KAVJV2701

Y

KAVJV4001 to

KAVJV4002

Y

Y

KAVJV4003 to

KAVJV5005

Y

KAVJV5006

Y

Y

KAVJV9001 to

KAVJV9502

Y

KAVJZ0998 to

KAVJZ0999

Y

KAVJZ5001 to

KAVJZ5002

Y

KAVJZ5003

Y

Y

KAVJZ5010 to

KAVJZ5999

Y

4.5 List of messages output to syslog and the Windows event log

This section lists the message information that is output by PFM - Manager or PFM - Web Console to syslog or the Windows event log.

syslog refers to the syslog file. For the storage location of the syslog file, see the syslog daemon configuration file (the default is /etc/syslogd.conf).

The Windows event log is displayed at the following location:

For Windows Server 2003 and Windows Server 2008

The Windows event log is displayed in the application log of the Event Viewer window.

The Event Viewer window can be displayed by choosing Administrative Tools and then Event Viewer, which are displayed from the Windows Start menu.

For Windows Server 2012

The Windows event log is displayed in the application log of the Event Viewer window.

To display the Event Viewer window, display the Start screen from the desktop, and select Administrative Tools and then Event Viewer.

In the case of an event that is output by PFM - Manager or PFM - Web Console, the identifier PFM is displayed for Source in the Event Viewer window. For details about the identifiers for PFM - Agent or PFM -RM, see the description about identifiers in the appendix of each PFM - Agent or PFM - RM manual.

4.5.1 Output destinations for PFM - Manager messages

The following table lists the message information that is output by PFM - Manager to syslog and to the Windows event log.

Table 4‒5: List of message information output to syslog and the Windows event log

Message ID

Syslog

Windows event log

Facility

Level

Event ID

Type

KAVE00001-I

LOG_DAEMON

LOG_INFO

1

Information

KAVE00002-I

LOG_DAEMON

LOG_INFO

2

Information

KAVE00003-I

LOG_DAEMON

LOG_INFO

3

Information

KAVE00004-I

LOG_DAEMON

LOG_INFO

4

Information

KAVE00005-I

LOG_DAEMON

LOG_INFO

5

Information

KAVE00006-I

LOG_DAEMON

LOG_INFO

6

Information

KAVE00007-I

LOG_DAEMON

LOG_INFO

7

Information

KAVE00008-I

LOG_DAEMON

LOG_INFO

8

Information

KAVE00009-I

LOG_DAEMON

LOG_INFO

9

Information

KAVE00010-I

LOG_DAEMON

LOG_INFO

10

Information

KAVE00011-I

LOG_DAEMON

LOG_INFO

11

Information

KAVE00012-I

LOG_DAEMON

LOG_INFO

12

Information

KAVE00013-I

LOG_DAEMON

LOG_INFO

13

Information

KAVE00014-I

LOG_DAEMON

LOG_INFO

14

Information

KAVE00015-I

LOG_DAEMON

LOG_INFO

15

Information

KAVE00016-I

LOG_DAEMON

LOG_INFO

16

Information

KAVE00021-I

LOG_DAEMON

LOG_INFO

21

Information

KAVE00022-I

LOG_DAEMON

LOG_INFO

22

Information

KAVE00023-I

LOG_DAEMON

LOG_INFO

23

Information

KAVE00028-I

LOG_DAEMON

LOG_INFO

28

Information

KAVE00029-I

LOG_DAEMON

LOG_INFO

29

Information

KAVE00100-E

LOG_DAEMON

LOG_ERR

100

Error

KAVE00101-E

LOG_DAEMON

LOG_ERR

101

Error

KAVE00102-E

LOG_DAEMON

LOG_ERR

102

Error

KAVE00103-E

LOG_DAEMON

LOG_ERR

103

Error

KAVE00104-E

LOG_DAEMON

LOG_ERR

104

Error

KAVE00105-E

LOG_DAEMON

LOG_ERR

105

Error

KAVE00107-E

LOG_DAEMON

LOG_ERR

107

Error

KAVE00115-E

LOG_DAEMON

LOG_ERR

115

Error

KAVE00116-E

LOG_DAEMON

LOG_ERR

116

Error

KAVE00117-E

LOG_DAEMON

LOG_ERR

117

Error

KAVE00118-E

LOG_DAEMON

LOG_ERR

118

Error

KAVE00119-E

LOG_DAEMON

LOG_ERR

119

Error

KAVE00120-E

LOG_DAEMON

LOG_ERR

120

Error

KAVE00121-E

LOG_DAEMON

LOG_ERR

121

Error

KAVE00122-E

LOG_DAEMON

LOG_ERR

122

Error

KAVE00123-E

LOG_DAEMON

LOG_ERR

123

Error

KAVE00126-E

LOG_DAEMON

LOG_ERR

126

Error

KAVE00128-E

LOG_DAEMON

LOG_ERR

128

Error

KAVE00131-E

LOG_DAEMON

LOG_ERR

131

Error

KAVE00133-E

LOG_DAEMON

LOG_ERR

133

Error

KAVE00134-E

LOG_DAEMON

LOG_ERR

134

Error

KAVE00137-E

LOG_DAEMON

LOG_ERR

137

Error

KAVE00138-E

LOG_DAEMON

LOG_ERR

138

Error

KAVE00139-E

LOG_DAEMON

LOG_ERR

139

Error

KAVE00140-E

LOG_DAEMON

LOG_ERR

140

Error

KAVE00141-E

LOG_DAEMON

LOG_ERR

141

Error

KAVE00157-E

LOG_DAEMON

LOG_ERR

157

Error

KAVE00160-E

LOG_DAEMON

LOG_ERR

160

Error

KAVE00161-E

LOG_DAEMON

LOG_ERR

161

Error

KAVE00162-E

LOG_DAEMON

LOG_ERR

162

Error

KAVE00163-E

LOG_DAEMON

LOG_ERR

163

Error

KAVE00164-E

LOG_DAEMON

LOG_ERR

164

Error

KAVE00166-W

LOG_DAEMON

LOG_WARNING

166

Warning

KAVE00167-E

LOG_DAEMON

LOG_ERR

167

Error

KAVE00168-E

LOG_DAEMON

LOG_ERR

168

Error

KAVE00169-E

LOG_DAEMON

LOG_ERR

169

Error

KAVE00170-E

LOG_DAEMON

LOG_ERR

170

Error

KAVE00171-E

LOG_DAEMON

LOG_ERR

171

Error

KAVE00172-E

LOG_DAEMON

LOG_ERR

172

Error

KAVE00173-E

LOG_DAEMON

LOG_ERR

173

Error

KAVE00174-E

LOG_DAEMON

LOG_ERR

174

Error

KAVE00175-E

LOG_DAEMON

LOG_ERR

175

Error

KAVE00176-E

LOG_DAEMON

LOG_ERR

176

Error

KAVE00181-W

LOG_DAEMON

LOG_WARNING

181

Warning

KAVE00182-E

LOG_DAEMON

LOG_ERR

182

Error

KAVE00193-E

LOG_DAEMON

LOG_ERR

193

Error

KAVE00194-E

LOG_DAEMON

LOG_ERR

194

Error

KAVE00195-E

LOG_DAEMON

LOG_ERR

195

Error

KAVE00196-E

LOG_DAEMON

LOG_ERR

196

Error

KAVE00197-E

LOG_DAEMON

LOG_ERR

197

Error

KAVE00198-E

LOG_DAEMON

LOG_ERR

198

Error

KAVE00199-E

LOG_DAEMON

LOG_ERR

199

Error

KAVE00200-E

LOG_DAEMON

LOG_ERR

200

Error

KAVE00201-E

LOG_DAEMON

LOG_ERR

201

Error

KAVE00202-E

LOG_DAEMON

LOG_ERR

202

Error

KAVE00203-W

LOG_DAEMON

LOG_ERR

203

Warning

KAVE00205-W

LOG_DAEMON

LOG_WARNING

205

Warning

KAVE00206-E

LOG_DAEMON

LOG_ERR

206

Error

KAVE00234-I

LOG_DAEMON

LOG_INFO

234

Information

KAVE00235-I

LOG_DAEMON

LOG_INFO

235

Information

KAVE00236-E

LOG_DAEMON

LOG_ERR

236

Error

KAVE00237-E

LOG_DAEMON

LOG_ERR

237

Error

KAVE00238-E

LOG_DAEMON

LOG_ERR

238

Error

KAVE00252-E

LOG_DAEMON

LOG_ERR

252

Error

KAVE00253-E

LOG_DAEMON

LOG_ERR

253

Error

KAVE00254-E

LOG_DAEMON

LOG_ERR

254

Error

KAVE00316-E

LOG_DAEMON

LOG_ERR

316

Error

KAVE00317-W

LOG_DAEMON

LOG_WARNING

317

Warning

KAVE00318-W

LOG_DAEMON

LOG_WARNING

318

Warning

KAVE00319-W

LOG_DAEMON

LOG_WARNING

319

Warning

KAVE00324-W

LOG_DAEMON

LOG_WARNING

324

Warning

KAVE00328-E

LOG_DAEMON

LOG_ERR

328

Error

KAVE00329-E

LOG_DAEMON

LOG_ERR

329

Error

KAVE00330-E

LOG_DAEMON

LOG_ERR

330

Error

KAVE00344-E

LOG_DAEMON

LOG_ERR

344

Error

KAVE00345-E

LOG_DAEMON

LOG_ERR

345

Error

KAVE00346-E

LOG_DAEMON

LOG_ERR

346

Error

KAVE00347-E

LOG_DAEMON

LOG_ERR

347

Error

KAVE00374-E

LOG_DAEMON

LOG_ERR

374

Error

KAVE00532-W

LOG_DAEMON

LOG_WARNING

532

Warning

KAVE00999-E

LOG_DAEMON

LOG_ERR

999

Error

KAVE06083-E

LOG_DAEMON

LOG_ERR

6083

Error

KAVE06097-E

LOG_DAEMON

LOG_ERR

6097

Error

KAVL15000-I

LOG_DAEMON

LOG_INFO

15000

Information

KAVL15001-I

LOG_DAEMON

LOG_INFO

15001

Information

KAVL15002-E

LOG_DAEMON

LOG_ERR

15002

Error

KAVL15003-E

LOG_DAEMON

LOG_ERR

15003

Error

KAVL15004-E

LOG_DAEMON

LOG_ERR

15004

Error

KAVL15005-W

LOG_DAEMON

LOG_WARNING

15005

Warning

KAVL15006-E

LOG_DAEMON

LOG_ERR

15006

Error

KAVL15007-W

LOG_DAEMON

LOG_WARNING

15007

Warning

KAVL15008-E

LOG_DAEMON

LOG_ERR

15008

Error

KAVL15009-E

LOG_DAEMON

LOG_ERR

15009

Error

KAVL15010-E

LOG_DAEMON

LOG_ERR

15010

Error

KAVL15011-E

LOG_DAEMON

LOG_ERR

15011

Error

KAVL15012-E

LOG_DAEMON

LOG_ERR

15012

Error

KAVL15013-E

LOG_DAEMON

LOG_ERR

15013

Error

KAVL15100-E

LOG_DAEMON

LOG_ERR

15100

Error

KAVL15101-E

LOG_DAEMON

LOG_ERR

15101

Error

KAVL15102-E

LOG_DAEMON

LOG_ERR

15102

Error

KAVL15103-E

LOG_DAEMON

LOG_ERR

15103

Error

KAVL15104-E

LOG_DAEMON

LOG_ERR

15104

Error

4.5.2 Output destinations for PFM - Web Console messages

The following table lists the message information that is output by PFM - Manager to syslog and to Windows event log.

Note that event IDs for all the Windows event logs will be 1.

Table 4‒6: List of message information output to syslog and the Windows event log

Message ID

Syslog

Windows event log

Facility

Level

Event ID

Type

KAVJA0001-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0002-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0003-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0004-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0005-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0006-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0007-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0008-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0009-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0010-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0011-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0012-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0013-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0014-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0015-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0016-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA0017-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA2501-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA4001-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA4002-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA4003-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJA5004-I

LOG_DAEMON

LOG_INFO

1

Information

KAVJH0001-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJH0002-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJS0010-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJS4007-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJS4016-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2552-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2553-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2554-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2555-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2556-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2557-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2558-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2559-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2560-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2561-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2562-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2563-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV2564-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV4001-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV4002-E

LOG_DAEMON

LOG_ERR

1

Error

KAVJV5006-I

LOG_DAEMON

LOG_INFO

1

Information

KAVJZ5003-I

LOG_DAEMON

LOG_INFO

1

Information

4.6 Messages

This section lists and describes the messages issued by PFM - Manager and PFM - Web Console and indicates (where applicable) the action to be taken when a message has been output.

KAVE00001-I

Name Server has started. (host=host-name, service=service-ID)

The Name Server service has started.

(S)

Starts the Name Server service's processing.

KAVE00002-I

Name Server has stopped. (host=host-name, service=service-ID)

The Name Server service has stopped.

(S)

Stops the Name Server service's processing.

KAVE00003-I

Master Manager has started. (host=host-name, service=service-ID)

The Master Manager service has started.

(S)

Stops the Master Manager service's processing.

KAVE00004-I

Master Manager has stopped. (host=host-name, service=service-ID)

The Master Manager service has stopped.

(S)

Stops the Master Manager service's processing.

KAVE00005-I

Master Store has started. (host=host-name, service=service-ID)

The Master Store service has started.

(S)

Starts the Master Store service's processing.

KAVE00006-I

Master Store has stopped. (host=host-name, service=service-ID)

The Master Store service has stopped.

(S)

Stops the Master Store service's processing.

KAVE00007-I

Correlator has started. (host=host-name, service=service-ID)

The Correlator service has started.

(S)

Starts the Correlator service's processing.

KAVE00008-I

Correlator has stopped. (host=host-name, service=service-ID)

The Correlator service has stopped.

(S)

Stops the Correlator service's processing.

KAVE00009-I

Action Handler has started. (host=host-name, service=service-ID)

The Action Handler service has started.

(S)

Starts the Action Handler service's processing.

KAVE00010-I

Action Handler has stopped. (host=host-name, service=service-ID)

The Action Handler service has stopped.

(S)

Stops the Action Handler service's processing.

KAVE00011-I

Trap Generator has started. (host=host-name, service=service-ID)

The Trap Generator service has started.

(S)

Starts the Trap Generator service's processing.

KAVE00012-I

Trap Generator has stopped. (host=host-name, service=service-ID)

The Trap Generator service has stopped.

(S)

Stops the Trap Generator service's processing.

KAVE00013-I

View Server has started. (host=host-name, service=service-ID)

The View Server service has started.

(S)

Starts the View Server service's processing.

KAVE00014-I

View Server has stopped. (host=host-name, service=service-ID)

The View Server service has stopped.

(S)

Stops the View Server service's processing.

KAVE00015-I

Openview Object Manager has started. (host=host-name, port=port-number)

The NNM Object Manager service, which updates the object database by monitoring SNMP traps from the Trap Generator service, has started.

(S)

Starts NNM object database synchronization processing.

KAVE00016-I

Openview Object Manager has stopped. (host=host-name, port=port-number)

The NNM Object Manager service, which updates the object database by monitoring SNMP traps from the Trap Generator, has stopped.

(S)

Stops NNM object database synchronization processing.

KAVE00017-I

The status of status-of-the-selected-name was changed by a user request. The new status is specified-status.

The symbol status was changed by the user's status change request.

(S)

Changes the symbol status.

KAVE00018-I

The command ended normally. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id, rc=return-code)

The command defined in the action definition has terminated.

(S)

Terminates the command.

KAVE00019-I

The command was started. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id)

The command defined in the action definition has been started.

(S)

Starts the command.

KAVE00020-I

The e-mail was sent. (alarm=alarm-name, alarm table=alarm-table-name, address=e-mail-address)

The e-mail defined in the action definition has been sent.

(S)

Sends the e-mail.

KAVE00021-I

Agent Store has started. (host=host-name, service=service-ID)

The Agent Store service has started.

(S)

Starts the Agent Store service.

KAVE00022-I

Agent Store has stopped. (host=host-name, service=service-ID)

The Agent Store service has stopped.

(S)

Stops the Agent Store service.

KAVE00023-I

Service was stopped by the forced termination request. (host=host-name, service1=stopped-service-id, service2=request-source-service-id)

The service was stopped by the forced termination request.

(S)

Terminates the service.

KAVE00024-I

Alarm issue: time, agent, host-name, status, alarm-name, alarm-table-name, message-text

The indicated alarm was issued.

(S)

Issues the alarm.

KAVE00025-I

service-name was forcibly stopped. (PID=process-ID)

The indicated service was stopped forcibly by the jpcspm stop command with the kill=immediate option specified.

(S)

Stops the service forcibly.

KAVE00026-I

Manager was successfully connected, so stand-alone mode will now end. (host=host-name, service=service-ID)

The service connected successfully to PFM - Manager, so the stand-alone mode has ended, and the service will now operate in the normal mode.

(S)

Switches the service to the normal mode.

KAVE00027-I

Manager was successfully connected. (host=host-name, service=service-ID)

The service connected to PFM - Manager.

(S)

Updates configuration information for the service.

KAVE00028-I

Status Server has started. (host=host-name, service=service-ID)

The Status Server service has started.

(S)

Starts the Status Server service's processing.

KAVE00029-I

Status Server has stopped. (host=host-name, service=service-ID)

The Status Server service has stopped.

(S)

Stops the Status Server service's processing.

KAVE00100-E

An error occurred in an OS API(API-name). (en=OS-detail-code, arg1=argument-1, arg2=argument-2, arg3=argument-3)

An error occurred in an OS API. The code indicated by en= is the errno of a system call or a Win32 API detailed code.

(S)

Suspends processing.

(O)

Check the OS detail code. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00101-E

An error occurred in a function (function-name). (rc=maintenance-code, arg1=argument-1, arg2=argument-2, arg3=argument-3)

An error occurred in a function being controlled.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00102-E

The system environment is invalid. (rc=maintenance-code)

The system environment is invalid. A system file was deleted illegally or its access permission was changed.

(S)

Suspends processing.

(O)

Re-install Performance Management.

KAVE00103-E

An unexpected exception has occurred. (rc=maintenance-code)

An unexpected error has occurred.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00104-E

Memory is insufficient. (size=allocation-size)

Memory allocation failed due to a memory shortage.

(S)

Suspends processing.

(O)

Close applications that are not being used currently, or increase the memory size. A memory shortage may have caused the service stoppage. Execute the jpctool service list command to check the status of services. If the Master Store or Agent Store service has stopped, the database may have been corrupted. Restore the database from the backup data or re-create the database, and then restart the Master Store or Agent Store service.

If this message is output for the View Server service, the cause of the problem might be due to the available memory size for the View Server service. Enable the report cache filing function or extend the maximum memory size that can be used by the View Server service. For details on how to increase the memory size, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00105-E

The disk capacity is insufficient.

File access failed due to a shortage of disk space.

(S)

Suspends processing.

(O)

Delete unnecessary files or increase the disk capacity.

A disk space shortage may have caused the service stoppage.

The service may have stopped due to a shortage of disk space. Execute the jpctool service list command to check the status of services. If the stopped service is the Master Store service or the Agent Store service, the database might be damaged. Restore the database from the backup data or re-create the database, and then restart the Master Store or Agent Store service.

When a realtime report, a historical report, or an event history is displayed, and this message is output by the Agent Collector service, the Agent Store service, or the Master Store service, there might not be enough free space on the disk containing the directory to which the temporary file is to be output. For details about the output destination directory for temporary files, see the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

KAVE00106-E

An error occurred in the network. (rc=maintenance-code)

An error occurred during TCP/IP communication, or a communication timeout occurred.

(S)

Suspends processing.

(O)

Check the activation status of the remote server and the network status.

KAVE00107-E

The network environment is invalid. (rc=maintenance-code)

TCP/IP initialization failed or socket generation failed.

(S)

Suspends processing.

(O)

Check the local host's network environment and the system environment.

KAVE00109-W

An error occurred in (function-name). Processing continue. (rc=error-message-or-error-code, arg1=argument-1, arg2=argument-2, arg3=argument-3)

An error occurred in the indicated function, but processing continues by skipping the function.

(S)

Skips the process that caused the error and continues processing. Some processes have not terminated normally.

(O)

Eliminate the cause of the error based on the error message or error code. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00110-W

An attempt to acquire the Object OID failed, but processing will continue. (rc=error-message)

The object searched for could not be found in the NNM object database.

(S)

Skips the process for the object in question and continues processing.

(O)

Check the NNM status.

KAVE00111-W

The received trap is ignored because the trap format is invalid. (OID invalid)

The format of the received Performance Management trap is invalid.

(S)

Discards the received trap and continues processing.

(O)

Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00113-E

An attempt to acquire the topology map failed. (rc=error-message)

NNM topology map could not be acquired.

(S)

Terminates with an error.

(O)

Check the NNM settings based on the indicated error message contents.

KAVE00114-E

An attempt to acquire the Object OID failed. (rc=error-message)

The selected object could not be found.

(S)

Terminates with an error.

(O)

Check the NNM settings based on the error message content. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00115-E

An attempt to start Name Server has failed. (host=host-name, service=service-ID)

An attempt to start the Name Server failed.

(S)

Terminates the Name Server service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00116-E

An attempt to start Master Manager has failed. (host=host-name, service=service-ID)

An attempt to start the Master Manager failed.

(S)

Terminates the Master Manager service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00117-E

An attempt to start Master Store has failed. (host=host-name, service=service-ID)

An attempt to start the Master Store failed.

(S)

Terminates the Master Store service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00118-E

An attempt to start Correlator has failed. (host=host-name, service=service-ID)

An attempt to start the Correlator failed.

(S)

Terminates the Correlator service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00119-E

An attempt to start Action Handler has failed. (host=host-name, service=service-ID)

An attempt to start the Action Handler failed.

(S)

Terminates the Action Handler service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00120-E

An attempt to start Trap Generator has failed. (host=host-name, service=service-ID)

An attempt to start the Trap Generator failed.

(S)

Terminates the Trap Generator service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00121-E

An attempt to start View Server has failed. (host=host-name, service=service-ID)

An attempt to start the View Server failed.

(S)

Terminates the View Server service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00122-E

Openview Object Manager could not start.

The system was unable to start the NNM Object Manager service, which updates the object database by monitoring SNMP traps from the Trap Generator.

(S)

Terminates NNM object database synchronization processing.

(O)

Check the cause that is output in the common message log.

KAVE00123-E

An attempt to get the port number failed. (port=service-name-of-port-number)

An attempt to get a port number failed.

(S)

Suspends service start processing.

(O)

In the services file, check whether the port number to be used is assigned to the Performance Management service. If the port number is assigned to another program, use the jpcconf port define command to change the port number.

KAVE00126-E

Invalid entry in jpcsto.ini. (product id=product-id, section=section-name, entry=entry-name)

A specification in the jpcsto.ini file is invalid.

(S)

Suspends the service's start processing.

(O)

Check the contents of the jpcsto.ini file.

KAVE00128-E

Illegal data was detected in the Store database. (db=database-file-name)

An unexpected service stoppage or a machine shutdown created illegal data in the Master Store or Agent Store service database.

(S)

Suspends processing.

(O)

When a backup file is available:

Restore the database from the backup file. For details about backup and restoration, see the chapter that describes backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.

When a backup file is not available:

Stop the Master Store or Agent Store service, then delete the Master Store or Agent Store service's database files (.DB or .IDX extension) and restart the service.

KAVE00129-E

An attempt to acquire report information failed. (msg=event-message)

The report could not be displayed because an attempt to obtain the report information failed.

(S)

Starting of PFM - Web Console will now stop.

(O)

Specify the report in the alarm definition.

KAVE00131-E

The number of open files exceeded the system limit. (rc=maintenance-code)

The file could not be opened because the number of open files exceeded the system limit.

(S)

Suspends processing.

(O)

Close applications that are currently not being used, or increase the system limit. The service may have been stopped because the system limit was exceeded. Execute the jpctool service list command to check the status of services. If the Master Store or Agent Store service has stopped, the database may have been corrupted. Restore the database from backup data or execute database re-creation, and then restart the Master Store or Agent Store service.

KAVE00132-E

Invalid data was detected in the communication message. (rc=maintenance-code)

Invalid data was detected in a communication message.

(S)

Suspends processing.

(O)

Ensure that the same report number is not being used by another program.

KAVE00133-E

A service that uses the same service ID is already running. (service=service-ID)

The service could not be started because a service that uses the same service ID is already running.

(S)

Suspends the service's startup processing.

(O)

Check the following:

Are there multiple services with the same instance name specified?

Is the service already running?

Is the physical host name the same as the logical host name in a cluster system?

The service cannot be started in a cluster system if the logical and physical hosts have the same name. Make sure that the physical and logical hosts have different names.

KAVE00134-E

An IP address could not be resolved. (host=host-name)

The necessary host information is not set up in the hosts file or DNS environment.

(S)

Suspends processing.

(O)

Ensure that the necessary host information is set up in the hosts file or DNS environment.

KAVE00135-E

An attempt to establish a communication connection with Name Server failed. (rc=maintenance-code)

It was not possible to establish a communication connection with the Name Server service.

(S)

Suspends processing.

(O)

Ensure that the Name Server service is running.

KAVE00137-E

The data directory (folder-name) is specified for two or more services.

The same Store database folder, backup folder, or export folder is specified for multiple services.

(S)

Suspends the service's startup processing.

(O)

Check the folder settings.

KAVE00138-E

The specified data directory (folder-name) does not exist.

The specified Store database directory, backup directory, export directory, or temporary file output destination directory does not exist.

(S)

If service initialization processing is being performed, the system cancels service startup processing.

If a service is being started, the system cancels the requested processing.

(O)

Check if the specified folder exists.

KAVE00139-E

You do not have permission to access the specified data directory (folder-name).

You do not have permission to access the specified Store database folder, backup folder, or export folder.

(S)

Suspends the service's startup processing.

(O)

Check the access permission for the specified folder.

KAVE00140-E

An I/O error occurred. (rc=maintenance-code)

An I/O error occurred during processing.

(S)

Suspends processing.

(O)

Check the file system status. An I/O error may have stopped the service. Execute the jpctool service list command to check the status of services. If the Master Store or Agent Store service has stopped, the database may have been corrupted. Restore the database from backup data or execute database re-creation, and then restart the Master Store or Agent Store service.

KAVE00141-E

An attempt to access a file or directory (file-name or folder-name) failed.

An attempt to access a file or directory failed.

(S)

Suspends processing.

(O)

Check the error message that was output immediately before this message.

KAVE00142-E

The command abnormally ended. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id, signal=signal-number)

The command defined in the action definition terminated abnormally because a signal was received.

(S)

Terminates the command.

KAVE00143-E

The command could not be started. (alarm=alarm-name, alarm table=alarm-table-name, system call=system-call-name, en=os-detail-code)

It was not possible to start the command defined in the action definition. The code indicated by en= is the errno of a system call or a Win32 API detailed code.

(S)

Suspends the command's startup processing.

(O)

Check the OS detailed code.

KAVE00144-E

An error has occurred during the starting of the command. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id, system call=system-call-name, en=os-detail-code)

The system encountered an error while trying to start the command defined in the action definition. The code indicated by en= is the errno of a system call or a Win32 API detailed code.

(S)

Suspends the command's startup processing.

(O)

Check the OS detailed code.

KAVE00145-E

An attempt to send the e-mail failed. (alarm=alarm-name, alarm table=alarm-table-name, address=e-mail-address)

The e-mail defined in the action definition could not be sent.

(S)

Suspends the e-mail transmission process.

(O)

Check the status of the email server.

KAVE00146-E

A shutdown request was issued, so backup or export processing is interrupted.

Backup or export processing was interrupted because a shutdown request was issued.

(S)

Cancels the backup or export process.

KAVE00147-E

Reception of a signal interrupted service processing. (signal=signal-number)

A signal caused a service interruption.

(S)

Suspends the service's processing.

KAVE00148-E

The command could not be started because the character string substitution processing failed. (alarm=alarm-name, alarm table=alarm-table-name, string=[substitution-character-string-name])

The command defined in the action definition could not be started because character string substitution failed.

(S)

Suspends the command's startup processing.

(O)

Check the action definition.

KAVE00149-E

The command could not be started because the access permission was denied. (alarm=alarm-name, alarm table=alarm-table-name, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because access permission was denied.

(S)

Suspends the command's startup processing.

(O)

Check the access permission for the file specified by the command name in the action definition.

KAVE00150-E

The command could not be started, because the pipe generation was failed. (alarm=alarm-name, alarm table=alarm-table-name, system call=system-call-name, en=OS-detail-code)

The command could not be started because pipe generation failed. The code indicated by en=OS-detail-code is the errno of a system call or a Win32 API detailed code.

(S)

Suspends the command's startup processing.

(O)

Check the OS detail code.

KAVE00151-E

The command could not be started because the execution file does not exist. (alarm=alarm-name, alarm table=alarm-table-name, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because no execution file exists.

(S)

Suspends the command's startup processing.

(O)

Check the file specified by the command name in the action definition.

KAVE00152-E

The command could not be started because the file is not an executable file. (alarm=alarm-name, alarm table=alarm-table-name, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because the specified file is not an executable file.

(S)

Suspends the command's startup processing.

(O)

Check the file specified by the command name in the action definition.

KAVE00153-E

The command could not be started because the access permission was denied. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because access permission was denied.

(S)

Suspends the command's startup processing.

(O)

Check the access permission for the file specified by the command name in the action definition.

KAVE00154-E

The command could not be started because the execution file does not exist. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because no executable file exists.

(S)

Suspends the command's startup processing.

(O)

Check the file specified by the command name in the action definition.

KAVE00155-E

The command could not be started because the file is not an executable file. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because the specified file is not an executable file.

(S)

Suspends the command's startup processing.

(O)

Check the file specified by the command name in the action definition.

KAVE00156-E

The command could not be started because memory is insufficient. (alarm=alarm-name, alarm table=alarm-table-name)

The command defined in the action definition could not be started because of a memory shortage.

(S)

Suspends the command's startup processing.

(O)

Close applications that are not being used or increase the memory size.

KAVE00157-E

An attempt to start Agent Store has failed. (host=host-name, service=service-ID)

An attempt to start Agent Store failed.

(S)

Terminates the Agent Store service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00158-E

The command could not be started because memory is insufficient. (alarm=alarm-name, alarm table=alarm-table-name, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because of a memory shortage.

(S)

Suspends the command's startup processing.

(O)

Close applications that are not being used or increase the memory size.

KAVE00159-E

The command could not be started because memory is insufficient. (alarm=alarm-name, alarm table=alarm-table-name, pid=process-id, system call=system-call-name, en=os-detail-code)

The command defined in the action definition could not be started because of a memory shortage.

(S)

Suspends the command's startup processing.

(O)

Close applications that are not being used or increase the memory size.

KAVE00160-E

An attempt to initialize a service failed. (rc=maintenance-code)

An attempt to initialize a service failed.

(S)

Suspends the service's startup processing.

(O)

Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00161-E

The number of entries in the system lock table exceeded a system dependent maximum.

The file could not be locked because the number of entries in the lock table exceeded the system-dependent maximum.

(S)

Stops the service.

(O)

Check the maximum limit for the number of entries in the lock table.

KAVE00162-E

The same service cannot be started.

The service could not be started because it had already started or was being started.

(S)

Stops the service.

(O)

Use the jpctool service list command to check service startup status.

KAVE00163-E

The database type is illegal. (db=database-file-name, product id1=product-id-1, product id2=product-id-2, version1=version-information-1, version2=version-information-2)

The database type for the Store database is invalid.

(S)

Stops the service.

(O)

The meanings of the values that are output in the message are explained below:

database-file-name

Name of the database file in which the error was detected.

product-id-1

Product ID that must be described in the database file.

product-id-2

Product ID that is specified by database-file-name and described in the database file.

version-information-1

Database file version information that should be described in the database file.

version-information-2

Database file version information that is described in the database file specified by database-file-name.

KAVE00164-E

The communication connection to another service failed. (rc=maintenance-code)

The communication connection to another service failed.

(S)

Suspends the service's startup processing.

(O)

Ensure that all services are running. The meaning of the maintenance-code is explained below:

-2: Communication timeout occurred.

-6: No response.

-13: Connection process failed.

-39: Data could not be sent to another related service.

KAVE00165-W

The reception of the trap will be canceled because the event was from an undefined agent. (product id=product-id)

A trap transmission event was received for an agent that was not found in the product definition information.

(S)

Suspends the trap transmission processing.

(O)

Execute additional setup for the agent.

KAVE00166-W

The Store service is delayed and the load on the service is high. Revise the collection items and the collection intervals. (queue length=waiting-requests-count)

The Master Store or Agent Store service's processing is delayed because there are too many requests.

(S)

Holds requests; this results in an increase in the amount of resources required for the Master Store or Agent Store service.

(O)

Check and, if necessary, revise the records collected by the Agent Collector as well as the collection interval and alarm conditions, and then adjust the number of requests to the Master Store or Agent Store service.

KAVE00167-E

The action definition could not be converted because memory is insufficient. (service=service-ID, alarm table=alarm-table-name, alarm=alarm-name)

Conversion of character encoding failed on the action definition due to a memory shortage.

(S)

May not be executing the defined action correctly when an alarm event occurs.

(O)

Close applications that are not being used currently or increase the memory size. Bind again the alarm table that resulted in the error.

KAVE00168-E

The alarm event could not be converted because memory is insufficient. (service=service-ID, alarm table=alarm-table-name, alarm=alarm-name)

Conversion of character encoding failed on the alarm event due to a memory shortage.

(S)

May not be executing the defined action correctly when an alarm event occurs.

(O)

Close applications that are not being used currently or increase the memory size. Make sure that the action defined for the alarm resulting in the error was executed successfully.

KAVE00169-E

The alarm definition could not be converted because memory is insufficient. (service=service-ID, alarm table=alarm-table-name, alarm=alarm-name)

Conversion of character encoding failed on the alarm definition due to a memory shortage.

(S)

May not issue the defined alarm correctly.

(O)

Close applications that are not being used currently or increase the memory size. Bind again the alarm table that resulted in the error.

KAVE00170-E

The event information could not be converted because memory is insufficient. (service=service-ID, alarm table=alarm-table-name, alarm=alarm-name)

Conversion of character encoding failed on the event registration information due to a memory shortage.

(S)

May not be executing the defined action correctly when an alarm event occurs.

(O)

Close applications that are not being used currently or increase the memory size. Use the following procedure to update the event registration information for the alarm that resulted in the error:

Select the alarm that resulted in the error.

From the File menu, choose Edit.

Choose the Finish button without changing any information.

KAVE00171-E

The alarm table binding information could not be converted because memory is insufficient. (service=service-ID, alarm table=alarm-table-name)

Conversion of character encoding failed on the alarm table bind information due to a memory shortage.

(S)

May not be issuing the defined alarm correctly.

(O)

Close applications that are not being used currently or increase the memory size. Bind again the alarm table that resulted in the error.

If KAVE00141-E is output to the PFM - Agent log, create the folder specified in JPC_TMPDIR or change the JPC_TMPDIR setting.

KAVE00172-E

The expression could not be converted because memory is insufficient. (service=service-ID)

Conversion of character encoding failed on the conditional expression due to a memory shortage when a report is displayed or linkage is established with an ODBC-based application program.

(S)

Resumes processing without converting the character encoding; therefore, search operations may not execute successfully.

(O)

Close applications that are not being used currently or increase the memory size. Re-execute the report display or operation with the ODBC-based application program.

KAVE00173-E

The LOGIF expression could not be converted because memory is insufficient. (service=service-ID)

Conversion of character encoding failed on the log output conditional expression due to a memory shortage.

(S)

The log output conditional expression may not be set correctly.

(O)

Close applications that are not being used currently or increase the memory size. Set the log output conditional expression again.

KAVE00174-E

The performance data could not be converted because memory is insufficient. (service=service-ID)

Conversion of character encoding failed on the performance data due to a memory shortage when linkage is established with an ODBC-based application program.

(S)

Resumes processing without converting the character encoding. The performance data may be displayed using the wrong character codes.

(O)

Close applications that are not being used currently or increase the memory size. Re-execute the ODBC-based application program operation.

KAVE00175-E

The E-mail title could not be converted because memory is insufficient.

Conversion of character encoding failed on the email subject due to a memory shortage.

(S)

Resumes processing without converting the character encoding. The email subject may be displayed using the wrong character codes.

(O)

Close applications that are not being used currently or increase the memory size.

KAVE00176-E

The E-mail text could not be converted because memory is insufficient.

Conversion of character encoding failed on the email text due to a memory shortage.

(S)

Resumes processing without converting the character encoding. The email text may be displayed using the wrong character codes.

(O)

Close applications that are not being used currently or increase the memory size.

KAVE00178-W

An attempt to connect to Manager failed, so the service will be started in stand-alone mode. (host=host-name, service=service-ID)

An attempt to connect the indicated service to PFM - Manager failed, so the service will be started in the stand-alone mode.

(S)

Starts the service in the stand-alone mode. When communication with PFM - Manager is restored, the system automatically switches the service to the normal mode. When you execute the jpctool service list command on a remote machine to check the status of the service started in stand-alone mode, Inactive is displayed if the status management function is disabled. When the status management function is enabled, the system displays S Active or S Busy, depending on the status of the service.

The conditions for startup in stand-alone mode are as follows:

When PFM - Manager is stopped

While PFM - Manager is stopped, PFM - Agent and the Action Handler service are started in the stand-alone mode.

When automatic startup is used

PFM - Agent and the Action Handler service may be started temporarily in the stand-alone mode because they are started without waiting for startup of the PFM - Manager service. After PFM - Manager has started, they are switched automatically to the normal mode.

When PFM - Manager is busy

If many PFM - Agent systems attempt to start concurrently, PFM - Agent and the Action Handler service may be started temporarily in the stand-alone mode due to a wait for communication with PFM - Manager. When communication with PFM - Manager is restored, the system automatically switches the service to the normal mode.

When communication cannot be established with PFM - Manager for a reason such as a communication error

PFM - Agent and the Action Handler service are started in the stand-alone mode. After communication with PFM - Manager is restored, they are switched automatically to the normal mode.

KAVE00179-W

Invalid entry was detected in the jpchosts.

There is an invalid entry in the jpchosts file.

(S)

Ignores the invalid entry and continues processing.

(O)

Check the entries in the jpchosts file.

Correct the invalid entry, and then restart the service.

KAVE00180-E

An error occurred during reading the jpchosts.

An error occurred during reading of the jpchosts file.

(S)

Ignores the invalid entry and continues processing.

(O)

Check for and correct any invalid characters in the jpchosts file and its properties, and then restart the service.

KAVE00181-W

Correlator was not able to acquire alarm status information from Collector. (service=service-ID)

During initialization of the Correlator service, the service was unable to acquire the alarm status information from the Collector service. service-ID indicates the agent that failed to acquire the alarm status information.

(S)

Assumes that all alarm statuses for the agent are normal, and continues initialization of the Correlator service.

(O)

If an alarm status displayed by PFM - Web Console differs from the actual agent status, bind the alarm table to the agent again.

KAVE00182-E

The record data could not be stored because the Store database reached the writing limit. (record=record-ID, file=file-name)

The record data could not be stored because the Store database is full.

(S)

Stops the service.

(O)

Use the following steps to clear the data in the database. If there is data in the database that you need, export it in CSV or HTML# format. If this message is output, the specified collection items or collection interval may not be adequate. Change the specified collection items and collection interval. For PFM - Agent, consider migration to Store version 2.0.

For Agent Store or Remote Monitor Store:

Use PFM - Web Console to open the Agent Collector properties and then modify the settings to stop collecting any of the records.

Start the stopped Agent Store service.

Use the jpcrpt command to export required data in CSV or HTML# format.

Use the jpctool db clear command to clear the database file.

Use PFM - Web Console to open the Agent Collector properties, specify only the records that you want to collect, and then resume the operations.

For Master Store:

Execute the jpctool service list command, and make sure that the Master Store service is stopped.

Manually delete the files below.

The file paths shown below are default file locations. If the locations have been changed, delete the files in the new locations.

When PFM - Manager is running on a physical host in a Windows environment:

- STPA.DB and STPA.IDX files in installation-folder\mgr\store

When PFM - Manager is running on a physical host in a UNIX environment:

- STPA.DB and STPA.IDX files in /opt/jp1pc/mgr/store

When PFM - Manager is running on a logical host in a Windows environment:

- STPA.DB and STPA.IDX files in environment-directory\jp1pc\mgr\store

When PFM - Manager is running on a logical host in a UNIX environment:

- STPA.DB and STPA.IDX files in environment-directory/jp1pc/mgr/store

Execute the jpcspm start command to start the Performance Management service.

#

If you are using PFM - Web Console 08-00 or earlier, export cannot be executed in HTML format.

KAVE00183-E

The alarm could not be evaluated because memory is insufficient. (service=service-ID, record=record-ID)

The alarm could not be evaluated because of a memory shortage.

(S)

Continues processing without evaluating the alarm for the record with the indicated record ID.

(O)

Close applications that are not being used currently or increase the memory size.

KAVE00184-W

The number of characters after expanding the variable exceeds the maximum for the value field. (service=service-ID, alarm table=alarm-table-name, alarm=alarm-name)

A character string was not fully displayed because the maximum number of characters for the item was exceeded when the variable specified for the item was expanded. The permitted maximum numbers of characters for items are as follows:

Alarm message on the General settings page of the New Alarm > Main Information window: 255 bytes

Email body in the Email Settings field of the New Alarm > Action window: 1,000 bytes

Command arguments in the Command Definition field of the New Alarm > Action window: 2,047 bytes

Message in the New Alarm > Action Definitions > JP1 Event Settings window: 128 bytes

Mail Subject for the Action Handler service's Mail in the Properties method for the Services tree: 100 bytes

(S)

Displays the permitted maximum number of characters and then resumes processing.

The system determines the characters to be displayed as follows:

When the value of the expanded variable exceeds the maximum number of characters

Characters up to the variable that exceeded the maximum number of permitted characters are displayed.

When the variable expansion was successful, but a subsequent character exceeded the maximum number of characters

Characters up to the maximum number of permitted characters are displayed.

(O)

Reset the value so that the value of the expanded variable does not exceed the maximum permissible number of characters.

KAVE00185-W

The number of characters entered in the value field exceeded the maximum length. (record=record-ID, maximum length=permitted-input-length-in-bytes)

The number of characters entered as the value of the filtering conditional expression in the report definition exceeds the maximum number of characters permitted for the field.

(S)

Compares the condition up to the maximum number of characters permitted for the field.

(O)

Check and, if necessary, revise the number of characters for the value of the filtering conditional expression.

KAVE00186-W

A record will be deleted because an invalid record was detected in the database. (prodid=product-ID, db=database-file-name)

An invalid record that was detected in the database is being deleted.

(S)

Deletes the invalid record and starts the service.

(O)

If this message was displayed for the Name Server or Master Manager service, no action is needed because the service will be started without any adverse effects on service operation or the data.

If this message was displayed for the Master Store or Agent Store service, some records may be deleted, which may result in inconsistent trend analysis of related performance data. To resolve such an inconsistency, take the action described below. Note that the Master Store or Agent Store service options will not be affected even if you do not take the following action.

When a backup file is available:

Restore the database from the backup file. For details about backup operations, see the chapter that describes backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.

When a backup file is not available:

Stop the Master Store or Agent Store service, then delete the database file (*.DB extension) in the Store directory indicated in the message and restart the service.

KAVE00187-E

An error occurred during communications processing. (service=service-ID)

Communication processing failed.

(S)

Cancels the requested processing.

(O)

Check the service ID for the following:

Is the service running?

Can communication be established?

Is the PFM - Manager for the connection destination correct?

KAVE00188-E

An attempt to send an event has failed. (service=service-ID)

One of the following processes failed:

Transmission of agent event

Transmission of alarm event

Execution of action

(S)

Skips event transmission processing.

(O)

Check the service ID for the following:

Is the service running?

Can communication be established?

Is the PFM - Manager for the connection destination correct?

KAVE00189-I

The re-send of the event was successful. (service=service-ID)

One of the following processes was successful:

Re-transmission of agent event

Re-transmission of alarm event

Re-execution of action

(S)

Terminates event re-transmission.

KAVE00190-W

During collection of real-time data, the number of instances of a multi-instance record exceeded the maximum. (record=record-ID)

The number of instances of a multi-instance record acquired during collection of realtime data exceeded 32,767 (which is the permitted maximum). The excess instances are being discarded.

(S)

Resumes processing.

KAVE00191-W

During alarm evaluation, the number of instances of a multi-instance record exceeded the maximum. (alarm table=alarm-table-name, alarm=alarm-name, record=record-ID)

The number of instances of a multi-instance record acquired by a single collection during alarm evaluation exceeded 32,767 (which is the permitted maximum). The excess instances will not be evaluated for alarms but they will be stored in the Store database.

(S)

Resumes processing.

KAVE00192-W

Reception of a signal caused the service to stop. (signal=signal-number)

The service will be stopped due to reception of a signal.

(S)

Suspends the service's processing.

KAVE00193-E

Name Server stopped abnormally. (host=host-name, service=service-ID)

The Name Server service terminated abnormally.

(S)

Terminates the Name Server service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00194-E

Master Manager stopped abnormally. (host=host-name, service=service-ID)

The Master Manager service terminated abnormally.

(S)

Terminates the Master Manager service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00195-E

Master Store stopped abnormally. (host=host-name, service=service-ID)

The Master Store service terminated abnormally.

(S)

Terminates the Master Store service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00196-E

Correlator stopped abnormally. (host=host-name, service=service-ID)

Correlator stopped abnormally.

(S)

Terminates the Correlator service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00197-E

Action Handler stopped abnormally. (host=host-name, service=service-ID)

The Action Handler service terminated abnormally.

(S)

Terminates the Action Handler service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00198-E

Trap Generator stopped abnormally. (host=host-name, service=service-ID)

The Trap Generator service terminated abnormally.

(S)

Terminates the Trap Generator service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00199-E

View Server stopped abnormally. (host=host-name, service=service-ID)

The View Server service terminated abnormally.

(S)

Terminates the View Server service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00200-E

Agent Store stopped abnormally. (host=host-name, service=service-ID)

The Agent Store service terminated abnormally.

(S)

Terminates the Agent Store service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00201-E

An attempt to access the configuration file failed. (file=file-name)

An attempt to access the settings file failed. If this message is displayed when settings are being read, such as at the time of service startup or display of properties, the settings have not been read correctly. If this message is displayed when properties are being updated, the settings have not been written correctly.

(S)

Cancels the write or read processing on the settings file.

(O)

Use PFM - Web Console to display the service properties, and then make sure that the settings are valid. If the settings have not been updated, change the settings again. If the properties are not displayed correctly, the settings have not been read correctly. Restart the service.

KAVE00202-E

Status Server stopped abnormally. (host=host-name, service=service-ID)

The Status Server service terminated abnormally.

(S)

Terminates the Status Server service's processing.

(O)

Check the cause that is output in the common message log. If the termination was caused by reception of a signal, KAVE00147-E has been output to the common message log.

KAVE00203-W

An attempt to contact the Status Server service has failed.(host=host-name)

The system attempted to connect to the Status Server service on the indicated host to acquire the status of each service of PFM - Manager or PFM - Agent, but could not do so. Possible reasons are the following:

The Status Server service is not running or is being started.

Because of network or server environment problems, either a response from the Status Server service takes a long time or the Status Server service cannot be connected.

(S)

Directly checks the status of each service of PFM - Manager or PFM - Agent, and continues processing.

(O)

No action is required if this message is output during a period of temporary heavy server load, such as when the server is started, and if no message indicating a Status Server service startup failure or a Status Server service stoppage is output. If neither of these message is output before or after the current message, the connection to the Status Server service will be restored after output of the current message.

If this message is output repeatedly each time a command operation is executed for a PFM - Manager or PFM - Agent service, the Status Server service might have stopped. Check the status of the Status Server service, and start it if it has stopped.

KAVE00205-W

An agent has been registered for which PFM - Manager cannot recognize the product ID or data model version. Please execute setup. (product id=product-ID, version=data-model-version).

Connection establishment was attempted from a product or a data model version of PFM - Agent that has not been set up in the PFM - Manager.

(S)

Resumes processing.

(O)

To manage the added agent, you must set it up in PFM - Manager, and PFM -Web Console. For details about how to set up an agent, see the chapter that describes agent setup in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00206-E

An attempt to start Status Server has failed.(host=host-name, service=service-ID)

An attempt to start the Status Server service failed.

(S)

Terminates the Status Server service's processing.

(O)

Check the cause that is output in the common message log. If the service was stopped due to reception of a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00207-E

An attempt to create a symbol has failed. (label=symbol-label, host=host-name, msg=NNM-error-message)

An attempt to create a symbol on the NNM submap failed. symbol-label displays the label of the symbol whose creation failed. host-name displays the host name of the PFM - Agent where the alarm occurred. NNM-error-message displays the NNM error message.

(S)

Cancels symbol creation processing.

(O)

Eliminate the cause of the error based on the displayed NNM error message. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00208-E

An attempt to update the status of a symbol has failed. (label=symbol-label, host=host-name, msg=NNM-error-message)

An attempt to update the status of a symbol on the NNM submap failed. symbol-label displays the label of the symbol whose update processing failed. host-name displays the host name of PFM - Agent where the alarm occurred. NNM-error-message displays the NNM error message.

(S)

Cancels symbol update processing.

(O)

Eliminate the cause of the error based on the displayed NNM error message. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00209-E

An attempt to find a symbol has failed. (host=host-name, msg=NNM-error-message)

An attempt to search for a symbol on the NNM map failed. host-name displays the host name of the PFM - Agent where the alarm occurred.

(S)

Cancels processing on the target object.

(O)

Eliminate the cause of the error based on the displayed NNM error message. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00210-W

The received trap was ignored because the SNMP trap format was invalid.

Format of the received SNMP trap is invalid.

(S)

Discards the received SNMP trap and resumes processing.

(O)

Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00211-E

An attempt to update the property of an object has failed. (host=host-name, msg=NNM-error-message)

An attempt to update the property of an object failed. The received SNMP trap information is not applied. host-name displays the host name of the PFM - Agent where the alarm occurred. NNM-error-message displays the NNM error message.

(S)

Cancels processing on the target object.

(O)

Eliminate the cause of the error based on the displayed NNM error message. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00212-E

An attempt to create an object has failed. (host=host-name, msg=NNM-error-message)

An attempt to create an object in the NNM object database failed. The received SNMP trap information is not applied. host-name displays the host name of the PFM - Agent where the alarm occurred. NNM-error-message displays the NNM error message.

(S)

Cancels object creation processing.

(O)

Eliminate the cause of the error based on the displayed NNM error message. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00213-W

Collection of the performance data will be skipped because collection processing was delayed. (skipped time=scheduled-collection-time, scheduled time=scheduled-next-collection-time, record=record-name, type=collection-type)

Collection of the performance data is skipped because the collection processing or the data storage in the Store database was delayed. The next collection will be rescheduled to the time closest to the current time. This message may be displayed when the performance data collection completion time is after the next collection time or the collection time set based on the offset value is close to the collection time for another record. scheduled-collection-time displays the skipped collection time. scheduled-next-collection-time displays the reset collection time. Both scheduled-collection-time and scheduled-next-collection-time are displayed in the local time in the format YYYY/MM/DD hh:mm:ss, the values of which have the following meaning:

YYYY: year, MM: month, DD: date, hh: hour, mm: minute, ss: second.

record-name displays the name of the record whose collection was skipped. For collection-type, realtime is displayed for realtime data and historical is displayed for historical data or alarm monitoring data.

(S)

Skips collection of performance data. This performance data is not collected.

(O)

Check and, if necessary, revise the performance data collection items, interval, and offset value. For details about how to record performance data, see the chapter that describes management of operation monitoring data in the manual Job Management Partner 1/Performance Management User's Guide.

If this message is output during execution of the jpctool db backup command, extend the interval of performance data collection to reduce the processing load on services. You can thus reduce the frequency of the output of this message.

KAVE00214-E

An attempt to find an object has failed. (msg=NNM-error-message)

An attempt to search the NNM object database for the object corresponding to the received SNMP trap failed. NNM-error-message displays the NNM error message.

(S)

Cancels processing on the target object.

(O)

Eliminate the cause of the error based on the displayed NNM error message. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00215-W

Recovery processing was performed because invalid information was detected in the service configuration information file. (service=service-ID)

Recovery processing was performed because invalid information was detected when the service configuration information file (jpcns.ini) was referenced.

service-ID displays the service ID of the service that is related to the invalid information.

(S)

Resumes processing.

(O)

Make sure that the following information is correct. If the correct information has not been set, set the information again.

Host name of the PFM - Manager for the connection destination

Port number, if the port number used by the service has been fixed

KAVE00216-E

The requested amount of data cannot be processed because it is too large.

The amount of data requested for report display or other operations reached the processing limit. This message may be output when too much data is requested for a realtime report, a historical report, an event history, or the ODBC driver.

(S)

Stops the requested processing.

(O)

Reduce the amount of data that is acquired at one time by reducing the time period of the record data to be specified for the realtime report, historical report, event history, or ODBC driver.

Use the following formula to calculate the amount of data to be acquired at one time. Adjust the field size, the number of instances, and the number of records until the result of the calculation becomes no more than 2 GB.

total-size-of-specified-fields * number-of-instances * number-of-records [bytes]

For records other than the PA record

total-size-of-specified-fields is the total size of the fields specified for a report or the ODBC driver.

Example of calculating the PD_PDI record for PFM - Agent for Platform (Windows)

The conditions for displaying a historical report and the formula for calculating the size of the data are as follows:

Conditions:

- Specify the Date and Time field (char(6) type: 6 bytes).#1

- Specify the ODBC key fields.#1

Program field (string type: 256 bytes)

PID field (ulong type: 4 bytes)

- Specified fields other than the above

CPU % field (float type: 4 bytes)

User field (string type: 36 bytes)

Date field (char(3) type: 6 bytes)#2

- Number of instances collected per minute

200 instances

- Collection interval (number of requested records)

When you display the minute-by-minute records for one day in a report, the calculation for number of records is 60 minutes * 24 hours, which is 1,440 records.

Calculation formula

(6 + 256 + 4 + 4 + 36 + 6) * 200 * 1440 = 89,856,000 [bytes]

#1

When a realtime report or a historical report is displayed, the Date and Time field and the ODBC key fields are always acquired, even when you do not include them in the report display. When you use the ODBC driver to acquire data, only the fields specified in the conditions are acquired.

#2

The Date field and the Time field are automatically added when data is stored in the Store database. For a historical report, assume the size of each field to be 6 bytes. When you use the ODBC driver to acquire data, assume the size of each field to be 3 bytes. For other fields, assume sizes that are based on the types described in the applicable PFM - Agent manual.

Note that the number of instances changes for each collection of records. For details about the data type of each field, the size of each data type, and the ODBC key fields, see the chapter on records in the applicable PFM - Agent manual.

For the PA record

Assume 4,409 for total-size-of-specified-fields, 1 for number-of-instances, and the number of events generated during the specified period for number-of-records.

KAVE00217-I

The Agent Status was changed to Normality.

The agent status has been changed to normal due to, for example, a change in the alarm status.

(S)

Continues processing.

KAVE00218-I

The Agent status was changed to Warning.

The agent status has been changed to warning due to, for example, a change in the alarm status.

(S)

Continues processing.

KAVE00219-E

The Agent status was changed to Exception.

The agent status has been changed to abnormal due to, for example, a change in the alarm status.

(S)

Continues processing.

KAVE00220-E

An invalid value is set, so the process will be started with action log output functionality disabled. (label=label-name, specified value=setting-value)

Because an invalid value is set in the action log, the process starts with the action log output function disabled.

label-name indicates the name of the label set with an invalid value, and setting-value indicates the specified invalid value.

(S)

Disables the action log output function, and continues processing.

(O)

Check the setting value specified for label-name in the jpccomm.ini file.

KAVE00221-W

An invalid value is set, so the process will be started with the default setting for action log output functionality. (label=label-name, specified value=setting-value, applied value=current-value)

Because an invalid value is set in the action log, the process starts with the default settings.

label-name indicates the name of the label set with an invalid value, setting-value indicates the specified invalid value, and current-value indicates the currently applied value.

(S)

Temporarily changes the settings of the action log, and continues processing.

(O)

Check the setting value specified for label-name in the jpccomm.ini file.

KAVE00222-W

An invalid value is set, so the process will be started with the nearest setting for action log output functionality. (label=label-name, specified value=setting-value, applied value=current-value)

Because an invalid value is set in the action log, the process starts with the nearest valid settings.

label-name indicates the name of the label set with an invalid value, setting-value indicates the specified invalid value, and current-value indicates the currently applied value.

(S)

Temporarily changes the settings of the action log, and continues processing.

(O)

Check the setting value specified for label-name in the jpccomm.ini file.

KAVE00223-E

An attempt to access the action log output path has failed, so the process will be started with action log output functionality disabled. (path=output-destination, rc=maintenance-code)

Because the log output destination directory or a file under the log output destination directory cannot be accessed, the process starts with the action log output function disabled.

output-destination indicates the name of the log output destination directory that cannot be accessed, and maintenance-code indicates the maintenance code.

(S)

Disables the action log output function, and continues processing.

(O)

If the directory indicated by output-destination is incorrect, change the output destination for the action log. If output-destination is correct, make sure that the directory exists and that you have the access permission for the directory.

KAVE00224-E

An attempt to initialize the library has failed, so the process will be started with action log output functionality disabled. (rc=maintenance-code)

Because initialization of the action log output library has failed, the process will start with the action log output function disabled.

maintenance-code indicates the maintenance code.

(S)

Disables the action log output function, and continues processing.

(O)

Collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00225-E

An attempt to output the action log output has failed. (output-contents)

An attempt to output the action log has failed.

output-contents indicates the contents of the action log that could not be output.

(S)

Disables the action log output function, and continues processing.

(O)

Collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00226-E

An attempt to output the action log output has failed, so action log output functionality will be disabled in this process.

Because an attempt to output the action log has failed, the process continues processing with the action log output function disabled.

(S)

Invalidates changes to the action log output function, and continues processing.

(O)

Collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE00227-W

The maximum file size of the Store database has been reached, so the newly acquired function information will be partially deleted. (db=database, recordtype=record-type)

Because the maximum file size of the Store database has been reached, some of the newly acquired performance information will be discarded.

(S)

Cancels the storage of data and continues processing.

(O)

Change the estimated disk size for the Store database, and set the collection interval and collection items again.

KAVE00228-I

Storage of Store database data will now restart. (db=database, recordtype=record-type)

The storage of data into the Store database will restart.

(S)

Restarts the storage of data.

KAVE00229-E

The data model version of import data is different from the data model version of current product. (ver1=data-model-version, ver2=data-model-version)

The data model version of the import data differs from the data model version of the current product.

(S)

Cancels processing.

(O)

Because an upgrade installation has upgraded the data model of the product, the data model of the import data is old. If you want to refer to the import data, use the jpctool db dmconvert command to upgrade the data model of the import data. If you do not want to refer to the import data, use the jpcconf db define command to change the import directory to another directory or manually delete the files under the import directory.

KAVE00230-E

An attempt to access the import data has failed. (file=file-name)

An attempt to access the import data failed.

(S)

Cancels processing.

(O)

Make sure that you can access the import data. If you can access the import data, the import data may be damaged. Use the jpcconf db define command to change the import directory, or manually delete the files under the import directory.

KAVE00231-W

An attempt to delete a directory has failed. (dir=directory-name, rc=maintenance-code)

An attempt to delete the directory has failed. A directory is deleted in the following cases:

A record older than the retention period is generated in Store 2.0.

The jpctool db clear command is used to delete the Store database.

The jpctool db import command is used to delete the import directory.

(S)

Continues processing.

(O)

A possible cause of the failure to delete the directory could be that another program (Explorer, shell, backup software, virus scan software, for example) is being used.

If deletion of a record older than the retention period in Store 2.0 has failed.

The directory will be deleted in the deletion cycle that follows termination of the currently running program.

If the jpctool db clear command or the jpctool db import command was unable to delete the directory.

When the currently running program terminates, re-execute the jpctool db clear command or the jpctool db import command.

KAVE00232-W

IPv4 will be used for communication because no IPv6 addresses are available.

No IPv6 addresses are available on the local host. To use IPv6, a global address must be set.

(S)

Continues processing by using communication on IPv4 for services and commands.

(O)

Perform one of the following operations:

Add a global address as the IPv6 address of the local host in the jpchosts file.

Add a global address as the IPv6 address of the local host in the hosts file of the system.

KAVE00233-E

An attempt to get the node information of Status Server failed. (service=service-ID)

An attempt to acquire the node information of Status Server failed. The Status Server cannot be connected.

(S)

Continues processing. The correct information about the service could not be collected because an attempt to connect to Status Server failed.

(O)

Make sure that the port number for Status Server has been set properly. If not, set a valid port number. To check or set the port number, use the jpcconf port command. For details on the command, see the chapter that explains the jpcconf port command. If you are still unable to resolve the problem even after executing the command, collect the maintenance information and then contact the system administrator. For details on how to collect the maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00234-I

Remote Monitor Store has started. (host=host-name, service=service-ID)

Remote Monitor Store has started.

(S)

Starts Remote Monitor Store processing.

KAVE00235-I

Remote Monitor Store has stopped. (host=host-name, service=service-ID)

Remote Monitor Store has stopped.

(S)

Terminates Remote Monitor Store processing.

KAVE00236-E

An attempt to start Remote Monitor Store has failed. (host=host-name, service=service-ID)

An attempt to start Remote Monitor Store has failed.

(S)

Terminates Remote Monitor Store processing.

(O)

Check the cause of the problem output to the common message log. If the service was stopped by receiving a signal, KAVE00147-E or KAVE00192-W has been output to the common message log.

KAVE00237-E

Remote Monitor Store stopped abnormally. (host=host-name, service=service-ID)

Remote Monitor Store has stopped abnormally.

(S)

Terminates Remote Monitor Store processing.

(O)

Check the cause of the problem output to the common message log. If the service was stopped by receiving a signal, KAVE00147-E has been output to the common message log.

KAVE00238-E

The connection-target Manager does not support this product. (host=host-name, service=service-ID, manager host=PFM-Manager-host-name)

The connection-target Manager does not support this product. The service will now be terminated.

(S)

Terminates the service.

(O)

Make sure that the connection-target Manager supports this product. If not, change the connection-target Manager host to a different Manager that supports this product, and then restart the service. If this message is still output even the new connection-target Manager that supports this product, collect the maintenance information and then contact the system administrator.

KAVE00239-W

An alarm table cannot be bound to Remote Monitor. (service=service-ID)

An alarm table cannot be bound to Remote Monitor.

(S)

Ignores the alarm table bind request.

(O)

Check the service to which an attempt to bind an alarm table was performed. An alarm table cannot be bound to Remote Monitor. If you want to set alarms for a monitoring target of Remote Monitor, specify the virtual agent.

KAVE00240-W

Remote Monitor cannot display the report. (service=service-ID)

Remote Monitor cannot display the report.

(S)

Continues processing as if there is no data to display.

(O)

Check the service for which an attempt to display a report was performed. Remoter Monitor cannot display a report. If you want to display a report for a monitored target of Remote Monitor, specify the virtual agent.

KAVE00241-W

Polling for the target hosts will be stopped because the setting of health check is invalid. (label=label-name)

Polling for the target hosts by Remote Monitor (operation monitoring by ICMP) will now be canceled due to invalid settings for the health check.

(S)

Cancels polling for the target host by Remote Monitor (operation monitoring by ICMP).

(O)

Stop and then restart all the PFM services, including Status Server, that are running on the target host. After restarting, the settings will be recovered when the health check agent checks the statuses of the PFM services on the target host. If this message will still be output after restarting, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00242-W

Forwarding the event to the specified service was prevented. (service=service-ID, type=data-type)

Forwarding an event to the specified service was suppressed.

This message appears when forwarding an event to the old version of Action Handler is suppressed. In this case, the service ID of Action Handler that has been specified for the action execution service is displayed for service-ID, and PA is displayed for data-type as the event type.

(S)

Suppresses forwarding events to the specified service. The automatic action will not be executed because forwarding an event that is necessary to execute the action is suppressed.

(O)

Re-specify Action Handler for the action execution service that supports a product to be used for configuring the alarm settings.

KAVE00243-W

As generation of monitoring thread failed, data will be collected in degeneracy status (record=record-name, type=collection-type, planned=number-of-planned-threads, actual=number-of-generated-threads)

An attempt to create monitoring threads for collecting data from each monitoring target has partially failed. The data will be collected in a degenerated state.

record-name indicates the name of the record whose data collection was skipped. For collection-type, realtime will be displayed for realtime data, and historical will be displayed for historical data or alarm-monitoring data.

(S)

Continues to collect performance data by using the created monitoring threads. Collection of performance data might not be finished during the specified Collection Interval because it will take a longer time than the usual collection process.

(O)

If this message is output frequently, there might be insufficient resources on the host running Remote Monitor. If you are unable to resolve the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00244-E

Data collection will be skipped due to failure in generation of monitoring thread. (record=record-name, type=collection-type)

An attempt to create monitoring threads for collecting data from monitoring targets has failed. Data collection will be skipped.

record-name indicates the name of the record whose data collection was skipped. For collection-type, realtime will be displayed for realtime data, and historical will be displayed for historical data or alarm-monitoring data.

(S)

Skips performance data collection until the next collection attempt. Performance data will not be collected.

(O)

If this message is output frequently, there might be insufficient resources on the host running Remote Monitor. If you are unable to resolve the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00250-W

A display request was made from a Manager that does not support properties over 592 bytes. (service=service-ID, property=property-name)

A display request was made from a Manager that does not support properties that exceed 592 bytes. The property was displayed after being truncated to no more than 592 bytes. If the property is updated in this state, it is updated after being truncated to no more than 592 bytes.

service-ID is the ID of the service that displayed the property. property-name is the name of the property that is over 592 bytes, using the full path from the root.

(S)

Displays the property after truncating it to no more than 592 bytes.

(O)

Do not update properties.

If you update properties, check the settings of the property displayed in this message, and set them again correctly.

KAVE00251-W

A property was specified that exceeds 4096 bytes. (service=service-ID, property=property-name)

A property that exceeds 4,096 bytes was specified. The property is updated after being truncated to no more than 4,096 bytes.

service-ID is the ID of the service that set the property. property-name is the name of the property that exceeds 4,096 bytes, using the full path from the root.

(S)

Updates the property after truncating it to no more than 4,096 bytes.

(O)

Check the settings of the property displayed in this message, and set them again correctly.

KAVE00252-E

Action execution requests were discarded because the number of actions awaiting execution reached the limit. (service = service-ID)

Action execution requests were discarded because the number of actions awaiting execution exceeded the limit.

For details about the discarded actions, check the message KAVE00255-E in the common message log.

(O)

The number of alarms that occurred might have exceeded the estimate. Revise the alarm definition.

In addition, to balance requests for executing actions, consider distributing the Action Handlers that execute actions.

Re-execute the command as necessary.

KAVE00253-E

Actions awaiting execution were discarded because a shutdown request was issued. (service = service-ID)

The command is not executed for actions awaiting execution because a shutdown request was issued.

For details about the discarded actions, check the message KAVE00255-E in the common message log.

(O)

Re-execute the command as necessary.

KAVE00254-E

The action execution process timed out and will now be forcibly ended. (service = service-ID, alarm table = alarm-table-name, alarm = alarm-name, agent = service-ID-of-an-agent-in-which-an-alarm-occurred)

The action execution process timed out and will now be forcibly ended.

(S)

Forcibly ends the action execution process.

(O)

Determine and then remove the cause of the action execution timeout.

Re-execute the command as necessary.

KAVE00255-E

The action execution request will now be discarded. (service = service-ID, alarm table = alarm-table-name, alarm = alarm-name, agent = service-ID-of-an-agent-in-which-an-alarm-occurred)

The action execution request will now be discarded.

A message (KAVE00252-E or KAVE00253-E) that describes the reason will be output immediately after this message.

(S)

Does not execute the commands for the relevant action.

(O)

Check the message (KAVE00252-E or KAVE00253-E) that describes the reason.

KAVE00258-I

The action is now awaiting execution. (service = service-ID, alarm table = alarm-table-name, alarm = alarm-name, agent = service-ID-of-an-agent-in-which-an-alarm-occurred, queue length = waiting-requests-count)

The action is now awaiting execution because the maximum number of actions that can be concurrently executed was reached.

(S)

Manages the relevant action as an action awaiting execution.

KAVE00259-I

All actions awaiting execution were executed. (service = service-ID)

All actions awaiting execution were executed.

(S)

Executed all actions awaiting execution.

KAVE00260-I

The service will now start with the synchronous execution controller for actions enabled. (service = service-ID, concurrent count = number-of-actions-to-be-executed-concurrently, queue size = maximum-number-of-actions-waiting-to-be-executed, time limit = time-until-forced-termination)

The service will now start with the synchronous execution controller for actions enabled.

(S)

Starts the service with the synchronous execution controller for actions enabled.

KAVE00261-W

The synchronous execution controller for actions will now be disabled because an invalid value is set. (label = label-name, specified value = specified-value)

The service will now start with the synchronous execution controller for actions disabled because an invalid value is set.

(S)

Starts the service with the synchronous execution controller for actions disabled.

(O)

Check and, if necessary, revise the specified value. To apply the changed settings, restart the Action Handler service.

KAVE00262-E

An attempt to forcibly end the action execution process failed. (service = service ID, pid = process-ID)

An attempt to forcibly end the action execution process failed.

(S)

Continues processing and excludes the failed processes from the number of actions to be executed concurrently.

(O)

Check the process status displayed for process-ID, and forcibly stop the process as necessary.

KAVE00308-I

View Server was started in the PFM authentication mode. (host=host-name, service=service-ID)

View Server is being started in the PFM authentication mode.

(S)

Starts View Server in the PFM authentication mode.

KAVE00309-I

View Server was started in the JP1 authentication mode. (host=host-name, service=service-ID)

View Server is being started in the JP1 authentication mode.

(S)

Starts View Server in the JP1 authentication mode.

KAVE00310-W

An attempt to read the authentication mode has failed. (host=host-name, service=service-ID)

An attempt to read the authentication mode failed due to invalid authentication mode settings.

(S)

Starts View Server in the PFM authentication mode.

(O)

Check the authentication mode settings.

KAVE00311-E

The alias name is invalid. (Host Alias Name=alias-name)

The host name could not be acquired because the alias name was invalid.

(S)

Suppresses starting services during initializing services.

If a service is already running, an error message will be returned without acquiring the host name.

(O)

Specify a valid alias name.

You can use 1 to 32 single-byte alphanumeric characters.

You cannot specify localhost or an IP address for the alias name.

KAVE00312-E

The setting used for acquiring the physical host name is invalid. (Get Host Mode=value)

The host name could not be acquired because the settings for the function for setting monitoring-host names are invalid.

(S)

Suppresses starting services during initializing services.

If a service is already running, an error message will be returned without acquiring the host name.

(O)

Change the settings for the function for setting monitoring-host names. You can specify only 0, 1, or 2.

KAVE00313-E

The alias name is the same as the logical host name. (Host Alias Name=alias-name)

The same host name is specified for the both logical and physical hosts on the same host.

(S)

Suppresses starting of services while initializing services if the function for setting monitoring-host names is enabled.

Returns an error without acquiring the host name while starting up services if the function for setting monitoring-host names is enabled.

(O)

Change the alias name.

KAVE00314-E

The logical host name is the same as the physical host name. (lhost=logical-host--name)

An attempt to set up the logical host environment has failed because the specified logical host name is the same as the alias name on the same host.

(S)

Cancels processing.

(O)

Change the logical host name.

KAVE00315-E

The installed agent does not support the functionality for changing a physical host name.

PFM - Agent that does not support the function for setting monitoring-host names has been installed.

(S)

Cancels processing.

(O)

PFM - Agent that does not support the function for setting monitoring-host names might have been installed.

If you want to continue operations with the current environment, change the settings to acquire real host names as the host names.

KAVE00316-E

The functionality for binding multiple alarm tables will now be disabled because an invalid value was set. (label=label-name, specified value=specified-value)

The functionality for binding multiple alarm tables will now be disabled because an invalid value has been set. label-name indicates the label name to which the invalid value has been set. specified-value indicates the invalid value.

(S)

Continues processing by disabling the functionality for binding multiple alarm tables.

(O)

Check the value specified for the label name in the jpccomm.ini file.

KAVE00317-W

Multiple alarm tables will now be unbound because the functionality for binding multiple alarm tables is disabled. (service=service-ID)

All of the alarm tables being bound will now be unbound because the functionality for binding multiple alarm tables was disabled.

(S)

Unbinds all of the alarm tables that are bound to PFM - Agent indicated by service-ID.

(O)

If PFM - Agent indicated by service-ID is running, restart PFM - Agent to apply the updated status of the alarm table bind condition. Also, reconfigure the bind settings for PFM- Agent indicted by service-ID, if necessary.

KAVE00318-W

The setting for the PFM service auto-restart functionality will be reset to the default setting because the current setting is invalid. (service=service-ID, label=label-name, previous value=specified-value, current value=applied-value)

The settings for the PFM automatic service restart function will now be reset to the default because the current settings are invalid. If the settings are directly under Restart Configurations, service=service-ID will not be displayed.

(S)

Changes the specified value for the label name of the service ID to the default value that is indicated by applied-value.

(O)

Use PFM - Web Console to check the value indicated by the service-ID and label-name.

KAVE00319-W

The scheduled restart functionality will be disabled because the setting for the PFM service auto-restart functionality is invalid. (service=service-ID)

The scheduled restart functionality for the service indicated by service-ID will now be disabled because the settings for the PFM automatic service restart function are invalid.

(S)

Disables the scheduled restart functionality for the service indicated by service-ID.

(O)

Use PFM - Web Console to check the settings for the service that is indicated by service-ID.

KAVE00320-I

The service will start with the functionality for binding multiple alarm tables disabled. (host=host-name, service=service-ID)

The service will now start with the functionality for binding multiple alarm tables disabled.

(S)

Starts the service with the functionality for binding multiple alarm tables disabled.

KAVE00321-I

The service will start with the functionality for binding multiple alarm tables enabled. (host=host-name, service=service-ID)

The service will now start with the functionality for binding multiple alarm tables enabled.

(S)

Starts the service with the functionality for binding multiple alarm tables enabled.

KAVE00322-W

PFM service auto-restart functionality will run with the default setting temporarily because the current setting is invalid. (service=service-ID, label=label-name, applied value=applied-value)

The PFM automatic service restart function will now run with the default settings temporarily because the current settings are invalid. The current settings will not be updated. If the invalid settings are directly under Restart Configurations, service=service-ID will not be displayed.

(S)

Starts the function by using the default setting that is indicated by applied-value for the value indicated by label-name of service-ID.

(O)

Use PFM - Web Console to check the value indicated by label-name of service-ID.

KAVE00323-W

The auto-restart functionality has failed to check a status of a service. (service=service-ID)

The auto-restart functionality has failed to check the operating status of a service. service-ID is the ID of the service for which a check for the operating status failed.

This message is output when an access to the file that manages the service status failed. Possible causes of the access error are as follows:

The file is locked by an external application, such as a virus scan program.

Processing is concentrated on the target service, so status updates frequently occur.

The operating status of the service will be checked again after the interval set in Auto Restart - Interval. If this message is not output for the same service at the next check, there is no problem.

(S)

Cancels checking of the operating status of this service, and continues checking of the operating status of other services.

(O)

If this message is repeatedly output for the same service, execute the jpctool service list command to check the status of the target service. Restart the service if it is stopped.

KAVE00324-W

The auto-restart functionality has detected an abnormal termination of a service. (service=service-ID, reason=cause)

The automatic service restart function has detected an abnormal termination of a service. service-ID indicates the terminated service. cause indicates the error cause.

(S)

Attempts to restart the service by using the automatic service restart function.

KAVE00325-I

The auto-restart functionality will restart the service. (host=host-name, servicekey=service-key, inst=instance-name)

The automatic service restart function will restart the service that was abnormally terminated. host-name, service-key, and instance-name indicate the information about the service to be restarted. Note that inst=instance-name will not be displayed for a service of PFM - Manager or single-instance PFM - Agent.

(S)

Starts the service indicated by service-key and instance-name.

KAVE00326-I

The scheduled restart functionality will stop the service. (service=service-ID)

The scheduled restart functionality will now stop the service. service-ID indicates the ID of the service to be stopped.

(S)

Stops the service indicated by service-ID.

KAVE00327-I

The scheduled restart functionality will restart the service. (host=host-name, servicekey=service-key, inst=instance-name)

The scheduled restart functionality will now restart the service. host-name, service-key, and instance-name indicate the service to be restarted. Note that inst=instance-name will not be displayed for a service of PFM - Manager or single-instance PFM - Agent.

(S)

Starts the service indicated by service-key and instance-name.

KAVE00328-E

An attempt to stop the service failed. (service=service-ID)

An attempt to stop the service has failed. service-ID indicates the service ID of the service that could not be stopped.

(S)

Cancels processing of scheduled restarting. The system will not restart the service.

(O)

Check and correct the problem, and then manually stop and restart the service. To determine the cause of the problem, check the message output prior to this message.

KAVE00329-E

An attempt to restart the service failed. (host=host-name, servicekey=service-key, inst=instance-name)

An attempt to restart the service failed. host-name, service-key, and instance-name indicate the service that could not be started. Note that inst=instance-name will not be displayed for a service of PFM - Manager or single-instance PFM - Agent.

(S)

Cancels restart processing for the service.

(O)

Check and correct the problem, and then manually restart the service. To determine the cause of the problem, check the message output prior to this message.

KAVE00330-E

The service cannot be restarted because the maximum number of consecutive attempts to restart it has been reached. (service=service-ID, count=number-of-consecutive-attempts-to-restart)

The automatic service restart function cannot restart the service because the number of consecutive attempts to restart the service has been reached the maximum. service-ID indicates the service ID of the service that exceeded the maximum number of consecutive attempts to restart.

(S)

Cancels processing to restart the service.

(O)

Check and correct the problem that abnormally terminated the service. To determine the cause of the problem, check the message output by the service.

KAVE00331-E

An attempt to acquire the list containing information about the agent service has failed.

An attempt to acquire the list of agent services has failed.

(S)

Continues processing. Some PFM - Agent might not be displayed on the list due to the invalid list status.

(O)

Check the following:

- Whether the command was executed on the standby node while PFM - Manager had been set up on the logical host

In this case, re-execute the command on the executing node for PFM - Manager.

- Whether the file of the agent service list exists

- Whether you have permission to access the agent service list (permission to read and write)

In this case, stop the PFM - Manager services and then perform the following:

If the agent service list does not exist, copy the setagentlist.ini.model file and save it as setagentlist.ini.#

If the access permission for the agent service list has not been set, specify the appropriate access permission.

# Copy the setagentlist.ini.model file and save it as setagentlist.ini to initialize the settings for the agent service list. Register desired agents to display as necessary. For details about how to register agents, see the chapter that describes the jpcconf agent setup command.

KAVE00332-E

An attempt to modify the list containing information about the agent service has failed.

An attempt to update the list of agent services has failed.

(S)

Continues processing. Some PFM - Agent might not be displayed on the list due to the invalid list status.

(O)

Check the following:

- Whether the command was executed on the standby node while PFM - Manager had been set up on the logical host

In this case, re-execute the command on the executing node for PFM - Manager.

- Whether the file for the agent service list exists

- Whether you have permission to access the agent service list (permission to read and write)

In this case, stop the PFM - Manager services and then perform the following:

If the agent service list does not exist, copy the setagentlist.ini.model file and save it as setagentlist.ini.#

If the access permission for the agent service list has not been set, specify the appropriate access permission.

# Copy the setagentlist.ini.model file and save it as setagentlist.ini to initialize the settings for the agent service list. Register desired agents to display as necessary. For details about how to register agents, see the chapter that describes the jpcconf agent setup command.

KAVE00333-E

The status of the Collector service becomes either busy or abnormal stop. (host=host-name, service=service-ID)

The Store service detected that the status of the Collector service changed to either busy or abnormal stop.

(S)

Continues processing.

(O)

Check the common message log for the host that issued the event, and then correct the problem that changed the status to busy or an abnormal stop. If you are unable to determine the cause, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00334-I

The status of the Collector service recovered from busy or abnormal stop. (host=host-name, service=service-ID)

The Store service detected that the status of the Collector service changed from either busy or abnormal stop to active.

(S)

Continues processing.

KAVE00335-I

The PFM service has started. (host = host-name, service = service-ID)

The PFM service has started.

(S)

Starts to process the PFM service.

KAVE00336-I

The PFM service has stopped. (host = host-name, service = service-ID)

The PFM service has stopped.

(S)

Stops processing.

KAVE00337-E

An attempt to start the PFM service has failed. (host = host-name, service = service-ID)

An attempt to start the PFM service has failed.

(S)

Cancels processing.

(O)

Check the message that was output prior to this message.

KAVE00338-W

The setting JP1 System Event functionality will be the default setting because the current setting is invalid. (label=label-name, previous value=specified-value)

The settings of the JP1 System Event functionality will now be changed to the default because the current settings are invalid. label-name indicates the property whose setting is invalid, and specified-value indicates the invalid value.

(S)

Sets the default value because the current value specified for the property is invalid.

(O)

Use PFM - Web Console to revise the value specified for label-name.

KAVE00339-E

The PFM service stopped abnormally. (host = host-name, service = service-ID)

The PFM service has stopped abnormally.

(S)

Stops to process the PFM service.

(O)

Check the cause of the problem that has been output to the common message log for the host that issued the event.

KAVE00342-I

The service will start with the product name display functionality disabled. (host=host-name, service=service-ID)

The service will now start with the product name display functionality disabled.

(S)

Starts the service with the product name display functionality disabled.

KAVE00343-I

The service will start with the product name display functionality enabled. (host=host-name, service=service-ID)

The service will now start with the product name display functionality enabled.

(S)

Starts the service with the product name display functionality enabled.

KAVE00344-E

An attempt to register the action execution service information has failed. (service=service-ID, count=number-of-successfully-registered-actions/number-of-actions-to-be-registered)

Registration of the action execution service information specified in the alarm definition has failed because communication could not be established with PFM - Manager.

(S)

Continues processing.

(O)

Check the following:

Whether PFM - Manager is running

Whether a communication connection can be established with PFM - Manager

If a connection with PFM - Manager can be successfully established, the service indicated by service-ID might have been set as the action execution service for an excessive number of actions.

Use one of the following methods to reduce the number of actions to no more than number-of-successfully-registered-actions, and then restart the service indicated by service-ID, re-execute the jpctool alarm command, or retry the operation in the GUI window of PFM - Web Console respectively:

If the error occurred when the service indicated by service-ID started:

Set multiple Action Handler services as the action execution Action Handlers.

Set the action execution Action Handlers to LOCAL.

If the error occurred when the jpctool alarm command was executed or when an operation was performed in the GUI window of PFM - Web Console:

Process based on alarms, not on alarm tables.

Calculate the number of actions as follows:

number-of-actions = Total of number-of-triggers(Abnormal/Warning/Normal)-for-sending-emails and number-of-triggers(Abnormal/Warning/Normal)-for-executing-commands for the alarms for which the service indicated by service-ID is set as the action execution service

Example: Alarm alarm1 exists on alarm table Table1, and alarm alarm2 on alarm table Table2. If the action execution Action Handler is set to PH1Host1 and the triggers for sending emails and executing commands are set as follows in the action settings for individual alarms, the number of actions can be calculated as follows:

alarm1 : Emails (Abnormal, Warning)

Commands (Normal)

alarm2 : Emails (Abnormal)

Commands (Normal)

number-of-actions-for-which-action-execution-Action-Handler-is-set-to-PH1Host1 = 3 (number-of-triggers-for-sending-emails-for-alarm1 + number-of-triggers-for-executing-commands-for-alarm1) + 2 (number-of-triggers-for-sending-emails-for-alarm2 + number-of-triggers-for-executing-commands-for-alarm2) = 5

If this message is output when you import an alarm table from PFM - Web Console, restart the Action Handler service indicated by service-ID.

KAVE00345-E

An attempt to delete the action execution service information has failed. (service=service-ID, count=number-of-successfully-deleted-actions/number-of-actions-to-be-deleted)

An attempt to delete the action execution service information specified in the alarm definition has failed because communication could not be established with PFM - Manager.

(S)

Continues processing.

(O)

Check the following:

Whether PFM - Manager is running

Whether a communication connection can be established with PFM - Manager

If a connection with PFM - Manager can be successfully established, the service indicated by service-ID might have been set as the action execution service for an excessive number of actions.

User one of the following methods to reduce the number of actions to no more than number-of-successfully-registered-actions, and then restart the service indicated by service-ID, re-execute the jpctool alarm command, or retry the operation in the GUI window of PFM - Web Console respectively:

If the error occurred when the service indicated by service-ID started:

Set multiple Action Handler services as the action execution Action Handlers.

Set the action execution Action Handlers to LOCAL.

If the error occurred when the jpctool alarm command was executed or when an operation was performed in the GUI window of PFM - Web Console:

Process based on alarms, not on alarm tables.

Calculate the number of actions as follows:

number-of-actions = Total of number-of-triggers(Abnormal/Warning/Normal)-for-sending-emails and number-of-triggers(Abnormal/Warning/Normal)-for-executing-commands for the alarms for which the service indicated by service-ID is set as the action execution service

Example: Alarm alarm1 exists on alarm table Table1, and alarm alarm2 on alarm table Table2. If the action execution Action Handler is set to PH1Host1 and the triggers for sending emails and executing commands are set as follows in the action settings for individual alarms, the number of actions can be calculated as follows:

alarm1 : Emails (Abnormal, Warning)

Commands (Normal)

alarm2 : Emails (Abnormal)

Commands (Normal)

number-of-actions-for-which-action-execution-Action-Handler-is-set-to-PH1Host1 = 3 (number-of-triggers-for-sending-emails-for-alarm1 + number-of-triggers-for-executing-commands-for-alarm1) + 2 (number-of-triggers-for-sending-emails-for-alarm2 + number-of-triggers-for-executing-commands-for-alarm2) = 5

KAVE00346-E

Processing to register the action execution service information has failed. (service=service-ID, count=number-of-successfully-registered-actions)

Registration of the action execution service information that was specified in the alarm definition and requested from the service indicated by service-ID has failed.

(S)

Continues processing.

(O)

Check the following:

Whether the service indicated by service-ID is running

Whether a communication connection can be established with the service indicated by service-ID

If a connection with the service indicated by service-ID can be successfully established, the service might have been set as the action execution service for an excessive number of actions. Use either of the following methods to change the action execution service, and then restart the service indicated by service-ID:

Set multiple Action Handler services as the action execution Action Handlers.

Set the action execution Action Handlers to LOCAL.

Calculate the number of actions as follows:

number-of-actions = Total of number-of-triggers(Abnormal/Warning/Normal)-for-sending-emails and number-of-triggers(Abnormal/Warning/Normal)-for-executing-commands for the alarms for which the service indicated by service-ID is set as the action execution service

Example: Alarm alarm1 exists on alarm table Table1, and alarm alarm2 on alarm table Table2. If the action execution Action Handler is set to PH1Host1 and the triggers for sending emails and executing commands are set as follows in the action settings for individual alarms, the number of actions can be calculated as follows:

alarm1 : Emails (Abnormal, Warning)

Commands (Normal)

alarm2 : Emails (Abnormal)

Commands (Normal)

number-of-actions-for-which-action-execution-Action-Handler-is-set-to-PH1Host1 = 3 (number-of-triggers-for-sending-emails-for-alarm1 + number-of-triggers-for-executing-commands-for-alarm1) + 2 (number-of-triggers-for-sending-emails-for-alarm2 + number-of-triggers-for-executing-commands-for-alarm2) = 5

KAVE00347-E

Processing to delete the action execution service information has failed. (service=service-ID, count=number-of-successfully-deleted-actions)

An attempt to delete the action execution service information that was specified in the alarm definition and requested from the service indicated by service-ID has failed.

(S)

Continues processing.

(O)

Check the following:

Whether the service indicated by service-ID is running

Whether a communication connection can be established with the service indicated by service-ID

If a connection with the service indicated by service-ID can be successfully established, the service might have been set as the action execution service for an excessive number of actions. Use either of the following methods to change the action execution service, and then restart the service indicated by service-ID:

Set multiple Action Handler services as the action execution Action Handlers.

Set the action execution Action Handlers to LOCAL.

Calculate the number of actions as follows:

number-of-actions = Total of number-of-triggers(Abnormal/Warning/Normal)-for-sending-emails and number-of-triggers(Abnormal/Warning/Normal)-for-executing-commands for the alarms for which the service indicated by service-ID is set as the action execution service

Example: Alarm alarm1 exists on alarm table Table1, and alarm alarm2 on alarm table Table2. If the action execution Action Handler is set to PH1Host1 and the triggers for sending emails and executing commands are set as follows in the action settings for individual alarms, the number of actions can be calculated as follows:

alarm1 : Emails (Abnormal, Warning)

Commands (Normal)

alarm2 : Emails (Abnormal)

Commands (Normal)

number-of-actions-for-which-action-execution-Action-Handler-is-set-to-PH1Host1 = 3 (number-of-triggers-for-sending-emails-for-alarm1 + number-of-triggers-for-executing-commands-for-alarm1) + 2 (number-of-triggers-for-sending-emails-for-alarm2 + number-of-triggers-for-executing-commands-for-alarm2) = 5

KAVE00348-W

An attempt to send the alarm definition to an Agent failed. (service=service-ID)

The alarm definition is in an invalid state in the Agent because an attempt to distribute the action definition to the Agent failed.

(S)

Continues processing.

(O)

Confirm that the Agent is running, and if it is not, restart the Agent because it might have stopped. Also, revise the network settings such as the firewall, and re-bind the alarm from PFM - WebConsole or restart the Agent because there might be a problem in the network.

KAVE00349-I

The service will start with the metric-output at alarm-recovery function enabled. (host=host-name, service=service-ID)

The service will start with the function for measurement value output at alarm recovery enabled.

(S)

Starts with the function for measurement value output at alarm recovery enabled.

(O)

If this message is output at the Name Server, the settings will be applied to the PFM - Agent and PFM - RM that start or restart after the message is output. If you change the settings, restart PFM - Agent and PFM - RM.

KAVE00350-I

The service will start with the metric-output at alarm-recovery function disabled. (host=host-name, service=service-ID)

The service will start with the function for measurement value output at alarm recovery disabled.

(S)

Starts the service with the function for measurement value output at alarm recovery disabled.

(O)

If this message is output at the Name Server, the settings will be applied to the PFM - Agent and PFM - RM that start or restart after the message is output. If you change the settings, restart PFM - Agent and PFM - RM.

KAVE00351-W

The metric-output at alarm-recovery function will now be disabled because an invalid value was set.(label=label-name, specified value=specified-value)

The service will start with the function for measurement value output at alarm recovery disabled because an invalid value was set.

label-name indicates the label name for which an invalid value was set. specified-value indicates the invalid value that was set.

(S)

Starts the service with the function for measurement value output at alarm recovery disabled.

(O)

Check and, if necessary, revise the setting value specified by label-name in the jpccomm.ini file.

KAVE00352-W

The setting of historical data collection was changed. (service=service-ID, record=record-name, log=new-collection-setting)

The setting of historical data collection has been changed.

(S)

Changes the setting of historical data collection.

If log = Yes, the setting of historical data collection for the record-name record becomes enabled.

If log = No, the setting of historical data collection for the record-name record is cleared. In this case, historical data generated after this message is output cannot be displayed.

(O)

If log = Yes, change the properties (such as Collection Interval) regarding data collection for the record-name record as necessary.

If log = No, no special actions are required.

KAVE00353-W

The Correlator quick start function will be disabled because one or more invalid values are set. (label=label-name, specified value=specified-value)

The Correlator quick start function will be disabled because one or more invalid values are set.

label-name indicates the label name for which invalid values are set. specified-value indicates the invalid values that are set.

(S)

Disables the Correlator quick start function and continues processing.

(O)

Check the setting values specified for label-name in the jpccomm.ini file.

KAVE00354-I

The service will start with the Correlator quick start function disabled. (host=host-name, service=service-ID)

The service will start with the Correlator quick start function disabled.

(S)

Starts the service with the Correlator quick start function disabled.

KAVE00355-I

The service will start with the Correlator quick start function enabled (host=host-name, service=service-ID)

The service will start with the Correlator quick start function enabled.

(S)

Starts the service with the Correlator quick start function enabled.

KAVE00356-W

The alarm status reacquisition function will be enabled because one or more invalid values are set. (label=label-name, specified value=specified-value)

The alarm status reacquisition function will be enabled because one or more invalid values are set.

label-name indicates the label name for which invalid values are set. specified-value indicates the invalid values that are set.

(S)

Enables the alarm status reacquisition function and continues processing.

(O)

Check the setting values specified for label-name in the jpccomm.ini file.

KAVE00357-I

The service will start with the alarm status reacquisition function disabled. (host=host-name, service=service-ID)

The service will start with the alarm status reacquisition function disabled.

(S)

Starts the service with the alarm status reacquisition function disabled.

KAVE00358-I

The service will start with the alarm status reacquisition function enabled. (host=host-name, service=service-ID)

The service will start with the alarm status reacquisition function enabled.

(S)

Starts the service with the alarm status reacquisition function enabled.

KAVE00359-W

Correlator was not able to acquire alarm status information from Collector. (service=service-ID)

The Correlator service was not able to acquire alarm status information from the Collector service. The alarm status information will be acquired again when an alarm event is received from the corresponding agent because the Correlator quick start function or the alarm status reacquisition function is enabled.

service-ID indicates the agent from which the alarm status information could not be acquired.

(S)

Acquires the alarm status information again when an alarm event is received from the corresponding agent. At this time, the alarm status information for the agent is assumed to be in either of the following statuses:

If no alarm events have been received from the agent since the Correlator service started:

The same status as when PFM - Manager was last stopped

If alarm events have been received from the agent since the Correlator service started:

The status determined based on the alarm events received after the Correlator service started

(O)

If the alarm status information displayed on PFM - Web Console differs from the status of the actual agent and if immediate status synchronization is required, restart the corresponding agent or bind the alarm table to the agent again.

KAVE00360-I

Correlator successfully acquired alarm status information from Collector by retrying. (service=service-ID)

Correlator successfully acquired alarm status information from Collector during alarm status reacquisition processing.

service-ID indicates the agent from which the alarm status information was acquired.

(S)

Operates using the acquired alarm status information.

KAVE00361-E

An attempt to read the configuration file failed. (file=file-name, section=section-name, label=label-name)

An attempt to read the configuration file failed. If this message is output while the service is starting, the configuration cannot be correctly read.

(S)

Suspends the service's startup processing.

(O)

Restart the service.

KAVE00363-W

The business group access control function will now be disabled because an invalid value was specified. (label=label-name, specified value=specified-value)

The service will start with the business group access control function disabled because an invalid value was set.

label-name indicates the label name for which an invalid value was set. specified-value indicates the invalid value that was set.

(S)

Starts the service with the business group access control function disabled.

(O)

Check and, if necessary, revise the setting values specified for label-name in the jpccomm.ini file.

KAVE00364-E

An error occurred during reading the configuration file. (file=file-name, section=section, label=label-name)

An attempt to access the configuration file failed.

(S)

Cancels restart processing for the service.

(O)

Check file-name, section, and label-name in this message. Check and, if necessary, revise the section name, label name, and setting values in the configuration file, and then restart the service. If this message is still output, check whether you have permission to access the configuration file (permission to read and write). If the cause cannot be determined, collect maintenance information and contact the system administrator.

KAVE00365-I

The service will start with the business group access control function enabled.

The service will start with the business group access control function enabled.

(S)

Starts the service with the business group access control function enabled.

KAVE00366-I

The service will start with the option for restricting remote operation from Agent hosts disabled.

The service will start with the option for restricting remote operation from Agent hosts disabled.

(S)

Starts the service with the option for restricting remote operation from Agent hosts disabled.

KAVE00367-I

The service will start with the option for restricting remote operation from Agent hosts enabled.

The service will start with the option for restricting remote operation from Agent hosts enabled.

(S)

Starts the service with the option for restricting remote operation from Agent hosts enabled.

KAVE00368-W

The option for restricting remote operation from Agent hosts will now be disabled because an invalid value was specified. (label=label-name, specified value=specified-value)

The service will start with the option for restricting remote operation from Agent hosts disabled because an invalid value was set.

label-name indicates the label name for which an invalid value was set. specified-value indicates the invalid value that was set.

(S)

Starts the service with the option for restricting remote operation from Agent hosts disabled.

(O)

Check and, if necessary, revise the setting value specified for label-name in the jpccomm.ini file.

KAVE00369-W

The option for restricting remote operation from Agent hosts will now be enabled because an attempt to acquire a setting failed.

The service will start with the option for restricting remote operation from Agents hosts enabled because an attempt to acquire the setting failed.

(S)

Starts the service with the option for restricting remote operation from Agent hosts enabled.

(O)

Check and, if necessary, revise the section name, label name, and specified setting values in the jpccomm.ini file.

KAVE00370-I

The service will start with the option for restricting the viewing of service information from Agent hosts disabled.

The service will start with the option for restricting the viewing of service information from Agent hosts disabled.

(S)

Starts the service with the option for restricting the viewing of service information from Agent hosts disabled.

KAVE00371-I

The service will start with the option for restricting the viewing of service information from Agent hosts enabled. (label=label-name, specified value=specified-value)

The service will start with the option for restricting the viewing of service information from Agent hosts enabled.

label-name indicates the label name for which a valid value was set. specified-value indicates the valid value that was set.

(S)

Starts the service with the option for restricting the viewing of service information from Agent hosts enabled.

KAVE00372-W

The option for restricting the viewing of service information from Agent hosts will now be disabled because an invalid value was specified. (label=label-name, specified value=specified-value)

The service will start with the option for restricting the viewing of service information from Agent hosts disabled because an invalid value was set.

label-name indicates the label name for which an invalid value was set. specified-value indicates the invalid value that was set.

(S)

Starts the service with the option for restricting the viewing of service information from Agent hosts disabled.

(O)

Check and, if necessary, revise the setting value specified for label-name in the jpccomm.ini file.

KAVE00373-W

The option for restricting the viewing of service information from Agent hosts will now be enabled because an attempt to acquire a setting failed.

The service will start with the option for restricting the viewing of service information from Agent hosts enabled because an attempt to acquire the setting failed.

(S)

Starts the service with the option for restricting the viewing of service information from Agent hosts enabled.

(O)

Check and, if necessary, revise the section name, label name, and specified setting values in the jpccomm.ini file.

KAVE00374-E

An alarm definition failed to be updated and is in an invalid state. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An alarm definition failed to be updated and is in an invalid state. Update the displayed alarm definition again.

product-ID, alarm-table-name, and alarm-name provide information about the invalid alarm definition.

(S)

Suspends update processing for the alarm definition.

(O)

The alarm definition is in an invalid state. Update the displayed alarm definition again.

KAVE00375-W

An attempt to delete action execution service information failed. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An attempt to delete action execution service information failed when an alarm was modified. After an alarm is modified, an action that is executed when the status of the alarm is changed back to normal might be executed. Behavior of the modified alarm and the action are not affected.

product-ID, alarm-table-name, and alarm-name provide information about the alarm definition for which deletion of action execution service information failed.

(S)

Continues processing.

KAVE00376-W

An attempt to send an action definition to an Action Handler failed. (service=service-ID, product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An attempt to send an action definition to an Action Handler failed and the action definition of the Action Handler is in an invalid state.

service-ID indicates the ID of the Action Handler service to which sending of an action definition failed.

product-ID, alarm-table-name, and alarm-name provide information about the alarm definition for which the action definition was not successfully sent.

(S)

Continues processing.

(O)

The Action Handler might have been stopped. Check whether the Action Handler is running, and restart it if it is stopped. Also, there might be a network problem. Check and, if necessary, revise the network settings, such as the Firewall settings, and then rebind the alarm from PFM - Web Console or restart the Action Handler.

KAVE00377-W

The number of alarms to be bound exceeds the recommended number. (service=service-ID, number of alarms=number-of-alarms)

The number of alarms to be bound exceeded the recommended value.

service-ID indicates the agent for which the number of alarms to be bound exceeded the recommended value. number-of-alarms indicates the number of bound alarms.

(S)

Continues processing.

(O)

Set the alarms again so that the number of alarms to be bound will not exceed the recommended value.

KAVE00378-E

The number of alarms to be bound exceeds the limit. (service=service-ID, number of alarms=number-of-alarms)

Processing cannot continue because the number of alarms to be bound exceeded the limit value. Set the alarms again so that the number of alarms to be bound will not exceed the limit value.

service-ID indicates the agent for which the number of alarms to be bound exceeded the limit value. number-of-alarms indicates the number of bound alarms.

(S)

Cancels processing.

(O)

Set the alarms again so that the number of alarms to be bound will not exceed the limit value.

KAVE00379-W

The number of alarms to be bound exceeds the limit. (service=service-ID, number of alarms=number-of-alarms)

The number of alarms to be bound exceeded the limit value. Set the alarms again so that the number of alarms to be bound will not exceed the limit value.

service-ID indicates the agent for which the number of alarms to be bound exceeded the limit value. number-of-alarms indicates the number of bound alarms.

(S)

Continues processing.

(O)

Set the alarms again so that the number of alarms to be bound will not exceed the limit value.

KAVE00380-E

An alarm table cannot be bound because the number of alarms to be bound exceeds the limit.

An alarm table cannot be bound because the number of alarms to be bound exceeded the limit value.

(S)

Cancels processing.

(O)

Check the KAVE00378-E message output in the common message log, and set the alarms again so that the number of alarms to be bound to the target agent will not exceed the limit value.

KAVE00381-E

An alarm cannot be added to the alarm table because the number of alarms to be bound exceeds the limit.

An alarm cannot be added to the alarm table because the number of alarms to be bound exceeded the limit value.

(S)

Cancels processing.

(O)

Check the KAVE00378-E message output in the common message log, and set the alarms again so that the number of alarms to be bound to the corresponding agent will not exceed the limit value.

KAVE00390-E

A request was received from ITSLM for which no linkage settings are specified. (host=ITSLM-host)

Linkage settings have not been configured for a host whose name was specified in a request received from ITSLM.

(S)

Suspends processing.

(O)

Check whether the linkage settings and the settings on ITSLM match.

KAVE00391-E

An attempt to get information from Master Manager failed.

An attempt to acquire information from a database managed by Master Manager failed.

(S)

Suspends processing.

(O)

Check whether Master Manager is running and connected.

KAVE00392-E

An attempt to communicate with an Agent failed. (service=service-ID)

An attempt to communicate with an Agent/RM Collector failed.

(S)

Suspends processing for the corresponding Agent/RM Collector.

(O)

Check whether the Agent/RM Collector is running and connected.

KAVE00393-E

An attempt to communicate with the Collector service failed. (service=service-ID)

An attempt to communicate with the Agent/RM Collector service failed.

(S)

Suspends processing.

(O)

Check whether the Agent/RM Store service is running and connected.

KAVE00394-E

An attempt to communicate with the Store service failed. (service=service-ID)

An attempt to communicate with the Agent/RM Store service failed.

(S)

Suspends processing.

(O)

Check whether the Agent/RM Store service is running and connected.

KAVE00395-W

An attempt to read from the database failed. (service=service-ID, database=database)

An attempt to read from the database failed.

(S)

Continues processing with the assumption that linkage has not been established with ITSLM.

(O)

Collect maintenance information and contact the system administrator.

KAVE00396-E

An attempt to update the database failed. (service=service-ID, database=database)

An attempt to update the database failed.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator.

KAVE00397-E

An attempt to delete the database failed. (service=service-ID, database=database)

An attempt to delete the data files (*.DB), index files (*.IDX), and lock files (*.LCK) which make up the database failed.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator.

KAVE00398-W

An attempt to delete the database failed. (service=service-ID, database=database)

An attempt to delete the data files (*.DB), index files (*.IDX), and lock files (*.LCK) which make up the database failed.

(S)

If the database is COSLMMI, continues processing with the assumption that linkage with ITSLM is not established.

If the database is MASUSPEND, the next time the monitoring suspension function is enabled, the previously used settings are inherited. To delete unnecessary settings, execute the jpcconf monitor resume command when the monitoring suspension function is enabled. Note that the behavior while the monitoring suspension function is disabled is not affected.

(O)

Collect maintenance information and contact the system administrator.

KAVE00399-E

An attempt to read the system file failed. (file=file)

An attempt to read the system file failed.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator.

KAVE00400-E

An attempt to read the system file failed. (file=file)

An attempt to read the system file failed.

(S)

Continues processing with the assumption that linkage has not been established with ITSLM.

(O)

Collect maintenance information and contact the system administrator.

KAVE00401-E

The format of the system file is invalid. (file=file)

An attempt to parse the system file failed.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator.

KAVE00402-E

The format of the system file is invalid. (file=file)

An attempt to parse the system file failed.

(S)

Continues processing with the assumption that linkage has not been established with ITSLM.

(O)

Collect maintenance information and contact the system administrator.

KAVE00403-E

An attempt to update the system file failed. (file=file)

An attempt to update the system file failed.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator.

KAVE00404-W

An attempt to read the connection information file failed. (service=service-ID)

An attempt to read the connection information file (jpcitslm.ini) failed.

(S)

Continues processing with the assumption that linkage has not been established with ITSLM.

(O)

Check the status of the connection information file.

KAVE00405-E

An attempt to update the connection information file failed. (service=service-ID)

An attempt to update the connection information file (jpcitslm.ini) failed.

(S)

Suspends processing.

(O)

Check the status of the connection information file.

KAVE00406-E

An attempt to delete the connection information file failed. (service=service-ID)

An attempt to delete the connection information file (jpcitslm.ini) failed.

(S)

Suspends processing.

(O)

Check the status of the connection information file.

KAVE00407-W

The format of the connection information file is invalid. (service=service-ID)

An attempt to parse the connection information file (jpcitslm.ini) failed.

(S)

Continues processing with the assumption that linkage has not been established with ITSLM.

(O)

Collect maintenance information and contact the system administrator.

KAVE00408-W

An attempt to read the definition file for custom monitoring items failed.

An attempt to read the definition file for custom monitoring items (monitoringitems.cfg) failed.

(S)

Continues processing with the assumption that the definition file for custom monitoring items has not been specified.

(O)

Check the status of the definition file for custom monitoring items.

KAVE00409-W

The format of the definition file for custom monitoring items is invalid. (line=line-number)

An attempt to parse the definition file for custom monitoring items (monitoringitems.cfg) failed. The format is invalid, or a field that cannot be specified as a monitoring item is included.

(S)

If the syntax version of the file or the format of character codes is invalid, the system continues processing with the assumption that the definition file for custom monitoring items has not been specified. If the format in a section or subsection is invalid, the system skips applying the corresponding section or subsection.

(O)

Check the settings in the definition file for custom monitoring items, and acquire the monitoring items from ITSLM again.

KAVE00410-E

The number of ITSLM hosts that can be linked exceeds the limit.

The number of ITSLM hosts set to be linked exceeded the number of ITSLM hosts that can be linked.

(S)

Suspends processing.

(O)

Update the window for managing properties, and check the linkage settings.

KAVE00411-W

An Agent that is not being managed is specified. (service=service-ID)

An Agent that is not being managed by Master Manager was specified.

(S)

Skips processing for the corresponding Agent/RM Collector.

(O)

Check the settings on ITSLM.

KAVE00412-E

A monitoring item that has a different data model version than the Agent was specified. (service=service-ID, Agent version=Agent-data-model-version, requested version=specified-data-model-version)

A monitoring item that has a different data model version than the Agent was specified.

(S)

Skips processing for the corresponding Agent/RM Collector.

(O)

Check the settings on ITSLM.

KAVE00413-E

A field that cannot be specified as a monitoring item was specified. (service=service-ID, record=record-name, field=field)

A field that cannot be specified as a monitoring item was specified.

(S)

Skips processing for the corresponding Agent/RM Collector.

(O)

Check the settings on ITSLM.

KAVE00414-W

An attempt to start monitoring failed. (service=service-ID, error type=error-type)

An attempt to start monitoring a monitoring item for the Agent/RM indicated by service-ID failed due to an error indicated by error-type.

(S)

Skips processing for the corresponding Agent/RM Collector.

(O)

Check the Agent/RM Collector log.

KAVE00415-W

An attempt to stop monitoring failed. (service=service-ID, error type=error-type)

An attempt to stop monitoring a monitoring item for the Agent/RM indicated by service-ID failed due to an error indicated by error-type.

(S)

Skips processing for the corresponding Agent/RM Collector.

(O)

Check the Agent/RM Collector log.

KAVE00416-E

The specified Agent type does not exist. (product id=product-ID-of-the-specified-Agent)

An Agent type that is not managed by Master Manager was specified.

(S)

Suspends processing.

(O)

Check the settings on ITSLM.

KAVE00417-E

The specified data model version does not exist. (product id=product-ID-of-the-specified-Agent, version=specified-data-model-version)

A data model version that is not managed by Master Manager was specified.

(S)

Suspends processing.

(O)

Check the settings on ITSLM.

KAVE00418-E

The specified Agent is not running. (service=service-ID)

The specified Agent is not running.

(S)

Suspends processing.

(O)

Start the Agent/RM, and re-execute processing.

KAVE00419-E

An attempt to retrieve a property from Service Response failed. (service=service-ID)

An attempt to retrieve a property from Service Response failed.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator.

KAVE00420-E

An attempt to filter the monitoring items failed. (service=service-ID, item=monitoring-item-ID)

An attempt to filter the monitoring items failed.

(S)

Suspends processing.

(O)

Check the settings on ITSLM.

KAVE00421-I

An attempt to send data to ITSLM failed. (host=ITSLM-host-name, port=ITSLM-port-number, interval=interval-time)

An attempt to send data to ITSLM failed.

(S)

Resends data after the interval time (units: seconds).

KAVE00422-W

The number of events waiting to be processed reached the limit.

The number of events waiting to be processed reached the limit. New events will not be accepted until currently waiting events are processed.

(S)

Continues processing.

(O)

Send processing is delayed. Check whether there is a stopped service.

Restart the service if necessary.

KAVE00423-E

An attempt to send an event failed. (service=service-ID)

An attempt to send an event to the service indicated by service-ID failed.

(S)

Suspends processing.

(O)

Check the status of the service indicated by service-ID. Restart the service if it is stopped.

KAVE00424-I

Alarm definition information was successfully sent. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm definition information was successfully sent.

product-ID, alarm-table-name, and alarm-name respectively indicate the product ID, alarm table name, and alarm name of the alarm definition that was successfully sent.

If an alarm table is bound to an agent, alarm-name becomes n/a.

If all alarm tables for an agent are unbound, both alarm-table-name and alarm-name become n/a.

(S)

Continues processing.

KAVE00425-I

Action definition information was successfully sent. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Action definition information was successfully sent.

product-ID, alarm-table-name, and alarm-name respectively indicate the product ID, alarm table name, and alarm name of the action definition that was successfully sent.

(S)

Continues processing.

KAVE00428-E

An attempt to send alarm definition information failed. (service=service-ID, product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An attempt to send alarm definition information failed.

service-ID indicates the service ID of the agent to which sending failed.

product-ID, alarm-table-name, and alarm-name respectively indicate the product ID, alarm table name, and alarm name of the alarm definition that was not successfully sent.

If an alarm table is bound to an agent, alarm-name becomes n/a.

If all alarm tables for an agent are unbound, both alarm-table-name and alarm-name become n/a.

(S)

Suspends send processing.

(O)

Perform one of the following operations:

Update the alarm indicated by alarm-name again.

Bind the alarm tables to the agent indicated by service-ID again.

Restart the agent indicated by service-ID.

KAVE00429-E

An attempt to send action definition information failed. (operate=operation, service=service-ID, product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An attempt to send action definition information failed.

service-ID indicates the service ID of the Agent or Action Handler to which sending failed.

product-ID, alarm-table-name, and alarm-name respectively indicate the product ID, alarm table name, and alarm name of the action definition that was not successfully sent.

(S)

Suspends send processing.

(O)

Perform either of the following operations:

Update the alarm indicated by alarm-name again.

Restart the agent or Action Handler indicated by service-ID.

KAVE00430-W

An attempt to send alarm definition information was interrupted. (service=agent-service-ID, product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm definition information will not be sent to an agent, and the PFM - Manager service will be stopped. When PFM - Manager is restarted, a request for alarm definition will be sent again to the corresponding agent.

product-ID, alarm-table-name, and alarm-name respectively indicate the product ID, alarm table name, and alarm name of the alarm definition that was interrupted.

(S)

Suspends processing. When restarting PFM - Manager, the system sends an alarm definition request to the corresponding agent.

KAVE00431-W

An attempt to send action definition information was interrupted. (service=Action-Handler-service-ID, product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Action definition information will not be sent to an Action Handler, and the PFM - Manager service will be stopped. When PFM - Manager is restarted, a request for action definition will be sent again to the Action Handler.

product-ID, alarm-table-name, and alarm-name respectively indicate the product ID, alarm table name, and alarm name of the action definition that was interrupted.

(S)

Suspends send processing. When restarting PFM - Manager, the system sends an action definition request to the corresponding Action Handler.

KAVE00432-E

An attempt to send action definition information was interrupted. (service=Action-Handler-service-ID, product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Action definition information will not be sent to an Action Handler, and the PFM - Manager service will be stopped. When PFM - Manager is restarted, restart the corresponding Action Handler.

product-ID, alarm-table-name, and alarm-name respectively indicate the product ID, alarm table name, and alarm name of the action definition that was interrupted.

(S)

Suspends send processing.

(O)

After PFM - Manager is restarted, restart the corresponding Action Handler service.

KAVE00433-E

An attempt to send a request to release or synchronize ITSLM linkage was interrupted.

Notification of release or synchronization of ITSLM linkage will not be sent to an agent, and PFM - Manager will be stopped. After PFM - Manager is restarted, set the properties again.

(S)

Suspends send processing.

(O)

After PFM - Manager is restarted, set the properties again.

KAVE00434-W

Definition information will be synchronized because the retransmission file is invalid.

Definition information will be synchronized for the services that need synchronization because the retransmission file is invalid.

(S)

Synchronizes definition information for the services that need synchronization.

KAVE00435-W

An attempt to delete the retransmission file failed. (file name=file-name)

An attempt to delete the retransmission file failed.

file-name indicates the full path to the file.

(S)

Continues processing.

(O)

Delete the file indicated by file-name.

KAVE00436-W

An attempt to save the events waiting to be sent failed.

An attempt to save the events waiting to be sent failed during stop processing. When PFM - Manager is restarted, synchronization will be performed with all services.

(S)

Continues stop processing. When PFM - Manager is restarted, synchronization will be performed with all services.

KAVE00437-I

Definition information will be synchronized. (service=service-ID)

Definition information will be synchronized with the service indicated by service-ID.

(S)

Synchronizes definition information.

If the service indicated by service-ID is an agent, all alarm statuses will be initialized.

KAVE00438-E

An attempt to update the node information cache failed. (host=host-name, service=service-ID).

An attempt to update the node information cache failed.

host-name indicates the PFM - Manager host name.

service-ID indicates the Name Server service ID.

(S)

Continues processing with the cache mode disabled.

(O)

Check whether a memory shortage has occurred in the system running PFM - Manager. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00439-I

The service will start with the node information cache mode disabled. (host=host-name, service=service-ID)

The service will start with the node information cache mode disabled.

host-name indicates the PFM - Manager host name.

service-ID indicates the Name Server service ID.

(S)

Starts the service with the node information cache mode disabled.

KAVE00440-I

Monitoring stopped for a monitoring item that is not managed by ITSLM. (service=service-ID)

Monitoring stopped for a monitoring item that is not managed by ITSLM.

(S)

No longer monitors the corresponding monitoring item.

KAVE00441-W

An attempt to stop monitoring a monitoring item that is not managed by ITSLM failed. (service=service-ID, error type=error-type)

An attempt to stop monitoring a monitoring item that is not managed by ITSLM failed due to an error indicated by error-type.

(S)

Continues sending the corresponding monitoring item.

(O)

Check the Agent/RM Collector log.

KAVE00442-E

The entered host name is invalid. (host=entered-host-name)

The host name included a character that cannot be used, or 64 or more characters have been entered.

(S)

Suspends processing.

(O)

Check the entered value.

KAVE00443-E

The Collector service does not support ITSLM linkage. (service=service-ID)

The Agent/RM Collector version does not support ITSLM linkage.

(S)

Suspends processing for the corresponding Agent/RM Collector.

(O)

To perform ITSLM linkage, the Agent/RM Collector version must be 10-00 or later.

KAVE00444-E

An attempt to synchronize definition information failed. (service=service-ID)

An attempt to synchronize definition information with the service indicated by service-ID failed.

The latest alarm definition or action definition is not applied, so alarm monitoring or action execution might not be performed correctly.

(S)

Suspends synchronizing definition information.

(O)

Restart the service indicated by service-ID.

KAVE00445-W

Because an attempt to send data to ITSLM failed, the data was deleted. (host=ITSLM-host-name, port=ITSLM-port-number, service=service-ID, record time=record-creation-date-and-time(YYYY/MM/DD hh:mm:ss))

service-ID indicates the service ID of the agent, remote agent, or group agent from which the discarded data was collected.

(S)

Does not resend the corresponding data.

(O)

Check whether ITSLM is running and the network settings between the Agent/RM and ITSLM.

KAVE00446-E

The number of monitoring items that can be linked to ITSLM exceeds the limit.(service=service-ID, monitoring=number-of-monitoring-items-being-monitored, requested=number-of-requested-monitoring-items)

Monitoring of monitoring items that exceed the maximum number of monitoring items (100) that can be linked to ITSLM was requested.

(S)

Does not start monitoring of the requested monitoring items. The system continues monitoring of the already monitored items.

(O)

Configure the setting so that the number of monitoring items for the corresponding Agent becomes no more than 100 on ITSLM, and then restart monitoring.

KAVE00447-I

A request of alarm table bind settings was successfully sent. (service=agent-service-ID)

A request for alarm table bind settings to an agent indicated by agent-service-ID was successfully sent.

(S)

Continues processing.

KAVE00448-E

An attempt to send a request of alarm table bind settings failed. (service=agent-service-ID)

A request for alarm table bind settings to an agent indicated by agent-service-ID failed.

(S)

Suspends the request for alarm table bind settings to the agent indicated by agent-service-ID.

(O)

Perform either of the following operations:

If no alarm tables are bound to the agent indicated by agent-service-ID, temporarily bind alarm tables, and then unbind all the alarm tables.

Restart the agent indicated by agent-service-ID.

KAVE00451-E

An attempt to register the node information failed. (register service=node-registration-source-service-ID, destination service=node-registration-destination-service-ID)

An attempt to register the node information from node-registration-source-service-ID to node-registration-destination-service-ID failed.

(S)

Continues processing.

(O)

If node-registration-destination-service-ID is the View Server service:

Execute the jpctool service sync command to synchronize service information.

If node-registration-destination-service-ID is other than the View Server service:

Restart the service indicated by node-registration-source-service-ID or node-registration-destination-service-ID.

KAVE00452-E

An attempt to delete the node information failed. (register service=node-deletion-source-service-ID, destination service=node-deletion-target-service-ID)

An attempt of node-deletion-source-service-ID to delete the node information on node-deletion-target-service-ID failed.

(S)

Continues processing.

(O)

If node-deletion-target-service-ID is the View Server service:

Execute the jpctool service sync command to synchronize service information.

If node-deletion-target-service-ID is other than the View Server service:

Restart the service indicated by node-deletion-source-service-ID or node-deletion-target-service-ID.

KAVE00453-W

An attempt to acquire agent information failed. (service=service-ID)

An attempt to acquire agent information from the service indicated by service-ID failed.

(S)

Continues processing.

(O)

Make sure that the service indicated by service-ID is running, and then execute the jpctool service sync command.

KAVE00454-E

The communication connection to another service failed. (service=service-ID)

A communication connection to the service indicated by service-ID failed.

(S)

Suspends processing.

(O)

Check the following for the service indicated by service-ID:

Is the service running?

Can a communication connection be established?

Is the correct PFM - Manager set for the connection destination?

KAVE00455-E

An attempt to read the configuration file failed. (file=file)

An attempt to read the configuration information file failed.

(S)

Suspends processing.

(O)

Check the status of the configuration information file and restart processing.

KAVE00456-W

An attempt to read the configuration file failed. (file=file)

An attempt to read the configuration information file failed.

(S)

Skips reading of the configuration information file.

(O)

Check the status of the configuration information file and restart processing.

KAVE00457-E

The format of a line in the configuration file is invalid. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00458-W

The format of a line in the configuration file is invalid. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Skips reading of the configuration information file.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00459-E

The tree structure for a section in the configuration file is invalid. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00460-W

The tree structure for a section in the configuration file is invalid. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Skips reading of the configuration information file.

(O)

Check and correct the settings in the configuration information file and restart processing.

KAVE00461-E

An invalid section was specified in the configuration file. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00462-W

An invalid section was specified in the configuration file. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Skips applying the corresponding section.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00463-E

An invalid property was specified in the configuration file. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00464-W

An invalid property was specified in the configuration file. (file=file, line=line-number)

An attempt to parse the configuration information file failed.

(S)

Skips applying the section where the corresponding property exists.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00465-E

A required section was not specified in the configuration file. (file=file, line=line-number, section=section-name)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00466-W

A required section was not specified in the configuration file. (file=file, line=line-number, section=section-name)

An attempt to parse the configuration information file failed.

(S)

Skips applying the parent section of the corresponding section.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00467-E

A required property was not specified in the configuration file. (file=file, line=line-number, property=property-name)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00468-W

A required property was not specified in the configuration file. (file=file, line=line-number, property=property-name)

An attempt to parse the configuration information file failed.

(S)

Skips applying the parent section where the corresponding property must exist.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00469-E

The same property is specified multiple times in one section in the configuration file. (file=file, line=line-number, property=property-name)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00470-W

The same property is specified multiple times in one section in the configuration file. (file=file, line=line-number, property=property-name)

An attempt to parse the configuration information file failed.

(S)

Skips applying the section where the corresponding property exists.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00471-E

An invalid value was specified in a property of the configuration file. (file=file, line=line-number, property=property-name)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00472-W

An invalid value was specified in a property of the configuration file. (file=file, line=line-number, property=property-name)

An attempt to parse the configuration information file failed.

(S)

Skips applying the section where the corresponding property exists.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00473-E

The maximum number of sections that can be set in the configuration file has been exceeded. (file=file, line=line-number, section=section-name)

An attempt to parse the configuration information file failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00474-W

The maximum number of sections that can be set in the configuration file has been exceeded. (file=file, line=line-number, section=section-name)

An attempt to parse the configuration information file failed.

(S)

Skips applying the corresponding section.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00475-E

The maximum number of sections that can be set in the merged configuration data has been exceeded. (section=section-name)

An attempt to merge configuration data failed.

(S)

Suspends processing.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00476-W

The maximum number of sections that can be set in the merged configuration data has been exceeded. (section=section-name)

An attempt to merge configuration data failed.

(S)

Skips applying the corresponding section.

(O)

Check the settings in the configuration information file and restart processing.

KAVE00477-I

The service will start with compatible mode. (host=%1, service=%2)

The Trap Generator service will start in compatible mode.

(S)

Starts the Trap Generator service in compatible mode.

KAVE00479-I

The service will start with the multiple monitoring function enabled.

The service is started with the multiple monitoring function enabled.

(S)

Starts the service with the multiple monitoring function enabled.

KAVE00480-W

The remote action control function will start in all-execution mode because an invalid value is specified. (label=label-name, specified value=specified-value)

The remote action control function is started in all-execution mode because an invalid value has been specified.

label-name indicates the name of the label that contains the invalid value, and specified-value indicates the invalid value that has been specified.

(S)

Continues processing by disabling the remote action control function.

(O)

Check the value specified in the label indicated by label-name in the jpccomm.ini file.

KAVE00481-I

The service will start with the remote action control function enabled. (label=label-name, specified value=specified-value)

The service is started with the remote action control function enabled.

(S)

Starts the service with the remote action control function enabled.

KAVE00483-E

The status management function must be enabled because the multiple monitoring function is enabled.

The status management function must be enabled to enable the multiple monitoring function.

(S)

Suspends the service startup processing.

(O)

If you want to start a service with the multiple monitoring function enabled, enable the status management function before starting the service.

KAVE00485-W

The service will start with the multiple monitoring function disabled because the multiple monitoring settings are invalid. (host=host-name, service=service-ID)

Because the multiple monitoring settings are invalid, the service indicated by host-name and service-ID is started with the multiple monitoring function disabled.

(S)

Starts the service.

(O)

If you want to run the service with the multiple monitoring function enabled, stop the service once, execute the jpcconf mgrhost define command to set two connection-target Manager hosts, and then start the service again.

If you want to run the service with the multiple monitoring function disabled, wait until the service stops next time, execute the jpcconf mgrhost define command to set one connection-target Manager host, and then start the service again.

KAVE00487-I

The service will start with the dispersion of the reconnection enabled. (host = host-name, service = service-ID, mode = Random-Retry-Mode-value)

The service will start with the dispersion of the reconnection enabled.

(S)

Starts the service with the dispersion of the reconnection enabled.

KAVE00493-E

A service could not start because the current physical host name of the server at startup is different from the physical host name at the last startup. (last host = previous-host-name, current host = current-host-name, mode = mode, service = service-ID)

A service could not start because the physical host name of the server at the current startup is different from the physical host name at the previous startup.

(S)

Suspends the service startup processing.

(O)

For details about the restoration procedure, see the chapter that describes the action to be taken for troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE00500-W

The real-time report is not displayed because the re-schedule mode for records that take more than 10 seconds to collect is applied. (service = service-ID, record = record-name)

The real-time report cannot be displayed because the re-schedule mode for records that take more than 10 seconds to collect is applied.

(S)

Terminates the processing for displaying a real-time report.

(O)

In the Service Properties window, change the setting Realtime Report Data Collection mode for the records for which the re-schedule mode is applied, to temporary log mode.

Alternatively, consider using a historical report.

KAVE00501-W

The display processing for a real-time report was skipped because the collection of the performance data was skipped. (service = service-ID, record = record-name, wait time = wait-time)

The display processing for a real-time report was skipped because the processing for collecting history records and the processing for displaying a real-time report overlapped.

(S)

Skips collection of real-time reports. The performance data for the skipped time is not displayed in the real-time report.

(O)

Wait a while, and then display the real-time report again. If the problem persists, in the Service Properties window, change the setting Realtime Report Data Collection mode to temporary log mode.

Alternatively, consider using a historical report.

KAVE00502-W

The real-time report cannot be displayed because the temporary data of the specified record does not exist. (service = service-ID, record = record-name)

The real-time report cannot be displayed because temporary data for the specified record does not exist.

(S)

Continues processing as if there is no data to display.

(O)

Wait for the duration of the sum of the values of Collection Interval and Collection Offset that are specified for the target record in the Service Properties window, and then display the real-time report again.

Alternatively, consider using a historical report. Note that, if 0 is specified for Collection Interval, you can display neither a real-time report nor a historical report in temporary log mode. Consider specifying the default value or a larger value.

KAVE00503-W

The service will start with the history collection priority function disabled because an invalid value was specified. (service = service-ID, section = section-name, label = label-name, specified value = specified-value)

The service will start with the history collection priority function disabled because an invalid value was specified. If a remote monitor is starting with the function disabled, the function is also disabled for the remote agent and group agent that operate under the remote monitor.

(S)

Disables the history collection priority function and then continues processing.

(O)

In the jpccomm.ini file, make sure the relevant label exists in the displayed section and check the value specified for the label. If the label does not exist, add it, and then set a value.

KAVE00504-E

The service will start with the history collection priority function disabled because the function environment is invalid. (service = service-ID)

The service will start with the history collection priority function disabled because the function environment is invalid. If a remote monitor is starting with the function disabled, the function is also disabled for the remote agent and group agent that operate under the remote monitor.

(S)

Disables the history collection priority function and then continues processing.

(O)

Restart the service. If the problem persists, collect maintenance information and then contact the system administrator.

KAVE00505-W

The record data cannot be displayed because the operation mode was changed from temporary log mode to re-schedule mode while the real-time report was being displayed. (service = service-ID, record = record-name)

The record data cannot be displayed because the operation mode was changed from temporary log mode to the re-schedule mode while the real-time report was displayed.

(S)

Terminates the processing for displaying a real-time report.

(O)

Display the real-time report again.

KAVE00506-W

The service will start with the host's preset value because an invalid value was specified. (service = service-ID, section = section-name, label = label-name, specified value = specified-value)

The service will start with the host's preset value because an invalid value was specified.

(S)

Disables the history collection priority function for each agent and then continues processing.

(O)

In the jpccomm.ini file, make sure the relevant label exists in the displayed section and check the value specified for the label. If the label does not exist, add it, and then set a value.

KAVE00507-I

The host will start with the monitoring suspension function enabled. (host = host-name)

The host will start with the monitoring suspension function enabled.

(S)

Starts with the monitoring suspension function enabled.

KAVE00508-W

The host will start with the monitoring suspension function disabled because the settings could not be acquired. (host = host-name)

The host will start with the monitoring suspension function disabled because the settings could not be acquired.

(S)

Starts with the monitoring suspension function disabled.

(O)

Check and, if necessary, revise the section name, label name, and setting values in the jpccomm.ini file.

KAVE00509-I

Monitoring will be suspended on the host. (host = host-name)

(S)

Suspends monitoring on the host.

KAVE00510-I

Monitoring by the agent will be suspended. (host = host-name, service = service-ID)

Monitoring by the agent will be suspended.

(S)

Suspends monitoring by the agent.

KAVE00511-I

Monitoring that was suspended on the host will resume. (host = host-name)

Monitoring on the host will resume.

(S)

Resumes monitoring on the host.

KAVE00512-I

Monitoring by the agent will be resumed (host = host-name, service = service-ID)

Monitoring by the agent will resume.

(S)

Resumes monitoring by the agent.

KAVE00515-W

Synchronization to the secondary server will not be executed because an attempt to load the automatic synchronization options of the settings information for the monitoring suspension function failed.

The settings information for the monitoring suspension function is not automatically synchronized to the secondary server.

(S)

Does not automatically synchronize the settings information for the monitoring suspension function to the secondary server.

(O)

Perform either of the following actions, and then re-execute the processing for suspending or resuming monitoring:

- Migrate the definition information to the secondary server by using the jpctool config mgrexport or jpctool config mgrimport command.

- Check and, if necessary, revise the section name, label name, and setting values in the jpccomm.ini file.

KAVE00516-I

Synchronization of the settings information for the monitoring suspension function to the secondary server was successful.

Synchronization of the settings information for the monitoring suspension function was successful.

(S)

Successfully synchronized the settings information for the monitoring suspension function.

KAVE00517-W

Failed to synchronize the settings information for the monitoring suspension function to the secondary server.

Synchronization of the settings information for the monitoring suspension function failed.

(S)

Failed to synchronize the settings information for the monitoring suspension.

(O)

Migrate the definition information to the secondary server by using the jpctool config mgrexport or jpctool config mgrimport command, or check the items below, and then re-execute the processing for suspending or resuming monitoring.

Make sure the PFM-Manager service for the secondary server is running.

Make sure the ports for the Master Manager service of the primary and secondary servers are fixed.

Make sure the port numbers for the Master Manager service of the primary and secondary servers are the same.

KAVE00518-E

Failed to send a JP1 event.

An attempt to send a JP1 event failed.

(S)

Suspends the processing for sending a JP1 event.

(O)

Check the JP1/Base log.

KAVE00519-E

Failed to communicate with Master Manager.

An attempt to communicate with Master Manager failed.

(S)

Suspends processing.

(O)

Make sure Master Manager is running and connected, and then re-execute the processing for suspending or resuming monitoring.

KAVE00520-E

An error occurred while the settings information for the monitoring suspension function was being updated on Master Manager.

An error occurred while the settings information for the monitoring suspension function was being updated on Master Manager.

(S)

Suspends processing.

(O)

Check the Master Manager log, take the appropriate action, and then re-execute the processing for suspending or resuming monitoring.

KAVE00521-W

A service failed to communicate with Agent Collector. (service = service-ID)

An attempt to apply the monitoring status to Agent Collector failed.

(S)

Skips application of the monitoring status to the target Agent Collector.

(O)

Check the start information and version of Agent Collector, and then restart the target agent.

KAVE00522-W

An error occurred while the settings information for the monitoring suspension function was being updated on Agent Collector. (service = service-ID)

An error occurred while the monitoring status was being applied to Agent Collector indicated by service ID.

(S)

Skips application of the monitoring status to the target Agent Collector.

(O)

Check the Agent Collector log, take the appropriate action, and then restart the target agent.

KAVE00523-E

An error occurred while the settings information for the monitoring suspension function was being acquired on Master Manager.

An error occurred while the monitoring status was being acquired on Master Manager.

(S)

Suspends processing.

(O)

Check the Master Manager log, take the appropriate action, and then re-execute the processing for suspending or resuming monitoring.

KAVE00525-W

Monitoring will operate with the Active status because an attempt to set the monitoring suspension function failed.

The target hosts or agents will operate with the Active monitoring status because an attempt to set the monitoring suspension function failed.

(S)

Continues processing.

(O)

Re-execute the processing to suspend or resume monitoring.

KAVE00526-W

Failed to update the settings information file for the monitoring suspension function.

Update of the settings information file for the monitoring suspension function failed. The services in the process of starting up will start normally.

(S)

Continues the startup processing.

(O)

Re-execute the processing for suspending or resuming monitoring.

KAVE00527-W

Monitoring will operate in stand-alone mode because an attempt to acquire the settings information for the monitoring suspension function failed.

Hosts or agents in the process of starting up will operate in stand-alone mode because the acquisition of the settings information for the monitoring suspension function from Master Manager failed.

(S)

Continues the startup processing.

KAVE00528-E

Sending of an agent event was interrupted.

The PFM - Manager service will stop without sending an agent event to Correlator.

(S)

Suspends the processing for sending an event.

(O)

Restart the PFM - Manager, and then re-execute the processing for suspending or resuming monitoring.

KAVE00529-E

Sending of a JP1 event was interrupted.

The PFM - Manager service will stop without sending an agent event to JP1/Base.

(S)

Suspends the processing for sending an event.

(O)

Restart the PFM - Manager, and then re-execute the processing for suspending or resuming monitoring.

KAVE00531-E

A service failed to load a database. (service = service-ID, DB = database)

A service failed to load a database.

(S)

Suspends processing.

(O)

Collect maintenance information, and then contact the system administrator.

KAVE00532-W

Unnecessary service information might remain in the settings information for the monitoring suspension function.

Unnecessary service information might remain in the settings information for the monitoring suspension function. If the operation continues, an unexpected amount of memory might be used and the PFM service process might stop.

(S)

Continues processing.

(O)

If the monitoring host name has been changed, the old service information with the previous host name might remain in the system. Delete the remaining old service information. For details about how to check and delete service information, see the section that describes how to change monitoring host names in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

KAVE00999-E

Assertion failed. (ex=(condition-expression), file=file-name, line=line-number)

The service was stopped due to a fatal error.

(S)

Stops the service.

(O)

Probable causes include a logic conflict, an unexpected system call error, or insufficient memory. Collect maintenance information and contact the system administrator.

KAVE04902-E

Cannot continue process due to an error caused by the system environment , such as memory shortage.

Processing cannot continue due to an error (such as memory shortage) caused by the system environment.

(S)

Stops processing.

(O)

Check whether there is a memory shortage.

If this message appears even after you re-execute the command, collect maintenance information, and then contact the system administrator.

KAVE05000-E

The specified service is not running.

The service corresponding to the specified service ID and host name is not running.

(S)

If the command is being executed, cancels the command execution.

If the installation is being performed, continues processing.

(O)

If this message was output while the command was being executed, re-execute the command by specifying the correct service ID and host name. Use the jpctool service list command to check the service ID and host name.

If this message was output during the installation, this message has no effect.

KAVE05001-E

The specified service is running.

The specified service is already running.

(S)

Halts command execution.

(O)

Specify the correct service ID and host name, and then re-execute the command. To check the service ID and host name, execute the jpctool service list command.

KAVE05002-E

A sub-command name is invalid.

The specified sub-command name is invalid.

(S)

Halts command execution.

(O)

Specify the correct sub-command, and then re-execute the command.

KAVE05003-E

The specified database ID is invalid.

The specified database ID is invalid.

(S)

Halts command execution.

(O)

Specify the correct database ID, and then re-execute the command.

KAVE05004-E

The start time is invalid.

The specified data start time exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the correct data start time, and then re-execute the command.

KAVE05005-E

The end time is invalid.

The specified data end time exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the correct data end time, and then re-execute the command.

KAVE05006-E

The end time must not be before the start time.

The specified data end time is before the data start time.

(S)

Halts command execution.

(O)

Specify a data end time that is after the data start time. Specify the correct data end time and data start time, and then re-execute the command.

KAVE05007-E

No record corresponds to the specified record type.

No record corresponds to the specified record type.

(S)

Halts command execution.

(O)

Specify the correct record type, and then re-execute the command. For the record types, see the chapter that explains performance data collection and management in the applicable PFM - Agent manual.

KAVE05008-E

The service ID is not specified.

The service ID is not specified.

(S)

Halts command execution.

(O)

Specify the correct service ID, and then re-execute the command.

KAVE05009-E

The start time is not specified.

No data start time is specified.

(S)

Halts command execution.

(O)

Specify the correct data start time, and then re-execute the command.

KAVE05010-E

The end time is not specified.

No data end time is specified.

(S)

Halts command execution.

(O)

Specify the correct data end time, and then re-execute the command.

KAVE05011-E

The export file name is not specified.

No export file name is specified.

(S)

Halts command execution.

(O)

Specify the correct export file name, and then re-execute the command.

KAVE05012-E

The specified export file name is invalid.

The specified export file name exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the correct export file name, and then re-execute the command.

KAVE05013-E

The database ID is not specified.

No database ID is specified.

(S)

Halts command execution.

(O)

Specify the correct database ID, and then re-execute the command.

KAVE05014-E

The record type is not specified.

No record type is specified.

(S)

Halts command execution.

(O)

Specify the correct record type, and then re-execute the command.

KAVE05015-E

It was not possible to communicate with the service necessary for this operation.

A service necessary for this operation is not running, or an error occurred in the communication with the required service.

(S)

Halts command execution.

(O)

If the required service is not running, start it and then re-execute the command. If the required service is running, the jpctool db backup or jpctool db dump command may be executing. After the jpctool db backup or jpctool db dump command terminates, re-execute the command.

KAVE05016-E

A backup file or directory is inaccessible.

A backup file or directory is inaccessible. The file permission to the backup file or directory has been illegally altered or deleted.

(S)

Halts command execution.

(O)

If the file permission for the backup file or directory has been altered, restore it and then re-execute the command. If re-executing the command after changing the access permission results in the same error, the backup file or directory may have been deleted. In such a case, restart the Master Store or Agent Store service and then re-execute the command.

KAVE05017-E

An export file or directory is inaccessible.

An export file or directory is inaccessible. The file permission for the export file or directory has been illegally altered or deleted.

(S)

Halts command execution.

(O)

If the file permission for the export file or directory has been altered, restore it and then re-execute the command. If re-executing the command after changing the access permission results in the same error, the export file or directory may have been deleted. In such a case, restart the Master Store or Agent Store service and then re-execute the command.

KAVE05018-E

A backup file or directory was not found.

A backup file or folder was not found.

(S)

Halts command execution.

(O)

Check the backup file or folder. In addition, make sure that the specified backup directory contains the backup data of the currently used Store version.

KAVE05019-E

The specified sub-command is valid for the Store services only.

The specified sub-command can be issued only for the Store services.

The specified sub-command can be issued only for the Store services.

(S)

Halts command execution.

(O)

Specify the correct service ID and host name, and then re-execute the command. Execute the jpctool service list command to check the service ID and host name.

KAVE05020-E

The specified service ID is invalid.

The specified service ID exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the correct service ID, and then re-execute the command. Execute the jpctool service list command to check the service ID.

KAVE05021-E

The specified host name is invalid.

The specified host name exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the correct host name, and then re-execute the command. Execute the jpctool service list command to check the host name.

KAVE05022-E

For the export file name, specify a file name that does not include a directory name.

For the export file name, specify a file name that does not include a folder name.

(S)

Halts command execution.

(O)

Specify the correct export file name, and then re-execute the command.

KAVE05023-E

The specified backup directory name is invalid.

The specified backup directory name exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Check the backup directory name.

KAVE05024-E

The specified service is not registered.

The specified service information has already been deleted, or the specified service ID or host name is invalid.

(S)

Halts command execution.

(O)

Specify the correct service ID and host name, and then re-execute the command. Execute the jpctool service list command to check the service ID and host name.

KAVE05026-E

Backup processing of the Store database terminated abnormally. (service=service-id)

Backup processing of the Store database terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05027-E

Clear processing of the Store database terminated abnormally. (service=service-ID, dbid=database-ID)

Clear processing of the Store database terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message

KAVE05028-E

Dump processing of the Store database terminated abnormally. (service=service-ID, dbid=database-ID)

Export processing of the Store database terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05029-E

List processing of the service information terminated abnormally.

List processing of the service information terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05030-E

Delete processing of the service information terminated abnormally. (service=service-id)

Delete processing of the service information terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05031-E

Register processing of the service information terminated abnormally. (service=service-id)

Re-registration processing of the service information terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05032-E

Restore processing of the Store database terminated abnormally.

Restore processing of the Store database terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05033-E

A service could not start. (service=service-name, lhost=logical-host-name, inst=instance-name, rc=maintenance-code)

The indicated service could not be started.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that has been output in the common message log.

KAVE05034-E

A service could not stop. (service=service-id, inst=instance-name, rc=maintenance-code)

The indicated service could not be stopped.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that has been output in the common message log.

KAVE05035-E

The collection of maintenance information ended abnormally.

Collection of the maintenance information terminated abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05036-E

The sub-command is not specified.

The specified command name is invalid.

(S)

Halts command execution.

(O)

Specify the correct command name, then re-execute the command.

KAVE05037-E

Shutdown processing of the service terminated abnormally. (service=service-ID)

An attempt to terminate the service has failed because the service is not responding.

(S)

If the scheduled restart functionality is enabled, forcefully stops the service.

If the scheduled restart functionality is disabled, cancels shutdown processing for the service.

(O)

Check the message that was output to the system log or common message log prior to this message, and follow the instructions given in the message.

If the scheduled restart functionality is enabled, check the common message log to confirm that the service indicated by service-ID is running after this message was output. If the service is running, no action is required.

KAVE05038-E

The specified record type is invalid.

The specified record type exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify a valid record type, and then re-execute the command.

KAVE05039-E

An error occurred in the sending of an event.

An error occurred while a JP1 event was being sent.

(S)

Suspends the process for sending the JP1 event.

(O)

Check the JP1/Base log.

KAVE05040-E

The specified event server name is too long.

The event server name exceeds the maximum length.

(S)

Suspends processing.

(O)

Specify the correct event server name.

KAVE05041-E

The specified instance name is invalid.

The specified instance name exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the correct instance name, and then re-execute the command.

KAVE05042-E

An incorrect argument is specified.

An argument that is specified is not correct.

(S)

Halts command execution.

(O)

Specify the correct argument, and then re-execute the command.

KAVE05043-E

The specified service needs the instance startup environment. (service=service-name)

The specified service requires an instance startup environment.

(S)

Halts command execution.

(O)

When this message is output for the jpcspm start command

Set up the instance startup environment, and then re-execute the command.

When this message is output for the jpcspm stop command

Set up the instance startup environment.

When this message is output for the jpcconf port command

Set up the instance startup environment, and then re-execute the command.

KAVE05044-E

A service could not start because a communication connection with a Manager component could not be established.

The Agent Collector, Agent Store, or Action Handler service could not be started because a communication connection with PFM - Manager could not be established.

(S)

Halts command execution.

(O)

Make sure that the host name of PFM - Manager for the connection destination is correct. If it is correct, check the following:

Is the PFM - Manager service running?

Can a communication connection be established?

KAVE05045-E

The current directory is not correct.

The current folder is not correct.

(S)

Halts command execution.

(O)

Move the current folder to the correct location, and then re-execute the command.

KAVE05046-E

The specified sub-command cannot be used on an Agent host.

The specified sub-command cannot be used on a PFM - Agent host.

(S)

Halts command execution.

(O)

Specify the correct sub-command, and then re-execute the command.

KAVE05047-E

The specified service needs the instance name.

The specified service needs an instance name.

(S)

Halts command execution.

(O)

Specify an instance name, and then re-execute the command.

KAVE05048-E

The error occurred in the update processing of the system file.

Updating of the system file failed.

(S)

Halts command execution.

(O)

The system file may be corrupted. Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05049-E

There is no executable service corresponding to specified subcommand and service ID.

There is no executable service corresponding to the specified command.

(S)

Halts command execution.

(O)

Check the service startup status by executing the jpctool service list command.

KAVE05051-E

The file does not exist. (path)

The file specified for loading or writing does not exist. One of the following is the possible cause of this error:

An incorrect file name was specified.

The file system has been unmounted.

(S)

Stops the requested process.

(O)

Check the file or folder indicated by path, correct the cause of the error, and then re-execute the command.

KAVE05052-E

An attempt to access a file or directory (path) failed.

An error other than a disk capacity shortage occurred during a normal access, such as for file creation, deletion, loading, or writing. One of the following is the possible cause of this error:

No access permission.

The file system has been unmounted.

A directory path is used for a file path.

(S)

Stops the requested processing.

(O)

When this message is displayed during command execution

Check the status of the file indicated by path, eliminate the cause of the access error, and then re-execute the command.

When this message is displayed during upgrading of the PFM - Agent version

Check the status of the file indicated by path, eliminate the cause of the access error, and then re-install PFM - Agent.

When path indicates a directory, files whose names begin with PFM might remain after the error. Change the access permission and delete the files whose names begin with PFM.

KAVE05053-E

No empty area is available for file or directory creation. (path)

Disk capacity shortage occurred during creation or expansion of a file or folder.

(S)

Stops the requested processing.

(O)

Increase the available space in the file system indicated by path or change the configuration destination for the file, and then re-execute the command.

KAVE05054-E

An attempt to register a Windows service failed. (service-name)

This message is output when an unexpected error occurs during registration of a Windows service. A Windows service status incompatibility or resource shortage may cause this error.

(S)

Stops the requested processing.

(O)

Restart the system, and then re-execute the command. If the error persists, the system may be corrupted. Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05055-E

An attempt to delete a Windows service failed. (service-name)

This message is output when an unexpected error occurs during deletion of a Windows service. A Windows service status incompatibility or resource shortage may cause this error.

(S)

Stops the requested processing.

(O)

Restart the system, and then re-execute the command. If the error persists, the system may be corrupted. Collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05057-E

The setup command is executing in another session.

Multiple setup commands cannot be executed concurrently.

(S)

Stops the requested processing.

(O)

Wait for a short while, and then execute the command. If a setup command in another session is stuck in execution status because the command is waiting for a response, terminate it.

KAVE05058-E

The specification of the service key is incorrect.

An invalid value is specified for the service key. This error also occurs when a service key that cannot be processed by the command is specified. For example, if mgr is specified for the jpcconf inst setup command, which creates an instance environment, this specification is not recognized. Also, the PFM - Agent with the specified service key may not have been set up correctly.

(S)

Stops the requested processing.

(O)

Check and, if necessary, revise the command syntax, and then re-execute the command.

KAVE05059-E

The specification of the logical host name is incorrect.

Either the length of the specified host name (logical host name) exceeds the maximum value, or an invalid value was specified.

(S)

Stops the requested processing.

(O)

Check for the following in the argument specified for the -lhost option, and then re-execute the command:

Is a character string specified that is longer than 32 characters (units: bytes)?

Does the character string include a space?

Is localhost specified in the -lhost option of the jpcconf ha setup command?

If the JPC_HOSTNAME environment variable has been set, release the setting, and then re-execute the command with the -lhost option specified.

KAVE05060-E

The specification of the instance name is incorrect.

The specified instance name exceeds the maximum length or an invalid value was specified.

(S)

Stops the requested processing.

(O)

Check for the following in the argument specified for the -inst option, and then re-execute the command.

Is a character string specified that is longer than 32 characters (units: bytes)?

Does the character string include a space?

KAVE05061-E

The specification of the environment directory is incorrect.

The specified environment directory name exceeds the maximum length or an invalid value was specified.

(S)

Stops the requested processing.

(O)

Make sure that a character string specified in the argument for the -d option is no longer than 80 characters (units: bytes), and then re-execute the command.

KAVE05062-E

The specified service is not installed or is not set up. (servicekey=service-key)

Product information could not be acquired from the specified service key. The following are likely causes of this error for the product associated with the specified service key:

The product has not been installed in the system.

Product setup is not completed.

(S)

Stops the requested processing.

(O)

Check the service key specification, and then re-execute the command. Install the product if it has not been installed.

KAVE05063-E

The specified service is not supported for logical host startup. (servicekey=service-key)

Startup on a logical host is not supported for the product indicated by the service key specified in the jpcconf ha command.

(S)

Stops the requested processing.

(O)

Check and, if necessary, revise the service key specification, and then re-execute the command.

KAVE05064-E

The specified service is not supported for multi-instance startup. (servicekey=service-key)

Startup of an instance is not supported for the program indicated by the specified service key.

(S)

Stops the requested processing.

(O)

Check and, if necessary, revise the service key specification, and then re-execute the command.

KAVE05068-E

The logical host environment has already been created. (servicekey=service-key, lhost=logical-host-name)

An attempt was made to create a logical host environment that has already been registered with the jpcconf ha command.

(S)

Stops the requested service.

(O)

Use the jpcconf ha list command to check the logical host environments that have been set up.

KAVE05069-I

Creating the logical host environment. (servicekey=service-key, lhost=logical-host-name, dir=environment-directory-name)

The logical host environment is being created.

(S)

Continues the requested processing.

KAVE05070-I

The logical host environment was created. (servicekey=service-key, lhost=logical-host-name, dir=environment-directory-name)

The logical host environment was created.

(S)

Terminates command execution.

KAVE05071-E

An attempt to create the logical host environment failed. (servicekey=service-key, lhost=logical-host-name, dir=environment-directory-name)

A message indicating the cause was output before this message.

(S)

Stops the requested service.

(O)

Check the error in the message output prior to this message, eliminate the problem, and then re-execute the command.

KAVE05078-E

The instance environment does not exist. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

An attempt was made to reference, update, or delete the settings of a non-existent instance environment.

(S)

Stops the requested processing.

(O)

Use the jpcconf inst list command to check the created instances.

KAVE05079-E

The instance environment has already been created. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

An attempt was made to add an instance environment that has already been created.

(S)

Stops the requested processing.

(O)

Use the jpcconf inst list command to check the created instances.

KAVE05080-I

The instance environment is now being created. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

The instance environment is being created.

(S)

Continues the requested processing.

KAVE05081-I

The instance environment has been created. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

The instance environment has been created.

(S)

Terminates command execution.

KAVE05082-E

The instance environment could not be created. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

A message indicating the cause was output before this message.

(S)

Stops the requested processing.

(O)

Check the error in the message displayed before this message, eliminate the cause of the error, and then re-execute the command.

KAVE05083-I

The instance environment is being deleted. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

The instance environment is being deleted.

(S)

Continues the requested processing.

KAVE05084-I

The instance environment was deleted. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

The instance environment has been deleted.

(S)

Terminates command execution.

KAVE05085-E

The instance environment could not be deleted. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

A message indicating the cause was output before this message.

(S)

Stops the requested processing.

(O)

Check the error in the message displayed before this message, eliminate the cause of the error, and then re-execute the command.

KAVE05086-E

The specification of the host name is incorrect.

The specified host name exceeds the maximum length or an invalid value was specified.

(S)

Stops the requested processing.

(O)

Check the following, and then re-execute the command:

Is a character string that was specified longer than 32 characters (units: bytes)?

Is the IP address specified directly?

Does the character string include a space?

Does the character string include a period?

KAVE05087-I

The connecting host has changed. (host-name-before-change -> host-name-after-change)

The connecting host has changed.

(S)

Terminates command execution.

KAVE05088-E

The connection host cannot be changed in this environment.

One of the following is the possible cause of this error:

An attempt was made from the host on which PFM - Manager is installed to set another host as the connection destination.

An attempt was made to change the connection destination of the physical host from a host on which the service running on the physical host is not installed.

(S)

Stops the requested processing.

(O)

Check the execution environment of the command.

KAVE05089-Q

Running services will be forcedly terminated. Do you want to continue? (Y/N)

This confirmation message explains that the services of the Performance Management programs must be stopped before you use a setup command to change the environment.

When the jpcconf inst setup command is being executed:

The system stops the service of only the applicable PFM - Agent service and then continues the requested processing.

When the jpcconf inst unsetup command is being executed:

The system stops the service of only the applicable PFM - Agent service.

When the jpcconf port define command is being executed:

The system stops the services of all Performance Management programs.

When the jpcconf mgrhost define command is being executed:

The system stops the services of all Performance Management programs.

(S)

Continues processing only if Y or y is entered. The system stops processing if any other character (including a blank or a character string) is entered.

(O)

Enter a response.

KAVE05090-I

Service is stopped.

This message is displayed while the service is stopped (while a command is being called internally). The result of an internal command is not displayed on the terminal because it is directed elsewhere.

(S)

Continues the requested processing.

KAVE05091-E

An internal command cannot be executed. (command-line)

An internal command called by the setup command could not be executed. The system environment may not be correct.

(S)

Stops the requested processing. If you are using the linkage function with PFM - Web Console to manage starting, stopping, or displaying the PFM - Web Console service, stops processing of PFM - Web Console only.

(O)

Make sure that a file exists in the location indicated by command-line, or you have permission to execute the command. Forward the location to the system administrator or support service. If the KAVE05092-E message appears subsequently, forward the reason code in the message to the system administrator or support service.

KAVE05092-E

An error occurred so command execution was terminated. (rc=reason-code)

Command execution was terminated because an error occurred. One of the following reason codes is displayed, depending on the situation:

When this message is displayed following KAVE05091-E:

1 is displayed as the reason code.

When this message is displayed following KAVE05099-E:

The termination code of an internal command is displayed as the reason code.

All other cases:

The detail code of the preceding error message is displayed.

(S)

Stops the requested processing.

(O)

Check the error message displayed before this message, correct the cause of the error, and then re-execute the command.

KAVE05093-E

Mutually-exclusive options are specified.

Mutually-exclusive options were specified.

(S)

Stops the requested processing.

(O)

Specify the options correctly, and then re-execute the command.

KAVE05094-E

An option is duplicated. (option)

An option was duplicated.

(S)

Stops the requested processing.

(O)

Specify the options correctly, and then re-execute the command.

KAVE05095-E

A required argument for this option is not specified. (option)

No argument is specified for the option.

(S)

Stops the requested processing.

(O)

Specify the option correctly, and then re-execute the command.

KAVE05096-E

The connecting host has not been set yet.

A service configuration information file cannot be found, or no host entry has been set up at the connection destination.

(S)

Stops the requested processing.

(O)

Specify a host name in the -host or -localhost option of the jpcconf mgrhost define command.

KAVE05097-E

An option is invalid. (option)

The indicated specified option is invalid.

(S)

Stops the requested processing.

(O)

Specify the correct option, and then re-execute the command.

KAVE05098-E

The instance name is not specified.

No instance name is specified.

(S)

Stops the requested processing.

(O)

Specify the correct instance name, and then re-execute the command.

KAVE05099-E

An internal command terminated abnormally. (command-line)

An internal command called by the setup command returned an error.

(S)

Stops the requested processing.

(O)

Check the message output to the system log or common message log. If the problem cannot be resolved, forward to the system administrator or support service the command line indicated in this message and the reason code in the KAVE05092-E message, which is output following this message.

KAVE05100-E

The specified service is not installed.

The specified service is not installed.

(S)

Halts command execution.

(O)

Specify the correct service ID and host name, and then re-execute the command. Execute the jpctool service list command to check the service ID and host name.

KAVE05101-E

The service keyname is not specified.

The service keyname is not specified.

(S)

Halts command execution.

(O)

Specify a service keyname, and then re-execute the command.

KAVE05102-E

The collection-destination directory is not specified.

The collection-destination folder is not specified.

(S)

Halts command execution.

(O)

Specify a collection-destination folder, and then re-execute the command.

KAVE05103-E

The name of the specified collection-destination directory is incorrect.

The specified collection-destination folder name exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the collection-destination folder correctly, and then re-execute the command.

KAVE05104-E

The collection-destination directory cannot be accessed.

The collection-destination directory cannot be accessed because the access permission is invalid or the disk capacity is insufficient.

(S)

Halts command execution.

(O)

Specify the folder with the correct access permission or a folder with sufficient disk capacity, and then re-execute the command.

KAVE05105-E

The collection-destination directory was not found.

The collection-destination folder was not found.

(S)

Halts command execution.

(O)

Specify the correct collection-destination folder, and then re-execute the command.

KAVE05106-E

The name of the backup-file directory is not specified.

No directory name is specified for the backup file.

(S)

Halts command execution.

(O)

Specify the name of the backup directory, and then re-execute the command.

KAVE05107-E

The name of the backup-file directory is incorrect.

The specified backup file directory name exceeds the maximum length or its format is invalid.

(S)

Halts command execution.

(O)

Specify the backup file directory correctly, and then re-execute the command.

KAVE05108-E

The start, stop, setup or alarm command is being executed.

An attempt was made to execute the command while the jpcspm start, jpcspm stop, jpcconf port, or jpctool alarm command was being executed.

(S)

Halts command execution.

(O)

Wait until the jpcspm start, jpcspm stop, jpcconf port, or jpctool alarm command is completed, and then re-execute the command.

KAVE05110-E

The host name is not specified.

The logical host name has not been specified.

(S)

Halts command execution.

(O)

Specify the logical host name, and re-execute the command.

KAVE05111-E

The environment directory is not specified.

The environment directory has not been specified.

(S)

Halts command execution.

(O)

Specify the environment directory, and re-execute the command.

KAVE05112-E

The specification of the file name is incorrect.

The file name specification is invalid.

(S)

Halts command execution.

(O)

Specify a valid file name, and then re-execute the command.

KAVE05113-E

The file name is not specified.

The file name has not been specified.

(S)

Halts command execution.

(O)

Specify the file name, and re-execute the command.

KAVE05114-E

You do not have permission to access the specified environment directory. (dir=environment-directory)

The specified environment directory cannot be accessed. One of the following is the probable cause of this error:

The directory does not exist.

You do not have access permission.

Disk capacity is insufficient.

(S)

Halts command execution.

(O)

Check the specified directory and re-execute the command.

KAVE05115-E

Multiple logical hosts cannot be set for the Manager service.

A PFM - Manager is already set up on a logical host in the Performance Management system.

(S)

Halts command execution.

(O)

Delete the unneeded logical host environment of the PFM - Manager service, and then re-execute the command.

KAVE05116-E

The environment directory was already set up for the specified logical host. (lhost=logical-host-name, dir=environment-directory)

When adding a service to an existing logical host, you must specify an environment directory that has already been set up.

(S)

Halts command execution.

(O)

Either specify an environment directory that is already being used by the logical host or do not specify an environment directory, then re-execute the command.

KAVE05117-E

Manager is set up for a logical host, so the processing of Manager for a physical host cannot be executed.

Processing cannot be performed on PFM - Manager for a physical host because PFM - Manager is set up on a logical host.

(S)

Halts command execution.

(O)

Specify the logical host option, and then re-execute the command.

KAVE05118-E

The service required for set up of a logical host does not exist.

The service required for logical host setup was not found. One of the following is the probable cause of this error:

If all is specified in the service key, there is no such PFM - Agent service that supports logical hosts.

The service has already been set up for the logical host.

(S)

Halts command execution.

(O)

Check the installed products and the specification of the logical host option.

KAVE05119-E

The specified service is not set up for a logical host.

The specified service is not set up for the logical host.

(S)

Halts command execution.

(O)

Check if the service is set up for the logical host and if the specification for the logical host option is correct.

KAVE05120-E

The specified file does not exist. (file=file-name)

The specified file does not exist.

(S)

Halts command execution.

(O)

Specify the correct file name, and then re-execute the command.

KAVE05121-E

An attempt to access the specified file failed. (file=file-name)

An attempt to access the specified file failed.

(S)

Halts command execution.

(O)

Check the access permissions to the file, and then re-execute the command.

KAVE05122-E

An attempt to open the specified file failed. (file=file-name)

An attempt to open the specified file failed.

(S)

Halts command execution.

(O)

Specify the correct file name, and re-execute the command.

KAVE05123-E

A logical host is set up, so the specified service cannot be started. (servicekey=service-key)

The specified service cannot be started because a logical host has been set up.

(S)

Halts command execution.

(O)

Specify the logical host option, and then re-execute the command.

KAVE05124-E

A set up logical host does not exist.

No logical host has been set up for services of Performance Management programs.

(S)

Halts command execution.

(O)

Specify the logical host option correctly, and then re-execute the command.

KAVE05125-I

Deleting the logical host environment. (servicekey=service-key, lhost=logical-host-name)

The logical host environment is being deleted.

(S)

Continues the requested processing.

KAVE05126-I

The logical host environment was deleted. (servicekey=service-key, lhost=logical-host-name)

The logical host environment was deleted.

(S)

Stops command execution.

KAVE05127-E

An attempt to delete the logical host environment failed. (servicekey=service-key, lhost=logical-host-name)

No logical host has been set up.

(S)

Halts command execution.

(O)

Check the cause, and then re-execute the command. For details about the cause, check the message output immediately before this message.

KAVE05128-E

An instance environment exists, so the logical host environment deletion is not possible. (servicekey=service-key)

The logical host cannot be deleted because an instance environment exists.

(S)

Halts command execution.

(O)

Delete all instances on the logical host, and then re-execute the command.

KAVE05129-E

The service required for deletion of the logical host does not exist.

The service required to delete the logical host does not exist.

(S)

Halts command execution.

(O)

Check the command arguments and the logical host environment.

KAVE05132-E

A physical host definition cannot be set because a logical host is already set up.

A physical host definition cannot be set because a logical host is set up.

(S)

Halts command execution.

(O)

Specify the logical host option, and then re-execute the command.

KAVE05133-E

A physical host definition cannot be referenced because a logical host is set up.

A physical host definition cannot be referenced because a logical host is set up.

(S)

Halts command execution.

(O)

Specify the logical host option, and then re-execute the command.

KAVE05134-E

The service key (service-key) cannot be specified.

An unavailable service key was specified.

(S)

Halts command execution.

(O)

Check if a valid service key was specified.

KAVE05135-E

A service that is not supported for the specified sub-command is specified. (subcmd=sub-command-name, service=service-key)

A service was specified that does not support the specified sub-command.

(S)

Halts command execution.

(O)

Make sure that the correct sub-command name and service key are specified.

KAVE05136-I

The logical host startup information listing ended normally.

Display of startup information for the logical host ended normally.

(S)

Terminates command execution.

KAVE05137-E

The logical host startup information listing ended abnormally.

Display of startup information for the logical host ended abnormally.

(S)

Halts command execution.

(O)

Check the cause, and then re-execute the command. For details about the cause, check the message that was output immediately before this message.

KAVE05138-E

The environment directory cannot be accessed. (dir=directory-name)

The environment directory cannot be accessed.

(S)

When a command is executed

Halts command execution.

At installation

Continues processing.

(O)

Check the following:

When a command is executed

- Make sure that the specified directory exists.

- Make sure that the command has not been executed on the standby node.

At installation

When installation is performed on the executing node, make sure that the shared disk containing the environment directory is mounted. Note that this message has no effect when installation is completed successfully on the standby node.

KAVE05139-I

The export processing of the logical host environment definition file ended normally.

Export of the environment definition file for the logical host ended normally.

(S)

Terminates command execution.

KAVE05140-I

The import processing of the logical host environment definition file ended normally.

Import of the environment definition file for the logical host ended normally.

(S)

Terminates command execution.

KAVE05141-E

The export processing of the logical host environment definition file ended abnormally.

Export of the environment definition file for the logical host ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05142-E

The import processing of the logical host environment definition file ended abnormally.

Import of the environment definition file for the logical host ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05143-E

A service is running, so the processing is not possible.

The processing cannot be performed because a service is running.

(S)

Halts command execution.

(O)

If you want to create or delete a logical host environment, check the following and then re-execute the command:

If you are creating or deleting a logical host for a PFM - Manager service, make sure that all services on the PFM - Manager host are stopped.

If you are deleting a logical host environment for a PFM - Agent service, make sure that the PFM - Agent logical host service to be deleted is stopped.

If you are deleting the last service on the specified logical host, make sure that the Agent Handler service on the logical host with the same name is stopped.

This message may also be displayed during service start or stop processing. In such a case, make sure that the service has completely stopped and then re-execute the command.

KAVE05144-E

The import file format is invalid. (file=file-name)

The format of the import file is invalid.

(S)

Halts command execution.

(O)

Specify a valid import file, and then re-execute the command.

KAVE05145-E

The logical host service is running, so the processing is not possible. (lhost=logical-host-name)

The processing cannot be performed because the logical host start service is running.

(S)

Halts command execution.

(O)

Stop the logical host start service, and then re-execute the command. This message may also be displayed when the service start or stop processing is taking a long time. In such a case, make sure that the service has completely stopped and then re-execute the command.

KAVE05146-Q

The file already exists. Do you want to update the file? (Y/N)

The specified file already exists.

(S)

If you enter Y or y, the system updates the file and continues processing. If you respond with any other character (including a space or a character string), the system halts command execution.

(O)

Make sure that it is acceptable to overwrite the existing file.

KAVE05147-E

The export processing of the logical host environment definition file was cancelled.

Export processing was stopped because a character other than Y was entered in response to the file update confirmation message.

(S)

Halts command execution.

(O)

Either back up the existing file or change the specified file name, and then re-execute the command.

KAVE05148-E

The jp1pc directory does not exist in the environment directory on the specified logical host. (lhost=logical-host-name, dir=environment-directory)

The jp1pc directory does not exist in the environment directory of the logical host that was set up.

(S)

Halts command execution.

(O)

Make sure that the jp1pc directory exists in the environment directory of the specified logical host, and then re-execute the command.

KAVE05149-E

The environment directory cannot be created because the jp1pc directory already exists in the specified directory. (dir=directory-name)

The environment directory cannot be created because the jp1pc directory already exists in the specified directory.

(S)

Halts command execution.

(O)

Specify a directory in which a jp1pc directory does not exist, and then re-execute the command.

KAVE05150-Q

A logical host environment that is not in the import file exists. Do you want to delete the logical host environment? (lhost=logical-host-name, servicekey=service-key) (Y/N) [N]:

A logical host environment that is not specified in the import file exists on the target logical host.

(S)

The system deletes the logical host environment only if you enter Y or y. If you respond with any other character (including a space or a character string), the system does not delete the logical host environment.

(O)

Make sure that deleting the specified logical host environment is acceptable.

KAVE05151-Q

Do you want to create the specified logical host environment? (lhost=logical-host-name, servicekey=service-key) (Y/N) [Y]:

The import file contains a newly added logical host environment.

(S)

If you enter N or n, the system does not create the logical host environment. If you respond with any other character (including a space or a character string), the system creates the logical host environment.

(O)

Make sure that creating the specified logical host environment is acceptable.

KAVE05152-Q

A logical host environment that is not in the import file exists. Do you want to delete the logical host environment? (lhost=logical-host-name, servicekey=service-key, inst=instance-name) (Y/N) [N]:

A logical host environment that is not specified in the import file exists on the target logical host.

(S)

If you enter Y or y, the system deletes the logical host environment. If you respond with any other character (including a space or a character string), the system does not delete the logical host environment.

(O)

Make sure that deleting the specified logical host environment is acceptable.

KAVE05153-Q

Do you want to create the specified logical host environment? (lhost=logical-host-name, servicekey=service-key, inst=instance-name) (Y/N) [Y]:

The import file contains a newly added logical host environment.

(S)

If you enter N or n, the system does not create the logical host environment. If you respond with any other character (including a space or a character string), the system creates the logical host environment.

(O)

Make sure that creating the specified logical host environment is acceptable.

KAVE05154-E

The Windows service(Windows-service-name) is marked as a target of deletion.

The Windows service has already been marked for deletion.

(S)

Halts command execution.

(O)

Restart the system to complete deletion of the service.

KAVE05155-I

The creating of the logical host environment will now be skipped. (servicekey=service-key, lhost=logical-host-name)

Creation of the logical host environment is being skipped.

(S)

Skips creation of the logical host environment.

KAVE05156-I

The deleting of the logical host environment will now be skipped. (servicekey=service-key, lhost=logical-host-name)

Deletion of the logical host environment is being skipped.

(S)

Skips deletion of the logical host environment.

KAVE05157-I

The creating of the logical host environment will now be skipped. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Creation of the logical host environment is being skipped.

(S)

Skips creation of the logical host environment.

KAVE05158-I

The deleting of the logical host environment will now be skipped. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Deletion of the logical host environment is being skipped.

(S)

Skips deletion of the logical host environment.

KAVE05159-E

The environment directory cannot be created because the specified directory does not exist. (dir=directory)

The environment directory could not be created because the specified directory does not exist.

(S)

Halts command execution.

(O)

Specify a directory that exists, and then re-execute the command.

KAVE05160-W

Processing is skipped because the service is running. (servicekey=service-key)

Processing has been skipped because the service was running.

(S)

Continues command execution.

(O)

Use the jpctool service list command to check the service's start status. This message may also be displayed when the service start or stop processing is taking a long time. In such a case, make sure that the service has stopped completely and then re-execute the command.

KAVE05161-E

The specification of the option is incorrect. (option)

The indicated option specification is invalid.

(S)

Halts command execution.

(O)

Check the command options.

KAVE05162-I

The Store service is not supported for the process of creating indexes. (version=version)

The Master Store or Agent Store service version does not support creation of a Store database index. The Store database index is created when the Master Store or Agent Store service starts. The following versions support index creation:

06-70-/F or later

07-00-/B or later

(S)

Skips index creation.

KAVE05163-E

An error occurred in the Windows service control manager. (service=service-name, lhost=logical-host-name, inst=instance-name)

During service start processing, an error occurred on Windows service control manager.

(S)

Halts command execution.

(O)

Check the following and then re-execute the jpcspm start command:

Was another Windows service started concurrently?

Are the settings correct?

Are there enough resources?

Were any messages output to the system log and common message log by the service that resulted in the error?

If re-execution results in the same message, change the retry interval and count set for the command to automatically start the service. For details on how to change the retry interval and count, see the chapter that explains the procedure in the Job Management Partner 1/Performance Management User's Guide.

KAVE05164-E

The number of open files exceeded the system limit.

A file open error occurred because the system's limit on the number of open files was exceeded.

(S)

Halts command execution.

(O)

Terminate an application that is not being used or increase the system limit value for the number of files that can be opened.

KAVE05165-E

An I/O error occurred during processing.

An I/O error occurred during processing.

(S)

Halts command execution.

(O)

Check the file system status.

KAVE05166-I

The host name will now be changed. (newhost=new-host-name)

The host name will now be changed.

(S)

Starts the command execution.

KAVE05167-I

The host name was successfully changed. (newhost=new-host-name)

The host name was successfully changed.

(S)

Ends the command execution successfully.

KAVE05168-I

The logical host name will now be changed. (oldhost=old-logical-host-name, newhost=new-logical-host-name)

The logical host name will now be changed.

(S)

Starts the command execution.

KAVE05169-I

The logical host name was successfully changed. (oldhost=old-logical-host-name, newhost=new-logical-host-name)

The logical host name was successfully changed.

(S)

Ends the command execution successfully.

KAVE05170-I

The setting used for acquiring the physical host name will now be changed. (mode=mode, Host Alias Name=alias-name)

The setting for acquiring the physical host name will now be modified.

(S)

Starts the command execution.

KAVE05171-I

The setting used for acquiring the physical host name was successfully changed. (mode=mode, Host Alias Name=alias-name)

The setting for acquiring the physical host name ended successfully.

(S)

Ends the command execution successfully.

KAVE05172-I

The host information was successfully backed up. (dir=backup-directory)

The host information was successfully backed up.

(S)

Continues processing.

KAVE05173-E

An attempt to back up host information has failed. (dir=backup-directory)

An attempt to back up host information has failed.

(S)

Cancels the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05174-I

The backup of host information was successfully deleted. (dir=backup-directory)

The backup of host information was successfully deleted.

(S)

Continues processing.

KAVE05175-W

An attempt to delete the backup of host information has failed. (dir=backup-directory)

An attempt to delete the backup of host information has failed.

(S)

Continues processing.

(O)

Check the backup directory, and then manually delete the backup.

KAVE05176-E

The specified alias name is invalid. (Host Alias Name =alias-name)

The specified alias name is invalid.

(S)

Cancels the command execution.

(O)

Check the following for the specified alias name, and then re-execute the command:

Whether the specified name does not exceed 32 characters (in bytes)

Whether the IP address is not specified directly

Whether the specified name does not include a space

Whether localhost is not specified

KAVE05177-E

The alias name is the same as the logical host name. (Host Alias Name=alias-name)

The specified alias name is the same as the logical host name on the same host.

(S)

Cancels the command execution.

(O)

Specify the alias name that is different from the logical host name on the same host, and then re-execute the command.

KAVE05178-E

The installed agent does not support the functionality for changing a physical host name.

PFM - Agent that does not support the functionality for changing a physical host name has been installed.

(S)

Cancels the command execution.

(O)

The method for acquiring the physical host names could not be changed because the version of installed PFM - Agent is earlier than 08-00. Use the real host name to perform operation.

KAVE05179-E

The specified host name is invalid. (host=host-name)

The specified host name is invalid.

(S)

Cancels the command execution.

(O)

Check the following for the specified host name, and then re-execute the command:

Whether the specified name does not exceed 255 characters (in bytes)

Whether the IP address is not specified directly

Whether the specified name does not include a space

Whether localhost is not specified

KAVE05180-W

An attempt to set a port number failed because the port number information was duplicated. (service=service-ID)

Multiple fixed port numbers were specified for the service to be updated. The fixed port number settings for the specified service have been canceled.

(S)

Cancels the fixed port number settings for the corresponding service, and then continues processing.

(O)

Re-specify the fixed port number settings for the corresponding service if necessary.

KAVE05181-E

An attempt to change the host name ended abnormally. (newhost=new-host-name)

An attempt to change the host name ended abnormally.

(S)

Cancels the command execution.

(O)

Check the message that was output prior to this message, and eliminate the cause of the error by following the instructions given in that message. Restore the backup data and definition files from the backup directory specified in the -d option, and then re-execute the jpcconf host hostname command to change the host name. For details about the restore procedure, see the chapter that describes the jpcconf host hostname command.

If you start the PFM service before the host name is successfully changed, management information about the PFM service might become invalid. Therefore, do not start the PFM service until the host name is successfully changed.

If you are unable to determine the cause of the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05182-E

An attempt to change the logical host name ended abnormally. (oldhost=old-logical-host-name, newhost=new-logical-host-name)

An attempt to change the logical host name ended abnormally.

(S)

Cancels the command execution.

(O)

Check the message that was output prior to this message, and eliminate the cause of the error by following the instructions given in that message. Restore the backup data and definition files from the backup directory specified in the -d option, and then re-execute the jpcconf host hostname command to change the logical host name. For details about the restore procedure, see the chapter that describes the jpcconf host hostname command.

If you start the PFM service before the logical host name is successfully changed, management information about the PFM service might become invalid. Therefore, do not start the PFM service until the logical host name is successfully changed.

If you are unable to determine the cause of the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05183-E

An attempt to change the setting used for acquiring the physical host name ended abnormally. (mode=mode, Host Alias Name=alias-name)

An attempt to configure the settings used for acquiring the physical host name ended abnormally.

(S)

Cancels the command execution.

(O)

Check the message that was output prior to this message, and eliminate the cause of the error by following the instructions given in that message. Restore the backup data and definition files from the backup directory specified in the -d option, and then re-execute the jpcconf host hostmode command to change the setting of the method used for acquiring the physical host name. For details about the restore procedure, see the chapter that describes the jpcconf host hostmode command.

If you start the PFM service before the setting of the method used for acquiring the physical host name is successfully changed, management information about the PFM service might become invalid. Therefore, do not start the PFM service until the setting of the method used for acquiring the physical host name is successfully changed.

If you are unable to determine the cause of the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05184-E

The new host name is not specified.

The new host name is not specified.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the new host name.

KAVE05185-E

The backup directory is not specified.

The backup directory is not specified.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the backup directory.

KAVE05186-E

The mode for acquiring the physical host name is not specified.

The method for acquiring physical host names is not specified.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the method for acquiring physical host names.

KAVE05187-E

The alias name is not specified.

The alias name is not specified.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the alias name.

KAVE05188-E

The specified logical host name is the same as the physical host name. (lhost=logical-host-name)

The specified logical host name is the same as the physical host name on the same host.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the logical host name that is different from the physical host name.

KAVE05189-E

The specified physical host name is the same as the logical host name. (lhost=logical-host-name)

The specified physical host name is the same as the logical host name on the same host.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the physical host name that is different from the logical host name.

KAVE05190-E

An attempt to update the file failed. (file=file-name)

An attempt to update the file failed.

(S)

Cancels the command execution.

(O)

Recover the file by using the backup that you specified when executing the jpcconf host command, and then re-execute the command. If the problem still occurs even after you re-execute the command, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05191-E

A specified argument cannot be specified in this environment. (argument=argument)

A specified argument cannot be specified in this environment.

(S)

Cancels the command execution.

(O)

A specified argument cannot be specified because it is invalid in this environment. For details about the arguments, see 2. Commands.

KAVE05192-E

A specified logical host name is already in use. (lhost=logical-host-name)

The specified logical host name is already in use.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying a different logical host name that is not in use.

KAVE05200-E

You do not have permission to execute the command.

You do not have permission to execute the command.

(S)

Halts command execution.

(O)

Check the command execution permission.

KAVE05202-E

An unexpected exception has occurred. (rc1=maintenance-code-1, rc2=maintenance-code-2)

An unexpected error has occurred.

(S)

Halts command execution.

(O)

Check the message output to the system log or common message log. If the problem cannot be resolved, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05203-E

Memory is insufficient.

Memory allocation failed because of insufficient memory.

(S)

Halts command execution.

(O)

Close applications that are not being used or increase the memory size.

KAVE05204-E

The disk capacity is insufficient.

File access failed because of insufficient disk capacity.

(S)

Halts command execution.

(O)

Delete unnecessary files or increase the disk capacity.

KAVE05205-E

An error occurred in the network. (rc=maintenance-code)

An error occurred during TCP/IP communication, or a communication timeout occurred.

(S)

Halts command execution.

(O)

Check the activation status of the remote server and the network status.

KAVE05206-E

The network environment is incorrect. (rc=maintenance-code)

TCP/IP initialization failed or socket generation failed.

(S)

Halts command execution.

(O)

Check the local host's network environment and the system environment.

KAVE05209-E

The specified sub-command is invalid for the Master Manager, Master Store, Name Server or Status Server service.

The specified command cannot be issued for the Master Manager, Master Store, Name Server, or Status Server service.

(S)

Halts command execution.

(O)

Specify the correct service ID and then re-execute the command.

KAVE05212-E

Specified logical hostname is not set up. (lhost=logical-host-name)

The specified logical host name has not been set up.

(S)

Halts command execution.

(O)

Check the logical host name, and then re-execute the command.

KAVE05213-E

The system environment is incorrect. (rc=maintenance-code)

The system environment is incorrect. A system file was deleted illegally or its access permission was changed.

(S)

Halts command execution.

(O)

If this message was output when executing the command, see the message that was output to the common message log prior to this message. If there is no message immediately before this message, re-install Performance Management.

KAVE05215-E

Processing cannot continue because Name Server is not running.

The Name Server service is not running.

(S)

Halts command execution.

(O)

Start the PFM - Manager service, and then re-execute the command.

KAVE05216-E

Processing cannot continue because Master Manager is not running.

The Master Manager service is not running.

(S)

Halts command execution.

(O)

Start the PFM - Manager service, and then re-execute the command.

KAVE05217-E

A host IP address could not be resolved.

Required host information has not been set up in the hosts file or DNS environment.

(S)

Halts command execution.

(O)

Set up the required host information in the hosts file or DNS environment, and then re-execute the command.

Make sure that it is possible to resolve the IP address of this host as well as the IP address of each host on each machine in the Performance Management system, set the required host information in the jpchosts file, the hosts file, or the DNS environment, and then re-execute the command.

For details, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

KAVE05222-E

Parsing failed. There is a parse error near option-name.

Option parsing failed. An invalid character is specified near the indicated characters.

(S)

Suspends processing.

(O)

Specify the correct parameter.

KAVE05223-E

The specified message text is too long.

The specified message text is too long.

(S)

Suspends processing.

(O)

Specify the message text correctly.

KAVE05224-E

option is defined more than once.

The indicated option cannot be specified more than once.

(S)

Suspends processing.

(O)

Specify the options correctly.

KAVE05225-E

An operand of option option-name is missing.

No value is specified for the indicated option.

(S)

Suspends processing.

(O)

Specify the correct parameter.

KAVE05226-E

The specification of the operand parameter is incorrect.

The value specified for the indicated parameter is invalid. The parameter value that was specified cannot be used.

(S)

Suspends processing.

(O)

Specify the parameter correctly.

KAVE05227-E

Processing was terminated because a signal was received.

Processing was terminated because a signal was received.

(S)

Halts command execution.

KAVE05228-E

The Store database files could not be accessed.

The database file of the Master Store or Agent Store service cannot be accessed. The file access permission to the database or folder has been altered illegally.

(S)

Halts command execution.

(O)

If the file permission to the database file or folder of the Master Store or Agent Store service has been altered, restore it and then re-execute the command.

KAVE05229-E

The specified sub-command is invalid for the Name Server or Status Server service.

The specified sub-command cannot be registered in the Name Server or Status Server service.

(S)

Halts command execution.

(O)

Specify the correct service ID, and then re-execute the command.

KAVE05230-E

The specified instance name is not set up. (inst=instance-name)

The specified instance name is not set up.

(S)

Halts command execution.

(O)

Specify the correct instance name, and then re-execute the command.

KAVE05231-W

Processing is skipped because the service has stopped. (service=service-id)

Some processing was skipped because the indicated service is stopped.

(S)

Continues command execution.

(O)

Ensure that the service is running, and then re-execute the command.

KAVE05232-E

Because backup or export was being processed, the request was refused.

Because backup or export was being processed, the request was refused.

(S)

Halts command execution.

(O)

Wait for backup or export processing to finish, and then re-execute the command.

KAVE05233-W

Processing is skipped because the service is running. (service=service-id)

Some processing was skipped because the indicated service is running.

(S)

Continues command execution.

(O)

Check the service's startup status by executing the jpctool service list command.

KAVE05234-E

The communication time-out occurred.

A timeout occurred during communication.

(S)

Halts command execution.

(O)

Check the following, and then re-execute the command:

Is the communicating service running?

Is it taking a long time to process a large amount of data?

For the jpctool db dump command, consider taking the following actions to reduce the amount of data to be processed:

Narrow the interval between the start date/time and the end date/time specified in the command options.

Specify in the command option a specific record ID instead of a wildcard character for the record ID.

KAVE05235-E

The backup processing was interrupted because the Store service stopped. (service=service-ID)

Backup processing was interrupted because the Master Store or Agent Store service was stopped.

(S)

Suspends the backup processing.

(O)

Start the Master Store or Agent Store service, and then re-execute backup processing. Do not restore the data that was being saved when this message was output.

KAVE05236-E

The dump processing was interrupted because the Store service stopped. (service=service-ID, dbid=database-ID)

Export processing was interrupted because the Master Store or Agent Store service was stopped.

(S)

Suspends the export processing.

(O)

Start the Master Store or Agent Store service, and then re-execute export processing.

KAVE05237-E

The service did not return the response to the request of the command in time. (service=service-name, lhost=logical-host-name, inst=instance-name, rc=maintenance-code)

The service did not return a response to the demand of the command within the specified time. One of the following is the possible cause of this error:

The service's status is busy.

The service is not running because an error occurred during startup of the UNIX version of the service.

(S)

Halts command execution. If you are using the linkage function with PFM - Web Console to manage stopping the PFM - Web Console service, the system stops only processing of PFM - Web Console.

(O)

Execute the jpctool service list command to check the service status. If the service status does not change from busy over a long time, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05238-W

The service will now forcibly stop because the service does not respond. (service=service-name, lhost=logical-host-name, inst=instance-name, option=option)

The service did not stop within the predetermined time. The service is being stopped forcibly because of the specified option.

(S)

Stops the service forcibly.

KAVE05239-E

An error occurred in archiving files.

An error occurred during file archiving using the tar command.

(S)

Suspends processing.

(O)

Check the standard error output, and eliminate the cause of the error.

KAVE05240-E

An error occurred in compressing the archive.

An error occurred in compression of the archive by the compress command or the gzip command.

(S)

Skips compression and continues processing.

(O)

Check whether the compress command or the gzip command has been installed. If they have not been installed, install them and manually compress the collected maintenance information.

For cases other than above, check the standard error output, and eliminate the cause of the error.

KAVE05241-E

The file copying failed because the disk capacity is insufficient or the destination path is too long.

An error occurred while a collected file was being copied.

(S)

Suspends processing.

(O)

Make sure that there is sufficient disk space available on the copy destination drive. If there is sufficient disk space, copying may have failed because the path of the collected file is too long. If that is the case, shorten the destination folder path and then re-execute the command.

KAVE05242-W

An attempt to acquire additional information of an agent failed. (servicekey=service-key, rc=return-code)

An attempt to collect additional information from an agent failed.

(S)

Continues processing.

KAVE05243-Q

A port number that does not exist in the import file exists in the services file. Do you want to delete it? (service=service-name, port=port-number) (Y/N) [N]:

A port number not specified in the import file exists in the services file.

(S)

The system deletes the port number if you enter Y or y. If you respond with any other character (including a space or a character string), the system does not delete the port number.

(O)

Make sure that deleting the specified port number is acceptable.

KAVE05244-Q

The specified port number is registered in the services file. Is this OK? (service=service-name, port=port-number) (Y/N) [Y]:

The specified port number does not exist in the services file.

(S)

The system does not register the port number into the services file if you enter N or n. If you respond with any other character (including a space or a character string), the system registers the port number into the services file.

(O)

Make sure that registering the specified port number into the services file is acceptable.

KAVE05245-E

The specified port number is already in use by another service. (service=service-name, port=port-number)

The specified port number cannot be registered into the services file because it is being used by another service.

(S)

Skips registration of the port number into the services file.

(O)

Check the port numbers, and specify a port number that is not in use in the services file.

KAVE05246-Q

The same service name exists in the services file but the port number is different. Do you want to change the port number from (old-port-number) to (new-port-number)? (service=service-name) (Y/N) [Y]:

Another service with the same name, but a different port number, exists in the services file.

(S)

The system does not change the port number in the services file if you enter N or n. If you respond with any other character (including a space or a character string), the system changes the port number in the services file.

(O)

Make sure that changing the port number in the services file is acceptable.

KAVE05247-I

The setup of the JP1/IM monitoring object cooperative function will now start.

Setup of the JP1/IM monitoring object cooperative function has started.

(S)

Starts the command normally.

KAVE05248-I

The unsetup of the JP1/IM monitoring object cooperative function will now start.

Unsetup of the JP1/IM monitoring object cooperative function has started.

(S)

Starts the command normally.

KAVE05249-E

The JP1/Base software installation directory cannot be acquired.

Referencing of the registry failed.

(S)

Stops the requested processing.

(O)

Check if JP1/Base has been installed. If JP1/Base has not been installed, install it and then execute the setup.

KAVE05250-E

The adapter command does not exist.

PFM - Manager has not been installed correctly.

(S)

Stops the requested processing.

(O)

Re-install PFM - Manager, and then set it up correctly.

KAVE05251-E

An adapter command configuration file storage directory does not exist.

There is no adapter command configuration file storage directory.

(S)

Stops the requested processing.

(O)

The following directory may be missing, which may be the reason for this error:

Windows: JP1/Base-installation-folder\plugin\conf\

UNIX: /opt/jp1base/plugin/conf/

Check if the JP1/Base product has been installed, and whether or not the adapter command configuration file storage directory has been deleted. If the directory has been deleted, re-install it and execute the setup.

KAVE05252-E

An attempt to delete the adapter command configuration file failed.

An attempt to delete the adapter command configuration file failed.

(S)

Stops the requested processing.

(O)

Re-execute the setup.

KAVE05253-E

An attempt to create the adapter command configuration file failed.

An attempt to create the adapter command configuration file failed.

(S)

Stops the requested processing.

(O)

Re-execute the setup.

KAVE05254-I

An adapter command configuration file does not exist.

The adapter command configuration file to be deleted was not found.

(S)

Resumes processing.

KAVE05255-I

An attempt to set up the JP1/IM monitoring object cooperative function ended normally.

Setup of the JP1/IM monitoring object cooperative function terminated normally.

(S)

Terminates the command normally.

KAVE05256-I

An attempt to unset up the JP1/IM monitoring object cooperative function ended normally.

Unsetup of the JP1/IM monitoring object cooperative function terminated normally.

(S)

Terminates the command normally.

KAVE05257-E

The JP1/PFM installation directory cannot be acquired.

Referencing of the registry failed.

(S)

Stops the requested processing.

(O)

Check if JP1/Base has been installed. If JP1/Base has not been installed, install it and then execute the setup.

KAVE05258-E

The setup key is not specified.

An argument specification is missing.

(S)

Stops the requested processing.

(O)

Re-execute the setup.

KAVE05259-E

An attempt to set up the JP1/IM monitoring object cooperative function ended abnormally.

Setup of the JP1/IM monitoring object cooperative function terminated abnormally.

A message indicating the cause was issued before this message.

(S)

Stops the requested processing.

(O)

Refer to the error message displayed before this message, eliminate the cause of the error, and then re-execute the command.

KAVE05260-E

An attempt to unset up the JP1/IM monitoring object cooperative function ended abnormally.

Unsetup of the JP1/IM monitoring object cooperative function terminated abnormally.

A message indicating the cause was issued before this message.

(S)

Stops the requested processing.

(O)

Refer to the error message displayed before this message, eliminate the cause of the error, and then re-execute the command.

KAVE05261-I

The port number deletion processing will now be skipped. (service=service-name, port=port-number)

Deletion of the port number is being skipped.

(S)

Skips deletion of the port number.

KAVE05262-I

The port number registration processing will now be skipped. (service=service-name, port=port-number)

Registration of the port number is being skipped.

(S)

Skips registration of the port number.

KAVE05263-I

The port number update processing will now be skipped. (service=service-name, port=port-number)

Updating of the port number is being skipped.

(S)

Skips updating of the port number.

KAVE05264-W

The collection of database information is skipped because the service is running. (service=service-name, lhost=logical-host-name, inst=instance-name)

Collection of database information is being skipped because the Master Store or Agent Store service is running.

If the service is running on a physical host, lhost=logical-host-name is not displayed. If the service is a single-instance agent, inst=instance-name is not displayed.

(S)

Skips collection of database information.

(O)

To collect the database information, stop the Master Store or Agent Store service, and then re-execute the command.

KAVE05265-E

The processing is not possible because the Store service or restore command is accessing the Store database.

The processing cannot be performed because the Master Store service, Agent Store service, or the restore command is accessing the Store database.

(S)

Halts command execution.

(O)

Either stop the Master Store or Agent Store service or stop the restore command, and then re-execute the command.

KAVE05266-E

The backup command was interrupted because Master Manager stopped.

The jpctool db backup command was suspended because the Master Manager service stopped.

(S)

Suspends the jpctool db backup command, but continues backup processing with the Master Store or Agent Store service.

(O)

To check the termination status of the backup processing that continued after the backup command was suspended, check the BACKUP.LOG file output under the Store database backup directory with generation number 01. If you find Ended normally, the backup processing ended normally.

KAVE05267-E

The dump command was interrupted because Master Manager stopped. (dbid=database-ID)

The jpctool db dump command was suspended because the Master Manager service stopped.

(S)

Suspends the jpctool db dump command, but continues the export processing with the Master Store or Agent Store service.

(O)

To check the termination status of the export processing that continued after the command was suspended, check the DUMP.LOG file output under the Store database export directory. If you find Ended normally, the export processing ended normally.

KAVE05268-E

An attempt to communicate with the Store service has failed. (service=service-ID)

An attempt to communicate with the Master Store or Agent Store service failed.

(S)

Halts command execution.

(O)

Check the service start status:

Is the service running?

Is communication connection possible?

Is PFM - Manager for the connection destination correct?

KAVE05269-E

A file I/O error occurred in processing of the Store database. (service=service-ID)

A file I/O error occurred on the Master Store or Agent Store service.

(S)

Halts command execution.

(O)

Check the status of the file system in the system where the Master Store or Agent Store service is running.

KAVE05270-E

An attempt to create a backup or export process has failed. (service=service-ID)

An attempt to create a backup or export process failed.

(S)

Halts command execution.

(O)

Check the system where the Master Store or Agent Store service is running to determine whether a memory shortage has occurred.

KAVE05271-E

The processing to import the alarm definition ended abnormally. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm definition import processing terminated abnormally.

(S)

If there is more alarm definition information to be imported, the system continues processing; otherwise, the system terminates the command.

(O)

Check the error message issued immediately before this message.

KAVE05272-I

The processing to import the alarm definition ended normally. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm definition import processing terminated normally.

(S)

If there is more alarm definition information to be imported, the system continues processing; otherwise, the system terminates the command.

KAVE05273-I

The processing to import the alarm definition was skipped. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm definition import processing was skipped because a character other than N or n was entered as the response to the alarm overwrite confirmation message.

(S)

If there is more alarm definition information to be imported, the system continues processing; otherwise, the system terminates the command.

KAVE05274-Q

An alarm with the same name already exists. Would you like to overwrite it? (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name) (Y/N)

An attempt was made to import an alarm definition, but the alarm already exists.

(S)

The system overwrites the alarm definition if you enter Y or y. If you respond with any other character, the system does not overwrite the alarm definition.

(O)

Check to determine whether the specified alarm can be overwritten.

KAVE05275-E

An alarm table with a different data model version exists. (product id=product-ID, alarm table=alarm-table-name, ver=data-model-version)

An attempt was made to import an alarm definition, but the alarm table already exists for a different data model version.

(S)

Cancels the alarm definition import processing.

(O)

Check the alarm definition data model version, and then re-execute the command.

KAVE05276-E

The processing to export the alarm definition was cancelled.

Export of the alarm definition was canceled because a character other than N or n was entered as the response to the file update confirmation message.

(S)

Halts command execution.

(O)

Make sure that the file is correct at the export destination, and then re-execute the command.

KAVE05277-I

The processing to export the alarm definition ended normally.

The alarm definition export processing terminated normally.

(S)

Terminates the command normally.

KAVE05278-E

The processing to export the alarm definition ended abnormally.

The alarm definition export processing terminated abnormally.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05279-I

The processing to display the alarm definition ended normally. (product id=product-ID, alarm table=alarm-table-name)

The alarm definition display processing terminated normally. If only -key was specified in the jpctool alarm list command, alarm names are not displayed.

(S)

Terminates the command normally.

KAVE05280-E

The processing to display the alarm definition ended abnormally. (product id=product-ID, alarm table=alarm-table-name)

The alarm definition display processing terminated abnormally. If only -key was specified in the jpctool alarm list command, alarm names are not displayed.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05281-E

The specified alarm table does not exist. (product id=product-ID, alarm table=alarm-table-name)

The specified alarm table does not exist.

(S)

Halts command execution.

(O)

Make sure that the correct alarm table is specified, and then re-execute the command.

KAVE05282-E

The specified alarm does not exist. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

The specified alarm does not exist.

(S)

Halts command execution.

(O)

Make sure that the correct alarm is specified, and then re-execute the command.

KAVE05283-E

The processing to bind the alarm table ended abnormally. (serviceid=service-ID, alarm table=alarm-table-name)

The alarm table bind processing terminated abnormally.

(S)

If there is another agent to be bound, the system continues processing; otherwise, the system terminates the command.

(O)

Check the error message issued immediately before this message.

KAVE05284-E

The agent that corresponds to the specified service ID does not exist.

The agent with the specified service ID does not exist.

(S)

Halts command execution.

(O)

Make sure that the correct service ID is specified, and then re-execute the command.

KAVE05285-I

The processing to bind the alarm table ended normally. (serviceid=service-ID, alarm table=alarm-table-name)

The alarm table bind processing terminated normally.

(S)

If there is another agent to be bound, the system continues processing; otherwise, the system terminates the command.

KAVE05286-E

The processing to unbind the alarm table ended abnormally. (serviceid=service-ID, alarm table=alarm-table-name)

The alarm table unbind processing terminated abnormally.

(S)

If there is another agent to be unbound, the system continues processing; otherwise, the system terminates the command.

(O)

Check the error message issued immediately before this message.

KAVE05287-I

The processing to unbind the alarm table ended normally. (serviceid=service-ID, alarm table=alarm-table-name)

The alarm table unbind processing terminated normally.

(S)

If there is another agent to be unbound, the system continues processing; otherwise, the system terminates the command.

KAVE05288-W

The alarm table is not bound to the specified agent. (product id=product-ID, alarm table=alarm-table-name)

The alarm table has not been bound to the specified agent.

If the -all option is specified, alarm table=alarm-table-name will not be displayed.

(S)

Halts command execution.

(O)

Check the agent to which the alarm table has been bound, and then re-execute the command.

KAVE05289-E

Alarm activation failed. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm activation failed.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05290-I

Alarm activation succeeded. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm was activated successfully.

(S)

Terminates the command normally.

KAVE05291-E

Alarm deactivation failed. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm deactivation failed.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05292-I

Alarm deactivation succeeded. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

Alarm was deactivated successfully.

(S)

Terminates the command normally.

KAVE05293-E

The processing to copy the alarm ended abnormally. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name, name=target-name)

The alarm copy processing terminated abnormally.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05294-E

The processing to copy the alarm table ended abnormally. (product id=product-ID, alarm table=alarm-table-name, name=target-name)

The alarm table copy processing terminated abnormally.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05295-I

The processing to copy the alarm ended normally. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name, name=target-name)

The alarm copy processing terminated normally.

(S)

Terminates the command normally.

KAVE05296-I

The processing to copy the alarm table ended normally. (product id=product-ID, alarm table=alarm-table-name, name=target-name)

The alarm table copy processing terminated normally.

(S)

Terminates the command normally.

KAVE05297-E

An alarm with the specified name already exists. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An alarm with the specified name already exists.

(S)

Halts command execution.

(O)

Check the alarm name in the specified alarm table, and then re-execute the command.

KAVE05298-E

An alarm table with the specified name already exists. (product id=product-ID, alarm table=alarm-table-name)

An alarm table with the specified name already exists.

(S)

Halts command execution.

(O)

Check the alarm table name defined with the specified service key, and specify a name that does not already exist.

KAVE05299-E

The processing to delete the alarm ended abnormally. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

The alarm deletion processing terminated abnormally.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05300-E

The processing to delete the alarm table ended abnormally. (product id=product-ID, alarm table=alarm-table-name)

The alarm table deletion processing terminated abnormally.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05301-I

The processing to delete the alarm ended normally. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

The alarm deletion processing terminated normally.

(S)

Terminates the command normally.

KAVE05302-I

The processing to delete the alarm table ended normally. (product id=product-ID, alarm table=alarm-table-name)

The alarm table deletion processing terminated normally.

(S)

Terminates the command normally.

KAVE05303-E

The alarm table cannot be edited because it is read-only. (product id=product-ID, alarm table=alarm-table-name)

The alarm table cannot be edited (imported or copied) because it is read-only.

(S)

Cancels the editing (importing or copying) of the alarm table.

(O)

Check if the specified alarm table is a solution set. If it is, specify another alarm table, and then re-execute the command.

KAVE05304-E

The number of alarms exceeds the alarm table maximum. (product id=product-ID, alarm table=alarm-table-name)

The number of alarms in the alarm table has reached the maximum.

(S)

Stops adding alarms to the alarm table.

(O)

Check the number of alarms in the specified alarm table. If the number of defined alarms exceeds the maximum value, specify another alarm table name, and then re-execute the command.

KAVE05305-E

The alarm definition file is invalid. (error=cause-of-error, line=line-number)

The alarm definition file is invalid.

(S)

If the jpctool alarm import command was executed, the system cancels the command execution. If the jpctool alarm check command was executed, the system continues processing.

(O)

Correct the alarm definition file on the basis of the displayed error cause and location, and then re-execute the command.

KAVE05306-E

The View Server service does not support the alarm operation command.

The View Server service does not support the alarm operation command.

(S)

Halts command execution. To execute the alarm operation command, PFM - Manager 08-00 or later is required.

KAVE05307-Q

The specified alarm table will now be deleted. Is this OK? (product id=product-ID, alarm table=alarm-table-name) (Y/N)

The specified alarm table will be deleted. Is this acceptable?

(S)

Deletes the alarm table if Y or y is entered. If you respond with any other character, the system cancels the deletion processing.

(O)

Check whether or not the specified alarm table can be deleted.

KAVE05308-Q

The specified alarm will now be deleted. Is this OK? (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name) (Y/N)

The specified alarm will be deleted. Is this acceptable?

(S)

Deletes the alarm if Y or y is entered. If you respond with any other character, the system cancels the deletion processing.

(O)

Check whether or not the specified alarm can be deleted.

KAVE05309-E

The processing to delete the alarm table was cancelled. (product id=product-ID, alarm table=alarm-table-name)

The alarm table deletion processing was cancelled because a character other than Y or y was entered as the response to the alarm table deletion confirmation message.

(S)

Halts command execution.

(O)

Make sure that the alarm table to be deleted is correct, and then re-execute the command.

KAVE05310-E

The processing to delete the alarm was cancelled. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

The alarm deletion processing was cancelled because a character other than Y or y was entered as the response to the alarm deletion confirmation message.

(S)

Halts command execution.

(O)

Make sure that the alarm to be deleted is correct, and then re-execute the command.

KAVE05311-W

The number of alarms that can be defined at the same time in the alarm definition file exceeded the maximum. (the number of alarm=number-of-exported-alarms/maximum-number-of-alarms-that-can-be-defined-concurrently)

The number of alarms in the alarm definition file has exceeded the maximum.

(S)

Resumes processing.

(O)

Divide the contents of the alarm definition file into multiple segments, and then execute import processing.

KAVE05312-I

The processing to check the alarm definition ended normally.

The alarm definition checking processing terminated normally.

(S)

Terminates the command normally.

KAVE05313-E

The processing to check the alarm definition ended abnormally.

The alarm definition checking processing terminated abnormally.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE05314-E

You cannot create an alarm table whose name starts with PFM. (product id=product-ID, alarm table=alarm-table-name)

An alarm table name beginning with PFM was specified when an alarm table was to be copied or a new alarm was to be created.

(S)

Cancels alarm table copying or new alarm creation.

(O)

An alarm table whose name begins with PFM cannot be used. Specify an alarm table name that does not begin with PFM, and then re-execute the command.

KAVE05315-E

An error occurred in an OS API(API-name). (en=OS-detail-code, arg1=argument-1, arg2=argument-2, arg3=argument-3)

An error occurred in an OS API. The code displayed as the OS detail code is the detail code of the system call errno or Win32 API.

(S)

Suspends processing.

(O)

Check the OS detail code. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05337-I

An alarm with the specified name already exists.(file=file-name, product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An alarm with the specified name already exits. When the system imports this alarm, it will display a message asking whether or not the alarm is to be overwritten.

(S)

Resumes processing.

(O)

The alarm definition file already contains the specified alarm. Check the message that has been output to the common message log.

KAVE05338-E

The processing cannot be continued because the alarm is being updated.(product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

The processing cannot be continued because the alarm is being updated.

(S)

Halts command execution.

(O)

Check the specified alarm and alarm table, and then re-execute the command.

KAVE05339-E

The alarm table of data model version (data-model-version-of-alarm-table) cannot be bound to an agent of data model version (data-model-version-of-agent). (alarm table=alarm-table-name)

The specified alarm table has a data model version that cannot be bound.

(S)

Halts command execution.

(O)

Check the data model versions of the specified alarm table and agent, and then re-execute the command. For details about data model versions, see the chapter that describe records in the applicable PFM - Agent manual.

KAVE05340-E

There is no alarm definition for the specified agent. (servicekey=service-key)

The processing cannot be continued because no alarm has been defined in the agent with the specified service key.

(S)

Halts command execution.

(O)

Make sure that the agent with the specified service key has alarm definition information.

KAVE05342-W

Processing is skipped because the service does not support the processing. (service=service-ID)

Processing is skipped because the service does not support the processing.

(S)

Continues execution of the command.

(O)

Make sure that the specified service supports the processing.

KAVE05343-E

The status management function cannot be disabled because a dependent function is enabled.

Because a function dependent on the status management function is enabled, the status management function cannot be disabled. The following functions are dependent on the status management function:

Health check function

Multiple monitoring function

(S)

Cancels execution of the command.

(O)

Disable the function dependent on the status management function, and then re-execute the command.

KAVE05344-E

The specified sub-command can only be used on a Manager host.

The specified sub-command can only be executed on a Manager host.

(S)

Cancels execution of the command.

(O)

Execute the sub-command on a Manager host.

KAVE05345-E

The health check function cannot be enabled because the status management function is not available.

The health check function cannot be enabled because the status management function has not been set up.

(S)

Cancels execution of the command.

(O)

Set up the status management function, and then re-execute the command.

KAVE05346-I

The setup of the health check function will now start. (host=host-name)

Setup of the health check function will start. host-name indicates the name of the host where the health check function will be set up.

(S)

Starts setup of the health check function.

KAVE05347-I

The setup of the health check function ended normally. (host=host-name)

Setup of the health check function ended normally. host-name indicates the name of the host where the health check function has been set up.

(S)

Ends setup of the health check function.

KAVE05348-E

The setup of the health check function terminated abnormally. (host=host-name)

Setup of the health check function ended abnormally. host-name indicates the name of the host where the setup of the health check function was attempted.

(S)

Ends setup of the health check function.

(O)

Check the preceding message and take the action indicated in the message. If the cause of the failure is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05349-E

The import processing cannot be executed because the status management function is not available.

Because the status management function has not been set up, the specified logical host environment definition file cannot be imported. The definition to be imported contains one of the following functions that are dependent on the status management function:

Health check function

Multiple monitoring function

(S)

Cancels execution of the command.

(O)

Enable the status management function, and then re-execute the command.

KAVE05350-W

The health check function on a physical host will be disabled because the status management function is not available.

Because the status management function has not been set up, the health check function on the physical host is disabled.

(S)

Disables the health check function on the physical host, and continues processing.

(O)

To enable the health check function again, set up the status management function and then set the health check function.

KAVE05351-E

The functionality for binding multiple alarm tables is disabled.

The specified operation cannot be performed because the functionality for binding multiple alarm tables is disabled.

(S)

Cancels the operation.

(O)

Make sure that the functionality for binding multiple alarm tables is enabled, and then re-execute the command.

KAVE05352-E

The number of alarm tables to be bound exceeds the limit. (serviceid=service-ID)

The operation cannot be continued because the number of alarm tables to be bound exceeds the limit.

(S)

Cancels the operation.

(O)

Check the argument, and then re-execute the command. If the specified argument is valid, check alarm tables that are bound to the specified service, unbind unnecessary alarm tables, and then re-execute the command.

KAVE05353-W

The alarm table is already bound to the specified agent. (product id=product-ID, alarm table=alarm-table-name)

The alarm table is already bound to the specified agent.

(S)

Cancels the command execution.

(O)

Check the agent to which an additional alarm table will be bound, and then re-execute the command.

KAVE05354-E

The processing to display the bind information ended abnormally. (serviceid=service-ID)

Processing to unbind all the alarm tables ended abnormally.

(S)

Continues processing if there are any other agents to be unbound. If not, terminates the command.

(O)

Check the error message that was output prior to this message.

KAVE05355-I

The processing to display the bind information ended normally. (serviceid=service-ID)

Processing to unbind all the alarm tables ended normally.

(S)

Continues processing if there are any other agents to be unbound. If not, finishes the command execution.

KAVE05356-E

The processing for additional binding of the alarm table ended abnormally. (serviceid=service-ID, alarm table=alarm-table-name)

Processing for additional binding of the alarm table ended abnormally.

(S)

Continues processing if there are any other agents to be bound. If not, finishes the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05357-I

The processing for additional binding of the alarm table ended normally. (serviceid=service-ID, alarm table=alarm-table-name)

Processing for additional binding of the alarm table ended normally.

(S)

Continues processing if there are any other agents to be bound. If not, finishes the command execution.

KAVE05358-E

The processing to unbind all the alarm tables ended abnormally. (serviceid=service-ID)

Processing to unbind all the alarm tables ended abnormally.

(S)

Continues processing if there are any other agents to be unbound. If not, finishes the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05359-I

The processing to unbind all the alarm tables ended normally. (serviceid=service-ID)

Processing to unbind all the alarm tables ended normally.

(S)

Continues processing if there are any other agents to be unbound. If not, finishes the command execution.

KAVE05360-E

The alarm definition is invalid. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

The alarm definition is invalid. product-ID, alarm-table-name, and alarm-name indicate the information about the invalid alarm definition.

(S)

Cancels the operation.

(O)

The alarm definition is invalid. Delete the displayed alarm definition.

KAVE05361-I

The monitoring target is now being added. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

The monitoring target is now being added to Remote Monitor.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Starts processing to add the monitoring target to Remote Monitor.

KAVE05362-I

The monitoring target has been added. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

The monitoring target has been added to Remote Monitor.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Ends processing to add the monitoring target to Remote Monitor.

KAVE05363-E

An attempt to add the monitoring target has failed. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

An attempt to add the monitoring target to Remote Monitor has failed.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05367-I

The monitoring target is now being updated. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

The monitoring target that has already been set to Remote Monitor is now being updated.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Starts processing to update the monitoring target that has already been set to Remote Monitor.

KAVE05368-I

The monitoring target has been updated. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

The monitoring target that has already been set to Remote Monitor was updated.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Finishes processing to update the monitoring target that has already been set to Remote Monitor.

KAVE05369-E

An attempt to update the monitoring target has failed. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

An attempt to update the monitoring target that has already been set to Remote Monitor failed.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05373-Q

name already exists. Do you want to update it? (Y/N)

This message confirms you to update the current definition because the specified name already exists.

(S)

Continues processing if Y or y is entered.

Cancels the command execution if N or n is entered.

If you enter any other character, the system will display the same message again.

(O)

Respond to the command.

KAVE05374-E

monitoring-target-name is already used by another monitoring group.

The specified monitoring-target-name is already used by another monitoring group.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying another monitoring target name that is not in use.

KAVE05376-I

The monitoring target is now being deleted. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

The monitoring target that has been set to Remote Monitor is now being deleted.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Starts processing to delete the monitoring target that has been set to Remote Monitor.

KAVE05377-I

The monitoring target has been deleted. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

The monitoring target that has been set to Remote Monitor was deleted.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Finishes processing to delete the monitoring target that has been set to Remote Monitor.

KAVE05378-E

An attempt to delete the monitoring target has failed. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

An attempt to delete the monitoring target that has been set to Remote Monitor failed.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05382-E

name does not exist.

The specified name does not exist.

(S)

Cancels the command execution.

(O)

Check the specified argument, and then re-execute the command.

KAVE05383-E

monitoring-target-name is not a monitoring target.

The specified monitoring-target-name is not a monitoring target.

(S)

Cancels the command execution.

(O)

Specify a valid monitoring target name, and then re-execute the command.

KAVE05385-E

An attempt to display the list of monitoring targets or monitoring groups has failed. (servicekey=service-key, inst=instance-name, lhost=logical-host-name)

An attempt to display the list of monitoring targets or groups has failed.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05386-I

The processing to display the configuration of the monitoring target ended normally. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

Processing to display the configuration of the monitoring target ended.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Finishes the command execution.

KAVE05387-E

An attempt to display the configuration of the monitoring target has failed. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

An attempt to display the configuration of the monitoring target has failed.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Check the error message that was output prior to this message.

KAVE05390-E

name is reserved and unavailable.

The specified name is reserved and cannot be used.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying another name.

KAVE05391-W

An alarm table cannot be bound to Remote Monitor. (service=service-ID)

An alarm table cannot be bound to Remote Monitor.

(S)

Cancels processing to bind the alarm table. If there is an agent that needs to be bound, the system continues processing.

(O)

Check the service to which an attempt to bind an alarm table performed. An alarm table cannot be bound to Remote Monitor. To set an alarm for a monitoring target of Remote Monitor, re-execute the command by specifying the virtual agent.

KAVE05392-W

An attempt to notify to Remote Monitor service was failed. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, update interval=update-interval)

An attempt to notify the Remote Monitor service has failed. It might take time to reflect the updates to the Remote Monitor service.

(S)

Cancels the command execution.

(O)

Use PFM - Web Console to make sure that the property of the service of the corresponding Remote Monitor instance has been updated. If the updates will not be reflected even after the specified time (in minutes) indicated by update-interval will pass, restart the service of the corresponding Remote Monitor instance.

KAVE05393-E

Specified sub-command cannot be used on this host.

The specified sub-command cannot be used on this host.

(S)

Cancels the command execution.

(O)

Check the executing host or the specified sub-command.

KAVE05394-E

The specified service is not supported for remote monitoring. (servicekey=service-key)

The specified service does not support remote monitoring.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the service that supports remote monitoring.

KAVE05395-W

The specified host name is invalid.

The specified host name is invalid.

(S)

Continues processing.

(O)

Specify a valid name.

KAVE05396-I

The monitoring target was not updated. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, target=monitoring-target-name)

The monitoring target that has already been set to Remote Monitor could not be updated.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Finishes the command execution.

KAVE05397-E

The number of monitoring targets had already reached the maximum limit. (servicekey=service-key, inst=instance-name, lhost=logical-host-name, max targets=maximum-number-of-monitoring-targets)

The number of monitoring targets that can be set to the Remote Monitor instance has already reached the maximum targets.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Delete unnecessary monitoring targets from the instance, or add the monitoring targets to a different instance.

KAVE05399-I

The existing file will be updated. (file=file-name)

The specified file already exists. This message corresponds to the KAVE05146-Q message. This occurred in query suppression mode, so the file will be updated and processing will continue.

(S)

Updates the file and continues processing.

KAVE05400-I

A logical host environment exists that is not in the import file. Processing will continue without deleting the logical host environment. (lhost=logical-host--name, servicekey=service-key[, inst=instance-name])

A logical host environment that is not in the import file exists.

This message corresponds to the KAVE05150-Q or KAVE05152-Q message. This occurred in query suppression mode, so the logical host environment will not be deleted and processing will continue.

inst=instance-name is displayed only for a multi-instance agent.

(S)

Continues processing without deleting the logical host environment.

(O)

Check the logical host environment in the message, and delete the logical host environment if it is not necessary.

KAVE05401-I

The specified logical host environment will be created. (lhost=logical-host--name, servicekey=service-key, inst=instance-name)

A new logical host environment will be added to the import file. This message corresponds to the KAVE05151-Q or KAVE05153-Q message. This occurred in query suppression mode, so processing will continue without confirmation.

inst=instance-name is displayed only for a multi-instance agent.

(S)

Creates a logical host environment and continues processing.

KAVE05402-I

A port number is in the services file that is not in the import file. Processing will continue without deleting the port number.(service=service-name, port=port-number)

A port number that is not in the import file exists in the services file. This message corresponds to the KAVE05243-Q message. This occurred in query suppression mode, so the port number will not be deleted and processing will continue.

(S)

Continues processing without deleting the port number.

KAVE05403-I

The specified port number will be registered in the services file. (service=service-name, port=port-number)

The specified port number will be registered in the services file. This message corresponds to the KAVE05244-Q message. This occurred in query suppression mode, so processing will continue without confirmation.

(S)

Registers the port number in the services file and continues processing.

KAVE05404-I

The service port number will be changed from (old-port-number) to (new-port-number). (service=service-name)

The same service name exists in the services file, but the port number is different. This message corresponds to the KAVE05244-Q message. This occurred in query suppression mode, so the port number in the services file will be changed and processing will continue.

(S)

Changes the port number in the services file and continues processing.

KAVE05405-I

name will be updated.

The name the user specified already exists. This message corresponds to the KAVE05373-Q message. This occurred in query suppression mode, so update processing will continue.

(S)

Continues update processing.

KAVE05406-I

The Store database will be initialized. (service=service-ID)

The Store database will be initialized when setup of the Store database extended functionality is canceled. This message corresponds to the KAVE05873-Q message. This occurred in query suppression mode, so processing will continue without confirmation.

(S)

Initializes the Store database data and continues processing.

KAVE05407-I

An existing instance environment will be updated. (lhost=logical-host--name, servicekey=service-key, inst=instance-name)

The instance the user specified already exists. This message corresponds to the KAVE05912-Q message. This occurred in query suppression mode, so update processing will continue.

(S)

Continues update processing.

KAVE05408-I

A port number was registered for the service. (service=service-ID, port=port-number)

Registering of a port number finished. This occurred in non-interactive input mode. If you release the fixed port number, <none> will be displayed for the port number.

(S)

Continues processing.

KAVE05409-W

A port number will not be set because another service is already using the specified port number. (service=service-ID, port=port-number)

The specified port number is already used by another service. This occurred in non-interactive input mode, so the setting of the port number for the corresponding service will be skipped.

service-ID indicates the ID of the service for which a port number is to be set. port-number indicates the port number written in the definition file.

(S)

Skips setting a port number for the corresponding service, and continues processing.

KAVE05410-W

A port number will not be set because the specified port number is invalid. (service=service-ID, port=port-number)

An invalid port number was specified. This occurred in non-interactive input mode, so the setting of the port number for the corresponding service will be skipped.

service-ID indicates the ID of the service for which a port number is to be set. port-number indicates the port number written in the definition file.

(S)

Skips setting a port number for the corresponding service, and continues processing.

KAVE05412-E

The product information in the non-interactive input definition file does not match the target product. (defined product=product-ID-in-the-definition-file, target product=target-product-ID)

Product information in the non-interactive input definition file does not match the target product.

(S)

Halts command execution.

(O)

Check and, if necessary, revise the product information in the non-interactive input definition file, and then re-execute the command.

KAVE05413-E

A required item is not in the non-interactive input definition file. (section=section, label=label)

A required item is not in the non-interactive input definition file.

(S)

Halts command execution.

(O)

Correct the non-interactive input definition file, and then re-execute the command.

KAVE05414-E

An item in the non-interactive input definition file is invalid. (section=section, label=label, value=value)

An item in the non-interactive input definition file is invalid.

(S)

Halts command execution.

(O)

Correct the non-interactive input definition file, and then re-execute the command.

KAVE05415-E

Exporting of the non-interactive input definition file template was cancelled.

Exporting of the non-interactive input definition file template was canceled because a character other than Y or y was entered as the response to the file update confirmation message.

(S)

Halts command execution.

KAVE05416-I

The non-interactive input definition file template was exported successfully.

The non-interactive input definition file template was exported successfully.

(S)

Terminates the command normally.

KAVE05417-E

Exporting of the non-interactive input definition file template failed.

Exporting of the non-interactive input definition file template failed.

(S)

Halts command execution.

(O)

Check the error message that was output prior to this message.

KAVE05418-W

The message text was truncated because it was too long. (len1=number-of-characters-before-truncated, len2=number-of-characters-after-truncated)

The message text was truncated because the length of the specified message text exceeded the limit.

(S)

Continues command execution.

KAVE05419-E

The version information of the non-interactive input definition file is invalid. (line=line-number)

The version information of the non-interactive input definition file is invalid.

(S)

Halts command execution.

(O)

Correct the version number of the non-interactive input definition file, and then re-execute the command.

KAVE05420-I

Business group definitions will now be imported.

Business group definitions will now be imported.

(S)

Starts the command execution.

KAVE05421-I

Business group definitions were successfully imported.

Business group definitions were successfully imported.

(S)

Terminates command execution.

KAVE05422-E

The importing of business group definitions ended abnormally.

Importing of business group definitions ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05423-Q

Do you want to update the business groups that already exist? (Y/N)

An attempt was made to import business group definitions, but the business groups already exist.

(S)

Updates the business group definitions only when Y or y is entered. If other characters are entered, the system does not update the business group definitions.

(O)

Check whether or not the specified business group can be updated.

KAVE05424-I

The existing business groups will now be updated.

The specified business groups already exists. This message corresponds to the KAVE05423-Q message. This occurred in query suppression mode, so the business groups will be updated.

(S)

Updates the business groups and continues processing.

KAVE05425-I

The existing business groups will not be updated.

Importing of business group definitions will be skipped because the -skip option was specified for a command argument or a character other than N or n was entered as the response to the business group update confirmation message.

(S)

Continues processing if further business group definitions are to be imported. If no further business group definitions are to be imported, the system terminates the command.

KAVE05426-E

A host with the specified name already exists in another business group. (group=business-group-name, host=host-name)

A host with the specified name already exists in another business group.

(S)

Halts command execution.

(O)

Correct the business group definitions, and then re-execute the command.

KAVE05427-E

An attempt to access the specified directory failed. (dir=directory-name)

An attempt to access the specified directory failed.

(S)

Halts command execution.

(O)

Make sure that the specified directory exists and can be accessed, and then re-execute the command.

KAVE05428-E

The business group information output file cannot be accessed. (dir=directory-name)

The business group information output file (monitoring_system_data.csv) cannot be accessed.

(S)

Halts command execution.

(O)

Make sure that the business group information output file exists and can be accessed, and then re-execute the command.

KAVE05429-W

A business group with the specified name already exists. (group=business-group-name)

A business group with the specified name already exists. When the system imports the business group, it will display a message asking whether or not the business group is to be updated.

(S)

Continues processing.

(O)

The specified business group is already defined in the business group definition file. Check whether or not the business group can be updated.

KAVE05430-E

An invalid value has been specified. (label=label-name, value=value, line=line-number)

An invalid value has been specified.

(S)

Halts command execution.

(O)

Correct the value and re-execute the command.

KAVE05431-E

An invalid value has been specified. (header=header-name, value=value, line=line-number)

An invalid value has been specified.

(S)

Halts command execution.

(O)

Correct the value and re-execute the command.

KAVE05432-E

The specified file cannot be imported because it is an incompatible version. (file=file-name, version=file-version)

The version information of the specified file is invalid.

(S)

Halts command execution.

(O)

Specify a file with the supported version, and then re-execute the command.

KAVE05433-E

Multiple business groups with the same name are defined in the specified file. (group=business-group-name)

Multiple business groups with the same name are defined in the specified file.

(S)

Halts command execution.

(O)

Correct the business group definitions, and then re-execute the command.

KAVE05434-E

Multiple hosts with the same name are defined in the specified file. (host=host-name)

Multiple hosts with the same name are defined in the specified file.

(S)

Halts command execution.

(O)

Correct the business group definitions, and then re-execute the command.

KAVE05435-I

Business group definitions will now be exported.

Business group definitions will now be exported.

(S)

Starts the command execution.

KAVE05436-I

Business group definitions were successfully exported.

Business group definitions were successfully exported.

(S)

Terminates command execution.

KAVE05437-E

The exporting of business group definitions ended abnormally.

Exporting of business group definitions ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05438-E

The exporting of business group definitions was canceled.

Exporting of business group definitions was canceled because a character other than Y or y was entered as the response to the file update confirmation message.

(S)

Halts command execution.

(O)

Back up the existing file or change the specified file name, and then re-execute the command.

KAVE05439-E

The specified business group does not exist. (group=business-group-name)

The specified business group does not exist.

(S)

Halts command execution.

(O)

Make sure that the specified business group exists, and then re-execute the command.

KAVE05440-E

The specified business group name is invalid. (group=business-group-name)

The format of the specified business group name is invalid.

(S)

Halts command execution.

(O)

Specify a correct business group name, and then re-execute the command.

KAVE05441-I

The specified business group will now be deleted. (group=business-group-name)

The specified business group will now be deleted.

(S)

Continues processing.

KAVE05442-I

A list of business group names was successfully displayed.

A list of business group names was successfully displayed.

(S)

Terminates command execution.

KAVE05443-E

The displaying of a list of business group names ended abnormally.

The displaying of a list of business group names ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05444-I

Business group definitions will now be displayed.

Business group definitions will now be displayed.

(S)

Starts the command execution.

KAVE05445-I

Business group definitions were successfully displayed.

Business group definitions were successfully displayed.

(S)

Terminates command execution.

KAVE05446-E

The displaying of business group definitions ended abnormally.

The displaying of business group definitions ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05447-I

The business groups will now be deleted.

The business groups will now be deleted.

(S)

Starts the command execution.

KAVE05448-I

The business groups were successfully deleted.

The business groups were successfully deleted.

(S)

Terminates command execution.

KAVE05449-E

The deletion of the business groups ended abnormally.

The deletion of the business groups ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05450-Q

Do you want to delete the specified business groups? (Y/N)

The specified business groups will now be deleted. Do you want to delete them?

(S)

Deletes the business groups only when Y or y is entered. If other characters are entered, the business groups will not be deleted.

(O)

Check whether or not the specified business groups can be deleted.

KAVE05451-E

The deletion of the business groups was canceled.

The deletion of the business groups was canceled because a character other than Y or y was entered as the response to the confirmation message for deleting business groups.

(S)

Halts command execution.

(O)

Make sure that the business groups to be deleted are correctly specified, and then re-execute the command.

KAVE05452-I

The specified business groups will now be deleted.

The specified business groups will now be deleted. This message corresponds to the KAVE05450-Q message. This occurred in query suppression mode, so the business groups will be deleted and processing will continue.

(S)

Deletes the business groups and continues processing.

KAVE05453-I

Business group definitions will now be checked.

Business group definitions will now be checked.

(S)

Starts the command execution.

KAVE05454-I

Business group definitions were successfully checked.

Business group definitions were successfully checked.

(S)

Terminates command execution.

KAVE05455-E

The checking of business group definitions ended abnormally.

The checking of business group definitions ended abnormally.

(S)

Halts command execution.

(O)

Eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05456-E

The specified value is too long. (label=label-name,value=value,line=line-number)

The length of the character string for the specified value exceeded the limit.

(S)

Halts command execution.

(O)

Correct the value and re-execute the command.

KAVE05457-E

The specified value is too long. (header=header-name,value=value,line=line-number)

The length of the character string for the specified value exceeded the limit.

(S)

Halts command execution.

(O)

Correct the value and re-execute the command.

KAVE05458-E

The specified business group name is too long. (group=business-group-name)

The length of the specified business group name exceeded the limit.

(S)

Halts command execution.

(O)

Specify a correct business group name, and then re-execute the command.

KAVE05459-E

The business group access control function is disabled.

The business group access control function is disabled.

(S)

Halts command execution.

(O)

Enable the business group access control function, and then re-execute the command.

KAVE05460-I

The business group is not defined.

The business group is not defined.

(S)

Terminates command execution.

(O)

Make sure that the business group is defined, and then re-execute the command.

KAVE05470-E

The common account information is not configured. (type = common-account-information-type, lhost = logical-host-name)

The common account information is not configured.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Halts command execution.

(O)

Configure the common account information, and then re-execute the command.

KAVE05471-I

The common account information was displayed successfully. (type = common-account-information-type, lhost = logical-host-name)

The common account information was displayed successfully.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Terminates command execution.

KAVE05472-E

An attempt to display the common account information failed. (type = common-account-information-type, lhost = logical-host-name)

An attempt to display the common account information failed.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Halts command execution.

(O)

Check the error message that was output prior to this message.

KAVE05473-I

The common account information was configured successfully. (type = common-account-information-type, lhost = logical-host-name)

The common account information was configured successfully.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Terminates command execution.

KAVE05474-E

An attempt to configure the common account information failed. (type = common-account-information-type, lhost = logical-host-name)

An attempt to configure the common account information failed.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Halts command execution.

(O)

Check the error message that was output prior to this message.

KAVE05475-I

The common account information was deleted successfully. (type = common-account-information-type, lhost = logical-host-name)

The common account information was deleted successfully.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Terminates command execution.

KAVE05476-E

An attempt to delete the common account information failed. (type = common-account-information-type, lhost = logical-host-name)

An attempt to delete the common account information failed.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Halts command execution.

(O)

Check the error message that was output prior to this message.

KAVE05477-Q

The common account information is already configured. (type = common-account-information-type, lhost = logical-host-name). Do you want to update it? (Y/N)

This is a confirmation message asking whether the common account information is to be updated.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Continues processing if the response is the uppercase letter Y or the lowercase letter y (1 byte). If the response is a space character or a character other than an uppercase Y or lowercase y, processing is canceled.

(O)

Enter a response to the command.

KAVE05478-I

The common account information is being updated. (type = common-account-information-type, lhost = logical-host-name)

The common account information will be updated. This message corresponds to the KAVE05477-Q message. This processing was executed in query suppression mode, so the update processing will continue.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Updates the common account information and then continues processing.

KAVE05479-Q

The common account information will be deleted. (type = common-account-information-type, lhost = logical-host-name). Are you sure you want to delete this information? (Y/N)

This is a confirmation message asking whether the common account information is to be deleted.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Continues processing if the response is the uppercase letter Y or the lowercase letter y (1 byte). If the response is a space character or a character other than an uppercase Y or lowercase y, processing is canceled.

(O)

Enter a response to the command.

KAVE05480-I

The common account information is being deleted. (type = common-account-information-type, lhost = logical-host-name)

This message corresponds to the KAVE05479-Q message. This processing was executed in query suppression mode, so the deletion processing will continue.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Deletes the common account information and then continues processing.

KAVE05481-I

The input definition file template was exported successfully. (type = common-account-type)

The input definition file template was exported successfully.

(S)

Terminates command execution.

KAVE05482-E

The common account information type is not specified.

The common account information type is not specified.

(S)

Halts command execution.

(O)

Specify the common account information type, and then re-execute the command.

KAVE05483-E

The specified common account information type is invalid. (type = common-account-information-type)

The specified common account information type is invalid.

(S)

Halts command execution.

(O)

Specify the correct common account information type, and then re-execute the command.

KAVE05484-E

Some common account information items are missing. (type = common-account-information-type, query = query)

Some common account information items are missing. If the number of common account information items increases due to a product version upgrade, the common account information created in older versions becomes unavailable.

(S)

Halts command execution.

(O)

Re-create the common account information, and then re-execute the command.

KAVE05485-E

The common account information type specified in the input definition file does not match the type specified in the command. (defined type = common-account-information-type-for-the-input-definition-file, target type = common-account-information-type-for-the-command, section = section, label = label)

The common account information type of the input definition file does not match the type specified in the command.

(S)

Halts command execution.

(O)

Correct the common account information type of the input definition file, and then re-execute the command. Alternatively, change the type of the common account information to be specified, and then re-execute the command.

KAVE05486-E

The common account information is being used by a monitoring target or an instance. (type = common-account-information-type, lhost = logical-host-name, productid = product-ID, inst = instance-name, target = monitoring-target-name)

Because an environment that uses the common account information exists, deletion of the common account information was stopped.

Note that, for a physical host environment, information about logical hosts does not appear. In addition, if an instance or monitoring target does not exist, the information for that instance or monitoring target is not displayed.

(S)

Halts command execution.

(O)

For an instance or a monitoring target that uses the common account information, either specify the setting that does not use the common account information or delete the setting that uses the common account information, and then re-execute the command.

KAVE05487-I

The common account information was not updated. (type = common-account-information-type, lhost = logical-host-name)

The configured common account information was not updated.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Terminates command execution.

KAVE05488-I

The common account information was not deleted. (type = common-account-information-type, lhost = logical-host-name)

The common account information was not deleted.

Note that, for a physical host environment, information about logical hosts does not appear.

(S)

Terminates command execution.

KAVE05489-W

The specified file does not exist. (file = file-name)

The specified file does not exist.

(S)

Continues processing.

(O)

Check the specified file.

KAVE05490-E

An attempt to access the file failed. (file = file-name)

An attempt to access the file failed because another process is referencing or updating the file.

(S)

Terminates command execution.

(O)

Wait a while, and then re-execute the command.

KAVE05491-Q

The existing values specified in the common account information will be deleted. Are you sure you want to delete these values? (Y/N)

This is a confirmation message asking whether the existing values specified in the common account information are to be deleted.

(S)

Continues processing if the response is the uppercase letter Y or the lowercase letter y (1 byte). If the response is a space character or a character other than an uppercase Y or lowercase y, processing is canceled.

(O)

Enter a response to the command.

KAVE05492-I

The existing values specified in the common account information are being deleted.

The existing values specified in the common account information will be deleted. This message corresponds to the KAVE05491-Q message. This processing was executed in query suppression mode, so the update processing will continue.

(S)

Deletes the setting values and then continues processing.

KAVE05800-I

The updating of the data model will now start.

Updating of the data model version is being started.

(S)

Starts command execution.

KAVE05801-I

The updating of the data model ended.

Updating of the data model version is finished.

(S)

Terminates command execution.

KAVE05810-E

An option is not specified.

An option is not specified.

(S)

Halts command execution.

(O)

Specify the option, and then re-execute the command.

KAVE05811-E

The specified dictionary file was not found. (dict=dictionary-file-name)

The specified dictionary file does not exist.

(S)

Cancels installation processing.

(O)

When the Store database has been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Install the PFM - Agent that existed before upgrading.

3. Restore the Store database.

4. Reinstall the PFM - Agent whose upgrading failed.

When the Store database has not been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Reinstall the PFM - Agent whose upgrading failed.

For details about restoration of the Store database, see the chapter that describes backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05812-E

The specified dictionary file is invalid. (dict=dictionary-file-name, line=line-number, errmsg=message)

The contents of the dictionary file are invalid.

(S)

Cancels installation processing.

(O)

When the Store database has been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Install the PFM - Agent that existed before upgrading.

3. Restore the Store database.

4. Reinstall the PFM - Agent whose upgrading failed.

When the Store database has not been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Reinstall the PFM - Agent whose upgrading failed.

For details about restoration of the Store database, see the chapter that describes backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05813-E

A datatype cannot be converted. (dict=dictionary-file-name, line=line-count)

A data type cannot be converted.

(S)

Cancels installation processing.

(O)

When the Store database has been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Install the PFM - Agent that existed before upgrading.

3. Restore the Store database.

4. Reinstall the PFM - Agent whose upgrading failed.

When the Store database has not been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Reinstall the PFM - Agent whose upgrading failed.

For details about restoration of the Store database, see the chapter that describes backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05814-E

A rule cannot be converted. (dict=dictionary-file-name, line=line-count)

A collection rule cannot be converted.

(S)

Cancels installation processing.

(O)

When the Store database has been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Install the PFM - Agent that existed before upgrading.

3. Restore the Store database.

4. Reinstall the PFM - Agent whose upgrading failed.

When the Store database has not been backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Reinstall the PFM - Agent whose upgrading failed.

For details about restoration of the Store database, see the chapter that describes backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05815-E

The specified directory was not found. (dir=directory)

The specified directory does not exist.

(S)

Cancels installation processing.

(O)

Check if the displayed directory can be created. If it cannot be created, eliminate the cause of the error, and then re-install.

KAVE05816-E

The specified Store database is invalid. (db=database, errmsg=message)

The contents of the specified Store database are invalid.

(S)

Cancels installation processing.

(O)

When the message was displayed during successful upgrading of PFM - Agent

An invalid record was detected, but no action is required because data integrity has been restored by deleting the corresponding record.

When the message was displayed during unsuccessful upgrading of PFM - Agent

When the Store database was backed up before upgrading

Execute the following procedure:

1. Uninstall the PFM - Agent whose upgrading failed.

2. Install the PFM - Agent that existed before upgrading.

3. Restore the Store database.

4. Reinstall the PFM - Agent whose upgrading failed.

When the Store database was not backed up before upgrading

Delete the Store database file (.DB and .IDX file extensions) of the Agent Store whose upgrading failed, and then reinstall PFM - Agent.

For details about restoration of the Store database, see the chapter that describes backup and restoration in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE05817-E

The Store database directory cannot be specified as the work directory. (wkdir=work-directory, stdir=database-directory)

The Store database directory cannot be specified as the work directory.

(S)

Cancels installation processing.

(O)

Check if the specified work directory is a symbolic link to the database directory. If it is, delete the symbolic link, and then re-execute installation.

KAVE05821-E

The product ID of the data model is incorrect. (prodid1=product-ID, prodid2=product-ID)

The product ID of the data model is incorrect.

(S)

Halts command execution.

(O)

Check the service key of the specified PFM - Agent, and either specify the correct PFM - Agent or the correct Store database, then re-execute the command.

KAVE05823-E

The version of the data model is incorrect. (ver1=data-model-version, ver2=data-model-version)

The data model version is incorrect.

(S)

Halts command execution.

(O)

Check the data model version of the specified PFM - Agent, specify the correct Store database, and then re-execute the command. For details about the data model version, see the chapter that describes records in the applicable PFM - Agent manual.

KAVE05832-E

An attempt to access a file failed. (file=file-name, api=API-name, en=error-code, errmsg=message)

An attempt to access the specified file failed.

(S)

Cancels installation processing.

(O)

Check if the file is accessible. If it is not, eliminate the cause of the access error, and then re-execute installation.

KAVE05833-E

An attempt to access a directory failed. (dir=directory-name, api=API-name, en=error-code, errmsg=message)

An attempt to access the specified directory failed.

(S)

Cancels installation processing.

(O)

Check if the directory is accessible. If it is not, eliminate the cause of the access error, and then re-execute installation.

KAVE05834-W

The records of the database-ID database up to database-deletion-time were deleted because the Store database reached the write limit during the update of the data model. (drawer=summary-type, db=database-file-name)

When the data model was being upgraded, records were deleted because the write limit value for the Store database was reached.

When the database ID is PI

The type of summary record to be deleted depends on the value of drawer. The value of drawer is one of 1 (minute), 2 (hour), 3 (day), 4 (week), 5 (month), or 6 (year). Records whose summary type is shorter than that of the drawer value are deleted, and records whose summary type is longer than that of the drawer value are retained. For summary records whose type corresponds to the drawer value, those that were collected prior to the deletion time are deleted. As for records that were collected at the deletion time, some of them may be deleted.

When the database ID is other than PI

Records collected prior to the deletion time are deleted. However, some records collected at the deletion time may also be deleted because records are stored in the database until the write limit value is reached. The value of drawer is always 1.

(S)

Deletes records, and then continues installation processing.

(O)

The data retention period settings may not be appropriate for the upgraded data model. Check and, if necessary, revise the data retention period settings for the new data model.

KAVE05835-I

Setup of the Store database extended functionality will now start. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Setup of the extended functionality of the Store database will start.

(S)

Starts setup of the extended functionality of the Store database.

KAVE05836-I

Setup of the Store database extended functionality ended normally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Setup of the extended functionality of the Store database ended normally.

(S)

Ends (in a normal end) setup of the extended functionality of the Store database.

KAVE05837-E

Setup of the Store database extended functionality ended abnormally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Setup of the extended functionality of the Store database ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05838-I

Unsetup of the Store database extended functionality will now start. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Unsetup of the extended functionality of the Store database will start.

(S)

Starts unsetup of the extended functionality of the Store database.

KAVE05839-I

Unsetup of the Store database extended functionality ended normally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Unsetup of the extended functionality of the Store database ended normally.

(S)

Ends (in a normal end) unsetup of the extended functionality of the Store database.

KAVE05840-E

Unsetup of the Store database extended functionality ended abnormally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Unsetup of the extended functionality of the Store database ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05841-I

Import processing of the Store database will now start. (servicekey=service-key, lhost=logical-host-name, inst=instance-name, dir=directory-name)

Importing of data into the Store database will start.

(S)

Starts importing data into the Store database.

KAVE05842-I

Store database import processing ended normally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name, dir=directory-name)

Importing of data into the Store database ended normally.

(S)

Ends (in a normal end) the import of data into the Store database.

KAVE05843-E

Store database import processing ended abnormally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name, dir=directory-name)

Importing of data into the Store database ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05844-I

Data imported into the Store database will now be cleared. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Clearing of the data imported into the Store database will start.

(S)

Starts to clear the data imported into the Store database.

KAVE05845-I

Clearing of data imported Store database ended normally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Clearing of the data imported into the Store database ended normally.

(S)

Ends (in a normal end) the clearing of the data imported into the Store database.

KAVE05846-E

Clearing of data imported Store database ended abnormally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Clearing of the data imported into the Store database ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05847-I

Data model conversion of backup data will now start. (dir=directory-name)

Conversion of the data model of the backup data will start.

(S)

Starts conversion of the data model of the backup data.

KAVE05848-I

Data model conversion of backup data ended normally. (dir=directory-name)

Conversion of the data model of backup data ended normally.

(S)

Ends (in a normal end) the conversion of the data model of the backup data.

KAVE05849-E

Data model conversion of backup data ended abnormally. (dir=directory-name)

Conversion of the data model of the backup data ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output prior to this message, and eliminate the cause of the error by following the instructions given in that message. Then, restore the backup data and definition files that were backed up by the command, and re-execute the jpctool db dmconvert command. For details about the restore procedure, see the chapter that describes the jpctool db dmconvert command.

Note that before the restore procedure, Performance Management commands or services must not be used to view or operate on the Store database in backup-directory.

If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05850-I

The update processing of the files ended normally.

The ini file was updated normally.

(S)

Terminates command execution.

KAVE05851-E

An attempt to update the files failed.

Updating of the ini file failed.

(S)

Stops the requested service.

(O)

Check the following:

If you specified a service key, does a model file exist?

If you specified the name of an ini file, does the specified file exist?

KAVE05852-I

Displaying the version information of backup data ended normally. (dir=directory-name)

Displaying of the backup data version ended normally.

(S)

Ends (in a normal end) display of the backup data version.

KAVE05853-E

Displaying the version information of backup data ended abnormally. (dir=directory-name)

Displaying of the backup data version ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05854-I

Displaying the version information of the Store database ended normally.

Displaying of the Store database version ended normally.

(S)

Ends (in a normal end) display of the Store database version.

KAVE05855-E

Displaying the version information of the Store database ended abnormally.

Displaying of the Store database version ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05856-I

Updating the configuration information of the Store database ended normally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name, label=label-name)

Updating of the Store database settings ended normally.

(S)

Ends (in a normal end) update of the Store database settings.

KAVE05857-E

Updating the configuration information of the Store database ended abnormally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name, label=label-name)

Updating of the Store database settings ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05858-I

Displaying Store database configuration information ended normally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Displaying of the Store database settings ended normally.

(S)

Ends (in a normal end) display of the Store database settings.

KAVE05859-E

Displaying Store database configuration information ended abnormally. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

Displaying of the Store database settings ended abnormally.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05860-E

The specified directory does not exist. (dir=directory-name)

The directory indicated by directory-name does not exist.

(S)

Stops processing.

(O)

Make sure that the directory specified in the argument exists.

KAVE05861-E

A specified setting is incorrect.

The value specified for an argument is incorrect.

(S)

Stops processing.

(O)

Make sure that the specified value is correct. If the specified value is a directory, make sure that the specified directory exists.

KAVE05862-E

The format of the specified directory is invalid. (dir=directory-name)

The format of the directory indicated by directory-name is invalid.

(S)

Stops processing.

(O)

Make sure that the directory indicated by directory-name is the backup directory for the Store database. If this message appears when you execute the jpctool db import command, make sure that the product ID and the data model version of the agent at the import destination and those of the specified backup directory match.

KAVE05863-E

The Store database extended functionality is already setup.

The extended functionality of the Store database is already set up.

(S)

Cancels setup because the extended functionality of the Store database is already set up.

(O)

Make sure that the specified argument is correct.

KAVE05864-E

The Store database extended functionality is not setup.

The extended functionality of the Store database is not set up.

(S)

Cancels processing.

(O)

Make sure that the specified argument is correct.

KAVE05865-E

The specified directory is not empty. (dir=directory-name)

The directory indicated by directory-name is not empty.

(S)

Stops processing.

(O)

The directory to be specified must be empty. Check and delete contents of the directory indicated by directory-name, or specify a different directory that is empty.

KAVE05867-E

Initialization of the Store database failed.

Initialization of the Store database has failed.

(S)

Terminates the command.

(O)

Check the message that was output immediately before this message.

KAVE05868-E

Processing will now stop because, in the current status, the service cannot process requests. (service=service-name, status=status)

Because the service indicated by service-name cannot process requests, processing stops. status indicates the status of the service.

(S)

Stops processing.

(O)

Eliminate the cause of the error and then re-execute the command.

KAVE05871-E

A request was refused because importing was being performed.

Data cannot be imported because the Store service is importing other data.

(S)

Stops processing.

(O)

Wait until the current import operation has finished, and then re-execute the command.

KAVE05872-E

The Store database does not exist in the specified environment.

There is no information to be displayed because the Store service does not exist in the specified environment.

(S)

Stops processing.

(O)

Check the command arguments and then re-execute the command.

KAVE05873-Q

If you continue the processing, the Store database will be initialized. Do you want to continue? (Y/N)

This confirmation message asks, when you are canceling setup of the extended functionality of the Store database, whether it is okay to initialize the Store database.

(S)

Continues processing only when you specify Y or y. The system cancels processing if any other characters (including a space character or nothing) is entered.

(O)

Respond to the command.

KAVE05874-Q

If you continue the processing, the import data will be initialized. Do you want to continue? (Y/N)

This confirmation message asks, when you are importing new data into the Store database, whether it is okay to initialize existing import data in the import directory.

(S)

Continues processing only when you specify Y or y. The system cancels processing if you specify any other character (including a space character or nothing).

(O)

Respond to the command.

KAVE05875-E

The specified Store service does not support import processing.

Import was not performed because the specified version of the Store service could not import data.

(S)

Stops processing.

(O)

The Agent Store service of Store 1.0 cannot import data. Enable the extended functionality of the Store database, and then re-execute the command.

KAVE05876-E

Conversion of a database has failed. (db=database-name)

Processing has stopped because conversion of the database indicated by database-name failed.

(S)

Stops processing.

(O)

Check the message that was output immediately before this message.

KAVE05877-E

An attempt to transfer a database file has failed. (db=database-name)

Processing has stopped because file transfer failed for the database indicated by database-name.

(S)

Stops processing.

(O)

Eliminate the cause of the failure and re-execute the command. Possible causes of the failure are the following:

Disk space is insufficient at the move destination.

The user does not have access permission for the directory.

KAVE05878-E

The specified service does not support the Store database extended functionality.

Setup could not be performed because the service specified in the argument cannot use the extended functionality of the Store database.

(S)

Stops processing.

(O)

The extended functionality of the Store database is available for agent products of version 08-00 or later. Upgrade your agent, and then re-execute the command.

KAVE05879-E

Master Store service backup data cannot be specified.

The jpcconf db display command or the jpctool db dmconvert command was executed for the backup data collected by the Master Store service. These commands can be used only for backup data collected by the Agent Store service.

(S)

Stops processing.

(O)

Check the arguments and the backup data, and then re-execute the command.

KAVE05880-E

An I/O error occurred during processing. (file-name)

An I/O error occurred during access to the file or the directory indicated by file-name.

(S)

Stops processing.

(O)

Eliminate the cause of the failure and re-execute the command. Possible causes of the I/O error are the following:

Disk space is insufficient.

The user does not have access permission for the file.

The file or the directory does not exist.

KAVE05881-E

The current configuration information exceeds the Store database extended functionality limit. (dir=directory-name, label=label-name)

The name of the directory indicated by label-name exceeds the limit on directories that can be used by the extended functionality of the Store database.

(S)

Stops processing.

(O)

Change the name of the directory indicated by label-name to a value permitted by the extended functionality of the Store database, and re-execute the command.

KAVE05882-E

Unsetup of the Store database extended functionality is not supported for this product. (servicekey=service-key)

The specified product cannot remove the Store database extended functionality. The unsetup of the extended functionality will not be performed.

(S)

Cancels processing.

(O)

Check the command argument. If the setting is invalid, re-execute the command by specifying the correct argument.

KAVE05883-W

The setting of JP1 System Event functionality will be the default setting because the current setting is invalid. (label=label-name, value=current-value, default=default-value)

The default setting will be used for the JP1 system event functionality because the current setting is invalid.

(S)

Operates the JP1 system event functionality by using the default setting because the current setting is invalid.

(O)

Use PFM - Web Console to modify the JP1 event settings on the corresponding host. If this message is still output, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05900-E

No setup file exists. (path)

The setup file stored in the following PFM - Agent setup file folder could not be found:

In Windows: installation-folder\setup\

In UNIX: /opt/jp1pc/setup/

The setup file name that corresponds to the specified service key is displayed in path.

However, if the setup file cannot be found in the PFM - Agent setup file folder when all is specified as the service key, NULL is displayed.

(S)

Stops the requested processing.

(O)

Copy the PFM - Agent setup file to be added to the PFM - Agent setup file folder, and then re-execute the command.

KAVE05901-E

An attempt to extract the setup file failed. (path)

An error occurred during extraction of the setup file indicated by path. Possible causes are as follows:

You do not have access permission for the setup file.

You do not have access permission for the following PFM - Agent setup file extraction folder:

In Windows: installation-folder\setup\extract\

In UNIX: /opt/jp1pc/setup/extract/

An invalid file exists in the following PFM - Agent setup file folder:

In Windows: installation-folder\setup\

In UNIX: /opt/jp1pc/setup/

Insufficient disk space

(S)

Stops the requested processing.

(O)

Check the following, and then re-execute the command:

Do you have access permission for the setup file indicated by path?

Do you have access permission for the PFM - Agent setup file extraction folder?

Is there an invalid file in the PFM - Agent setup file folder?

Is the disk space sufficient?

KAVE05902-E

An attempt to setup the new agent (Pfm-Agent-service-key) for Manager failed. (version=version)

An attempt to set up a PFM - Agent, indicated by Pfm-Agent-service-key, for PFM - Manager failed. Possible causes are as follows:

You do not have access permission for the following folders:

In Windows:

- installation-folder\mgr\manager\

- installation-folder\mgr\viewsvr\

In UNIX:

- /opt/jp1pc/mgr/manager/

- /opt/jp1pc/mgr/viewsvr/

Insufficient disk space

A service is running

(S)

Stops the requested processing.

(O)

Check the following, and then re-execute the command:

Do you have access permission for the folder?

Is the disk space sufficient?

Is there a service that is running?

KAVE05904-E

An attempt to setup the new agent (Pfm-Agent-service-key) failed. (version=version)

An attempt to copy the information about the PFM - Agent, indicated by Pfm-Agent-service-key, to the jpcplist.ini file, failed.

It is possible that the following file does not exist or that you do not have access permission for the following file:

In Windows: installation-folder\jpcplist.ini

In UNIX: /opt/jp1pc/jpcplist.ini

(S)

Stops the requested processing.

(O)

Check the following, and then re-execute the command:

Does the jpcplist.ini file exist?

Do you have access permission for the jpcplist.ini file?

KAVE05905-E

An attempt to delete temporary files failed. (path)

The files under the folder indicated by path could not be deleted.

(S)

Stops the requested processing.

(O)

Once the command terminates, delete the files under the folder indicated by path, and then re-execute the command.

KAVE05906-I

A new agent (Pfm-Agent-service-key) was added for Manager. (version=version)

The solution set of the PFM - Agent, indicated by Pfm-Agent-service-key, was added to PFM - Manager.

(S)

Continues the requested processing.

KAVE05908-I

New agent setup (Pfm-Agent-service-key) ended successfully. (version=version)

The information about the PFM - Agent, indicated by Pfm-Agent-service-key, was added to the jpcplist.ini file, and the setup processing terminated normally.

(S)

Terminates the requested processing. However, processing continues if all was specified for the service key and unprocessed files remain.

KAVE05912-Q

The instance environment already exists. Do you want to update? (Y/N)

This is a confirmation message asking whether or not the instance environment is to be updated.

(S)

Resumes processing when the response is the uppercase letter Y or the lowercase letter y (1 byte). If the response is a space character or a character other than an uppercase Y or lowercase y, processing is cancelled.

(O)

Enter a response to the command.

KAVE05913-I

The instance environment is being updated. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

The system is updating the instance environment assigned by the service key and instance name.

(S)

Resumes the requested processing.

KAVE05914-I

The instance environment was updated. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

The instance environment assigned by the service key and instance name has been updated.

(S)

Terminates command execution.

KAVE05915-E

The instance environment was not updated. (servicekey=service-key, lhost=logical-host-name, inst=instance-name)

A message indicating the cause was issued before this message.

(S)

Cancels the requested processing.

(O)

Check the previous message for the nature of the error, correct the error, and then re-execute the command.

KAVE05916-I

The service configuration information listing ended normally.

Display of the service configuration information terminated normally.

(S)

Terminates command execution.

KAVE05917-I

The service configuration information definition ended normally.

Definition of the service configuration information terminated normally.

(S)

Terminates command execution.

KAVE05918-W

The specified port number is in use by another service.

An attempt was made to specify a port number that has already been registered for another service.

(S)

Continues the requested processing.

(O)

Check and enter a port number that has not been registered.

KAVE05919-E

The port number is not registered correctly in the services file.

The port number has not been registered correctly in the services file.

(S)

Halts command execution.

(O)

Set the port number correctly with the following procedure:

When <error> is displayed for the Services item in the execution results of the jpcconf port list command

Execute the jpcconf port define command to specify the port number

When <error> is displayed for the Port item in the execution results of the jpcconf port list command

1. Check the services file to determine if the port number resulting in the error is duplicated. If it is, delete it.

2. Execute the jpcconf port define command to specify the port number.

Other

1. Check the services file to determine if the port number for the Name Server service has been registered correctly. If it has not been registered correctly, register the following port number in the services file:

jp1pcnsvr 22285/tcp

2. Execute the jpcconf port define command to specify the port number.

KAVE05920-W

The value 'value' is out of range.

The indicated value is outside the permitted range.

(S)

Resumes the requested processing.

(O)

Check and re-enter the port number.

KAVE05921-W

The processing was cancelled by a user operation.

In response to a prompt, the user requested that processing be stopped.

(S)

Stops the requested processing.

KAVE05922-E

No port number that can be set for the services file exists.

No port number is available that can be set in the services file.

(S)

Stops the requested processing.

(O)

Check the port information registered in the services file, and then re-execute the command.

KAVE05923-W

Characters other than 1 byte characters were entered.

A character string containing characters other than alphanumeric characters and symbols was entered.

(S)

Continues the requested processing.

(O)

Check the entered value, and then enter the correct value.

KAVE05924-W

An invalid character string was entered. (OK word=specifiable-character-string)

A character string that cannot be specified was entered.

(S)

Continues the requested processing.

(O)

Check the entered value, and then enter the correct value.

KAVE05925-W

Invalid characters were entered. (NG word=prohibited-character)

A prohibited character was entered.

(S)

Continues the requested processing.

(O)

Check the entered value, and then enter the correct value.

KAVE05926-W

No input value was entered.

A space or return character alone cannot be specified.

(S)

Continues the requested processing.

(O)

Enter a value other than the following:

Space only

Return character only

KAVE05927-W

The entered value exceeded the maximum length. (maximum length=permitted-input-length-in-bytes)

The entered value exceeds the maximum number of bytes.

(S)

Continues the requested processing.

(O)

Check the maximum length in bytes, and then re-enter.

KAVE05928-W

The entered value was smaller than the minimum value allowed. (minimum value=minimum-input-value)

The entered value is less than the permitted minimum value.

(S)

Continues the requested processing.

(O)

Check the minimum value, and then re-enter.

KAVE05929-W

The entered value was larger than the maximum value allowed. (maximum value=maximum-input-value)

The entered value is greater than the permitted maximum value.

(S)

Continues the requested processing.

(O)

Check the maximum value, and then re-enter.

KAVE05930-W

A non-numerical value was entered.

A non-numerical value was entered.

(S)

Continues the requested processing.

(O)

Re-enter the value as a numerical value.

KAVE05931-W

The re-entered value does not match the previous value.

The re-entered value does not match the previous value.

(S)

Continues the requested processing.

(O)

Re-enter the same value as was entered previously.

KAVE05944-W

The processing to set up the new agent for the Manager will be skipped because a newer version of the agent has already been set up . (servicekey=service-key-of-PFM-Agent, version=version)

Processing to set up the new agent to PFM - Manager will not be performed because the version of the setup archive of PFM - Agent, indicated by service-key-of-PFM-Agent, to be added to PFM - Manager is older than the one included in PFM - Manager. version indicates the version of the archive that was used for the additional setups.

(S)

Skips the additional setups of the agent to PFM - Manager.

(O)

Check the setup archive that was used for the additional setups.

If the archive is appropriate, the agent must have already been set up to PFM - Manager, and you do not need to perform additional setup. If you want to define a report or alarm for the agent before connecting, execute the jpcconf agent setup command with the -register option specified.

KAVE05945-E

The specified option can only be used on a Manager host.

The specified option can only be used on the PFM - Manager host.

(S)

Cancels the command execution.

(O)

Execute the command on the PFM - Manager host.

KAVE05946-I

The agent was registered in the Manager successfully. (servicekey=service-key-of-PFM-Agent)

The specified PFM - Agent was registered in PFM - Manager successfully.

(S)

Continues processing.

KAVE05947-I

The agent was set up for the Manager successfully. (servicekey=service-key-of-PFM-Agent, version=version)

The specified PFM - Agent was set up to PFM - Manager successfully.

(S)

Continues processing.

KAVE05948-E

An attempt to setup the agent for the Manager failed. (servicekey=service-key-of-PFM-Agent, version=version)

An attempt to set up PFM - Agent indicated by service-key-of-PFM-Agent on PFM - Manager has failed. The possible causes are as follows:

The access permissions for the following directories are missing, or there is not enough disk space:

For Windows

installation-folder\mgr\manager\

installation-folder\mgr\viewsvr\

For UNIX

/opt/jp1pc/mgr/manager/

/opt/jp1pc/mgr/viewsvr/

While PFM - Manager has been set up in the logical host environment and is running on the executing node, you do not have permission to access the directories listed below or there is not enough disk space:

For Windows

environment-directory\jp1pc\mgr\manager\

environment-directory\jp1pc\mgr\viewsvr\

For UNIX

environment-directory/jp1pc/mgr/manager/

environment-directory/jp1pc/mgr/viewsvr/

PFM - Manager has been set up in the logical host environment, and it is running on the standby node.

(S)

Cancels processing.

(O)

If PFM - Manager has been set up in the logical host environment and is running on the standby node, re-execute the command on the executing node.

If this message was displayed during the installation, check the following and then re-install PFM - Manager:

Whether you have the permissions to access the directories

Whether there is enough disk space

If you are unable to resolve the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05949-E

An attempt to register the agent into the Manager failed. (servicekey=service-key-of-PFM-Agent)

An attempt to register the specified PFM - Agent to PFM - Manager has failed. The possible causes are as follows:

The specified PFM - Agent is not included in PFM - Manager.

The following files are missing or you do not have the permission to access the files

When operating PFM - Manager on the physical host

For Windows: installation-folder\mgr\manager\setagentlist.ini

For UNIX: /opt/jp1pc/mgr/manager/setagentlist.ini

When operating PFM - Manager on the logical host

For Windows: environment-directory\jp1pc\mgr\manager\setagentlist.ini

For UNIX: environment-directory/jp1pc/mgr/manager/setagentlist.ini

(S)

Cancels processing.

(O)

Check the following, and then re-execute the command:

Whether the specified PFM - Agent has already been set up to PFM - Manager (check the release notes)

Whether the setagentlist.ini file exists

Whether you have permission to access the setagentlist.ini file

If the setagentlist.ini file does not exist, copy and rename the setagentlist.ini.model file as setagentlist.ini, and then re-register the agent to PFM - Manager.

KAVE05950-E

The specified agent is not set up for the Manager. (servicekey=service-key-of-PFM-Agent)

An attempt to register the specified agent to PFM - Manager has failed because the agent has not been set up to PFM - Manager.

(S)

Cancels processing.

(O)

Use the setup archive to perform the additional setups for the agent.

KAVE05951-W

The specified agent is already registered in the Manager. (servicekey=service-key-of-PFM-Agent)

An attempt to register PFM - Agent that has already been registered in PFM - Manager was performed.

(S)

Cancels processing.

KAVE05952-I

The rebuilding of agent registration information for the Manager will now start.

An attempt to reconfigure the agent registration information on PFM - Manager will now start according to the registration information of the agent that has been set up by the jpcconf agent setup command.

(S)

Continues processing.

KAVE05953-I

The rebuilding of agent registration information for the Manager has ended.

Reconfiguring the agent registration information of PFM - Manager according to the registration information of the agent that has been set up by the jpcconf agent setup command on PFM - Manager, has finished.

(S)

Continues processing.

KAVE05954-E

The specified port number is in used by another. (service=service-ID-or-component-name, value=specified-value)

An attempt to specify the port number that has already been registered with another service was performed.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying a port number that is not in use.

KAVE05955-E

The value 'value' is out of range. (service=service-ID-or-component-name)

The value is not in the valid range.

(S)

Cancels the command execution.

(O)

Check the port number, and then re-execute the command.

KAVE05956-I

The synchronization of agent information will now start.

Synchronization of agent information will now start.

(S)

Starts the command execution.

KAVE05957-I

The synchronization of agent information ended normally.

Synchronization of agent information ended normally.

(S)

Terminates command execution.

KAVE05958-E

The synchronization of agent information ended abnormally.

Synchronization of agent information ended abnormally.

(S)

Halts command execution.

(O)

Check the preceding message and take the action indicated in the message.

If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE05959-E

An alarm definition failed to be updated and is in an invalid state. (product id=product-ID, alarm table=alarm-table-name, alarm=alarm-name)

An alarm definition failed to be updated and is in an invalid state. Delete or update the displayed alarm definition again.

product-ID, alarm-table-name, and alarm-name provide information about the invalid alarm definition.

(S)

Cancels command execution.

(O)

An alarm definition is in an invalid state. Delete or update the displayed alarm definition again.

KAVE05960-E

The number of alarms to be bound exceeds the limit. (service=service-ID)

Processing cannot continue because the number of alarms to be bound exceeds the limit.

(S)

Cancels processing.

(O)

Check the argument, and then re-execute the command. If the specified argument is valid, check alarm tables that are bound to the specified service, unbind unnecessary alarm tables, and then re-execute the command.

KAVE05961-E

Alarm table contains alarms of different data model versions. (product id=product-ID, alarm table=alarm-table-name, version1=data-model-version, version2=data-model-version)

Processing cannot continue because the alarm definition file is invalid.

(S)

Cancels command execution.

(O)

Check and, if necessary, revise the data model version specified in the alarm definition file, and then re-execute the command.

KAVE05962-I

The backup of definition information will now start.

Backup of definition information will now start.

(S)

Starts the command execution.

KAVE05963-I

The backup of definition information ended normally.

Backup of definition information ended normally.

(S)

Terminates command execution.

KAVE05964-E

The backup of definition information ended abnormally.

Backup of definition information ended abnormally.

(S)

Halts command execution.

(O)

Check and eliminate the cause of the error, and re-execute the command. For the cause, check the error message that was output immediately before this message.

KAVE05965-E

The current directory is not correct.

The current directory is not correct.

(S)

Halts command execution.

(O)

Move the current directory to the correct location, and then re-execute the command.

KAVE05966-E

An attempt to back up the file failed. (file=file-name)

An attempt to back up the file indicated by file-name failed.

(S)

Continues processing.

(O)

The backup target file might have been updated. Re-execute the command without changing any definitions and configurations. If multiple attempts to execute the command fail, check the manual and manually back up all the definition information.

KAVE05967-E

An attempt to back up agent-specific definition information failed. (product id=product-ID)

An attempt to back up agent-specific definition information failed.

product-ID indicates the product ID of the agent for which backup failed.

(S)

Continues processing.

(O)

Possible causes are as follows:

The capacity of the disk on which the backup target directory resides is insufficient.

The backup target information was updated during command execution.

Eliminate the cause of the error, and re-execute the command. If re-execution of the command fails, check the manual for the agent for which backup failed, and then manually back up the agent-specific definition file.

KAVE05968-E

The specified definition file name is too long.

Processing cannot continue because the specified definition file name was too long.

(S)

Halts command execution.

(O)

Configure the setting so that the file path of the specified definition file will not exceed the limit.

KAVE05969-E

The specified agent cannot bind the alarm table because the agent does not support alarm notifications of state changes for each instance. (serviceid = service-ID, alarm table =alarm-table-name)

An alarm table that includes alarms indicating state changes for individual instances cannot be bound to an agent that does not support the notifications of state changes for each instance.

(S)

Skips the alarm table binding to the agent specified by service-ID, and continues command processing.

(O)

Check the version of the agent to which you want to bind the alarm table, and then re-execute the command.

KAVE05970-E

Alarm definitions cannot be updated because the alarm is bound to an agent that does not support alarm notifications of state changes for each instance. (alarm table = alarm-table-name, alarm = alarm-name)

The notifications of state changes for each instance cannot be enabled because the indicated alarm is bound to an agent that does not support the notifications of state changes for each instance.

(S)

Skips the updating of the alarm, and continues command processing.

(O)

Check the version of the agent.

KAVE05971-E

The process was stopped because the exclusion command was not finished within a set time.

While an alarm command was waiting to be executed, a timeout occurred before the execution of a command that cannot be executed at the same time as the alarm command finished.

For details about the suspension of alarm command execution, see Commands that cannot be executed with alarm commands.

(S)

Halts command execution.

(O)

Re-execute the command.

KAVE05972-W

The process will be started with exclusion command wait functionality disabled because an invalid value is set. (label = label-name, specified value = specified-value)

The process will start with the functionality for suspending the execution of alarm commands disabled because an invalid value is set.

(S)

Disables the functionality for suspending the execution of alarm commands and then continues processing.

(O)

In the file jpccomm.ini, check the relevant labels and setting values.

KAVE05973-W

The process will be started with default wait time because an invalid value is set. (label = label-name, specified value = specified-value)

The process will start with the default wait time for alarm commands because an invalid value is set.

(S)

Specifies the default value for the wait time and then continues processing.

(O)

In the file jpccomm.ini, check the relevant labels and setting values.

KAVE05974-E

The wait time specification is invalid.

An invalid value was specified for the wait time.

(S)

Halts command execution.

(O)

Check the specified wait time, and then re-execute the command.

KAVE06000-I

Backup processing of the Store database terminated normally. (service=service-ID)

Backup processing of the Store database terminated normally.

(S)

Terminates command execution.

KAVE06001-I

Clear processing of the Store database terminated normally. (service=service-id, dbid=database-id)

Clear processing of the Store database terminated normally.

(S)

Terminates command execution.

KAVE06002-I

Dump processing of the Store database terminated normally. (service=service-id, dbid=database-id)

Export processing of the Store database terminated normally.

(S)

Terminates command execution.

KAVE06003-I

List processing of the service information terminated normally.

List processing of the service information terminated normally.

(S)

Terminates command execution.

KAVE06004-I

Delete processing of the service information terminated normally. (service=service-id)

Deletion of the service information terminated normally.

(S)

Terminates command execution.

KAVE06005-I

Register processing of the service information terminated normally. (service=service-id)

Re-registration of the service information terminated normally.

(S)

Terminates command execution.

KAVE06006-I

Restore processing of the Store database terminated normally.

Restore processing of the Store database terminated normally.

(S)

Terminates command execution.

KAVE06007-I

The service will now start. (service=service-name, lhost=logical-host-name, inst=instance-name)

The indicated service is starting.

(S)

Starts the service.

KAVE06008-I

The service will now stop. (service=service-name, lhost=logical-host-name, inst=instance-name)

The indicated service is stopping.

(S)

Stops the service.

KAVE06009-I

The collection of maintenance information will now start.

Collection of maintenance information is beginning.

(S)

Starts command execution.

KAVE06010-I

The collection of maintenance information ended normally.

Collection of maintenance information terminated normally.

(S)

Terminates command execution.

KAVE06011-I

The event was sent normally. (ID=event-id, event-level)

A JP1 event was sent.

(S)

Sent the JP1 event normally.

KAVE06013-I

The file was not found for the specified information.

Archive file was not created because the collection-target file specified by the option does not exist.

(S)

Terminates processing.

(O)

Ensure that the correct collection target is specified.

KAVE06014-I

The creation of indexes will now start. (servicekey=service-key, inst=instance-name, host=host-name)

Creation of an index file has started.

If the service is running on a logical host, lhost=logical-host-name is displayed instead of host=host-name. If the service is a single-instance agent, inst=instance-name is not displayed.

(S)

Starts creation of an index file.

KAVE06015-I

The creation of indexes succeeded. (servicekey=service-key, inst=instance-name, host=host-name)

Creation of an index file was successful.

If the service is running on a logical host, lhost=logical-host-name is displayed instead of host=host-name. If the service is a single-instance agent, inst=instance-name is not displayed.

(S)

Terminates command execution.

KAVE06016-E

An attempt to create indexes failed. (servicekey=service-key, inst=instance-name, host=host-name)

Creation of an index file failed.

If the service is running on a logical host, lhost=logical-host-name is displayed instead of host=host-name. If the service is a single-instance agent, inst=instance-name is not displayed.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE06017-W

Processing will now be skipped because the instance environment does not exist. (service=service-key)

Processing will be skipped because there is no instance environment.

(S)

Continues command execution.

(O)

When this message is output with the jpcspm start command

Set up the instance startup environment, and then re-execute the command.

When this message is output with the jpcspm stop command

Set up the instance startup environment.

KAVE06018-W

Processing will be skipped because the service is in a state in which processing cannot be requested. (service=service-ID, status=status)

Processing will be skipped because the service is in a status in which it cannot process the request.

status displays the service's current status in the same format as is used in the execution results of the jpctool service list command.

(S)

Continues command execution.

KAVE06019-E

When the -stat option is specified, wildcard characters cannot be used in the host name.

When the -stat option is specified, the host name cannot contain a wildcard character.

(S)

Halts command execution.

(O)

Re-execute the command without using a wildcard character in the host name that is specified in the host=host-name option.

KAVE06020-E

Status Server cannot process the request. (host=host-name)

The Status Server service cannot process the request.

(S)

Halts command execution.

(O)

Check if the Status Server service is running at the host displayed as host=host-name.

KAVE06021-W

The detailed information cannot be displayed because Status Server is not running. (host=host-name)

The detailed information cannot be displayed because the Status Server service is not running or connection cannot be established with the Status Server.

(S)

Continues command execution.

(O)

Check if the Status Server service is running at the indicated host. Also, check whether or not a communication connection can be established with that host.

KAVE06022-I

Status Server will not be stopped because a service that relies on Status Server is running.

The Status Server service will not be stopped because a service that depends on the Status Server service is running.

(S)

Terminates command execution.

(O)

If you want to stop the Status Server service, you must first stop all the services except for the Status Server service on the physical and logical hosts on the machine where the command is executed.

Check if there are any currently running services on the physical host or the logical host. If services are running, stop all the services except the Status Server service, and then re-execute the command.

Even when all the services other than the Status Server service have already stopped, this message may still appear depending on when the services stopped.

KAVE06023-E

The specified processing cannot be executed because the status management function is not available.

The specified processing cannot be executed because the status management function has not been set up.

(S)

Halts command execution.

(O)

If the status management function has not been set up, neither the -stat option nor the -stat service can be specified. Set up the status management function, and then re-execute the command.

KAVE06024-E

The processing cannot be continued because the service is in the status of start pending or stop pending.(service=service-name, lhost=logical-host-name, inst=instance-name)

Processing cannot continue because the service is starting or stopping. If the service has already accepted a start or stop request, this message may be displayed, even when the jpcspm start or jpcspm stop command is cancelled. In Windows, this message may be displayed if the jpcspm start or jpcspm stop command is executed while the service is being started or stopped from the Service Control Manager.

(S)

Halts command execution. If you are using the linkage function with PFM - Web Console to manage starting or stopping the PFM - Web Console service, the system only cancels processing of PFM - Web Console.

(O)

Use the jpctool service list command to check that the service has been placed in request wait or stopped status, and then re-execute the command.

KAVE06025-I

The setup of the status management function will now start.

Setup of the status management function is starting.

(S)

Starts setup of the status management function.

KAVE06026-I

An attempt to set up the status management function ended normally.

Setup of the status management function terminated normally.

(S)

Terminates command execution.

KAVE06027-E

The setup of the status management function terminated abnormally.

Setup of the status management function failed.

(S)

Halts command execution.

(O)

Check the error message issued immediately before this message.

KAVE06028-W

The configuration file was not updated because the environment directory was inaccessible.(dir=directory-name)

The configuration file was not updated because the environment directory was not accessible. This message may be displayed if the shared disk containing the environment directory is not mounted or if the command is executed at the standby node.

(S)

Continues the requested processing.

(O)

Make sure that the environment directory is accessible, and then re-execute the command at the executing node.

KAVE06029-I

The port number was successfully registered. (service=service-name, port=port-number)

Registration of a port number in the services file was successful.

(S)

Resumes installation processing.

KAVE06030-W

The port number is duplicated. (service=service-name, port=port-number)

The port number for the service was registered in the service file, but the same port is in use by another service.

(S)

Resumes installation processing.

(O)

If the Performance Management service is running, stop it, and then use the jpcconf port define command to change the port number for the corresponding service.

KAVE06031-E

An attempt to register the port number has failed. (service=service-name, port=port-number)

An attempt to register the port number into the services file failed.

(S)

Cancels installation processing.

(O)

Make sure that the services file can be written, and then reinstall Performance Management.

KAVE06032-E

An attempt to read the NNM linkage definition file (jpcnnm.ini) has failed.

An attempt to read the NNM linkage definition file (jpcnnm.ini) failed.

(S)

Suspends processing.

(O)

Make sure that the NNM linkage definition file is available and accessible, and then re-execute the command.

KAVE06033-E

The syntax in the NNM linkage definition file (jpcnnm.ini) is invalid.

The specification format of the NNM linkage definition file (jpcnnm.ini) is invalid.

(S)

Suspends processing.

(O)

Check the specification format of the NNM linkage definition file, and then re-execute the command.

KAVE06034-E

The definition of the Manager at the connection destination is not set. (host=host-name)

The host name of the Manager that issued an SNMP trap to the NNM linkage definition file (jpcnnm.ini) is not set. In (host=host-name) for Host Name, the PFM - Manager host name that issued an SNMP trap is displayed.

(S)

Interrupts processing.

(O)

Make sure the Manager host at the connection destination is set in the NNM linkage definition file (jpcnnm.ini), and then try again. Note: This message is also output to the Web browser. However, (host=host-name) is not output.

KAVE06035-E

The specified browser path is invalid. (file=browser-path)

An attempt to start the Web browser failed because the specified Web browser path was invalid.

(S)

Suspends processing.

(O)

Check the browser path settings in the NNM linkage definition file (jpcnnm.ini), and then re-execute the command.

KAVE06036-W

The default browser will now start because the specified browser path is invalid. (file=browser-path)

The default browser is being started because the specified Web browser path is invalid

(S)

Starts the default browser.

(O)

Check the browser path settings in the NNM linkage definition file (jpcnnm.ini), and then re-execute the command.

KAVE06037-W

The window to select the Manager is not set up.

The window for selecting the PFM - Manager has not been created.

(S)

Suspends processing.

(O)

Create an HTML file for selecting PFM - Manager by executing the following command:

jpcconf ov enable -mkhtml

KAVE06038-E

An attempt to display a report has failed.

The report and login windows cannot be displayed because Web browser startup failed.

(S)

Stops the requested processing.

(O)

Check and, if necessary, revise the NNM linkage facility customization procedure. If the cause cannot be determined, collect maintenance information, and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE06039-E

An attempt to update the status of an object has failed. (msg=NNM-error-message)

An attempt to update the status of an object in the NNM object database failed. An NNM error message is displayed in NNM-error-message.

(S)

Cancels updating of the target object's status.

(O)

Eliminate the cause of the error based on the displayed NNM error message. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVE06040-E

An attempt to start the administrator console has failed.

An attempt to start the administrator console has failed.

(S)

Stops the administrator console.

(O)

Check the error message that was output prior to this message. If you are unable to resolve the problem, start another command prompt that is run by administrator permissions, execute the jpcras command to collect information, and then contact the system administrator.

KAVE06041-E

The user doesn't have Administrator right to start Administrator Console.

The administrator console cannot be started by a user who does not have administrator permissions.

(S)

Stops the administrator console.

(O)

Start the console with administrator permissions.

KAVE06046-W

The service ID is displayed because the product ID could not be recognized. (product id=product-ID)

The service ID is displayed because the product ID indicated by product-ID could not be recognized.

(S)

Continues the command execution.

(O)

To display in user-friendly format, register the agent that is indicated by product-ID by executing the jpcconf agent setup command on the command execution host.

KAVE06047-I

Setup of the product name display functionality will now start. (host=host-name)

Setup of the product name display functionality will now start. host-name indicates the name of the host to which the setup of product name display functionality will be performed.

(S)

Starts the setup of the product name display functionality.

KAVE06048-I

Setup of the product name display functionality ended normally. (host=host-name)

Setup of the product name display functionality ended normally. host-name indicates the name of the host to which the setup of the product name display functionality has been performed.

(S)

Ends the setup of the product name display functionality.

KAVE06049-E

Setup of the product name display functionality ended abnormally. (host=host-name)

Setup of the product name display functionality ended abnormally. host-name indicates the name of the host to which the setup of the product name display functionality has been performed.

(S)

Cancels the setup of the product name display functionality.

(O)

Check the message that was output prior to this message, and follow the instructions given in the message. If you are unable to determine the cause of the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE06050-I

Setup of the monitoring product type extension will now start. (host=host-name)

Setup of the function for extending the types of monitored products will now start. host-name indicates the name of the host to which the setup of the function for extending the types of monitored products will be performed.

(S)

Starts the setup of the function for extending the types of monitored products.

KAVE06051-I

Setup of the monitoring product type extension ended normally. (host=host-name)

Setup of the function for extending the types of monitored products ended normally. host-name indicates the name of the host to which the setup of the function for extending the types of monitored products has been performed.

(S)

Ends the setup of the function for extending the types of monitored products.

KAVE06052-E

Setup of the monitoring product type extension ended abnormally. (host=host-name)

Setup of the function for extending the types of monitored products ended abnormally. host-name indicates the name of the host to which the setup of the function for extending the types of monitored products has been performed.

(S)

Cancels the setup of the function for extending the types of monitored products.

(O)

Check the message that was output prior to this message, and follow the instructions given in the message. If you are unable to determine the cause of the problem, collect maintenance information and then contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE06053-E

The specified target name is invalid.

The specified target name is invalid.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the valid target name.

KAVE06054-E

The target is not specified.

The target name is not specified properly.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the target name properly.

KAVE06055-E

The specified operation name is invalid.

The specified operation name is invalid.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the valid operation name.

KAVE06056-E

The operation has not been specified.

The operation name is not specified properly.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the operation name properly.

KAVE06057-E

The Web Console service could not start. (lhost=logical-host-name,rc=maintenance-code,msg="stderr-of-PFM-Web Console")

An attempt to start the Web Console service has failed.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Eliminate the cause of the problem, and then re-execute the command. For the cause, check the error message that was output to the common message log or the PFM - Web Console log.

KAVE06058-E

The Web Console service could not be stopped. (lhost=logical-host-name,rc=maintenance-code,msg="stderr-of-PFM-Web-Console")

An attempt to stop the Web Console service has failed.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels termination of the Web Console service.

(O)

Eliminate the cause of the problem, and then re-execute the command. For the cause, check the error message that was output to the common message log or the PFM - Web Console log.

KAVE06059-E

A Web Console service does not exist for the specified host name. (lhost=host-name)

PFM - Web Console that is running on the specified host does not exist.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the host on which PFM - Web Console is running.

If PFM - Web Console is running on the physical host, execute the command without specifying lhost.

KAVE06060-E

A Web Console service does not exist on the physical host name.

PFM - Web Console that is running on the physical host does not exist.

(S)

Cancels the command execution.

(O)

Re-execute the command by specifying the host on which PFM - Web Console is running.

KAVE06061-E

The PFM - Web Console environment is invalid.

The PFM - Web Console environment is invalid.

(S)

Cancels the starting, stopping, or displaying of information of the Web Console service.

(O)

Collect the information about PFM - Web Console, and then contact the system administrator or support service.

KAVE06062-E

A PFM - Web Console which can be linked does not exist.

PFM - Web Console that can be linked does not exist.

(S)

Cancels the command execution.

(O)

Make sure that the version of PFM - Web Console supports the linkage function.

If the version supports the function, perform the linkage settings on PFM - Web Console, and then re-execute the command.

KAVE06063-E

Processing of the Web Console service information ended abnormally. (lhost=logical-host-name,rc=maintenance-code,msg="standard-error-output-of-PFM-Web-Console")

Processing of displaying the Web Console service information ended abnormally.

lhost=logical-host-name will not be displayed for the service for starting the physical host.

(S)

Cancels the command execution.

(O)

Eliminate the cause of the problem, and then re-execute the command. For the cause, check the error message that was output prior to this message or the PFM - Web Console log.

KAVE06064-E

the specification of the value is incorrect. (option=option-name, value=value)

Processing of displaying the Web Console service information ended abnormally.

(S)

The specified value is invalid.

(O)

Re-execute the command by specifying the valid value.

KAVE06065-W

Remote Agent and Group Agent could not be displayed because a connection with Master Manager could not be established.

Information about Remote Agent and Group Agent could not be displayed because Master Manager is not running or could not be connected to.

(S)

Continues the command execution.

(O)

Make sure that Name Server and Master Manager are running, or they are not in busy status. Also, make sure that a connection to the Manager host can be established.

KAVE06066-E

The monitoring product type extension cannot be disabled because dependent service information is registered. (host=host-name)

The function for extending the types of monitored products could not be disabled because service information that requires the function has been registered.

(S)

Cancels the command execution.

(O)

If the function for extending the types of monitored products is disabled, services that require the function can no longer be used. Before disabling the function, stop the services, delete the information about the services, and then re-execute the command. To delete the service information, use the jpctool service delete command. For details about the command, see 2. Commands.

KAVE06067-E

An attempt to acquire the Web Console service information failed.

An attempt to acquire the Web Console service information has failed.

(S)

Cancels the starting, stopping, or displaying of information of the Web Console service.

(O)

Eliminate the cause of the problem, and then re-execute the command. For the cause, check the error message that was output prior to this message or the PFM - Web Console log.

KAVE06069-E

The specification of the directory is incorrect. (dir=directory-name)

The specification of the directory is incorrect.

(S)

Halts command execution.

(O)

Specify the correct directory, and then re-execute the command.

KAVE06071-I

The agents tree will now be imported.

The Agents tree will now be imported.

KAVE06072-I

The agents tree will now be exported.

The Agents tree will now be exported.

KAVE06073-I

The existing agents tree will be updated.

The Agents tree already exists for the specified user. This message corresponds to the KAVE06076-Q message. This occurred in query suppression mode, so the Agents tree will be updated and processing will continue.

(S)

Updates the Agents tree and continues processing.

KAVE06074-I

The agents tree was successfully imported.

The Agents tree was successfully imported.

KAVE06075-I

The agents tree was successfully exported.

The Agents tree was successfully exported.

KAVE06076-Q

Would you like to overwrite the agents tree? (Y/N)

This is a confirmation message asking whether or not you wish to overwrite the Agents tree.

(S)

Waits for a response.

(O)

Enter Y or y if you want to overwrite the Agents tree. Enter other characters if you do not want to do so.

KAVE06077-E

Importing of the agents tree was cancelled.

An attempt to import the Agents tree failed.

(S)

Terminates the command.

(O)

Check the preceding message and take the action indicated in the message.

If the cause cannot be determined, collect maintenance information and contact the system administrator.

For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE06078-E

Exporting of the agents tree was cancelled.

An attempt to export the Agents tree failed.

(S)

Terminates the command.

(O)

Check the preceding message and take the action indicated in the message.

If the cause cannot be determined, collect maintenance information and contact the system administrator.

For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVE06079-E

The specified agent does not exist. (agent=agent-name, line=line-number)

The specified agent does not exist in the specified definition file.

(S)

Suspends processing.

(O)

Make sure that the agent is correctly specified.

If you want to import a non-existent agent, specify the -nocheck option.

KAVE06080-E

An attempt to communicate with View Server failed. (maintenance information=maintenance-information)

The View Server service is not running.

(S)

Suspends processing.

(O)

Check whether the View Server service is running.

KAVE06081-E

The number of folders that can be directly under the root exceeds the maximum. (maximum=maximum-value, line=line-number)

The number of folder nodes that can be defined directly under the root node exceeds the maximum value.

(S)

Suspends processing.

(O)

Reduce the number of folders to no more than the maximum value, and then restart processing.

KAVE06082-E

The number of agents that can be directly under the root exceeds the maximum. (maximum=maximum-value, line=line-number)

The number of agent nodes that can be defined directly under the root node exceeds the maximum value.

(S)

Suspends processing.

(O)

Reduce the number of agents to no more than the maximum value, and then restart processing.

KAVE06083-E

An unexpected error occurred. (maintenance information=maintenance-information)

An unexpected error occurred during processing.

(S)

Suspends processing.

(O)

Collect maintenance information and contact the system administrator.

KAVE06084-E

The specified user was not found. (user name=user-name)

User information about the specified user name cannot be acquired.

(S)

Suspends processing.

(O)

Check whether the specified user exists. Also, if the JP1 authentication mode is used, check whether a connection to the authentication server can be established.

KAVE06085-E

An attempt to read the file failed. (file=file-name, maintenance information=maintenance-information)

An error occurred when reading a file.

(S)

Suspends processing.

(O)

Check the status of the file.

KAVE06086-E

A folder with the same name is already defined. (folder=folder-name, line=line-number)

A folder with the same name is already defined in a folder.

(S)

Suspends processing.

(O)

Change the folder name, and then restart processing.

KAVE06087-E

An agent with the same name is already defined. (agent=agent-name, line=line-number)

An agent with the same name is already defined in a folder.

(S)

Suspends processing.

(O)

Restart processing.

KAVE06088-E

The manager is not running on the specified logical host.

The Manager is not running on the specified logical host.

(S)

Halts command execution.

(O)

Check whether the Manager is running on the specified logical host.

If a physical host is used, do not specify the -lhost option.

KAVE06089-E

A syntax error was found while the file was being read. (file=file-name, line=line-number)

A syntax error was detected while the definition file was being read.

(S)

Suspends processing.

(O)

Check and, if necessary, revise the contents of the definition file.

KAVE06090-E

A specified parameter is invalid. (tag name=tag-name, parameter=parameter-name, value=value, line=line-number)

The format of the value specified for the parameter-name parameter of the tag-name tag is invalid.

(S)

Suspends processing.

(O)

Set the value according to the parameter format, and then restart processing.

KAVE06091-E

The number of folder levels in the agents tree exceeds the maximum. (folder=folder-name, maximum=maximum-value, line=line-number)

The number of folder levels specified in the definition file exceeds the maximum value.

(S)

Suspends processing.

(O)

Reduce the number of folder levels to no more than the maximum value, and then restart processing.

KAVE06092-E

The number of folders that can be directly under a folder exceeds the maximum. (folder=folder-name, maximum=maximum-value, line=line-number)

The number of folder nodes that can be defined directly under a folder node exceeds the maximum value.

(S)

Suspends processing.

(O)

Reduce the number of folders to no more than the maximum value, and then restart processing.

KAVE06093-E

The number of agents that can be directly under a folder exceeds the maximum. (folder=folder-name, maximum=maximum-value, line=line-number)

The number of agent nodes that can be defined directly under a folder node exceeds the maximum value.

(S)

Suspends processing.

(O)

Reduce the number of agent nodes to no more than the maximum value, and then restart processing.

KAVE06094-E

The agent of a product that PFM - Manager cannot recognize has been specified. (agent=agent-name, line=line-number)

The agent of a product that has not been registered in the system has been specified.

(S)

Suspends processing.

(O)

Check whether the agent name is correctly specified. If it is correctly specified, register PFM - Agent or PFM - RM.

KAVE06095-E

The format of the user name is invalid. (user name=user-name)

The format of the user name specified as an argument is invalid.

(S)

Suspends processing.

(O)

Check whether the user name is correctly specified.

KAVE06096-E

An attempt to output the file failed. (file=file-name, maintenance information=maintenance-information)

An error occurred while the file was being output.

(S)

Suspends processing.

(O)

Check the file status.

KAVE06097-E

The system environment is invalid. (maintenance information=maintenance-information)

The system environment is invalid. A system file was deleted illegally or its access permission was changed.

(S)

Suspends processing.

(O)

Reinstall Performance Management.

KAVE06098-E

The specified DTD is invalid.

The DTD specified in the DOCTYPE declaration is invalid.

(S)

Suspends processing.

(O)

Check whether DTD is correctly specified.

KAVE06117-I

Synchronization of configuration information will now start.

The synchronization of configuration information will be started.

(S)

Starts execution of the command.

KAVE06118-I

Synchronization of configuration information ended normally.

The synchronization of configuration information ended normally.

(S)

Terminates execution of the command.

KAVE06119-E

Synchronization of configuration information ended abnormally.

The synchronization of configuration information ended abnormally.

(S)

Cancels execution of the command.

(O)

Eliminate the cause of the abnormal end, and then re-execute the command. To find the cause, check the messages output before this message.

KAVE06120-I

Synchronization of all services succeeded.

The synchronization of all services succeeded.

(S)

Continues processing.

KAVE06121-W

A service exists that could not be synchronized because it does not support synchronization.

A service could not be synchronized because the service does not support synchronization.

(S)

Continues processing.

(O)

Restart the service that is listed in the syncresult.csv file as the one for which synchronization failed.

KAVE06122-W

A host exists that could not be synchronized because the status management function is disabled or is not supported.

A host could not be synchronized because the status management function was disabled on the host or is not supported by the host.

(S)

Continues processing.

(O)

Restart the services running on the host that is listed in the syncresult.csv file as the one for which synchronization failed. The services that are not running will be synchronized when they start.

KAVE06131-E

The command to synchronize configuration information is being executed.

You cannot execute multiple jpctool config sync commands concurrently.

(S)

Cancels execution of the command.

KAVE06132-I

Judgment of the synchronization results will now start.

The evaluation of synchronization results will be started.

(S)

Continues processing.

KAVE06133-I

Judgment of the synchronization results ended normally.

The evaluation of synchronization results ended normally.

(S)

Continues processing.

KAVE06134-W

Judgment of the synchronization results failed.

The evaluation of synchronization results failed because of a timeout.

(S)

Continues processing.

(O)

Restart the service that is listed in the syncresult.csv file as the one for which synchronization failed.

KAVE06135-E

The multiple monitoring function is disabled.

The specified processing cannot be executed because the multiple monitoring function is disabled.

(S)

Cancels execution of the command.

(O)

Check the multiple monitoring settings, and then re-execute the command.

KAVE06136-I

Export of the multiple monitoring definitions will now start.

The export of multiple monitoring definitions will be started.

(S)

Starts execution of the command.

KAVE06137-I

Export of the multiple monitoring definitions ended normally.

The export of multiple monitoring definitions ended normally.

(S)

Terminates execution of the command.

KAVE06138-E

Export of the multiple monitoring definitions ended abnormally.

The export of multiple monitoring definitions ended abnormally.

(S)

Cancels execution of the command.

(O)

Eliminate the cause of the abnormal end, and then re-execute the command. To find the cause, check the messages output before this message.

KAVE06139-I

Import of the multiple monitoring definitions will now start.

The import of multiple monitoring definitions will be started.

(S)

Starts execution of the command.

KAVE06140-I

Import of the multiple monitoring definitions ended normally.

The import of multiple monitoring definitions ended normally.

(S)

Terminates execution of the command.

KAVE06141-E

Import of the multiple monitoring definitions ended abnormally.

The import of multiple monitoring definitions ended abnormally.

(S)

Cancels execution of the command.

(O)

Eliminate the cause of the abnormal end, and then re-execute the command. To find the cause, check the messages output before this message.

KAVE06142-E

The specified definition differs from the PFM - Manager definition. (definition-information-name)

The specified definition information differs from that of the import-destination PFM - Manager.

(S)

Cancels execution of the command.

(O)

Check and eliminate the cause of the error, and then re-execute the command.

KAVE06143-I

Import of the definitions will now start. (config=definition-information-type)

The import of definition information will be started.

(S)

Starts the import of definition information.

KAVE06144-I

Import of the definitions ended normally. (config=definition-information-type)

The import of definition information ended normally.

(S)

Ends the import of definition information normally.

KAVE06145-I

The primary PFM - Manager settings were successfully specified.

The PFM - Manager on the command execution host was successfully set as the primary PFM - Manager.

(S)

Continues processing.

KAVE06146-E

An attempt to set up the primary PFM - Manager failed.

The PFM - Manager on the command execution host could not be set as the primary PFM - Manager.

(S)

Cancels execution of the command.

(O)

Check whether the Status Server service is running on the command execution host. After making sure that the service is running, re-execute the command.

KAVE06147-I

The program will now start notifying hosts of the primary host name.

The notification of the primary host name to all the hosts in the PFM system will be started.

(S)

Continues processing.

KAVE06148-I

The program has finished notifying hosts of the primary host name.

The notification of the primary host name to all the hosts in the PFM system ended.

(S)

Terminates execution of the command.

KAVE06149-E

The program failed to notify all hosts of the primary host name. (host=host-name)

The notification of the primary host name to the host indicated by host-name failed.

(S)

Continues processing.

(O)

Execute the jpcconf mgrhost define -shift command on the host indicated by host-name, or re-execute the jpcconf primmgr notify command.

KAVE06150-I

The program successfully notified all hosts of the primary host name.

The notification of the primary host name to all the hosts in the PFM system succeeded.

(S)

Continues processing.

KAVE06151-W

The program failed to notify at least one host of the primary host name.

The notification of the primary host name to at least one host failed.

(S)

Continues processing.

(O)

Execute the jpcconf mgrhost define -shift command on the host for which Failure is output in the primnotifyresult.csv file, or re-execute the jpcconf primmgr notify command.

KAVE06152-E

A command to notify hosts of the primary host name is being executed.

The command used to notify hosts of the primary host name is now running. You cannot execute multiple jpcconf primmgr notify commands concurrently.

(S)

Cancels execution of the command.

(O)

Wait until the command used to notify hosts of the primary host name terminates, and then re-execute the command if necessary.

KAVE06154-E

The name of the export directory is invalid.

The specified export directory name is longer than the set limit or has an invalid format.

(S)

Cancels execution of the command.

(O)

Check the export directory name.

KAVE06155-E

An attempt to export the file failed. (file=file-name)

The export of the file indicated by file-name failed.

(S)

Cancels execution of the command.

(O)

The export target might have been changed. Without changing definitions and configuration, re-execute the command.

KAVE06157-E

An attempt to switch the connecting host failed.

Switching the host connected to the command execution host between the primary and secondary hosts failed.

(S)

Cancels execution of the command.

(O)

Restart the PFM service on the command execution host. Otherwise, restore the primary or secondary setting of the connected PFM - Manager host, make sure that the Status Server service is running on the command execution host, and then restart the command.

KAVE06158-E

The specified definition is invalid.

The definition information specified by the argument has an invalid content.

(S)

Cancels execution of the command.

(O)

Re-execute the jpctool config mgrexport command to export the definition information. Do not change the content of the exported definition information.

KAVE06159-E

An attempt to analyze to system file failed. (file=file)

The analysis of a system file failed.

(S)

Cancels execution of the command.

(O)

Collect maintenance information, and then contact the system administrator.

KAVE06160-E

The command cannot be executed because the PFM - Manager is not the primary Manager.

The command cannot be executed because the PFM - Manager host is not the primary host.

(S)

Cancels execution of the command.

(O)

Log in to the primary PFM - Manager host, and then re-execute the command.

KAVE06161-E

The new host name has already been specified for the primary or secondary Manager at the connection destination. (newhost =host-name)

The command cannot be executed because the new host name has already been set as the primary or secondary host name of the connection destination Manager host.

(S)

Cancels execution of the command.

(O)

Change the new host name so that it differs from the primary or secondary host name of the connection destination Manager host, and then re-execute the command. Alternatively, change the primary or secondary host name of the connection destination Manager host, and then re-execute the command.

KAVE06171-E

The specified directory name is invalid (dir = directory-name)

The specified directory name is invalid.

(S)

Halts command execution.

(O)

Check the specified directory name, and then re-execute the command.

KAVE06172-W

The logical host settings information cannot be output because the execution was performed in the standby host.

The logical host settings information cannot be output because the command was executed on the standby host.

(S)

Continues processing.

(O)

To output the logical host settings information, execute the command on the active host.

KAVE06173-I

Output to the settings file will now start.

Output to the settings file will now start.

(S)

Continues processing.

KAVE06174-I

Output to the settings file ended normally.

Output to the settings file ended normally.

(S)

Terminates processing.

KAVE06175-E

Output to the settings file terminated abnormally.

Output to the settings file terminated abnormally.

(S)

Terminates processing.

(O)

Check the cause of the error, and then re-execute the command. For details about the cause of the error, check the error message that was output immediately before this message.

KAVE06176-E

The function to temporarily suspend monitoring is disabled.

The monitoring suspension function is disabled.

(S)

Suspends processing.

(O)

Enable the function for temporarily suspending monitoring, and then re-execute the command.

KAVE06177-E

The specified host does not exist. (host = host-name)

The specified host does not exist.

(S)

Suspends processing.

(O)

Specify the correct host name, and then re-execute the command. If you want to specify the name of a host that does not exist, specify the force option, and then re-execute the command.

KAVE06178-E

Monitoring of the specified service cannot be temporarily suspended.

The specified service is invalid.

(S)

Suspends processing.

(O)

Check the -id option of the commands for the monitoring suspension function (the commands that begin with jpctool monitor).

KAVE06180-I

The monitoring suspension function was successfully set and the monitoring status was successfully displayed.

The monitoring suspension function was successfully set and the monitoring status was successfully displayed.

(S)

Terminates command execution.

KAVE06181-Q

Monitoring of the displayed host or agent will resume. Do you want to continue? (Y/N)

Monitoring will resume on the displayed target.

(S)

Resumes monitoring on the displayed target if the response is Y or y. If the response is a space character or a character string other than an uppercase Y or a lowercase y, command execution is stopped.

(O)

Confirm whether to resume monitoring.

KAVE06182-Q

Monitoring on the displayed host or agent will be suspended. Do you want to continue? (Y/N)

Monitoring on the displayed target will be suspended.

(S)

Suspends monitoring on the displayed target if the response is Y or y. If the response is a space character or a character string other than an uppercase Y or lowercase y, command execution is stopped.

(O)

Confirm whether to suspend monitoring.

KAVE06183-I

The settings information for the monitoring suspension function on the monitoring manager was successfully updated.

The settings information for the monitoring suspension function on the monitoring manager was successfully updated.

(S)

Terminates command execution.

KAVE06184-E

The specified business group or target host does not exist. (group = business-group-name)

The specified business group or target host does not exist.

(S)

Halts command execution.

(O)

Make sure the specified business group and the command target host in the business group exist, and then re-execute the command.

KAVE06185-E

Failed to update the settings information for the monitoring suspension function on the monitoring manager.

Update of the settings information for the monitoring suspension function on the monitoring manager failed.

(S)

Suspends processing.

(O)

Check the cause that was output in the common message log.

KAVE06186-I

The settings information for the monitoring suspension function on the monitoring agent was successfully updated.

The settings information for the monitoring suspension function on the monitoring agent was successfully updated.

(S)

Terminates command execution.

KAVE06187-W

A monitoring agent did not respond when the settings information for the monitoring suspension function was updated.

A host or service whose monitoring status is unknown exists.

(S)

Continues command execution.

(O)

Check whether the service to which an asterisk (*) is appended is running. If the service is not running or the service is in stand-alone mode, no action needs to be taken, because the monitoring status is established when the service starts or when the service switches to normal mode. If the service to which an asterisk (*) is appended is running, check the communication status, and then re-execute the command to suspend or resume monitoring.

KAVE06188-W

Failed to update the settings information for the monitoring suspension function on the monitoring agent.

Update of the settings information for the monitoring suspension function on the monitoring agent failed.

(S)

Terminates command execution.

(O)

Check the status of the monitoring agent. If the failure is due to a temporary communication error, re-execute the command or restart the monitoring agent to apply the settings for suspending or resuming monitoring. You do not need to take action if the host is stopped according to schedule for reasons such as maintenance.

KAVE06189-W

Failed to update the settings information for the monitoring suspension function on the monitoring agent. (host = host-name, service ID = service-ID)

Update of the settings information for the monitoring suspension function on the agent host failed.

(S)

Terminates command execution.

(O)

Check the cause that was output in the common message log.

KAVE06190-W

Deletion of the settings information file for the monitoring suspension function has failed. Please delete it manually. (file = file-name)

Deletion of the settings information file for the monitoring suspension function failed. Delete the file manually.

(S)

Continues processing.

(O)

Manually delete the file that was output to the message.

KAVE06191-I

Monitoring will resume.

Monitoring will resume.

(S)

Continues processing.

KAVE06192-I

Monitoring was successfully resumed.

Monitoring was successfully resumed.

(S)

Terminates processing.

KAVE06193-I

Monitoring will be suspended.

Monitoring will be suspended.

(S)

Continues processing.

KAVE06194-I

The suspension of monitoring was successful.

Monitoring was successfully suspended.

(S)

Terminates processing.

KAVE07000-E

This function is not supported.

An attempt was made to use a function that is not supported by the ODBC driver.

(S)

Terminates with an error.

(O)

Check the functions supported by the ODBC driver.

KAVE07001-E

Server request error: cause

An error occurred during query processing.

(S)

Suspends processing.

(O)

Refer to the cause that is indicated in the message and resolve the problem.

KAVE07002-E

SQL syntax error: invalid table name: 'table-name'.

The specified table name cannot be used.

(S)

Suspends processing.

(O)

Check the table name.

KAVE07003-I

The connection information is insufficient.

The ODBC connection character string is missing necessary information. Dialog cannot be continued because prompting is prohibited.

(S)

Suspends processing.

(O)

Add the necessary information.

KAVE07004-E

Reentry error: The function is already executing.

A lock is in effect.

(S)

Suspends processing.

(O)

Execute the command again.

KAVE07005-E

The data source cannot be registered in the registry.

Setting of the data source failed.

(S)

Suspends processing.

(O)

Make sure that you have the Performance Management administrator user permission.

KAVE07006-E

SQL syntax error: 'cause' near 'token-2'

The specified syntax contains an error. The cause is located near Token 2.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07007-E

SQL syntax error: unknown column 'column-name'.

The indicated column cannot be used.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07008-E

A network error has occurred during the building of the dictionary: cause

A network error occurred.

(S)

Suspends processing.

(O)

Check and, if necessary, revise the network environment.

KAVE07009-W

A network error has occurred during the obtaining of the dictionary for 'product-name': cause

A network error occurred while the indicated product's database definition information was being obtained.

(S)

Suspends processing.

(O)

Check and, if necessary, revise the network environment.

KAVE07010-E

SQL syntax error: column 'column-name' not in specified table(s).

The syntax contains an error.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07011-E

SQL syntax error: ambiguous column reference: 'expression'.

The syntax contains an error.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07012-E

SQL syntax error: incompatible types used in expression in column 'column-name'.

The syntax contains an error.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07013-E

SQL syntax error: no key column specified in selection list.

The specified operation requires a key column.

(S)

Suspends processing.

(O)

Add at least one of the following key columns to the selection list:

record-ID_RECORD_TYPE

record-ID_DATETIME

record-ID_DATE

record-ID_TIME

record-ID_DEVICEID

record-ID_PRODID

record-ID_PROD_INST

record-ID_DRAWER_TYPE

KAVE07014-E

Memory became insufficient.

A memory allocation failure occurred.

(S)

Suspends processing.

(O)

Check the system environment.

KAVE07015-E

SQL syntax error: invalid date/time/timestamp value: 'value'.

A date/time value is invalid.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07016-E

The data source name 'data-source-name' contains invalid characters.

A data source name contains invalid characters.

(S)

Suspends processing.

(O)

Correct the data source name.

KAVE07018-E

The instance name suffix contains invalid characters.

An instance name suffix contains invalid characters.

(S)

Suspends processing.

(O)

Correct the instance name suffix.

KAVE07019-E

The description contains invalid characters.

A description contains invalid characters.

(S)

Suspends processing.

(O)

Correct the description.

KAVE07020-E

The requested function requires read/write access and the database is read-only.

A database-updating request was received, but this is a read-only database.

(S)

Suspends processing.

(O)

Change the processing so that only reading is performed on the database.

KAVE07021-E

The 'value' value is out of range.

The indicated value is outside the supported range.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07022-W

The option was changed.

A data source setting was modified.

(S)

Modifies the ODBC setting and continues processing.

(O)

No action is required.

KAVE07024-E

The cursor position is invalid.

Invalid cursor operation.

(S)

Suspends processing.

(O)

Correct the cursor operation.

KAVE07025-W

The 'column' column was truncated.

A character string was truncated because it was too long.

(S)

Truncates data.

(O)

Check the processing.

KAVE07026-E

An invalid conversion was requested for the 'column' column.

An invalid type conversion was requested for the indicated column.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07027-E

Division by zero was detected during expression processing.

Division by zero was detected while the expression was being processed.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07028-E

An invalid date/time/timestamp operation was detected during expression processing.

A date operation is invalid.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07030-E

SQL syntax error: column 'column-name' is not available for real-time requests.

The indicated column cannot be used.

(S)

Suspends processing.

(O)

Correct the syntax.

KAVE07031-E

An error occurred in reading JPCNS.INI: error-cause

Loading of the settings file failed.

(S)

Suspends processing.

(O)

Check the Performance Management settings. Also, check whether the environment variables are set up.

KAVE07032-E

An error occurred in reading the definition file.

Accessing the product definition file failed.

(S)

Suspends processing.

(O)

Check the Performance Management settings. Also, check whether the environment variables are set up.

KAVE07033-E

The PQL trace file is invalid.

The specified file name is invalid.

(S)

Suspends processing.

(O)

Check the file name, output destination folder, and access permission.

KAVE07999-E

SQL parser failure. message

An internal error occurred during SQL parsing.

(S)

Suspends processing.

(O)

Refer to the text indicated by message and correct the cause of the error. If the error cannot be corrected, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVJA0001-E

<installDir> is not correctly specified in the system properties file.

The <installDir> is set by the installer, so the user cannot modify this statement.

(S)

Suspends processing.

(O)

Reinstall the application.

KAVJA0002-E

The directory specified for the value of <installDir> in the system properties file does not exist.

Path name: specified-installation-directory

The <installDir> is set by the installer, so the user cannot modify this statement.

(S)

Suspends processing.

(O)

Reinstall the application.

KAVJA0003-E

The value of <installDir> in the system properties file is not a directory.

Path name: specified-installation-directory

The <installDir> is set by the installer, so the user cannot modify this statement.

(S)

Suspends processing.

(O)

Reinstall the application.

KAVJA0004-E

An attempt to access the directory specified by <installDir> in the system properties file failed.

Path name: specified-installation-directory

The logged-in user does not have permission to read the directory.

(S)

Suspends processing.

(O)

Make sure that the permission settings to access this directory are correct.

KAVJA0005-E

During the initialization, a memory shortage occurred.

Maintenance information:maintenance-information

It is impossible for the server to allocate enough memory.

(S)

Suspends processing.

(O)

Stop unnecessary applications and close unused windows to increase available memory.

KAVJA0006-E

The initialization of the logging function failed.

Maintenance information:maintenance-information

Initialization of the logging function failed.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJA0007-E

The path to the initialization information file is not set in the java execution environment.

The path to the initialization information file is not specified in the Java system environment.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJA0008-E

The specified initialization information file of the java execution environment was not found.

Path name: file-path

The initialization information file specified in the Java system environment was not found.

(S)

Suspends processing.

(O)

Reinstall the application.

KAVJA0009-E

The specified initialization information file of the java execution environment is not a file.

Path name: file-path

The initialization information file name specified in the Java system environment is not for a file.

(S)

Suspends processing.

(O)

Reinstall the application.

KAVJA0010-E

An attempt to read the specified initialization information file of the java execution environment failed because of a lack of permission.

Path name: file-path

An attempt to read the initialization information file specified in the Java system environment failed because there is no read permission for that file.

(S)

Suspends processing.

(O)

Make sure that the logged-in user has the required permission to read the initialization file.

KAVJA0011-E

A severe error due to an invalid configuration was detected while the configuration file was being read.

Path name: file-path

The cause of this error is indicated by the details that follow the message text.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJA0012-E

A syntax error was found while the configuration file was being read.

Path name: file-path

Line: line-number

The cause of this error is indicated by the details that follow the message text.

(S)

Suspends processing.

(O)

Modify the line in the parameter file to remove the invalid specification, and then retry.

KAVJA0013-E

An error was detected during the reading of the configuration file.

Path name: file-path

The cause of this error is indicated by the details that follow the message text.

(S)

Suspends processing.

(O)

Modify the line in the parameter file to remove the invalid specification, and then retry.

KAVJA0014-E

An error was detected while a process was terminating.

Maintenance information:maintenance-information

An error was detected during process termination.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJA0015-E

An I/O error occurred during the reading of the file.

Path name: file-path

Error information: error-information

An I/O error was detected while the file was being read.

(S)

Suspends processing.

(O)

Remove the error cause and then retry.

KAVJA0016-E

A directory referenced during system initialization does not exist.

Maintenance information = maintenance-information

The directory does not exist.

(S)

Suspends processing.

(O)

Confirm that the directory exists, and try again.

KAVJA0017-E

Access permissions for a directory referenced during system initialization are unavailable.

Maintenance information = maintenance-information

The directory cannot be accessed because read permissions are not available.

(S)

Suspends processing.

(O)

Confirm that the access permission settings for this directory are correct.

KAVJA2501-E

An attempt to read the message file has failed.

File name: message-file-name

The file will not be read.

An error occurred during reading of a multiple language message file.

(S)

Skips processing.

(O)

Make sure that the contents of the file are correct, and then restart the service.

KAVJA4001-E

An internal inconsistency was detected during the initialization.

Maintenance information: maintenance-information

An internal conflict was detected during initialization.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJA4002-E

An unexpected error occurred during initialization.

Module name: module-name

Maintenance information: maintenance-information

An unexpected error occurred during initialization.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJA4003-E

An attempt to read the message resource file failed.

File name: file-name

Maintenance information: maintenance-information

A read error occurred for the message resource file.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJA5004-I

The termination process has completed.

Process termination processing has been completed.

(S)

Completes process termination processing.

KAVJF2501-E

An unexpected error occurred during an attempt to access the report cache file.

Report output will be canceled.

An unexpected error occurred during processing.

(S)

Suspends output of the report.

(O)

Contact the system administrator.

KAVJF2502-E

An I/O error occurred during an attempt to access the report cache file.

Report output will be canceled.

An I/O error occurred during processing.

(S)

Suspends output of the report.

(O)

From the report window, display the print window again.

If you cannot determine the cause of the problem, collect maintenance information by using the jpcwras command, and then contact the system administrator.

KAVJH0001-E

An unexpected error was detected while initiating the system.

Module Name: DESCRIPTION

Class Name: class-name

Maintenance Information: maintenance-information

An unexpected error was detected while initiating the system.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJH0002-E

An attempt to read a data-model file has failed.

Module Name: DESCRIPTION

Class Name: class-name

Maintenance Information: maintenance-information

The store directory of a data-model file cannot be accessed.

(S)

Suspends processing.

(O)

Make sure the file below the directory "/resources" exists and the permission settings to access this directory are correct.

KAVJH0003-E

An attempt to read a data-model file has failed.

Maintenance Information: maintenance-information

The user does not have access permission for the data model file.

(S)

Cancels Description window display processing.

(O)

Make sure the file below the directory "/resources" exists and the permission settings to access this directory are correct.

KAVJH0004-E

An attempt to read a data-model file has failed.

Maintenance Information: maintenance-information

The data-model file is corrupted.

(S)

Cancels Description window display processing.

(O)

Re-execute the setup command.

KAVJH0005-E

An unexpected error has occurred.

Maintenance Information: maintenance-information

An unexpected error occurred.

(S)

Cancels Description window display processing.

(O)

Contact the system administrator.

KAVJH2501-E

An unexpected error occurred.

Maintenance Information: maintenance-information

An unexpected error occurred.

(S)

Cancels processing to display the properties window.

(O)

Contact the system administrator.

KAVJH2502-E

An attempt to read a Property definition file has failed.

Maintenance Information: maintenance-information

The user does not have access permissions for the directory containing the Property definition file.

(S)

Continues processing.

(O)

Make sure that a file exists under the directory "/resources" and that the permission settings to access the directory are correct.

KAVJH2503-E

An attempt to read a Property definition file has failed.

Maintenance Information: maintenance-information

The user does not have access permissions for the Property definition file.

(S)

Continues processing.

(O)

Make sure that a file exists under the directory "/resources/properties" and that the permission settings to access the directory are correct.

KAVJH2504-E

An attempt to read a Property definition file has failed.

Maintenance Information: maintenance-information

The format of the property definition file is invalid.

(S)

Continues processing.

(O)

Re-execute the setup command.

KAVJJ0001-E

Select a display format (Graph, List or Table).

You must select at least one display format.

(S)

Suspends processing.

(O)

Select at least one display format (Graph, List or Table).

KAVJJ0002-E

Specify the required items.(Item Name:'item-name')

A required item is not specified.

(S)

Suspends processing.

(O)

Enter the required item(s).

KAVJJ0003-E

The drilldown target report definition was not found.

The drilldown target report definition has been removed.

(S)

Suspends processing.

(O)

Specify an existing report definition as the drilldown target.

KAVJJ2551-E

The report does not support multiple agents.

The bookmark cannot be registered.

Because a report type other than historical (multiple agents) is specified, you cannot specify multiple agents.

(S)

Cancels processing.

(O)

Specify historical (multiple agents) as the report type, or specify only one agent.

KAVJJ2552-E

The number of alarm tables to be bound to agent-name exceeds the maximum allowed value maximum-value.

The number of alarm tables to be bound to an agent has exceeded the maximum limit.

(S)

Returns to the bind settings window, and requires to re-specify alarm tables.

(O)

Select alarm tables to be bound to an agent. Do not exceed the maximum number of alarm tables that can be bound to an agent.

KAVJJ5001-I

Close this window once the file has been downloaded.

A report has been output in CSV format, and the window for downloading the data opened.

(O)

Downloads the CSV data, and then close the window.

KAVJJ6601-I

Service:service-name

Status: The service is now starting.

The service is being started.

(S)

Displays the message as status information in the information frame.

KAVJJ6602-I

Service:service-name

Status: The service is active.

The service is active.

(S)

Displays the message as status information in the information frame.

KAVJJ6603-I

Service:service-name

Status: The service is now stopping.

The service is being stopped.

(S)

Displays the message as status information in the information frame.

KAVJJ6604-I

Service:service-name

Status: The service is currently stopped.

The service has stopped.

(S)

Displays the message as status information in the information frame.

KAVJJ6605-I

Service:service-name

The service stopped.

The status of the indicated service is that is was stopped.

(S)

Displays the message in the information frame on the basis of the return value from the service stop command.

KAVJJ6606-I

Service:service-name

The service was forced to terminate.

The status of the indicated service is that is was stopped forcibly.

(S)

Displays the message in the information frame on the basis of the return value from the forced service stop command.

KAVJJ6607-I

Service:service-name

An attempt to force the service to terminate has failed.

An attempt to forcibly stop the indicated service failed.

(S)

Displays the message in the information frame on the basis of the return value from the forced service stop command.

KAVJJ6608-I

Service:service-name

Status: The service is active.[Stand-alone mode]

The status of the service is that it is active in the stand-alone mode.

(S)

Displays the message as status information in the information frame.

KAVJJ6609-I

Service:service-name

Status: The service is processing a request.

The service is processing a request.

(S)

Displays the message as status information in the information frame.

KAVJJ6610-I

Service:service-name

Status: The service is processing a request.[Stand-alone mode]

The status of the service is that it is processing a request in the stand-alone mode.

(S)

Displays the message as status information in the information frame.

KAVJJ6611-I

Operations cannot be performed in the navigation frame or the method frame while application definitions are being updated.

An operation was performed while application definitions were being updated.

(S)

Continues processing.

(O)

Wait until the processing finishes, and then retry the operation.

KAVJJ6612-I

Selected agents cannot be viewed.Agent name : service-ID-of-the-agent-viewed-by-JP1/ITSLM

Information about the selected agent cannot be viewed due to one of the following reasons:

Service information for the agent has been deleted, and this change has been applied by the jpcconf service sync command.

Permission for the user to view the agent has been deleted due to a change in the configuration of the business group.

The function that restricts operations in the Agents tree by general user permissions is enabled, and the selected agent has not been registered in the login user's User Agent tree.

(S)

Continues processing.

(O)

Configure the settings so that the selected agent can be viewed.

KAVJJ8001-Q

reports-count reports will be displayed.

Each report will be displayed in a separate report window.

Do you want to continue?

An attempt was made to display multiple reports.

(S)

Waits for a response.

(O)

To continue, click the OK button. To not display the reports, click the Cancel button.

KAVJJ8002-Q

Do you want to delete the 'folder-name' folder?

This is a confirmation message asking whether or not you wish to delete the indicated folder.

(S)

Waits for a response.

(O)

To delete the folder, click the OK button. To not delete the folder, click the Cancel button.

KAVJJ8003-Q

Do you really want to delete the report definition 'report-name'?

This is a confirmation message asking whether or not you wish to delete the indicated report definition.

(S)

Waits for a response.

(O)

To delete the report definition, click the OK button. To not delete it, click the Cancel button.

KAVJJ8004-Q

The folder 'folder-name' and everything in it will be deleted. Is this OK?

This is a confirmation message asking whether or not you wish to delete the indicated folder and all the data under it.

(S)

Waits for a response.

(O)

To delete the folder and all data under it, click the OK button. To not delete the folder, click the Cancel button.

KAVJJ8005-Q

When using one of the [Line], [Area], and [Stacked Area] graph formats, only one field can be selected for the Multi-Instance's or the Multi-Agent's graph window. If you select more than one, the graph format will change to [Column]. Is this OK?

This is a confirmation message asking whether or not you wish to select the fields.

(S)

Waits for a response.

(O)

To select the fields, click the OK button. To not select the fields, click the Cancel button.

KAVJJ8006-Q

A report of the same name (report-name) already exists in the specified folder. Is it OK to overwrite it?

This is a confirmation message asking whether or not you wish to overwrite the indicated existing report.

(S)

Waits for a response.

(O)

To overwrite the existing report, click the OK button. To cancel, click the Cancel button.

KAVJJ8007-Q

Changing the report type will clear the record and field settings. Do you want to continue?

This is a confirmation message asking whether or not you wish to change the report type.

(S)

Waits for a response.

(O)

To change the report type even if the settings are cleared, click the OK button. To cancel, click the Cancel button.

KAVJJ8008-Q

All compound conditions for the selected conditional expression will be deleted. Is this OK?

This is a confirmation message asking whether or not you wish to delete all compound conditions for the conditional expression.

(S)

Waits for a response.

(O)

To delete the compound conditions, click the OK button. To cancel, click the Cancel button.

KAVJJ8009-Q

The report wizard settings will be cancelled, and the wizard will end. Is this OK?

This is a confirmation message asking whether or not you wish to exit the window used to define reports.

(S)

Waits for a response.

(O)

To exit the window even if the settings are cleared, click the OK button. To cancel, click the Cancel button.

KAVJJ8010-Q

The contents of the information frame will be disabled. Do you want to continue?

This is a confirmation message asking whether or not you wish to discard the contents of the information frame and manipulate another frame.

(S)

Waits for a response.

(O)

To manipulate another frame even if the settings are cleared, click the OK button. To cancel, click the Cancel button.

KAVJJ8011-Q

Changing the product will clear the record and field settings. Do you want to continue?

This is a confirmation message asking whether or not you wish to change the product.

(S)

Waits for a response.

(O)

To change the product, click the OK button. To cancel, click the Cancel button.

KAVJJ8012-Q

Changing the record will clear the field settings. Do you want to continue?

This is a confirmation message asking whether or not you wish to change the record.

(S)

Waits for a response.

(O)

To change the record even if the settings are cleared, click the OK button. To cancel, click the Cancel button.

KAVJJ8013-Q

Do you want to delete the 'bookmark-name' bookmark?

This is a confirmation message asking whether or not you wish to delete the indicated bookmark.

(S)

Waits for a response.

(O)

To delete the bookmark, click the OK button. To not delete the bookmark, click the Cancel button.

KAVJJ8014-Q

When the registered report 'report-name' is deleted and a bookmark becomes empty,

the 'bookmark-name' bookmark will also be deleted.

Do you want to continue?

This is a confirmation message asking whether or not you wish to delete the indicated registered report.

(S)

Waits for a response.

(O)

To delete the registered report, click the OK button. To not delete the registered report, click the Cancel button.

KAVJJ8015-Q

A [Display key] field cannot be selected when the graph format is [Line], [Area], or [Stacked Area]. If you select the [Display key] field, the graph format will change to [Column]. Is this OK?

This is a confirmation message asking whether or not you wish to select the field.

(S)

Waits for a response.

(O)

To select the field, click the OK button. To not select the field, click the Cancel button.

KAVJJ8016-Q

Operations cannot be performed in the navigation frame or method frame during property distribution.

An operation was attempted while properties were being distributed.

(S)

Continues distributing properties.

(O)

Wait until the processing ends, and then retry the operation.

To stop property distribution, click [Stop].

KAVJJ8501-Q

Do you want to delete the following agent?

(agent-name)

This is a confirmation message asking whether or not you wish to delete the indicated agent.

(S)

Waits for a response.

(O)

To delete the agent, click the OK button. To not delete the agent, click the Cancel button.

KAVJJ8502-Q

Do you want to delete the following folder and all data in it?

(folder-name)

This is a confirmation message asking whether or not you wish to delete the indicated folder.

(S)

Waits for a response.

(O)

To delete the folder, click the OK button. To not delete the folder, click the Cancel button.

KAVJJ8526-Q

Do you want to delete the following alarm table and all data in it?

(alarm-table-name)

This is a confirmation message asking whether or not you wish to delete the indicated alarm table.

(S)

Waits for a response.

(O)

To delete the alarm table, click the OK button. To not delete the alarm table, click the Cancel button.

KAVJJ8527-Q

Do you want to delete the following alarm?

(alarm-name)

This is a confirmation message asking whether or not you wish to delete the indicated alarm.

(S)

Waits for a response.

(O)

To delete the alarm, click the OK button. To not delete the alarm, click the Cancel button.

KAVJJ8528-Q

Do you want to unbind the alarm table?

This is a confirmation message asking whether or not you wish to unbind the alarm table.

(S)

Waits for a response.

(O)

To unbind the alarm table, click the OK button. To not unbind the alarm table, click the Cancel button.

KAVJJ8531-Q

The alarm wizard settings will not be set and the wizard will end. Is this OK?

This is a confirmation message asking whether or not you wish to exit the alarm wizard.

(S)

Waits for a response.

(O)

To exit the alarm wizard even if the settings are cleared, click the OK button. To cancel, click the Cancel button.

KAVJJ8551-Q

Is it OK to delete the following baseline?

(baseline)

This message asks whether you want to delete the baseline.

(S)

Waits for a response.

(O)

To delete the baseline, click the OK button. If you do not want to delete the baseline, click the Cancel button.

KAVJJ8552-Q

The alarm creation settings will be canceled, and alarm creation will end. Is this OK?

The message is confirming that you want to terminate alarm creation.

(S)

Waits for a response.

(O)

To terminate alarm creation and cancel the settings, click the OK button. To cancel the operation, click the Cancel button.

KAVJJ8553-Q

Do you want to bind the new alarm to the specified agent?

If there is an alarm already bound to the agent, the new alarm will replace it.

(To create a new alarm without binding, click the [Cancel] button.)

The message is confirming that you want to bind the alarm.

(S)

Waits for a response.

(O)

To bind the alarm to the specified agent, click the OK button. To cancel binding, click the Cancel button.

KAVJJ8554-Q

Do you want to bind the new alarm to the specified agent?

If an alarm is already bound to the agent, the alarm will be appended to the bound one.

(To create a new alarm without binding, click the [Cancel] button.)

The message is confirming that you want to bind the alarm.

(S)

Waits for a response.

(O)

To bind the alarm to the specified agent, click the OK button. To cancel binding, click the Cancel button.

KAVJJ8555-Q

The alarm creation settings will be canceled, and the program returns to the previous window.

Is this OK?

The message is confirming that you want to return to the previous window.

(S)

Waits for a response.

(O)

To cancel the alarm creation settings and return to the previous window, click the OK button. To cancel operations, click the Cancel button.

KAVJJ8571-Q

Are you sure you want to log out?

The message is confirming that you want to log out.

(S)

Waits for a response.

(O)

To log out, click the OK button. To cancel logout, click the Cancel button.

KAVJJ8572-Q

The report definition setting will be canceled.

Is this OK?

The message is confirming that you want to cancel the report definition setting.

(S)

Waits for a response.

(O)

To cancel the report definition setting, click the OK button. To cancel the report definition setting, click the Cancel button.

KAVJJ8573-Q

The report definition was edited.

Do you want to save it?

The message is confirming that you want to save the report definition.

(S)

Waits for a response.

(O)

To save the report definition, click the OK button. To not save the report definition, click the Cancel button.

KAVJJ8574-Q

The field defined for a drilldown report will be deselected.

The setting of the drilldown report definition for the deselected field will be canceled. Is this OK?

The message is confirming that you want to deselect the field.

(S)

Waits for a response.

(O)

To deselect the field, click the OK button. To cancel the deselection, click the Cancel button.

KAVJJ8575-Q

The field included in the field drilldown condition expression will be deselected.

The field drilldown condition expression containing the relevant field will be deleted from the field drilldown operation.

Is this OK?

The message is confirming that you want to deselect the operand of the condition expression.

(S)

Waits for a response.

(O)

To deselect the operand of the condition expression, click the OK button. To cancel deselection, click the Cancel button.

KAVJJ8576-Q

Do you want to save this layout?

(If saved, this layout will overwrite the previous layout.)

The message is confirming that you want to save (and overwrite) the tiling display.

(S)

Waits for a response.

(O)

To save (and overwrite) the tiled layout, click the OK button. To not save the tiled layout, click the Cancel button.

KAVJJ8577-Q

The [property-name] property was selected.

Distribution to services in which the selected property does not exist will fail.

Do you want to continue?

This message confirms whether you want to perform distribution to services for which the selected property does not exist.

(S)

Waits for a response.

(O)

To resume the operation, click the OK button. To stop the operation, click the Cancel button.

KAVJJ8578-Q

The settings will be deselected.

Do you want to continue?

This message confirms whether you want to deselect the settings.

(S)

Waits for a response.

(O)

To deselect the settings, click the OK button. To cancel the operation, click the Cancel button.

KAVJJ8579-Q

The process to change the monitoring suspension settings will be stopped.

All of the previously entered information will become invalid.

Do you want to continue?

This message confirms whether you want to terminate the process to change the monitoring suspension settings.

(S)

Waits for a response.

(O)

To terminate the process, click the OK button. To cancel termination, click the Cancel button.

KAVJJ8601-Q

Do you want to stop the service(service-name)?

This is a confirmation message asking whether or not you wish to execute the service stop command.

(S)

Waits for a response. If the OK button is clicked, the system stops the service; if the Cancel button is clicked, the system does nothing.

(O)

Choose the OK or Cancel button displayed in the dialog box.

KAVJJ8602-Q

An attempt to stop the service (service-name) has failed.

Do you want to force the service to terminate?

This is a confirmation message asking whether or not you wish to forcibly terminate the service if the service stop command fails.

(S)

Waits for a response. If the OK button is clicked, the system stops the service; if the Cancel button is clicked, the system does nothing.

(O)

Choose the OK or Cancel button displayed in the dialog box.

KAVJJ8603-Q

The selected application definitions will be deleted. Do you want to continue?

(Deletion of application definitions might take some time.)

This is a confirmation message asking whether or not you wish to delete the selected application definitions.

(S)

Waits for a response.

(O)

If you want to delete the selected application definitions, click the OK button. If you do not want to delete them, click the Cancel button.

KAVJJ8604-Q

Any changes you have made will be lost.

Are you sure you want to cancel editing?

This is a confirmation message asking whether or not you wish to cancel your changes to contents of the application definition.

(S)

Waits for a response.

(O)

To cancel your changes to contents of the application definition, click the OK button. If you do not want to cancel them, click the Cancel button.

KAVJJ8605-Q

Any changes you have made will be lost.

Are you sure you want to cancel editing?

This is a confirmation message asking whether or not you wish to cancel your changes to contents of the application definition template.

(S)

Waits for a response.

(O)

To cancel your changes to contents of the application definition template, click the OK button. If you do not want to cancel them, click the Cancel button.

KAVJJ8626-Q

Importing the alarm table will overwrite the existing alarm table. Do you want to continue?

This is a confirmation message asking whether or not you wish to import the alarm table.

(S)

Waits for a response.

(O)

To overwrite the existing alarm table, click the OK button. To cancel, click the Cancel button.

KAVJJ8627-Q

Importing the report definition will overwrite the existing report definition. Do you want to continue?

This is a confirmation message asking whether or not you wish to import the report definition.

(S)

Waits for a response.

(O)

To overwrite the existing report definition, click the OK button. To cancel, click the Cancel button.

KAVJJ8651-Q

Do you want to delete the user (user-name)?

This is a confirmation message asking whether or not you wish to delete the indicated user.

(S)

Waits for a response.

(O)

To delete the user, click the OK button. To not delete the user, click the Cancel button.

KAVJJ8652-Q

This password is not recommended. Do you want to continue?

Avoid passwords that are:

- 5 or fewer characters

- Only letters or only numbers

- The same as the user name

This is a confirmation message asking whether or not you wish to use the password despite that it is not recommended.

(S)

Waits for a response.

(O)

To continue with the processing, click the OK button. To not continue with the processing, click the Cancel button.

KAVJJ8653-Q

A user with the same name already exists. This user can only be overwritten if the user is not logged in.

Do you want to overwrite the user?

This is a confirmation message asking whether or not you wish to overwrite the user.

(S)

Waits for a response.

(O)

To overwrite, click the OK button. To not overwrite, click the Cancel button.

KAVJJ8654-Q

The specified value of property-name is invalid.

Specify an integer.

A value specified for property-name is invalid.

(S)

Prompts for re-entry of the property value. The cursor moves to the invalid property value.

KAVJJ8655-Q

The specified value of property-name is invalid.

Specify an integer from lower-limit to upper-limit.

A value specified for property-name is invalid.

(S)

Prompts for re-entry of the property value. The cursor moves to the invalid property value.

KAVJJ8656-Q

The specified value of property-name is invalid.

Specify a real number.

A value specified for property-name is invalid.

(S)

Prompts for re-entry of the property value. The cursor moves to the invalid property value.

KAVJJ8657-Q

The specified value of property-name is invalid.

Specify a value from lower-limit to upper-limit.

A value specified for property-name is invalid.

(S)

Prompts for re-entry of the property value. The cursor moves to the invalid property value.

KAVJJ8658-Q

The specified value of property-name is invalid.

Specify a value in the correct format.

A value specified for property-name is invalid.

(S)

Prompts for re-entry of the property value. The cursor moves to the invalid property value.

KAVJJ8659-Q

The number of characters in the specified value of property-name is invalid.

Specify from lower-limit to upper-limit characters.

The number of characters specified for property-name is invalid.

(S)

Prompts for re-entry of the property value. The cursor moves to the invalid property value.

KAVJJ8660-Q

Are you sure you want to change the bind settings of the alarm table?

This is a confirmation message asking whether you want to change the bind settings of the alarm table.

(S)

Waits for a response.

(O)

To change the bind settings of the alarm table, click the OK button. To keep the same settings, click the Cancel button.

KAVJJ8661-Q

If you refresh the Bind Settings window, changes will be lost. Are you sure you want to do this?

This is a confirmation message asking whether you want to disable the selection status of the alarm table that has been changed from the initial status and then update the information.

(S)

Waits for a response.

(O)

To continue processing, click the OK button. To cancel processing, click the Cancel button.

KAVJK0001-E

command-line: No sub-command is specified on the command line.

No subcommand is specified in the command line arguments.

(S)

Cancels command processing.

(O)

See the manual for the correct command line syntax, and then retry execution.

KAVJK0002-E

command-line: No parameter file is specified on the command line.

The path to the parameter file is not specified correctly in the command line arguments.

(S)

Cancels command processing.

(O)

Specify the path of the parameter file according to the manual.

KAVJK0003-E

command-line: The specified file path of the parameter file is invalid.

The path of the parameter file specified on the command line is invalid.

(S)

Cancels command processing.

(O)

Make sure that the parameter file is located in the path.

KAVJK0004-E

command-line: The output file pathname is not specified on the command line.

The path to the output file is not specified correctly in the command line arguments.

(S)

Cancels command processing.

(O)

Specify the path of the output file according to the manual.

KAVJK0005-E

command-line: The specified file path of the output file is invalid.

The path of the output file specified on the command line is invalid.

(S)

Cancels command processing.

(O)

Make sure that the output file is located in the path.

KAVJK0006-E

command-line: Specified arguments are invalid.

There are too many arguments.

(S)

Cancels command processing.

(O)

See the manual for the correct command line syntax, and then retry execution.

KAVJK0007-E

command-line: An argument is duplicated.

Argument: argument

The same arguments are repeatedly specified on the command line.

(S)

Cancels command processing.

(O)

See the manual for the correct command line syntax, and then retry execution.

KAVJK0008-E

command-line: An invalid service ID was specified.

Service ID: [service-ID]

The specified service ID is too short, invalid, or not used by Agent Store. Alternatively, the service is stopped.

(S)

Cancels command processing.

(O)

Specify a valid service ID, confirm that service is running, and then retry.

KAVJK0009-E

command-line: The specified update count is outside the valid range.

The update count specified for the rc argument on the command line is outside the valid range.

(S)

Cancels command processing.

(O)

Specify a value from 1 to 2,147,483,647.

KAVJK0010-E

command-line: The specified update interval is outside the valid range.

The update interval specified for the ri argument on the command line is outside the valid range.

(S)

Cancels command processing.

(O)

Specify a value from minimum-value to maximum-value.

KAVJK0051-E

command-line: The XML parser returned a DTD validation error.

Line: line-number

Cause: message

The XML parser failed to validate the DTD of the user-specified parameter file.

(S)

Cancels command execution.

(O)

Check the Line in the parameter file, modify the invalid specification based on the Cause, and then retry.

KAVJK0052-E

command-line: The DTD specified in the DOCTYPE statement is invalid.

Line: line-number

DTD: [message-or-DTD-file-name]

The DTD identifier of the DOCTYPE declaration in the parameter file is not an identifier made public by the system.

(S)

Cancels command execution.

(O)

Change the DTD identifier to an identifier made public by the system, and then retry.

KAVJK0053-E

command-line: An XML element value is invalid.

Line: line-number

Element name: tag-name

Element value: [tag-value]

An invalid element value is specified in the parameter file.

(S)

Skips the processing of the service ID resulting in the error and processes the next service ID.

(O)

Check the line in the parameter file, modify the invalid element value(s) based on the Cause, and then retry.

KAVJK0054-E

command-line: An XML attribute value is invalid.

Line: line-number

Element name: tag-name

Attribute name: attribute-name

Attribute value: [attribute-value]

An invalid or duplicated attribute value is specified in the parameter file.

(S)

Skips processing of the service ID resulting in the error and processes the next service ID.

(O)

Check the Line in the parameter file, modify the invalid or duplicated attribute value based on the Cause, and then retry.

KAVJK0101-E

An attempt to create the output file failed.

Output file name: file-name

The output file already exists.

(S)

Cancels command execution.

(O)

Specify a different file name, and then retry.

KAVJK0102-E

The specified file is read-only.

The user does not have permission to overwrite the specified output file.

(S)

Cancels command execution.

(O)

Specify a different file name, and then retry.

KAVJK0103-E

The specified report definition or folder does not exist.

A nonexistent report definition or folder was specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Make sure that the specifications in the parameter file are correct.

KAVJK0104-E

The specified report definition or folder is read-only.

An attempt was made to delete a read-only report definition or folder.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Make sure that the specifications in the parameter file are correct.

KAVJK0105-E

A communication error occurred while the specified report definition or folder was being processed.

Maintenance information: detail-information

A remote messaging interface error occurred during the processing.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Make sure communication with the Manager host can be performed correctly, and that the Manager is running.

KAVJK0106-E

An attempt to output to the file failed while the specified report definition or folder was being processed.

Cause: detail-information

An output file access error occurred during the processing.

(S)

Cancels command processing.

(O)

Remove the cause, and then retry.

KAVJK0109-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-definition>

Attribute name: name

Attribute value: [report-name]

The length of the specified report name is zero or longer than 64 characters.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a report name from one to 64 characters.

KAVJK0110-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-definition>

Attribute name: parent-folder

Attribute value: [folder-name]

The length of a folder name in the specified folder path is zero or longer than 64 characters.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Each folder name in the folder path should be from one to 64 characters.

KAVJK0111-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-definition>

The specified report definition absolute-path-of-the-report already exists.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a unique report definition name.

KAVJK0112-E

The parameter file contains an invalid statement.

Line: line-number

Element: <product-id>

Value: [product-ID]

The specified product ID is not supported by the Server.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a product ID that is supported by the Server.

KAVJK0113-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-type>

Attribute name: type

Attribute value: [report-type]

The specified report type is not supported by the Server.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify one of the following report types.

Both uppercase and lowercase can be used for the character string:

historical-single-agent

HISTORICAL-SINGLE-AGENT

historical-multiple-agents

HISTORICAL-MULTIPLE-AGENTS

realtime-single-agent

REALTIME-SINGLE-AGENT

KAVJK0114-E

The parameter file contains an invalid statement.

Line: line-number

Element: <record>

Attribute name: id

Attribute value: [record-ID]

The specified record ID is not supported by the Server.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a record ID that is supported by the Server.

KAVJK0115-E

The parameter file contains an invalid statement.

Line: line-number

Element: <field>

Attribute name: display-name

Attribute value: [user-display-name]

A display name longer than 24 characters is specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a display name up to 24 characters.

KAVJK0116-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Value: [field-ID]

The specified field ID is not known by the Server.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a field ID known by the Server.

KAVJK0117-E

The parameter file contains an invalid statement.

Line: line-number

Element: <field>

The field ID is not specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a field ID.

KAVJK0118-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [filtering-condition]

A comparison operator is not specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify one of the following comparison operators:

=, >, >=, <, <=, <>

KAVJK0119-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [filtering-condition]

The comparison operator comparison-operator is invalid.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify one of the following comparison operators:

=, >, >=, <, <=, <>

KAVJK0120-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

The right operand of the <expression> value is not specified, however specify-when-displayed is false or not specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify true for specify-when-displayed if you want to omit the definition of the right operand and specify it when prompted.

KAVJK0121-E

The parameter file contains an invalid statement.

Line: line-number

Element: <date-range>

Value: [report-display-period]

The specified date range is invalid.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify one of the following as the date range. Both uppercase and lowercase can be used for the character string:

WITHIN_THE_PAST_HOUR

WITHIN_THE_PAST_24_HOURS

WITHIN_THE_PAST_7_DAYS

WITHIN_THE_PAST_MONTH

WITHIN_THE_PAST_YEAR

SPECIFY_WHEN_DISPLAYED

KAVJK0122-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-interval>

Value: [report-acquisition-interval]

The specified report-interval is invalid.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify one of the following as the report-interval. Both uppercase and lowercase can be used for the character string:

MINUTE

HOUR

DAY

WEEK

MONTH

YEAR

KAVJK0123-E

The parameter file contains an invalid statement.

Line: line-number

Element: <graph-type>

Value: [graph-type]

The specified graph type is invalid.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify one of the following as the graph type. Both uppercase and lowercase can be used for the character string:

COLUMN

STACKED_COLUMN

BAR

STACKED_BAR

PIE

LINE

AREA

STACKED_AREA

KAVJK0124-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Value: [label]

An axis label longer than 40 characters is specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify an axis label up to 40 characters.

KAVJK0125-E

The parameter file contains an invalid statement.

Line: line-number

Element: <ref-report>

Attribute name: pathname

Attribute value: [absolute-path-of-the-report]

The specified report definition is not defined on the Server.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a report definition that is defined on the Server.

KAVJK0126-E

The parameter file contains an invalid statement.

Line: line-number

Element:<ref-report>

Attribute name: pathname

Attribute value: [folder-path]

A report definition is not specified for the drilldown report.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a report definition path name connecting the folder path and report definition name by '/'.

KAVJK0127-E

The specified folder does not contain a report definition.

An empty folder is specified as the target to output the report definition information.

(S)

Skips processing on the specified folder and processes the next folder or report definition in the parameter file.

(O)

Modify the report definition pathname (folder names and the report definition name delimited by '/') specified in the parameter file.

KAVJK0128-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Attribute name: attribute-name

Attribute value: [folder-path]

The specified folder path does not start with '/'.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the folder path according to the manual, and then retry.

KAVJK0129-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-definition>

Attribute name: parent-folder

Attribute value: [folder-path]

The value specified as a folder path is a report definition.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the folder path according to the manual, and then retry.

KAVJK0130-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-definition>

Attribute name: parent-folder

Attribute value: [folder-path]

When 'create' is specified as a subcommand, a system folder cannot be specified as the parent folder.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the folder path according to the manual, and then retry.

KAVJK0131-E

The parameter file contains an invalid statement.

Line: line-number

Element: <record>

Attribute name: id

Attribute value: [record-ID]

When 'historical-multiple-agents' is specified as the report-type, the record ID of multi-instance record cannot be specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify the ID of a single-instance record.

KAVJK0132-E

The parameter file contains an invalid statement.

Line: line-number

Element: <field>

Attribute name: graph

Fields for which the data type is char, string or time_t cannot be displayed in graph format.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify 'false' as the graph attribute of char, string or time_t type fields.

KAVJK0133-E

The parameter file contains an invalid statement.

Line: line-number

Element: <fields>

FALSE is specified for the table, list and graph attributes of all the fields.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify TRUE for at least one of the table, form or graph attributes of any field specified in the parameter file.

KAVJK0134-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [field-ID]

To specify the condition expression for a field drilldown, the field ID to be set for the left operand must match the field ID of a record defined in the drilldown report.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the field ID specified as the left operand according to the manual.

KAVJK0135-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

The right operand in the expression is invalid.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of the right operand according to the manual.

KAVJK0136-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

When the right operand is not enclosed in quotation marks, it is assumed that the right operand is a field ID. However, a field ID is specifiable for the right operand only in a condition expression of a field drilldown.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of the right operand according to the manual.

KAVJK0137-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

The value specified for the right operand exceeds the maximum length.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify up to 2,048 characters in the right operand.

KAVJK0138-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

The right operand is invalid.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

When specifying a condition expression of a field drilldown and the field type of the left operand is time_t, the right operand should be a field ID, or omitted with specify-when-displayed attribute set to TRUE.

KAVJK0139-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

The right operand is invalid.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

When specifying <condition-expression> as a child of <report> and the field type of the left operand is time_t, the right operand should be omitted with specify-when-displayed attribute set to TRUE.

KAVJK0140-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Value: [field-ID]

The specified field ID is not specified by the <fields> element.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the field ID statements in <fields> according to the manual.

KAVJK0141-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Value: [field-ID]

The specified field is neither DATETIME nor any of the fields listed by <fields>. Or it is DEVICEID or PROD_INST however the record to be reported is multi-instance record.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the field ID in <expression> according to the manual.

KAVJK0142-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

The value of the right operand is out of range.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of the right operand according to the manual.

KAVJK0143-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

The number of digits of the value in the right operand exceeds the maximum value.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of the right operand according to the manual.

KAVJK0144-E

The parameter file contains an invalid statement.

Line: line-number

Element: <indication-settings>

Attribute name: maximum-number-of-records

Attribute value: [attribute-value]

The value of maximum-number-of-records is out of range.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a value from 1 to 2,147,483,647.

KAVJK0145-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-interval>

Value: [value]

record-ID is not a PI record. The value of the <report-interval> tag must be MINUTE.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Change the report-interval to MINUTE.

KAVJK0146-E

The parameter file contains an invalid statement.

Line: line-number

Element: <peak-time>

The <peak-time> tag cannot be specified because the specified record (record-ID) is not a PI record or is a multi-instance record.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the <peak-time> tag.

KAVJK0147-E

The parameter file contains an invalid statement.

Line: line-number

Element: <peak-time>

<peak-time> tag is not specifiable because the type of field-ID is neither long, short, ulong, double nor float.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the <peak-time> tag.

KAVJK0148-E

The parameter file contains an invalid statement.

Line: line-number

Element: <peak-time>

<peak-time> tag is specifiable only if <report-interval> tag is set to HOUR.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the <peak-time> tag.

KAVJK0149-E

The parameter file contains an invalid statement.

Line: line-number

Element: <display-key>

When the report type is historical-multiple-agents, <display-key> tag is not specifiable.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the <display-key> tag.

KAVJK0150-E

The parameter file contains an invalid statement.

Line: line-number

Element: <graph-properties>

When no field has the graph attribute set to TRUE, <graph-properties> tag is not specifiable.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the <graph-properties> tag.

KAVJK0151-E

The parameter file contains an invalid statement.

Line: line-number

Element: <graph-type>

Value: [graph-type]

When specifying a multi-instance record, or the report type is multi-agents, and the graph attribute is set to TRUE for more than one field, LINE, AREA, and STACKED_AREA are not specifiable.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of <graph-type> tag.

KAVJK0152-E

The parameter file contains an invalid statement.

Line: line-number

Element: <graph-type>

Value: [graph-type]

When <display-key> tag is specified, LINE, AREA, and STACKED_AREA are not specifiable for <graph-type> tag.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of <graph-type> tag.

KAVJK0153-E

The parameter file contains an invalid statement.

Line: line-number

Element: <graph-type>

Value: graph-type

When specifying a multi-instance record, or the report type is multi-agents, and the series-direction attribute is set to BY_COLUMN, LINE, AREA, and STACKED_AREA are not specifiable for graph-type.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of <graph-type> tag.

KAVJK0154-E

The parameter file contains an invalid statement.

Line: line-number

Element: <graph-type>

Value: graph-type

When specifying a single-instance record, or the report type is single-agent, and the series-direction attribute is set to BY_ROW, LINE, AREA, and STACKED_AREA are not specifiable for graph-type.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the value of <graph-type> tag.

KAVJK0155-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

When PIE is specified for <graph-type> tag, tag-name is not specifiable.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the tag-name tag.

KAVJK0156-E

The parameter file contains an invalid statement.

Line: line-number

Element: <data-label>

When specifying a single-instance record and the report type is single-agent and <graph-type> tag is LINE, AREA, or STACKED_AREA, <data-label> tag cannot be specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the <data-label> tag.

KAVJK0157-E

The parameter file contains an invalid statement.

Line: line-number

Element: <ref-report>

Value: [report-definition-path]

The product ID of the report definition specified for the drilldown does not match, or the data model version is new.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the pathname attribute to specify a correct report definition.

KAVJK0158-E

The XML parser returned a DTD validation error.

Line: line-number

Cause: message

The XML parser failed to validate the user-specified parameter file using the DTD.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Check the Line in the parameter file, modify the invalid specification based on the Cause, and then retry.

KAVJK0159-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression>

Value: [expression-value-in-right-hand-term]

The right operand contains a control character or (, ), [, ], <, >, =, or ".

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Remove the control character or the (, ), [, ], <, >, =, or " from the right operand, and then retry.

KAVJK0160-E

The parameter file contains an invalid statement.

Line: line-number

Element: <ref-field>

Attribute name: id

Attribute value: [field-name]

The value of the ref-field is duplicated.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Make sure that the field ID for the field drilldown is unique.

KAVJK0161-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-definition>

Attribute name: parent-folder

Attribute value: [folder-name]

The folder name starts with or ends with a single-byte blank character.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Remove the first or last blank character, and then retry.

KAVJK0162-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Attribute name: attribute-name

Attribute value: [attribute-value]

The attribute value contains a control character.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Remove the control character from the attribute value, and then retry.

KAVJK0163-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Element value: [value]

The element value contains a control character.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Remove the control character from the element value, and then retry.

KAVJK0164-E

An I/O error occurred during the reading of the confirmation from the user.

Cause: error-information

An I/O error occurred on the user entry.

(S)

Cancels command processing.

(O)

Remove the cause, and then retry.

KAVJK0165-E

The parameter file contains an invalid statement.

Line: line-number

Element: <report-definition>

Attribute name: name

Attribute value: [report-name]

The specified report name is a string of blank character(s).

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a report name starting with one or more characters other than blank.

KAVJK0166-E

command-line: The value specified for the conditional expression in the parameter file exceeds the maximum length.

Line: line-number

Element: tag-name

The value specified for the conditional expression in <logif> exceeds 511 bytes.

(S)

Skips processing of the service ID resulting in the error and processes the next service ID.

(O)

Specify a value within 511 bytes for the conditional expression in <logif>.

KAVJK0167-E

The parameter file contains an invalid statement.

Line: line-number

Element: <field>

Value: [field-name]

The value of the field is duplicated.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Make sure that the field ID of a field is specified only once.

KAVJK0168-E

A report definition with the specified report name has been created by another user.

Report name: absolute-path-of-the-report

The report definition with the specified report name was created by another user.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Check the server status, and then retry.

KAVJK0169-E

The specified folder path has been deleted by another user.

Folder path: folder-path

The specified folder path was deleted by another user.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Check the server status, and then retry.

KAVJK0170-E

command-line: An XML attribute value is invalid.

Line: line-number

Element name: tag-name

Attribute name: attribute-name

Attribute value: [attribute-value]

The service ID of the specified parameter file is too short, invalid, not used by Agent Store, or specified more than once; or the service has stopped.

(S)

Skips processing of the service ID resulting in the error and then processes the next service ID.

(O)

Specify a valid service ID, make sure that the service is running, and then retry.

KAVJK0171-E

The parameter file contains an invalid entry.

Line: line-number

Element: <indication-settings>

If you specify the realtime-single-agent <report-type> tag, you cannot specify the <indication-settings> tag.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify the <realtime-indication-settings> tag.

KAVJK0172-E

The parameter file contains an invalid entry.

Line: line-number

Element: <realtime-indication-settings>

If you specify historical-single-agent or historical-multiple-agents for the <report-type> tag, you cannot specify the <indication-settings> tag.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify the <indication-settings> tag.

KAVJK0173-E

The parameter file contains an invalid entry.

Line: line-number

Element: <refresh-interval>

Attribute name: [attribute-name]

If you specify "true" for do-not-refresh-automatically, you cannot specify initial-value and minimum-value attributes.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the initial-value and minimum-value attributes.

KAVJK0174-E

The parameter file contains an invalid entry.

Line: line-number

Element: <refresh-interval>

Attribute name: initial-value

Attribute value: [attribute-value]

The value of initial-value is outside the valid range.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a value from minimum-value to 3,600.

KAVJK0175-E

The parameter file contains an invalid entry.

Line: line-number

Element: <refresh-interval>

Attribute name: minimum-value

Attribute value: [attribute-value]

The value of minimum-value is outside the valid range.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a value from 10 to 3,600.

KAVJK0176-E

The parameter file contains an invalid entry.

Line: line-number

Element: <display-by-ranking>

You cannot make the specification if the record specified as the id attribute of the <record> tag is a single-line record.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Delete the <realtime-indication-settings> tag.

KAVJK0177-E

The parameter file contains an invalid entry.

Line: line-number

Element: <display-by-ranking>

Attribute name: field

Attribute value: [attribute-value]

An attribute field (character and time) that cannot be specified for ranking has been specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a field other than character and time.

KAVJK0178-E

The parameter file contains an invalid entry.

Line: line-number

Element: <display-by-ranking>

Attribute name: display-number

Attribute value: [attribute-value]

The value of display-number is outside the valid range.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Specify a value from 1 to 100.

KAVJK0179-E

The parameter file contains an invalid entry.

Line: line-number

Element: <field>

Value: [attribute-value]

If you specified realtime-single-agent for the <report-type> tag, you cannot specify [attribute-value] for the <field> tag.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Revise the specified field ID.

KAVJK0180-E

The parameter file contains an invalid statement.

Line: line-number

Element: <peak-time>

The <peak-time> tag cannot be specified because the specified report definition record (record-ID) is not a PI record or is a multi-line record.

(S)

Cancels command processing.

(O)

Delete the <peak-time> tag.

KAVJK0201-E

command-line: The parameter file directory is invalid.

Parameter file name: file-name

The specified directory does not exist, or read is not permitted.

(S)

Cancels command execution.

(O)

Confirm that the directory exists, permit read-only access, and then retry.

KAVJK0202-E

command-line: An attempt to read the parameter file failed.

Parameter file name: file-name

Cause: [exception-reporting-message]

The specified file does not exist, read is not permitted, or an abnormal error occurred during read.

(S)

Cancels command execution.

(O)

Confirm that the file exists, permit read-only access, and then retry.

KAVJK0203-E

command-line: The directory to output the file is invalid.

Output file name: file-name

The directory does not exist or the output file cannot be created because of a problem in the access permission.

(S)

Cancels command execution.

(O)

Confirm that the specified directory exists and that the access permission is correct, and then retry.

KAVJK0204-E

command-line: An attempt to create the output file failed.

Output file name: file-name

Cause: [exception-reporting-message]

The specified output file already exists and overwrite is not permitted, or an abnormal error occurred during write.

(S)

Cancels command execution.

(O)

Confirm that the file access permission is correct, remove the cause of the error, and then retry.

KAVJK0205-E

command-line: A subcommand is invalid.

The first argument on the command line is not a valid subcommand.

(S)

Cancels command processing.

(O)

Modify the command line according to the manual, and then retry.

KAVJK0206-E

command-line: Output of the file was stopped because, in the confirmation dialog box, the user canceled the overwrite of the existing file.

Output of the file was stopped because the overwrite operation was cancelled by the user as the response to the file overwrite confirmation message.

(S)

Cancels command processing.

KAVJK0207-E

command-line: The user does not have access permissions for the specified output destination file path.

Path name: file-path

The user does not have access permissions for the specified output destination path.

(S)

Cancels command processing.

(O)

Check the access permissions for the specified output destination path.

KAVJK0208-E

command-line: The file path of the specified output destination is invalid.

Path name: file-path

Possible causes are as follows:

A directory that does not exist was specified in the output destination file path.

A directory name was specified for the output file name.

(S)

Cancels command processing.

(O)

Specify a valid output destination file path.

KAVJK0209-E

command-line: An I/O error occurred during the opening of the output file.

Error information: error-information

A file I/O error occurred during processing.

(S)

Cancels command processing.

(O)

Determine the cause of the error, and then try again.

KAVJK0210-E

command-line: An I/O error occurred during the writing of the output file.

Error information: error-information

A file I/O error occurred during processing.

(S)

Cancels command processing.

(O)

Determine the cause of the error, and then try again.

KAVJK0211-E

command-line: An I/O error occurred during the opening of the input file.

Error information: error-information

A file I/O error occurred during the opening of the input file.

(S)

Cancels command processing.

(O)

Determine the cause of the error, and then try again.

KAVJK0212-E

command-line: An I/O error occurred during the reading of the input file.

Error information: error-information

A file I/O error occurred during processing.

(S)

Cancels command processing.

(O)

Determine the cause of the error, and then try again.

KAVJK0213-E

command-line: The user does not have access permissions for the specified input file.

Path name: file-path

The file cannot be accessed because the user does not have read permission.

(S)

Cancels command processing.

(O)

Check the access permissions for the file.

KAVJK0214-E

command-line: The specified input file path is invalid.

Path name: file-path

Possible causes are as follows:

A directory that does not exist in the input file path was specified.

A directory name was specified for the input file name.

(S)

Cancels command processing.

(O)

Specify a valid input file path.

KAVJK0301-E

command-line: An attempt to connect to the Manager failed.

Manager host name: connection-target-Manager-host-name

Port number: connection-target-Manager-port-number

A session with the Manager could not be established.

Either the Manager is not running, or the connection target is incorrect.

(S)

Cancels command execution.

(O)

Make sure that the Manager is running and that the connection target is correct.

KAVJK0302-E

command-line: Communication with the Manager failed.

Cause: error-message.

An error occurred in the communication with the Manager.

(S)

jpcasrec or jpcaspsv command: Skips processing of the service ID resulting in the error and processes the next service ID.

jpcrdef command: Skips processing of the specified report definition and processes the next report definition in the parameter file.

jpcprocdef command: Suspends processing.

(O)

Make sure communication with the Manager host can be performed correctly, and that the Manager is running.

KAVJK0303-E

command-line: The definition read or update request to Manager failed.

Cause: error-information

Exception Message: exception-reporting-message

The request to Manager to read or update the required definition failed.

(S)

Cancels command execution.

(O)

Remove the Cause. Check the error messages in the server log files.

KAVJK0304-E

command-line: An attempt to connect to the Manager has failed.

Manager host name: connection-target-Manager-host-name

Port number: connection-target-Manager-port-number

Maintenance information: maintenance-information

A session with the Manager could not be established.

Either the Manager is not running, or the connection target is incorrect.

(S)

Cancels command processing.

(O)

Make sure that the Manager is running and that the connection target is correct.

KAVJK0305-E

The agent cannot be connected.

The report cannot be acquired because the agent or the store database is not running, or the network path to the agent was intercepted.

(S)

Cancels command processing.

(O)

If the agent or database is not running:

Start the agent and the store database, and then retry.

KAVJK0306-E

command-line: A session with the Manager could not be established.

Manager host name: host-name

Port number: port-number

A connection could not be established with the Manager because an invalid host name was specified for the connection-target Manager host in the initial settings file.

(S)

Cancels command processing.

(O)

Use the correct format to specify the host.

KAVJK0401-E

command-line: Memory has become insufficient.

Web Console memory shortage occurred.

(S)

Cancels command execution.

(O)

Specify optional -mx for the command argument, and enhance the maximum heap size.

KAVJK0402-E

command-line: A system error occurred.

Cause: error-message.

A system error occurred.

(S)

Cancels command execution.

(O)

Check the log file, and remove the Cause.

KAVJK0403-E

command-line: Initialization failed.

Cause: error-message.

The initialization information could not be acquired, or logging could not start.

(S)

Cancels command execution.

(O)

Confirm that the settings in config.xml are correct.

KAVJK0404-E

A critical configuration error was detected during reading of the parameter file.

Maintenance information: maintenance-information

A critical configuration error was detected while the parameter file was being read.

(S)

Suspends processing.

(O)

Contact the system administrator.

KAVJK0405-E

command-line: A Manager access error occurred.

Maintenance information: maintenance-information

A Manager access error was detected.

(S)

Cancels command processing.

(O)

Make sure communication with the Manager host can be performed correctly, and that the Manager is running.

KAVJK0502-E

The configuration file was not found.

The configuration file was not found at the installation directory.

(S)

Cancels command execution.

(O)

Check the installation directory for the initialization file.

KAVJK0503-E

The parameter file was not found.

The parameter file specified in the command line is invalid.

(S)

Cancels command execution.

(O)

Specify a correct parameter file, and then retry.

KAVJK0504-E

An internal error occurred.

An internal conflict was detected during command processing.

(S)

Cancels command execution.

(O)

This is a system environment error; contact the system administrator.

KAVJK0505-E

A syntax error occurred.

The format of the command line is invalid.

(S)

Cancels command processing.

(O)

Modify the command line according to the manual, and then retry.

KAVJK0601-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

The content of the tag has not been specified.

(S)

Cancels command processing.

(O)

Specify the content of the tag.

KAVJK0602-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Attribute name: attribute-name

A required attribute has not been specified.

(S)

Cancels command processing.

(O)

Specify the attribute.

KAVJK0603-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Value: [agent-name]

A nonexistent agent has been specified.

(S)

Cancels command processing.

(O)

Specify an existing agent.

KAVJK0604-E

command-line: The parameter file contains an invalid statement.

Element: <agent>

Value: [agent-name]

An agent that does not conform to the product in the specified report definition has been specified.

(S)

Cancels command processing.

(O)

Specify an agent that conforms to the product in the report definition.

KAVJK0605-E

command-line: The parameter file contains an invalid statement.

The filter expression specified in the <expression-values> tag is incomplete.

The value for the [Specify when displayed] filter expression has not been specified.

(S)

Cancels command processing.

(O)

Specify the value for the filter expression.

KAVJK0606-E

command-line: The parameter file contains an invalid statement.

The date of <start-tag> tag is later than that of <end-tag> tag.

(S)

Cancels command processing.

(O)

Specify a date for <start-tag> tag that is earlier than <end-tag> tag.

KAVJK0607-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Attribute name: attribute-name

Attribute value: [attribute-value]

The format for an integer value attribute is invalid.

(S)

Cancels command processing.

(O)

Specify an integer.

KAVJK0609-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

The <tag-name> tag cannot be specified because the specified report record ID (record-ID) is not a PI record.

(S)

Cancels command processing.

(O)

Delete the <tag-name> tag specification.

KAVJK0610-E

The parameter file contains an invalid statement.

Line: line-number

Element: <start-time>

Value: [value-for-start-time]

The date is outside the valid range.

(S)

Cancels command processing.

(O)

Specify a value from 1971 to 2035 for the year.

KAVJK0611-E

The parameter file contains an invalid statement.

Line: line-number

Element: <end-time>

Value: [value-for-end-time]

The date is outside the valid range.

(S)

Cancels command processing.

(O)

Specify a value from 1971 to 2035 for the year.

KAVJK0612-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Value: [input-value]

The format of the date is invalid.

(S)

Cancels command processing.

(O)

Use the correct format to specify the date.

KAVJK0613-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

The <tag-name> tag has been specified for a report for which the [Specify when displayed] filter expression has not been defined.

(S)

Cancels command processing.

(O)

Delete the <tag-name> tag specification.

KAVJK0614-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression-value>

Attribute name: pos

Attribute value: [value-of-pos]

The pos in the <expression-value> tag is outside of the valid range.

(S)

Cancels command processing.

(O)

Specify a value from 0 to maximum-value.

KAVJK0615-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression-value>

Maintenance information: value-of-pos, maximum-value

No filter expression corresponding to the <expression-value> tag exists.

(S)

Cancels command processing.

(O)

Delete the <expression-value> tag.

KAVJK0616-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression-value>

Value: [value]

The value for the filter expression is invalid.

(S)

Cancels command processing.

(O)

Specify a valid value for the filter expression.

KAVJK0617-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Attribute name: attribute-name

The attribute-name attribute has been specified although the field attribute of the <tag-name> tag is NONE.

(S)

Cancels command processing.

(O)

Delete the attribute-name attribute setting.

KAVJK0618-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Multiple agents cannot be specified when 'Historical (Multiple Agents)' is not selected for the report type.

(S)

Cancels command processing.

(O)

Specify only one agent.

KAVJK0619-E

The parameter file contains an invalid statement.

Line: line-number

Element: <indication-settings>

The <indication-settings> tag cannot be specified when 'Realtime (Single Agent)' is selected for the report type.

(S)

Cancels command processing.

(O)

Specify the <realtime-indication-settings> tag.

KAVJK0620-E

The parameter file contains an invalid statement.

Line: line-number

Element: <realtime-indication-settings>

The <realtime-indication-settings> tag cannot be specified when historical report is selected for the report type.

(S)

Cancels command processing.

(O)

Specify the <indication-settings> tag.

KAVJK0621-E

The parameter file contains an invalid statement.

Line: line-number

Element: <peak-time>

The <peak-time> tag cannot be specified because [Hour] is not selected for the report-interval.

(S)

Cancels command processing.

(O)

Delete the <peak-time> tag.

KAVJK0622-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Value: [field-ID]

A field ID which is not selected in the report definition has been specified.

(S)

Cancels command processing.

(O)

Revise the field ID specification.

KAVJK0623-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression-value>

Value: [value]

The number of characters that can be specified for the filter expression value exceeds the maximum.

(S)

Cancels command processing.

(O)

Specify a character string of up to 2,048 characters for the filter expression value.

KAVJK0624-E

The parameter file contains an invalid statement.

Line: line-number

Element: <expression-value>

Value: [value]

A control character or one of the following characters has been specified for the filter expression value: ( ) [ ] < > = "

(S)

Cancels command processing.

(O)

Delete the control character or one of the following characters that has been specified for the filter expression value: ( ) [ ] < > = "

KAVJK0625-E

command-line: The parameter file contains an invalid statement.

The <date-range>, <start-time>, and <end-time> tags cannot all be specified simultaneously.

(S)

Cancels command processing.

(O)

Revise the <date-range>, <start-time>, and <end-time> specifications.

KAVJK0626-E

The parameter file contains an invalid statement.

Line: line-number

Element: <display-by-ranking>

The <display-by-ranking> tag cannot be specified when the record is a single-instance record.

(S)

Cancels command processing.

(O)

Delete the <display-by-ranking> tag.

KAVJK2501-E

An attempt to start Administrator Console(Web Console) has failed.

This error might have been caused by a system resource (such as virtual memory or desktop heap) shortage.

(S)

Administrator Console(Web Console) is stopping.

(O)

Stop unnecessary applications, or take actions for reducing the system resources required for applications that are using excessive system resources, so that sufficient system resources are secured. Then, restart Administrator Console(Web Console). If you are unable to resolve the problem, use the data collection tool to collect data, and then contact the system administrator.

KAVJK2502-E

The user doesn't have Administrator right to start Administrator Console(Web Console).

Users without Windows Administrators permissions cannot execute Administrator Console(Web Console).

(S)

Administrator Console(Web Console) is stopping.

(O)

An user excluding administrators group have to be elevated to administrator privilege after following.

- Enable UAC.

- Check user name and password who has administrator privilege.

KAVJK2503-E

The link configuration file was not found.

The link configuration file (pfmwebcon_host.conf) has been deleted.

(S)

Stops command processing.

(O)

Re-install the application.

KAVJK2504-E

You do not have permission to access the link configuration file.

Access permission for the link configuration file (pfmwebcon_host.conf) was changed.

(S)

Stops command processing.

(O)

Make sure you have access permission for the link configuration file.

KAVJK2505-E

The format of the link configuration file is invalid.

The format of the link configuration file (pfmwebcon_host.conf) is invalid. Perhaps an invalid keyword was specified.

(S)

Stops command processing.

(O)

Make sure the link configuration file is valid.

KAVJK2506-E

An unexpected exception occurred.

Maintenance information: detailed-error information

An unexpected exception occurred.

(S)

Stops command processing.

(O)

Contact the system administrator.

KAVJK2507-E

The parameter file contains an invalid statement.

Line: number-of-lines-in-the-parameter-file

Element: <tag-name>

Value: [specified-service-ID]

The specified service ID's agent does not have report feature.

(S)

Stops command processing.

(O)

Specify agent's service ID had report feature.

KAVJK2508-E

specified-service-ID: The specified service ID cannot output the report.

The agent of the service ID specified for the command line parameter agent does not have report feature.

(S)

Stops command processing.

(O)

Specify service ID had report feature.

KAVJK2512-E

The number of data items for the report to be output to the graph exceeds the maximum number of data items that can be displayed in a graph.

The number of data items for the report to be output to the graph exceeds the maximum number of data items that can be displayed in a graph.

(S)

Stops command processing.

(O)

Either shorten the report display interval in the report definition or decrease the number of selected fields, and then retry the operation.

KAVJK2513-E

An I/O error occurred during an attempt to access the report cache file.

Report output will be canceled.

Maintenance information: detailed-error-information

An I/O error occurred during processing.

(S)

Suspends output of the report.

(O)

Check that the disk has sufficient free space.

Stop Web Console if it is running, delete all subdirectories of the directory for storing the report cache file, and then retry the operation.

If you cannot determine the cause of the problem, collect maintenance information by using the jpcwras command, and then contact the system administrator.

KAVJK2514-E

An unexpected error occurred during an attempt to access the report cache file.

Report output will be canceled.

Maintenance information: detailed-error-information

An unexpected error occurred during processing.

(S)

Suspends output of the report.

(O)

Contact the system administrator.

KAVJK2515-E

Processing stopped because the user canceled updating of the application definitions.

Processing stopped because the user canceled updating of the application definitions.

(S)

Cancels command processing.

KAVJK2516-E

Processing stopped because the user canceled deletion of the application definitions.

Processing stopped because the user canceled deletion of the application definitions.

(S)

Cancels command processing.

KAVJK2519-E

An I/O error occurred in user input.

Error details : error-information(IOException-message)

An I/O error occurred in user input.

(S)

Cancels command processing.

(O)

Check the cause of the error, and then restart processing.

KAVJK2520-E

There is not enough memory.

The server ran out of memory.

(S)

Cancels command processing.

(O)

Close any unnecessary applications and windows to increase available memory.

KAVJK2521-E

The specified agent name is invalid.

Agent name : agent-name

The specified agent name is incorrect, or the specified agent type does not support process monitoring.

(S)

Cancels command processing.

(O)

Specify a valid agent name.

KAVJK2522-E

The specified application definition name is invalid.

Agent name : agent-name

Application definition name : application-definition-name

The format of the specified application definition name is invalid.

(S)

Cancels command processing.

(O)

Specify a valid application definition name.

KAVJK2525-E

An agent that is required for configuring the process monitoring setting has not been set up on the connected PFM-Manager. The process monitoring setting cannot be configured.

An agent for configuring the process monitoring setting has not been set up on the connected PFM - Manager. The process monitoring setting cannot be configured.

(S)

Cancels command processing.

(O)

On the connected PFM-Manager, set up an agent that can configure the process monitoring setting, and then retry the operation.

KAVJK2527-E

The connected PFM-Manager is a version that does not support the process monitoring setting.

The connected PFM - Manager is a version that does not support the process monitoring setting.

(S)

Cancels command processing.

(O)

Update the connected PFM - Manager to a version that supports the process monitoring setting.

KAVJK2528-E

The specified agent is not supported.

Agent name : agent-name

Possible causes are as follows:

The data model version of the specified agent is old.

The Remote Monitor Collector service or Group Agent of PFM-Remote Monitor for Platform was specified.

(S)

Cancels command processing.

(O)

Specify a valid agent name.

KAVJK2529-E

The parameter file contains an invalid statement.

Line number : line-number

Element : <tag-name>

Element value : [element-value]

The length of the specified string exceeds the limit, or the format of the string is invalid.

(S)

Cancels command processing.

(O)

Correct the parameter file, and then specify the correct value.

KAVJK2530-E

The parameter file contains an invalid statement.

Line number : line-number

Element : <tag-name>

Attribute name : attribute-name

Attribute value : [attribute-value]

The length of the specified string exceeds the limit, or the format of the string is invalid.

(S)

Cancels command processing.

(O)

Correct the parameter file, and then specify the correct value.

KAVJK2531-E

The parameter file contains an invalid statement.

Line number : line-number

Element : <tag-name (process01 to 15)>

Specified value at "min" : [value-specified-for-the-min-attribute-of-the-tag-name (process01 to 15)-tag]

Specified value at "max" : [value-specified-for-the-max-attribute-of-the-tag-name (process01 to 15)-tag]

The length of the specified string exceeds the limit, or the format of the string is invalid.

(S)

Cancels command processing.

(O)

Correct the parameter file, and then specify the correct value.

KAVJK2533-E

An attempt to update application definitions for the agent failed because the number of application definitions has reached the maximum (maximum-number-of-application-definitions-that-can-be-defined).

Agent name : agent-name

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

New application definitions cannot be created because other users created application definitions, and the number of application definitions has reached the maximum (maximum-number-of-application-definitions-that-can-be-defined)

(S)

Cancels processing.

(O)

Delete any unnecessary application definitions, and then set the application definitions again.

KAVJK2535-E

Update of application definitions failed because the specified agent could not be accessed.

Agent name : agent-name

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

Update of application definitions failed because the agent or the Store database was not running, or the network route to the agent was blocked.

(S)

Cancels command processing.

(O)

If the agent or store database is not running, start the agent and store database, and then retry the operation.

KAVJK2536-E

One or more application definitions might not have been correctly updated.

Agent name : agent-name

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

Update of application definitions failed because the agent or the store database is not running, or the network path to the agent is blocked.

(S)

Cancels processing.

(O)

If the agent is not running, start it.

The application definition "application-definition-name" might not have been correctly updated.

Create the application definition again by overwriting it.

KAVJK2537-E

Output of application definitions failed.

Agent name : agent-name

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

Output of application definitions failed because the agent or the store database is not running, or the network path to the agent is blocked.

(S)

Cancels command processing.

(O)

If the agent or store database is not running, start the agent and store database, and then retry the operation.

KAVJK2538-E

Output of the list of application definition names failed.

Agent name : agent-name

Output of the list of application definition names failed because the agent or the store database is not running, or the network path to the agent is blocked.

(S)

Cancels command processing.

(O)

If the agent or store database is not running, start the agent and store database, and then retry the operation.

KAVJK2543-E

Duplicate application definition names exist in the parameter file.

Application definition name : application-definition-name (Multiple names can be listed, delimited by commas.)

Duplicate application definition names exist in the parameter file.

(S)

Cancels command processing.

(O)

Reconfigure the parameter file.

KAVJK2544-E

The number of application definitions specified in the parameter file exceeds maximum-number-of-application-definitions-that-can-be-defined.

The number of application definitions specified in the parameter file exceeds maximum-number-of-application-definitions-that-can-be-defined.

(S)

Cancels command processing.

(O)

Make sure that the number of application definitions specified in the parameter file is no more than maximum-number-of-application-definitions-that-can-be-defined.

KAVJK2545-E

Duplicate application definition names are specified in the command line.

Application definition name : duplicate-application-definition-name (Multiple names can be listed, delimited by commas.)

Duplicate application definition names are specified in the command line.

(S)

Cancels command processing.

(O)

Correct the specified application definitions, and then retry the operation.

KAVJK2546-E

Acquisition of application definition information failed.

Agent name : agent-name

Acquisition of application definition information failed because the agent is not running, or the network path to the agent is blocked.

(S)

Cancels command processing.

(O)

If the agent is not running, start it and then retry the operation.

KAVJK2547-E

The number of application definitions to be specified for the agent exceeds maximum-number-of-application-definitions-that-can-be-defined.

The number of application definitions to be specified for the agent exceeds maximum-number-of-application-definitions-that-can-be-defined.

(S)

Cancels command processing.

(O)

Make sure that the number of application definitions to be specified for the agent is no more than maximum-number-of-application-definitions-that-can-be-defined.

KAVJK2548-E

Application definitions could not be output because they do not exist.

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

All the specified application definitions do not exist on the agent.

(S)

Cancels command processing.

(O)

Correct the application definitions, and then retry the operation.

KAVJK2549-E

No application definitions exist in the specified agent.

No application definitions exist in the specified agent.

(S)

Cancels command processing.

(O)

Specify an agent that has application definitions.

KAVJK2550-E

The system environment is invalid.

The system environment is invalid.

(S)

Cancels command processing.

(O)

Reinstall the application.

KAVJK2551-E

The number of specified application definitions exceeds maximum-number-of-application-definitions-that-can-be-defined.

The number of specified application definitions exceeds maximum-number-of-application-definitions-that-can-be-defined.

(S)

Cancels command processing.

(O)

Make sure that the number of specified application definitions is no more than maximum-number-of-application-definitions-that-can-be-defined.

KAVJK2552-E

An error occurred in the connected PFM-Manager.

Error Code : error-code-received-from-the-Manager

An error occurred during processing on the connected PFM-Manager.

(S)

Cancels processing.

(O)

Make sure that the connected PFM-Manager is running normally, and then retry the operation.

If the problem persists, contact the system administrator.

KAVJK2553-E

A connection with PFM - Manager was refused.

The PFM - Manager specified as the connection target does not meet the requirements for establishing a connection.

(S)

Cancels processing.

(O)

If the version of the connected PFM - Manager is newer than that of PFM - Web Console, make sure that there are no functions enabled on PFM - Manager that are not supported by PFM - Web Console.

If such a function is enabled, disable the function or upgrade PFM - Web Console to a newer version.

KAVJK2554-E

One or more application definitions might not have been correctly updated.

Agent name : agent-name

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

Communication with Manager failed.

(S)

Cancels processing.

(O)

Make sure communication with the Manager host can be performed correctly, and that the Manager is running.

The application definition "application-definition-name (Multiple names can be listed, delimited by commas.)" might not have been correctly updated.

Create the application definition again by overwriting it.

KAVJK2557-E

Graph library has failed to create the image.

An I/O error occurred during an attempt to create the graph image.

(S)

Suspends output of the report.

(O)

Restart the service, and then retry the operation from the main window. If you cannot determine the cause of the problem, collect maintenance information by using the jpcwras command, and then contact the system administrator.

KAVJK2558-E

An agent that has not been set up is specified.

Agent name : agent-name

An agent that has not been set up is specified.

(S)

Aborts processing.

(O)

Set up the agent, and then retry the operation.

If the problem persists, contact the system administrator.

KAVJK2559-E

A timeout occurred while displaying the report. Output of the report will now be canceled.

PFM - Manager is taking a long time to respond.

(S)

Suspends processing.

(O)

In the case of output the historical report, revise the report display interval in the report definition, and then output the report again. To output the report without changing the report display interval, extend the timeout value for displaying reports.

In the case of output the real-time report, wait a while and then execute the command again, or consider using the historical report.

If the problem persists, PFM - Manager or the service of the agent might be in the Busy status. Check the service status by using the command to displays the service configuration and status of the Performance Management program.

KAVJK2560-E

An error occurred in the connected PFM-Manager.

Maintenance information: error-code-received-from-the-Manager

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then re-execute the command. If the problem persists, check the PFM-Manager service status.

KAVJK2561-E

The parameter file contains an invalid statement.

Line: number-of-lines-in-the-parameter-file

Element: <exclude-terminal-data>

Value: [invalid-character-string]

The specified value is invalid.

(S)

Skips processing for the specified report definition, and moves to processing for the next report definition.

(O)

Specify one of the following.

Both uppercase and lowercase can be used for the character string:

STARTTIME

ENDTIME

BOTHTIME

NONE

KAVJK2562-E

Execution of the command failed because the destination is not the primary PFM - Manager.

manager host name: host-name-of-connection-target-Manager

port number: port-number-of- connection-target-Manager

Execution of the command failed because the destination is not the primary PFM - Manager.

(S)

Cancels command processing and returns end code 12.

(O)

Execute the command in the PFM - Web Console host that is connected to the primary PFM - Manager.

KAVJK2563-E

The output of the report was skipped because the temporary data of the specified record does not exist.

Service: service-ID

Record: record-ID

Number of times that report could not be acquired: update-number-of-the-skipped-update

The output of the report was skipped because temporary data for the specified record does not exist.

(S)

Ignores the report results that could not be obtained and continues processing.

(O)

If the number of the records of the output file is insufficient, execute the command again after waiting for the time equal to the sum of Collection Interval and Collection Offset of the record-ID record, or consider using the historical report.

However, if Collection Interval is set to 0, the historical report and real-time report in the temporary log mode cannot be output. Consider specifying a value of default or higher for Collection Interval.

KAVJK2564-E

The output of the report was skipped because collection of performance data was skipped.

Service: service-ID

Record: record-ID

Number of times that report could not be acquired: update-number-of-the skipped-update

The output of the report was skipped because the record could not be obtained due to performance data collection.

(S)

Ignores the report results that could not be obtained and continues processing.

(O)

If the number of the records of the output file is insufficient, wait a while, and then execute the command again.

If the problem persists, change the Realtime Report Data Collection Mode of the record-ID record to the temporary log mode, or consider using the history report.

KAVJK2565-E

The real-time report cannot be output because the re-schedule mode for records that take more than 10 seconds to collect is applied.

Service: service-ID

Record: record-ID

The re-schedule mode cannot be used because the Over 10 Sec Collection Time is Yes.

(S)

Suspends processing.

(O)

Change the Realtime Report Data Collection Mode of the record-ID record into the temporary log mode, or consider using the historical report.

KAVJK2566-E

command-line: The update failed because a property that does not exist in the service was specified for a tag of the parameter file.

Service: service-ID

Line: line-number

Element: tag-name

The update failed because a property that does not exist in the service was specified to be updated.

(S)

Skips processing for the service ID for which an error was detected, and performs processing for the next service ID.

(O)

Check the following with respect to the Element:

For "realtime-report-data-collection-mode", check whether the specified service and the version of PFM - Base or PFM - Manager installed on the same host supports the history collection priority function. For a version compatible with the history collection priority function, check whether the function is enabled in PFM - Base or PFM - Manager.

KAVJK2567-E

The report cannot be output because the operation mode was changed from the temporary log mode to the re-schedule mode during output of the real-time report.

Service: service-ID

Record: record-ID

The report cannot be output because the operation mode was changed from temporary log mode to the re-schedule mode during the output of the real-time report.

(S)

Suspends processing.

(O)

Re-execute the command.

KAVJK2568-E

The command is stopped because a function that is not supported by the connection-destination PFM - Manager is used in the specified agent.

Agent: agent-service-ID

Function: function-name

The command was stopped because a function that is not supported by the connection-destination PFM - Manager is used on the specified agent.

(S)

Suspends processing.

(O)

Disable the function of PFM - Base installed on the same host as the specified agent, or upgrade the connection-destination PFM - Manager to a version that supports the function.

KAVJK2701-E

You do not have execution permission.

The user does not have execution permissions.

(S)

Cancels command execution and returns termination code 2.

(O)

Execute the command as a user with Windows Administrators permissions.

KAVJK2702-E

An attempt to create the authentication key file has failed.

Cause:error-information

An attempt to create a key file for authentication failed because the key file for authentication or the storage destination directory could not be accessed.

(S)

Cancels command execution.

(O)

Confirm that the authentication key file or the directory storing the key file exist, and that read access is permitted. Then re-execute the command.

KAVJK2703-E

The user name or password is invalid.

The user name or password specified in the argument is invalid.

(S)

Cancels command execution.

(O)

Specify a valid user name and password, and then re-execute the command

KAVJK2704-E

Creation of the authentication key file was cancelled.

Creation of the authentication key file was cancelled by the user.

(S)

Cancels command execution.

(O)

Re-execute the command.

KAVJK2705-E

command-line: The authentication key file cannot be accessed.

Key file name:authentication-key-file-path

The authentication key file is inaccessible.

(S)

Cancels command execution.

(O)

Confirm that the authentication key file or the directory storing the key file exist, and that read access is permitted. Then re-execute the command. If the authentication key file does not exist, use the jpcmkkey command to create it.

KAVJK2706-E

command-line: The authentication key file is invalid.

Key file name:authentication-key-file-path

The authentication key file is invalid.

(S)

Cancels command execution.

(O)

Use the jpcmkkey command to re-create the key file.

KAVJK2707-E

command-line: The authentication key file could not be used to authenticate Manager.

PFM - Manager authentication failed because the user name or password contained in the authentication key file is invalid.

(S)

Cancels command execution.

(O)

Use the jpcmkkey command to re-create the key file.

KAVJK2708-E

command-line: The user specified in the authentication key file does not have execution permission.

The user information contained in the authentication key file does not have the execution permission required to execute the command.

(S)

Cancels command execution.

(O)

Confirm the execution permission of this command, and then use the jpcmkkey command to re-create the key file for a user with permission to execute this command.

KAVJK2709-E

command-line: The specified service ID is invalid.

Service ID:[service-ID]

The specified service ID is invalid, too short, or not used by Agent Collector. Alternatively, the service has stopped.

(S)

Cancels command processing.

(O)

Specify a valid service ID, confirm that the service is running, and then retry the command.

KAVJK2710-E

command-line: An XML attribute value in the parameter file is invalid.

Line: line-number

Element name: tag-name

Attribute name: attribute-name

Attribute value: [attribute-value]

A service ID of the specified parameter file is invalid, too short, not used by Agent Collector, or specified more than once. Alternatively, the service has stopped.

(S)

Skips processing of the service ID resulting in the error, and then processes the next service ID.

(O)

Specify a valid service ID, confirm that the service is running, and then retry the command.

KAVJK2711-E

Communication with Manager failed. Output of the report will now be cancelled.

Possible causes of this error are as follows:

PFM - Manager stopped.

PFM - Manager is taking a long time to respond.

A communication error occurred.

(S)

Cancels command processing.

(O)

Make sure that Manager is running and that the Web Console host can communicate with the Manager host, and then retry the command.

KAVJK2712-E

The parameter file contains an invalid statement.

Line: line-count

Element: tag-name

Value: [field-ID]

The indicated field ID is not specified in the DATETIME, PROD_INST, DEVICEID, or <fields> tag.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the field ID in tag-name according to the manual.

KAVJK2713-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Value: [field-ID]

For a single-row record, a field ID other than one specified in the DATETIME, <fields> tag is specified. For a multi-row record, a field ID of a record-specific ODBC key field (other than one specified in the DATETIME, <fields> tag) is specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the field ID in tag-name according to the manual.

KAVJK2714-E

The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

Value: [field-ID]

For a single-row record, a field ID other than one specified in the RECORD_TIME, <fields> tag is specified. For a multi-row record, a field ID of a record-specific ODBC key field (other than one specified in the RECORD_TIME, <fields> tag) is specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

Modify the field ID in tag-name according to the manual.

KAVJK2715-E

command-line: The parameter file contains an invalid statement.

Line: line-number

Element: tag-name

The tag-name tag in the specified DTD version is invalid.

(S)

For jpcrdef create

Skips processing of the specified report definition, and starts processing the next report definition in the parameter file.

For jpcaspsv update

Skips processing of the specified agent, and starts processing of the next agent in the parameter file.

(O)

Revise the DTD version attribute specified in the parameter file.

KAVJK2716-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

Attribute name: attribute-name

The tag-name tag in the specified DTD version is invalid.

(S)

Cancels processing.

(O)

Revise the value specified in attribute-name.

KAVJK2717-E

The parameter file contains an invalid statement.

Line: line-number

Element: <tag-name>

The min. value is greater than the max. value.

(S)

Cancels processing.

(O)

Revise the values specified in tag-name.

KAVJK2718-E

An X-coordinate is invalid because it is a null value.

The value of the X-coordinate is null.

(S)

Cancels execution of the command.

(O)

Revise the value.

KAVJK2719-E

An Y-coordinate is invalid because it is a null value.

The value of the Y-coordinate is null.

(S)

Cancels execution of the command.

(O)

Revise the value.

KAVJK2720-E

A label is invalid because it is a null value.

The value of the label is null.

(S)

Cancels execution of the command.

(O)

Revise the value.

KAVJK2721-E

A series label is invalid because it is a null value.

The value of the legend label is null.

(S)

Cancels execution of the command.

(O)

Revise the value.

KAVJK2722-E

The option specified for the graph type is incorrect.

Graph type: graph-type

The specified option is invalid for the graph type.

(S)

Cancels execution of the command.

(O)

Revise the graph option settings.

KAVJK2723-E

The parameter file contains an invalid statement.

Line: line-number

Element: <element-name>

Attribute name: attribute-name

Attribute value: [attribute-value]

The format for a Numeric value attribute is invalid.

(S)

Cancels execution of the command.

(O)

Specify a Numeric value.

KAVJK2724-E

An internal problem was detected

Maintenance information: exception-message.

An internal problem was detected during the creation of Graph.

(S)

Cancels execution of the command.

(O)

Contact the system administrator.

KAVJK2725-E

The parameter file contains an invalid statement.

Line: line-number

Element: <ref-bookmark>

Attribute name: pathname

Attribute value: [absolute-path-for-the-bookmark]

The specified bookmark does not exist.

(S)

Skips processing of the specified report definition, and starts processing the next report definition in the parameter file.

(O)

Specify an existing bookmark, or make sure that the full path of the bookmark is correct.

KAVJK2726-E

The combination report cannot be generated.

The type of the entered bookmark name is not "combination-bookmark".

(S)

Cancels processing.

(O)

Revise the entered bookmark name so that its type is "combination-bookmark".

KAVJK2727-E

The specified item (bookmark-name-or-registered-report-name) or folder does not exist.

A nonexistent item (bookmark-name-or-registered-report-name) or folder was specified.

(S)

Skips processing.

(O)

Make sure that the specifications in the parameter file are correct.

KAVJK2728-E

The parameter file is invalid.

Line: line-number

Element: name-of-element-with-invalid-value

Attribute name: name-of-attribute-with-invalid-value

Attribute value: [failed-attribute-value]

The specified folder path does not start with a forward slash (/).

(S)

Skips processing of the specified bookmark.

(O)

Revise the folder path, and then retry the operation.

KAVJK2729-E

The combination report cannot be generated.

The combination report cannot be acquired because no report was set in the combination bookmark.

(S)

Cancels processing.

(O)

Set at least one report in the combination bookmark, and then retry the operation.

KAVJK2730-E

The specified report is not registered for the specified bookmark.

A bookmark that has no registered report was specified.

(S)

Skips processing of the specified bookmark.

(O)

Make sure that the specifications in the parameter file are correct.

KAVJK2731-E

The parameter file is invalid.

Line: line-number

Element: name-of-element-with-invalid-value

Value: [failed-value]

The date is outside the valid range.

(S)

Cancels processing of the command.

(O)

For the year, specify a value from 1971 to 2035.

KAVJK2732-E

The parameter file is invalid.

Line: line-number

Element: name-of-element-with-invalid-value

Attribute name: name-of-attribute-with-invalid-value

Attribute value: [invalid-attribute-value]

The folder name starts with or ends with a single-byte space character.

(S)

Cancels processing of the command.

(O)

Make sure there is no space character at the start or end of the folder name, and then retry the operation.

KAVJK2733-E

The report cannot be generated.

The report cannot be acquired because the agent or the store database is not running, or there is a break in the network path to the agent.

(S)

Cancels processing.

(O)

Start the agent and the store database, and then retry the operation.

KAVJK2734-E

The agent cannot be connected.

The report cannot be registered for the specified bookmark because the agent or the store database is not running, or because there is a break in the network path to the agent.

(S)

Aborts command processing.

(O)

If the agent or database is not running, start the agent and the store database, and then retry the operation.

KAVJK2735-E

The value specified for the total number of displayed series groups is outside the valid range.

The value specified for the total number of displayed series groups is outside the valid range.

(S)

Aborts processing.

(O)

Specify a value from 1 to maximum-value.

KAVJK2736-E

The parameter file is invalid

Line: line-number

Element: name-of-element-with-invalid-value

Attribute name: name-of-attribute-with-invalid-value

Attribute value: [invalid-attribute-value]

The length of the [invalid-attribute-value] in the name-of-attribute-with-invalid-value is less than 1 or more than 64 characters.

(S)

Skips processing.

(O)

Specify a value for name-of-attribute-with-invalid-value that is from 1 to 64 characters.

KAVJK2737-E

The parameter file is invalid

Line: line-number

Element: name-of-element-with-invalid-value

Attribute name: name-of-attribute-with-invalid-value

Attribute value: [invalid-attribute-value]

A real-time report cannot be registered for a combination bookmark.

(S)

Aborts processing.

(O)

Specify a report other than a real-time report.

KAVJK2738-E

The parameter file is invalid

Line: line-number

Element: name-of-element-with-invalid-value

Attribute name: name-of-attribute-with-invalid-value

Attribute value: [invalid-attribute-value]

A report that has no graph cannot be registered for a combination bookmark.

(S)

Aborts processing.

(O)

Specify a report that has a graph.

KAVJK2739-E

The parameter file is invalid

Line: line-number

Element: name-of-element-with-invalid-value

The specified product ID of the invalid-attribute-value agent does not match the specified product ID of the invalid-attribute-value report.

(S)

Aborts processing.

(O)

Make sure the product IDs of the agent and the report match.

KAVJK2740-E

The parameter file is invalid

Line: line-number

Element: name-of-element-with-invalid-value

There is no report to register.

(S)

Aborts processing.

(O)

To create a bookmark, specify at least one report to register.

KAVJK2741-E

The parameter file is invalid

Line: line-number

Element: name-of-element-with-invalid-value

Attribute name: name-of-attribute-with-invalid-value

Attribute value: [invalid-attribute-value]

A report specified by the [Display] key cannot be registered for a combination bookmark.

(S)

Aborts command processing.

(O)

Specify a report that does not contain a display key.

KAVJK2742-E

The parameter file is invalid

Line: line-number

Element: name-of-element-with-invalid-value

Attribute name: name-of-attribute-with-invalid-value

Attribute value: [invalid-attribute-value]

The format of the specified file is invalid or the file size is 0 bytes.

(S)

Aborts command processing.

(O)

Specify a file that has the correct format and whose size is at least 1 byte, and then retry the operation.

KAVJK2750-E

The parameter file contains an invalid statement.

Line: line-number-in-the-parameter-file

Element: <tag-name>

Attribute name: attribute-name

The tag-name tag is required for the specified DTD version.

(S)

Cancels processing.

(O)

Revise the attribute value specified for attribute-name in the parameter file.

KAVJK2751-E

The agent is not specified.

The agent for which a report is to be output is not specified.

(S)

Cancels processing.

(O)

Specify the agent either as a command line parameter or in the parameter file.

KAVJK2752-E

The parameter file contains an invalid statement.

Line: line-number-in-the-parameter-file

Element: <tag-name>

The tag-name tag cannot have both absolute time and relative time specifications at the same time.

(S)

Cancels processing.

(O)

For an absolute time, specify the value directly. For a relative time, use a <relative-time> tag.

KAVJK2753-E

The parameter file contains an invalid statement.

Line: line-number-in-the-parameter-file

Element: relative-time

Multiple <relative-time> tags cannot be specified within the same parent element.

(S)

Cancels processing.

(O)

Specify only one <relative-time> tag.

KAVJK2754-E

The parameter file contains an invalid statement.

Line: line-number-in-the-parameter-file

Element: relative-time

Attribute name: attribute-name

Attribute value: attribute-value

The attribute attribute-name in the <relative-time> tag is outside the valid range.

(S)

Cancels processing.

(O)

Specify one of the following as the origin time.

now, NOW

this-hour, THIS-HOUR

this-day, THIS-DAY

this-week, THIS-WEEK

this-month, THIS-MONTH

this-year, THIS-YEAR

Specify a value from -12 to 12 for the relative month.

Specify a value from -53 to 53 for the relative week.

Specify a value from -366 to 366 for the relative day.

Specify a value from -24 to 24 for the relative hour.

Specify a value from -60 to 60 for the relative minute.

KAVJK2755-E

The parameter file contains an invalid statement.

Line: line-number-in-the-parameter-file

Element: relative-time

The date calculated in the <relative-time> tag is outside the valid range.

(S)

Cancels processing.

(O)

Revise the specified attribute values such that the year of the calculated date will be from 1971 to 2035.

KAVJK2756-E

The parameter file contains an invalid statement.

Line: line-number-in-the-parameter-file

Element: relative-time

Field ID: View-name-of-the-field

A <relative-time> tag is specified for non-time field.

(S)

Cancels processing.

(O)

Specify the field value directly.

KAVJK2757-E

command-line: The specified service ID is invalid.

The service ID specified for the command line parameter agent is invalid.

(S)

Cancels processing.

(O)

Revise the value specified for agent.

KAVJK2758-E

command-line: The specified service ID is invalid.

The agent of the service ID specified for the command line parameter agent does not exist.

(S)

Cancels processing.

(O)

Specify the service ID of an agent that exists.

KAVJK2759-E

command-line: The specified service ID is invalid.

The service ID specified for the command line parameter agent does not match the product specified in the report definition.

(S)

Cancels processing.

(O)

Specify the service ID of an agent that matches the product specified in the report definition.

KAVJK2760-E

command-line: The specified service ID is invalid.

Multiple agent service IDs cannot be specified if the report is not a multi-agent historical report.

(S)

Cancels processing.

(O)

Specify only one agent service ID.

KAVJK4001-E

command-line: An internal inconsistency was detected.

Maintenance information: maintenance-information.

An internal inconsistency was detected in the command process.

(S)

Cancels command execution.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJK4002-E

command-line: An attempt to output a report failed.

Maintenance information: processing-that-resulted-in-an-error-and-its-error-code

An error occurred in the connected PFM - Manager.

This error might occur if you attempt to output reports by executing successive jpcrpt commands in a short time.

(S)

Suspends processing.

(O)

Adjust the execution intervals between the jpcrpt commands.

If the problem persists, contact the system administrator.

KAVJK5001-I

The specified report definition is read-only. This item is skipped.

Line:line-number

A read-only report definition was specified.

(S)

Skips processing of the specified report definition and processes the next report definition in the parameter file.

KAVJK6503-I

The number of lines of data to be output exceeds the maximum number of lines (maximum-number-of-lines-for-the-output-table-data-in-the-print-window-specified-in-config.xml) for a table.

The data will be output to the table up to the maximum number of lines.

The number of lines of data to be output exceeds the maximum number of lines (maximum-number-of-lines-for-the-output-table-data-in-the-print-window-specified-in-config.xml) for a table.

The data will be output to the table up to the maximum number of lines.

(S)

Outputs the table data up to the maximum number of lines.

(O)

Set the number of lines of data to be output for a table to no more than the maximum-number-of-lines-for-the-output-table-data-in-the-print-window-specified-in-config.xml, and then output the data again.

KAVJK6504-I

Processing to update application definitions will now continue.

Possible causes are shown below. This occurred in query suppression mode, so processing will continue.

One or more application definitions to be overwritten exist.

Application definitions to be deleted exist.

(S)

Continues processing.

KAVJK6505-I

Deletion of application definitions will now continue.

This occurred in query suppression mode, so deletion of application definitions will continue.

(S)

Continues processing.

KAVJK6506-I

The existing output file will be updated.

The specified output file already exists. This occurred in query suppression mode, so the output file will be updated and processing will continue.

(S)

Continues processing.

KAVJK6511-I

The specified agent is PFM-Agent for Platform (Unix), but the value specified for the "type" attribute of the "<process>" element in the specified parameter file is "service" or "SERVICE". (Number = number (Multiple names can be listed, delimited by commas.))

The value will be interpreted as "none".

Application definition name : application-definition-name

The specified agent is PFM - Agent for Platform (UNIX), but the value specified for the type attribute of the <process> element in the specified parameter file is service or SERVICE. (Number = number (Multiple numbers can be listed, delimited by commas.))

(S)

Continues processing with the assumption that none is specified for the type attribute.

KAVJK6512-I

The specified agent is PFM-Agent for Platform (Windows), but the value specified for the <virtual-env-id> element in the specified parameter file is not empty. The value will be ignored.

Application definition name : application-definition-name (Multiple names can be listed, delimited by commas.)

The specified agent is PFM - Agent for Platform (Windows), but the element value specified for the <virtual-env-id> element in the specified parameter file is not null. The value will be ignored.

(S)

Continues processing, ignoring this value.

KAVJK6514-I

No application definitions exist on the specified agent.

Agent name : agent-name

No application definitions exist on the specified agent.

(S)

Stops processing.

KAVJK6516-I

The specified application definitions do not exist on the specified agent.

Agent name : agent-name

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

The specified application definitions do not exist on the specified agent.

(S)

Stops processing.

KAVJK6518-I

Multiple application definitions to be overwritten exist.

One or more application definitions to be overwritten exist.

(S)

Outputs the KAVJK8604-Q message and waits for a response.

KAVJK6519-I

Among the specified application definitions, nonexistent application definitions were specified.

Application definition names : application-definition-name (Multiple names can be listed, delimited by commas.)

The specified application definitions do not exist on the agent.

(S)

Outputs only the application definitions that exist on the agent that are among the specified application definitions.

KAVJK6520-I

The specified agent has no application definitions.

Agent name : agent-name

The specified agent has no application definitions.

(S)

Stops processing.

KAVJK6521-I

Multiple application definitions to be deleted exist.

One or more application definitions to be deleted exist.

(S)

Outputs the KAVJK8604-Q message and waits for a response.

KAVJK6522-I

The real-time report is output in the temporary log mode.

As the values displayed in the report, the values acquired as the historical data are output. Also, if 2 or a higher value is specified for -rc, the report is output for each Collection Interval of the record.

The specified record is set to temporary log mode.

(S)

Continues processing.

KAVJK6523-I

The real-time report is output in the re-schedule mode.

The output of the report might take time.

The specified record is set to the re-schedule mode.

(S)

Continues processing.

KAVJK6701-I

The authentication key file has been created. User Name:user-name

The authentication key file has been created.

(S)

Returns termination code 0.

KAVJK8001-Q

Do you really want to delete the report definition "folder-path/report-name"?[y/n]

This is a confirmation message asking whether or not you wish to delete the report definition.

(S)

Waits for a response.

If y or Y is entered, the system executes deletion processing. If any other value is entered, the system skips processing of the specified report definition and processes the next report definition in the parameter file.

(O)

To delete the report definition, enter y or Y. To not delete it, enter any other value.

KAVJK8002-Q

Do you want to delete the folder "folder-path" including all subfolders and report-definitions?[y/n]

This is a confirmation message asking whether or not you wish to delete the folder and report definition.

(S)

Waits for a response.

If y or Y is entered, the system executes deletion processing. If any other value is entered, the system skips processing of the specified folder and report definition, and processes the next report definition in the parameter file.

(O)

To delete the folder and report definition, enter y or Y. To not delete them, enter any other value.

KAVJK8003-Q

Are you sure you want to overwrite the "file-path" file?[y/n]

A file with the same name already exists at the output destination.

(S)

Waits for a response.

If y or Y is entered, the system overwrites the existing file. If any other value is entered, the system cancels the file output processing.

(O)

To overwrite the existing file, enter y or Y. To not overwrite it, enter any other value.

KAVJK8601-Q

The authentication key file already exists. Is it OK to overwrite it? [y/n]

This is a confirmation message asking whether or not you wish to overwrite the authentication key file.

(S)

Waits for a response.

(O)

To overwrite the existing authentication key file, enter y or Y. To not overwrite it, enter any other value.

KAVJK8604-Q

Do you want to continue the processing? [y/n]

Possible causes are as follows:

One or more application definitions to be overwritten exist.

Application definitions to be deleted exist.

(S)

Waits for a response.

If y or Y is entered as the response to the confirmation message, the system continues processing. If any other value is entered, the system suspends processing.

(O)

To continue processing, enter y or Y. If you do not want to continue processing, enter any other value.

KAVJK8605-Q

Do you want to delete the application definition "application-definition-name" of the agent "agent-name"? [y/n]

The delete subcommand was specified.

(S)

Waits for a response.

If y or Y is entered as the response to the confirmation message, the system deletes the application definition. If any other value is entered, the system suspends processing.

(O)

To delete the application definition, enter y or Y. If you do not want to delete the application definition, enter any other value.

KAVJK8609-Q

Do you want to delete all application definitions of the agent "agent-name"? [y/n]

The delete subcommand was specified.

(S)

Waits for a response.

If y or Y is entered as the response to the confirmation message, the system deletes the application definition. If any other value is entered, the system suspends processing.

(O)

To delete the application definition, enter y or Y. If you do not want to delete the application definition, enter any other value.

KAVJL5001-I

The login service will now be started.

The logging function is starting.

(S)

Starts the logging function's processing.

KAVJS0001-E

The cache expired.

Condition ID:condition-ID

The condition cache has expired.

(S)

Suspends processing.

(O)

Re-select the report from the Main window. Or, Close any unnecessary reports and display the report again.

KAVJS0002-E

The specified report definition was not found.

Report ID:report-ID

The specified report definition has been removed or is in an abnormal state.

(S)

Suspends processing.

(O)

Confirm that the report definition exists.

KAVJS0004-E

The drilldown target report definition was not found.

Report ID:report-ID

Field Name:field-name

The drilldown target report definition has been removed.

(S)

Suspends processing.

(O)

Specify an existing report definition as the drilldown target.

KAVJS0005-E

The specified drilldown definition was not found in the report definition of the drilldown source.

Report ID:report-ID

Field Name:field-name

The specified drilldown definition does not exist. The drilldown definition may have been removed.

(S)

Suspends processing.

(O)

Check the report definition.

KAVJS0006-E

The entered value field-name is outside the valid range.

The value entered for the indicated field is outside the permitted range.

(S)

Suspends processing.

(O)

Revise the value field-name.

KAVJS0007-E

The format of the value entered for field-name is invalid.

The input format of the indicated field is invalid.

(S)

Suspends processing.

(O)

Revise the value field-name.

KAVJS0008-E

The end time is earlier than the start time.

The start date and time is after the end date and time.

(S)

Suspends processing.

(O)

Specify an end time later than the start time.

KAVJS0009-E

The specified character set character-set is not supported.

The character set character-set specified in the configuration file is not supported.

(S)

Suspends processing.

(O)

Change the character set to any of the following supported sets: US-ASCII, windows-1252, ISO-8859-1, UTF-8, UTF-16, UTF-16BE, UTF-16LE, Shift_JIS, EUC-JP, EUC-JP-LINUX, or MS932.

KAVJS0010-E

Memory has become insufficient.

A server memory shortage occurred.

(S)

Suspends processing.

(O)

Stop unnecessary applications and close unused windows to increase available memory.

KAVJS0011-E

The session timed out.

No operation was conducted during the session life time.

(S)

Suspends processing.

(O)

Close the browser, and then retry execution.

KAVJS0012-E

An attempt to communicate with the Manager failed.

Maintenance information: detailed-error-information

An error occurred in the communication with the Manager.

(S)

Suspends processing.

(O)

Confirm that Manager has restarted, and then log in to Web Console again.

KAVJS0013-E

The value of Maximum number of records is outside the valid range.

The specified maximum number of records is outside the permitted range.

(S)

Suspends processing.

(O)

Specify a value from 1 to maximum-value.

KAVJS0014-E

The format of the value for the Maximum number of records is invalid.

The format of the specified maximum number of records is invalid.

(S)

Suspends processing.

(O)

Specify an integer value greater than zero.

KAVJS0015-E

The report definition specified has been changed.

Report ID:report-ID

The indicated report's definition has been changed.

(S)

Suspends processing.

(O)

Redisplay the report from the Main window.

KAVJS0016-E

The filter-numberth filter expression is outside the valid range.

The indicated input filter value is outside the permitted range.

(S)

Suspends processing.

(O)

Modify the value specified as the filter.

KAVJS0017-E

The filter-numberth value entered as the filter is invalid.

The indicted input filter value's format is invalid.

(S)

Suspends processing.

(O)

Modify the value specified as the filter.

KAVJS0018-E

The conditional expression of the field drilldown does not match the record of the referenced report.

Report name:report-name

Field name:field-name

The field drilldown conditional expression for the drilldown source report does not match the record for the drilldown target report.

(S)

Suspends processing.

(O)

Modify the conditional expression of the field drilldown for this report definition according to the manual.

KAVJS0019-E

The field specified in the conditional expression of the field drilldown is not selected with the report definition.

Report name:report-name

Field name:field-name

The field set as the field drilldown conditional expression for the drilldown source report is not selected in the report definition.

(S)

Suspends processing.

(O)

Modify the report definition to specify the drilldown according to the manual.

KAVJS0020-E

An invalid token was detected during Link&Launch.

An invalid token was detected during Link&Launch.

(S)

Suspends processing.

(O)

Re-execute the Link&Launch.

KAVJS0021-E

The received token has expired.

This problem occurs when PR pages are accessed using a bookmark or other invalid context.

(S)

Suspends processing.

(O)

Re-execute the Link&Launch.

KAVJS0022-E

During execution of Link&Launch, an attempt to connect to the Manager failed due to an RMI error.

Module name: Link&Launch

Maintenance information: maintenance-information

The Manager is not running, or the destination host is invalid.

(S)

Suspends processing.

(O)

Make sure the Manager is running and that the destination host is correct.

KAVJS0023-E

During execution of Link&Launch, an attempt to connect to the Manager failed.

Module name: Link&Launch

Maintenance information: maintenance-information

The Manager is not running, or the destination host is invalid.

(S)

Suspends processing.

(O)

Make sure the Manager is running and that the destination host is correct.

KAVJS0025-E

The operation was conducted from a window displayed during a session that was already logged out.

An attempt was made to use the window that was displayed by a session that has already been closed.

(S)

Suspends processing.

(O)

Close the window, and then open a new window.

KAVJS0026-E

The graph data contains an unsupported value.

The graph display field contains NaN, Infinity or another invalid number that may not be supported by the specified agent.

(S)

Suspends processing.

(O)

Cancel the setting of the graph display field, and then redisplay the report.

KAVJS0027-E

The user name or password is invalid.

An invalid user name or password was specified in the login window.

(S)

Suspends processing.

(O)

Specify a valid user name and password, and then retry.

KAVJS0028-E

A multi-byte character is included.

A multi-byte character was entered in a field that permits only single-byte characters.

(S)

Suspends processing.

(O)

Enter only single-byte characters, and then retry.

KAVJS0029-E

During execution of user authentication, an attempt to connect to the Manager failed due to an RMI error.

Maintenance information: maintenance-information

The Manager is not running, or the destination host is invalid.

(S)

Aborts processing.

(O)

Make sure the Manager is running and that the destination host is correct.

KAVJS0030-E

During execution of user authentication, an attempt to connect to the Manager failed.

Maintenance information: maintenance-information

The Manager is not running, or the destination host is invalid.

(S)

Aborts processing.

(O)

Make sure the Manager is running and that the destination host is correct.

KAVJS0031-E

The maximum character length for a report name is 64 characters.

The report name has more than 65 characters.

(S)

Prompts the user to re-enter the report name. The system returns to the report renaming window.

(O)

Use a report name with less than 64 characters.

KAVJS0032-E

The maximum character length for a folder name is 64 characters.

The folder name has more than 65 characters.

(S)

Prompts the user to re-enter the folder name. The system returns to the folder renaming window.

(O)

Use a folder name with less than 64 characters.

KAVJS0033-E

The specified report name already exists. Specify another name.

The specified folder name already exists in the report name.

(S)

Prompts the user to re-enter the report name. The system returns to the report renaming window.

(O)

Specify a report name differing from the existing report name in the same directory.

KAVJS0034-E

The specified folder name already exists. Specify another name.

The specified folder name already exists in the same directory.

(S)

Prompts the user to re-enter the folder name. The system returns to the folder renaming window.

(O)

Specify a folder name differing from the existing folder name in the same directory.

KAVJS0035-E

The specified folder was not found. Folder ID: folder-ID

The specified folder cannot be obtained because the folder has been deleted, or its status is invalid.

(S)

Suspends processing.

(O)

Make sure that the folder exists.

KAVJS0036-E

Wizard transition is invalid. (Maintenance Information: maintenance-information)

An inconsistency error occurred in a wizard context ID.

(S)

Suspends processing.

(O)

Retry the wizard.

KAVJS0037-E

Wizard transition is invalid. (Maintenance Information: maintenance-information)

An inconsistency error occurred in a wizard context page ID.

(S)

Suspends processing.

(O)

Retry the wizard.

KAVJS0038-E

Transaction transition is invalid. (Maintenance Information:maintenance-information)

An inconsistency error occurred in a transaction ID.

(S)

Suspends processing.

(O)

Retry the transaction.

KAVJS0039-E

The specified initial value is out of range.

The specified initial value is outside the permitted range.

(S)

Suspends processing.

(O)

Specify a value from the minimum to 3,600.

KAVJS0040-E

The specified format of the initial value is invalid.

The format of the specified initial value is invalid.

(S)

Suspends processing.

(O)

Specify positive integers.

KAVJS0041-E

The specified minimum value is out of range.

The specified minimum value is outside the permitted range.

(S)

Suspends processing.

(O)

Specify a value from 10 to 3,600.

KAVJS0042-E

The specified format of the minimum value is invalid.

The format of the specified minimum value is invalid.

(S)

Suspends processing.

(O)

Specify positive integers.

KAVJS0043-E

The specified display number value is out of range.

The specified display count is outside the permitted range.

(S)

Suspends processing.

(O)

Specify a value from 1 to 100.

KAVJS0044-E

The specified display number format is invalid.

The format of the specified display count is invalid.

(S)

Suspends processing.

(O)

Specify positive integers.

KAVJS0045-E

Specify a maximum of 40 characters for the x-axis label.

The specified x-axis label is 41 or more characters (one-byte or two-byte characters).

(S)

Suspends processing.

(O)

Specify a maximum of 40 characters (one-byte or two-byte characters) for the x-axis label, and then retry.

KAVJS0046-E

Specify a maximum of 40 characters for the y-axis label.

The specified y-axis label is 41 or more characters (one-byte or two-byte characters).

(S)

Suspends processing.

(O)

Specify a maximum of 40 characters (one-byte or two-byte characters) for the y-axis label, and then retry.

KAVJS0047-E

Specify a maximum of 24 characters for the display name.

The specified display name is 25 or more characters (one-byte or two-byte characters).

(S)

Suspends processing.

(O)

Use a maximum of 24 characters (one-byte or two-byte characters) to specify the display name, and then retry.

KAVJS0048-E

The value entered for the filter is invalid.

The input format of the filter value is invalid.

(S)

Suspends processing.

(O)

Change the value specified for the filter.

KAVJS0049-E

Data label 1 is not specified.

Data label 2 was specified without specifying data label 1.

(S)

Suspends processing.

(O)

If you specify data label 2, also specify data label 1.

KAVJS0050-E

The report cannot be copied.

The data cannot be obtained because the specified folder has been deleted or the folder status is invalid.

(S)

Suspends processing.

(O)

Refresh the folder selection window, and then reselect the folder.

KAVJS0051-E

The report cannot be copied.

A folder that has the same name as the copy-destination folder already exists.

(S)

Suspends processing.

(O)

Rename the folder or select another copy-destination folder.

KAVJS0052-E

The report cannot be copied.

A report that has the same name already exists in the copy-destination folder.

(S)

Suspends processing.

(O)

Rename the report or select another copy-destination folder.

KAVJS0053-E

Specify a maximum of 64 characters for a bookmark name.

The bookmark name has 65 or more characters.

(S)

Prompts re-entry of a bookmark name.

(O)

Specify a maximum of 64 characters for the bookmark name.

KAVJS0054-E

The specified bookmark was not found.

Bookmark ID: bookmark-ID

The data cannot be obtained because the specified bookmark has been deleted or the bookmark status is invalid.

(S)

Suspends processing.

(O)

Make sure that the bookmark exists.

KAVJS0055-E

The specified registered report does not exist.

Registered report ID: report-ID

The specified registered report has been deleted, or cannot be acquired because its status is invalid.

(S)

Suspends processing.

(O)

Make sure that the registered report exists.

KAVJS0056-E

The specified bookmark name already exists. Specify another name.

The specified bookmark name already exists in the same directory.

(S)

Prompts re-entry of a bookmark name.

(O)

Specify a bookmark name different from the names of folders or bookmarks that are in the same directory.

KAVJS0057-E

The report cannot be displayed.

The agent that was bound during bookmark registration was not found. This agent may not exist.

(S)

Suspends processing.

(O)

Make sure that the agent bound during bookmark registration has not been deleted.

KAVJS0058-E

The specified update interval value is outside the valid range.

The value specified for the refresh interval is outside the permitted range.

(S)

Suspends processing.

(O)

Specify a value from minimum-refresh-interval to maximum-refresh-interval.

KAVJS0059-E

The format of the specified update interval value is invalid.

The format of the specified refresh interval is invalid.

(S)

Suspends processing.

(O)

Specify positive integers.

KAVJS0060-E

The selected report definition has been deleted.

Report ID: report-ID

The report definition has been deleted.

(S)

Suspends processing.

(O)

Refresh the report tree and then select report.

KAVJS0061-E

The filter expression cannot be edited.

A report definition at the field drilldown destination has been deleted.

Report ID: report-ID

(S)

Suspends processing.

(O)

Bind any existing report definitions.

KAVJS0062-E

The filter expression cannot be edited.

A report definition at the field drilldown destination was changed while the filter expression was being edited.

Report ID: report-ID

(S)

Suspends processing.

(O)

Bind the report again, or change the report definition at the drilldown destination.

KAVJS0063-E

The filter expression editing has been canceled.

The record at the field drilldown destination was changed while the filter expression was being edited.

Report ID: report-ID

(S)

Suspends processing.

(O)

Bind the report again, or change the report definition at the drilldown destination.

KAVJS0064-E

The filter expression editing has been canceled.

A report definition at the field drilldown destination was changed while the filter expression was being edited.

Report ID: report-ID

(S)

Suspends processing.

(O)

Bind any existing report definitions.

KAVJS0065-E

An invalid URL has been specified.

This problem occurs when Contents are accessed using a bookmark or other invalid context.

(S)

Suspends processing.

(O)

Specify the correct URL for access.

KAVJS0066-E

A nonexistent agent ID has been specified.

Agent ID: agent-ID

A nonexistent agent ID was specified for Link&Launch functionality.

(S)

Suspends processing.

(O)

Restart the service.

KAVJS0067-E

A drilldown report cannot be displayed.

Maintenance information: maintenance-information

An attempt to display a drilldown report failed because the line data selected for the field drilldown exceeded the maximum number of items that could be handled, and data was deleted.

(S)

Suspends processing.

KAVJS0068-E

The specified folder name already exists. Specify another name.

The specified folder name already exists in the same directory.

(S)

Requests another folder name. The window for renaming folders is redisplayed.

(O)

Specify a folder name different from the names of folders or bookmarks that are in the same directory.

KAVJS0069-E

The specified folder name already exists. Specify another name.

The specified folder name already exists in the same directory.

(S)

Requests another folder name. The window for renaming folders is redisplayed.

(O)

Specify a folder name different from the names of folders or report definitions that are in the same directory.

KAVJS2501-E

A new folder cannot be created because the number of folder levels exceeds the allowed maximum.

A new folder cannot be created because the number of folder levels exceeds the allowed maximum.

(O)

Select a node in which the number of folder levels has not reached the maximum.

KAVJS2502-E

A new folder cannot be created because the number of folders in 1 node exceeds the allowed maximum.

A new folder cannot be created because the number of folders in 1 node exceeds the allowed maximum.

(O)

Select a node where the number of folders in 1 node has not reached the maximum, or delete unnecessary folders.

KAVJS2503-E

A new agent cannot be created because the maximum number of agents in 1 node exceeds the allowed maximum.

A new agent cannot be created because the maximum number of agents in 1 node exceeds the allowed maximum.

(O)

Select a node where the number of agents in 1 node has not reached the maximum, or delete unnecessary agents.

KAVJS2504-E

An attempt to copy a folder has failed because a folder with the same name already exists in the copy destination.

A folder with the same name as the folder to be copied already exists in the copy destination.

(O)

Select a node in which a folder with same name does not exist.

KAVJS2505-E

An attempt to copy a folder has failed because the copy destination and the copy source are on the same node.

The copy destination and the copy source are on the same node.

(O)

Select a copy destination that is on a different node from the copy source.

KAVJS2506-E

An attempt to copy a folder failed because the number of folder levels exceeds the allowed maximum.

Copying a folder to this destination would exceed the maximum number of folder levels.

(O)

Select a node in which the maximum number of folder levels will not be exceeded.

KAVJS2507-E

An attempt to copy a folder failed because the number of folders on a node exceeded the allowed maximum.

Copying a folder to this destination would exceed the maximum number of folders allowed on a node.

(O)

Select a node on which the maximum number of folders will not be exceeded, or delete any unnecessary folders.

KAVJS2508-E

An attempt to copy an agent failed because the number of agents on a node exceeded the allowed maximum.

Copying an agent to this destination would exceed the maximum number of agents allowed on a node.

(O)

Select a node on which the maximum number of agents will not be exceeded, or delete any unnecessary agents.

KAVJS2511-E

An application definition template with the specified name already exists.

An application definition template with the specified name already exists.

(S)

Prompts for re-entry.

(O)

Specify another name.

KAVJS2512-E

An application definition with the specified name already exists.

An application definition with the specified name already exists.

(S)

Prompts for re-entry.

(O)

Specify another name.

KAVJS2513-E

The description entered exceeds the maximum number of characters.

Enter a description that does not exceed maximum-length-of-description characters.

The specified description exceeds the maximum number of characters.

(S)

Prompts for re-entry.

(O)

Enter a description that does not exceed the maximum number of characters, and then retry the operation.

KAVJS2514-E

The specified name for the application definition template exceeds the maximum number of characters.

Specify a name that does not exceed maximum-length-of-the-template-name characters.

The specified name for the application definition template exceeds the maximum number of characters.

(S)

Prompts for re-entry.

(O)

Specify a name for the application definition template that does not exceed the maximum number of characters, and then retry the operation.

KAVJS2515-E

The length of the name for the specified application definition is outside the valid range.

The length of the name for the specified application definition is outside the valid range.

(S)

Prompts for re-entry.

(O)

Specify a name with a length of from minimum-length-of-the-instance-name (0 if a lower limit is not set) to maximum-length-of-the-instance-name characters for the application definition.

KAVJS2516-E

The length of item-name (name/label) is outside the valid range. (Process number=number)

The length of item-name (name/label) is outside the valid range. (Process number=number)

(S)

Prompts for re-entry.

(O)

Specify a value with a length of from minimum-character-length (Character string None is output if a lower limit is not set.) to maximum-character-length (Character string None is output if upper limit is not set.) characters.

KAVJS2517-E

The minimum or maximum values of the item are invalid. (Process number=number)

Possible causes of this error are as follows:

The format of the minimum is invalid.

The format of the maximum is invalid.

The minimum is greater than the maximum.

(S)

Prompts for re-entry.

(O)

Check and re-enter the appropriate values.

KAVJS2519-E

An attempt to retrieve the information for an application definition template has failed.

Template name: template-name

The format of the information for the application definition template is invalid.

(S)

Suspends processing.

(O)

Contact the system administrator.

KAVJS2522-E

An attempt to update the information for an application definition template has failed.

Template name: application-definition-template-name

An error occurred while the application definition template file was being written.

(S)

Redisplays the window for editing application definition templates.

(O)

Contact the system administrator.

KAVJS2523-E

An attempt to retrieve the information for an application definition template has failed.

Template name: application-definition-template-name

An error occurred while the application definition template file was being read.

(S)

Suspends processing.

(O)

Contact the system administrator.

KAVJS2524-E

The number of selected processes/services-in-the-Create-or-Edit-window exceeds the maximum number of items that can be added to the process monitoring settings.

number-of-processes-to-be-added items will be added.

The number of selected processes/services-in-the-Create-or-Edit-window exceeds the maximum number of items that can be added to the process monitoring settings.

(S)

Adds only the processes or services that can be added from among the processes/services-in-the-Create-or-Edit-window, and then stops processing.

KAVJS2525-E

An attempt to update an application definition has failed.

Application definition name: application-definition-name (For creation and deletion, this is the target definition name. For editing, this is the definition name after the update.)

Agent name: agent-name (Multiple names can be listed, delimited by commas.)

Possible causes are as follows:

There are agents that are not running.

There are agents that could not be connected to.

The same application definition name has already been made by another browser.

(S)

Cancels processing.

(O)

If the agents are not running, start the agents.

Set the application definition again in the Process Monitoring Settings window.

KAVJS2526-E

An attempt to retrieve the information for an application definition has failed.

Agent name: agent-name

An attempt to retrieve the information for an application definition has failed because the agent is not running or the network connection to the agent failed.

(S)

Suspends processing.

(O)

If the agents are not running:

Start the agents, and then retry the operation.

KAVJS2527-E

The name of the application definition is invalid.

The format of the application definition name is invalid.

(S)

Prompts for re-entry.

(O)

Specify a name in the correct format.

KAVJS2528-E

The name of the application definition template is invalid.

The format of the application definition template name is invalid.

(S)

Prompts for re-entry.

(O)

Specify a name in the correct format.

KAVJS2529-E

The agent cannot be connected to.

A report could not be retrieved because either the agent or the store database is not running, or the network connection to the agent failed.

(S)

Suspends output of the report.

(O)

If the agent or the store database is not running:

Start the agent and the store database, and then retry the operation.

KAVJS2530-E

An attempt to retrieve the process list has failed.

Agent name: agent-name

An attempt to retrieve the process list has failed because the agent was not running or the network route to the agent was blocked.

(S)

Suspends processing.

(O)

Wait a while, and then retry the operation.

If the agents are not running:

Start the agents, and then retry the operation.

KAVJS2531-E

The number of data items for the report to be output to the graph exceeds the maximum number of data items that can be displayed in a graph.

The number of data items for the report to be output to the graph exceeds the maximum number of data items that can be displayed in a graph.

(S)

Suspends processing.

(O)

Either shorten the report display interval in the report definition or decrease the number of selected fields, and then retry the operation.

KAVJS2532-E

An attempt to set up process monitoring alarms for an agent failed.

Agent name: name-of-agent-that-failed-to-bind (Multiple names can be listed, delimited by commas.)

Possible causes are as follows:

The agents are not running, or the network connection to the agents failed.

The specified agent does not support alarm notifications of state changes for each instance.

The response from PFM - Manager is taking too long, or PFM - Manager stopped.

(S)

Sets up process monitoring alarms only for the available agents.

(O)

Perform the following:

If the agents are not running, start the agents, and then retry the operation.

Check the version of the agent bound to this alarm table, and then try to configure the Process Monitoring Settings again.

Wait a while, and then configure the Process Monitoring Settings. If the problem persists, check the status of the PFM - Manager service.

KAVJS2533-E

An attempt to set up process monitoring alarms for an agent failed.

Agent name: agent-name

The number of alarm tables bound to an agent has exceeded the maximum limit.

(S)

Sets up process monitoring alarms only for the available agents.

(O)

In the Alarm Table Bind Settings window, reduce the number of alarm tables bound to the agent.

KAVJS2534-E

The value of "item-name (name/label)" is invalid. (Process number=number)

The value of item-name (name/label) is invalid. (Process number=number)

(S)

Prompts for re-entry.

(O)

Specify a valid value.

KAVJS2535-E

The virtual environment ID is invalid.

The format of the virtual environment ID is invalid.

(S)

Prompts for re-entry.

(O)

Specify a valid ID.

KAVJS2536-E

The length of the specified virtual environment ID is outside the valid range.

Specify an ID that does not exceed maximum-length-of-the-virtual-environment-ID characters.

The character length of the specified virtual environment ID is outside the valid range.

(S)

Prompts for re-entry.

(O)

Specify a virtual environment ID that does not exceed the maximum number of characters, and then retry the operation.

KAVJS2537-E

Process monitoring setup could not start.

Process monitoring setup could not start because alarm tables and report definitions for the agent have not been set up.

(S)

Suspends processing.

(O)

Set up the agent, and then retry the operation.

KAVJS2538-E

An attempt to load an application definition template has failed.

Template name: application-definition-template-name

To determine the cause of the error, search the log file for the name of the application definition template.

(S)

Displays only the templates that could be acquired.

(O)

Check the log file, and then eliminate the cause of the error.

KAVJS2539-E

An attempt to load an application definition template has failed.

An unexpected error occurred during loading of the application definition template.

(S)

Suspends processing.

(O)

Contact the system administrator.

KAVJS2540-E

The content of application definition template is not corresponding to the specified agent.

Template name: application-definition-template-name

Specified item name:item-name

Number:number

The content of application definition template does not correspond to the specified agent.

(S)

Suspends processing.

(O)

Edit the application definition template contents to support the specified agent again.

KAVJS2541-E

The display of the real-time report was skipped because the temporary data of the specified record does not exist.

Service: service-ID

Record: record-ID

Temporary data for the specified record does not exist.

(S)

Ignores the report results that could not be obtained and continues processing.

(O)

Wait for the time equal to the sum of Collection Interval and Collection Offset of the record-ID record, and then refresh the real-time report or consider using the historical report.

If the data is currently being updated automatically, a real-time report will be displayed when the data is obtained at the next update.

However, if Collection Interval is set to 0, the historical report and real-time report in the temporary log mode cannot be displayed. Consider specifying a value of default or higher for Collection Interval.

KAVJS2542-E

Acquisition of the data failed. The list cannot be displayed.

Service: service-ID

Record: record-ID

The list cannot be displayed because temporary data for the specified record does not exist.

(S)

Suspends processing.

(O)

Wait for the time equal to the sum of Collection Interval and Collection Offset of the record-ID record, and then refresh the list.

However, if Collection Interval is set to 0, the list in the temporary log mode cannot be displayed. Consider specifying a value of default or higher for Collection Interval.

KAVJS2543-E

The display of the real-time report was skipped because collection of performance data was skipped.

Service: service-ID

Record: record-ID

Display of the real-time report was skipped because the record could not be obtained due to performance data collection.

(S)

Ignores the report results that could not be obtained and continues processing.

(O)

Wait a while, and then refresh the real-time report.

If the data is currently being updated automatically, a real-time report will be displayed when the data is obtained at the next update.

If the problem persists, change the Realtime Report Data Collection Mode of the record-ID record into the temporary log mode, or consider using the historical report.

KAVJS2544-E

The list cannot be displayed because collection of the data was skipped.

Service: service-ID

Record: record-ID

Display of the list was skipped because the record could not be obtained due to performance data collection.

(S)

Suspends processing.

(O)

Wait a while, and then refresh the list.

If the problem persists, change the Realtime Report Data Collection Mode of the record-ID record to the temporary log mode.

KAVJS2545-E

The real-time report cannot be displayed because the re-schedule mode for records that take more than 10 seconds to collect is applied.

Service: service-ID

Record: record-ID

The re-schedule mode cannot be used because the Over 10 Sec Collection Time is Yes.

(S)

Suspends processing.

(O)

Change the Realtime Report Data Collection Mode of the record-ID record into the temporary log mode, or consider using the historical report.

KAVJS2546-E

The list cannot be displayed because the re-schedule mode for records that take more than 10 seconds to collect is applied.

Service: service-ID

Record: record-ID

The re-schedule mode cannot be used because the Over 10 Sec Collection Time is Yes.

(S)

Suspends processing.

(O)

If the temporary log mode is acceptable, change the Realtime Report Data Collection Mode of the record-ID record to the temporary log mode.

KAVJS2547-E

The report cannot be displayed because the operation mode was changed from the temporary log mode to the re-schedule mode during output of the real-time report.

Service: service-ID

Record: record-ID

The report cannot be displayed because the operation mode was changed from temporary log mode to the re-schedule mode during the output of the real-time report.

(S)

Suspends processing.

(O)

Display the real-time report again.

KAVJS2548-E

The operation is stopped because a function that is not supported by the connection-destination PFM - Manager is used in the specified agent.

Agent: agent-service-ID

Function: function-name

The operation was stopped because a function that is not supported by the connection-destination PFM - Manager is used on the specified agent.

(S)

Suspends processing.

(O)

Disable the function of PFM - Base installed on the same host as the specified agent, or upgrade the connection-destination PFM - Manager to a version that supports the function.

KAVJS2549-E

The property update of the service failed.

Service: service-ID

The property update of the service failed because the Startup Information File (jpccomm.ini) of PFM - Base or PFM - Manager installed in the same host as that of the agent might have been changed.

(S)

Suspends processing.

(O)

Update the properties again.

KAVJS2551-E

Use 64 bytes or fewer for the alarm table name.

The specified alarm table name is 65 bytes or more.

(S)

Prompts for a re-entry of the alarm table name. The system returns to the alarm table name entry window.

(O)

Specify 64 bytes or fewer for the alarm table name.

KAVJS2552-E

Use 20 bytes or fewer for the alarm name.

The specified alarm name is 21 bytes or more.

(S)

Prompts for re-entry of the alarm name. The system returns to the alarm name entry window.

(O)

Use 20 bytes or fewer for the alarm name.

KAVJS2553-E

Use 255 bytes or fewer for the message text.

The specified message text is 256 bytes or more.

(S)

Prompts for re-entry of the message text. The system returns to the message text entry window.

(O)

Use 255 bytes or fewer for the message text.

KAVJS2554-E

The format of the start and/or end time for the specified monitoring period is invalid.

The format of the start and/or end time for the specified monitoring interval period is invalid.

(S)

Prompts for re-entry of the times. The system returns to the monitoring time period entry window.

(O)

Specify the start and end time for the monitoring period in 24-hour time, in HH:MM format.

KAVJS2555-E

The specified alarm table name already exists. Specify another name.

The specified alarm table name already exists.

(S)

Prompts for re-entry of the alarm table name. The system returns to the alarm table name entry window.

(O)

Specify an alarm table name differing from the existing alarm table name.

KAVJS2556-E

The specified alarm name already exists. Specify another name.

The specified alarm name already exists in the specified alarm table.

(S)

Prompts for re-entry of the alarm name. The system returns to the alarm entry window.

(O)

Specify an alarm name that does not exist in the specified alarm table.

KAVJS2557-E

The specified damping value is outside the permitted range.

The specified damping value is outside the permitted range.

(S)

Prompts for re-entry of the damping value. The system returns to the entry window.

(O)

Specify a value from 1 to 32,767.

KAVJS2558-E

All alarm table names beginning with "PFM" are reserved. You cannot make an alarm table name that starts with "PFM".

An alarm table name starting with "PFM" cannot be made.

(S)

Prompts for re-entry of the alarm table name. The system returns to the alarm table name entry window.

(O)

Specify an alarm table name that does not start with "PFM".

KAVJS2559-E

An attempt to retrieve the specified alarm table has failed.

Possible causes are as follows:

The specified alarm table has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Check the following:

Make sure that the alarm table exists.

Wait a while, and then retry the operation. If the problem persists, check the PFM-Manager service status.

KAVJS2560-E

An attempt to retrieve the specified alarm has failed.

Possible causes are as follows:

The specified alarm has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Check the following:

Make sure that the alarm table exists.

Wait a while, and then retry the operation. If the problem persists, check the PFM-Manager service status.

KAVJS2561-E

The number of alarm tables exceeds the allowed maximum.

The number of alarm tables exceeds the maximum allowed in the system.

(S)

Suspends processing.

(O)

Delete any unnecessary alarm tables.

KAVJS2562-E

The number of alarms exceeded the allowed maximum.

The number of alarms exceeds the maximum allowed in the system.

(S)

Suspends processing.

(O)

Delete any unnecessary alarms.

KAVJS2563-E

The number of conditional expressions exceeds the allowed maximum.

The number of conditional expressions exceeds the maximum allowed in the system.

(S)

Suspends processing.

(O)

Delete any unnecessary conditional expressions.

KAVJS2564-E

Use 749 bytes or fewer for the conditional expression.

The specified conditional expression is 750 bytes or more.

(S)

Prompts for a re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Use 749 bytes or fewer for the conditional expression.

KAVJS2565-E

Use 127 bytes or fewer for the conditional expression.

The specified conditional expression is 128 bytes or more.

(S)

Prompts for re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Use 127 bytes or fewer for the conditional expression.

KAVJS2566-E

The conditional expression is invalid.

The conditional expression contains an invalid character string.

(S)

Prompts for re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Enter a valid character string for the conditional expression.

KAVJS2567-E

Use 127 bytes or fewer for the email address.

The specified email address is 128 bytes or more.

(S)

Prompts for re-entry of the email address. The system returns to the email address entry window.

(O)

Use 127 bytes or fewer for the email address.

KAVJS2568-E

Use 1,000 bytes or fewer for the email text.

The specified email text is 1,001 bytes or more.

(S)

Prompts for re-entry of the email message text. The system returns to the email text entry window.

(O)

Use 1,000 bytes or fewer for the email text.

KAVJS2569-E

Use 511 bytes or fewer for the command name.

The specified command name is 512 bytes or more.

(S)

Prompts for re-entry of the command name. The system returns to the command name entry window.

(O)

Use 511 bytes or fewer for the command name.

KAVJS2570-E

Use 2,047 bytes or fewer for the command argument.

The specified command argument is 2,048 bytes or more.

(S)

Prompts for re-entry of the command argument. The system returns to the command argument entry window.

(O)

Use 2,047 bytes or fewer for the command argument.

KAVJS2571-E

Specify an event ID by using a hexadecimal number in the range 0 to 1fff, or 7fff8000 to 7fffffff.

The specified event ID was not a hexadecimal number, or was not in the range 0 to 1fff, or 7fff8000 to 7fffffff.

(S)

Prompts for re-entry of the event ID. The system returns to the event ID entry window.

(O)

Specify an event ID by using a hexadecimal number in the range 0 to 1fff, or 7fff8000 to 7fffffff.

KAVJS2572-E

Use 128 bytes or fewer for the event message.

The specified event message is 129 bytes or more.

(S)

Prompts for re-entry of the message. The system returns to the message entry window.

(O)

Use 128 bytes or fewer for the event message.

KAVJS2573-E

An attempt to activate an alarm has failed.

Possible causes are as follows:

The specified alarm has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Activates only the alarms that can be activated and then terminates processing.

(O)

Check the following:

Make sure that the alarm table exists.

Wait a while, and then activate the alarm. If the problem persists, check the PFM-Manager service status.

KAVJS2574-E

An attempt to bind an alarm for an agent has failed.

Possible causes are as follows:

The specified agent or alarm has been deleted.

The specified agent does not support alarm notifications of state changes for each instance.

The response from PFM - Manager is taking too long, or PFM - Manager stopped.

(S)

Binds only those agents that can be bound and then terminates processing.

(O)

Perform the following:

Make sure that the alarm and selected agent exists.

Check the version of the agent bound to this alarm table, and then try to bind the alarm again.

Wait a while, and then try to bind the alarm again. If the problem persists, check the status of the PFM - Manager service.

KAVJS2575-E

An attempt to unbind an alarm for an agent has failed.

Possible causes are as follows:

An alarm or agent has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Unbinds only those agents that can be unbound and then terminates processing.

(O)

Check the following:

Make sure that the alarm and selected agent exists.

Wait a while, and then try to unbind the alarm again. If the problem persists, check the PFM-Manager service status.

KAVJS2576-E

An attempt to copy an alarm or alarm table has failed.

Possible causes are as follows:

The specified alarm or alarm table has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Check the following:

Make sure that the specified alarm or alarm table exists.

Wait a while, and then try to copy the alarm or alarm table again. If the problem persists, check the PFM-Manager service status.

KAVJS2577-E

An attempt to delete an alarm or alarm table has failed.

Possible causes are as follows:

The specified alarm or alarm table has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Check the following:

Make sure that the specified alarm or alarm table exists.

Wait a while, and then try to delete the alarm or alarm table again. If the problem persists, check the PFM-Manager service status.

KAVJS2578-E

The alarm table name is invalid.

The specified alarm table name contains invalid characters.

(S)

Prompts for re-entry of the alarm table name. The system returns to the alarm table name entry window.

(O)

The following characters can be used for alarm table names:

Alphanumeric ASCII characters

% - ( ) _ . / @ [ ]

KAVJS2579-E

The alarm name is invalid.

The specified alarm name contains invalid characters.

(S)

Prompts for re-entry of the alarm name. The system returns to the alarm name entry window.

(O)

The following characters can be used for alarm names:

Alphanumeric ASCII characters

% - ( ) _ . / @ [ ]

KAVJS2580-E

The message text is invalid.

The specified message text contains invalid characters.

(S)

Prompts for re-entry of the message text. The system returns to the message text entry window.

(O)

Use only alphanumeric ASCII characters for the message text.

KAVJS2581-E

The specified email address is invalid.

The specified email address contains invalid characters.

(S)

Prompts for re-entry of the email address. The system returns to the email address entry window.

(O)

Use only alphanumeric ASCII characters for the email address.

KAVJS2582-E

The specified command name is invalid.

The specified command name contains invalid characters.

(S)

Prompts for re-entry of the command name. The system returns to the command name entry window.

(O)

Use only alphanumeric ASCII characters for command names.

KAVJS2583-E

Specify no more than 64 characters for a baseline name.

The specified baseline name contains 65 or more characters.

(S)

Requests another baseline name.

(O)

Specify no more than 64 characters for the baseline name.

KAVJS2584-E

The specified baseline was not found.

Baseline ID: baseline-ID

The specified baseline cannot be acquired because it has been deleted or is invalid.

(S)

Cancels processing.

(O)

Make sure that the baseline exists.

KAVJS2585-E

The specified baseline name already exists. Specify another name.

The specified baseline name already exists in the same bookmark.

(S)

Requests another baseline name.

(O)

Specify a baseline name that is different from other baseline names that are in the same bookmark.

KAVJS2586-E

A combination bookmark cannot be created because the maximum number of registered combination bookmarks has been reached.

You cannot create a registered report or a baseline because the limit on number of items registered for the combination bookmark would be exceeded.

(S)

Cancels processing.

(O)

Delete any unnecessary registered reports or baselines.

KAVJS2587-E

Specify no more than 40 characters for a series group name.

The specified series group name contains 41 or more characters.

(S)

Requests another series group name.

(O)

Specify no more than 40 characters for a series group name.

KAVJS2588-E

Specify no more than 64 characters for a graph title.

The specified graph title contains 65 or more characters.

(S)

Requests another graph title.

(O)

Specify no more than 64 characters for a graph title.

KAVJS2589-E

An attempt to read a data-model file has failed.

An explanation cannot be displayed.

You do not have permission to access the data-model file.

(S)

Displays the field selection window but without any explanation.

(O)

Make sure the file below the directory "/resources" exists and the permission settings to access this directory are correct.

KAVJS2590-E

An attempt to read a data-model file has failed.

An explanation cannot be displayed.

The data-model file is corrupted.

(S)

Displays the field selection window but without any explanation.

(O)

Re-execute the setup command.

KAVJS2591-E

A binding attempt failed because the number of alarm tables exceeded the maximum allowed value (maximum-value).

Agent name: agent-name

There is an agent for which binding failed because the number of alarm tables that can be bound to the agent exceeds the maximum value.

(S)

Execute binding only for an agent that can be bound, and then display the View Results window.

(O)

Make sure there is no problem with the number of alarm tables that are bound to the agent.

KAVJS2593-E

In [Field], select a field.

There is no selected field.

(S)

Prompts the user to select a field. The program returns to the Edit Report Definitions window.

(O)

Select at least one field.

KAVJS2594-E

The format of the value specified in [Filter] is invalid.

The format of the filter value is invalid.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Revise the value specified in [Filter].

KAVJS2595-E

In [Indication settings], the specified initial value is outside the valid range.

In [Indication settings], the specified initial value is outside the valid range.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a value from the minimum to 3,600.

KAVJS2596-E

In [Indication settings], the specified initial value is invalid.

In [Indication settings], the specified initial value is invalid.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a positive integer.

KAVJS2597-E

In [Indication settings], the specified minimum value is outside the valid range.

In [Indication settings], the specified minimum value is outside the valid range.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a value from 10 to 3,600.

KAVJS2598-E

In [Indication settings], the specified minimum value is invalid.

In [Indication settings], the specified minimum value is invalid.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a positive integer.

KAVJS2599-E

In [Indication settings], the specified display number is outside the valid range.

In [Indication settings], the specified display number is outside the valid range.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a value from 1 to 100.

KAVJS2600-E

In [Indication settings], the specified display number is invalid.

In [Indication settings], the specified display number is invalid.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a positive integer.

KAVJS2601-E

The specified value is outside the valid range. Specify a value from minimum-value to maximum-value.

The entered value is outside the valid range.

(S)

Prompts for re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Specify a value inside the valid range, and then retry the operation.

KAVJS2602-E

The specified value contains invalid characters.

A multi-byte character was specified in a field that permits only alphanumeric ASCII characters.

(S)

Prompts for re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Use only alphanumeric ASCII characters, and then retry the operation.

KAVJS2603-E

The specified value exceeds the maximum length.

Specify a value that is maximum-number-of-characters characters or fewer.

The entered value exceeds the maximum number of characters.

(S)

Prompts for re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Specify a value that does not exceed the maximum number of characters, and then retry the operation.

KAVJS2604-E

The service properties could not be updated.

Possible causes are as follows:

A service has stopped or a communication error has occurred.

The maximum number of nodes that can be added to a service has been exceeded.

An agent in the connected PFM - Manager is in the suspended state.

(S)

Suspends processing.

(O)

Check the following:

Make sure the operating status and communication status of the service and manager are normal.

Make sure the number of property nodes does not exceed the maximum.

Use either the Monitoring Suspension Settings window or a command that displays the monitoring suspension settings and monitoring status to check the monitoring status of the agent. If an agent is in the suspended state, resume the monitoring of the agent. If the problem persists, disable the monitoring suspension function.

KAVJS2605-E

The conditional expression is invalid.

The conditional expression contains an invalid character.

(S)

Prompts for re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Enter a valid character string for the conditional expression.

KAVJS2606-E

The specified host name could not be resolved.

The specified host name is invalid.

(S)

Prompts for re-entry of the conditional expression. The system returns to the conditional expression entry window.

(O)

Specify the correct host name.

KAVJS2607-E

Distribution of a service property has failed.

Service name: service-name

Property name: property-name

The possible causes for the service for which property distribution failed are as follows:

A distribution-destination service has stopped or a communication error has occurred.

The versions of the Store databases for the distribution-destination services do not match.

The maximum number of nodes that can be added to a distribution-destination service has been exceeded.

If the name of a property is displayed, the property does not exist in the distribution-destination service, or an agent in the service is in the suspended state.

(S)

Distributes properties to the services that can receive properties and ends processing.

(O)

For the failed distribution-destination service(s):

Make sure the operating status and communication status of the service and manager are normal.

Make sure the versions of the distribution-source Store databases match.

Make sure the number of property nodes does not exceed the maximum.

If "Realtime Report Data Collection Mode" is displayed as the property name, check whether the version of the PFM - Base or PFM - Manager installed on the same host as that of the distribution-destination service supports the history collection priority function. For a version compatible with the history collection priority function, check whether the function is enabled in PFM - Base or PFM - Manager.

If "Monitoring Level" is displayed for the property name, use either the Monitoring Suspension Settings window or a monitoring resume command to resume the monitoring of agents in the suspended state. If the problem persists, disable the monitoring suspension function.

KAVJS2608-E

The message is too long. Use 1023 or fewer bytes for the event message.

The specified event message is 1024 or more bytes.

(S)

Prompts for re-entry of the message. The system returns to the message entry window.

(O)

Use 1023 or fewer bytes for the event message.

KAVJS2609-E

An agent that has not been set up is selected.

product ID : product-ID

data model version : data-model-version

An agent that has not been set up is selected.

(S)

Aborts processing.

(O)

Set up the agent, and then retry the operation.

If the problem persists, contact the system administrator.

KAVJS2612-E

An I/O error occurred during an attempt to access the report cache file.

Report output will be canceled.

Maintenance information: detailed-error-information

An I/O error occurred during processing.

(S)

Suspends output of the report.

(O)

Check that the disk has sufficient free space.

Delete all subdirectories of the directory for storing the report cache file, restart the service, and then select the reports from the main window.

If you cannot determine the cause of the problem, collect maintenance information by using the jpcwras command, and then contact the system administrator.

KAVJS2613-E

An unexpected error occurred during an attempt to access the report cache file.

Report output will be canceled.

Maintenance information: detailed-error-information

An unexpected error occurred during processing.

(S)

Suspends output of the report.

(O)

Contact the system administrator.

KAVJS2614-E

An attempt to update an application definition for one or more agents failed.

Agent name: agent-name

Application definition name: application-definition-name

Possible causes are as follows:

One or more agents are not running.

One or more agents could not be connected to.

(S)

Updates application definitions only for the available agents.

(O)

If agents are not running, start them.

Set the application definition again in the Process Monitoring Settings window.

KAVJS2615-E

An attempt to update an application definition for one or more agents failed.

Agent name: agent-name

Application definition name: application-definition-name

The application definition cannot be created because other users have created application definitions, and the number of application definitions has reached the maximum (maximum-number-of-application-definitions).

(S)

Updates application definitions only for the available agents.

(O)

To create the application definition, delete any unnecessary application definitions, and then set the new application definition again in the Process Monitoring Settings window.

KAVJS2616-E

An attempt to update an application definition for one or more agents failed.

Agent name: agent-name

Application definition name: application-definition-name

An attempt to edit an application definition became an attempt to create it because it has been deleted by another user. However, the application definition cannot be created because the maximum number of application definitions (maximum-number-of-application-definitions) has been reached.

(S)

Updates application definitions only for the available agents.

(O)

The application definition cannot be edited because it has been deleted.

To create the application definition, delete any unnecessary application definitions, and then set the new application definition again in the Process Monitoring Settings window.

KAVJS2617-E

An attempt to update an application definition for one or more agents failed.

The application definition might not be correctly updated.

Agent name: agent-name

Application definition name: application-definition-name

Possible causes are as follows:

One or more agents are not running.

One or more agents could not be connected to.

(S)

Updates application definitions only for the available agents.

(O)

If agents are not running, start them.

If application definition [application-definition-name] exists, delete it manually.

Set the application definition again in the Process Monitoring Settings window.

KAVJS2618-E

An attempt to update an application definition for one or more agents failed.

The application definition might not be correctly updated.

Agent name: agent-name

Application definition name: application-definition-name

Possible causes are as follows:

One or more agents are not running.

One or more agents could not be connected to.

(S)

Updates application definitions only for the available agents.

(O)

If agents are not running, start them.

If application definition [application-definition-name] exists, delete it manually.

Because the application definition before editing has been lost, re-create the application definition in the Process Monitoring Settings window.

KAVJS2619-E

An attempt to update an application definition for one or more agents failed.

Agent name: agent-name

Application definition name: application-definition-name

An attempt to update an application definition failed.

(S)

Updates application definitions only for the available agents.

(O)

For details on the errors affecting each agent, refer to the error messages in the range from KAVJS2614-E to KAVJS2618-E output to the operation status logs.

Take action as described in the message, remove all causes of the error, and then set the application definition again.

KAVJS2620-E

The selected agents have been removed from the Agents tree.

Processing cannot continue.

Agents : agent-name (Multiple names can be listed, delimited by commas.)

The agents might have been deleted from the system.

(S)

Suspends processing.

(O)

Refresh the Agents tree.

KAVJS2621-E

The selected folder has been removed from the Agents tree.

Processing cannot continue.

Folder : folder-name

All agents under the folder might have been deleted from the system.

(S)

Suspends processing.

(O)

Refresh the Agents tree.

KAVJS2622-E

An error occurred in the connected PFM-Manager.

Maintenance information: error-code-received-from-the-Manager

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then retry the operation. If the problem persists, check the PFM-Manager service status.

KAVJS2623-E

A connection with PFM - Manager was refused.

Login failed.

The PFM - Manager specified as the connection target does not meet the requirements for establishing a connection.

(S)

Suspends processing.

(O)

If the version of the connected PFM - Manager is newer than that of PFM - Web Console, make sure that there are no functions enabled on PFM - Manager that are not supported by PFM - Web Console.

If such a function is enabled, disable the function or upgrade PFM - Web Console to a newer version.

KAVJS2624-E

Some agents have not been set up.

product ID : product-ID

data model version : data-model-version

Some agents have not been set up.

(S)

Suspends processing.

(O)

Set up the agent, and then retry the operation.

KAVJS2628-E

More than 100 keywords have been entered.

More than 100 keywords have been entered.

(S)

Suspends processing.

(O)

Enter 100 or fewer keywords, and then retry the operation.

KAVJS2629-E

A timeout occurred while displaying the report. Output of the report will now be canceled.

PFM - Manager is taking a long time to respond.

(S)

Suspends processing.

(O)

In the case of display the historical report, revise the report display interval in the report definition, and then display the report again. To display the report without changing the report display interval, extend the timeout value for displaying reports.

In the case of display the real-time report, wait a while and then displaying the report again, or consider using the historical report.

If the problem persists, PFM - Manager or the service of the agent might be in the Busy status. Check the service status by using the command to displays the service configuration and status of the Performance Management program.

KAVJS2630-E

No command definition action handler matches the keywords.

The previous filter status will be reverted to.

Filter keywords: filter-keywords-entered-by-the-user

No action handler that matches the filter keywords exists.

(S)

Returns to the previous status.

KAVJS2631-E

No email definition action handler matches the keywords.

The previous filter status will be reverted to.

Keywords: filter-keywords-entered-by-the-user

No action handler that matches the filter keywords exists.

(S)

Returns to the previous status.

KAVJS2632-E

An error occurred in the connected PFM-Manager.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then retry the operation. If the problem persists, check the PFM-Manager service status.

KAVJS2633-E

An error occurred in the connected PFM-Manager.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then log in to Web Console again. If the problem persists, check the PFM-Manager service status.

KAVJS2634-E

An error occurred in the connected PFM-Manager.

Maintenance information: error-code-received-from-the-Manager

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then log in to Web Console again. If the problem persists, check the PFM-Manager service status.

KAVJS2635-E

An error occurred while importing the alarm table.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then try to import the alarm table again. If the problem persists, check the PFM-Manager service status.

KAVJS2636-E

An attempt to create an alarm has failed.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then try to create the alarm again. If the problem persists, check the PFM-Manager service status.

KAVJS2637-E

An attempt to register an alarm has failed.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then perform registration or settings. If the problem persists, check the PFM-Manager service status.

KAVJS2638-E

An error occurred in the connected PFM-Manager.

Maintenance information: error-code-received-from-the-Manager

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then log in to Web Console again. If the problem persists, check the PFM-Manager service status.

KAVJS2639-E

An error occurred in the connected PFM-Manager.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Wait a while, and then log in to Web Console again. If the problem persists, check the PFM-Manager service status.

KAVJS2640-E

Failed to update the service property.

Service name: service-ID

Property name: property-name

An agent in the connected PFM - Manager is in the suspended state.

(S)

Suspends processing.

(O)

Use either the Monitoring Suspension Settings window or a command that displays the monitoring suspension settings and monitoring status to check the monitoring status of the agent. If an agent is in the suspended state, resume the monitoring of the agent. If the problem persists, disable the monitoring suspension function.

KAVJS2651-E

Use 16 characters or fewer for the user name.

The user name was not specified or the specified user name was 17 characters or more.

(O)

Use 16 characters or fewer for the user name.

KAVJS2652-E

Use 16 characters or fewer for the password.

The password was not specified or the specified password was 17 characters or more.

(O)

Use 1-16 characters for the password.

KAVJS2653-E

The specified user name contains invalid characters.

The specified user name contains characters whose ASCII code is outside the range from 0x20 to 0x7e.

(O)

Specify the user name by using characters whose ASCII code is in the range from 0x20 to 0x7e.

KAVJS2654-E

The specified password contains invalid characters.

The specified password contains characters whose ASCII code is outside the range from 0x20 to 0x7e.

(O)

Specify the password by using characters whose ASCII code is in the range from 0x20 to 0x7e.

KAVJS2655-E

The passwords entered for "Password" and "Confirm password" are different.

At least one of the entries in "Password" and "Confirm password" is incorrect.

(O)

Enter the same password for "Password" and "Confirm password".

KAVJS2656-E

An attempt to create a user has failed because the specified user is currently logged in.

The specified user cannot be overwritten because a user with the same name is already logged in.

(O)

Wait for the specified user to log out or use a different name to create the name.

KAVJS2657-E

An attempt to update a user has failed because the specified user is either currently logged in or has been deleted.

The specified user cannot be updated because the user is either currently logged in or has been deleted.

(O)

If the specified user is logged in, wait until the user logs out. Otherwise, update the navigation frame and then choose a different user.

KAVJS2658-E

An attempt to delete a user has failed because the specified user is currently logged in.

The specified user cannot be deleted because the user is currently logged in.

(O)

Wait until the user logs out.

KAVJS2659-E

An attempt to copy a user has failed because the specified user is either currently logged in or has been deleted.

The specified user cannot be copied because the user is either currently logged in or has been deleted.

(O)

If the specified user is logged in, wait until the user logs out. Otherwise, update the navigation frame and then choose a different user.

KAVJS2660-E

The user "user-name" has already been deleted.

The specified user has already deleted.

(O)

Update the navigation frame and then choose a different user.

KAVJS2661-E

An attempt to copy a user has failed because the specified user has been deleted.

A user could not be copied because the specified user has been deleted.

(O)

Update the navigation frame and then choose a different user to copy.

KAVJS2662-E

The graph library has failed to generate the image.

An I/O error occurred during an attempt to generate a graph image.

(S)

Suspends output of the report.

(O)

Restart the service, and then retry the operation from the main window. If you cannot determine the cause of the problem, collect maintenance information by using the jpcwras command, and then contact the system administrator.

KAVJS2663-E

The system does not contain the agent to be displayed.

The agent to be displayed might have been deleted from the system.

(S)

Suspends processing.

(O)

Execute a command to synchronize the service information registered in PFM - Manager and PFM - Web Console. Log in again, and then retry the operation.

KAVJS2664-E

Information was changed for the host of the agent to be displayed.

The host information for the agent to be displayed was changed.

(S)

Suspends processing.

(O)

Execute a command to synchronize the service information registered in PFM - Manager and PFM - Web Console. Log in again, and then retry the operation.

KAVJS2665-E

Failed to update the monitoring suspension settings.

Possible causes:

The agent to be updated was removed from the system.

Information was changed for the host of the agent to be updated.

(S)

Suspends processing.

(O)

Execute a command to synchronize the service information registered in PFM - Manager and PFM - Web Console. Log in again, and then retry the operation.

KAVJS2666-E

The operation cannot continue because another user is changing the monitoring suspension settings.

Another user is changing the monitoring suspension settings.

(S)

Suspends processing.

(O)

Change the monitoring suspension settings again. If another user is changing the monitoring suspension settings, you can use the Monitoring Suspension Settings window to check the status of the monitoring suspension.

KAVJS2667-E

The monitoring suspension settings of the health check agent cannot be displayed.

Unnecessary service information for a health check agent still exists.

Possible causes are as follows:

The health check function is disabled.

The host name of the monitoring manager was changed.

(S)

Suspends processing.

(O)

Delete the service information for the health check agent. Execute the command to synchronize the service information registered in PFM - Manager and in PFM - Web Console. Log in again, and then retry the operation.

KAVJS2671-E

The current password is incorrect.

The current password was not entered correctly.

(O)

Enter the current password again.

KAVJS2672-E

The specified alarm or alarm table does not exist.

The specified alarm or alarm table has been deleted, or cannot be acquired because its status is invalid.

(S)

Suspends processing.

(O)

Make sure that the specified alarm or alarm table exists.

KAVJS2673-E

Alarm condition expressions cannot be set for a different record because [State changes for each record instance] is specified in [Main Information].

Alarm condition expressions cannot be set for a different record because [State changes for each record instance] is specified in [Main Information].

(S)

Cancels processing.

(O)

If you want to set alarm condition expressions for a different record, specify [State changes for the alarm] in [Main Information].

KAVJS2674-E

The update operation cannot be performed because the destination is not the primary PFM - Manager.

The update operation cannot be performed because the destination is not the primary PFM - Manager.

(S)

Aborts processing.

(O)

Perform this operation in the PFM - Web Console host that is connected to the primary PFM - Manager.

KAVJS2675-E

Creating or editing an alarm failed because at least one bound agent does not support function-name.

Creating or editing an alarm failed because at least one bound agent does not support function-name.

(S)

Aborts processing.

(O)

If you want to use function-name, update to a version for which the agents support function-name, and then try again.

If you want to complete the creating or editing of the alarm, select setting-content, and re-register the alarm.

You can update the alarm again by clicking the Finish button.

KAVJS2676-E

The version of the connection-target PFM - Manager has been changed.

The version of PFM - Manager for the connection destination has been changed.

(S)

Aborts processing.

(O)

Restart PFM - Web Console service.

KAVJS2681-E

The format of the specified refresh interval value is invalid.

The format of the specified refresh interval is invalid.

(S)

Suspends processing.

(O)

Specify a positive integer for the refresh interval.

KAVJS2682-E

The specified refresh interval value is outside the valid range.

The specified refresh interval is outside the permitted range.

(S)

Suspends processing.

(O)

Specify a value from 10 to 3,600.

KAVJS2683-E

In [Indication settings], the value for the maximum number of records is outside the valid range.

In [Indication settings], the value for the maximum number of records is outside the valid range.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a value from 1 to maximum-value.

KAVJS2684-E

In [Indication settings], the value for the maximum number of records is invalid.

In [Indication settings], the value for the maximum number of records is invalid.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify a positive integer.

KAVJS2685-E

Select a display format (Graph, List, or Table).

A display format must be selected.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Select at least one display format.

KAVJS2686-E

In [Components], the maximum character length of a display name is 24 characters.

The display name specified in [Components] is 25 or more characters (one-byte or two-byte characters).

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify no more than 24 characters (one-byte or two-byte characters) for the display name, and then retry the operation.

KAVJS2687-E

Specify no more than 40 characters for the x-axis label in [Graph].

The specified x-axis label in [Graph] consists of 41 or more characters (one-byte or two-byte characters).

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify no more than 40 characters (one-byte or two-byte characters) for the x-axis label, and then retry the operation.

KAVJS2688-E

Specify no more than 40 characters for the y-axis label in [Graph].

The specified y-axis label in [Graph] consists of 41 or more characters (one-byte or two-byte characters).

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Specify no more than 40 characters (one-byte or two-byte characters) for the y-axis label, and then retry the operation.

KAVJS2689-E

In [Graph], data label 1 is not specified.

An attempt was made to set data label 2 without setting data label 1.

(S)

Prompts the user to re-enter the value. The program returns to the Edit Report Definitions window.

(O)

Set data label 1 before setting data label 2.

KAVJS2690-E

An attempt to change the bind settings of an alarm table for an agent has failed.

Agent name: agent-name

Possible causes are as follows:

The specified agent or alarm table has been deleted.

The number of alarms binding an agent exceeded the maximum number.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Modify the bind settings only for agents for which such processing is possible, and then display the View Results window.

(O)

Check the following:

Make sure that the alarm table and specified agent exist.

Check the agent bound to this alarm table, unbind or delete unnecessary alarms, and then try again.

Wait a while, and then try to change the bind settings of the alarm table again. If the problem persists, check the PFM-Manager service status.

KAVJS2691-E

The cache expired.

The cache used for the window used for printing the summary display has expired.

(S)

Aborts processing.

(O)

Click the anchor for the window used for printing the summary display, and display that window again.

KAVJS2692-E

The specified report name already exists. Specify another name.

The specified report name already exists in the same directory

(S)

Prompts the user to re-enter the report name. The program returns to the report name entry window.

(O)

Specify a report name that does not exist in the same directory.

KAVJS2693-E

The specified folder was not found.

Folder ID: folder-ID

The specified folder could not be obtained because it has been deleted or is in an invalid state.

(S)

Prompts the user to re-enter the report name or the report folder name.

The program returns to the report name entry window or the report folder name entry window.

(O)

Make sure that the folder exists.

KAVJS2694-E

The specified report definition was not found.

Report ID: report-ID

The specified report definition could not be obtained because it has been deleted or is in an invalid state.

(S)

Prompts the user to re-enter the report name. The program returns to the report name entry window.

(O)

Make sure that the report definition exists.

KAVJS2695-E

The report name is too long. Specify it using no more than 64 characters.

The specified report name consists of 65 or more characters.

(S)

Prompts the user to re-enter the report name. The program returns to the report name entry window.

(O)

Specify a report name that is no more than 64 characters.

KAVJS2696-E

The folder name is too long. Specify it using no more than 64 characters.

The specified folder name consists of 65 or more characters.

(S)

Prompts the user to re-enter the folder name. The program returns to the folder name entry window.

(O)

Specify a folder name that is no more than 64 characters.

KAVJS2697-E

The specified folder name already exists. Specify another name.

The specified folder name already exists in the same directory.

(S)

Prompts the user to re-enter the folder name. The program returns to the folder name entry window.

(O)

Specify a folder name that does not exist in the same directory.

KAVJS2698-E

An attempt to read a data-model file has failed.

An explanation cannot be displayed.

The data-model file is not set up.

(S)

Displays the field selection window but without any explanation.

(O)

Re-execute the setup command.

KAVJS2699-E

The screen transition is invalid. (maintenance information = maintenance-information)

An error occurred. The wizard context ID is inconsistent.

(S)

Aborts processing.

(O)

Redisplay the report again from the main window, and then edit the report definition.

KAVJS2700-E

Acquisition of the data model version failed because the Agent Collector service does not exist.

Service: service-ID-(Agent Collector service)-or-user-friendly-name-of-the-Collector-service

Acquisition of the data model version failed because the Agent Collector service was either removed or is not registered.

(S)

Suspends processing.

(O)

Verify that service-ID-(Agent Collector service)-or-user-friendly-name-of-the-Collector-service is running.

KAVJS2701-E

The specified maximum number of displayed events was invalid. Specify an integer from minimum-value to maximum-value.

The specified maximum number of events was invalid.

(O)

Specify an integer within the valid range.

KAVJS2702-E

The specified agent does not exist in the system.

Maintenance information: error-message-containing-an-agent-node-name-that-does-not-exist-in-the-system

Possible causes are as follows:

The agent has been deleted from the system.

Permission for the user to view the agent has been deleted due to a change in the configuration of the business group.

(S)

Suspends processing.

(O)

Check the following:

Make sure that the specified agent exists. If it has been deleted from the system, delete it from User Agents.

Inquire of system administrator whether user has permission to view the specified agent. If it has been deleted due to a change in the configuration of the business group, give the permission for the user to view the specified agent, or delete the agent from User Agents.

KAVJS2751-E

An attempt to retrieve the alarm table or folder to be exported has failed.

Possible causes are as follows:

The alarm table or folder to be exported has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Suspends processing.

(O)

Check the following:

Refresh the information, and make sure that the alarm table or folder to be exported exists.

Wait a while, and then try to export the alarm table again. If the problem persists, check the PFM-Manager service status.

KAVJS2752-E

An error occurred while exporting the alarm table.

Maintenance information: detailed-error-information

An error occurred while the alarm table was being exported.

(S)

Suspends processing.

(O)

Remove the cause of the problem, and try again.

KAVJS2753-E

The format of the specified file is invalid.

A file in an invalid format was specified for alarm table importing.

(S)

Suspends processing.

(O)

Specify a file that has the correct format, and then retry the operation.

KAVJS2754-E

An alarm table was specified for an agent that has not been set up.

product ID: program-ID

data model version: data-model-version

An alarm table was specified for an agent that has not been set up.

(S)

Suspends processing.

(O)

Set up the agent, and then retry the operation.

KAVJS2755-E

An error occurred while importing the alarm table.

Maintenance information: detailed-error-information

An error occurred while the alarm table was being imported.

(S)

Suspends processing.

(O)

Remove the cause of the problem, and try again.

KAVJS2756-E

The report definition or folder to be exported does not exist.

The report definition or folder to be exported does not exist.

(S)

Suspends processing.

(O)

Refresh the information, and make sure that the report definition or folder to be exported exists.

KAVJS2757-E

An error occurred while exporting report definition.

Maintenance information: detailed-error-information

An error occurred while a report definition was being exported.

(S)

Suspends processing.

(O)

Remove the cause of the problem, and try again.

KAVJS2758-E

The format of the specified file is invalid.

A file in an invalid format was specified for report definition importing.

(S)

Suspends processing.

(O)

Specify a file that has the correct format, and then retry the operation.

KAVJS2759-E

A report definition was specified for an agent that has not been set up.

Product ID: [product-ID]

DataModelVersion: [data-model-version]

A report definition was specified for an agent that has not been set up.

(S)

Suspends processing.

(O)

Set up the agent, and then retry the operation.

KAVJS2760-E

An error occurred while importing report definition.

Maintenance information: detailed-error-information

An error occurred while a report definition was being imported.

(S)

Suspends processing.

(O)

Remove the cause of the problem, and try again.

KAVJS2776-E

An unexpected error occurred during JP1 authentication.

A system error occurred during communication with the authentication server.

(O)

Contact the system administrator because the communication environment is incorrect.

KAVJS2777-E

An error occurred while attempting to establish a connection with the authentication server during JP1 authentication.

The specified authentication server is not running, or the destination host is incorrect.

(O)

Make sure the authentication server is correct and that its destination host is running.

KAVJS2778-E

An unexpected error occurred during JP1 authentication.

An error occurred while initializing the JP1 authentication API.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJS2779-E

An error occurred while attempting to establish a connection with the authentication server during JP1 authentication.

A connection could not be made with the specified authentication server because the authentication server name was invalid.

(O)

Make sure the destination host of the authentication server specified in the Manager is correct.

KAVJS2780-E

You do not have the necessary permissions to access PFM.

According to the specified authentication server, the user does not have the necessary permissions to access PFM.

(O)

Log in as a user with the necessary permissions, and then confirm the user settings on the authentication server.

KAVJS2781-E

An attempt at single sign-on failed because authentication information issued from a linked program was invalid.

An attempt at single sign-on failed because authentication information issued from a linked program was invalid. PFM and the related program might be using different authentication servers.

(O)

Log in by entering the user name and the password, and then confirm the user settings on the authentication server.

KAVJS2782-E

An attempt at single sign-on failed because PFM-Manager does not support single sign-on.

The authentication mode of PFM-Manager is set to not allow single sign-on.

(O)

Log in by entering the user name and the password.

KAVJS2826-E

The specified maximum value is less than or equal to the minimum value.

The specified maximum value is less than or equal to the minimum value.

(S)

Suspends processing.

(O)

Specify a maximum value that is larger than the minimum value.

KAVJS2827-E

The range is too small.

The difference between the maximum and minimum values is too small.

(S)

Suspends processing.

(O)

Adjust the minimum or maximum value so that the range is valid.

KAVJS2829-E

The format of the specified value maximum-or-minimum-value is invalid.

The format of the indicated maximum or minimum value is invalid.

(S)

Suspends processing.

(O)

Specify the value as a floating point number.

KAVJS2830-E

Communication with Manager failed. The report cannot be displayed.

Possible causes are as follows:

PFM - Manager stopped.

PFM - Manager is taking a long time to respond.

A communication error has occurred.

(S)

Suspends processing.

(O)

Make sure that Manager is running and that the Web Console host can communicate with the Manager host, and then try to display the report again.

KAVJS2831-E

Communication with Manager failed. The report cannot be output.

Possible causes are as follows:

PFM - Manager stopped.

PFM - Manager is taking a long time to respond.

A communication error has occurred.

(S)

Suspends processing.

(O)

Make sure that Manager is running and that the Web Console host can communicate with the Manager host, and then try to output the report again.

KAVJS2832-E

The value of the specified value maximum-or-minimum-value is invalid.

The specified maximum or minimum value is invalid.

(S)

Suspends processing.

(O)

Reduce the absolute value of maximum-or-minimum-value.

KAVJS2833-E

The range is too large.

The difference between the maximum value and the minimum value is too large.

(S)

Suspends processing.

(O)

Adjust the minimum or maximum value so that the range is valid.

KAVJS2834-E

The bound agent(s) cannot be displayed.

Alarm table name: alarm-table-name

Possible causes are as follows:

The alarm tables might have not existed.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Cancels processing.

(O)

Check the following:

Make sure the selected alarm table has not already been deleted.

Wait a while, and then try to display the bound agent again. If the problem persists, check the PFM-Manager service status.

KAVJS2835-E

An attempt to change the bind settings of an alarm table has failed.

Agent name: agent-name

Possible causes are as follows:

The specified agent or alarm table has been deleted.

The number of alarms binding an agent exceeded the maximum.

The specified agent does not support alarm notifications of state changes for each instance.

(S)

Changes the bind settings only for agents whose settings can be changed, and then finishes processing.

(O)

Perform the following:

Make sure that the alarm table and specified agent exist.

Check the agent bound to this alarm table, unbind or delete unnecessary alarms, and then try to change the bind settings of the alarm table again.

Check the version of the agent bound to this alarm table, and then try to change the bind settings of the alarm table again.

KAVJS2836-E

An attempt to change the bind settings of an alarm table for an agent has failed.

Possible causes are as follows:

The specified agent or alarm table has been deleted.

The response from PFM-Manager is taking too long, or PFM-Manager stopped.

(S)

Changes the bind settings only for agents whose settings can be changed, and then finishes processing.

(O)

Check the following:

Make sure that the alarm table and specified agent exist.

Wait a while, and then perform the bind settings of an alarm table. If the problem persists, check the PFM-Manager service status.

KAVJS2837-E

An attempt to import an alarm definition has failed.

Alarm table name: maintenance-information

An error occurred during update of an alarm table.

(S)

Suspends processing.

(O)

Check the connecting PFM-Manager service status, and then retry the operation.

If the problem persists, contact the system administrator.

KAVJS2838-E

An attempt to register an alarm has failed.

Processing will now stop because there was no response from PFM-Manager during an attempt to register an alarm.

(S)

Suspends processing.

(O)

Wait a while, and then perform registration or settings. If the problem persists, check the PFM-Manager service status.

You can re-register the alarm by clicking the Finish button.

KAVJS2839-E

An attempt to update an alarm has failed.

Processing will now stop because there was no response from PFM-Manager during an attempt to update an alarm.

(S)

Suspends processing.

(O)

Wait a while, and then perform update processing. If the problem persists, check the PFM-Manager service status.

If the alarm is bound to an agent, PFM-Manager might be in the Busy status because the agent service is not responding. Check the service status of the agent to which the alarm is bound.

You can re-update the alarm by clicking the Finish button.

KAVJS2840-E

The number of alarms binding an agent exceeded the maximum number.

The number of alarms binding an agent exceeded the maximum.

(S)

Suspends processing.

(O)

Check the agent bound to this alarm table, unbind or delete unnecessary alarms, and then try again.

KAVJS4001-E

A request parameter is invalid.

Parameter name: parameter-name

An invalid request was received from the window.

(S)

Suspends processing.

(O)

Contact the system administrator.

KAVJS4002-E

The product ID is not specified for the report definition.

Report name: report-name

An attempt was made to open a report definition without a specification of the product id.

(S)

Suspends processing.

(O)

Check the report definition.

KAVJS4003-E

The record ID is not specified for the report definition.

Report name: report-name.

An attempt was made to open a report definition without a specification of the record id.

(S)

Suspends processing.

(O)

Check the report definition.

KAVJS4004-E

The record does not have a field.

Record: record-name

Report definition report-name

An attempt was made to access a report definition with a record that does not have a field.

(S)

Suspends processing.

(O)

Check the report definition.

KAVJS4006-E

Session information from the Web browser has become invalid.

Maintenance information:maintenance-information

Processing has been suspended because the session information held by the browser became invalid.

(S)

Suspends processing.

(O)

Close all Web browsers accessing PFM - Web Console, restart the Web browser, and then log in again.

KAVJS4007-E

An unexpected error occurred.

Maintenance information:maintenance-information

An unexpected error occurred.

(S)

Aborts processing.

(O)

Login to PFM - Web Console again, and then retry the operation.

If the problem persists, restart the service.

If the problem persists after restart the service, contact the system administrator.

KAVJS4008-E

An internal inconsistency was detected.

Maintenance information:maintenance-information

An internal conflict was detected in the system.

(S)

Suspends processing.

(O)

Contact the system administrator.

KAVJS4009-E

A Manager access error occurred.

Maintenance information:maintenance-information

A Manager access error occurred.

(S)

Suspends processing.

(O)

Make sure communication with the Manager host can be performed correctly, and that the Manager is running.

KAVJS4010-E

The field drilldown failed.

Row ID:row-identification-key

The row ID of the field drilldown target is too long. The URL was not fully specified.

(S)

Suspends processing.

(O)

Revise the report definition, and then reduce the number of field drilldown settings.

KAVJS4011-E

Initialization of the bookmark function has failed.

Maintenance information: maintenance-information

Initialization of the bookmark function has failed.

(S)

Suspends processing.

(O)

Make sure the storage destination for the bookmark information specified in "config.xml" is the directory, and that the permission settings to access this directory are correct.

KAVJS4012-E

The cache expired.

The cache for reports has expired.

(S)

Suspends processing.

(O)

Reselect the report from the Main window. Alternatively, close any unnecessary reports and Print windows, and then retry the operation.

For a real-time report, see the Help to check the items in the initialization settings file (config.xml) and the data cache, and increase the value of realtimeCacheInterval as necessary.

KAVJS4013-E

An attempt to register an alarm or set an action has failed.

Maintenance information: internal-processing-that-caused-the-error

An attempt to register an alarm failed because there was no response from PFM-Manager.

(S)

Suspends processing.

(O)

Wait a while, and then perform registration or settings. If the problem persists, check the PFM-Manager service status.

If the alarm is registered in the alarm tree, the action failed to be set. Set the action from the Edit menu.

If the alarm is not registered in the alarm tree, re-register the alarm.

KAVJS4014-E

An attempt to update an alarm has failed.

(The alarm was not updated, or an action setting was lost.)

Maintenance information: internal-processing-that-caused-the-error

An attempt to update an alarm failed because there was no response from PFM-Manager.

(S)

Suspends processing.

(O)

Wait a while, and then perform update processing. If the problem persists, check the PFM-Manager service status.

If the alarm is bound to an agent, PFM-Manager might be in the Busy status because the agent service is not responding. Check the service status of the agent to which the alarm is bound.

You can update the alarm again by clicking the Finish button.

KAVJS4015-E

An attempt to update an alarm has failed.

(The alarm has been deleted, or an action setting was lost.)

Maintenance information: internal-processing-that-caused-the-error

An attempt to update an alarm failed because there was no response from PFM-Manager.

(S)

Suspends processing.

(O)

Wait a while, and then perform update processing. If the problem persists, check the PFM-Manager service status.

If the alarm is bound to an agent, PFM-Manager might be in the Busy status because the agent service is not responding. Check the service status of the agent to which the alarm is bound.

If the alarm is not registered in the alarm tree, register the alarm.

KAVJS4016-E

An error occurred while starting PFM - Web Console.

An error occurred while starting the service for the following reasons.

The user does not have permission to start service. (UNIX only)

The service does not exist.

The service is invalid.

The application is not installed correctly.

(S)

Aborts processing.

(O)

As for the start authority of the default of service, nobody/root is set for UNIX.

Please change User and Group of the /opt/jp1pcwebcon/CPSB/httpsd/conf/httpsd.conf file to the group to which users whom the system has other than root and the user belong, and execute the jpcwstart command again when failing because of this setting.

Still, when becoming the same error, contact the system administrator because the system environment is incorrect.

For Windows, contact the system administrator because the system environment is incorrect.

KAVJS4017-E

An error occurred in the connected PFM-Manager.

Maintenance information: processing-that-resulted-in-an-error-and-its-error-code

An error occurred during processing on the connected PFM - Manager.

(S)

Suspends processing.

(O)

Make sure that the connected PFM-Manager is running normally, and then retry the operation.

If the problem persists, contact the system administrator.

KAVJS4018-E

An attempt to display a report failed.

Maintenance information: processing-that-resulted-in-an-error-and-its-error-code

An error occurred in the connected PFM - Manager.

This error might occur if you attempt to output reports by executing successive jpcrpt commands in a short time.

(S)

Suspends processing.

(O)

Make sure that the jpcrpt command is not being executed.

If the jpcrpt command is being executed, wait until it finishes, and then try to display the report again.

If the problem persists, contact the system administrator.

KAVJS5001-I

No record was fetched. The report cannot be displayed.

Probable causes:

The Agent was not running during the report period.

The Agent was in the suspended state running during the report period.

A requested record was not collected during the report period.

No collected data meets the filtering condition.

(S)

Suspends processing.

(O)

Make sure that:

The Agent is running.

The Agent is set up to collect the required records.

Modify the report filtering condition if necessary.

Modify the report display period if necessary.

KAVJS5002-I

There is no record. A report cannot be displayed.

One of the following is the most likely cause:

The Agent is not running.

There is no data that satisfies the filter conditions for a report definition.

(S)

Suspends processing.

(O)

Make sure that the agent is running. If the agent is not running, restart the agent correctly, and then re-execute or refresh the report.

If the data is currently being updated automatically, a report will be displayed when the data is obtained at the next update.

Review the filter conditions of the report definition.

KAVJS5003-I

No record was fetched. The report cannot be displayed.

Probable causes:

The Report was not set in the combination bookmark.

The Agent was not running during the report period.

A requested record was not collected during the report period.

No collected data meets the filtering condition.

(S)

Cancels processing.

(O)

Make sure that:

The Report is set in the combination bookmark.

The Agent is running.

The Agent is set up to collect the required records.

Modify the report filtering condition if necessary.

KAVJS6551-I

Even if any JP1 event commands are defined, PFM - Web Console reports will not be display by JP1/IM - Manager, because no report has been specified.

No report to be displayed has been set.

(O)

Specify a report to be displayed.

KAVJS6552-I

The email settings in the action definition will be cleared because the value of [Email] in [Capabilities] in the Action Handler properties is set to "No".

In the Action Handler properties, Email in Capabilities is set to No.

(O)

Check and, if necessary, revise the Capabilities settings in the Action Handler properties.

KAVJS6553-I

No fields matched the [Keywords to find] entry.

The [Keywords to find] entry does not exist in a field name and a field explanation.

(S)

Aborts processing.

(O)

Change the [Keywords to find] entry, and then search again.

KAVJS6554-I

The number of fields that matched the [Keywords to find] entry exceeded limit.

The search has been stopped.

The number of fields that matched the [Keywords to find] entry exceeded the limit.

(S)

Aborts search processing.

(O)

Modify the [Keywords to find] entry to narrow the search.

KAVJS6555-I

maximum-number-of-reports-for-the-tiling-display reports are displayed because the maximum number(maximum-number-of-reports-for-the-tiling-display) of registered reports that can be displayed was exceeded.

The number of registered reports registered in one bookmark exceeds the maximum number displayable in the tiling display.

(S)

Continues processing for maximum-number-of-reports-for-the-tiling-display reports.

(O)

Set the number of registered reports to maximum-number-of-reports-for-the-tiling-display or fewer.

KAVJS6556-I

There is no monitoring-target data to be summarized.

Select the folder containing the data.

Under the specified folder, there is no data to be summarized.

(S)

Aborts processing.

(O)

Under the specified folder, register one or more agents.

KAVJS6557-I

The operational status of the server and agent cannot be monitored because the health check service is disabled.

The Manager at the connection destination does not provide the health check service, or the health check service is disabled.

(S)

Aborts monitoring of the operational status of the server and agent.

(O)

Make sure that:

The setting of the health check function of Manager is enabled.

The health check Agent is running.

KAVJS6558-I

The operational status of the agent cannot be monitored because the [Monitoring Level] setting of the health check function is not set to [Service].

The setting of the health check function for the connection-target Manager is not set to [Service].

(S)

Aborts monitoring of the operational status of the agent.

(O)

Set the setting of the health check function to [Service].

KAVJS6559-I

Under the specified folder, there are no agents to which alarms can be bound.

Under the specified folder, there are no agents to which alarms can be bound.

(S)

Aborts alarm monitoring.

(O)

Agents to which alarms can not be bound are not targets in the alarm monitoring.

KAVJS6560-I

Under the specified folder, there are Group Agents only.

Under the specified folder, there are Group Agents only.

(S)

Aborts monitoring of the operational status of the server and agent.

(O)

Group Agents are not targets in the operational status of the server and agent.

KAVJS6561-I

No process-list-type matched the search keywords.

A word specified as a filter keyword does not exist in the process list.

(S)

Suspends processing.

(O)

Retry the search using different keywords.

KAVJS6562-I

The number of lines of data to be output exceeds the maximum number of lines (maximum-number-of-lines-for-the-output-table-data-in-the-print-window-specified-in-config.xml) for a table.

The data will be output to the table up to the maximum number of lines.

The number of lines of data to be output exceeds the maximum number of lines (maximum-number-of-lines-for-the-output-table-data-in-the-print-window-specified-in-config.xml) for a table.

The data will be output to the table up to the maximum number of lines.

(S)

Outputs the table data up to the maximum number of lines.

(O)

Set the number of lines of data to be output for a table to no more than the maximum-number-of-lines-for-the-output-table-data-in-the-print-window-specified-in-config.xml.

KAVJS6563-I

The number of drilldown data used exceeds the maximum number of areas(maximum-number-of-drilldown-data-that-can-be-used-for-a-graph) for a graph.

The display function of a drilldown is invalidated.

The number of drilldown data items used for a graph exceeds the maximum number of data items (maximum-number-of-drilldown-data-that-can-be-used-for-a-graph).

The field drilldown display function will be disabled.

(S)

Disables the field drilldown display function for a graph.

(O)

Shorten the report display period in the report definition or unbind the drilldown report defined for the fields displayed in the graph, and then display the report again.

KAVJS6564-I

The number of graph data used exceeds the maximum number of data (maximum-number-of-plots-available-for-autolabel-display) can be output autolabel for a graph.

The display function of a autolabel is invalidated.

The number of data items used in a graph exceeds the maximum number of data items (maximum-number-of-plots-available-for-autolabel-display) available for autolabel display.

The autolabel display function for a graph is disabled.

(S)

Disables the autolabel display function for the graph.

(O)

Check and, if necessary, revise the report display period in the report definition. Then, display the report again.

KAVJS6565-I

An user may be already logged in by the web browser on the same terminal. Do you login forcibly?

A user might be already logged in by a Web browser on the same terminal.

(O)

Click [execute] button to login forcibly. In that case, the previous user will be logged out. Click [close] button to cancel login and close the window.

KAVJS6566-I

One or more selected agents were hidden by the filter.

One or more selected agents were hidden by the filter.

(S)

Displays only the agents that match the filter keywords without changing the selection status.

(O)

To perform an operation on selected agents that are hidden, either specify keywords to search for the agents or undo the filter that was applied to the agents, and then perform the intended operation.

KAVJS6567-I

One or more selected reports were hidden by the filter.

One or more selected reports were hidden by the filter.

(S)

Displays only the reports that match the filter keywords without changing the selection status.

(O)

To perform an operation on selected reports that are hidden, either specify keywords to search for the reports or undo the filter that was applied to the reports, and then perform the intended operation.

KAVJS6569-I

No agents are in the selected folder.

No agents exist in the selected folder.

(S)

Suspends processing.

(O)

Select a folder that contains one or more agents.

KAVJS6570-I

There is an agent whose monitoring status is unknown.

There is an agent whose monitoring status is unknown.

(S)

Continues processing.

(O)

Check the version and service status of the agent whose monitoring status is displayed with a question mark (?).

If the agent does not support the monitoring suspension function, upgrade it to a version that supports the function.

If the agent is not running, the status will be updated when the agent starts up.

If the agent is running or is operating in stand-alone mode, wait a while, and then refresh the information. If the problem persists, check the status of the communication between the connected PFM - Manager and the agent.

KAVJS6701-I

There are no events.

One of the following is the most likely cause:

The Master Store service is not running.

No data satisfies the filter conditions for the displayed report settings.

No events were generated during the specified period.

(S)

Suspends processing.

(O)

Make sure that the Master Store service is running.

Check the selected agents.

Review the filter conditions in the report display settings.

KAVJS6702-I

An agent that cannot unbind all alarm tables that are bound to it exists.

Agent name: agent-name

Some of the bound alarm tables are not displayed because the selected agent has a different data model version.

(S)

Continues processing.

(O)

To unbind all currently bound alarm tables, you must match the data model versions of selected agents.

KAVJS6703-I

Specified user is already logged in. Do you login forcibly?

The specified user has already logged in.

(S)

Waits for a response.

(O)

Specified user is already logged in. Click [Execute] button to login forcibly. In that case, the previous user will be logged out. Click [Close] button to cancel login and close the window.

KAVJS6704-I

The system will connect to PFM. Log in with a PFM user acount.

This message appears when the service is started from another product that is not linked with JP1 authentication.

(O)

Log in by using a user name and password for a PFM user. If you want to skip the PFM login operation, change the authentication for PFM to JP1 authentication mode.

KAVJS6705-I

The version of the connection-target PFM - Manager has been changed.

The version of PFM - Manager for the connection destination has been changed.

(S)

Continues processing.

(O)

Restart PFM - Web Console service.

Click [Execute] button to login without restarting. In that case, some functions of PFM - Web Console may not run normally.

KAVJS6801-I

The manual has not been set up.

The manual files were not copied to the "doc" directory in the installation directory.

(S)

Suspends processing.

(O)

Copy the manual files to the "doc" directory in the installation directory, and then restart the service.

KAVJT0003-E

An attempt to start the service has failed.

An attempt to start the service has failed for the following reasons.

The user does not have permission to start service. (UNIX only)

The service does not exist.

The service is invalid.

The application is not installed correctly.

(S)

Stops execution of the command.

End code 4 is returned.

(O)

As for the start authority of the default of service, nobody/root is set for UNIX.

Please change User and Group of the /opt/jp1pcwebcon/CPSB/httpsd/conf/httpsd.conf file to the group to which users whom the system has other than root and the user belong, and execute the jpcwstart command again when failing because of this setting.

Still, when becoming the same error, contact the system administrator because the system environment is incorrect.

For Windows, contact the system administrator because the system environment is incorrect.

KAVJT0004-E

An attempt to stop the service has failed.

An attempt to stop the service has failed.

This message is displayed because stop process is taking too long. Possible causes is that user execute jpcwstop command when operating PFM - Web Console.

In this case, the service will stop after displaying this message.

(S)

Stops execution of the command.

End code 4 is returned.

(O)

Please execute the jpcwstop command again for a while after putting time. It is not necessary to deal because it succeeds in the stop of service when the message of KAVJT5004-I is output. Please contact the system administrator when you cannot stop serving even if the jpcwstop command is executed again.

KAVJT0005-E

An argument is invalid.

usage: jpcwras <directory>

<directory>: Specify the existing output directory.

An argument is invalid.

(S)

Cancels command execution and returns termination code 1.

(O)

Check the argument.

KAVJT0006-E

Output directory does not exist.

Output directory does not exist.

(S)

Stops execution of the command. End code 4 is returned.

(O)

Confirm if the directory specified in the argument of the jpcwras command exists.

KAVJT0007-E

An error occurred during writing.

A write error occurred.

(S)

Cancels command execution and returns termination code 3.

(O)

Check the available space on the drive that contains the directory specified in the argument of the jpcwras command.

Check the access permission for the directory specified in the argument of the jpcwras command.

KAVJT0008-E

The setup directory does not exist.

The setup directory does not exist.

(S)

Cancels command execution and returns termination code 1.

(O)

Check if the setup directory exists at the system installation directory.

KAVJT0009-E

An error occurred during processing archive-file-name.

An error occurred while the archive file was being processed.

(S)

Starts processing the next Agent archive file. The system returns termination code 3.

(O)

Eliminate the cause of the error and then re-execute the command.

KAVJT0010-E

The destination directory does not exist.

The destination directory does not exist.

(S)

Cancels command execution and returns termination code 4.

(O)

Check if the CPSB/CC/web/containers/PFMWebConsole/webapps/PFMWebConsole/images/products directory exists in the system installation directory.

KAVJT0011-E

The output-destination directory is not empty.

The output-destination directory is not empty.

(S)

Cancels command execution and returns termination code 5.

(O)

Specify an empty output-destination directory.

KAVJT0012-E

An argument is invalid.

usage: jpcwstart

An argument is invalid.

(S)

Cancels command execution and returns termination code 5.

(O)

Check the argument.

KAVJT0013-E

An argument is invalid.

usage: jpcwstop [-immediate]

An argument is invalid.

(S)

Stops execution of the command.

End code 5 is returned.

(O)

Please confirm an argument.

KAVJT0014-E

The file for processing does not exist.

The archive file does not exist.

(S)

Cancels command execution and returns termination code 5.

(O)

Check if the archive file exists.

KAVJT0015-E

An argument is invalid.

usage: jpcwagtsetup

An argument is invalid.

(S)

Cancels command execution and returns termination code 6.

(O)

Check the argument.

KAVJT0016-E

The descriptions directory does not exist.

The descriptions directory does not exist.

(S)

Cancels command execution and returns termination code 1.

(O)

Check if the PR_HOME environment variable has been defined or if the descriptions directory exists in the system installation directory.

KAVJT0017-E

Memory has become insufficient. (available-memory-size bytes)

A memory shortage occurred during command execution.

(S)

Cancels command execution and returns termination code 7.

(O)

Exit unneeded applications and windows to obtain more memory.

KAVJT0018-E

An unexpected error occurred.

Maintenance information: maintenance-information

An unexpected error occurred

(S)

Cancels command execution and returns termination code 8.

(O)

This is a system environment error; contact the system administrator.

KAVJT0019-E

The wegetinfo.exe file was not found.

The wegetinfo.exe file cannot be found.

(S)

Cancels command execution and returns termination code 9.

(O)

Check if the wegetinfo.exe file exists in the lib directory in the installation directory.

KAVJT0023-E

The properties directory does not exist.

The properties directory does not exist.

(S)

Cancels the command execution.

Returns termination code 1.

(O)

Make sure that the properties directory does not exist in the installation directory for the system.

KAVJT2501-E

The PFM - Web Console backup of definition information ended abnormally.

The PFM - Web Console backup of definition information ended abnormally.

(S)

Cancels command execution and returns a termination code.

(O)

Check and correct the problem, and then re-execute the command. To determine the cause of the problem, check the message output prior to this message.

KAVJT2502-E

An argument is invalid.

An argument is invalid.

(S)

Cancels command execution and returns termination code 1.

(O)

Check the argument.

KAVJT2503-E

An attempt to access the specified directory failed.

The specified directory does not exist or was not accessible.

(S)

Cancels command processing and returns termination code 1.

(O)

Make sure that the specified directory exists and is accessible, and then re-execute the command.

KAVJT2504-E

The specified directory is not empty.

The specified directory is not empty.

(S)

Cancels command processing and returns termination code 4.

(O)

The specified directory must be an empty directory. Check the contents of directories, and specify an empty directory.

KAVJT2505-E

The specified directory name is invalid.

The specified directory name is too long.

(S)

Cancels command processing and returns termination code 1.

(O)

Specify the correct directory name, and then re-execute the command.

KAVJT2506-E

An attempt to create the directory failed.

An attempt to create a directory failed.

(S)

Cancels command execution and returns termination code 3.

(O)

Check the access permission for the directory specified by the command argument. Check the free space of the drive on which the directory specified by the command argument resides.

KAVJT2507-E

The specified directory name is included unavailable character.

The specified directory name includes an unavailable character.

(S)

Cancels command processing and returns termination code 1.

(O)

Specify the correct directory name, and then re-execute the command.

KAVJT2508-E

You do not have permission to execute the command.

You do not have permission to execute the command.

(S)

Stops execution of the command. End code 2 is returned.

(O)

Check the permission to execute the command.

KAVJT2510-E

The system environment is incorrect.

The system environment is invalid. A system file was deleted illegally or its access permission was changed.

(S)

Cancels command execution and returns termination code 100.

(O)

Re-install the application.

KAVJT2511-E

Memory has become insufficient.

A memory shortage occurred during command execution.

(S)

Cancels command processing and returns termination code 200.

(O)

Exit unneeded applications and windows to obtain more memory.

KAVJT2512-E

The disk capacity is insufficient.

File access failed due to a shortage of disk space.

(S)

Cancels command processing and returns termination code 210.

(O)

Check the free space of the drive on which the directory specified by the command argument resides.

KAVJT2513-E

An attempt to back up the file failed. (path=path)

path : path

An attempt to back up a file in the folder indicated by path failed.

(S)

Cancels command execution and returns termination code 235.

(O)

Delete everything in the backup directory, and then re-execute the command.

KAVJT2514-E

An unexpected exception occurred.

An unexpected error occurred.

(S)

Cancels command processing and returns termination code 255.

(O)

Contact the system administrator.

KAVJT2515-E

An attempt to access a file or directory failed. (path=path)

An attempt to access a file or directory failed.

(S)

Cancels command processing and returns termination code 202.

(O)

Make sure that you can correctly access path, and then re-execute the command. If multiple attempts to execute the command fail, check the backup procedure in the manual and manually back up all the definition information.

KAVJT2516-E

The configuration file is invalid.

The initialization file (config.xml) is invalid.

(S)

Cancels command processing and returns termination code 101.

(O)

Check whether the service can start. If it cannot start, check and, if necessary, revise the settings in the initialization file (config.xml).

KAVJT5001-I

The service started successfully.

The service started successfully.

(S)

End code 0 is returned.

KAVJT5002-I

The service has already started.

The service has already started.

(S)

End code 1 is returned.

KAVJT5003-I

The service stopped successfully.

The service stopped successfully.

(S)

End code 0 is returned.

KAVJT5004-I

The service has already stopped.

The service has already stopped.

(S)

End code 3 is returned.

KAVJT5005-I

jpcwras started.

The jpcwras command is starting.

(S)

Starts the jpcwras processing.

KAVJT5006-I

jpcwras succeeded.

The jpcwras command terminated normally.

(S)

Returns termination code 0.

KAVJT5007-I

jpcwagtsetup finished successfully. Restart the service that applies the agent configuration information.

The jpcwagtsetup command terminated normally. To apply the agent configuration information, restart the service.

(S)

Returns termination code 0 or 3.

KAVJT5008-I

archive-file-name was processed.

Processing of the indicated archive file has been completed.

(S)

Starts processing the next Agent archive file.

KAVJT5009-I

image-file-name was processed.

The processing of the image file succeeded.

(S)

The processing of the next image file has begun.

KAVJT5010-I

imgsetup finished successfully. Restart the service that applies the images.

imgsetup finished successfully. Restart the service that applies the images.

(S)

End code 0 is returned.

KAVJT6501-I

The PFM - Web Console backup of definition information will now start.

The PFM - Web Console backup of definition information will now start.

(S)

Continues command processing.

KAVJT6502-I

The PFM - Web Console backup of definition information ended normally.

The backup of PFM - Web Console definition information ended normally.

(S)

Ends command processing.

KAVJT6551-W

Backup processing of definition information is skipped. (path=path)

An attempt to access the path specified for bookmarkRepository or processMonitoringTemplatesRepository in the initialization file (config.xml) failed.

(S)

Continues processing of the command and returns termination code 15.

(O)

If you executed the command on the standby node, ignore this message.

If you executed the command on a machine other than the standby node, check the following, delete everything in the backup directory, and then re-execute the command:

Confirm that the path specified for bookmarkRepository or for processMonitoringTemplatesRepository in the initialization file (config.xml) exists.

KAVJV2501-E

The systemDef.properties file could not be found.

The systemDef.properties file does not exist.

(S)

Ignores the definition file and continues processing.

(O)

Reinstall the product.

KAVJV2502-E

There is no file in the path value-specified-as-file-name.

The file is not stored at the correct location.

(S)

Ignores the definition file and continues processing.

(O)

Place the file into the path value-specified-as-file-name.

KAVJV2503-E

An attempt to read the file-path file has failed.

The user does not have access permission for the file.

(S)

Ignores the definition file and continues processing.

(O)

Make sure you can access the file.

KAVJV2504-E

An I/O error occurred with the file-path file. Error information: error-information

An I/O error occurred during processing.

(S)

Ignores the definition file and continues processing.

(O)

Make sure the file is valid.

KAVJV2505-E

There is a syntax error in the specification of a property value in the file-path file. The specification (property-name=value) will be ignored.

The specified property value contains a syntax error.

(O)

Revise the specification of the property value.

KAVJV2506-E

The specification for the target node node-name in the file-path file is duplicated. The specification (property-name=value) will be ignored.

The target node is specified more than once.

(O)

Delete the duplicated specification.

KAVJV2507-E

The selected property will be ignored because it does not exist in the distribution-destination service. (distribution service = service-name, ignored property = property-name)

The selected property does not exist in the destination service.

KAVJV2551-E

The data file of the baseline was not read correctly.

Node name: node-name

File path: actual-path-name-of-data

The data file is corrupted or does not exist.

(S)

Cancels processing.

(O)

Delete the node of the baseline, or register the baseline and then overwrite the registration.

KAVJV2552-E

An attempt to initialize the report cache file manager has failed.

The directory for storing the report cache file cannot be created.

Path: path-to-the-save-directory

(S)

Stops the startup processing.

(O)

Check whether the location specified for storing the report cache file is a directory, and whether you have appropriate access permissions.

KAVJV2553-E

An attempt to initialize the report cache file manager has failed.

The location specified for storing the report cache file is not a directory.

Path: path-to-the-save-directory

(S)

Stops the startup processing.

(O)

Check whether the directory path-to-the-save-directory exists.

KAVJV2554-E

The directory for storing the report cache file cannot be created.

Directory for storing the report cache file: path-to-the-save-directory

A possible cause of this error is as follows:

The path to the directory for storing the report cache file exceeds 150 characters.

(S)

Stops the startup processing.

(O)

Specify a directory for storing the report cache file whose path does not exceed 150 characters, and then restart the service.

KAVJV2555-E

An attempt to initialize the system has failed.

Directory: set-directory

The directory for storing application definition templates could not be created.

(S)

Stops the startup processing.

(O)

Check whether you have access permissions for the directory set-directory.

KAVJV2556-E

An attempt to initialize the system has failed.

Directory: set-directory

The location specified for storing application definition templates is not a directory.

(S)

Stops the startup processing.

(O)

Check whether set-directory is a directory.

KAVJV2557-E

An attempt to initialize the system has failed.

Directory: set-directory

Possible causes of this error are as follows:

The path to the directory for storing application definition templates exceeds 100 characters.

The directory for storing application definition templates is not accessible.

(S)

Stops the startup processing.

(O)

Eliminate whatever is preventing access to the directory for storing application definition templates, and then restart the service.

Specify a directory for storing application definition templates whose path does not exceed 100 characters, and then restart the service.

KAVJV2558-E

The directory for storing the report cache file could not be deleted after maximum-number-of-attempts-for-deletion-by-monitoring attempts. Deletion will be skipped.

Directory: directory-failed-to-be-deleted

All the attempts (up to the maximum number) to delete the directory by monitoring failed.

(S)

The directory will be deleted the next time the service starts.

(O)

Restart the service. If the directory still cannot be deleted, delete it manually.

KAVJV2559-E

An attempt to initialize the system has failed.

Directory: set-directory

An attempt to initialize the system has failed.

(S)

Stops the startup processing.

(O)

Check whether the location for storing the application definition templates specified in config.xml is a directory, and that you have appropriate access permissions.

KAVJV2560-E

An unexpected error occurred during initialization of the application definition template manager.

Module name: PROCESSMONITORING

Class name: causal-class-name

Maintenance information: cause (maintenance-message)

An unexpected error occurred during system initialization.

(S)

Stops the startup processing.

(O)

Contact the system administrator.

KAVJV2561-E

Initialization of the report cache file function has failed.

Maintenance information: maintenance-information

Initialization of the report cache file function has failed.

(S)

Suspends processing.

(O)

Check whether the location for storing the report cache file specified in config.xml is a directory, and that you have appropriate access permissions.

KAVJV2562-E

An unexpected error occurred during initialization of the report cache file function.

Module name: REPORTCACHEFILE

Class name: causal-class-name

Maintenance information: cause (maintenance-message)

An unexpected error occurred during system initialization.

(S)

Stops the startup processing.

(O)

Contact the system administrator.

KAVJV2563-E

An attempt to initialize the report cache file function has failed.

The directory for storing the report cache file could not be created.

Path: work-directory-path-name

(O)

Check whether the location specified for storing the report cache file is a directory, and that you have appropriate access permissions.

KAVJV2564-E

An attempt to initialize the report cache file function has failed.

The location specified for storing the report cache file is not a directory.

Path: work-directory-path-name

(S)

Suspends processing.

(O)

Check whether the directory work-directory-path-name exists.

KAVJV2701-E

A Manager shutdown was detected. Events can no longer be monitored.

View Server may have been stopped or restarted.

(S)

Attempts to reconnect at Event Monitor's automatic refresh interval.

(O)

Confirm that Manager has restarted, and then log in to Web Console again.

KAVJV4001-E

During the initialization, an unexpected error occurred.

Module name: VSA

Class name: class-name

Maintenance information: maintenance-information

An unexpected error was detected during system initialization.

(O)

Contact the system administrator.

KAVJV4002-E

During the initialization, an unexpected error occurred.

Module name: VSABASE

Class name: class-name

Maintenance information: maintenance-information

An unexpected error was detected during system initialization.

(O)

Contact the system administrator.

KAVJV4003-E

During initialization of the bookmark manager, an unexpected error occurred.

Module name: BOOKMARK

Class name: class-name

Maintenance information: maintenance-information

An unexpected error was detected during system initialization.

(O)

Contact the system administrator.

KAVJV4004-E

During initialization of the bookmark manager, an error occurred.

The bookmark work directory cannot be generated.

Path name: path-name

(O)

Make sure the creation destination for the bookmark work directory is the directory, and that the permission settings to access the bookmark work directory are correct.

KAVJV4005-E

Initialization of the bookmark manager has failed.

The bookmark work directory is not a directory.

Path name: path-name

(S)

Suspends processing.

(O)

Check whether the directory path-name exists.

KAVJV4006-E

The value specified for <base-pattern> in the initial settings file is invalid.

Format-set ID: ID

An undefined format-set ID is specified in <format-set>.

(S)

Suspends processing.

(O)

Make sure that the value of <base-pattern> in the initial settings file is correct.

KAVJV4007-E

Resource generation has failed.

The tree could not be displayed because the attempt to collect tree information failed.

(S)

Suspends processing.

(O)

Contact the system administrator because the system environment is incorrect.

KAVJV4008-E

The specification of the date format is invalid.

Attribute name: attribute-name

Attribute value: attribute-value

The value of the date format specified in the initial settings file is invalid.

(S)

Suspends processing.

(O)

Check the date format specified in the initial settings file.

KAVJV4009-E

An attempt to initialize the system has failed.

The default directory for storing bookmark information could not be accessed.

(S)

Stops the startup processing.

(O)

Make the default directory for storing bookmark information accessible, and then restart the service.

Change the location of the directory for storing bookmark information to an accessible location, and then restart the service.

KAVJV4010-E

An unexpected error occurred while a corrupted data file was being restored.

File path: file-path

Maintenance information: maintenance-information

An unexpected error occurred while a corrupted data file was being restored.

(S)

Cancels the bookmark restoration processing.

(O)

Check the access permissions for the file path.

Check that the disk has sufficient free space.

Delete the default directory for storing bookmark information, and then restart the service.

KAVJV4011-E

The directory for storing bookmark information could not be created.

Directory for storing bookmark information: directory-name

Possible causes are as follows:

The path length of the directory for storing bookmark information exceeded 150 characters.

The directory for storing bookmark information could not be accessed.

(S)

Stops the startup processing.

(O)

Make the default directory for storing bookmark information accessible, and then restart the service.

Specify the path length of the directory for storing bookmark information up to 150 characters, and then restart the service.

KAVJV5001-I

During the initialization an RMI error occurred.

Module name: VSA

Maintenance information: maintenance-information

The Manager is not running, or the specified destination host is invalid.

(O)

Make sure that the Manager is running and that the destination host is correct.

KAVJV5002-I

During the initialization, an attempt to establish a connection with Manager failed.

Module name: VSA

Maintenance information: maintenance-information

The Manager is not running, or the specified destination host is invalid.

(O)

Make sure that the Manager is running and that the destination host is correct.

KAVJV5003-I

During the initialization, an attempt to establish a connection with the Manager failed.

Module name: VSA

Maintenance information: maintenance-information

The Manager is not running, or the specified destination host is invalid.

(O)

Make sure communication with the Manager host can be performed correctly, and that the Manager is running.

KAVJV5004-I

The corrupted data file was deleted.

Node name: node-name

File path: file-path

The corrupted data file was deleted successfully.

KAVJV5005-I

The corrupted data file was restored.

Node name: node-name

File path: file-path

The corrupted data file was restored successfully.

KAVJV5006-I

An invalid host name was specified for the Manager host in the initial settings file.

A connection could not be established with the Manager because an invalid host name was specified for the connection-target Manager host in the initial settings file.

(S)

Stops the startup processing.

(O)

Use the correct format to specify the host.

KAVJV9001-K

The data file was not read correctly.

Node name: node-name

File path: file-path

The data file is corrupted or does not exist.

(S)

Deletes or restores the corresponding file or cleans up the invalid information from the bookmarks tree as needed, and then continues reading the node information.

KAVJV9002-K

The directory for storing bookmark information could not be accessed.

Directory for storing bookmark information: directory-name

Possible causes are as follows:

This was the first startup after changing the directory for storing bookmark information.

The directory for storing bookmark information was deleted.

The directory for storing bookmark information could not be accessed.

(S)

Creates the directory containing the bookmark information at the location specified in config.xml.

KAVJV9004-K

The directory for storing the report cache file could not be accessed.

Directory for storing the report cache file: save-directory

Possible causes of this error are as follows:

This was the first startup after changing the directory for storing the report cache file.

The directory for storing the report cache file has been deleted.

The directory for storing the report cache file is not accessible.

(S)

Creates a directory for storing the report cache file at the location specified in config.xml.

KAVJV9502-K

The directory for storing application definition templates could not be accessed.

Directory: directory-for-storing-the-application-definition-template

Possible causes of this error are as follows:

This was the first startup after changing the directory for storing application definition templates.

The directory for storing application definition templates has been deleted.

The directory for storing application definition template files is not accessible.

(S)

Creates directory-for-storing-the-application-definition-template at the location specified in config.xml.

KAVJZ0998-E

An error occurred in JSP.

An error occurred in JSP. You might have been logged out.

(S)

Suspends processing.

(O)

Log in to PFM - Web Console again, and then retry the operation. If the problem persists, contact the system administrator.

KAVJZ0999-E

A specified host cannot be accessed.

An attempt to initialize the application failed.

(S)

Suspends processing.

(O)

Contact the system administrator.

KAVJZ5001-I

Login is finished.

User ID: user-ID

session ID: session-ID

The user logged in successfully.

(S)

Starts login processing.

KAVJZ5002-I

Logout is finished.

UserID: user-ID

The user logged out successfully.

(S)

Starts logout processing.

KAVJZ5003-I

The application has started successfully.

The system started successfully.

(S)

Starts system processing.

KAVJZ5010-I

START: class-name#method-name

This message indicates the start of a method.

KAVJZ5011-I

END : class-name#method-name

This message indicates the end of a method.

KAVJZ5012-I

START: class-name#method-name

This message indicates the start of an application call.

KAVJZ5013-I

END : class-name#method-name

This message indicates the end of an application call.

KAVJZ5014-I

variable-name=[variable-value]

This is a log message indicating the specified variable value.

KAVJZ5015-I

character-string

This is a log message indicating the specified character string.

KAVJZ5999-E

Exception

stack-trace

This is a log message indicating the stack trace in the event of an exception.

KAVL15000-I

Agent Collector has started. (host=host-name, service=service-ID)

Startup of the Agent Collector service has been completed.

(S)

Starts the collection of performance data by using the Agent Collector service.

KAVL15001-I

Agent Collector has stopped. (host=host-name, service=service-ID)

The Agent Collector service ended normally.

(S)

Ends the processing of the Agent Collector service.

KAVL15002-E

An attempt to start Agent Collector has failed. (host=host-name, service=service-ID)

An attempt to start the Agent Collector service has failed.

(S)

Ends the processing of the Agent Collector service.

(O)

Check the preceding message output to the system log or the common message log, and take the action indicated in the message. If the script has stopped because a signal was received, KAVL15004-E or KAVL15005-W is output to the common message log. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15003-E

Agent Collector stopped abnormally. (host=host-name, service=service-ID)

The Agent Collector service stopped abnormally.

(S)

Ends the processing of the Agent Collector service.

(O)

Check the preceding message output to the system log or the common message log, and take the action indicated in the message. If the script has stopped because a signal was received, KAVL15004-E or KAVL15005-W is output to the common message log. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15004-E

Reception of a signal interrupted service processing. (signal=signal-number)

Processing of the service has been canceled because a signal was received. The code indicated by signal-number is an OS signal number.

(S)

Ends the processing of the Agent Collector service.

KAVL15005-W

Reception of a signal caused the service to stop. (signal=signal-number)

The service has stopped because a signal was received. The code indicated by signal-number is an OS signal number.

(S)

Ends the processing of the Agent Collector service.

KAVL15006-E

The health check process will be stopped because an abnormal termination of the service process was detected.

The health check process will be stopped because abnormal termination of a service process was detected.

(S)

Ends the processing of the Agent Collector service.

(O)

Check the cause of the abnormal termination of the service process in the message output to the system log or the common message log, and take the action indicated in the message. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15007-W

The health check process will be restarted because an abnormal termination of the health check process was detected.

The health check process will be restarted because abnormal termination of the health check process was detected.

(S)

Restarts the health check process.

(O)

If this message appears repeatedly, check the cause of the abnormal termination of the health check process in the message output to the system log or the common message log, and take the action indicated in the message. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15008-E

An attempt to start the health check process has failed.

An attempt to start the health check process has failed.

(S)

Ends the processing of the Agent Collector service.

(O)

Check the preceding message output to the system log or the common message log, and take the action indicated in the message. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15009-E

The health check process stopped abnormally.

The health check process stopped abnormally.

(S)

Ends the processing of the health check process.

(O)

Check the preceding message output to the system log or the common message log, and take the action indicated in the message. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15010-E

Initialization of Agent Collector has failed.

Initialization failed during startup of the Agent Collector service.

(S)

Ends the processing of the Agent Collector service.

(O)

Make sure that the service startup information file (jpcagt.ini) exists. If the file does not exist, copy the jpcagt.ini.model file to the jpcagt.ini file and then set up the health check function again. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15011-E

Initialization of the health check process has failed.

Initialization failed during startup of the health check process.

(S)

Ends the processing of the health check process.

(O)

Check the preceding message output to the system log or the common message log, and take the action indicated in the message. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15012-E

The same service cannot be started.

An attempt to start a service failed because the same service has already been started.

(S)

Stops the service.

(O)

Use the jpctool service list command to check the startup status of the service.

KAVL15013-E

The number of times the health check process was repeatedly restarted exceeded the maximum limit.

Attempts to restart the health check process were performed because the health check process terminated abnormally, but the number of restart attempts exceeded the maximum limit. The health check process might have terminated abnormally immediately after starting. Note that the maximum limit is set to 5.

(S)

Stops the Agent Collector processing.

(O)

Check the message output to the system log or the common message log to determine the cause of the abnormal termination of the health check process, and then follow the instructions given in the message. If you are unable to determine the cause, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVL15014-W

An attempt to send a health check event has failed. (agent=service-ID, status=health-check-status)

An attempt to send a health check event has failed. The health check event will be re-sent when the next health check event occurs and at every collection interval of the health check agent. If the health check event is successfully resent, the KAVL15016-I message will be output.

service-ID indicates the service ID of the agent for which sending of the health check event failed.

health-check-status indicates the health check status of the health check event that was not successfully sent.

(S)

Skips sending of an event.

(O)

Check whether the PFM - Manager service is running. If it is not running, restart it. If it is running, resending the health check event will automatically correct the error.

KAVL15015-I

The status of an unsent health check event has been changed. (agent=service-ID, previous status=pre-change-health-check-status, current status=post-change-health-check-status)

The health check status of an agent that has unsent health check events has been changed. When health check events are resent, only the health check events that indicate the post-change health check status will be sent.

service-ID indicates the service ID of the agent for which the health check status was changed.

pre-change-health-check-status indicates the pre-change health check status of the corresponding agent.

post-change-health-check-status indicates the post-change health check status of the corresponding agent.

(S)

Continues processing.

KAVL15016-I

Unsent health check events have been successfully sent. (sent events=number-of-resent-events, remaining events=number-of-remaining-unsent-events)

Unsent health check events have been successfully sent.

number-of-resent-events indicates the number of health check events that were successfully resent.

number-of-remaining-unsent-events indicates the number of health check events that had not been sent when this message was output.

If number-of-remaining-unsent-events is 0, this indicates that all health check events that were waiting to be resent have been successfully sent.

(S)

Suspends processing.

KAVL15017-I

There are unsent health check events. (events=number-of-unsent-events)

There were unsent health check events when the service stopped. These events will not be resent.

number-of-unsent-events indicates the number of unsent health check events at the time the service stopped.

(S)

Continues processing.

KAVL15018-I

The service will start with the health check by ICMP enabled. (host=host-name, service=service-ID)

The service will start with health check by ICMP enabled.

If connection to the Status Server via TCP/IP failed due to a timeout, confirmation using ICMP communication is conducted.

(S)

Starts the service with health check by ICMP enabled.

KAVL15019-W

The health check by ICMP will now be disabled because an invalid value was set. (label=label-name, specified value=specified-value)

The service will start with health check by ICMP disabled because an invalid value was set.

(S)

Starts the service with health check by ICMP disabled.

(O)

Check and, if necessary, revise the setting values. To apply the settings, restart the Manager service.

KAVL15020-I

An information health check event was issued. (host=host-name, service=service-ID, hcsstatus=health-check-status, Collector=Collector-status, Store=Store-status, Action Handler=Action-Handler-status)

Issuance of a health check event was detected. The current health check status of the target host or service is normal.

service-ID indicates the service ID of the target agent for health check. host-name indicates the name of the target host. health-check-status indicates the health check status of the target host or service. Collector-status indicates the operating status of the Collector service on the target agent. Store-status indicates the operating status of the Store service on the target agent. Action-Handler-status indicates the operating status of Action Handler on the target agent.

(S)

Continues processing.

KAVL15021-W

A warning health check event was issued. (host=host-name, service=service-ID, hcsstatus=health-check-status Collector=Collector-status, Store=Store-status, Action Handler=Action-Handler-status)

Issuance of a health check event was detected. The current health check status of the target host or service is warning.

service-ID indicates the service ID of the target agent for health check. host-name indicates the name of the target host. health-check-status indicates the health check status of the target host or service. Collector-status indicates the operating status of the Collector service on the target agent. Store-status indicates the operating status of the Store service on the target agent. Action-Handler-status indicates the operating status of Action Handler on the target agent.

(S)

Continues processing.

(O)

Check the common message log for the event source host, and eliminate the cause of the warning status. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVL15022-E

An exception health check event was issued. (host=host-name, service=service-ID, hcsstatus=health-check-status, Collector=Collector-status, Store=Store-status, Action Handler=Action-Handler-status)

Issuance of a health check event was detected. The current health check status of the target host or service is abnormal.

service-ID indicates the service ID of the target agent for health check. host-name indicates the name of the target host. health-check-status indicates the health check status of the target host or service. Collector-status indicates the operating status of the Collector service on the target agent. Store-status indicates the operating status of the Store service on the target agent. Action-Handler-status indicates the operating status of Action Handler on the target agent.

(S)

Continues processing.

(O)

Check the common message log for the event source host, and eliminate the cause of the abnormal status. If the cause cannot be determined, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

KAVL15100-E

An error occurred in an OS API (API-name). (en=OS-detail-code, arg1=argument-1, arg2=argument-2, arg3=argument-3)

An error occurred in an OS API. The code indicated by OS-detail-code is errno of the system call or a Win32API detail code.

(S)

Cancels processing.

(O)

Check the OS detail code. If the cause is unknown, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15101-E

An error occurred in a function (function-name). (rc=maintenance-code, arg1=argument-1, arg2=argument-2, arg3=argument-3)

An error occurred in a function between controls.

(S)

Cancels processing.

(O)

Collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15102-E

The system environment is invalid. (rc=maintenance-code)

The system environment is invalid. The system file was deleted illegally or the access permission was changed.

(S)

Cancels processing.

(O)

Re-install Performance Management.

KAVL15103-E

An unexpected exception has occurred. (rc=maintenance-code)

An unexpected error occurred.

(S)

Cancels processing.

(O)

Collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the manual Job Management Partner 1/Performance Management User's Guide.

KAVL15104-E

Memory is insufficient. (size=allocated-size)

Memory allocation failed.

(S)

Cancels processing.

(O)

Stop applications that are not being used or increase memory. Services may have stopped due to insufficient memory. Use the jpctool service list command to check the status of services.

KAVL15105-W

The monitoring status of the health check could not be updated because the settings information for the function to temporarily suspend monitoring was not successfully acquired.

Acquisition of the settings information for the monitoring suspension function from the Master Manager service failed. As a result, the monitoring status of the health check was not updated.

(S)

Continues processing with the same monitoring status as immediately before the failed update for the health check function, and tries to update the monitoring status at the next collection.

(O)

Check the startup status of the Master Manager service and the network status.

Appendixes

A. Identifiers

When you are using PFM - Manager, there may be situations in which you will need an identifier for PFM - Manager. The following table shows the PFM - Manager identifiers.

For details about the identifiers for PFM - Agent or PFM -RM, see the description of identifiers in the appendix of each PFM - Agent or PFM - RM manual.

Table A‒1: PFM - Manager identifiers

Purpose

Name

Identifier

Description

Commands, etc.

Product ID

P

The product ID is part of the service ID. A service ID is needed in order to use a command to, for example, check the Performance Management system configuration or to back up performance data. For service IDs, see the description of naming rules for the services in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

0

Product ID of the health check agent

Service key

When the product name display function is enabled:

all#: Includes the services of all of the programs of the Performance Management products (including the PFM - Web Console service).

jp1pc#: PFM - Manager, PFM - Base, PFM - Agent, and PFM - RM services

Manager: PFM - Manager services

AH: Action Handler services

StatSvr: Status Server services

When the product name display function is disabled:

all#: Includes the services of all of the programs of the Performance Management products (including the PFM - Web Console service)

jp1pc#: PFM - Manager, PFM - Base, PFM - Agent, and PFM - RM services

mgr: PFM - Manager service

act: Action Handler service

stat: Status Server service

Needed in order to use a command to, for example, start or stop PFM - Manager.

When the product name display function is enabled:

HC

When the product name display function is disabled:

agt0

Service key of the health check agent.

ODBC

Product type identifier

PWB

Needed in order to use an SQL statement to extract PFM - Manager data. For details, see the chapter that explains operation analysis linked to an ODBC-based application program in the Job Management Partner 1/Performance Management User's Guide.

HC

Product type identifier of the health check agent

#

This identifier can be specified only by the jpcspm start command, jpcspm stop command, and jpctool service list command. For any other command, the service key for jp1pc is all. There is no service key for all.

B. Processes

This appendix describes the processes of PFM - Manager, PFM - Web Console, and PFM- Base.

For details about the processes of PFM - Agent or PFM - RM, see the appendix of each PFM - Agent or PFM - RM manual.

B.1 PFM - Manager processes

The table below lists the PFM - Manager processes. The number that follows each process indicates the number of instances of that process that can be active simultaneously.

For PFM - Manager in a logical host environment, the information in the table applies to each logical host (note, however, that the Status Server service can run only on a physical host).

Table B‒1: PFM - Manager processes

Process name (number of instances of the process)

Function

Windows version

UNIX version

jpcagt0.exe(1)

jpcagt0(1)

Agent Collector service process (only when the health check function is enabled)

jpc0collect.exe(1)#1

jpc0collect(1)#1

Agent Collector collection process (only when the health check function is enabled)

jpcah.exe(1)

jpcah(1)

Action Handler service process

jpcep.exe(1)

jpcep(1)

Correlator service process

jpcmm.exe(1)

jpcmm(1)

Master Manager service process

jpcnsvr.exe(1)

jpcnsvr(1)

Name Server service process

jpcstatsvr.exe(1)

jpcstatsvr(1)

Status Server service process

jpcsto.exe(1)

jpcsto(1)

Master Store service process

jpcsto.exe(1)

jpcsto(1)

Agent Store service process (only when the health check function is enabled)

jpctrap.exe(1)

jpctrap(1)

Trap Generator service process

jpctraps.exe(1)#2

jpctraps(1)#2

Trap Generator service trap transmission process

jpcvsvr.exe(1)

jpcvsvr(1)

View Server service process

stpqlpr.exe(1)#3

stpqlpr(1)#3

Store database backup/export execution process

#1

Sub-process of the jpcagt0 process.

#2

Sub-process of the jpctrap process.

#3

Sub-process of the jpcsto process.

B.2 PFM - Web Console processes

The table below lists the PFM - Web Console processes. The number that follows each process indicates the number of instances of that process that can be active simultaneously.

Table B‒2: PFM - Web Console processes

Process name (number of instances of the process)

Function

Windows version

UNIX version

httpsd.exe(2)

httpsd(8)#³

PFM - Web Service service process

jpcwebcon.exe(1)

N/A

PFM - Web Console service process

cjstartweb.exe(1)#1

cjstartweb(1)

Web container service process

cprfd.exe(1)

cprfd(1)

Web service trace information output service

rotatelogs2.exe(4)

N/A

Process for monitoring logs

hntr2srv.exe(1)#2

N/A

Integrated trace start service

hntr2mon.exe(1)#2

N/A

Integrated trace service

Legend:

N/A: Not applicable

#1

Sub-process of the jpcwebcon process.

#2

Process that is shared among all programs that use the integrated trace log installed on the same machine.

#3

The minimum number of processes for httpsd is 8, however, depending on the PFM - Web Console operational status, the number might increase the maximum to 150.

B.3 PFM - Base processes

The table below lists the PFM- Base processes. The number that follows each process indicates the number of instances of that process that can be active simultaneously.

For PFM- Base in a logical host environment, the information in the table applies to each logical host (note, however, that the Status Server service can run only on a physical host).

Table B‒3: PFM - Base processes

Process name (number of instances of the process)

Function

Windows version

UNIX version

jpcah.exe(1)

jpcah(1)

Action Handler service process

jpcstatsvr.exe(1)

jpcstatsvr(1)

Status Server service process

C. Port Numbers

This appendix describes the port numbers used by PFM - Manager, PFM - Web Console, and PFM - Base and explains the directions of passage through a firewall.

For details about the port numbers and firewall passage directions for PFM - Agent or PFM - RM, see the appendix of each PFM - Agent or PFM - RM manual.

Port numbers can be changed as desired, in accordance with the user environment.

For details about how to change a port number, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide. Note that the protocol used is TCP.

Note

Performance Management supports static NAT (Basic NAT) that performs 1-to-1 address translation.

It does not support dynamic NAT or NAPT (IP Masquerade, NAT+) that includes the port translation function.

C.1 Performance Management port numbers

This section describes the port numbers that are used by PFM - Manager, PFM - Web Console, and PFM - Base.

For details about the port numbers for the Agent Collector and Remote Monitor Collector service, or Agent Store and Remote Monitor Store service, see the lists of port numbers provided in the appendix of each PFM - Agent or PFM - RM manuals.

(1) Port numbers used by PFM - Manager

The following table shows the port numbers used by PFM - Manager:

Table C‒1: Port numbers used by PFM - Manager

Port number

Service name

Parameter

Use

20275#1

Action Handler

jp1pcah

Used to execute actions.

Automatic#2

Agent Collector (health check agent)

jp1pcagt0

Used to bind alarms and acquire realtime reports.

Automatic#2

Agent Store (health check agent)

jp1pcsto0

Used to record performance data and acquire historical reports.

20273#1

Correlator

jp1pcep

Used to send the events of each PFM - Agent or PFM - RM to PFM - Manager.

20271#1

Master Manager

jp1pcmm

Used when each service communicates with the Master Manager service.

20272#1

Master Store

jp1pcsto

Used to record the events of each PFM - Agent or PFM - RM.

22292#3

NNM Object Manager

jp1pcovsvr

Used to link with NNM.

22285

Name Server

jp1pcnsvr

Used when each service communicates with the Name Server service.

22350

Status Server

jp1pcstatsvr

Used to check the service status.

20274#1

Trap Generator

jp1pctrap

Used when SNMP traps are sent.

20276#1

View Server

jp1pcvsvr2

Used to send the events and reports of each PFM - Agent or PFM - RM to PFM - Web Console.

22286

View Server (between PFM - Web Console and View Server service)

jp1pcvsvr

Used to log in to PFM - Manager and to manipulate PFM - Web Console's GUI.

View Server (between JP1/ITSLM and PFM - Manager)

jp1pcvsvr

Used to set a linkage with PFM - Manager from JP1/ITSLM.

#1

This is the port number assigned by the system; it is used unless you change the port number to a value you select by executing the jpcconf port define command. If you do not execute the jpcconf port define command, the system automatically assigns an available port number each time a service is restarted.

#2

When the jpcconf port define command is executed, a port number that is not being used at that point is assigned automatically and displayed. Also, if you do not execute the jpcconf port define command, a port number that is not being used by the system is automatically assigned each time the service is restarted.

#3

The port number is used only when the product is installed on Windows Server 2003, or Solaris (SPARC).

(2) Port numbers used by PFM - Web Console

The following table shows the port numbers used by PFM - Web Console:

Table C‒2: Port numbers used by PFM - Web Console

Port number

Service name

Parameter

Use

20358

Web Service

N/A

Used to connect from a Web browser to PFM - Web Console.

20359

Web Console

N/A

Used when the Web Service service establishes communication connection with the Web Console service.

20360

Web Console

N/A

Used to manage the Web Console service.

Automatic#

Web Console

N/A

Callback port number (ownPort) used by the PFM - Web Console service

Automatic#

Web Console

N/A

Callback port number (ownCmdPort) used by the PFM - Web Console command

Legend:

N/A: Not applicable

#

When PFM - Web Console starts, a port number set in the config.xml file is automatically assigned to PFM - Web Console. If no port number is set in the config.xml file, a port number that is not being used by the system is automatically assigned to PFM - Web Console each time PFM - Web Console is restarted.

(3) Port numbers used by PFM - Base

The following table shows the port numbers used by PFM - Base:

Table C‒3: Port numbers used by PFM - Base

Port number

Service name

Parameter

Use

20275#1

Action Handler

jp1pcah

Used to execute actions.

22292#2

NNM Object Manager

jp1pcovsvr

Used to link with NNM.

22350

Status Server

jp1pcstatsvr

Used to check the service status.

#1

This is the port number assigned by the system; it is used unless you change the port number to a value you select by executing the jpcconf port define command. If you do not execute the jpcconf port define command, the system automatically assigns an available port number each time a service is restarted.

#2

The port number is used only when the product is installed on Windows Server 2003, Solaris (SPARC), or HP-UX.

(4) About port number information registered in the services file on the PFM - Base host

When you install PFM - Base, register the following port number information in the services file:

jp1pcnsvr: 22285/tcp

jp1pcstatsvr: 22350/tcp

jp1pcovsvr: 22292/tcp#

The port number 22285 above is a port that waits for the NameServer service of the PFM - Manager host and is used for specifying the communication port from the PFM - Base host.

PFM - Base communicates with the NameServer service by using this port information as the destination. Therefore, do not change the setting value except when the port number of the NameServer service is changed. If you change or delete the port number, PFM - Base cannot communicate with NameServer.

#

The port number is used only when PFM - Base is installed on Windows Server 2003, Solaris (SPARC), or HP-UX.

C.2 Firewall penetration directions

This section describes the firewall passage directions of Performance Management.

The following figure shows an example of a system configuration that explains the relationship between Performance Management and a firewall. If there is a firewall between hosts, the settings for penetration are needed.

Figure C‒1: Relationship between Performance Management and firewalls

The statuses of the firewall passage directions are as follows:

Firewall between a Web browser and PFM - Web Console

Firewall between PFM - Web Console and PFM - Manager

Firewall between PFM - Manager and PFM - Agent, PFM - RM, or PFM - Base

Firewall between PFM - Agent, PFM - RM, or PFM - Base and another PFM - Agent, PFM - RM, or PFM - Base

The following describes the settings required to enable penetration of the firewall for each case. The following legend and notes are for the tables below that show firewall penetration directions.

Legend:

->: The direction in which communication (connection) begins

#1

After communication (connection) begins, sending and receiving are performed on the established session. Specify the settings so that a response to the established session can also penetrate a firewall.

#2

When communication (connection) begins, the connection-source host uses a free port number assigned by the OS as the sending port. Therefore, specify the settings so that any port number can penetrate a firewall as the sending port.

#3

The port number can be fixed by using the jpcconf port define command. Also, the parameter is a value that is displayed at the Services field output by the jpcconf port list -key all command when the port number is fixed.

#4

When the status of the Performance Management service that runs in a cluster system is checked, the connection-source host communicates with the Status Server service of the connection-destination host by using the host names (IP addresses) of the physical host and logical host.

Therefore, allow a port number specified for jp1pcstatsvr to penetrate a firewall for communication from the connection-source host to the host names (IP addresses) of both the physical host and logical host in a communication performed with the Status Server service.

For example, when you specify the settings of the Status Server service for communication from PFM - Manager to the PFM - Agent, PFM - RM, or PFM - Base host, allow a port number specified for jp1pcstatsvr to penetrate a firewall for communication with both the following host names (IP addresses).

PFM - Agent, PFM - RM, or PFM - Base host (Physical host)

PFM - Agent, PFM - RM, or PFM - Base host (Logical host)

(1) Firewall among a Web browser, PFM - Web Console, and PFM - Manager

The following figure shows port passing of a firewall among a Web browser, PFM - Web Console, and PFM - Manager.

Figure C‒2: Port passing of a firewall among a Web browser, PFM - Web Console, and PFM - Manager

Also, the following figure shows IP address passing between PFM - Web Console and PFM - Manager.

Figure C‒3: IP address passing between PFM - Web Console and PFM - Manager

The settings required to allow penetration of a firewall are needed for IP address so that it can be used for communication among the target hosts. Specify the settings for penetrating the firewall for IP address with so that sending and receiving can be performed.

Because IP address with is not used between PFM - Web Console and PFM - Manager, the settings required for penetrating a firewall are not needed for it.

(a) Firewall that exists in communication from a Web browser to PFM - Web Console

When a Web browser connects to PFM - Web Console across a firewall, set the port numbers according to the directions shown in the following table so that communications can penetrate the firewall.

Table C‒4: Firewall penetration directions (communication from a Web browser to PFM - Web Console)

Host using a Web browser

Pass direction#1

PFM - Web Console host

Any#2

->

20358

(Default)

Specify the settings of the firewall so that the sending port that a Web browser uses temporarily can pass through the receiving port 20358 (the default) of PFM - Web Console

(b) Firewall that exists in communication from PFM - Web Console to PFM - Manager

When PFM - Web Console connects to PFM - Manager across a firewall, set the port numbers according to the directions shown in the following table so that communications can penetrate the firewall.

Table C‒5: Firewall penetration directions (communication from PFM - Web Console to PFM - Manager)

PFM - Web Console host

Pass direction#1

PFM - Manager host#3

Any#2

->

jp1pcvsvr

Specify the settings of the firewall so that the sending port that PFM - Web Console uses temporarily can pass through the receiving port of PFM - Manager.

(c) Firewall that exists in communication from PFM - Manager to PFM - Web Console

If PFM - Manager and PFM - Web Console are to be installed across a firewall, the use of a Virtual Private Network is recommended. If a VPN cannot be used, you should set up a callback port number.

To set a callback port number, use the initialization file for the PFM - Web Console host (config.xml). The following table describes the settings:

Table C‒6: Firewall penetration directions (communication from PFM - Manager to PFM - Web Console)

PFM - Manager host

Pass direction#1

PFM - Web Console host

Any#2

->

Callback port number that PFM - Web Console service uses (ownPort)

Callback port number that the PFM - Web Console command uses (ownCmdPort)

Specify the settings of the firewall so that the sending port that PFM - Manager uses temporarily can pass through the receiving port of PFM - Web Console.

For details about the specifiable values, see E. Initialization File (config.xml).

To apply the changes in the initialization file (config.xml), you need to restart PFM - Web Console. If any other settings are changed, PFM - Web Console may not function correctly.

The following shows an example of the settings:

Figure C‒4: Example of setting the initialization file (config.xml)

After setting this file, allow each port number to penetrate the firewall in the directions shown in the table.

(2) Firewall between PFM - Manager and PFM - Agent or PFM - RM

The following figure shows port passing of a firewall from PFM - Manager to PFM - Agent or PFM - RM.

Figure C‒5: Port passing of a firewall from PFM - Manager to PFM - Agent or PFM - RM

The following figure shows port passing of a firewall from PFM - Agent or PFM - RM to PFM - Manager.

Figure C‒6: Port passing of a firewall from PFM - Agent or PFM - RM to PFM - Manager

Also, the following figure shows IP address passing between PFM - Manager and PFM - Agent or PFM - RM.

Figure C‒7: IP address passing between PFM - Manager and PFM - Agent or PFM - RM

The settings required to allow penetration of a firewall are needed for IP address so that it can be used for communication among the target hosts. Specify the settings for penetrating the firewall for IP address with so that sending and receiving can be performed.

Because IP address with is not used between PFM - Manager and PFM - Agent or PFM - RM, the settings for penetrating a firewall are not needed for it.

(a) Firewall that exists in communication from PFM - Manager to PFM - Agent, PFM -RM, or PFM - Base

If there is a firewall between PFM - Manager and PFM - Agent, PFM - RM, or PFM - Base, set fixed port numbers for all PFM - Manager and PFM - Agent, PFM - RM, or PFM - Base services. Additionally, set port numbers according to the directions shown in the following table so that communications can penetrate the firewall.

For details about the Agent Store services and Agent Collector services, see the appendix in each PFM - Agent manual. For details about the Remote Monitor Store services and Remote Monitor Collector services, see the appendix of the PFM - RM manual.

Table C‒7: Firewall penetration directions (communication from PFM - Manager to PFM - Agent, PFM - RM, or PFM - Base)

PFM - Manager host

Pass direction#1

PFM - Agent, PFM - RM, or PFM - Base host#3

Any#2

->

jp1pcah

jp1pcstatsvr

The port number of the Collector service of PFM - Agent or PFM - RM

The port number of the Store service of PFM - Agent or PFM - RM

Table C‒8: Firewall penetration directions (communication from PFM - Manager to PFM - Agent, PFM - RM, or PFM - Base that runs in a cluster system)

PFM - Manager host

Pass direction#1

PFM - Agent, PFM - RM, or PFM - Base host#3

Any#2

->

jp1pcah

jp1pcah_logical-host-name

jp1pcstatsvr#4

The port number of the Collector service of PFM - Agent or PFM - RM

The port number of the Store service of PFM - Agent or PFM - RM

Specify the settings of the firewall so that the sending port that PFM - Manager uses temporarily can pass through the receiving port of PFM - Agent, PFM - RM, or PFM - Base.

(b) Firewall that exists in communication from PFM - Agent, PFM -RM, or PFM - Base to PFM - Manager

If there is a firewall between PFM - Manager and PFM - Agent, PFM - RM, or PFM - Base, set fixed port numbers for all PFM - Manager and PFM - Agent, PFM - RM, or PFM - Base services. Additionally, set port numbers according to the directions shown in the following table so that communications can penetrate the firewall.

Table C‒9: Firewall penetration directions (communication from PFM - Agent, PFM - RM, or PFM - Base to PFM - Manager)

PFM - Agent, PFM - RM, or PFM - Base host

Pass direction#1

PFM - Manager host#3

Any#2

->

jp1pcagt0

jp1pcsto0

jp1pcnsvr

jp1pcmm

jp1pcsto

jp1pcep

jp1pctrap

jp1pcvsvr2

jp1pcah

jp1pcstatsvr

Table C‒10: Firewall penetration directions (communication from PFM - Agent, PFM - RM, or PFM - Base to PFM - Manager that runs in a cluster system)

PFM - Agent, PFM - RM, or PFM - Base host

Pass direction#1

PFM - Manager host#3

Any#2

->

jp1pcagt0_logical-host-name

jp1pcsto0_logical-host-name

jp1pcnsvr

jp1pcmm

jp1pcsto

jp1pcep

jp1pctrap

jp1pcvsvr2

jp1pcah

jp1pcah_logical-host-name

jp1pcstatsvr#4

Specify the settings of the firewall so that the sending port that PFM - Agent, PFM - RM, or PFM - Base uses temporarily can pass through the receiving port of PFM - Manager.

(3) Firewall between PFM - Agent or PFM - RM and PFM - Agent or PFM - RM on another host

The following figure shows port passing of a firewall between PFM - Agent or PFM - RM and PFM - Agent or PFM - RM on another host.

Figure C‒8: Port passing of a firewall between PFM - Agent or PFM - RM and PFM - Agent or PFM - RM on another host

The following figure shows IP address passing between PFM - Agent or PFM - RM and PFM - Agent or PFM - RM on another host.

Figure C‒9: IP address passing between PFM - Agent or PFM - RM and PFM - Agent or PFM - RM on another host

The settings required to allow penetration of a firewall are needed for IP address so that it can be used for communication among the target hosts. Specify the settings for penetrating the firewall for IP address with so that sending and receiving can be performed.

Because IP address with is not used between PFM - Agent or PFM - RM and PFM - Agent or PFM - RM on another host, the settings for penetrating a firewall are not needed for it.

(a) Firewall that exists in communication from PFM - Agent, PFM -RM, or PFM - Base to PFM - Agent, PFM -RM, or PFM - Base on another host

If there is a firewall between PFM - Agent, PFM - RM, or PFM - Base and PFM - Agent, PFM - RM, or PFM - Base on another host, the settings required for penetrating the firewall are needed only when you want to execute the jpctool db backup, jpctool db dump, or jpctool service list command between the target hosts. Also, the settings for penetrating a firewall between PFM - Manager and PFM - Agent, PFM - RM, or PFM - Base are needed.

Note that when you execute the jpctool db dump or jpctool service list command with the -proxy option specified in an environment in which communication from the target host to the PFM - Manager host can be established, communication is performed through PFM - Manager. Therefore, command execution becomes possible, and the settings required for penetrating a firewall are not needed.

When you execute the jpctool db backup command for the target host, the settings for penetrating a firewall are needed. You can perform operations required to obtain a backup on the local host by specifying the -alone option for the command. In this case, the settings required for penetrating a firewall are not needed. So, consider this in the operation design.

For details about the jpctool db backup, jpctool db dump, or jpctool service list command, see 2. Commands.

When you specify the settings required to allow penetration of a firewall, set fixed port numbers for all of both PFM - Agent and PFM - RM, or the PFM - Base services. Additionally, set port numbers according to the directions shown in the following table so that communications can penetrate the firewall.

For details about the Agent Store services and Agent Collector services, see the appendix in each PFM - Agent manual. For details about the Remote Monitor Store services and Remote Monitor Collector services, see the appendix of the PFM - RM manual.

Table C‒11: Firewall penetration directions (communication from PFM - Agent, PFM - RM, or PFM - Base to another PFM - Agent, PFM - RM, or PFM - Base)

PFM - Agent, PFM - RM, or PFM - Base host

Pass direction#1

Another PFM - Agent, PFM - RM, or PFM - Base host#3

Any#2

->

jp1pcah

jp1pcstatsvr

The port number of the Collector service of PFM - Agent or PFM - RM

The port number of the Store service of PFM - Agent or PFM - RM

Table C‒12: Firewall penetration directions (communication from PFM - Agent, PFM - RM, or PFM - Base to another PFM - Agent, PFM - RM, or PFM - Base that runs in a cluster system)

PFM - Agent, PFM - RM, or PFM - Base host

Pass direction#1

Another PFM - Agent, PFM - RM, or PFM - Base host#3

Any#2

->

jp1pcah

jp1pcah_logical-host-name

jp1pcstatsvr#4

The port number of the Collector service of PFM - Agent or PFM - RM

The port number of the Store service of PFM - Agent or PFM - RM

Specify the settings of the firewall so that the sending port that PFM - Agent, PFM - RM, or PFM - Base uses temporarily can pass through the receiving port of another PFM - Agent, PFM - RM, or PFM - Base.

C.3 Setting host names to be used for communication between PFM - Manager and PFM - Web Console or JP1/ITSLM

If you are using IP address translation (NAT translation) or multiple IP addresses between the PFM - Manager host and the PFM - Web Console or JP1/ITSLM host, communication between PFM - Manager and PFM - Web Console or JP1/ITSLM might be disrupted.

To perform communication between PFM - Manager and PFM - Web Console or JP1/ITSLM, host names to be used for communication need to be set. How to set host names differs depending on the following conditions:

The IP address# used by the PFM - Manager host cannot be accessed from the PFM - Web Console host and the JP1/ITSLM host.

The IP address# used by the PFM - Web Console host cannot be accessed from the PFM - Manager host.

#

If the host uses multiple IP addresses, the first IP address to be resolved for that host name is used.

The following subsections describe how to set host names to be used for communications between PFM - Manager and PFM - Web Console or JP1/ITSLM.

(1) When the IP address used by the PFM - Manager host cannot be accessed from the PFM - Web Console host and the JP1/ITSLM host

Specify the PFM - Manager host name or IP address in the jpcvsvr.ini file for the PFM - Manager host as follows, and then restart PFM - Manager:

java.rmi.server.hostname=PFM-Manager-host-name or IP-address

The location of the jpcvsvr.ini file depends on the OS, as described below:

For Windows version of PFM - Manager

For physical host operation:

installation-folder\mgr\viewsvr\jpcvsvr.ini

For logical host operation:

environment-directory\jp1pc\mgr\viewsvr\jpcvsvr.ini

For UNIX version of PFM - Manager

For physical host operation:

/opt/jp1pc/mgr/viewsvr/jpcvsvr.ini

For logical host operation:

environment-directory/jp1pc/mgr/viewsvr/jpcvsvr.ini

PFM - Web Console and JP1/ITSLM uses the specified PFM - Manager host name or IP address to connect to PFM - Manager. This is because when a host name is specified, PFM - Manager also uses the specified host name for internal communications, so this host name must be enabled on the PFM - Manager host.

(2) When the IP address used by the PFM - Web Console host cannot be accessed from the PFM - Manager host

Specify the PFM - Web Console host name in the initialization file (config.xml) for the PFM - Web Console host, and then restart PFM - Web Console if it is already running. The following table describes the settings:

Table C‒13: Host name or IP address settings

Description

Setting

Permitted value#

Default value

Host name or IP address used as the callback target when PFM - Web Console connects to PFM - Manager

ownHost

For host name:

Numbers 0 to 9

. (period)

- (hyphen)

Alphabetic characters A to Z and a to z

The length is 1 to 255 bytes and the name must begin with an alphanumeric character.

For IP address:

0.0.0.0 to 255.255.255.255

IP address of the PFM - Web Console host

#

If an invalid value is specified or the specification is omitted, the default value is set.

To enable the settings in the initialization file (config.xml), you must restart PFM - Web Console. If any other settings are changed, PFM - Web Console may not function correctly. If any other settings are changed, PFM - Web Console may not function correctly.

PFM - Manager uses the specified PFM - Web Console host name to connect to PFM - Web Console.

The following shows an example:

C.4 Changing port numbers used in PFM - Web Console

This section explains how to change the port numbers used in PFM - Web Console.

(1) Changing the http request port number

The default port number for access from a Web browser to PFM - Web Console is 20358.

To change this port number:

Change the port number.

In the Windows version of PFM - Web Console

PFM-Web-Console-installation-directory\CPSB\httpsd\conf\httpsd.conf

In the UNIX or Linux version of PFM - Web Console

/opt/jp1pcwebcon/CPSB/httpsd/conf/httpsd.conf

Change the following line in the file indicated above.

LISTEN 20358

Restart the services.

Restart the PFM - Web Service and the PFM - Web Console service.

(2) Changing the AJP communication port

The default port number for the AJP communication port of PFM - Web Console is 20359.

To change this port number:

Change the port number.

In Windows:

installation-directory\CPSB\CC\web\containers\PFMWebConsole\usrconf\usrconf.properties

In UNIX or Linux:

/opt/jp1pcwebcon/CPSB/CC/web/containers/PFMWebConsole/usrconf/usrconf.properties

Change the following line in the file indicated above.

webserver.connector.ajp13.port=20359

Also change the file indicated below.

In Windows:

installation-directory\CPSB \CC\web\redirector\workers.properties

In UNIX or Linux:

/opt/jp1pcwebcon/CPSB/CC/web/redirector/workers.properties

Change the following line in the file indicated above.

worker.worker1.port=20359

Restart the services.

Restart the PFM - Web Service and the PFM - Web Console service.

(3) Changing the component container management port

The default port number for the component container management port of PFM - Web Console is 20360.

To change this port number:

Change the port number.

In Windows:

installation-directory\CPSB\CC\web\containers\PFMWebConsole\usrconf\usrconf.properties

In UNIX or Linux:

/opt/jp1pcwebcon/CPSB/CC/web/containers/PFMWebConsole/usrconf/usrconf.properties

Change the following line in the file indicated above.

webserver.shutdown.port=20360

Restart the services.

Restart the PFM - Web Service and the PFM - Web Console service.

D. Files and Directories

This appendix describes for each OS the Performance Management files and directories.

The following are the installation directories for Performance Management, depending on the program and the OS.

Installation directory for PFM - Manager, PFM - Agent, PFM - RM, and PFM - Base

In Windows:

Performance Management can be installed in any folder.# The default folder is as follows:

For Windows Server 2003 (x64), the 64-bit version of Windows Server 2008, and Windows Server 2012:

system-drive\Program Files (x86)\Hitachi\jp1pc\

For other OSs:

system-drive\Program Files\Hitachi\jp1pc\

#

Any installation directory can be selected only in the case where no Performance Management is already installed.

In UNIX:

/opt/jp1pc/

Installation directory for PFM - Web Console

In Windows:

PFM - Web Console can be installed in any folder. The default folder is as follows:

system-drive\Program Files\Hitachi\jp1pcWebCon\

For Windows Server 2003 (x64) and the 64-bit version of Windows Server 2008:

system-drive\Program Files (x86)\Hitachi\jp1pcWebCon\

For other OSs:

system-drive\Program Files\Hitachi\jp1pcWebCon\

In UNIX:

/opt/jp1pcwebcon/

D.1 Files and directories for PFM - Manager (in Windows)

The following table lists the files and folders for the Windows version of PFM - Manager:

Table D‒1: Files and folders for PFM - Manager (Windows version)

Folder name

File name

Description

system-drive\Windows\System32\

N/A

Folder for the Windows system files

jpccommVVRRnn.dll

Performance Management common base library

jpcodbc.dll#1

ODBC driver

libjpcauditVVRRnn.dll

Performance Management action log library

libjpchcccomm[VVRRnn].dll

Log library for Performance Management character code conversion

libjpchccjpcomm[VVRRnn].dll

Log library for Performance Management character code conversion

MSVCIRT.DLL#1

Microsoft istream-related Runtime

msvcp100.dll

Microsoft C++ Runtime

MSVCP60.DLL#1

Microsoft C++ Runtime

msvcr100.dll

Microsoft C++ Runtime

MSVCRT.DLL#1

Microsoft C Runtime

tls704d.dll#1

RogueWave runtime

installation-folder\

inst.ini

Version information file

instmgr.ini

PFM - Manager product information file

jpccomm.ini

Startup information file common to all components

jpccomm.ini.model

Sample file for startup information file common to all components

jpchosts

Host information settings file

jpchosts.model

Sample file for host information settings file

jpcns.ini#2

Service configuration information file

jpcns.ini.model

Sample file for service configuration information file

jpcns_backup.ini

Backup file for service configuration information file

jpcplist.ini

Product definition file

jpcplist.ini.model

Sample file for product definition file

installation-folder\agt0\

N/A

Health check agent root folder

jpcagtras.bat

Script for collecting health check agent-specific information

installation-folder\agt0\agent\

N/A

Agent Collector service root folder

COSLMMI.DB

Data file for the JP1/ITSLM linkage setting

COSLMMI.IDX

Index file for the data file for the JP1/ITSLM linkage setting

COSLMMI.LCK

Lock file for the data file for the JP1/ITSLM linkage setting

jpc0collect.exe

Agent Collector service subprocess

jpcagt.ini

Agent Collector service configuration file

jpcagt.ini.model

Model file for the Agent Collector service configuration file

jpcagt0.exe

Agent Collector service

jpcitslm.ini

JP1/ITSLM linkage setting file

suspended.dat

Monitoring suspension information file

installation-folder\agt0\lib\

N/A

Storage folder for the health check agent-specific library

jpcagt0msg.dll

Message catalog

installation-folder\agt0\store\

N/A

Agent Store service root folder

*.DB

Performance data files

*.IDX

Index files for the performance data files

*.LCK

Lock files for the performance data files

jpcsto.ini

Agent Store service configuration file

jpcsto.ini.model

Model file for the Agent Store service configuration file

installation-folder\agt0\store\STPD\

N/A

Storage folder for the performance data of the health check agent

installation-folder\agt0\store\STPI\

N/A

Storage folder for the performance data of the health check agent

installation-folder\agt0\store\STPL\

N/A

Storage folder for the performance data of the health check agent

installation-folder\auditlog\

N/A

Action log file output folder

jpcaudit.log#3

Action log file

installation-folder\bin\

N/A

Command storage folder

installation-folder\bin\action\

N/A

Base folder of Action Handler service

jpcah.exe

Service executing program of Action Handler

jpcah.ini

Service startup initialization file of Action Handler

jpcah.ini.model

Sample file for service startup initialization file of Action Handler

installation-folder\bin\action\log\

N/A

Storage folder for internal log file of Action Handler service

installation-folder\bin\NNMEx\

N/A

Storage folder for PFM - Web Console and NNM linkage facility commands

jpcactlh.exe

NNM linkage: additional action command

jpcovlnh.exe

NNM linkage: server operation management GUI startup command

jpcovobj.exe

NNM linkage: object manager

jpcovrpt.exe

NNM linkage: report linkage command

jpcovsts.exe

NNM linkage: status change command

jpcovsyc.exe

NNM linkage: map manager

installation-folder\bin\statsvr\

N/A

Base folder of Status Server service

jpcstat.ini

Service startup initialization file of Status Server

jpcstat.ini.model

Sample file for service startup initialization file of Status Server

jpcstatsvr.exe

Service executing program of Status Server

restart.ini

Setup file for PFM service automatic restart function

installation-folder\bin\statsvr\log\

N/A

Storage folder for internal log file of Status Server service

installation-folder\bin\store\

N/A

Base folder of Agent Store service and Remote Monitor Store service

jpcsto.exe#4

Service executing program of Agent Store and Remote Monitor Store

stpqlpr.exe#4

BACKUP and DUMP command

installation-folder\ITSLM\

N/A

Storage folder for the definition file for JP1/ITSLM-linkage custom monitoring items

monitoringitems.cfg

Definition file for JP1/ITSLM-linkage custom monitoring items

monitoringitems.cfg.model

Model file for the definition file for JP1/ITSLM-linkage custom monitoring items

installation-folder\lib\

N/A

Message catalog storage folder

jpcmgrmsg.dll

Message catalog

installation-folder\log\

N/A

Storage folder for log files

jpclog01#5

Common message log file (alternative)

jpclog02#5

Common message log file (alternative)

jpclogw01#5

Common message log file

jpclogw02#5

Common message log file

installation-folder\mgr\

N/A

PFM - Manager root folder

PATCHLOG.TXT

Log file for patches

readme.txt

README.TXT

VERSION.TXT

Version check file

installation-folder\mgr\clator\

N/A

Correlator service root folder

jpcep.exe

Correlator service executable program

jpcep.ini

Correlator service startup information file

jpcep.ini.model

Model file for the Correlator service startup information file

installation-folder\mgr\clator\log\

N/A

Storage folder for Correlator service internal log files

installation-folder\mgr\conf\

N/A

Storage folder for configuration files

installation-folder\mgr\ITSLM\

N/A

Storage folder for the JP1/ITSLM linkage setting file

installation-folder\mgr\lib\

N/A

Storage folder for the PFM - Manager-specific libraries

installation-folder\mgr\manager\

N/A

Master Manager service root folder

*.DAT

Data model definition files

*.DB

Data files containing definitions of alarms and actions, product information, and service configuration information

*.IDX

Index files for the data files containing definitions of alarms and actions, product information, and service configuration information

*.LCK

Lock files for the data files containing definitions of alarms and actions, product information, and service configuration information

jpcmm.exe

Master Manager service executable program

jpcmm.ini

Master Manager service startup information file

jpcmm.ini.model

Model file for the Master Manager service startup information file

updinfo_masus.dat

Monitoring suspension information file

installation-folder\mgr\manager\log\

N/A

Storage folder for Master Manager service internal log files

installation-folder\mgr\namesvr\

N/A

Name Server service root folder

*.DB

Data files containing service information

*.IDX

Index files for the data files containing service information

*.LCK

Lock files for the data files containing service information

jpcnsvr.exe

Name Server service executable program

jpcnsvr.ini

Name Server service startup information file

jpcnsvr.ini.model

Model file for the Name Server service startup information file

installation-folder\mgr\namesvr\log\

N/A

Storage folder for Name Server service internal log files

installation-folder\mgr\setup\

N/A

Storage folder for agent information

installation-folder\mgr\store\

N/A

Master Store service root folder

*.DAT

Data model definition files

*.DB

Data files containing alarm events

*.IDX

Index files for the data files containing alarm events

*.LCK

Lock files for the data files containing alarm events

jpcsto.ini

Master Store service startup information file

jpcsto.ini.model

Model file for the Master Store service startup information file

installation-folder\mgr\store\backup\

N/A

Standard database backup destination folder

installation-folder\mgr\store\dump\

N/A

Standard database export destination folder

installation-folder\mgr\store\log\

N/A

Storage folder for Master Store service internal log files

installation-folder\mgr\trapgen\

N/A

Trap Generator service root folder

jpctrap.exe

Trap Generator service executable program

jpctrap.ini

Trap Generator service startup information file

jpctrap.ini.model

Model file for the Trap Generator service startup information file

jpctraps.exe

SNMP trap transmission command

installation-folder\mgr\trapgen\log\

N/A

Storage folder for Trap Generator service internal log files

installation-folder\mgr\viewsvr\

N/A

View Server service root folder

jpcvsvr.exe

View Server service executable program

jpcvsvr.ini

View Server service startup information file

jpcvsvr.ini.model

Model file for the View Server service startup information file

installation-folder\mgr\viewsvr\data\

N/A

Storage folder for definitions

installation-folder\mgr\viewsvr\jre0900\

N/A

Storage folder for JRE

installation-folder\mgr\viewsvr\lib\

N/A

Storage folder for the View Server service-specific libraries

installation-folder\mgr\viewsvr\log\

N/A

Storage folder for View Server service internal log files

installation-folder\mgr\viewsvr\Reports\

N/A

Storage folder for report definition files

installation-folder\NNMEx\

N/A

Storage folder for PFM - Web Console and NNM linkage facility definition file

jpcnnm.ini

NNM linkage definition file

jpcnnm.ini.model

Sample file for NNM linkage definition file

jpcovsetup.bat

Setup script for NNM linkage facility

jpcovunsetup.bat

Unsetup script for NNM linkage facility

installation-folder\NNMEx\conf\

N/A

Configuration file-related folder.

jpctrapd.C

Trap definition and additional action definition files

jpctrapd.SJIS

Trap definition and additional action definition files

installation-folder\NNMEx\fields\

N/A

Configuration file-related folder

installation-folder\NNMEx\fields\C\

N/A

Field definition file folder

jpcovobj.frf

Object manager field definition file

installation-folder\NNMEx\html\

N/A

Storage folder for NNM linkage HTML file

jpcselectmgr.html

PFM - Manager selection window HTML file

jpcselectmgr.html.model

Sample file for PFM - Manager selection window HTML file

installation-folder\NNMEx\html\language-code\

N/A

Storage folder for language-specific HTML files for errors

jpcnnmerr1_language-code.html

HTML file 1 for error windows

jpcnnmerr2_language-code.html

HTML file 2 for error windows

jpcnnmerr3_language-code.html

HTML file 3 for error windows

installation-folder\NNMEx\lrf\

N/A

Local definition file-related folder

jpcovobj.lrf

Local definition file-related folder

installation-folder\NNMEx\registration\

N/A

Registration file-related folder

installation-folder\NNMEx\registration\$LANG\

N/A

Windows: ja_JP.Japanese_Japan.932

UNIX: C,ja_JP.EUC, ja_JP.PCK

jpcovsyc.arf

Symbol manager registration file

jpcview.arf

Menu command registration file

installation-folder\NNMEx\snmp_mibs\

N/A

SNMP MIB definition file-related folder

installation-folder\NNMEx\snmp_mibs\Vendor\

N/A

MIB OID structure vendor folder

installation-folder\NNMEx\snmp_mibs\Vendor\Hitachi\

N/A

MIB OID structure vendor name folder

jp1pc.oid

MIB OID registration file

installation-folder\NNMEx\symbols\

N/A

Symbol definition file-related folder

installation-folder\NNMEx\symbols\C\

N/A

Symbol definition file folder

installation-folder\NNMEx\symbols\C\jp1pc\

N/A

Symbol definition file folder

jp1pc.srf

Symbol definition file

jp1pc_generic.srf

Symbol definition file

jp1pc_nt.srf

Symbol definition file

jp1pc_unix.srf

Symbol definition file

installation-folder\patch_files\

N/A

Storage folder for patch files

installation-folder\pid\

N/A

Storage folder for PID information

installation-folder\setup\

N/A

Storage folder for setup files

jpcagt0u.Z

Archive file for PFM - Agent setup (UNIX)

jpcagt0w.EXE

Archive file for PFM - Agent setup (Windows)

installation-folder\setup\alarm\

N/A

Storage folder for alarm definition files

installation-folder\setup\extract\

N/A

Setup file expansion folder

installation-folder\setup\update\

N/A

Storage folder for INI file upgrade control files

installation-folder\sys\

N/A

Storage folder for PFM system information

installation-folder\tools\

N/A

Command storage folder

jpcagtsetup.exe

Additional setup command for PFM - Agent and PFM - RM

jpcalarm.exe

Alarm definition command

jpcconf.exe

Setup operation command

jpcctrl.exe

Service management command

jpchasetup.exe

Logical host environment setup command

jpcimevt.exe

JP1/IM linkage: JP1 event issuance command

jpcimsetup.exe

Service management command

jpcinslist.exe

Instance startup environment display command

jpcinssetup.exe

Instance startup environment setup command

jpcinsunsetup.exe

Instance startup environment unsetup command

jpcnsconfig.exe

Service configuration definition command

jpcnshostname.exe

Host name setting command

jpcras.bat

Maintenance information collection command

jpcresto.exe

Store data restore command

jpcspm.exe

Service start or stop request command

jpcstart.exe

Service start request command

jpcstop.exe

Service stop request command

jpcstsetup.exe

Status management function setup command

jpctool.exe

Operation command

installation-folder\tools\log\

N/A

Storage folder for command log files

Legend:

N/A: Not applicable

#1

This file does not exist in Windows Server 2008 and Windows Server 2012.

#2

A file named jpcns_backup.ini may be created in the same directory. This file is used internally by Performance Management. Do not change or delete this file.

#3

You can use the jpccomm.ini file to change the number of log files.

#4

The executable file of the old version, if any, will be deleted when overwrite installation is performed for Performance Management.

#5

The file name that is output differs depending on the output method for the log file.

For details about the output format of log files, see the chapter that describes how to detect error in Performance Management in the Job Management Partner 1/Performance Management User's Guide.

D.2 Files and directories for PFM - Manager (in UNIX)

The following table lists the files and directories for the UNIX version of PFM - Manager:

Important note

If you change the file permission, the product will no longer operate normally. Do not change the file permission.

If you change the umask setting, the file permission might be changed during operation. Do not change the umask setting.

Table D‒2: Files and directories for PFM - Manager (UNIX version)

Directory name

File name

File permission

Description

/etc/

rc.jp1_pc

555

Service automatic start script (AIX)

/etc/init.d/

jp1_pc

555

Service automatic start script (Solaris)

/etc/rc.d/init./d/

jp1_pc

555

Service automatic start script (Linux)

/opt/jp1pc/

inst.ini

644

Version information file

instmgr.ini

644

PFM - Manager product information file

jpc_start

555

Service automatic start script file#1

jpc_start.model

500

Sample file of service automatic start script file

jpc_stop

555

Service automatic stop script file#1

jpc_stop.model

500

Sample file of service automatic stop script file

jpccomm.ini#2

666

Startup information file common to all components

jpccomm.ini.model

444

Sample file for startup information file common to all components

jpchosts

644

Host information settings file

jpchosts.model

444

Sample file for host information settings file

jpcns.ini#2#3

644

Service configuration information file

jpcns.ini.model

444

Sample file for service configuration information file

jpcns_backup.ini

644

Backup file for service configuration information file

jpcplist.ini#2

644

Product definition file

jpcplist.ini.model

444

Sample file for product definition file

/opt/jp1pc/agt0/

N/A

755

Base directory of health check agent

jpcagtras

555

Script for collecting health check agent-specific information

/opt/jp1pc/agt0/agent/

N/A

755

Base directory of Agent Collector service

COSLMMI.DB

644

Data file for the JP1/ITSLM linkage settings

COSLMMI.IDX

644

Index file for the data file for the JP1/ITSLM linkage settings

COSLMMI.LCK

644

Lock file for the data file for the JP1/ITSLM linkage settings

jpc0collect

500

Agent Collector service subprocess

jpcagt.ini

500

Agent Collector service configuration file

jpcagt.ini.model

444

Model file for the Agent Collector service configuration file

jpcagt0

500

Agent Collector service

jpcitslm.ini

644

JP1/ITSLM linkage settings file

suspended.dat

644

Monitoring suspension information file

/opt/jp1pc/agt0/nls/

N/A

755

Storage folder for the health check agent-specific library

jpcagt0msg.cat

444

Message catalog

/opt/jp1pc/agt0/store/

N/A

755

Base directory of Agent Store service

*.DB

644

Performance data files

*.IDX

644

Index files for the performance data files

*.LCK

644

Lock files for the performance data files

jpcsto.ini

644

Agent Store service configuration file

jpcsto.ini.model

444

Model file for the Agent Store service configuration file

/opt/jp1pc/agt0/store/STPD/

N/A

755

Storage directory for the performance data of the health check agent

/opt/jp1pc/agt0/store/STPI/

N/A

755

Storage directory for the performance data of the health check agent

/opt/jp1pc/agt0/store/STPL/

N/A

755

Storage directory for the performance data of the health check agent

/opt/jp1pc/auditlog/

N/A

700

Action log file output directory

jpcaudit.log#4

500

Action log file

/opt/jp1pc/bin/

N/A

755

Command storage directory

/opt/jp1pc/bin/action/

N/A

755

Base directory of Action Handler service

jpcah

500

Service executing program of Action Handler

jpcah.ini#2

644

Service startup initialization file of Action Handler

jpcah.ini.model

444

Sample file of service startup initialization file of Action Handler

/opt/jp1pc/bin/action/log/

N/A

777

Storage directory for internal log file of Action Handler service

/opt/jp1pc/bin/NNMEx/

N/A#5

755

Storage directory for PFM - Web Console and NNM linkage facility commands

jpcactlh#5

555

NNM linkage: additional action command

jpcovlnh#5

555

NNM linkage: server operation management GUI startup command

jpcovobj#5

555

NNM linkage: object manager

jpcovrpt#5

555

NNM linkage: report linkage command

jpcovsts#5

555

NNM linkage: status change command

jpcovsyc#5

555

NNM linkage: map manager

/opt/jp1pc/bin/statsvr/

N/A

755

Base directory of Status Server service

jpcstat.ini#2

644

Service startup initialization file of Status Server

jpcstat.ini.model

444

Sample file for service startup initialization file of Status Server

jpcstatsvr

500

Service executing program of Status Server

restart.ini

666

Setup file for PFM service automatic restart function

/opt/jp1pc/bin/statsvr/log/

N/A

777

Storage directory for internal log file of Status Server service

/opt/jp1pc/bin/store/

N/A

755

Base directory of Agent Store service and Remote Monitor Store service

jpcsto

500

Service executing program of Agent Store and Remote Monitor Store

stpqlpr

500

BACKUP and DUMP command

/opt/jp1pc/ITSLM/

N/A

755

Storage directory for the definition file for JP1/ITSLM-linkage custom monitoring items

monitoringitems.cfg

644

Definition file for JP1/ITSLM-linkage custom monitoring items

monitoringitems.cfg.model

444

Model file for the definition file for JP1/ITSLM-linkage custom monitoring items

/opt/jp1pc/lib/

N/A

755

Storage directory for common libraries

libjpcaudit64VVRRnn.{a|so|sl}

555

PFM action log library

libjpcauditVVRRnn.{a|so|sl}

555

PFM action log library

libjpccomm64VVRRnn.{a|so|sl}#6

555

Performance Management common library

libjpccommVVRRnn.{a|so|sl}#7

555

Performance Management common library

/opt/jp1pc/log/

N/A

777

Storage directory for log files

jpclog01#8

555

Common message log file

jpclog02#8

555

Common message log file (alternative)

jpclogw01#8

555

Common message log file

jpclogw02#8

555

Common message log file (alternative)

/opt/jp1pc/mgr/

N/A

755

Base directory for PFM - Manager

PATCHLOG.TXT

644

Patch log file

/opt/jp1pc/mgr/clator/

N/A

755

Base directory for Correlator

jpcep

500

Correlator service executing program

jpcep.ini#2

644

Correlator service startup initialization file

jpcep.ini.model

444

Model file for Correlator service startup initialization file

/opt/jp1pc/mgr/clator/log/

N/A

777

Storage directory for Correlator internal logs

/opt/jp1pc/mgr/conf/

N/A

755

Storage directory for configuration files

/opt/jp1pc/mgr/ITSLM/

N/A

755

Storage directory for the JP1/ITSLM linkage settings file

/opt/jp1pc/mgr/lib/

N/A

755

Storage directory for the PFM - Manager-specific libraries

/opt/jp1pc/mgr/manager/

N/A

777

Base directory for Master Manager

*.DAT

444

Data model definition files

*.DB

644

Data files containing information such as definition information for alarms and actions, product information, service configuration information, and so on.

*.IDX

644

Index files for data files containing information such as definition information for alarms and actions, product information, service configuration information, and so on.

*.LCK

644

Lock files for data files containing information such as definition information for alarms and actions, product information, service configuration information, and so on.

jpcmm

500

Master Manager service executing program

jpcmm.ini#2

644

Master Manager service startup initialization file

jpcmm.ini.model

444

Model file for Master Manager service startup initialization file

updinfo_masus.dat

644

Monitoring suspension information file

/opt/jp1pc/mgr/manager/log/

N/A

777

Storage directory for internal Master Manager logs

/opt/jp1pc/mgr/namesvr/

N/A

755

Base directory for Name Server

*.DB

644

Service information data files

*.IDX

644

Index files for service information data files

*.LCK

644

Lock files for service information data files

jpcnsvr

500

Name Server service executing program

jpcnsvr.ini#2

644

Name Server service startup initialization file

jpcnsvr.ini.model

444

Model file for Name Server service startup initialization file

/opt/jp1pc/mgr/namesvr/log/

N/A

777

Storage directory for internal Name Server logs

/opt/jp1pc/mgr/setup/

N/A

755

Storage directory for agent information

/opt/jp1pc/mgr/store/

N/A

755

Base directory for Master Store

*.DAT

444

Data model definition files

*.DB

644

Alarm event data files

*.IDX

644

Index files for alarm event data files

*.LCK

644

Lock files for alarm event data files

jpcsto.ini#2

644

Master Store service startup initialization file

jpcsto.ini.model

444

Model file for Master Store service startup initialization file

/opt/jp1pc/mgr/store/backup/

N/A

755

Default database backup directory

/opt/jp1pc/mgr/store/dump/

N/A

777

Default database export directory

/opt/jp1pc/mgr/store/log/

N/A

777

Storage directory for internal Master Store logs

/opt/jp1pc/mgr/trapgen/

N/A

755

Base directory for Trap Generator

jpctrap

500

Trap Generator service executing program

jpctrap.ini#2

644

Trap Generator service startup initialization file

jpctrap.ini.model

444

Model file for Trap Generator service startup initialization file

jpctraps

500

SNMP trap send command

/opt/jp1pc/mgr/trapgen/log/

N/A

777

Storage directory for internal Trap Generator logs

/opt/jp1pc/mgr/viewsvr/

N/A

777

Base directory for View Server

jpcvsvr

500

View Server service executing program

jpcvsvr.ini#2

644

View Server service startup initialization file

jpcvsvr.ini.model

444

Model file for View Server service startup initialization file

/opt/jp1pc/mgr/viewsvr/data/

N/A

700

Storage directory for definition data

/opt/jp1pc/mgr/viewsvr/jre0900/

N/A

755

Storage directory for JRE

/opt/jp1pc/mgr/viewsvr/lib/

N/A

755

Storage directory for the View Server service-specific libraries

/opt/jp1pc/mgr/viewsvr/log/

N/A

777

Storage directory for internal View Server logs

/opt/jp1pc/mgr/viewsvr/Reports/

N/A

777

Storage directory for report definition information files

/opt/jp1pc/sys/

N/A

755

Storage directory for PFM system information

/opt/jp1pc/nls/

N/A

755

Storage directory for the message catalog

/opt/jp1pc/nls/$LANG/

N/A

755

Same as above

jpcmgrmsg.cat

444

Message catalog

/opt/jp1pc/NNMEx/

N/A#5

777

Storage directory for PFM - Web Console and NNM linkage facility definition files

jpcnnm.ini#5

644

NNM linkage definition file

jpcnnm.ini.model#5

444

Sample file for NNM linkage definition file

jpcovsetup.sh#5

544

Setup script for NNM linkage facility

jpcovunsetup.sh#5

544

Unsetup script for NNM linkage facility

/opt/jp1pc/NNMEx/conf/

N/A#5

755

Configuration file-related directory

jpctrapd.C#5

444

Trap definition and additional action definition files

jpctrapd.EUC#5

444

Trap definition and additional action definition files

jpctrapd.SJIS#5

444

Trap definition and additional action definition files

/opt/jp1pc/NNMEx/fields/

N/A#5

755

Field definition file-related directory

/opt/jp1pc/NNMEx/fields/C/

N/A#5

755

Field definition file directory

jpcovobj.frf#5

444

Object manager field definition file

/opt/jp1pc/NNMEx/html/

N/A#5

755

Storage directory for NNM linkage HTML files

jpcselectmgr.html#5

644

PFM - Manager selection window HTML file

jpcselectmgr.html.model#5

444

Sample file for PFM - Manager selection window HTML file

/opt/jp1pc/NNMEx/html/language-code/

N/A#5

755

Storage directory for language-specific HTML files for errors

jpcnnmerr1_language-code.html#5

444

HTML file 1 for error windows

jpcnnmerr2_language-code.html#5

444

HTML file 2 for error windows

jpcnnmerr3_language-code.html#5

444

HTML file 3 for error windows

/opt/jp1pc/NNMEx/lrf/

N/A#5

755

Local definition file-related directory

jpcovobj.lrf#5

444

Object manager local registration file

/opt/jp1pc/NNMEx/registration/

N/A#5

755

Registration file-related directory

/opt/jp1pc/NNMEx/registration/$LANG/

N/A#5

755

Windows:ja_JP.Japanese_Japan.932

UNIX:C,ja_JP.EUC,ja_JP.PCK

jpcovsyc.arf#5

444

Symbol manager registration file

jpcview.arf#5

444

Menu command registration file

/opt/jp1pc/NNMEx/snmp_mibs/

N/A#5

755

SNMP MIB definition file-related directory

/opt/jp1pc/NNMEx/snmp_mibs/Vendor/

N/A#5

755

MIB OID structure vendor directory

/opt/jp1pc/NNMEx/snmp_mibs/Vendor/Hitachi/

N/A#5

755

MIB OID structure vendor name directory

jp1pc.oid#5

444

MIB OID registration file

/opt/jp1pc/NNMEx/symbols/

N/A#5

777

Symbol definition file-related directory

/opt/jp1pc/NNMEx/symbols/C/

N/A#5

777

Symbol definition file directory

/opt/jp1pc/NNMEx/symbols/C/jp1pc/

N/A#5

777

Symbol definition file directory

jp1pc.srf#5

444

Symbol definition file

jp1pc_generic.srf#5

444

Symbol definition file

jp1pc_nt.srf#5

444

Symbol definition file

jp1pc_unix.srf#5

444

Symbol definition file

/opt/jp1pc/patch_files/

N/A

755

Storage directory for patch files

/opt/jp1pc/pid/

N/A

755

Storage directory for PID information

/opt/jp1pc/setup/

N/A

755

Storage directory for setup files

jpcagt0u.Z

444

Archive file for PFM - Agent setup (UNIX)

jpcagt0w.EXE

444

Archive file for PFM - Agent setup (Windows)

/opt/jp1pc/setup/alarm/

N/A

755

Storage directory for alarm definition files

/opt/jp1pc/setup/extract/

N/A

755

Storage directory for expanded setup files

/opt/jp1pc/setup/update/

N/A

755

Storage directory for INI file Vup control files

/opt/jp1pc/tools/

N/A

755

Storage directory for commands

jpcagtsetup

555

Additional setup command for PFM - Agent and PFM - RM

jpcalarm

555

Alarm definition command

jpcconf

555

Setup operation command

jpcctrl

4555 (with s-bit)

Service management command

jpchasetup

555

Command for setting up a logical host environment

jpcimevt

555

Linkage with JP1/IM: command for issuing JP1 events

jpcimsetup

555

Command for setting up and canceling setup of the JP1/IM monitoring object linkage function

jpcinslist

555

Command for displaying an instance startup environment

jpcinssetup

555

Command for setting up an instance startup environment

jpcinsunsetup

555

Command for canceling setup of an instance startup environment

jpcnsconfig

555

Service configuration definition command

jpcnshostname

555

Command for setting host names

jpcras

555

Command for collecting maintenance data

jpcresto

555

Command for restoring the Store database

jpcspm

555

Service start or stop request command

jpcstart

555

Command for issuing service startup requests

jpcstop

555

Command for issuing service stop requests

jpcstsetup

555

Command for setting up the status management function

jpctool

555

Operation command

/opt/jp1pc/tools/log/

N/A

777

Storage directory for command log files

/var/lock/subsys/

jp1_pc

644

Service automatic start lock file (Linux)

Legend:

N/A: Not applicable

#1

You create this file by copying it from the sample file.

#2

Files with the extension lck may be created in the same directory. These files are used internally by Performance Management. Do not change or delete these files.

Example: An installation-folder\jpccomm.ini.lck file exists for installation-folder\jpccomm.ini.

#3

A file named jpcns_backup.ini may be created in the same directory. This file is used internally by Performance Management. Do not change or delete this file.

#4

You can use the jpccomm.ini file to change the number of log files.

#5

This file exists only in Solaris.

#6

This file exists only in AIX.

#7

This file exists only in AIX, and Linux.

#8

The file name that is output differs depending on the output method for the log file.

For details about the output method for log files, see the chapter explaining how to detect errors in the Job Management Partner 1/Performance Management User's Guide.

D.3 Files and directories for PFM - Base (in Windows)

The following table lists the files and folders for the Windows version of PFM - Base:

Table D‒3: Files and folders for PFM - Base (Windows version)

Folder name

File name

Description

system-drive\Windows\System32\

N/A

Windows system folder

jpccommVVRRnn.dll

Performance Management common base library

jpcodbc.dll#1

ODBC driver

libjpcauditVVRRnn.dll

Performance Management action log library

libjpchcccomm[VVRRnn].dll

Log library for Performance Management character code conversion

libjpchccjpcomm[VVRRnn].dll

Log library for Performance Management character code conversion

MSVCIRT.DLL#1

Microsoft istream-related Runtime

msvcp100.dll

Microsoft C++ Runtime

MSVCP60.DLL#1

Microsoft C++ Runtime

msvcr100.dll

Microsoft C++ Runtime

MSVCRT.DLL#1

Microsoft C Runtime

tls704d.dll#1

RogueWave runtime

installation-folder\

inst.ini

Version information file

instagtp.ini

PFM - Base product information file

jpccomm.ini

Startup information file common to all components

jpccomm.ini.model

Sample file for startup information file common to all components

jpchosts

Host information settings file

jpchosts.model

Sample file for host information settings file

jpcns.ini#2

Service configuration information file

jpcns.ini.model

Sample file for service configuration information file

jpcns_backup.ini

Backup file for service configuration information file

jpcplist.ini

Product definition file

jpcplist.ini.model

Sample file for product definition file

installation-folder\agtp\

N/A

PFM - Base product information file

PATCHLOG.TXT

Patch log file

readme.txt

README.TXT

VERSION.TXT

Version check file

installation-folder\auditlog\

N/A

Action log file output folder

jpcaudit.log

Action log file

installation-folder\bin\

N/A

Command storage folder

installation-folder\bin\action\

N/A

Base folder of Action Handler service

jpcah.exe

Service executing program of Action Handler

jpcah.ini

Service startup initialization file of Action Handler

jpcah.ini.model

Sample file for service startup initialization file of Action Handler

installation-folder\bin\action\log\

N/A

Storage folder for internal log file of Action Handler service

installation-folder\bin\NNMEx\

N/A#1

Storage folder for PFM - Web Console and NNM linkage facility commands

jpcactlh.exe#1

NNM linkage: additional action command

jpcovlnh.exe#1

NNM linkage: server operation management GUI startup command

jpcovobj.exe#1

NNM linkage: object manager

jpcovrpt.exe#1

NNM linkage: report linkage command

jpcovsts.exe#1

NNM linkage: status change command

jpcovsyc.exe#1

NNM linkage: map manager

installation-folder\bin\statsvr\

N/A

Base folder of Status Server service

jpcstat.ini

Service startup initialization file of Status Server

jpcstat.ini.model

Sample file for service startup initialization file of Status Server

jpcstatsvr.exe

Service executing program of Status Server

restart.ini

Setup file for PFM service automatic restart function

installation-folder\bin\statsvr\log\

N/A

Storage folder for internal log file of Action Handler service

installation-folder\bin\store\

N/A

Base folder of Agent Store service and Remote Monitor Store service

jpcsto.exe#3

Agent Store service and Remote Monitor Store service

stpqlpr.exe#3

BACKUP and DUMP command

installation-folder\lib\

N/A

Storage folder for common message catalogs

jpcmgrmsg.dll

Message catalog

installation-folder\log\

N/A

Storage folder for log files

jpclog01#4

Common message log file

jpclog02#4

Common message log file (alternative)

jpclogw01#4

Common message log file

jpclogw02#4

Common message log file (alternative)

installation-folder\NNMEx\

N/A#1

Storage folder for PFM - Web Console and NNM linkage facility definition files

jpcnnm.ini#1

NNM linkage definition file

jpcnnm.ini.model#1

Sample file for NNM linkage definition file

jpcovsetup.bat#1

Setup script for NNM linkage facility

jpcovunsetup.bat#1

Unsetup script for NNM linkage facility

installation-folder\NNMEx\conf\

N/A#1

Configuration file-related folder

jpctrapd.C#1

Trap definition and additional action definition files

jpctrapd.SJIS#1

Trap definition and additional action definition files

installation-folder\NNMEx\fields\

N/A#1

Field definition file-related folder

installation-folder\NNMEx\fields\C\

N/A#1

Field definition file folder

jpcovobj.frf#1

Object manager field definition file

installation-folder\NNMEx\html\

N/A#1

Storage folder for NNM linkage HTML files

jpcselectmgr.html#1

PFM - Manager selection window HTML file

jpcselectmgr.html.model#1

Sample file for PFM - Manager selection window HTML file

installation-folder\NNMEx\html\language-code\

N/A#1

Storage folder for language-specific HTML files for errors

jpcnnmerr1_language-code.html#1

HTML file 1 for error windows

jpcnnmerr2_language-code.html#1

HTML file 2 for error windows

jpcnnmerr3_language-code.html#1

HTML file 3 for error windows

installation-folder\NNMEx\lrf\

N/A#1

Local definition file-related folder

jpcovobj.lrf#1

Object manager local registration file

installation-folder\NNMEx\registration\

N/A#1

Registration file-related folder

installation-folder\NNMEx\registration\$LANG\

N/A#1

Windows:ja_JP.Japanese_Japan.932

UNIX:C,ja_JP.EUC,ja_JP.PCK

jpcovsyc.arf#1

Symbol manager registration file

jpcview.arf#1

Menu command registration file

installation-folder\NNMEx\snmp_mibs\

N/A#1

SNMP MIB definition file-related folder

installation-folder\NNMEx\snmp_mibs\Vendor\

N/A#1

MIB OID structure vendor folder

installation-folder\NNMEx\snmp_mibs\Vendor\Hitachi\

N/A#1

MIB OID structure vendor name folder

jp1pc.oid#1

MIB OID registration file

installation-folder\NNMEx\symbols\

N/A#1

Symbol definition file-related folder

installation-folder\NNMEx\symbols\C\

N/A#1

Symbol definition file folder

installation-folder\NNMEx\symbols\C\jp1pc\

N/A#1

Symbol definition file folder

jp1pc.srf#1

Symbol definition file

jp1pc_generic.srf#1

Symbol definition file

jp1pc_nt.srf#1

Symbol definition file

jp1pc_unix.srf#1

Symbol definition file

installation-folder\patch_files\

N/A

Folder for patch files

installation-folder\pid\

N/A

Storage folder for PID information

installation-folder\setup\

N/A

Storage folder for patch files

installation-folder\setup\alarm\

N/A

Storage folder for alarm definition files

installation-folder\setup\extract\

N/A

Setup file expansion folder

installation-folder\setup\update\

N/A

Storage folder for INI file Vup control files

installation-folder\sys\

N/A

Storage folder for PFM system information

installation-folder\tools\

N/A

Command storage folder

jpcagtsetup.exe

Additional setup command for PFM - Agent and PFM - RM

jpcconf.exe

Setup operation command

jpcctrl.exe

Service management command

jpchasetup.exe

Logical host environment setup command

jpcimevt.exe

JP1/IM linkage: JP1 event issuance command

jpcinslist.exe

Instance startup environment display command

jpcinssetup.exe

Instance startup environment setup command

jpcinsunsetup.exe

Instance startup environment unsetup command

jpcnsconfig.exe

Service configuration definition command

jpcnshostname.exe

Host name setting command

jpcras.bat

Maintenance information collection command

jpcresto.exe

Store data restore command

jpcspm.exe

Service start or stop request command

jpcstart.exe

Service start request command

jpcstop.exe

Service stop request command

jpcstsetup.exe

Status management function setup command

jpctool.exe

Operation command

installation-folder\tools\log\

N/A

Folder for log output

Legend:

N/A: Not applicable

#1

32-bit version

#2

A file named jpcns_backup.ini may be created in the same directory. This file is used internally by Performance Management. Do not change or delete this file.

#3

The executable file of the old version, if any, will be deleted when overwrite installation is performed for Performance Management.

#4

The file name that is output differs depending on the output method for the log file.

For details about the output method for log files, see the chapter explaining how to detect errors in the Job Management Partner 1/Performance Management User's Guide.

D.4 Files and directories for PFM - Base (in UNIX)

The following table lists the files and directories for the UNIX version of PFM - Base:

Important note

If you change the file permission, the product will no longer operate normally. Do not change the file permission.

If you change the umask setting, the file permission may be changed during operation. Do not change the umask setting.

Table D‒4: Files and directories for PFM - Base (UNIX version)

Directory name

File name

File permission

Description

/etc/

rc.jp1_pc

555

Service automatic start script (AIX)

/etc/init.d/

jp1_pc

555

Service automatic start script (Solaris)

/etc/rc.d/init.d/

jp1_pc

555

Service automatic start script (Linux)

/opt/jp1pc/

inst.ini

644

Version information file

instagtp.ini

644

PFM - Base product information file

jpc_start

555

Service automatic start script file#1

jpc_start.model

600

Sample file of service automatic start script file

jpc_stop

555

Service automatic stop script file#1

jpc_stop.model

600

Sample file of service automatic stop script file

jpccomm.ini#2

666

Startup information file common to all components

jpccomm.ini.model

444

Sample file for startup information file common to all components

jpchosts

644

Host information settings file

jpchosts.model

444

Sample file for host information settings file

jpcns.ini#2#3

644

Service configuration information file

jpcns.ini.model

444

Sample file for service configuration information file

jpcns_backup.ini

644

Backup file for service configuration information file

jpcplist.ini#2

644

Product definition file

jpcplist.ini.model

444

Sample file for product definition file

/opt/jp1pc/agtp/

N/A

755

Directory for PFM - Base

PATCHLOG.TXT

644

Patch log file

/opt/jp1pc/auditlog/

N/A

700

Action log file output directory

jpcaudit.log#4

500

Action log file

/opt/jp1pc/bin/

N/A

755

Command storage directory

/opt/jp1pc/bin/action/

N/A

755

Base directory of Action Handler service

jpcah

500

Service executing program of Action Handler

jpcah.ini#2

644

Service startup initialization file of Action Handler

jpcah.ini.model

444

Sample file of service startup initialization file of Action Handler

/opt/jp1pc/bin/action/log/

N/A

777

Storage directory for internal log file of Action Handler service

/opt/jp1pc/bin/NNMEx/

N/A#5

755

Storage directory for PFM - Web Console and NNM linkage facility commands

jpcactlh#5

555

NNM linkage: additional action command

jpcovlnh#5

555

NNM linkage: server operation management GUI startup command

jpcovobj#5

555

NNM linkage: object manager

jpcovrpt#5

555

NNM linkage: report linkage command

jpcovsts#5

555

NNM linkage: status change command

jpcovsyc#5

555

NNM linkage: map manager

/opt/jp1pc/bin/statsvr/

N/A

755

Base directory of Status Server service

jpcstat.ini#2

644

Service startup initialization file of Status Server

jpcstat.ini.model

444

Sample file for service startup initialization file of Status Server

jpcstatsvr

500

Service executing program of Status Server

/opt/jp1pc/bin/statsvr/log/

N/A

777

Storage directory for internal log file of Status Server service

/opt/jp1pc/bin/store/

N/A

755

Base directory of Agent Store service and Remote Monitor Store service

jpcsto

500

Service executing program of Agent Store and Remote Monitor Store

stpqlpr

500

BACKUP and DUMP command

/opt/jp1pc/lib/

N/A

755

Storage directory for common libraries

libjpcaudit64VVRRnn.{a|so|sl}

555

PFM action log library

libjpcauditVVRRnn.{a|so|sl}

555

PFM action log library

libjpccomm64VVRRnn.{a|so|sl}#6

555

Performance Management common library

libjpccommVVRRnn.{a|so|sl}#7

555

Performance Management common library

/opt/jp1pc/log/

N/A

777

Storage directory for log files

jpclog01#8

666

Common message log file

jpclog02#8

666

Common message log file (alternative)

jpclogw01#8

666

Common message log file

jpclogw02#8

666

Common message log file (alternative)

/opt/jp1pc/sys/

N/A

755

Storage directory for PFM system information

/opt/jp1pc/nls/

N/A

755

Storage directory for message catalogs

/opt/jp1pc/nls/$LANG/

N/A

755

Same as the above

jpcmgrmsg.cat

444

Message catalog

/opt/jp1pc/NNMEx/

N/A#5

755

Storage directory for PFM - Web Console and NNM linkage facility definition files

jpcnnm.ini#5

644

NNM linkage definition file

jpcnnm.ini.model#5

444

Sample file for NNM linkage definition file

jpcovsetup.sh#5

644

Setup script for NNM linkage facility

jpcovunsetup.sh#5

644

Unsetup script for NNM linkage facility

/opt/jp1pc/NNMEx/conf/

N/A#5

755

Configuration file-related folder

jpctrapd.C#5

444

Trap definition and additional action definition files

jpctrapd.EUC#5

444

Trap definition and additional action definition files

jpctrapd.SJIS#5

444

Trap definition and additional action definition files

/opt/jp1pc/NNMEx/fields/

N/A#5

755

Field definition file-related directory

/opt/jp1pc/NNMEx/fields/C/

N/A#5

755

Field definition file directory

jpcovobj.frf#5

444

Object manager field definition file

/opt/jp1pc/NNMEx/html/

N/A#5

755

Storage directory for NNM linkage HTML files

jpcselectmgr.html#5

644

PFM - Manager selection window HTML file

jpcselectmgr.html.model#5

444

Sample file for PFM - Manager selection window HTML file

/opt/jp1pc/NNMEx/html/language-code/

N/A#5

755

Storage directory for language-specific HTML files for errors

jpcnnmerr1_language-code.html#5

444

HTML file 1 for error windows

jpcnnmerr2_language-code.html#5

444

HTML file 2 for error windows

jpcnnmerr3_language-code.html#5

444

HTML file 3 for error windows

/opt/jp1pc/NNMEx/lrf/

N/A#5

755

Local definition file-related directory

jpcovobj.lrf#5

444

Object manager local registration file

/opt/jp1pc/NNMEx/registration/

N/A#5

755

Registration file-related directory

/opt/jp1pc/NNMEx/registration/$LANG/

N/A#5

755

Windows:ja_JP.Japanese_Japan.932

UNIX:C,ja_JP.EUC,ja_JP.PCK

jpcovsyc.arf#5

444

Symbol manager registration file

jpcview.arf#5

444

Menu command registration file

/opt/jp1pc/NNMEx/snmp_mibs/

N/A#5

755

SNMP MIB definition file-related directory

/opt/jp1pc/NNMEx/snmp_mibs/Vendor/

N/A#5

755

MIB OID structure vendor directory

/opt/jp1pc/NNMEx/snmp_mibs/Vendor/Hitachi/

N/A#5

755

MIB OID structure vendor name directory

jp1pc.oid#5

444

MIB OID registration file

/opt/jp1pc/NNMEx/symbols/

N/A#5

755

Symbol definition file-related directory

/opt/jp1pc/NNMEx/symbols/C/

N/A#5

755

Symbol definition file directory

/opt/jp1pc/NNMEx/symbols/C/jp1pc/

N/A#5

755

Symbol definition file directory

jp1pc.srf#5

444

Symbol definition file

jp1pc_generic.srf#5

444

Symbol definition file

jp1pc_nt.srf#5

444

Symbol definition file

jp1pc_unix.srf#5

444

Symbol definition file

/opt/jp1pc/patch_files/

N/A

755

Storage directory for patch files

/opt/jp1pc/pid/

N/A

755

Storage directory for PID information

/opt/jp1pc/setup/

N/A

755

Storage directory for setup files

/opt/jp1pc/setup/alarm/

N/A

755

Storage directory for alarm definition files

/opt/jp1pc/setup/extract/

N/A

755

Setup file expansion directory

/opt/jp1pc/setup/update/

N/A

755

Storage directory for INI file Vup control files

/opt/jp1pc/tools/

N/A

755

Storage directory for commands

jpcagtsetup

555

Additional setup command for PFM - Agent and PFM - RM

jpcconf

555

Setup operation command

jpcctrl

4555 (with s-bit)

Service management command

jpchasetup

555

Command for setting up a logical host environment

jpcimevt

555

Linkage with JP1/IM: command for issuing JP1 events

jpcinslist

555

Command for displaying an instance startup environment

jpcinssetup

555

Command for setting up an instance startup environment

jpcinsunsetup

555

Command for canceling setup of an instance startup environment

jpcnsconfig

555

Service configuration definition command

jpcnshostname

555

Command for setting host names

jpcras

555

Command for collecting maintenance data

jpcresto

555

Command for restoring the Store database

jpcspm

555

Service start or stop request command

jpcstart

555

Command for issuing service startup requests

jpcstop

555

Command for issuing service stop requests

jpcstsetup

555

Command for setting up the status management function

jpctool

555

Operation command

/opt/jp1pc/tools/log/

N/A

777

Storage directory for command log files

/sbin/init.d/

jp1_pc

555

Service automatic start script (HP-UX)

/var/lock/subsys/

jp1_pc

644

Service automatic start lock file (Linux)

Legend:

N/A: Not applicable

#1

You create this file by copying it from the sample file.

#2

Files with the extension lck may be created in the same directory. These files are used internally by Performance Management. Do not change or delete these files.

Example: An installation-folder\jpccomm.ini.lck file exists for installation-folder\jpccomm.ini.

#3

A file named jpcns_backup.ini may be created in the same directory. This file is used internally by Performance Management. Do not change or delete this file.

#4

You can use the jpccomm.ini file to change the number of log files.

#5

This file exists only in HP-UX and Solaris.

#6

This file exists only in HP-UX and AIX.

#7

This file exists only in HP-UX, AIX, and Linux.

#8

The file name that is output differs depending on the output method for the log file.

For details about the output method for log files, see the chapter on using the log file trapping function for detecting errors in the Job Management Partner 1/Performance Management User's Guide.

D.5 Files and directories for PFM - Web Console (in Windows)

The following table lists the files and folders for the Windows version of PFM - Web Console:

Table D‒5: Files and folders for PFM - Web Console (Windows)

Folder name

File name

Description

installation-folder\

readme.txt

README.TXT

VERSION.TXT

File that describes the name and version of the program product

installation-folder\bin\

N/A

Storage folder for the PFM - Web Console service

jpcwadmin.exe#1

Program for starting the administrator console (Web Console)

jpcwebcon.exe

PFM - Web Console service executing program

jpcwstatus.exe

Command for obtaining the service status

jpcwvcheck.exe

Command for comparing text file versions

installation-folder\bookmarks\

N/A

Storage directory for bookmarks

installation-folder\cmdkey\

N/A

Storage folder for authentication key files

installation-folder\conf\

N/A

Storage folder for configuration files

aspsv_params.dtd

DTD file for parameter file used in commands

asrec_params.dtd

config.dtd

DTD file for initialization file

config.xml

Initialization file

pfmwebcon_host.conf

Configuration file for linking start and stop by the jpcspm command

pr.properties

System property file

processmonitoring_params.dtd

DTD file for parameter file used in commands

rdef_create_params.dtd

rdef_delete_params.dtd

rdef_output_params.dtd

rdef_params.dtd

rpt_params.dtd

installation-folder\CPSB\

N/A

Storage folder for PFM - Web Service service

installation-folder\CPSB\CC\web\containers\PFMWebConsole\usrconf\

usrconf.properties

User properties file

installation-folder\CPSB\CC\web\redirector\

workers.properties

Worker definition file

installation-folder\CPSB\httpsd\conf\

httpsd.conf

Web Server configuration file

installation-folder\doc\

N/A

Storage folder for HTML or PDF manuals

installation-folder\doc\language-code\

N/A

Storage folder for language-specific HTML or PDF manuals

installation-folder\doc\language-code\pcop\

N/A

Storage folder for the Job Management Partner 1/Performance Management User's Guide

installation-folder\doc\language-code\pcre\

N/A

Storage folder for the manual Job Management Partner 1/Performance Management Reference

installation-folder\doc\language-code\pcsy\

N/A

Storage folder for the Job Management Partner 1/Performance Management Planning and Configuration Guide

installation-folder\lib\

N/A

Storage folder for libraries and internal commands

installation-folder\log\

N/A

Storage folder for log files

jpcaspsv_<subcmd>_loglog-file-number#2.log

Log file

jpcasrec_<subcmd>_loglog-file-number#2.log

jpcmkkey_loglog-file-number#2.log

jpcprocdef_<subcmd>_loglog-file-number#2.log

jpcrdef_<subcmd>_loglog-file-number#2.log

jpcrpt_<pid>_loglog-file-number#2.log

jpcwtracelog-file-number#2.log

installation-folder\ML\

N/A

Storage folder for modification patch information for the integrated model name

installation-folder\ossSource\

N/A

Storage folder for the source file of the open source software

*.zip

Source file (zip format) of the open source software

installation-folder\processMonitoringTemplates\

N/A

Storage directory for application definition templates

installation-folder\reportcache\

N/A

Storage folder for report cache files

installation-folder\reportcache\cmd\

N/A

Storage folder for report cache files (for command output)

installation-folder\reportcache\serv\

N/A

Storage folder for report cache files (for output of the monitoring console window)

installation-folder\resources\

N/A

Storage folder for resource files

installation-folder\resources\descriptions\

*.dat

Storage folder for data model description files

installation-folder\resources\properties\

*.dat

Storage folder for property definition files

installation-folder\sample\

N/A

Storage folder for sample files

installation-folder\sample\conf\

N/A

Storage folder for the original config.xml file and the samples of the parameter files used by the jpcrpt command

config.xml

config_language-code.xml

Original language-specific config.xml file

jpcrpt-parameters.xml

jpcrpt-parameters_language-code.xml

Sample of a parameter file for outputting a report by using the jpcrpt command

jpcrpt-parameters-for-combination-report.xml

jpcrpt-parameters-for-combination-report_language-code.xml

Sample of a parameter file for outputting a combination report by using the jpcrpt command

jpcrpt-parameters-for-registration-report.xml

jpcrpt-parameters-for-registration-report_language-code.xml

Sample of a parameter file for outputting a registration report by using the jpcrpt command

jpcrpt-parameters-for-scheduled-operation*.xml

Sample of a parameter file for outputting a report by using the jpcrpt command with the relative time specified

installation-folder\sample\imconf\

N/A

Storage folder for samples of JP1/IM linkage definition files

hitachi_jp1_pfmwebcon_attr_language-code.conf

Sample of a language-specific definition file for extended event attributes

hitachi_jp1_pfmwebcon_mon_language-code.conf

Sample of a language-specific definition file for opening monitor windows

hitachi_jp1_pfmwebcon_tree.conf

Sample of a definition file for the tool launcher

installation-folder\sample\processmonitoringcommand\

N/A

Storage folder for the samples of application definition files used by the jpcprocdef command

jpcprocdef-parameters-unix.xml

Sample file of an application definition file for defining UNIX host process monitoring by using the jpcprocdef create command

jpcprocdef-parameters-windows.xml

Sample file of an application definition file for defining Windows host process monitoring by using the jpcprocdef create command

installation-folder\setup\

N/A

Storage folder for Agent archive files

installation-folder\tools\

N/A

Command storage folder

jpcaspsv.exe

Command file

jpcasrec.exe

jpcmkkey.exe

jpcprocdef.exe

jpcrdef.exe

jpcrpt.exe

jpcwagtsetup.bat

jpcwbackup.bat

jpcwras.bat

jpcwstart.bat

jpcwstop.bat

system-drive\Program Files\Common Files\Hitachi\

N/A

Storage folder for public DLL files of HNTRLib2

*#3

Public DLL files of HNTRLib2

system-drive\Program Files\Hitachi\HNTRLib2\

N/A

Storage folder for the executable file or the include file of HNTRLib2

*#3

The Executable file or the include file of HNTRLib2

system-drive\Program Files\Hitachi\systoru\

N/A

Storage folder for systoru files

*#3

systoru file

Legend:

N/A: Not applicable

#1

This file exists only in Windows Server 2008 and Windows Server 2012.

#2

log-file-number is the number of created log files, beginning from 1.

#3

* indicates an arbitrary character string.

D.6 Files and directories for PFM - Web Console (in UNIX)

The following table lists the files and directories for the UNIX version of PFM - Web Console:

Table D‒6: Files and directories for PFM - Web Console (for UNIX)

Directory name

File name

File permission#1

Description

/etc/rc.d/init.d/

jp1_webcon

500

Script for automatic service startup

/opt/hitachi/common/

N/A

555

HCCLib directory

/opt/hitachi/HNTRLib2/

N/A

555

HNTRLib2 directory

/opt/jp1pcwebcon/

N/A

755

PFM - Web Console installation destination

install.ini

400

Storage file for installation version information

jpcw_start.model

500

Model file for the service automatic startup shell

jpcw_stop.model

500

Model file for the service automatic stop shell

/opt/jp1pcwebcon/bin/

jpcwstatus

555

Command for obtaining the service status

jpcwvcheck

555

Command for comparing text file versions

/opt/jp1pcwebcon/bookmarks/

N/A

755

Storage directory for bookmark data

/opt/jp1pcwebcon/cmdkey/

N/A

755

Storage directory for the key file for authentication

/opt/jp1pcwebcon/conf/

N/A

755

Storage directory for configuration files

aspsv_params.dtd

644

DTD files for the parameter files used by commands

asrec_params.dtd

644

config.dtd

644

DTD file for the initialization file

config.xml

644

Initialization file

pfmwebcon_host.conf

644

Configuration file for linking start and stop by the jpcspm command

pr.properties

644

System property file

processmonitoring_params.dtd

644

DTD files for the parameter files used by commands

rdef_create_params.dtd

644

rdef_delete_params.dtd

644

rdef_output_params.dtd

644

rdef_params.dtd

644

rpt_params.dtd

644

/opt/jp1pcwebcon/CPSB/

N/A

755

Storage directory for the PFM - Web Service service

/opt/jp1pcwebcon/CPSB/CC/web/containers/PFMWebConsole/usrconf/

usrconf.properties

444

User properties file

/opt/jp1pcwebcon/CPSB/CC/web/redirector/

workers.properties

444

Worker definition file

/opt/jp1pcwebcon/CPSB/httpsd/conf/

httpsd.conf

644

Web Server configuration file

/opt/jp1pcwebcon/doc/

N/A

755

Storage directory for HTML or PDF manuals

/opt/jp1pcwebcon/doc/language-code/

N/A

755

Storage directory for language-specific HTML or PDF manuals

/opt/jp1pcwebcon/doc/language-code/pcop/

N/A

755

Storage directory for the Job Management Partner 1/Performance Management User's Guide

/opt/jp1pcwebcon/doc/language-code/pcre/

N/A

755

Storage directory for the manual Job Management Partner 1/Performance Management Reference

/opt/jp1pcwebcon/doc/language-code/pcsy/

N/A

755

Storage directory for the Job Management Partner 1/Performance Management Planning and Configuration Guide

/opt/jp1pcwebcon/lib/

N/A

755

Storage directory for libraries

/opt/jp1pcwebcon/log/

N/A

777

Storage directory for log files

jpcaspsv_<subcmd>_loglog-file-number#2.log

666

Log files

jpcasrec_<subcmd>_loglog-file-number#2.log

666

jpcmkkey_loglog-file-number#2.log

666

jpcprocdef_<subcmd>_loglog-file-number#2.log

666

jpcrdef_<subcmd>_loglog-file-number#2.log

666

jpcrpt_<pid>_loglog-file-number#2.log

666

jpcwstart.log

666

jpcwstop.log

666

jpcwtracelog-file-number#2.log

666

/opt/jp1pcwebcon/ML/

N/A

755

Storage folder for modification patch information for the integrated model name

/opt/jp1pcwebcon/ossSource/

N/A

755

Storage directory for the source file of open source software

*.zip

644

Source file (zip format) of open source software

/opt/jp1pcwebcon/processMonitoringTemplates/

N/A

755

Storage directory for application definition templates

/opt/jp1pcwebcon/reportcache/

N/A

755

Storage folder for report cache files

/opt/jp1pcwebcon/reportcache/cmd/

N/A

755

Storage folder for report cache files (for command output)

/opt/jp1pcwebcon/reportcache/serv/

N/A

755

Storage folder for report cache files (for output of the monitoring console window)

/opt/jp1pcwebcon/resources/

N/A

755

Storage directory for resource files

/opt/jp1pcwebcon/resources/descriptions/

*.dat

444

Storage directory for data model description files

/opt/jp1pcwebcon/resources/properties/

*.dat

444

Storage directory for property definition files

/opt/jp1pcwebcon/sample/

N/A

755

Storage directory for sample files

/opt/jp1pcwebcon/sample/conf/

N/A

755

Storage directory for the original config.xml file and the samples of parameter files used by the jpcrpt command

config.xml

config_language-code.xml

644

Original language-specific config.xml file

jpcrpt-parameters.xml

jpcrpt-parameters_language-code.xml

644

Sample of a parameter file for outputting a report by using the jpcrpt command

jpcrpt-parameters-for-combination-report.xml

jpcrpt-parameters-for-combination-report_language-code.xml

644

Sample of a parameter file for outputting a combination report by using the jpcrpt command

jpcrpt-parameters-for-registration-report.xml

jpcrpt-parameters-for-registration-report_language-code.xml

644

Sample of a parameter file for outputting a registration report by using the jpcrpt command

jpcrpt-parameters-for-scheduled-operation*.xml

644

Sample of a parameter file for outputting a report by using the jpcrpt command with the relative time specified

/opt/jp1pcwebcon/sample/imconf/

N/A

755

Storage directory for samples of JP1/IM linkage definition files

hitachi_jp1_pfmwebcon_attr_language-code.conf

644

Samples of language-specific JP1/IM linkage definition files

hitachi_jp1_pfmwebcon_mon_language-code.conf

644

hitachi_jp1_pfmwebcon_tree.conf

644

/opt/jp1pcwebcon/sample/processmonitoringcommand/

N/A

755

Storage folder for the samples of application definition files used by the jpcprocdef command

jpcprocdef-parameters-unix.xml

644

Sample file of an application definition file for defining UNIX host process monitoring by using the jpcprocdef create command

jpcprocdef-parameters-windows.xml

644

Sample file of an application definition file for defining Windows host process monitoring by using the jpcprocdef create command

/opt/jp1pcwebcon/setup/

N/A

755

Storage directory for Agent archives

/opt/jp1pcwebcon/tools/

N/A

755

Storage directory for commands

jpcaspsv

555

Command files

jpcasrec

555

jpcmkkey

555

jpcprocdef

555

jpcrdef

555

jpcrpt

555

jpcwagtsetup

555

jpcwbackup

555

jpcwras

555

jpcwstart

555

jpcwstop

555

/var/lock/subsys/

jp1_webcon

644

Lock file for automatic service startup

(only for Linux)

Legend:

N/A: Not applicable

#1

If you change the file permission, the product will no longer operate normally. Do not change the file permission.

If you change the umask setting, the file permission might be changed during operation. In such a case, the product will no longer operate normally. Do not change the umask setting.

#2

log-file-number is the number of created log files, beginning from 1.

D.7 Files and directories for PFM - Agent or PFM - RM

For the lists of files and directories for PFM - Agent or PFM - RM, see the description of the files and directories in the appendix of each PFM - Agent or PFM - RM manual.

E. Initialization File (config.xml)

The initialization file is an XML-format file used to set up an operating environment for PFM - Web Console. It is read when PFM - Web Console starts.

The storage directory for the initialization file (config.xml) is as follows:

In Windows:

installation-folder\conf\

In UNIX:

/opt/jp1pcjp1pcwebcon/conf/

Note

To restore config.xml to its status before editing, you must copy it from the following directory and then overwrite the directory shown above:

In Windows:

installation-folder\sample\conf\config.xml

In UNIX:

/opt/jp1pcwebcon/sample/conf/config.xml

If the same item is specified more than once in a single <param> tag, the first element is effective and the second and subsequent elements are ignored. This is not treated as an error.

E.1 Initialization file settings (config.xml)

The following table describes the setting items in the initialization file (config.xml).

(1) Setting file output

Table E‒1: Setting items for file output

Item

Description

characterCode

Specifies the character code that is to be output when the report displayed in the PFM - Web Console window is output in CSV format or when a file is output in CSV format by the jpcrpt command. The specifiable values are as follows:

US-ASCII

windows-1252

ISO-8859-1

UTF-8

UTF-16

UTF-16BE

UTF-16LE

Shift_JIS

EUC-JP

EUC-JP-LINUX

MS932

The default is UTF-8. If any other value is specified, the default value is set.

csvFileName

Specifies the name of the file to which the report displayed in the PFM - Web Console window is to be output in CSV format. Specify the file name by using characters totalling 100 bytes or less. The following characters can be used:

Numeric characters 0 to 9

. (period)

_ (underscore)

Single-byte space

Alphabetic characters A to Z and a to z

Note that you cannot specify a name consisting of only a single-byte space and period (.).

The default is Export.csv. If any value other than those allowed is specified, the default value is set.

lineSeparator

Specifies the end-of-line symbol that is to be output when the report displayed in the PFM - Web Console window is output in CSV format or when a file is output in CSV format by the jpcrpt command. The specifiable values are as follows:

CRLF: Linefeed code supported by Windows

LF: Linefeed code supported by UNIX

The default is CRLF.

If any value other those allowed is specified, the default value is set.

logDir

Specifies the directory to which PFM - Web Console log files are to be output.

You can specify single-byte alphanumeric characters or single-byte symbols.

Note that you cannot use the following characters:

In Windows:

$ % ^ ' ! = + { } @ [ ] ;

The default directory is as follows:

In Windows:

installation-folder\log\

In UNIX:

/opt/jp1pcwebcon/log/

If an invalid directory is specified or specification is omitted, the default value is set.

logFileNumber

Specifies the number of log files to be output by PFM - Web Console as an integer.

Specifiable values: 1 to 16

Default: 10

If the specified value is outside the specifiable range, the default value is set.

logFileNumberMulti

Specifies the number of log files to be output by the jpcrpt command as an integer.

Specifiable values: 1 to 64

Default: 10

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

When the outputMultiProcessForJpcrpt value is false, this setting is ineffective, and the logFileNumber setting value of <logging> is applied.

logFileRetention

Specifies the number of days for which log files are to be retained as an integer. This specification sets the retention period for log files output by the jpcrpt command.

Specifiable values: 1 to 30

Specifiable values: 1 to 30

If the specified value is outside the specifiable range, the default value is set.

logFileSize

Specifies the size of a single log file in megabytes.

Specifiable values: 1 to 100

Default: 4

If the specified value is outside the specifiable range, the default value is set.

logFileSizeMulti

Specifies the upper limit for the file size of a log file to be output by the jpcrpt command in megabytes.

Specifiable values: 1 to 16

Default: 4

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

When the outputMultiProcessForJpcrpt value is false, this setting is ineffective, and the logFileSize setting value of <logging> is applied.

outputMultiProcessForJpcrpt

Specifies the log output method for when the jpcrpt command is executed.

true: Outputs a single log file regardless of the process of the jpcrpt command. The logFileRetention setting is ineffective, and there is no limit on the log file retention period.

false: Outputs a single log file for each process of the jpcrpt command.

The default is true. Note that when the PFM - Web Console version is earlier than 10-00 or PFM - Web Console is upgraded from the previous version to 10-00, the default is false.

If the specified value is outside the specifiable range or specification is omitted, false is set.

(2) Setting PFM - Manager for the connection destination

Table E‒2: Setting items for PFM - Manager for the connection destination

Item

Description

host

Specifies the host name or the IP address of PFM - Manager to be connected.

For a host name:

The following characters can be used. Note that only an alphanumeric character can be specified as the first character.

Specify this item by using characters totalling 1 to 32 bytes.

Numeric characters 0 to 9

. (period)

- (hyphen)

Alphabetic characters A to Z and a to z

For an IP address:

0.0.0.0 to 255.255.255.255

If you specify an invalid character, the KAVJV5006-I message is output and startup of the PFM - Web Console service fails. If you specify a host name that does not exist, the KAVJS0029-E message is output and an error occurs at login to PFM - Web Console.

If specification is omitted, localhost is set.

Note that when you specify a host name for this item, even if the PFM - Manager to be connected uses an alias name added by the function for setting monitoring host names, specify the physical host name of the PFM - Manager host. The following shows an example:

Setting Examples:

PFM - Manager host name: hostA

The alias name of PFM - Manager added by the function for setting monitoring host names: hostB

Value to be set in this item: hostA

If a host name is specified in this item, the hosts file or DNS is used for name resolution. Therefore, confirm, beforehand, that the host name specified in this item can be resolved by using the hosts file or DNS.

port

Specifies the port number of the View Server service of PFM - Manager to be connected.

Specifiable values: 1024 to 65535

Default: 22286

(3) Settings for acquiring and displaying data

Table E‒3: Setting items for acquiring and displaying data

Item

Description

agentTreeAccessLimit

Specifies whether to limit the operation (creating and editing the Agents tree, and displaying it in the Products display format) of the Agents tree with the general user permission level.

on: Limited

off: Not limited (default)

If you specify on, the following limits are applied to the operation of the Agents tree with the general user permission level.

Products cannot be specified for Display Style in the navigation frame.

Edit Agents is not displayed in the method frame.

appendCommaDisplayedForNum (under <draw> tag)

Specifies whether to delimit the data label to be displayed for the graph scale every three digits with a comma.

true: Delimits the data label every three digits with a comma for display.

false: Does not delimit the data label with a comma for display.

The default is false. If the specified value is outside the specifiable range or specification is omitted, the default value is set.

area (under <graph-time-correction> tag)#1

Specifies the time correction method when a historical report (including combination reports) graph is displayed as an area graph.

You can specify NONE (disabled) or SECOND (enabled).

If you specify SECOND, the time is corrected in units of seconds.

The default value is NONE. If you specify any value other than those allowed or you do not specify a value, the default value is set.

autoLabelMaxFractionDigits (under <draw> tag)

Specifies the maximum number of digits that can be displayed as the decimal part of a data value to be displayed in the tool tips of the Autolabel function.

Specifiable values: 1 to 6

Default: 3

If the actual decimal part of the data value has more digits than the number of digits specified for this item, the data is displayed only for the specified number of digits from the first decimal place. If the specified number of digits is exceeded, the data is rounded off to the decimal place prior to the specified decimal place. For example, when the specified value is 2, and the data value of the specified plot in the tool tips is 1.23456, 1.23 is displayed in the tool tips.

If specification is omitted, the default value is set.

For details about the Autolabel function, see the part that describes how to display reports in the chapter that describes creation of reports for operation analysis in the Job Management Partner 1/Performance Management User's Guide.

autoLabelMaxIntegerDigits (under <draw> tag)

Specifies the maximum number of digits that can be displayed as the integer part of a data value to be displayed in the tool tips of the Autolabel function.

Specifiable values: 1 to 14

Default: 7

If the actual integer part of the data value has more digits than the number of digits specified for this item, the data is displayed only for the specified number of digits from the first digit. For example, when the specified value is 3, and the data value of the specified plot in the tool tips is 123456, 456 is displayed in the tool tips.

If specification is omitted, the default value is set.

For details about the Autolabel function, see the part that describes how to display reports in the chapter that describes creation of reports for operation analysis in the Job Management Partner 1/Performance Management User's Guide.

blockTransferMode

Specifies whether block transmission mode is set.

You can specify true (enabled) or false (disabled). The default value is true (enabled).

If you specify any other value or you do not specify a value, the default value is set.

The block transmission mode is enabled only for outputting reports in CSV format. The mode is disabled for output in HTML format.

bookmarkRepository#2

Specifies the absolute path to the repository#3 that stores the bookmark function definition information.

If the specified directory does not exist, the directory is created when the PFM - Web Console service starts.

Maximum length of path: 150 characters

You can specify single-byte alphanumeric characters or single-byte symbols.

Note that you cannot use the following characters.

In Windows:

$ % ^ ' ! = + { } @ [ ] ;

The default directory is as follows:

In Windows:

installation-folder\bookmarks\

In UNIX:

/opt/jp1pcwebcon/bookmarks/

If an invalid directory is specified, the following occurs: In Windows, the KAVJT0003-E message is displayed and a PFM - Web Console service startup error occurs, and in UNIX, the KAVJZ0999-E message is displayed when an attempt is made to access the specified directory from a Web browser and an application initialization error occurs.

cmdHtmlTableOutputMaxRowSize

Specifies the maximum number of lines of table data in an HTML-format report to be output by the jpcrpt command as an integer.

Specifiable values: 0 to 15000

Default: 0 (when PFM - Web Console 10-00 or later is newly installed, the default is 15000)

If the specified number of lines is exceeded, a message is output and table data is output up to the specified number of lines. Lines exceeding the specified number of lines are not output.

Note that if 0 is specified, there is no limit on the number of lines of table data. In this case, if you try to output a report containing a large amount of table data in HTML format by the jpcrpt command to display it in a Web browser, the Web browser might freeze up. For details, see the part that describes notes on displaying reports in the chapter that describes creation of reports for operation analysis in the Job Management Partner 1/Performance Management User's Guide.

If specification is omitted, 0 is set.

color1 to color16 (under <chart-symbolColors> tag)

Specifies a line color to be used in a graph.

You can select from 16 colors (color1 to color16). color1 is used for the first line of a graph, and color2, color3, color4, (omitted), and then color16 are used sequentially. For the 17th line, color1 is used again.

Specify a value in RGB format by delimiting each value of R, G, and B with a single-byte comma (,).

Specifiable values: 0 to 255

Default: As follows:

color1: 235,143,21 ()

color2: 204,0,0 ()

color3: 102,153,0 ()

color4: 0,102,255 ()

color5: 102,0,255 ()

color6: 255,51,153 ()

color7: 255,185,0 ()

color8: 255,17,17 ()

color9: 136,204,0 ()

color10: 71,145,255 ()

color11: 134,51,255 ()

color12: 255,149,246 ()

If even one of the specified R, G, and B values of the color1 to color12 items is outside the range of the specifiable range, the default value is used for the line color. If even one of the specified R, G, and B values of the color13 to color16 items is outside the range of the specifiable range, it is considered that the specification of the line color is omitted.

When the specification of the line color is omitted, the color with the applicable number is skipped. For example, if you omit specifying only color3, color1, color2, color4, (omitted) are used sequentially.

In addition, if even one of the color1 to color16 items is effective, only the effective item is used as the line color of a graph. For example, if there are three effective items (colors), only the three colors are used as the line colors.

columnBar

(under <graph-time-correction> tag)#1

Specifies the time correction method when a historical report (including combination reports) graph is displayed as a clustered vertical or horizontal bar graph.

You can specify NONE (disabled) or SECOND (enabled).

If you specify SECOND, the time is corrected in units of seconds.

The default value is NONE. If you specify any other value than those allowed, or you do not specify a value, the default value is set.

condExpValueUlongExtension

Sets the specifiable range for the definition of a conditional expression using the ulong data type. You can specify true or false.

true: 0 to 4294967295

false: 0 to 2147483647

The default is false.

If any other value than those allowed is specified, the default value is set.

numericSeparator

(under <number-format> tag)

Specifies a thousand separator symbol for numeric values to be output in CSV format by commands.

The specifiable value is either of the following values:

space: half-width space

quotation:'

period: .

comma: ,

The default is comma.

If any value other than the values allowed is specified, the default value is set.

Also, the same value as the one set for decimalPointSymbol cannot be specified. If the same value is specified, the default value is set.

decimalPointSymbol

(under <number-format> tag)

Specifies a decimal symbol for numeric values to be output in CSV format by GUI display or commands, and a decimal interpretative symbol for user entry values to be entered in GUI or a command parameter file.

The specifiable value is either of the following values:

period: .

comma: ,

The default is period.

If any value other than the values allowed is specified, the default value is set.

Also, the same value as the one set for numericSeparator cannot be specified. If the same value is specified, the default value is set.

displayAlarmTablesSeparately

Specifies whether to display the alarm tree separately.

The specifiable value is either of the following values:

true: Separate display is enabled.

false: Separate display is disabled.

The default is false. However, when PFM - Web Console 10-00 or later is newly installed, the default is true.

If the specified value is outside the specifiable range or specification is omitted, false is set.

For details about separate display, see the part that describes procedure for setting and operating alarms in the chapter that describes operation monitoring by alarms in the Job Management Partner 1/Performance Management User's Guide.

displayCountPerPage

Specifies the number of records to be displayed per page as an integer when a table is displayed in the View Report window.

Specifiable values: 1 to 2147483647

Default: 20

If the specified value is outside the specifiable range, the default value is set.

displayLegendCount

Specifies the maximum number of fields that can be displayed in the legend of a graph when the report series paging function is enabled. If the report series paging function is disabled, the value specified for this item is ignored.

Specifiable values: 1 to 40

Default: 14

If you specify any other value than those allowed, or you do not specify a value, the default value is set.

editReportByOrdinaryUser

Specifies whether to allow an ordinary user or business group ordinary user to operate (create, edit, delete, import, export) report definitions and bookmarks.

on: Editing allowed (default)

off: Editing not allowed

If you select off, ordinary users and business group ordinary users can no longer display editing methods or menus for reports and bookmarks.

enableAntiAliasForNonAreaGraph

(under <draw> tag)

Specifies whether to perform anti-aliasing for graph drawing.

This parameter is applied only in the following case:

A graph for which Area is not specified as the graph type

(For combination reports, when Area is not specified for any series group.)

If this parameter is not applied, true is set.

true: Anti-aliasing is performed.

false: Anti-aliasing is not performed.

The default is true. If specification is omitted, the default value is set.

When anti-aliasing is not performed, a jagged edge might be displayed at the boundary of a graph (the boundary of a graph is jagged). However, the display rate of a line graph is improved.

enableAutoLabelAtDefaultDisp

Specifies the initial value of the report graph option item Show Autolabel.

true: Specifies the initial value as checked.

false: Specifies the initial value as unchecked.

This setting is applied to reports other than combination reports.

The default is false. If the specified value is outside the specifiable range or specification is omitted, the default value is set.

enableDuplicateLogin

Controls concurrent logins to PFM - Web Console by the same user.

true: Permits concurrent logins

false: Does not permit concurrent logins

The default is true.

If false is set, concurrent logins by the same user are suppressed. If a user tries to log in under a user name that is already logged in, a confirmation message is displayed. If the user forcibly logs in, the session of the user who was already logged in is deleted and a new session is created.

excludeTerminalData (under <command> tag)

Specifies whether to output the report start time and end time data to a report when the <exclude-terminal-data> tag is omitted from the parameter file specified for entering the jpcrpt command.

STARTTIME: Start time data is not output to a report.

ENDTIME: End time data is not output to a report.

BOTHTIME: Start time and end time data are not output to a report.

NONE: Start time and end time data are output to a report.

The default is NONE.

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

excludeTerminalData (under <vsa> tag)

Specifies the initial value of Display the start time data and Display the end time data of the Settings for the report display period items.

STARTTIME: Specifies the initial value of Display the start time data as unchecked, and the initial value of Display the end time data as checked.

ENDTIME: Specifies the initial value of Display the start time data as checked, and the initial value of Display the end time data as unchecked.

BOTHTIME: Specifies the initial value of Display the start time data as unchecked, and the initial value of Display the end time data as unchecked.

NONE: Specifies the initial value of Display the start time data as checked, and the initial value of Display the end time data as checked.

The default is NONE.

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

exponentialDisplayMode

Specifies whether to display the scale on the vertical axis of a graph in exponential form.

You can specify true (enabled) or false (disabled).

If you specify true (enabled), the scale on the vertical axis of a graph is displayed in exponential form for values equal to or greater than 10⁷ or less than 0.001.

The default value is true (enabled). If you specify any other value than those allowed, or you do not specify a value, the default value is set.

firstDayOfWeek

Specifies the starting day of the week. The specifiable values are as follows:

AUTO

SUNDAY

MONDAY

TUESDAY

WEDNESDAY

THURSDAY

FRIDAY

SATURDAY

The default value is AUTO, which automatically selects the starting day of the week according to the locale. For example, Sunday is selected in Japan and America, and Monday is selected in France. If the specified value is outside the specifiable range, the default value is set.

foregroundCombinationGraph (under <draw> tag)

Specifies the graph type to be displayed in the foreground of a combination report.

Specifiable values: 3DBAR and LINE (Specify 3DBAR when you want to bring a clustered vertical or stacked vertical bar graph for which 3D display is enabled to the foreground; specify LINE when you want to bring a line graph to the foreground. The alphabetical characters are not case-sensitive.)

Default: 3DBAR

When no clustered vertical or stacked vertical bar graph for which 3D display is enabled is set or no line graph is set in a combination report, this setting is ignored.

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

graphMaxReportData

Specifies the maximum number of data items that can be displayed in a graph when the report cache filing function is enabled. If the report cache filing function is disabled, the value specified for this item is ignored.

Specifiable values: 1 to 2000000

Default: 2000000

If you specify any other value, the default value is set.

The number of data items that can be displayed in a graph can be calculated by the following expressions:

When a graph is a line, area, or stacked area

Number of data items displayable in a graph = Number of fields set in a report#4 x Number of obtained records

When a graph is not a line, area, and stacked area

Number of data items displayable in a graph = Number of fields set in a report#4 x Number of records for a single collection

informOfSharedSession

Specifies the settings of the login confirmation window when you disconnect the session of the user who was already logged in from a browser sharing the session to log out the user.

true: Displays the forced login confirmation window.

false: Does not display the forced login confirmation window.

If no value is set, false is set.

PFM - Web Console disconnects the session of the user who was already logged in to log out that user during the login processing from a browser sharing the session.

If true is set, the forced login confirmation window is displayed to notify a user that the session of the user who was already logged in is to be disconnected, and the notified user is allowed to select whether to forcibly log in.

legendSeriesOrderForHBar (under <draw> tag)

Changes the display order of the legend of a clustered horizontal bar graph (not a stacked horizontal bar graph).

Specifiable values: FORWARD and REVERSE (The alphabetical characters are not case-sensitive.)

FORWARD: The legend is displayed in order from the line displayed at the top of a graph.

REVERSE: The legend is displayed in order from the line displayed at the bottom of a graph (this is the same legend order as that in PFM - Web Console 09-00 or earlier).

Default: REVERSE

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

Note that setting this item changes only the line legend order. The line legend color is not changed.

line

(under <graph-time-correction> tag)#1

Specifies the time correction method when a historical report (including combination reports) graph is displayed as a line graph.

You can specify NONE (disabled) or SECOND (enabled).

If you specify SECOND, the time is corrected in units of seconds.

The default value is NONE. If you specify any other value than those allowed, or you do not specify a value, the default value is set.

lineSymbolSize (under <draw> tag)

Specifies the size of a plot to be used for displaying a line graph.

Specifiable values: LARGE, MEDIUM, SMALL, and AUTO (The alphabetical characters are not case-sensitive.)

Default: MEDIUM

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

If AUTO is specified, the size is automatically adjusted to a size appropriate for display of LARGE, MEDIUM, and SMALL depending on the number of time points in the report display range.

Note that this item is not applied to a thumbnail graph image in a tiling display. For such an image, a plot is always displayed with SMALL.

maxAutoLabelPoints (under <draw> tag)

If the number of plots in a graph exceeds a certain number, the Autolabel function is disabled. This item specifies the maximum number of plots that can be enabled for the Autolabel function for this item.

Specifiable values: 1 to 2000

Default: 1440

If specification is omitted, the default value is set.

For details about the Autolabel function, see the part that describes how to display reports in the chapter that describes creation of reports for operation analysis in the Job Management Partner 1/Performance Management User's Guide.

maxDisplayAgentsProducts (under <products> tag)

Specifies the display count for the higher-level agent operating statuses in the display summary. The specifiable range is 1 to 100.

The default is 5. If specification is omitted, the default value is set.

The value specified here is reflected when the display format for the Agents tree is products.

maxDisplayAgentsProducts (under <user-agents> tag)

Specifies the display count for the higher-level agent operating statuses (Product type view) in the display summary. The specifiable range is 1 to 100.

The default is 5. If specification is omitted, the default value is set.

The value specified here is reflected when the display format for the Agents tree is user-agents.

maxDisplayAgentsUser (under <user-agents> tag)

Specifies the display count for the higher-level agent operating statuses (User tree view) in the display summary. The specifiable range is 1 to 100.

The default is 5. If specification is omitted, the default value is set.

The value specified here is reflected when the display format for the Agents tree is user-agents.

maxDisplayAlarm (under <products> tag)

Specifies the display count for the higher-level agent alarm monitoring statuses in the display summary. The specifiable range is 1 to 100.

The default is 5. If specification is omitted, the default value is set.

The value specified here is reflected when the display format for the Agents tree is products.

maxDisplayAlarm (under <user-agents> tag)

Specifies the display count for the higher-level agent alarm monitoring statuses in the display summary. The specifiable range is 1 to 100.

The default is 5. If specification is omitted, the default value is set.

The value specified here is reflected when the display format for the Agents tree is user-agents.

maxDisplayServer (under <products> tag)

Specifies the display count for the higher-level server operational statuses in the display summary. The specifiable range is 1 to 100.

The default is 5. If specification is omitted, the default value is set.

The value specified here is reflected when the display format for the Agents tree is products.

maxDisplayServer (under <user-agents> tag)

Specifies the display count for the higher-level server operational statuses in the display summary. The specifiable range is 1 to 100.

The default is 5. If specification is omitted, the default value is set.

The value specified here is reflected when the display format for the Agents tree is user-agents.

maxDrilldownPoints

Specifies the maximum number of drilldown data items in a graph as an integer.

Specifiable values: 0 to 1500

Default: 0 (when PFM - Web Console 10-00 or later is newly installed, the default is 1500)

If the specified value is exceeded, displaying a drilldown report from a graph is disabled.

Note that if 0 is specified, there is no limit on the maximum number of drilldown data items in a graph. In this case, memory might run out and the PFM - Web Console service might stop, depending on the number of field points in the graph area. For details, see the part that describes notes on displaying reports in the chapter that describes creation of reports for operation analysis in the Job Management Partner 1/Performance Management User's Guide.

If specification is omitted, 0 is set.

maxEvents

Specifies the maximum number of events displayed in the display summary. The specifiable range is 1 to 999.

The default is 256.

maxFetchCount

(under <command> tag)

Specifies the maximum number of records that are to be acquired from View Server for a report output by the jpcrpt command as an integer.

Specifiable values: 1 to 2147483647

Default: maxFetchCount value under the <vsa> tag

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

Note:

Because the value of Maximum number of records specified when a report is registered as a bookmark is applied for combination reports or tiling displays, the maxFetchCount value is not applied in such situations.

maxFetchCount

(under <vsa> tag)

Specifies the maximum number of records that can be acquired from PFM - Manager as an integer.

Specifiable values: 1 to 2147483647

Default: 1440

If the specified value is outside the specifiable range, the default value is set.

Note:

Because the value of Maximum number of records specified when a report is registered as a bookmark is applied for combination reports or tiling displays, the maxFetchCount value is not applied in such situations.

maxMonitorEventNumForMultiTenant (under <multi-tenant> tag)

Specifies the maximum number of events that can be retained in the cache by PFM - Web Console when a business group is used.

Specifiable values: 1 to 10000

Default: 999

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

maxRealtimeCache

Specifies the maximum number of records per realtime report for which data is to be cached as an integer.

Specifiable values: 1 to 360

Default: 30

If the specified value is outside the specifiable range, the default value is set.

maxSeriesLabelLength

Specifies the maximum size of a string of characters in bytes that can be displayed in the legend label in a graph in a report. However, if the final character is the first byte of a multi-byte character, the final character is displayed properly. Specify the character string length as an integer within the range 1 to 1024 bytes. The default is 30. If you omit the specification, or you specify a value outside the range or an invalid value, the default value is set.

maxTileReports

Specifies the maximum number of reports that can be displayed in the Tiling Display. The specifiable range is 1 to 256.

The default is 50.

minimumNumberOfAgentsTitle

Specifies the minimum number of selected agents for displaying a title to be displayed in the method frame with the number of agents when showNumberOfAgentsTitle is true.

Specifiable values: 1 to 65535

Default: 4

If showNumberOfAgentsTitle is false, this setting is disabled. If the specified value is outside the specifiable range or specification is omitted, the default value is set.

noUseCircleColor (under <chart-symbolColors> tag)

Specifies a color number of color numbers from color1 to color16 that you do not want to use for pie graphs.

Specifiable values: 0 to 16

Default: 0 (There are no color numbers excluded for use for pie graphs.)

To specify multiple color numbers, delimit the specified color numbers with a single-byte comma (,).

In the following cases, it is assumed that 0 is specified. Therefore, all the colors specified for color1 to color16 are used for pie graphs.

Specification is omitted.

When multiple values are specified, but even one of the values is outside the specifiable range or invalid.

When multiple values are specified, but the values include 0.

In the following cases, the default colors of color1 to color12 are used for pie graphs.

All the color numbers are specified.

None of the color numbers from color1 to color16 is specified.

numericSeparator (under <number-format> tag)

Specifies a thousand separator symbol for numeric values to be output in CSV format by commands.

The specifiable value is either of the following values:

space:half-width space

quotation:'

period: .

comma: ,

The default is comma.

If any value other than the values allowed is specified, the default value is set.

Also, the same value as the one set for decimalPointSymbol cannot be specified. If the same value is specified, the default value is set.

pie

(under <graph-time-correction> tag)#1

Specifies the time correction method when a historical report graph is displayed as a pie graph.

You can specify NONE (disabled) or SECOND (enabled).

If you specify SECOND, the time is corrected in units of seconds.

The default value is NONE. If you specify any value other the values allowed, or you do not specify a value, the default value is set.

precision (under <draw> tag)

Specifies the maximum number of displayed digits of the decimal part when the data label to be displayed for the graph scale is a decimal value.

Specifiable values: 0 to 15

Default: 0 (when PFM - Web Console 10-00 or later is newly installed, the default is 3)

If you specify 0 for this item, the decimal part is not displayed.

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

Note that when the data label is an integer value, or the number of digits in the decimal part is smaller than the number of digits specified for this item, only the actual data label value is displayed and 0 is not applied to the rest of the digits.

printCacheSize

Specifies the maximum number of data items in the Print window to be cached as an integer.

Specifiable values: 5 to 20

Default: 20 (when PFM - Web Console 10-00 or later is newly installed, the default is 10)

If you specify any other value than those allowed, or you do not specify a value, 20 is set.

printTableMaxRowSize

Specifies the maximum number of lines of table data to be displayed in the Print window as an integer.

Specifiable values: 0 to 15000

Default: 0 (when PFM - Web Console 10-00 or later is newly installed, the default is 15000)

If the specified number of lines is exceeded, a message is output and table data is output up to the specified number of lines. Lines exceeding the specified number of lines are not output.

Note that if 0 is specified, there is no limit on the number of lines of table data. In this case, if you try to display a report containing a large amount of table data in the Print window, the Web browser might freeze up. For details, see the part that describes notes on displaying reports in the chapter that describes creation of reports for operation analysis in the Job Management Partner 1/Performance Management User's Guide.

If specification is omitted, 0 is set.

priority

Specifies how to propagate the health check icon in the Agents tree. You can select either of the following options as the propagation method:

Setting value

Order of priority for propagation

Note

HOST

H7 > H6 > H5 > H4 > H3 > H2 > H1

When monitoring the host operating status

AGENT

H6 > H5 > H4 > H7 > H3 > H2 > H1

When monitoring the agent operating status

Legend:

H1: Not supported (not supported)

H2: Running (running)

H3: Suspended (monitoring suspended)

H4: Incomplete (Incomplete)

H5: Stopped (stopped service)

H6: Unconfirmed (unconfirmed)

H7: Host Not Available (Host Not Available)

The default value is HOST. If you omit the specification, or if you specify an invalid value, the default value is set.

processMonitoringTemplatesRepository#2

Specifies the absolute path to the repository#3 that stores the template information of the application definition for process monitoring.

If the specified directory does not exist, the directory is created when the PFM - Web Console service starts.

Maximum length of path: 100 characters

You can specify single-byte alphanumeric characters or single-byte symbols.

Note that you cannot use the following characters.

In Windows:

$ % ^ ' ! = + { } @ [ ] ;

The default directory is as follows:

In Windows:

installation-folder\processMonitoringTemplates\

In UNIX:

/opt/jp1pcwebcon/processMonitoringTemplates/

If an invalid directory is specified, a PFM - Web Console service startup error occurs.

quickGuideHideReportIcon

Specifies whether to hide the icons for reports that cannot be displayed in the list of fields of the quick guide.

true: Hides the icons for reports that cannot be displayed.

false: Displays the icons for reports that cannot be displayed.

The default value is true. However, if a new installation of PFM - Web Console version 10-10-20 was performed, the default value is false.

If you specify any other value than those allowed or if you do not specify a value, true is set.

realtimeCacheInterval

Specifies the request interval limit time (in milliseconds) when realtime reports are refreshed automatically. If the automatic refreshing request interval exceeds this limit value, the server and agent assume that the report ended without a notification and terminate processing. Whether or not the request interval has exceeded the limit time is checked every 10 seconds.

For example, if the limit time is set to 61000 milliseconds, the actual limit time is from 61000 to 70000 milliseconds.

Specifiable values: 60000 to 3600000

Default: 600000

If the specified value is outside the specifiable range or specification is omitted, the default value is set.

reportCacheFileDir#2

Specifies the absolute path to the directory that stores report cache files.

If the specified directory does not exist, the directory is created when the PFM - Web Console service starts.

Maximum length of path: 150 characters

You can specify single-byte alphanumeric characters or single-byte symbols.

Note that you cannot use the following characters.

In Windows:

$ % ^ ' ! = + { } @ [ ] ;

The default directory is as follows:

In Windows:

installation-folder\reportcache\

In UNIX:

/opt/jp1pcwebcon/reportcache/

Note that if one or more of the following errors occur, the directory is not created.

The specified value is not a directory.

The specified value exceeds the maximum allowed length of a path.

An attempt to create the directory that stores report cache files has failed.

Note:

Specify a directory on the local disk as the directory that stores report cache files. If you specify a directory on the network, the operation of the GUI and the jpcrpt command takes more time than when a directory on the local disk is specified.

reportFirstDataTimeout

Specifies the timeout time in seconds for when a report is initially displayed.

This setting is applied only to the first display, and does not affect the refresh interval of real-time reports.

Specifiable values: 10 to 3600

Default: 600

If you specify any other value than those allowed, or you do not specify a value, the default value is set.

searchLimit

Specifies the limit on the number of searches for fields that match the search keyword. The specifiable range is 1 to 100.

The default is 50.

selectFormat

Specifies the date format when the locale is not en_US, en, or ja. For details, see the chapter that describes installation and setup in Job Management Partner 1/Performance Management Planning and Configuration Guide.

You can specify the following values:

pattern-ddMMyyyy

pattern-MMddyyyy

pattern-yyyyMMdd

The default is pattern-ddMMyyyy. If you specify any other value than those allowed, or you do not specify a value, the default value is set.

showNumberOfAgentsTitle

Specifies whether to use the agent name or the number of agents as the title to be displayed in the method frame depending on the number of agents selected in the navigation frame in the Agents tree.

true: Displays the number of agents.

false: Displays the agent name.

The default is true. Note that when the PFM - Web Console version is earlier than 10-00 or PFM - Web Console is upgraded from the previous version to 10-00, the default is false.

When the number of selected agents is fewer than the value specified for minimumNumberOfAgentsTitle, false is set. In addition, if the specified value is outside the specifiable range or specification is omitted, false is set.

stackedArea

(under <graph-time-correction> tag)#1

Specifies the time correction method when a historical report (including combination reports) graph is displayed as a stacked area graph.

You can specify NONE (disabled) or SECOND (enabled).

If you specify SECOND, the time is corrected in units of seconds.

The default value is NONE. If you specify any other value than those allowed, or you do not specify a value, the default value is set.

stackedColumnBar

(under <graph-time-correction> tag)#1

Specifies the time correction method when a historical report (including combination reports) graph is displayed as a stacked vertical or horizontal bar graph.

You can specify NONE (disabled) or SECOND (enabled).

If you specify SECOND, the time is corrected in units of seconds.

The default value is NONE. If you specify any other value than those allowed, or you do not specify a value, the default value is set.

updateInterval

Specifies the refresh interval (in seconds) for automatic refreshing.

Specifiable values: 10 to 3600

Default: 60

If the specified value is outside the specifiable range, the default value is set.

useReportCacheFile

Specifies whether to enable the report cache filing function.

true: The report cache filing function is used.

false: The report cache filing function is not used.

The report cache filing function can be used only when the block transmission mode is enabled. When the block transmission mode is disabled, even though true is specified, false is assumed.

The default is false.

If you specify any other value than those allowed, or you do not specify a value, the default value is set.

usingSeriesPagingOnTheGraph

Specifies whether to enable the report series paging function.

true: The report series paging function is used.

false: The report series paging function is not used.

The default is false. However, when PFM - Web Console 10-00 or later is newly installed, the default is true.

If you specify any other value than those allowed, or you do not specify a value, false is set.

#1

In the default initialization file (config.xml), the XML tags are commented out. So, if you want to set these items, uncomment the desired tag or tags and specify a value.

#2

The values of bookmarkRepository, ownPort, ownCmdPort, ownHost, reportCacheFileDir, and processMonitoringTemplatesRepository are not set in the default initialization file (config.xml). In addition, the XML tags themselves are also commented out. So, if you want to set these items, uncomment the desired tag or tags and specify a value.

#3

For details about the repository, see E.2 Repository for storing bookmark definition information.

#4

This indicates the number of fields specified for the report definition rather than the number of fields specified for the graph.

(4) Setting up communication with the View Server service

Table E‒4: Setting items for when PFM - Web Console communicates with View Server

Item

Description

ownCmdPort#1

Specifies the port number to be used by PFM - Web Console (command) to communicate with the View Server service.

Specifiable values: 1024 to 65535

Default: Any available port

If specification is omitted, an available port number is set.

You must specify this item for a firewall environment. For details, see C.2 Firewall penetration directions.

ownHost#1#2

Specifies the host name or IP address to be used as the callback target from the View Server service when PFM - Web Console communicates with the View Server service. This must be the name of a host running PFM - Web Console.

For a host name:

The following characters can be used. Note that only an alphanumeric character can be specified as the first character. Specify this item by using characters totalling from1 to 255 bytes.

Numeric characters 0 to 9

. (period)

- (hyphen)

Alphabetic characters A to Z and a to z

For an IP address:

0.0.0.0 to 255.255.255.255

If the specified value is outside the specifiable range or invalid, the IP address of the PFM - Web Console host is set.

ownPort#1

Specifies the port number to be used by PFM - Web Console (Web server) to communicate with the View Server service.

Specifiable values: 1024 to 65535

If specification is omitted, an available port number is set.

You must specify this item for a firewall environment. For details, see C.2 Firewall penetration directions.

#1

The values of bookmarkRepository, ownPort, ownCmdPort, ownHost, reportCacheFileDir, and processMonitoringTemplatesRepository are not set in the default initialization file (config.xml). In addition, the XML tags themselves are also commented out. So, if you want to set these items, uncomment the desired tag or tags, and specify a value.

#2

TCP/IP is used for communication between PFM - Manager and PFM - Web Console. This is also applied when PFM - Manager and PFM - Web Console exist together on the same host, not only when each of them exists on a separate host. Therefore, when you operate Performance Management, the host name or IP address that allows constant communication must be set on both the PFM - Manager host and the PFM - Web Console host. If the setting is not specified, the IP address that is first resolved from the PFM - Manager host name or PFM - Web Console host name is used.

For example, in the following configurations or operations, the host name or IP address that allows constant communication must be set on both the PFM - Manager host and the PFM - Web Console host.

When IP address translation (NAT) is used between the PFM - Manager host and the PFM - Web Console host

When the PFM - Manager host is connected to both the business LAN and the monitoring LAN, and Performance Management performs communication between hosts via the monitoring LAN

When the LAN cable is temporarily disconnected from the NIC for host maintenance operation (Because at this time, the IP address assigned to the NIC might be disabled)

(5) Setting automatic logout

Table E‒5: Setting items for automatic logout

Item

Description

sessionTimeout#

Specifies the expiration time in seconds to perform automatic logoff from PFM - Web Console if the user attempts no operations for a preset length of time or automatic update is not performed for a preset length of time.

Specifiable values: 0 to 86400

Default: 4000

If you specify 0, no timeout occurs. If the specified value is outside the specifiable range, the default value is set.

#

If you close the Web browser without logging off, session information remains in the PFM - Web Console memory as invalid and will be deleted automatically when a session timeout is detected. We recommend that you not set 0 as the value for sessionTimeout.

(6) Other settings

Table E‒6: Other setting items

Item

Description

alarmCompatibleMode(under <vsa> tag)

Specifies whether to enable measures to address the problem that occurs when an alarm is illegally deleted when the alarm is updated.

The specifiable value is either of the following values:

true: The measures are enabled.

false: The measures are disabled.

The default is true.

If you specify any other value than those allowed, or you do not specify a value, the default value is set.

When true is specified, the problem that may occur when an alarm is illegally deleted when the alarm is updated is resolved. However, the Alarm Cleared event that used to occur for the following alarms (when the alarm is updated), no longer occurs.

All the alarms (except for the alarm to be updated) of agents related to the alarm to be updated.

Alarms in the Warning or Abnormal state

cmdRptBookmarkNameDecodeOnce(under <command><export> tag)

Specifies how to read the attribute value of the bookmark name specified in the input parameter file when a registered report or a report with combination bookmarks is output by the jpcrpt command.

true: Replace \\ by \ and replace \/ by / to read the value.

false: Replace \\\\ by \ and replace \\\/ by / to read the value. \\ and \/ are read as delimiters.

The default is true. If you specify any other value than those allowed, or you do not specify a value, the default value is set.

selectAHModeForJP1Event

Specifies how to decide the Action Handler service to be selected by default in the window displayed by selecting New Alarm and Action Definition or Edit and Action Definition when JP1 event issuance is enabled as an action in the alarm definition. The following describes the specifiable values and their explanations:

compatible

When the PFM - Manager host name specified for host in the initialization file (config.xml) matches the physical host name of the PFM - Manager host, the Action Handler service of PFM - Manager is selected. If they do not match, LOCAL is selected. In the following cases, they do not match:

- When the IP address (other than 127.0.0.1) is specified

- When an alias name is assigned to PFM - Manager by the function responsible for setting monitoring host names

- When the case is different from that of the host name specified for host in the initialization file (config.xml)

local

LOCAL is always selected.

manager

The Action Handler service of PFM - Manager is always selected.

maintain

When you edit an already existing alarm, the setting status of the Action Handler service is inherited. When you create an alarm, LOCAL is selected.

multipleManager

When one host name is specified for PFM - Manager for the connection destination, the Action Handler service of PFM - Manager is selected. When two host names are specified for PFM - Manager for the connection destination, Manager is selected.

The default is compatible. However, when PFM - Web Console 10-00 or later is newly installed, the default is manager.

If you specify any other value than those allowed, or you do not specify a value, compatible is set.

validate

Enables or disables the check rule specified in the property definition file.

on: Enable (default)

off: Disable

E.2 Repository for storing bookmark definition information

Information about the organization of bookmarks and the bookmark folder and the application definition template information are stored as flat files in the OS's file system. This is called the repository. During installation, the default repository is created at the following location:

Information about the organization of bookmarks and the bookmark folder

installation-folder\bookmarks\

Application definition template information

installation-folder\processMonitoringTemplates\

(1) Changing the bookmark repository storage directory

You can change the directory for storing the bookmark repository (bookmark definition information) using bookmarkRepository in the initialization file (config.xml). To apply the new value, you must restart the PFM - Web Console service.

If the directory specified in the initialization file (config.xml) does not exist when the PFM - Web Console service starts, that directory is created automatically.

The following shows an example of a bookmarkRepository specification in config.xml.

Example:

This example specifies c:\user1\bookmarks as the bookmark repository storage directory:

<bookmark>
    <!-- The directory where bookmark repository is stored.
        Default           : <install directory>\bookmarks
    -->
    <param name="bookmarkRepository" value="c:\user1\bookmarks"/>
</bookmark>

(2) Changing the storage directory for the repository of the application definition template information

You can change the directory for storing the repository of the application definition template information using processMonitoringTemplatesRepository in the initialization file (config.xml). To apply the new value, you must restart the PFM - Web Console service.

If the directory specified in the initialization file (config.xml) does not exist when the PFM - Web Console service starts, that directory is created automatically.

The following shows an example of a processMonitoringTemplatesRepository specification in config.xml.

Example:

This example specifies c:\user1\processMonitoringTemplates as the storage directory for the repository of the application definition template information:

<process-monitoring>
    <!-- The directory where templates of process monitoring are stored.
        Default           : <install directory>\processMonitoringTemplates
    -->
    <param name="processMonitoringTemplatesRepository" value="c:\user1\processMonitoringTemplates"/>
</process-monitoring>

E.3 Example of an initialization file (config.xml)

The following shows an example of an initialization file (config.xml):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE application SYSTEM "config.dtd">
<!--
 * Title: PFM - Web Console Configuration File
 * Copyright: Copyright (c) 2009, 2011, Hitachi,Ltd.
 * (C)opyright 2000-2009, by Object Refinery Limited and Contributors.
 * Licensed Material of Hitachi, Ltd. Reproduction, use, modification or disclosure
   otherwise than permitted in the License Agreement is strictly prohibited.
-->

<application name="PFM-WebConsole">

    <logging>

        <!-- Path of log files directory -->
        <param name="logDir" value="/opt/jp1pcwebcon/log"/>

        <!-- Maximum number of log files
                Specifiable values: 1 to 16
                Default           : 10
        -->
        <param name="logFileNumber" value="10"/>

        <!-- Size of a log file (unit: MB=1024x1024byte)
                Specifiable values: 1 to 100
                Default           : 10
        -->
        <param name="logFileSize" value="1"/>

        <!-- Logging level of a log file
                Specifiable values: FATAL/WARN/DEBUG/TRACE
                Default           : DEBUG
        -->
        <param name="logLevel" value="DEBUG"/>

        <!-- Retention period of a log file
                Specifiable values: 1 to 30
                Default           : 30
        -->
        <param name="logFileRetention" value="30"/>

    </logging>

    <export>
        <!-- lineSeparator
                Specifiable values: CRLF,LF
                Default           : CRLF
        -->
        <param name="lineSeparator" value="CRLF"/>

        <!-- characterCode
                Specifiable values: US-ASCII,windows-1252,ISO-8859-1,
                UTF-8,UTF-16,UTF-16BE,UTF-16LE,
                Shift_JIS,EUC-JP,EUC-JP-LINUX,MS932
        -->
        <param name="characterCode" value=""/>

        <!-- Export filename -->
        <param name="csvFileName" value="Export.csv"/>
    </export>

    <vsa>
        <vserver-connection>
            <!-- The host computer name to which PFM View Server operates. -->
            <param name="host" value="hostB"/>
            <!-- The port number which PFM View Server uses.
                Specifiable values: 1 to 65535
                Default           : 22286
            -->
            <param name="port" value="22286"/>
            <param name="ownPort" value="22222"/>
            <param name="ownCmdPort" value="22223"/>
            <param name="ownHost" value="host1"/>

        </vserver-connection>

        <!-- The flag to enable duplicate login.
                Specifiable values: true or false
                Default           : true
        -->
        <param name=" enableDuplicateLogin " value="true"/>

        <!-- The maximum limits of the records.
                Specifiable values: 1 to 2,147,483,647
                Default           : 1,440
        -->
        <param name="maxFetchCount" value="1440"/>

        <!-- The maximum caches of the print windows.
                Specifiable values: 5 to 20
                Default           : 10
        -->
        <param name="printCacheSize" value="10"/>

        <!-- The maximum print window output table rows.
                Specifiable values: 0 to 15,000
                Default           : 0
        -->
        <param name="printTableMaxRowSize" value="15000"/>

        <!-- The display count per a page.
                Specifiable values: 1 to 2,147,483,647
                Default           : 20
        -->
        <param name="displayCountPerPage" value="20"/>

        <!-- Exclude the start or end time of the report.
                Specifiable values: NONE,STARTTIME,ENDTIME,BOTHTIME
                Default           : NONE
        -->
        <param name="excludeTerminalData" value="NONE"/>

        <!-- Maximum data receiving count per report.
                Specifiable values: 1 to 360
                Default           : 30
        -->
        <param name="maxRealtimeCache" value="30"/>

        <!-- The auto refresh interval.
                Specifiable values: 10 to 3600
                Default           : 60
        -->
        <param name="updateInterval" value="60"/>

        <!-- The login session timeout which PFM Web Console service uses (unit: s)
               Specifiable values: 0 to 86400
               Default           :4000
        -->
        <param name="sessionTimeout" value="4000"/>

        <!-- The range extension for condition expression definitions using ulong fields.
                Specifiable values: true,false
                Default           : false
        -->
        <param name="condExpValueUlongExtension" value="false"/>

        <!-- Maximum series label length.
                Specifiable values: 1 to 1024
                Default           : 30
        -->
        <param name="maxSeriesLabelLength" value="30"/>

        <!-- The Switch of the divided data receivable.
            Specifiable values: true or false
            Default           : true
        -->
        <param name="blockTransferMode" value="true"/>

        <!-- First day of the week
             Specifiable values : AUTO,SUNDAY,MONDAY,TUESDAY,WEDNESDAY,THURSDAY,FRIDAY,SATURDAY
             Default            : AUTO
        -->
        <param name="firstDayOfWeek" value="AUTO"/>

        <!--Exponential display for scales of graph.
            Specifiable values: true,false
            Default           : true
        -->
        <param name="exponentialDisplayMode" value="true"/>

        <!-- The maximum number of tiled reports.
            Specifiable values: 1 to 256
            Default           : 50
        -->
        <param name="maxTileReports" value="50"/>

        <!-- Select the command Action Handler mode for JP1Event.
            Specifiable values: compatible,local,manager,maintain,multipleManager
            Default           : compatible
        -->
        <param name="selectAHModeForJP1Event" value="manager"/>

        <!-- limit the operation of the agent tree in the agent hierarchy in the general user authority.
                Specifiable values: on or off
                Default           : off
        -->
        <param name="agentTreeAccessLimit" value="off"/>

        <!-- Use new mode to update alarm.
                Specifiable values: true,false
                Default           : true
        -->
        <param name="alarmCompatibleMode" value="true"/>

        <!-- display the alarm tree separated between monitoring templates and alarm tables made by user.
                Specifiable values: true or false
                Default           : false
        -->
        <param name="displayAlarmTablesSeparately" value="true"/>

        <report-cachefile-mode>
        <!-- The Report data outputs reportCache files.
              Specifiable values: true or false
              Default           : false
          -->
          <param name="useReportCacheFile" value="false"/>

          <!-- The directory where reportCache files is stored.
                  Default           : <install directory>\reportcache
           -->
          <!--
          <param name="reportCacheFileDir" value=""/>
          -->

          <!--graph Report Max ReportDataSize.
                 Specifiable values: 1 to2,000,000
           -->
          <param name="graphMaxReportData" value="2000000"/>
        </report-cachefile-mode>

        <format>
        <!-- Format set is specified.
                Specifiable values : pattern-ddMMyyyy,pattern-MMddyyyy,pattern-yyyyMMdd
            -->
            <param name="selectFormat" value=""/>
        </format>

        <bookmark>
            <!-- The directory where bookmark repository is stored.
                Default           : <install directory>\bookmarks
            -->
            <!--
            <param name="bookmarkRepository" value=""/>
            -->
        </bookmark>

        <health-check>
            <!-- Priority of Health check.
                Specifiable values: HOST or AGENT
                Default             HOST
            -->
            <param name="priority" value="HOST"/>
        </health-check>

        <properties-define>
            <!-- validate of properties.
                Specifiable values: on or off
                Default           : on
            -->
            <param name="validate" value="on"/>
        </properties-define>

        <report-define>
           <!-- possible edit report by ordinary user.
               Specifiable values: on or off
               Default           : on
           -->
           <param name="editReportByOrdinaryUser" value="on"/>
        </report-define>

        <graph-time-correction>
            <!--time correction of column or bar graph
                Specifiable values: NONE,SECOND
                Default           : NONE
            -->
            <!--
            <param name="columnBar" value="NONE"/>
            -->
            <!-- time correction of stacked column or stacked bar graph
                Specifiable values: NONE,SECOND
                Default           : NONE
            -->
            <!--
            <param name="stackedColumnBar" value="NONE"/>
            -->
            <!-- time correction of pie graph
                Specifiable values: NONE,SECOND
                Default           : NONE
            -->
            <!--
            <param name="pie" value="NONE"/>
             -->
            <!-- time correction of line graph
                Specifiable values: NONE,SECOND
                Default           : NONE
            -->
            <!--
            <param name="line" value="NONE"/>
            -->
            <!-- time correction of area graph
                Specifiable values: NONE,SECOND
                Default           : NONE
            -->
            <!--
            <param name="area" value="NONE"/>
            -->
            <!-- time correction of stacked area graph
                Specifiable values: NONE,SECOND
                Default           : NONE
            -->
            <param name="stackedArea" value="NONE"/>
        </graph-time-correction>
         <system-summary>
            <user-agents>
            <!-- the displaying rank value of server table on displaying user agents in system summary
                 Specifiable values: 1 to 100
                 Default           : 5
              -->
            <param name="maxDisplayServer"         value="5"/>

            <!-- the displaying rank value of agent table for user tree on displaying user agents in system summary
                 Specifiable values: 1 to 100
                 Default           : 5
              -->
            <param name="maxDisplayAgentsUser"     value="5"/>

            <!-- the displaying rank value of agent table for product kinds on displaying user agents in system summary
                 Specifiable values: 1 to 100
                 Default           : 5
             -->
            <param name="maxDisplayAgentsProducts" value="5"/>

            <!-- the displaying rank value of alarm table on displaying user agents in system summary
                 Specifiable values: 1 to 100
                 Default           : 5
             -->
            <param name="maxDisplayAlarm"          value="5"/>
         </user-agents>

         <products>
            <!-- the displaying rank value of server table on displaying product kinds in system summary
                 Specifiable values: 1 to 100
                 Default           : 5
             -->
            <param name="maxDisplayServer"         value="5"/>

            <!-- the displaying rank value of agent table on displaying product kinds in system summary
                 Specifiable values: 1 to 100
                 Default           : 5
             -->
             <param name="maxDisplayAgentsProducts" value="5"/>

             <!-- the displaying rank value of alarm table on displaying product kinds in system summary
                 Specifiable values: 1 to 100
                 Default           : 5
              -->
             <param name="maxDisplayAlarm"          value="5"/>
          </products>

          <event>
             <!-- the number of unsolved events displaying in system summary
                 Specifiable values: 1 to 999
                 Default           : 256
              -->
             <param name="maxEvents" value="256"/>
          </event>
      </system-summary>

      <multi-tenant>
         <!-- the number of monitor events for multi tenants
                  Specifiable values: 1 to 10,000
                  Default           : 999
         -->
         <param name="maxMonitorEventNumForMultiTenant" value="999"/>
      </multi-tenant>

      <field-search>
          <!-- the maximum number of field search result
                 Specifiable values: 1 to 100
                 Default           : 50
           -->
          <param name="searchLimit" value="50"/>
      </field-search>

      <graph-collection-points>
          <!-- Using series paging function on the graph.
               Specifiable values:true,false
               Default           : false                    -->
          <param name="usingSeriesPagingOnTheGraph" value="true"/>
          <!--Display legend count
              Specifiable values: 1 to 40
              Default           :14                         -->
          <param name="displayLegendCount" value="14"/>
      </graph-collection-points>

      <process-monitoring>
          <!-- The directory where templates of process monitoring are stored.
              Default           : <install directory>\processMonitoringTemplates
          -->
          <!--
          <param name="processMonitoringTemplatesRepository" value=""/>
          -->
      </process-monitoring>

   </vsa>

    <draw>
      <!-- Maximum  filed drilldown data for graph.
           Specifiable values: 0 to 1,500 (points)
           Default            :0
      -->
      <param name="maxDrilldownPoints" value="1500"/>

      <chart-symbolColors>
           <!--series color for graph.
            Possible to set, color1 to color16.
            Set RGB color,  R, G and B can be set delimits by comma.
            Specifiable values: 0 to 255
           -->

           <!-- dark orange -->
           <param name="color1" value="235,143,21"/>

           <!-- dark red -->
           <param name="color2" value="204,0,0"/>

           <!-- dark green -->
           <param name="color3" value="102,153,0"/>

           <!-- dark blue -->
           <param name="color4" value="0,102,255"/>

           <!-- dark violet -->
           <param name="color5" value="102,0,255"/>

           <!-- dark pink -->
           <param name="color6" value="255,51,153"/>

           <!-- light orange -->
           <param name="color7" value="255,185,0"/>

           <!-- light red -->
           <param name="color8" value="255,17,17"/>

           <!-- light green -->
           <param name="color9" value="136,204,0"/>

           <!-- light blue -->
           <param name="color10" value="71,145,255"/>

           <!-- light violet-->
           <param name="color11" value="134,51,255"/>

           <!-- light pink -->
           <param name="color12" value="255,149,246"/>

           <!-- Not use Color Number at Graph type Circle.
            Possible multiple number, set delimits by comma.
            Specifiable values: 0 to 16
            Default           : 0
           -->
           <!--
           <param name="noUseCircleColor" value=""/>
           -->

           <!--
            sample setting pattern,
            colors are used before Web Console 0910.
            color1            : red
            color2            : orange
            color3            : blue
            color4            : light gray
            color5            : magenta
            color6            : yellow
            color7            : gray
            color8            : lime
            color9            : dark gray
            color10           : cyan
            color11           : black
            color12           : pink
            not use Color Number at Graph type Circle.
                  : color1
           -->
           <!--
           <param name="color1" value="255,0,0"/>

           <param name="color2" value="255,200,0"/>

           <param name="color3" value="0,0,255"/>

           <param name="color4" value="192,192,192"/>

           <param name="color5" value="255,0,255"/>

           <param name="color6" value="255,255,0"/>

           <param name="color7" value="128,128,128"/>

           <param name="color8" value="0,255,0"/>

           <param name="color9" value="64,64,64"/>

           <param name="color10" value="0,255,255"/>

           <param name="color11" value="0,0,0"/>

           <param name="color12" value="255,175,175"/>

           <param name="noUseCircleColor" value="1"/>
           -->

      </chart-symbolColors>

      <!-- Symbol Size of line graph.
            Specifiable values: LARGE, MEDIUM, SMALL, AUTO
            Default            :MEDIUM
       -->
           <param name="lineSymbolSize" value="MEDIUM"/>

      <!-- legend Series Order or Horizontal Bar.
            Specifiable values: FORWARD, REVERSE
            Default            :REVERSE
       -->
           <param name="legendSeriesOrderForHBar" value="REVERSE"/>

       <!-- Using enable auto label in default graph option settings.
            Specifiable values: true or false
            Default            :false
       -->
           <param name="enableAutoLabelAtDefaultDisp" value="false"/>

       <!-- Maximum  Integer Digits for auto label.
            Specifiable values: 1 to 14
            Default            :7
       -->
           <param name="autoLabelMaxIntegerDigits" value="7"/>

       <!-- Maximum  Fraction  Digits for auto label.
            Specifiable values: 1 to 6
            Default            :3
       -->
           <param name="autoLabelMaxFractionDigits" value="3"/>

      <!-- Maximum plot data for auto label.
            Specifiable values: 1 to 2000
            Default            :1440
       -->
           <param name="maxAutoLabelPoints" value="1440"/>

      <!-- Displayed on the foreground for combination Graph.
            Specifiable values:  3DBAR, LINE
            Default            :3DBAR
       -->
           <param name="foregroundCombinationGraph" value="3DBAR"/>

     <!-- Displayed maximum fraction digits for data label.
            Specifiable values:  0 to 15
            Default            :0
       -->
           <param name="precision" value="3"/>

     <!--displayed append comma in Number for data label.
            Specifiable values:  true or false
            Default            :false
       -->
           <param name="appendCommaDisplayedForNum" value="false"/>

   </draw>

   <command>
       <export>
         <!-- The maximum limits of the records.
               Specifiable values: 1 to 2,147,483,647
               Default           : The value of maxFetchCount of the <vsa> tag is applied.
         -->
         <param name="maxFetchCount" value="1440"/>
         <!-- The maximum  html output table rows.
               Specifiable values: 0 to 15,000
               Default           : 0
         -->
         <param name="cmdHtmlTableOutputMaxRowSize" value="15000"/>

         <!-- The bookmark-name attribute for jpcrpt command is decoded once.
               Specifiable values: true,false
               Default           : true
         -->
         <param name="cmdRptBookmarkNameDecodeOnce" value="true"/>

         <!-- Exclude the start or end time of the report.
                 Specifiable values: NONE,STARTTIME,ENDTIME,BOTHTIME
                 Default           : NONE
         -->
         <param name="excludeTerminalData" value="NONE"/>

       </export>
   </command>
</application>

F. Startup Information File (jpccomm.ini)

The startup information file is an information file for setting up the operation of Performance Management.

The storage directory of the startup information file (jpccomm.ini) is shown below:

In Windows:

For physical hosts:

installation-folder\

For logical hosts:

environment-directory\jp1pc\

In UNIX:

For physical hosts:

/opt/jp1pc/

For logical hosts:

environment-directory\jp1pc\

When you want to restore the jpccomm.ini file to the data and settings it contained before it was edited, delete the edited jpccomm.ini file, copy the model file (jpccomm.ini.model) shown below, and then rename the model file jpccomm.ini.

In Windows:

installation-folder\jpccomm.ini.model

In UNIX:

/opt/jp1pc/jpccomm.ini.model

The following are notes on editing the jpccomm.ini file:

Notes:

For details about the items in the jpccomm.ini file and about whether these items can be edited, see the part that provides an explanation for each label in F.1 Settings items in the startup information file (jpccomm.ini).

When you rename the jpccomm.ini.model file to restore the jpccomm.ini file to the data and settings it contained before it was edited, the status management function is disabled and the Status Server service cannot be started. To use the status management function, re-enable the function by using the jpcconf stat enable command.

The jpccomm.ini file also contains definition information other than the following setting items. Do not change values other than the items that you need to change to meet your needs. If you change any other values, Performance Management might not operate normally.

F.1 Settings items in the startup information file (jpccomm.ini)

The following table describes settings items in the startup information file (jpccomm.ini). Disregard items that are not described in this table.

Set specifiable values following = after the label name. A blank character must not be specified at the beginning of a line and before and after =.

Table F‒1: Settings items in the startup information file (jpccomm.ini)

Section name

Label name

Description

Common Section

Common Msglog Size

Specifies the size of the file that stores the common message log in kilobytes.

Specifiable values: 4 to 32768

Default: 8192

(For a new installation, the default is 8192; for an upgrade installation, the default is the value specified before the upgrade.)

If the specified value is not a numeric value or is outside the specifiable range, the default value is set.

For details, see the part that describes how to set the file size of the common message log in the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Multiple Alarm Table Bind

Specifies whether to enable the function for binding an alarm to multiple alarm tables.

The specifiable values are 0 (disables) or 1 (enables).

The default value is 0.

For details, see the part that describes how to set the function for binding an alarm to multiple alarm tables in the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Display Product Name

Displays the settings information about the function for displaying the product name.

Do not edit the value of this label. To verify or change the value of this setting, use the jpcconf prodname command. For details, see 2. Commands.

Alarm Message Mode

Specifies whether to enable the function for measurement value output at alarm recovery.

The specifiable values are 0 (disables) or 1 (enables).

The default value is 0.

For details, see the part that describes how to set the function for measurement value output at alarm recovery in the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

JP1 Event Double Quote

Specifies whether to enclose a JP1 user event message with quotation marks. Note that this setting takes effect only for UNIX.

The specifiable values are 0 (does not enclose) or 1 (encloses).

The default value is 1.

For details, see the part that describes configuration for linking with JP1/IM in the chapter that describes operation monitoring by linking with the integrated management product (JP1/IM) in the Job Management Partner 1/Performance Management User's Guide.

Common Msglog Type

Specifies the output format of the common message log for linking with the log file trapping function of JP1/Base.

The specifiable value is either of the following values:

0: Sequential file format

1: Wrap-around file format

The default value is 0.

For details, see the part that describes how to set the output format of logs in the chapter that describes error detection for Performance Management in the Job Management Partner 1/Performance Management User's Guide.

NS Status Mode

Displays the settings information about the status management function.

Do not edit the value of this label. To verify or change the value of this setting, use the jpcconf stat command. For details, see 2. Commands.

NS IPv6 Mode

Displays the settings information about the network configuration.

Do not edit the value of this label. To verify or change the value of this setting, use the jpcconf ipv6 command. For details, see 2. Commands.

Get Host Mode

Specifies the acquisition method for the physical host name in the function for setting monitoring host names.

The specifiable values are as follows.

Note that the value of this label must be changed by using the jpcconf host hostmode command rather than edited. For details, see 2. Commands.

In Windows:

0: A host name is acquired by using the hostname command.

2: A host name is acquired by using the alias name.

In UNIX:

0: A host name is acquired by using the uname command.

1: A host name is acquired by using the hostname command.

2: A host name is acquired by using the alias name.

The default value is 0.

Host Name

Displays the name of a host in the environment where the Performance Management program runs. The host name is set automatically.

Do not edit the value of this label.

Host Alias Name

Displays the alias name of the environment where the Performance Management program runs.

Do not edit the value of this label.

Correlator Startup Mode

Specifies whether to use the Correlator quick startup function in PFM - Manager.

The specifiable values are 0 (does not use) or 1 (uses).

The default value is 1. However, for an overwrite installation, when this label is not described, the default value is 0.

Note that the value of this label does not need to be specified for PFM - Base, and the default values is as follows:

If the version of PFM - Base is earlier than 10-10-20: 0

If the version of PFM - Base is 10-10-20 or later: 1

However, for an overwrite installation, if this label is not included, the value is 0.

If the specified value is outside the specifiable range, it is assumed that 0 is specified.

If you specify 1, the following agent events are output:

State change (Unconfirmed)

State information

State information (Unconfirmed)

For details about the Correlator quick startup function, see the chapter about troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Retry Getting Alarm Status

When the Correlator service was not able to correctly confirm the alarm status of the agent due to an error like a communication error, specifies whether to reconfirm the alarm status next time an alarm event is received from the agent.

The specifiable values are 0 (does not reconfirm) or 1 (reconfirms).

The default value is 1.

If the specified value is outside the specifiable range, it is assumed that 1 is specified.

If you specify 1, the following agent events are output:

State change (Unconfirmed)

State information

State information (Unconfirmed)

Note that when the Correlator quick startup function is enabled, the alarm status is reconfirmed regardless of whether or not this label is enabled. For details about the Correlator quick startup function, see the chapter about troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Business Group Monitor Mode

Specifies whether to use the access control feature based on business groups.

The specifiable values are 0 (does not use) or 1 (uses).

The default value is 0.

If the specified value is outside the specifiable range, an error message is output and the PFM - Manager service fails to start.

For details, see the chapter that describes the management of user accounts and business groups in the Job Management Partner 1/Performance Management User's Guide.

Agent Remote Protection

Specifies whether to enable the option for restricting Agent host remote operation. The specifiable values are 0 (disables) or 1 (enables).

The default value is 0.

If the specified value is outside the specifiable range, it is assumed that 0 is specified.

For details, see the chapter that describes the Performance Management function in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Service List Protection

Specifies whether to enable the option for restricting the viewing of service information from Agent hosts. The specifiable values are 0 (disables) or 1 (enables).

The default value is 0.

If the specified value is outside the specifiable range, it is assumed that 0 is specified.

For details, see the chapter that describes the Performance Management function in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Prioritize Manager Startup Communication

Specifies whether to prioritize the processing for starting the PFM - Manager service. The specifiable values are 0 (do not prioritize) and 1 (prioritize).

The default value is 1.

When this label is not described for an overwrite installation, it is assumed that 1 is specified.

If a non-specifiable value is specified, it is assumed that 1 is specified.

When 0 is specified, requests from PFM - Agent and PFM -RM will be received during the startup of the PFM - Manager service. Accordingly, PFM - Agent and PFM -RM will switch from the standalone mode to the normal mode earlier. If, however, the system has a large number of PFM - Agent and PFM - RM hosts, the PFM - Manager service might fail to start. For this reason, we recommend that you specify 1.

Multiple Manager

Displays whether the multiple monitoring configuration is used. The meanings of the values are as follows:

0: Cannot be used

1: Can be used

The default value is 0.

Do not edit the value of this label. To change the value of this setting, use the jpcconf mgrhost define command. For details, see 2. Commands.

Remote Action Control

Specifies the remote action control mode. The specifiable values are as follows:

all: All-execution mode

one: One-sided execution mode

primary: Primary execution mode

The values are case sensitive. The default value is all. If a non-specifiable value is specified, it is assumed that all is specified.

For details, see the section that explains how to set up remote action control in the Job Management Partner 1/Performance Management User's Guide.

Alarm Command Wait Mode

Specifies whether to put the execution of alarm commands on hold when a command that cannot be executed concurrently is being executed in PFM - Manager. The specifiable values are as follows:

0: Do not put the execution on hold (Do not execute alarm commands if a command that cannot be executed concurrently is being executed)

1: Put the execution on hold

The default value is 0.

If you specify any other value than those allowed, 0 is set.

For details, see Commands that cannot be executed with alarm commands.

Alarm Command Timeout

Specifies the number of seconds for which the execution of alarm commands should be put on hold in PFM - Manager when the value of Alarm Command Wait Mode is 1.

Specifiable values: 0 to 3600

Default: 300

If the specified value is outside the specifiable range, the default value is set.

For details, see Commands that cannot be executed with alarm commands.

Historical Data Collection Priority Mode

Specifies whether to enable the historical data collection priority function for all Agent Collector services and Remote Monitor Collector services. The historical data collection priority function prioritizes the collection of historical data over the display of real-time reports.

The specifiable values are as follows:

0: Disable

1: Enable

The default value is 0.

If this setting exists in the Agent Collector x Section#1 section, the value of the setting in that section is prioritized.

For details, see the description of troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Random Retry Mode

Specifies whether attempts to connect the monitoring agent to the monitoring manager are to be made at random intervals (the dispersion of the reconnection).

The specifiable values are as follows:

0: Do not use random intervals

1: Use random intervals

The default value is 1. However, for an overwrite installation, if this label is not included, the value is 0.

If the specified value is outside the specifiable range, the default value is set.

Monitoring Suspend Mode

Specifies whether to enable the monitoring suspension function.

The specifiable values are as follows:

0: Disable

1: Enable

The default value is 0.

For details, see the description of the monitoring suspension function in the Job Management Partner 1/Performance Management User's Guide.

Auto Sync for Suspend Setting

Specifies whether to automatically synchronize the settings information to the secondary PFM - Manager, when monitoring is suspended or resumed for the primary PFM - Manager in a multiple monitoring environment and when the value of Monitoring Suspend Mode is 1.

The specifiable values are as follows:

0: Disable

1: Enable

The default value is 0.

For details, see the description of the automatic synchronization options for the settings information of the monitoring suspension function (for multiple monitoring) in the Job Management Partner 1/Performance Management User's Guide.

Action Log Section

Action Log Mode

Specifies whether to output action logs.

The specifiable values are 0 (does not output) or 1 (outputs).

The default value is 0.

If the specified value is outside the specifiable range, an error message is output and no action log is output.

For details, see the part that describes the settings for outputting action logs in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Action Log Dir#2

Specifies a directory to which action logs are output with its absolute path.

For a logical host environment, specify a directory on the shared disk. If the specified directory is not on the shared disk, an action log is output to each physical host constituting the logical host.

Specifiable values: 1 to 185-byte character string

Default: Not specified

If this label is not specified, the following directory is set.

For physical hosts:

Windows:installation-folder\auditlog\

UNIX:/opt/jp1pc/auditlog/

For logical hosts:

Windows: environment-directory\jp1pc\auditlog\

UNIX: environment-directory/jp1pc/auditlog/

If the specified path exceeds the maximum length, or an attempt to access the directory fails, an error message is output to the common log and no action log is output.

For details, see the part that describes the settings for outputting action logs in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Action Log Num

Specifies the maximum total number of action log files (the number of stored files). The total number indicates the total number of the current output files and shift files of action log files.

Specifiable values: Integer from 2 to 10

Default: Not specified

If this label is not specified, 5 is set.

If the specified value is not a numeric value, an error message is output and 5 is set.

If the specified value is outside the specifiable range, an error message is output and an integer value from 2 to 10 that is the nearest to the specified value is set.

For details, see the part that describes the settings for outputting action logs in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Action Log Size

Specifies the size of an action log file in kilobytes.

Specifiable values: Integer from 512 to 2096128

Default: Not specified

If this label is not specified, 2048 is set.

If the specified value is not a numeric value, an error message is output and 2048 is set.

If the specified value is outside the specifiable range, an error message is output and an integer value from 512 to 2096128 that is the nearest to the specified value is set.

For details, see the part that describes the settings for outputting action logs in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

All sections except the following sections

Common Section

Action Log Section

NS Keepalive Mode

Specifies operation from when Performance Management terminates communication until the line is disconnected.

The specifiable value is as follows.

0: Immediately after communication is terminated, the line is disconnected.

3: After communication is terminated, the line is held for the number of seconds specified for the NS Connection Timeout label.

The default value is 3.

For details, see the part that describes the settings for disconnecting a communication line in the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Action Handler Section

Action Execution Count Limitation

Specifies whether to enable the concurrent execution controller for actions. This controller limits the number command actions (remote and local actions) that can be executed concurrently by one Action Handler.

The specifiable values are as follows:

0: Disable

1: Enable

The default value is 0.

Action Concurrent Execution Count

Specifies the maximum number of command actions (actions) that can be executed concurrently. When the maximum number is reached, subsequent actions to be executed are put on hold and then executed sequentially.

Specifiable values: 1 to 48

Default: 10

If the specified value is not a numeric value or is outside the specifiable range, the default value is set.

Action Execution Queue Count

Specifies the maximum number of actions to be executed that can be put on hold. When the maximum number is reached, subsequent actions are output to the event log and the trace log, and then discarded.

Specifiable values: 1 to 2400

Default: 1000

If the specified value is not a numeric value or is outside the specifiable range, the default value is set.

Action Execution Time Limit

Specifies the time until an action is forcibly stopped for an action that remains unfinished for a long time.

Specifiable values: 0 to 900

Default: 300

If the specified value is not a numeric value or is outside the specifiable range, the default value is set.

It is recommended that the default value be used for this label, because actions in progress might be forcibly stopped if a smaller value is specified.

Name Server Section

NS Connection Timeout

Specifies the number of seconds for which the line is held after Performance Management terminates communication.

Specifiable values: 1 to 86400

Default: 70

If the specified value is not a numeric value or is outside the specifiable range, the default value is set.

For details, see the part that describes estimation and configuration when the number of PFM - Agents and PFM - RMs to be connected to PFM - Manager is large in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

NS Maximum Connections

Specifies the maximum number of connections that Performance Management can establish concurrently.

Specifiable values: 1 to 10000

Default: 100 (when PFM - Manager 09-00 or later is newly installed, the default is 1500)

If the specified value is not a numeric value or is outside the specifiable range, 100 is set.

For details, see the part that describes estimation and configuration when the number of PFM - Agents and PFM - RMs to be connected to PFM - Manager is large in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Master Manager Section

NS Connection Timeout

Same as the description of each label given in the Name Server Section.

NS Maximum Connections

Correlator Section

NS Connection Timeout

Same as the description of each label given in the Name Server Section.

NS Maximum Connections

Agent Collector x Section#1

NS Cache Maintenance Time

Specifies the minimum value of the record collection interval of PFM - Agent and PFM - RM.

Specifiable values: 0 to 604800

Default: 70

If the specified value is not a numeric value or is outside the specifiable range, the default value is set.

For details, see the part that describes estimation and configuration when the number of PFM - Agents and PFM - RMs to be connected to PFM - Manager is large in the appendix in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

NS Init Retry Count

Specifies the number of retries for the communication initialization processing.

Specifiable values: 1 to 2000.

Default: 2

If the specified value is not a numeric value or is outside the specifiable range, the default value is set.

Historical Data Collection Priority Mode

Specifies whether to enable the historical data collection priority function for each applicable Agent Collector or Remote Monitor Collector service individually. The historical data collection priority function prioritizes the collection of historical data over the display of real-time reports.

The specifiable values are as follows:

NA: Do not use individual settings

0: Disable

1: Enable

The default value is NA.

If NA is specified, the value specified for Historical Data Collection Priority Mode in Common Section is applied.

For details, see the description of troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

Agent Store x Section#1

NS Init Retry Count

Same as the description of the NS Init Retry Count label given in the Agent Collector x Section.

Tools Section

StartService Retry Interval

Specifies the retry interval for the startup of the Performance Management service in seconds.

Specifiable values: 30 to 600

Default: 45

If the specified value is outside the specifiable range, a value (30 or 600) that is the nearest to the specified value is set.

For details, see the part that describes startup on a Windows machine in the chapter that describes starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.

StartService Retry Count

Specifies the number of retries for the startup of the Performance Management service.

Specifiable values: 0 to 120

Default: 3

If the specified value is outside the specifiable range, a value (0 or 120) that is the nearest to the specified value is set.

For details, see the part that describes startup on a Windows machine in the chapter that describes starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.

#1

x indicates the product ID specific to each PFM - Agent or PFM - RM. For details about the product ID of PFM - Agent or PFM - RM, see the list of identifiers in the manual of each PFM - Agent or PFM - RM.

#2

After specifying this label on a physical host, when you set a logical host by using the jpcconf ha setup command, the settings of the physical host are applied to the logical host. When you use the logical host and physical host concurrently, make sure that the directory to which action logs are output is separate.

F.2 Procedure for changing the startup information file (jpccomm.ini)

To change the behavior of PFM - Manager, PFM - Agent, or PFM - RM, you must first stop the active Performance Management service on the host where the program is installed, edit and save the startup information file (jpccomm.ini), and then start the service that you previously stopped.

Prerequisites

If you are logged in to PFM - Web Console, you must log out. When you change the startup information file, the Performance Management service on the host is stopped. As a result, for PFM - Manager, operations from PFM - Web Console result in errors. Similarly, for PFM - Agent and PFM - RM, some operations might result in errors.

Procedure

Use the jpcspm stop command to stop the active Performance Management service on the host.

Use a text editor or another editor to open the jpccomm.ini file.

For details on the installation location of the jpccomm.ini file, see F. Startup Information File (jpccomm.ini).

Edit, save, and then close the jpccomm.ini file.

For details on the settings items in the jpccomm.ini file, see F.1 Settings items in the startup information file (jpccomm.ini).

Use the jpcspm start command to start the Performance Management service that you stopped in step 1.

G. Correspondence Between New Commands and Old Commands

The following table shows the correspondence between commands for version 09-00 or later and commands for version 08-11 or earlier for use on PFM - Manager, PFM - Agent, PFM - Base, and PFM - Web Console. You can still use the old commands on version 09-00 or later of PFM - Manager, PFM - Agent, PFM - Base, and PFM - Web Console.

Table G‒1: New commands and old commands of Performance Management (PFM - Manager, PFM - Agent, PFM - Base, and PFM - Web Console)

Old command name

New command name

Function

jpcagtsetup

jpcconf agent setup

Executes additional setup of a new PFM - Agent or PFM - RM.#1

jpcalarm active

jpctool alarm active

Enables a disabled alarm.

jpcalarm bind

jpctool alarm bind

Binds an alarm table to an agent.

jpcalarm check

jpctool alarm check

Checks the validity of the syntax and definitions in the alarm definition file.

jpcalarm copy

jpctool alarm copy

Copies an alarm table or alarm.

jpcalarm delete

jpctool alarm delete

Deletes an alarm table or alarm.

jpcalarm export

jpctool alarm export

Exports an alarm definition file.

jpcalarm import

jpctool alarm import

Imports an alarm definition file.

jpcalarm inactive

jpctool alarm inactive

Disables an enabled alarm.

jpcalarm list

jpctool alarm list

Displays alarm table definition information.

jpcalarm unbind

jpctool alarm unbind

Unbinds an alarm table.

jpcaspsv output

No change

Outputs definition information for the Store database storage conditions.

jpcaspsv update

No change

Changes definition information for the Store database storage conditions.

jpcasrec output

No change

Outputs definition information for the Store database recording method.

jpcasrec update

No change

Changes definition information for the Store database recording method.

jpcctrl backup

jpctool db backup

Creates a backup file for the data stored in the Master Store, Agent Store, or Remote Monitor Store service database.#1

jpcctrl clear

jpctool db clear

Erases the data stored in the Master Store, Agent Store, or Remote Monitor Store service database.#1

jpcctrl delete

jpctool service delete

Deletes the service information for an agent registered in Performance Management.#1

jpcctrl dump

jpctool db dump

Exports data from the Master Store, Agent Store, or Remote Monitor Store service database to a text file.#1

jpcctrl list

jpctool service list

Displays the service configuration and status of a Performance Management program.#1

jpcctrl register

jpctool service register

Re-registers deleted service information for a Performance Management program on Performance Management.#1

jpcdbctrl config

jpcconf db define

Changes and displays the settings of the Store service.

jpcdbctrl display

jpcconf db display

Displays information about the Store service or the backup data.

Checks the version of Store (1.0 or 2.0).

jpcdbctrl dmconvert

jpctool db dmconvert

Converts the data model of the backup data.

jpcdbctrl import

jpctool db import

Imports backup data to the Store database.

jpcdbctrl setup

jpcconf db vrset#2

Sets up the functions of Store 2.0 (for the Agent Store and Remote Monitor Store services).

jpcdbctrl unsetup

Restores the Store version to 1.0 from 2.0.

jpchasetup create

jpcconf ha setup

Creates a logical host environment for a Performance Management program.#1

jpchasetup delete

jpcconf ha unsetup

Deletes a logical host environment for a Performance Management program.#1

jpchasetup export

jpcconf ha export

Exports the logical host environment settings for a Performance Management program, to a file.#1

jpchasetup import

jpcconf ha import

Imports a logical host environment information file for a Performance Management program, to the standby node.#1

jpchasetup list

jpcconf ha list

Displays logical host environment settings for a Performance Management program.#1

jpcimevt

No change

Registers a JP1 event in the event server and sends the registered event to JP1/IM.

jpcimsetup#3

jpcconf im enable

Enables the JP1/IM monitored object linkage function.#1

jpcconf im disable

Disables the JP1/IM monitored object linkage function.#1

jpcinslist

jpcconf inst list

Displays the names of instances set up by a PFM - Agent or PFM - RM that can start a set of multiple services on a single host.#1

jpcinssetup

jpcconf inst setup

Creates or updates an instance environment for a PFM - Agent or PFM - RM that can start a set of multiple services on a single host.#1

jpcinsunsetup

jpcconf inst unsetup

Deletes an instance environment for a PFM - Agent or PFM - RM that can start a set of multiple services on a single host.#1

jpcmkkey

No change

Creates an authentication key file required for command execution in PFM - Web Console.

jpcnsconfig port#³

jpcconf port list

Displays port numbers used with Performance Management.#1

jpcconf port define

Sets port numbers used with Performance Management.#1

jpcnshostname#³

jpcconf mgrhost define

Sets or changes the host name of PFM - Manager for the connection destination (Name Server service).#1

jpcconf mgrhost display

Displays the host name of PFM - Manager for the connection destination (Name Server service).#1

jpcovsetup

jpcconf ov enable

Sets up the NNM linkage facility.#4

jpcovunsetup

jpcconf ov disable

Performs an unsetup of the NNM linkage facility.#4

jpcras

No change

Collects information about PFM - Manager, PFM - Agent, PFM - RM, or PFM - Base, as well as OS information.#1

jpcrdef create

No change

Registers new report definitions.

jpcrdef delete

No change

Deletes existing report definitions.

jpcrdef output

No change

Outputs existing report definitions.

jpcresto

jpctool db restore

Restores the Master Store, Agent Store, or Remote Monitor Store service database that was backed up by the jpctool db backup command.#1

jpcrpt

No change

Outputs a report displayed on PFM - Web Console to a batch report in the CSV format or HTML format.

jpcstart

jpcspm start

Starts the service of a Performance Management program at the local host.#1

jpcstop

jpcspm stop

Stops the service of a Performance Management program at the local host.#1

jpcstsetup disable

jpcconf stat disable

Disables the status management function.

jpcstsetup display

jpcconf stat display

Displays the status of the status management function.

jpcstsetup enable

jpcconf stat enable

Enables the status management function.

jpcstsetup hcdisable

jpcconf hc disable

Disables the health check function.

jpcstsetup hcdisplay

jpcconf hc display

Displays the status of the health check function.

jpcstsetup hcenable

jpcconf hc enable

Enables the health check function.

jpcwagtsetup

No change

Registers a new PFM - Agent or PFM - RM in PFM - Web Console.

jpcwras

No change

Collects PFM - Web Console information.

jpcwstart

No change

Starts the PFM - Web Console service.

jpcwstop

No change

Stops the PFM - Web Console service.

#1

If this command's execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

#2

These commands were integrated into a single new command.

#3

These commands were split into several new commands.

#4

These commands are stored in the following directory:

In Windows: installation-folder\NNMEx\

In UNIX: /opt/jp1pc/NNMEx/

H. Checking the Definition Information

Before importing definition information, the jpctool config mgrimport command checks whether the definition information specified by the -d option matches that stored in the import-source directory. If a discrepant item of definition information is found, a KAVE06142-E message is output to the standard error output and common message log. Note that the KAVE06142-E message is output as many times as the number of discrepant items of definition information.

The following table lists the definition information names that are displayed in the KAVE06142-E message and the items of definition information set in the relevant files.

Table H‒1: Definition information that is set in files

Definition information name

File name

(setup item name)

Checking method

jpchosts

jpchosts

(host information settings)

Compare files.#

jpcvsvr.ini, label=UserServer.

authenticationMode

jpcvsvr.ini

(authentication mode settings)

Compare the text strings of label settings.

monitoringitems.cfg

monitoringitems.cfg

(ITSLM-linkage custom monitoring items)

Compare files.#

#

When files are compared to check definition information, both of the files, including comments, must be completely identical.

The tables below list the definition information names that might be output in the KAVE06142-E message if discrepant definition information is found and the corresponding items of which the settings must be checked. If discrepant definition information is found, check the definition information name in the KAVE06142-E message, correct the setting of the discrepant definition information, and then re-execute the jpctool config mgrimport command.

Table H‒2: Definition information that is set in the jpccomm.ini file

Definition information name

Section name

Label name

jpccomm.ini, section=Common Section, label=Multiple Alarm Table Bind

Common Section

Multiple Alarm Table Bind

jpccomm.ini, section=Common Section, label=Alarm Message Mode

Alarm Message Mode

jpccomm.ini, section=Common Section, label=JP1 Event Double Quote

JP1 Event Double Quote

jpccomm.ini, section=Common Section, label=Correlator Startup Mode

Correlator Startup Mode

jpccomm.ini, section=Common Section, label=Retry Getting Alarm Status

Retry Getting Alarm Status

jpccomm.ini, section=Common Section, label=Business Group Monitor Mode

Business Group Monitor Mode

jpccomm.ini, section=Common Section, label=Agent Remote Protection

Agent Remote Protection

jpccomm.ini, section=Common Section, label=Service List Protection

Service List Protection

jpccomm.ini, section=Common Section, label=Prioritize Manager Startup

Prioritize Manager Startup

jpccomm.ini, section=Common Section, label=Multiple Manager

Multiple Manager

jpccomm.ini, section=Common Section, label=Remote Action Control

Remote Action Control

jpccomm.ini, section=Common Section, label=Alarm Command Wait Mode

Alarm Command Wait Mode

jpccomm.ini, section=Common Section, label=Alarm Command Timeout

Alarm Command Timeout

jpccomm.ini, section=Common Section, label=Historical Data Collection Priority Mode

Historical Data Collection Priority Mode

jpccomm.ini, section=Common Section, label=Random Retry Mode

Random Retry Mode

jpccomm.ini, section=Common Section, label=Monitoring Suspend Mode

Monitoring Suspend Mode

jpccomm.ini, section=Common Section, label=Auto Sync for Suspend Setting

Auto Sync for Suspend Setting

jpccomm.ini, section=Name Server Section, label=NS Connection Timeout

Name Server Section

NS Connection Timeout

jpccomm.ini, section=Name Server Section, label=NS Maximum Connections

NS Maximum Connections

jpccomm.ini, section=Name Server Section, label=NS Keepalive Mode

NS Keepalive Mode

jpccomm.ini, section=Master Manager Section, label=NS Connection Timeout

Master Manager Section

NS Connection Timeout

jpccomm.ini, section=Master Manager Section, label=NS Maximum Connections

NS Maximum Connections

jpccomm.ini, section=Master Manager Section, label=NS Keepalive Mode

NS Keepalive Mode

jpccomm.ini, section=Correlator Section, label=NS Connection Timeout

Correlator Section

NS Connection Timeout

jpccomm.ini, section=Correlator Section, label=NS Maximum Connections

NS Maximum Connections

jpccomm.ini, section=Correlator Section, label=NS Keepalive Mode

NS Keepalive Mode

jpccomm.ini, section=Tools Section, label=StartService Retry Interval

Tools Section

StartService Retry Interval

jpccomm.ini, section=Tools Section, label=StartService Retry Count

StartService Retry Count

jpccomm.ini, section=Tools Section, label=NS Keepalive Mode

NS Keepalive Mode

jpccomm.ini, section=Master Store Section, label=NS Keepalive Mode

Master Store Section

NS Keepalive Mode

jpccomm.ini, section=Action Handler Section, label=NS Keepalive Mode

Action Handler Section

NS Keepalive Mode

jpccomm.ini, section=Action Handler Section, label=Action Execution Count Limitation

Action Execution Count Limitation

jpccomm.ini, section=Action Handler Section, label=Action Concurrent Execution Count

Action Concurrent Execution Count

jpccomm.ini, section=Action Handler Section, label=Action Execution Queue Count

Action Execution Queue Count

jpccomm.ini, section=Action Handler Section, label=Action Execution Time Limit

Action Execution Time Limit

jpccomm.ini, section=Trap Generator Section, label=NS Keepalive Mode

Trap Generator Section

NS Keepalive Mode

jpccomm.ini, section=Status Server Section, label=NS Keepalive Mode

Status Server Section

NS Keepalive Mode

jpccomm.ini, section=View Server Section, label=NS Keepalive Mode

View Server Section

NS Keepalive Mode

jpccomm.ini, section=Agent Collector 0 Section, label=NS Keepalive Mode

Agent Collector 0 Section

NS Keepalive Mode

jpccomm.ini, section=Agent Collector 0 Section, label=Historical Data Collection Priority Mode

Historical Data Collection Priority Mode

Table H‒3: Definition information that is set from the services tree of PFM - Web Console (host name: HealthCheck)

Definition information name

Folder name

Property name

HealthCheck, Property=JP1 Event Configurations->Agent Collector

JP1 Event Configurations

--

Agent Collector

HealthCheck, Property=JP1 Event Configurations->Agent Store

Agent Store

HealthCheck, Property=Detail Records->PD->Log

Detail Records

PD

Log

HealthCheck, Property=Detail Records->PD->Collection Interval

Collection Interval

HealthCheck, Property=Detail Records->PD->Collection Offset

Collection Offset

HealthCheck, Property=Detail Records->PD->Realtime Report Data Collection Mode

Realtime Report Data Collection Mode#

HealthCheck, Property=Detail Records->PD->LOGIF

LOGIF

HealthCheck, Property=Detail Records->HC->Log

HC

Log

HealthCheck, Property=Detail Records->HC->Collection Interval

Collection Interval

HealthCheck, Property=Detail Records->HC->Collection Offset

Collection Offset

HealthCheck, Property=Detail Records->HC->Realtime Report Data Collection Mode

Realtime Report Data Collection Mode#

HealthCheck, Property=Detail Records->HC->LOGIF

LOGIF

HealthCheck, Property=Detail Records->HOST->Log

HOST

Log

HealthCheck, Property=Detail Records->HOST->Realtime Report Data Collection Mode

Realtime Report Data Collection Mode#

HealthCheck, Property=Detail Records->HOST->LOGIF

LOGIF

HealthCheck, Property=Interval Records->PI->Log

Interval Records

PI

Log

HealthCheck, Property=Interval Records->PI->Collection Interval

Collection Interval

HealthCheck, Property=Interval Records->PI->Collection Offset

Collection Offset

HealthCheck, Property=Interval Records->PI->Realtime Report Data Collection Mode

Realtime Report Data Collection Mode#

HealthCheck, Property=Interval Records->PI->LOGIF

LOGIF

HealthCheck, Property=Interval Records->SYS->Log

SYS

Log

HealthCheck, Property=Interval Records->SYS->Realtime Report Data Collection Mode

Realtime Report Data Collection Mode#

HealthCheck, Property=Interval Records->SYS->LOGIF

LOGIF

HealthCheck, Property=Interval Records->HAVL->Log

HAVL

Log

HealthCheck, Property=Interval Records->HAVL->Realtime Report Data Collection Mode

Realtime Report Data Collection Mode#

HealthCheck, Property=Interval Records->HAVL->LOGIF

LOGIF

HealthCheck, Property=Health Check Configurations->Monitoring Level

Health Check Configurations

--

Monitoring Level

HealthCheck, Property=Health Check Configurations->Incl Action Handler

Incl Action Handler

HealthCheck, Property=Health Check Configurations->Busy as Inactive

Busy as Inactive

HealthCheck, Property=Health Check Configurations->Time to Busy as Inactive Collector

Time to Busy as Inactive Collector

HealthCheck, Property=Health Check Configurations->Time to Busy as Inactive Store

Time to Busy as Inactive Store

HealthCheck, Property=Health Check Configurations->Time to Busy as Inactive AH

Time to Busy as Inactive AH

HealthCheck, Property=Health Check Configurations->JP1 Event

JP1 Event

HealthCheck, Property=Health Check Configurations->JP1 Event - Not Supported

JP1 Event - Not Supported

HealthCheck, Property=Health Check Configurations->JP1 Event - Running

JP1 Event - Running

HealthCheck, Property=Health Check Configurations->JP1 Event - Incomplete

JP1 Event - Incomplete

HealthCheck, Property=Health Check Configurations->JP1 Event - Stopped

JP1 Event - Stopped

HealthCheck, Property=Health Check Configurations->JP1 Event - Unconfirmed

JP1 Event - Unconfirmed

HealthCheck, Property=Health Check Configurations->JP1 Event - Host Not Available

JP1 Event - Host Not Available

HealthCheck, Property=Health Check Configurations->Parallel Confirmation Mode

Parallel Confirmation Mode

HealthCheck, Property=Health Check Configurations->Parallel Confirmation Count

Parallel Confirmation Count

HealthCheck, Property=Health Check Configurations->Minimum Period Per Host

Minimum Period Per Host

HealthCheck, Property=Health Check Configurations->Timeout Period Per Host

Timeout Period Per Host

Legend:

--: None

#

If the historical data collection priority function for prioritizing the collection of historical data over the display of real-time reports is enabled, the values of these properties must be the same. If this function is disabled, these properties are not displayed.

Table H‒4: Definition information that is set from the services tree of PFM - Web Console (host name: HealthCheck(Store))

Definition information name (string displayed in the message)

Folder name

Property name

HealthCheck(Store), Property=RetentionEx->Product Interval - PI->Period - Minute Drawer (Day)

RetentionEx

Product Interval - PI

Period - Minute Drawer (Day)

HealthCheck(Store), Property=RetentionEx->Product Interval - PI->Period - Hour Drawer (Day)

Period - Hour Drawer (Day)

HealthCheck(Store), Property=RetentionEx->Product Interval - PI->Period - Day Drawer (Week)

Period - Day Drawer (Week)

HealthCheck(Store), Property=RetentionEx->Product Interval - PI->Period - Week Drawer (Week)

Period - Week Drawer (Week)

HealthCheck(Store), Property=RetentionEx->Product Interval - PI->Period - Month Drawer (Month)

Period - Month Drawer (Month)

HealthCheck(Store), Property=RetentionEx->Product Interval - PI->Period - Year Drawer (Year)

Period - Year Drawer (Year)

HealthCheck(Store), Property=RetentionEx->Product Interval - SYS->Period - Minute Drawer (Day)

Product Interval - SYS

Period - Minute Drawer (Day)

HealthCheck(Store), Property=RetentionEx->Product Interval - SYS->Period - Hour Drawer (Day)

Period - Hour Drawer (Day)

HealthCheck(Store), Property=RetentionEx->Product Interval - SYS->Period - Day Drawer (Week)

Period - Day Drawer (Week)

HealthCheck(Store), Property=RetentionEx->Product Interval - SYS->Period - Week Drawer (Week)

Period - Week Drawer (Week)

HealthCheck(Store), Property=RetentionEx->Product Interval - SYS->Period - Month Drawer (Month)

Period - Month Drawer (Month)

HealthCheck(Store), Property=RetentionEx->Product Interval - SYS->Period - Year Drawer (Year)

Period - Year Drawer (Year)

HealthCheck(Store), Property=RetentionEx->Product Interval - HAVL->Period - Minute Drawer (Day)

Product Interval - HAVL

Period - Minute Drawer (Day)

HealthCheck(Store), Property=RetentionEx->Product Interval - HAVL->Period - Hour Drawer (Day)

Period - Hour Drawer (Day)

HealthCheck(Store), Property=RetentionEx->Product Interval - HAVL->Period - Day Drawer (Week)

Period - Day Drawer (Week)

HealthCheck(Store), Property=RetentionEx->Product Interval - HAVL->Period - Week Drawer (Week)

Period - Week Drawer (Week)

HealthCheck(Store), Property=RetentionEx->Product Interval - HAVL->Period - Month Drawer (Month)

Period - Month Drawer (Month)

HealthCheck(Store), Property=RetentionEx->Product Interval - HAVL->Period - Year Drawer (Year)

Period - Year Drawer (Year)

HealthCheck(Store), Property=RetentionEx->Product Detail - PD->Period (Day)

Product Detail - PD

Period (Day)

HealthCheck(Store), Property=RetentionEx->Product Detail - HC->Period (Day)

Product Detail - HC

Period (Day)

HealthCheck(Store), Property=RetentionEx->Product Detail - HOST->Period (Day)

Product Detail - HOST

Period (Day)

Master Manager, Property=JP1 Event Configurations->Name Server

JP1 Event Configurations

--

Name Server

Master Manager, Property=JP1 Event Configurations->Master Manager

Master Manager

Master Manager, Property=JP1 Event Configurations->Master Store

Master Store

Master Manager, Property=JP1 Event Configurations->Correlator

Correlator

Master Manager, Property=JP1 Event Configurations->Trap Generator

Trap Generator

Master Manager, Property=JP1 Event Configurations->View Server

View Server

Master Manager, Property=JP1 Event Configurations->Action Handler

Action Handler

Master Manager, Property=JP1 Event Configurations->Status Server

Status Server

Master Manager, Property=JP1 Event Configurations->JP1 Event Send Host

JP1 Event Send Host

Master Manager, Property=JP1 Event Configurations->Monitoring Console Host

Monitoring Console Host

Master Manager, Property=JP1 Event Configurations->Monitoring Console Port

Monitoring Console Port

Master Manager, Property=JP1 Event Configurations->Alarm->JP1 Event Mode

Alarm

JP1 Event Mode

Master Manager, Property=JP1 Event Configurations->System->Monitoring Suspend

System

Monitoring Suspend

Master Manager, Property=ITSLM Coordination Configuration->ITSLM Coordination->ITSLM Host

ITSLM Coordination Configuration

ITSLM Coordination

ITSLM Host

Legend:

--: None

I. Information Output by the jpcparamdump Command

I.1 Types of files output by the jpcparamdump command

The jpcparamdump command outputs settings information about the Performance Management program to a file. This command creates the directory specified by the -d option and outputs Host.prm, Instance.prm, or RA_monitoring-target-name.prm, depending on the product installed on the target host.

Files output by the jpcparamdump command

File name

Summary

Output destination#

Host.prm

The command outputs settings information about the following products:

PFM - Manager

PFM - Base

Single-instance PFM - Agent

directory-specified-by-the-"-d"-option/monitoring-host-name/

Instance.prm

The command outputs settings information about instances of the following products:

PFM - RM

Multi-instance PFM - Agent

directory-specified-by-the-"-d"-option/monitoring-host-name/product-name/instance-name

RA_monitoring-target-name.prm

The command outputs settings information about remote agents of the following products:

PFM - RM

#: Directories are created when the command is executed.

If the command execution host is a standby node for a logical host, the Instance.prm file and the RA_monitoring-target-name.prm file are not created.

Reference note

To view a list of monitoring agent instances and monitoring target configurations, execute the jpcparamdump command and then use the Windows dir command or the UNIX ls command to display directories under the directory specified for the -d option.

I.2 Content of the Host.prm file

Settings information about PFM - Manager or PFM - Base, and about the single-instance PFM - Agent is output to the Host.prm file. The output information is equivalent to the output results of various commands and the content of definition files.

Content output to the Host.prm file

No.

Header

Description

How to change the settings

Common parts

1

"******product-name******"

The name of the PFM - Manager or PFM - Base product installed on the command execution host

-

2

"***Host Name"

The monitoring host name obtained by the following command:

For physical hosts:

jpcconf host hostmode -display

For logical hosts:

hostmode : Logical

hostname : logical-host-name

-

3

"***Product Information List"

The product ID and version of PFM - Manager or PFM - Base installed on the command execution host

-

4

"***Port Number List"

The list of port numbers obtained by the following commands:

For physical hosts:

jpcconf port list -key all

For logical hosts:

jpcconf port list -key all -lhost logical-host-name

-

5

"***Connection Target PFM Manager"

PFM - Manager for the connection destination obtained by the following command:

For physical hosts:

jpcconf mgrhost display

For logical hosts:

jpcconf mgrhost display -lhost logical-host-name

-

6

"***Settings Information (Common)"

Settings common to the services (content of the jpccomm.ini file)

Edit the jpccomm.ini file. Note that some items cannot be edited.

For details, see F. Startup Information File (jpccomm.ini).

7

"***Settings Information (Action Handler Service)"

Action Handler service settings

[Capabilities Section]

Settings information about alarm execution actions

[SMTP Options]

Settings information about email delivery. Only the values of [Host], [Sender Name], and [Charset] can be changed.

[Mail Options]

Settings information about email delivery

Ignore any other items.

Select Action Handler in the Services tree in PFM - Web Console, and then change the settings for the following nodes displayed in Properties:

[Capabilities] node

[Mail] node

8

"***Settings Information (PFM Service Auto-Restart Function)"

Settings for the PFM Service Auto-Restart function#1.

The order in which sections and labels are displayed differs depending on the order in which they were set. In addition, section names include service IDs#2.

For each of the following services, select the service in the Services tree in PFM - Web Console, and then change the settings for Restart Configurations (displayed in Properties) and the nodes under it.

Master Manager

Action Handler

Agent Collector

Remote Monitor Collector

9

"***Settings Information (JP1 System Event)"

Settings for issuing JP1 system events.

The order in which sections and labels are displayed differs depending on the order in which they were set. In addition, section names include service IDs#2.

For each of the following services, select the service in the Services tree in PFM - Web Console, and then change the settings for JP1 Event Configurations (displayed in Properties) and the nodes under it.

Master Store

Agent Collector

Remote Monitor Collector

10

"***Host Information (jpchosts)"

Host information settings (content of the jpchosts file)

Edit the jpchosts file.

11

"***Settings Information (PFM Service Startup at OS Startup)"

Settings for starting the PFM service when the operating system is started. These settings are obtained by the following commands#1:

For Windows:

wmic service where ( DisplayName LIKE "PFM - %" ) get DisplayName, StartMode

For UNIX:

if [ -x /opt/jp1pc/jpc_start ];then echo jpc_start:available; else echo jpc_start:unavailable;fi;if [ -x /opt/jp1pc/jpc_stop ];then echo jpc_stop:available; else echo jpc_stop:unavailable;fi

For Windows:

Change the settings for the automatic startup of services for the operating system.

For UNIX:

Change the settings for the automatic startup of PFM services.

12

"***Settings Information (Common Account pfmhost)"

Common account information for the instance environment (pfmhost)

Use the jpcconf acc command.

13

"***Settings Information (Common Account wmi)"

Common account information for the monitoring target (wmi)

Use the jpcconf acc command.

14

"***Settings Information (Common Account ssh)"

Common account information for the monitoring target (ssh)

Use the jpcconf acc command.

Parts common to the single-instance PFM - Agent

15

"******product-name******"

The product name of the single-instance PFM - Agent installed on the command execution host

-

16

"***Product Information"

The product ID and version of PFM - Agent installed on the command execution host

-

17

"***Settings Information (Collector Service)"

Collector service settings (content of the jpcagt.ini file)

[Agent]

Information about agent settings

[Interval Records]

Settings for the method for recording PI records.

[Detail Records]

Settings for the method for recording PD records

[Log Records]

Settings for the method for recording PL records

Depending on the settings, the following items might be added after the operation starts #2:

Device Name Cache

ALL WPAR Collection for Process

Collection Offset from Top of Minute

Select Agent Collector in the Services tree in PFM - Web Console, and then change the settings for the following nodes displayed in Properties:

[Agent Configuration] node

[Interval Records] node and the nodes under it.

[Detail Records] node and the nodes under it.

[Log Records] node and the nodes under it

18

"***Settings Information (Store Service)"

Settings for the Store service (content of the jpcsto.ini file)

[RetentionEx Section] and [Retention Section]

Settings information about the storage period for agent performance data

[Mode Section]

Settings information about the Store version of the agent

[Data Section]

Information about the storage location for agent performance data

Ignore any other items.

[RetentionEx Section] and [Retention Section]

Select Agent Store in the Services tree in PFM - Web Console, and then change the settings for [RetentionEx] or [Retention] (displayed in Properties) and the nodes below it.

[Mode Section] or [Data Section]

Use the jpcconf db command.

19

"***ITSLM Connection Information"

ITSLM connection settings

Select the service to be changed in the Services tree in PFM - Web Console, and then change the [ITSLM Connection] settings for the [ITSLM Connection Configuration] node displayed in Properties.

20

"***Alarm Bind Information"

Settings for binding alarm tables

Use the Bind Alarm Table method for each agent in the Agents tree in PFM - Web Console, or use the jpctool alarm command.

21

"***Monitor Suspend Information"

Monitoring suspension settings

Use the Monitoring Suspension Settings method for each agent in the Agents tree in PFM - Web Console, or use the jpctool monitor command.

Parts specific to PFM - Agent for Platform (Windows)

22

"***Configuration Information (Periodically-Executed User Command Function)"

Configuration for the function for periodically executing user commands#1

Select Agent Collector in the Services tree in PFM - Web Console, and then change the settings for the [User Command Setting] node displayed in Properties.

23

"***Application Definition Information (Process Operation Status)"

Whether processes are running (application definition) #1

Select Agent Collector in the Services tree in PFM - Web Console, and then change the settings for the [Advanced application monitoring] node displayed in Properties.

24

"***Application Definition Information (Application Operation Status)"

Whether applications are running (application definition)#1

Select Agent Collector in the Services tree in PFM - Web Console, and then change the settings for the [Application monitoring setting] node displayed in Properties.

25

"***Settings Information (Collection of User Records)"

Settings for collecting user records#1.

Note that different values might be added to each device, regardless of these settings.

Use the collection data addition utility.

Parts specific to PFM - Agent for Platform (UNIX)

26

"***Configuration Information (Periodically-Executed User Command Function)"

Configuration for the function for periodically executing user commands#1

Select Agent Collector in the Services tree in PFM - Web Console, and then change the settings for the [User Command Setting] node displayed in Properties.

27

"***Application Definition Information (Process Operation Status)"

Whether processes are running (application definition) #1

Select Agent Collector in the Services tree in PFM - Web Console, and then change the settings for the [Advanced application monitoring] node displayed in Properties.

28

"***Application Definition Information (Application Operation Status)"

Whether applications are running (application definition)#1

Select Agent Collector in the Services tree in PFM - Web Console, and then change the settings for the [Application monitoring setting] node displayed in Properties.

29

"***Settings Information (evfile)"

Content of the event file#1

Change the settings contained in the event file (/opt/jp1pc/agtu/agent/evfile).

30

"***Settings information (wgfile)"

Content of the work group file #1

Change the settings contained in the work group file (/opt/jp1pc/agtu/agent/wgfile).

#1: For logical hosts, this is not output.

#2: When the output files are compared, the applicable portions might be treated as differences.

I.3 Content of the Instance.prm file

Content output to the Instance.prm file

No.

Header

Description

How to change the settings

Common parts

1

"******product-name******"

The product name of PFM - RM or the multi-instance PFM - Agent installed on the command execution host

-

2

"***Product Information"

The product ID and version of PFM - RM or the multi-instance PFM - Agent installed on the command execution host

-

3

"***Settings Information (Collector Service)"

Collector service settings (content of the jpcagt.ini file)

[Agent]

Information about agent settings

[Interval Records]

Settings for the method for recording PI records

[Detail Records]

Settings for the method for recording PD records

[Log Records]

Settings for the method for recording PL records

[Health Check Configurations]

Settings for the health check (ICMP) for the host to be monitored.

This is not displayed in an environment where an installation has just been performed.

Depending on the settings, the following item might be added after operation starts#:

Health Check for Target Hosts

Select the desired service (either Remote Monitor Collector for PFM - RM, or Agent Collector for PFM - Agent) in the Services tree in PFM - Web Console, and then change the settings for the following nodes displayed in Properties:

[Remote Monitor Configuration] or [Agent Configuration] node

[Interval Records] node and the nodes under it

[Detail Records] node and the nodes under it

[Log Records] node and the nodes under it

[Health Check Configurations] node

4

"***Settings Information (Store Service)"

Settings for the Store service (content of the jpcsto.ini file).

[RetentionEx Section] and [Retention Section]

Settings information about the storage period for agent performance data

[Mode Section]

Settings information about the Store version of the agent. Use the jpcconf db command to confirm the settings.

[Data Section]

Information about the storage location for agent performance data. Use the jpcconf db command to confirm the settings.

Ignore any other items.

[RetentionEx Section] and [Retention Section]

Select the desired Store service (either Remote Monitor Store for PFM - RM, or Agent Store for PFM - Agent) in the Services tree in PFM - Web Console, and then change the settings for [RetentionEx] or [Retention] (displayed in Properties) and the nodes under it.

[Mode Section] or [Data Section]

Use the jpcconf db command.

5

"***Settings Information (Group Agent)"

Settings for the method for recording performance data for the group agent.

Depending on the settings, the following item might be added after operation starts#:

monitoring-target-name

Select Group Agent in the Services tree in PFM - Web Console, and then change the settings for the following nodes displayed in Properties:

[Interval Records] node and the nodes under it

[Detail Records] node and the nodes under it

[Log Records] node and the nodes under it

6

"***ITSLM Connection Information"

ITSLM connection settings

Select the service to be changed in the Services tree in PFM - Web Console, and then change the [ITSLM Connection] settings for the [ITSLM Connection Configuration] node displayed in Properties.

7

"***Alarm Bind Information"

For PFM - RM, the settings for binding alarm tables for group agents are output. For the multi-instance PFM - Agent, the settings for binding alarm tables for instances are output.

Note:

If there is a problem in the communication between the monitoring manager and agents, the information output here might not match the information managed by the monitoring manager.

Use the Bind Alarm Table method for each agent in the Agents tree in PFM - Web Console, or use the jpctool alarm command.

8

"***Monitor Suspend Information (Collector Service)"

Monitoring suspension settings

Use the Monitoring Suspension Settings method for each agent in the Agents tree in PFM - Web Console, or use the jpctool monitor command.

9

"***Monitor Suspend Information (Group Agent)"

Monitoring suspension settings (group agent)

Use the Monitoring Suspension Settings method for each agent in the Agents tree in PFM - Web Console, or use the jpctool monitor command.

Parts specific to PFM - RM for Virtual Machine

10

"***Collector Plug-In Configuration (Virtage)"

Collector plug-in configuration for Virtage.

The information to be output differs depending on the product ID and version of PFM - RM for Virtual Machine.

-

11

"***Collector Plug-In Configuration (Hyper-V)"

Collector plug-in configuration for Hyper-V.

The information to be output differs depending on the product ID and version of PFM - RM for Virtual Machine.

12

"***Collector Plug-In Configuration (KVM)"

Collector plug-in configuration for KVM.

The information to be output differs depending on the product ID and version of PFM - RM for Virtual Machine.

13

"***Collector Plug-In Configuration (VMware)"

Collector plug-in configuration for VMware.

The information to be output differs depending on the product ID and version of PFM - RM for Virtual Machine.

14

"***Settings Information (VM Type)"

Connection definition information about the virtual environment.

The information to be output differs depending on the product ID and version of PFM - RM for Virtual Machine.

#: When the output files are compared, the applicable portions might be treated as differences.

I.4 Content of the RA_monitoring-target-name.prm file

Content output to the RA_monitoring-target-name.prm file

No.

Header

Description

How to change the settings

Common parts

1

"******product-name******"

The product name of PFM - RM installed on the command execution host

-

2

"***Product Information"

The product ID and version of PFM - RM installed on the command execution host

-

3

"***Settings Information (Remote Agent)"

Remote Agent settings.

[Target]

Settings information about the monitoring target.

For PFM - RM for Platform, the JPCAPP label indicates whether the setting for collecting information about whether processes are running (application definition) is enabled or disabled. (The value is 0 if the setting is disabled and 1 if it is enabled.)

[Interval Records]

Settings for the method for recording PI records.

[Detail Records]

Settings for the method for recording PD records.

[Log Records]

Settings for the method for recording PL records.

Select Remote Agent in the Services tree in PFM - Web Console, and then change the settings for the following nodes displayed in Properties:

[Remote Monitor Configuration] node and the nodes under it.

To change the JPCAPP value for PFM - RM for Platform, change the settings for [Application monitoring setting] under this node and the settings for the nodes below [Application monitoring setting].

[Interval Records] node and the nodes under it.

[Detail Records] node and the nodes under it.

[Log Records] node and the nodes under it.

4

"***Alarm Bind Information"

Settings for binding alarm tables

Note:

If there is a problem in the communication between the monitoring manager and agents, the information output here might not match the information managed by the monitoring manager.

Use the Bind Alarm Table method for each agent in the Agents tree in PFM - Web Console, or use the jpctool alarm command.

5

"***Monitor Suspend Information"

Monitoring suspension settings

Use the Monitoring Suspension Settings method for each agent in the Agents tree in PFM - Web Console, or use the jpctool monitor command.

Parts specific to PFM - RM for Platform

6

"***Application Definition Information (Process Operation Status)"

Whether processes are running (application definition).

This might be output even if the setting for collecting information about whether processes are running (application definition) is disabled (when the value of the JPCAPP label in [Target] of "***Settings Information (Remote Agent)" is 0). In such a case, ignore this content.

Use the same method as that for changing the JPCAPP value of "***Settings Information (Remote Agent)".

J. Version Changes

This appendix describes the changes in each version.

J.1 Changes in version 10-50

Note: The list below includes functions that are supported from the 10-10 release to the 10-50 release.

The following operating system is now supported:

Windows Server 2012 R2

The monitoring suspension function is now supported.

The quickGuideHideReportIcon item was added to the initialization file (config.xml).

The historical data collection priority function is now supported. This function prioritizes the collection of historical data over the display of real-time reports.

The data acquisition date and time is now displayed in the Process Monitoring Settings > Create a New Application Definition > Add from Running Processes window.

A function for putting the execution of alarm commands on hold is now supported.

The following commands were added:

jpcconf acc display

jpcconf acc setup

jpcconf acc unsetup

jpcparamdump

jpctool monitor list

jpctool monitor resume

jpctool monitor status

jpctool monitor suspend

Output examples and parameter file examples for the following commands were changed to correspond to version 0110:

jpcasrec output

jpcasrec update

The tag realtime-report-data-collection-mode was added for the parameter file of the jpcasrec update command.

A description of monitoring suspension was added for the following commands:

jpcconf ha setup

jpcconf ha unsetup

jpcconf hc enable

jpctool alarm active

A description of real-time reports was added for the following command:

jpcrpt

The -wait option was added for the following commands:

jpctool alarm active

jpctool alarm bind

jpctool alarm check

jpctool alarm copy

jpctool alarm delete

jpctool alarm export

jpctool alarm import

jpctool alarm inactive

jpctool alarm list

jpctool alarm unbind

The following PFM - Manager messages were added:

KAVE00252-E to KAVE00255-E, KAVE00258-E to KAVE00262-E, KAVE00487-I, KAVE00493-E, KAVE00500-W to KAVE00512-I, KAVE00515-W to KAVE00523-E, KAVE00525-W to KAVE00529-E, KAVE00531-E to KAVE00532-W, KAVE04902-E, KAVE05470-E to KAVE05492-I, KAVE05971-E to KAVE05974-E, KAVE06171-E to KAVE06178-E, KAVE06180-I to KAVE06194-I, KAVL15105-W

The following PFM - Web Console messages were added:

KAVJJ8577-Q to KAVJJ8579-Q, KAVJK2563-E to KAVJK2568-E, KAVJK4002-E, KAVJK6522-I, KAVJK6523-I, KAVJS2541-E to KAVJS2549-E, KAVJS2640-E, KAVJS2663-E to KAVJS2667-E, KAVJS4017-E, KAVJS4018-E, KAVJS6569-I, KAVJS6570-I

The following PFM - Manager messages were changed:

KAVE00398-W, KAVE05415-E, KAVE06158-E, KAVE06161-E

The following PFM - Web Console messages were changed:

KAVJK2559-E, KAVJS2530-E, KAVJS2604-E, KAVJS2607-E, KAVJS2629-E, KAVJS2702-E, KAVJS5001-I

Regarding the dispersion of the reconnection, the Random Retry Mode label was added to Common Section in the startup information file (jpccomm.ini).

Regarding the synchronous execution controller for actions, Action Handler Section was added to the startup information file (jpccomm.ini).

J.2 Changes in version 10-10

The following operating systems are now supported:

Red Hat Enterprise Linux(R) Server 5 (32-bit x86)

Red Hat Enterprise Linux(R) Server 5 (64-bit x86_64)

Operating status monitoring for instances is now supported.

The following commands were added:

jpcconf primmgr notify, jpctool config mgrexport, jpctool config mgrimport, jpctool config sync

Notes were added for the following commands:

jpcconf agttree import, jpcconf bgdef delete, jpcconf bgdef import, jpcconf mgrhost define, jpcconf stat disable, jpcrdef create, jpcrdef delete, jpctool alarm active, jpctool alarm bind, jpctool alarm check, jpctool alarm copy, jpctool alarm delete, jpctool alarm export, jpctool alarm import, jpctool alarm inactive, jpctool alarm unbind

A description of multiple monitoring was added for the return value 5 of the following commands:

jpctool alarm active, jpctool alarm bind, jpctool alarm copy, jpctool alarm delete, jpctool alarm import, jpctool alarm inactive, jpctool alarm unbind, jpcconf agttree import, jpcconf bgdef delete, jpcconf bgdef import

The return value 12 was added for the following commands:

jpcrdef create, jpcrdef delete

The return value 13 was added for the following commands:

jpctool alarm bind, jpctool alarm import

The return value 254 was added for the jpcconf mgrhost display command.

Format 2 and examples 3 to 5 were added for the jpcconf mgrhost define command.

Example 3 of the jpctool alarm export command was changed.

The Notify State label was added to the format of the alarm definition file for the jpctool alarm import command.

The following PFM - Manager messages were added:

KAVE00232-W, KAVE00479-I, KAVE00480-W, KAVE00481-I, KAVE00483-E, KAVE00485-W, KAVE05969-E, KAVE05970-E, KAVE06117-I, KAVE06118-I, KAVE06119-E, KAVE06120-I, KAVE06121-W, KAVE06122-W, KAVE06131-E, KAVE06132-I, KAVE06133-I, KAVE06134-W, KAVE06135-E, KAVE06136-I, KAVE06137-I, KAVE06138-E, KAVE06139-I, KAVE06140-I, KAVE06141-E, KAVE06142-E, KAVE06143-I, KAVE06144-I, KAVE06145-I, KAVE06146-E, KAVE06147-I, KAVE06148-I, KAVE06149-E, KAVE06150-I, KAVE06151-W, KAVE06152-E, KAVE06154-E, KAVE06155-E, KAVE06157-E, KAVE06158-E, KAVE06159-E, KAVE06160-E, KAVE06161-E

The following PFM - Web Console messages were added:

KAVJK2562-E, KAVJS2673-E, KAVJS2674-E, KAVJS2675-E, KAVJS2676-E, KAVJS4016-E, KAVJS6705-I

The following PFM - Manager messages were changed:

KAVE00213-W, KAVE05343-E, KAVE05349-E

The following PFM - Web Console messages were changed:

KAVJK2506-E, KAVJK2553-E, KAVJS2532-E, KAVJS2574-E, KAVJS2623-E, KAVJS2835-E, KAVJS4007-E, KAVJT2508-E, KAVJT6502-I

Details were added about definition information verification performed by using the jpctool config mgrimport command.

J.3 Changes in version 10-00

The following operating systems are no longer supported:

HP-UX 11i V2 (IPF)

Solaris 9 (SPARC)

Solaris 10 (x64)

Solaris 10 (x86)

AIX 5L V5.3

Red Hat Enterprise Linux(R) AS 4 (AMD64 & Intel EM64T)

Red Hat Enterprise Linux(R) AS 4 (IPF)

Red Hat Enterprise Linux(R) AS 4 (x86)

Red Hat Enterprise Linux(R) ES 4 (AMD64 & Intel EM64T)

Red Hat Enterprise Linux(R) ES 4 (x86)

Red Hat Enterprise Linux(R) 5 (AMD/Intel 64)

Red Hat Enterprise Linux(R) 5 (IPF)

Red Hat Enterprise Linux(R) 5 (x86)

Red Hat Enterprise Linux(R) 5 Advanced Platform (AMD/Intel 64)

Red Hat Enterprise Linux(R) 5 Advanced Platform (IPF)

Red Hat Enterprise Linux(R) 5 Advanced Platform (x86)

The following operating systems are now supported:

Linux 6 (x64)

Linux 6 (x86)

JP1/Performance Management can now link with JP1/IT Service Level Management.

Performance data can now be collected in IPv6 environments.

You can now specify filter conditions when searching from a window.

Limits now apply to the process that refines on-screen information based on keywords.

Preview items in the following windows have been added.

Quick Guide > Create Alarm window

New Alarm > Main window

Edit > Main window

New Alarm > Action Definition > JP1 Event window

Edit > Action Definition > JP1 Event window

Data group buttons have been added that you can use to navigate to the previous or next time band of a report.

A list of windows that can be displayed from each window has been added.

A description of the configuration component icons has been added.

The following windows have been added:

About window

List of Selected Agents window

Baseline window

Description of Record and Fields window

Bookmark (the folder name entry) window

Input Using Application Definition Template window for Application definition templates

Add from Running Processes window, Add from Running Processes (Command Lines) window, and Add from Services window for Application definition templates

The View Summary window has been changed to the System Operational Status Summary window.

The following commands have been added:

jpcconf ipv6 disable, jpcconf ipv6 display, jpcconf ipv6 enable

Notes on the following commands have been added:

jpcspm start, jpcspm stop, jpctool alarm active, jpctool alarm bind, jpctool alarm check, jpctool alarm copy, jpctool alarm delete, jpctool alarm export, jpctool alarm import, jpctool alarm inactive, jpctool alarm list, jpctool alarm unbind, jpctool db backup, jpctool db dump, jpctool service list

Notes on when the -mx option and -ms option are specified for the following commands have been added:

jpcaspsv output, jpcaspsv update, jpcasrec output, jpcasrec update, jpcmkkey, jpcrdef create, jpcrdef delete, jpcrdef output

The following messages have been added:

KAVE00250-W, KAVE00251-W, KAVE00323-W, KAVE00344-E to KAVE00360-I, KAVE00363-W to KAVE00381-E, KAVE00390-E to KAVE00448-E, KAVE00451-E to KAVE00454-E, KAVE05399-I to KAVE05410-W, KAVE05412-E to KAVE05460-I, KAVE05956-I to KAVE05961-E, KAVE06069-E, KAVE06071-I to KAVE06098-E, KAVJA2501-E, KAVJF2501-E, KAVJF2502-E, KAVJJ6611-I, KAVJJ6612-I, KAVJJ8603-Q to KAVJJ8605-Q, KAVJK2512-E to KAVJK2514-E, KAVJK2515-E, KAVJK2516-E, KAVJK2519-E to KAVJK2522-E, KAVJK2525-E, KAVJK2527-E to KAVJK2531-E, KAVJK2533-E, KAVJK2535-E to KAVJK2538-E, KAVJK2543-E to KAVJK2554-E, KAVJK2557-E, KAVJK2559-E to KAVJK2561-E, KAVJK6503-I to KAVJK6506-I, KAVJK6511-I, KAVJK6512-I, KAVJK6514-I, KAVJK6516-I, KAVJK6518-I to KAVJK6521-I, KAVJK8604-Q, KAVJK8605-Q, KAVJK8609-Q, KAVJS2511-E to KAVJS2517-E, KAVJS2519-E, KAVJS2522-E to KAVJS2540-E, KAVJS2608-E, KAVJS2612-E to KAVJS2624-E, KAVJS2628-E to KAVJS2639-E, KAVJS2662-E, KAVJS2672-E, KAVJS2700-E, KAVJS2837-E to KAVJS2840-E, KAVJS4013-E to KAVJS4015-E, KAVJS6566-I, KAVJS6567-I, KAVJS6561-I to KAVJS6563-I, KAVJS6564-I, KAVJS6704-I, KAVJV2552-E to KAVJV2564-E, KAVJV9004-K, KAVJV9502-K, KAVL15014-W to KAVL15022-E

The following messages have been changed:

KAVE00104-E, KAVE00162-E, KAVE00182-E, KAVE05015-E, KAVE05181-E to KAVE05183-E, KAVE05240-E, KAVE05304-E, KAVJK0301-E, KAVJK0302-E, KAVJK0401-E, KAVJK2501-E, KAVJK2502-E, KAVJK2711-E, KAVJS0027-E, KAVJS2559-E, KAVJS2560-E, KAVJS2573-E to KAVJS2577-E, KAVJS2604-E, KAVJS2690-E, KAVJS2751-E, KAVJS2830-E, KAVJS2831-E, KAVJS2834-E to KAVJS2836-E, KAVJS5001-I

The following messages have been deleted:

KAVE00245-W, KAVJS2525-E, KAVJV9003-K

The event log output message information for the following messages has been added:

KAVE00344-E to KAVE00347-E, KAVE06083-E, KAVE06097-E, KAVJV2552-E to KAVJV2564-E

A description of firewall penetration directions has been added and changes have been made.

The list of files and directories has been changed.

The settings items in the initialization file (config.xml) have been changed.

The start time and end time can now be hidden when displaying a report.

The following message text is now output as an agent event depending on the results of a check of the agent alarm status:

State change(Unconfirmed)

State information

State information(Unconfirmed)

The following message text is now output as an agent event related to the operating status of the monitored system:

Monitored System Available

Monitored System Unavailable

The trigger for issuing alarm events whose message text is Alarm Cleared has been changed.

An access control feature based on business groups has been added, allowing you to set the range of information individual users can monitor.

The jpctool service sync command can now be used to synchronize the service information registered in PFM - Manager and PFM - Web Console.

Business group ordinary user has been added as a user permission for Performance Management.

The autolabel feature can now display tooltips that show data values plotted on a graph.

The user-created alarm table can now be displayed as a separate tree from the table of alarms defined by monitoring templates.

In the Edit Agents > New Agents window, you can now use keywords to refine the list of agents.

Process Monitoring Settings > Save an Application Definition Template window has been added.

The interruption method at the data missing part of a graph has been changed.

When a series group contains 3D clustered column/3D stacked column graphs or line graphs, any group can now be displayed in the foreground regardless of the order of the series groups.

The sequence in which the Y axis scales are displayed in combination reports now conforms to the order in which the graphs are drawn.

The following conditions regarding combination reports have been added or changed:

The conditions under which some or all of a graph or legend is invisible and the legend breaks over two or more lines

The conditions under which part of the legend is invisible due to an excessive number of characters

The conditions under which the series group name overlaps the legend

The conditions under which a line break appears in the graph title

Process monitoring can now be set by using the following commands:

jpcprocdef create

Creates and edits an application definition.

jpcprocdef delete

Deletes an application definition.

jpcprocdef list

Displays a list of application definition names.

jpcprocdef output

Outputs the definition information of an application definition.

Accordingly, files and directories that these commands use have been added.

You can now use the following commands to create and edit business groups:

jpcconf bgdef check

Verifies the contents of a business group definition file.

jpcconf bgdef delete

Deletes definition information for a business group.

jpcconf bgdef display

Displays definition information for a business group.

jpcconf bgdef export

Exports definition information for a business group to a file.

jpcconf bgdef import

Imports definition information for a business group from a file.

jpcconf bgdef list

Displays a list of business group names.

The command return value (10) has been deleted.

A recovery procedure for when a command execution failed has been added.

Windows firewall information is now part of the troubleshooting information collected in a Windows environment.

Hosts operated from commands can now be restricted by using the following options:

Option for restricting Agent host remote operation

Option for restricting the viewing of service information from Agent hosts

The maximum number of alarms you can define in one alarm table has been increased from 50 to 250. Accordingly, the maximum number of alarms you can define in one alarm definition file has been increased from 50 to 250.

Backup data that can be deleted if it is unnecessary has been specified.

The following setting items have been added to the initialization file (config.xml):

alarmCompatibleMode, displayAlarmTablesSeparately, maxMonitorEventNumForMultiTenant, color1 to color16, noUseCircleColor, lineSymbolSize, legendSeriesOrderForHBar, autoLabelMaxIntegerDigits, autoLabelMaxFractionDigits, maxAutoLabelPoints, foregroundCombinationGraph, precision, appendCommaDisplayedForNum, cmdRptBookmarkNameDecodeOnce, enableAutoLabelAtDefaultDisp, selectAHModeForJP1Event, useReportCacheFile, reportCacheFileDir, usingSeriesPagingOnTheGraph, processMonitoringTemplatesRepository, agentTreeAccessLimit, printCacheSize, displayLegendCount, graphMaxReportData, printTableMaxRowSize, cmdHtmlTableOutputMaxRowSize, maxDrilldownPoints

The following labels have been added to the startup information file (jpccomm.ini):

Correlator Startup Mode in the Common Section

Retry Getting Alarm Status in Common Section

Business Group Monitor Mode in Common Section

Agent Remote Protection in Common Section

Service List Protection in Common Section

NS Init Retry Count in Agent Collector x Section

NS Init Retry Count in Agent Store x Section

When monitoring alarms using multi instance records, users can now be notified when the value of a field returns to a normal range.

Reports can now be displayed over several pages when there are too many graph legends.

Process monitoring in PFM - Agent for Platform and PFM - RM for Platform can now be configured in the Agents tree.

The OK button has been removed from the Service Properties window, and Finish and Apply buttons have been added.

The following commands can now be used to create and edit the Agents tree.

jpcconf agttree export

Exports an Agents tree definition file.

jpcconf agttree import

Imports an Agents tree definition file.

The setup command can now be executed in non-interactive mode.

The message sent when a JP1 event is issued can now be defined within a range from 0 to 1,023 bytes.

Parameters to be specified in the input file of the jpcrpt command have been added:

The information cached to memory when displaying reports can now be output to a file.

Files backed up when the Store version is 2.0 have been specified.

The maximum number of httpsd processes of PFM - Web Console has been changed.

You can now choose how the system determines which Action Handler service is selected by default in the New Alarm > Action Definition window and Edit > Action Definitions window of PFM -Web Console when issuing a JP1 event.

You can now limit the information available to users with general user permission in the Agents tree.

The maximum number of lines of table data displayed in the Print window and in HTML reports can now be restricted.

The maximum number of drilldown data items in a graph can now be restricted.

A description about the startup information file (jpccomm.ini) has been added.

J.4 Changes in version 09-00

The following program product has been added to Performance Management products to support remote monitoring:

PFM - RM

Accordingly, the jpcconf target command has been added.

The PFM - RM service, remote agents, and group agents can be operated on the monitoring console.

An event that occurs on a Performance Management service can be notified with a JP1 event or agent event. Accordingly, the following folder has been added to the list of properties of the Agent Collector service of the health check agent.

JP1 Event Configurations

The product name display function has been added, enabling service keys and service IDs to be displayed and specified in a new format. Accordingly, the jpcconf prodname command has been added. In addition, the argument -v for displaying the services by their product names has been added to the jpctool service list command.

New format commands that are compatible with commands earlier than version 08-11 have been added. In addition, the option formats have been unified.

Concurrent login by the same user can be controlled. Accordingly, the enableDuplicateLogin parameter has been added to the initialization file (config.xml).

An overview of the entire system and of the latest service operating statuses can be monitored in the Display Summary window. Accordingly, the following parameters have been added to the initialization file (config.xml):

maxDisplayServer

maxDisplayAgentsUser

maxDisplayAgentsProducts

maxDisplayAlarm

maxEvents

The tiling display function has been added, enabling multiple historical report graphs to be displayed as thumbnail images. Accordingly, the maxTileReports parameter has been added to the initialization file (config.xml).

The field search function has been added, enabling a search of monitored items with the keyword being information that the user wants to set when setting alarms and reports. Accordingly, the searchLimit parameter has been added to the initialization file (config.xml).

The quick guide function has been added, enabling reports to be displayed without executing the conventional report definition procedure. In addition, the alarm definition procedure has been simplified.

Display report definitions can be edited from the View Report window.

The procedure for changing the host name of a host running a Performance Management product has been simplified. Accordingly, the jpcconf host command has been added.

Startup and termination of the PFM - Manager, PFM - Base, and PFM - Web Console services can be linked using the jpcspm command.

The argument -force, which forcibly deletes service information, has been added to the jpctool service delete command.

The argument -key for using a service key to specify the service whose information you want to display has been added to the jpctool service list command.

The argument -immediate that forcibly terminates a service has been added to the jpcwstop command.

You can now control whether a general user can operate report definitions and bookmarks by setting the editReportByOrdinaryUser parameter of the initialization file (config.xml).

Windows Server 2008 is now supported.

A report's graph images can be time-corrected and displayed by setting the graph-time-collection parameter of the initialization file (config.xml).

The scale on the vertical axis of a graph can be displayed in exponential form.

Multiple alarm tables can be bound to a monitoring agent.

PFM - Web Console can be used in a UNIX environment.

Setup of Performance Management has been simplified.

An alarm table can be additionally bound using the jpcalarm bind command.

A list of the alarm tables bound by an agent can be displayed using the jpcalarm list command.

All alarm tables bound to an agent can be unbound using the jpcalarm unbind command.

The agent to which a report is output can be specified by the service ID of the Agent Collector service in the jpcrpt command.

The relative time from the command execution time can be specified as the child element of the corresponding tag in the parameter file for the jpcrpt command.

A storage folder for the property definition file and a storage folder for the data model description file have been added.

A PFM - Web Console service startup log file and a PFM - Web Console service termination log file have been added directly under /opt/jp1pcwebcon/log.

The check rule specified in the property definition file can be set in the parameters of the initialization file (config.xml).

firstDayOfWeek has been added to the parameters of the initialization file (config.xml).

The following messages have been added:

KAVE00217-I to KAVE00219-E, KAVE00233-E, KAVE00234-I to KAVE00245-W, KAVE00311-E to KAVE00316-E, KAVE00317-W to KAVE00319-W, KAVE00320-I to KAVE00321-I, KAVE00322-W, KAVE00324-W, KAVE00325-I to KAVE00327-I, KAVE00328-E to KAVE00332-E, KAVE00333-E to KAVE00339-E, KAVE00342-I, KAVE00343-I, KAVE05166-I to KAVE05192-E, KAVE05037-E, KAVE05351-E, KAVE05352-E, KAVE05353-W, KAVE05354-E, KAVE05355-I, KAVE05356-E, KAVE05357-I, KAVE05358-E, KAVE05359-I, KAVE05360-E, KAVE05361-I to KAVE05397-E, KAVE05882-E, KAVE05883-W, KAVE05944-W, KAVE05945-E, KAVE05946-I, KAVE05947-I, KAVE05948-E to KAVE05950-E, KAVE05951-W, KAVE05952-I, KAVE05953-I, KAVE05954-E to KAVE05955-E, KAVE06040-E, KAVE06041-E, KAVE06046-W, KAVE06047-I to KAVE06066-E, KAVJH2501-E to KAVJH2504-E, KAVJJ2552-E, KAVJJ5001-I, KAVJJ8552-Q to KAVJJ8555-Q, KAVJJ8571-Q to KAVJJ8576-Q, KAVJJ8654-Q to KAVJJ8661-Q, KAVJK2501-E to KAVJK2508-E, KAVJK2750-E to KAVJK2760-E, KAVJS2589-E to KAVJS2600-E, KAVJS2683-E to KAVJS2699-E, KAVJS2835-E, KAVJS2836-E, KAVJS6702-I, KAVJS6553-E to KAVJS6560-I, KAVJS6703-I, KAVJT0023-E, KAVL15013-E

The following messages have been changed:

KAVE00104-E, KAVE00181-W, KAVE00330-E, KAVE05000-E, KAVE05019-E, KAVE05213-E, KAVE05288-W, KAVE06035-E, KAVE06036-W, KAVJJ8602-Q, KAVJK2714-E, KAVJT0004-E, KAVJZ5999-E

The following messages have been deleted:

KAVE00112-E, KAVE00129-E, KAVE05903-E, KAVE05907-I, KAVJT0006-E

The descriptions of the following messages have been changed:

KAVE00331-E, KAVE00332-E, KAVE05948-E, KAVJS0012-E, KAVJT0003-E

J.5 Changes in version 08-11

As a result of support of the health check function, the operating statuses of the monitoring agent and the host on which the monitoring agent runs can be checked.

The tree view display in PFM - Web Console has been improved.

A window for printing or saving reports has been added to PFM - Web Console.

Properties specific to PFM - Agent can be batch-distributed.

Registered reports that are currently bookmarked and combination reports that are currently combination-bookmarked can be output from a command.

A timeout period can be specified for initiating automatic logout when a certain time has elapsed without user actions or automatic refresh being performed.

Bookmarks can be registered from the tree in the Agents window.

Reports and Bookmarks are available as options in the Tree type text box in the Select Reports window.

Baselines can be registered from the View Report window.

Reports can be overlaid when they are displayed.

Report properties can be displayed from the Reports window.

Combination bookmarks can be registered and edited from the Bookmarks window.

Bound agents can be displayed from the Alarms window.

Agent properties can be distributed from the Services window.

Store 2.0 is supported.

Bookmarks and combination bookmarks can be specified as drilldown destinations of reports.

The jpcrpt command can be used to output reports in HTML format.

The following messages have been added or changed:

Added messages

KAVE00216-E, KAVE00220-E, KAVE00221-W, KAVE00222-W, KAVE00223-E, KAVE00224-E, KAVE00225-E, KAVE00226-E, KAVE00227-W, KAVE00228-I, KAVE00229-E, KAVE00230-E, KAVE00231-W, KAVE05342-W, KAVE05343-E, KAVE05344-E, KAVE05345-E, KAVE05346-I, KAVE05347-I, KAVE05348-E, KAVE05349-E, KAVE05350-W, KAVE05835-I, KAVE05836-I, KAVE05837-E, KAVE05838-I, KAVE05839-I, KAVE05840-E, KAVE05841-I, KAVE05842-I, KAVE05843-E, KAVE05844-I, KAVE05845-I, KAVE05846-E, KAVE05847-I, KAVE05848-I, KAVE05849-E, KAVE05852-I, KAVE05853-E, KAVE05854-I, KAVE05855-E, KAVE05856-I, KAVE05857-E, KAVE05858-I, KAVE05859-E, KAVE05860-E, KAVE05861-E, KAVE05862-E, KAVE05863-E, KAVE05864-E, KAVE05865-E, KAVE05867-E, KAVE05868-E, KAVE05871-E, KAVE05873-E, KAVE05873-Q, KAVE05874-Q, KAVE05875-E, KAVE05876-E, KAVE05877-E, KAVE05878-E, KAVE05879-E, KAVE05880-E, KAVE05881-E, KAVJJ2551-E, KAVJJ-8016-I, KAVJJ8551-Q, KAVJK2715-E, KAVJK2716-E, KAVJK2717-E, KAVJK2718-E, KAVJK2719-E, KAVJK2720-E, KAVJK2721-E, KAVJK2722-E, KAVJK2723-E, KAVJK2724-E, KAVJK2725-E, KAVJK2726-E, KAVJK2727-E, KAVJK2728-E, KAVJK2729-E, KAVJK2730-E, KAVJK2731-E, KAVJK2732-E, KAVJK2733-E, KAVJK2736-E, KAVJS0068-E, KAVJS0069-E, KAVJS2583-E, KAVJS2584-E, KAVJS2585-E, KAVJS2586-E, KAVJS2587-E, KAVJS2588-E, KAVJS2607-E, KAVJS2834-E, KAVJS5003-I, KAVJV2501-E, KAVJV2502-E, KAVJV2503-E, KAVJV2504-E, KAVJV2505-E, KAVJV2506-E, KAVJV2507-E, KAVJV2551-E, KAVL15000-I, KAVL15001-I, KAVL15002-E, KAVL15003-E, KAVL15004-E, KAVL15005-W, KAVL15006-E, KAVL15007-W, KAVL15008-E, KAVL15009-E, KAVL15010-E, KAVL15011-E, KAVL15012-E, KAVL15100-E, KAVL15101-E, KAVL15102-E, KAVL15103-E, KAVL15104-E

The output destinations of the following messages have been changed:

KAVE06022-I, KAVE06023-E, KAVE06024-E

Changed messages

KAVE00105-E, KAVE00138-E, KAVE00171-E, KAVE05018-E, KAVE05138-E, KAVE05848-I, KAVE06022-I, KAVJS0001-E, KAVJS0034-E, KAVJS0056-E, KAVJS2604-E, KAVJS2607-E, KAVJS4012-E

PFM - Base has been added as the core program for monitoring.

PFM - Web Console has been added as a monitoring console server program.

The following change to the operating systems supported for PFM - Manager has been made:

Name of program

Revision

PFM - Manager

Windows Server 2000 has been removed.

The jpcalarm active command (that enables disabled alarms) has been added.

The jpcalarm bind command (that binds an alarm table to an agent) has been added.

The jpcalarm check command (that checks the syntax of alarm definition files and the validity of defined information) has been added.

The jpcalarm copy command (that copies an alarm table or an alarm) has been added.

The jpcalarm delete command (that deletes an alarm table or an alarm) has been added.

The jpcalarm export command (that exports alarm definition files) has been added.

The jpcalarm import command (that imports alarm definition files) has been added.

The jpcalarm inactive command (that disables enabled alarms) has been added.

The jpcalarm list command (that displays alarm table definition information) has been added.

The jpcalarm unbind command (that unbinds alarm tables) has been added.

The jpcaspsv output command (that outputs definition information for the Store database storage condition) has been added.

The jpcaspsv update command (that changes definition information for the Store database storage condition) has been added.

The jpcasrec output command (that outputs definition information for the Store database recording method) has been added.

The jpcasrec output command (that changes definition information for the Store database recording method) has been added.

The jpcmkkey command (that creates an authentication key file required in order to execute commands at PFM - Web Console) has been added.

The jpcwagtsetup command (that registers a new PFM - Agent into PFM - Web Console) has been added.

The jpcwras command (that collects information about PFM - Web Console) has been added.

The jpcwstart command (that starts the PFM - Web Console service) has been added.

The jpcwstop command (that stops the PFM - Web Console service) has been added.

The jpcrdef create command (that registers new report definitions) has been added.

The jpcrdef delete command (that deletes existing report definitions) has been added.

The jpcrdef output command (that outputs existing report definition information) has been added.

The jpcrpt command (that outputs a report displayed on PFM - Web Console to a CSV-format batch report) has been added.

The -direct and -alone arguments have been added to the jpcctrl backup command.

The -direct and -alone arguments have been added to the jpcctrl dump command.

The -stat argument has been added to the jpcctrl list command. For versions that support the status management function, this command can now be used to check service status details.

stat has been added as a service key that can be specified in the jpcnsconfig port command.

stat has been added as a service key that can be specified in the jpcras command.

stat has been added as a service key that can be specified in the jpcstart command.

stat has been added as a service key that can be specified in the jpcstop command.

The jpcstsetup disable command (that disables the status management function) has been added.

The jpcstsetup display command (that displays the status of the status management function) has been added.

The jpcstsetup enable command (that enables the status management function) has been added.

The jpcras command can now be used to collect Windows event log.

Messages have been added and changed.

K. Reference Material for This Manual

The reference material for readers of this manual is described in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

L. Glossary

Terminology used in this manual

See the glossary in the appendixes of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Index

A

About window[1]

Active Setting window[1]

additional setup[1]

agent

Service Properties window[1]

Agents tree

creating and updating[1]

exporting definition information to file[1]

Agents window[1]

alarm[1], [2]

copying[1]

deleting[1]

disabling[1]

enabling[1]

alarm definition

exporting to specified file[1]

Alarm Status window[1]

Alarms window[1]

alarm table

binding to agent[1]

copying[1]

deleting[1]

unbinding[1]

alarm table and alarm

defining and updating[1]

Alarm Table Bind Settings [Select Alarm Tables] window[1]

application definition file

format[1]

application definitions

deleting[1]

editing[1]

exporting[1]

listing[1]

setting[1]

B

backup data

displaying information[1]

backup file

creating[1]

Bind Alarm Table [Select Alarm Tables] window[1]

binding

alarm table to agent[1]

bookmark

meaning defined[1]

bookmarks tree

Properties window[1]

Bookmarks window[1]

business group definition file

checking contents[1]

business groups

deleting definition information[1]

displaying definition information[1]

exporting definition information[1]

importing definition information[1]

listing names[1]

C

Change Password window[1]

changing

host name of PFM - Manager host for connection destination[1]

settings of Store Service[1]

checking

business group definition file[1]

collecting

OS information[1]

collecting data about PFM - Web Console[1]

combination report

baseline display period[1]

drawing sequence of graph[1]

horizontal axis (x axis)[1]

number of fields[1]

series group setting[1]

vertical axis (y axis)[1]

Combination Report window[1]

Properties page[1]

Show Options page[1]

View report page[1]

command installation directories[1]

commands[1]

concurrent execution[1]

creating logical host environment[1]

deleting logical host environment[1]

disabling status management function[1]

displaying settings for logical host environment[1]

enabling status management function[1]

exporting settings of logical host environment[1]

importing logical host environment definition file[1]

input method[1]

jpctool alarm commands[1]

new commands and old commands[1]

notations used in syntax explanation[1]

notes (PFM - Web Console)[1]

notes common to all[1]

output method[1]

prerequisites for execution[1]

re-registering service information[1]

sending JP1 event[1]

specification method[1]

specification method and notations used in explaining syntax[1]

starting services[1]

stopping services[1]

supported DTD file[1]

config.xml[1], [2]

config.xml (other settings)[1]

config.xml (setting automatic logout)[1]

config.xml (settings for acquiring and displaying data)[1]

config.xml (setting up communication with View Server service)[1]

configuration component

agent[1]

folder[1]

group agent[1]

remote agent[1]

Remote Monitor Collector service[1]

root[1]

conventions

fonts and symbols[1]

mathematical expressions[1]

meaning of bookmark[1]

version numbers[1]

converting

data model[1]

copying

alarm table or alarm[1]

Copy window

Copy > Input Name [Alarm Table] window[1], [2]

Reports[1]

Users[1]

Correspondence between new commands and old commands[1]

creating

Agents tree[1]

backup file[1]

instance environment[1]

key file for authentication[1]

new report definition[1]

D

data

erasing[1]

exporting[1]

database data

restoring[1]

Data Group button[1]

data model

converting[1]

defining

alarm table and alarm[1]

definition file

format (jpcconf inst setup command)[1]

format (jpcconf port define command)[1]

format (jpcconf target setup command)[1]

definition information

checking definition information[1]

importing[1]

deleting

alarm table or alarm[1]

application definitions[1]

business group definition information[1]

instance environment[1]

service information for agent[1]

deleting report definition[1]

difference of displayed items among report types[1]

disabling

enabled alarm[1]

health check function[1]

IPv6 usage settings[1]

JP1/IM monitored object linkage function[1]

displaying

all host names of PFM - Manager hosts for connection destinations (Name Server services)[1]

bind information of alarm tables and alarms[1]

business group definition information[1]

definitions of alarm tables and alarms[1]

information about Store service or backup data[1]

instance names [1]

IPv6 usage settings[1]

port numbers[1]

service configuration and status[1]

settings for logical host environment[1]

settings of Store Service[1]

status of health check function[1]

status of status management function[1]

displaying definitions or bind information

alarm table and alarm[1]

Display Reports > Select Report window[1]

Display Summary window[1]

Agent Alarm Status area[1]

Agent Operational Status area[1]

Server Operational Status area[1]

Distribute Property > Progress Reports window[1]

Distribute Property > Select Property window[1]

Distribute Property > Select Property window (distributing properties whose nodes change their numbers)[1]

Distribute Property > Select Service window[1]

Distribute Property window[1]

DTD file[1]

E

Edit > Action > Select a report window[1]

Edit > Action Definitions > JP1 Event Settings window[1]

Edit > Action Definitions window[1]

Edit > Action window[1]

Edit > Alarm Conditions > Search Fields window[1]

Edit > Alarm Conditions window[1]

Edit > Components window[1]

Edit > Drilldown > Select Report > Edit Conditional Expression for Drilldown window[1]

Edit > Drilldown > Select Report window[1]

Edit > Drilldown window[1]

Edit > Field > Search Fields window[1]

Edit > Field window[1]

Edit > Filter window[1]

Edit > Graph window[1]

Edit > Indication Settings (Historical) window[1]

Edit > Indication Settings (Realtime) window[1]

Edit > Indication Settings window[1]

Edit > Main Information window[1]

Edit > Name and Type window[1]

Edit Agent Tree > Copy [Select Copy Place] window[1]

Edit Agent Tree > New Agent window[1]

Edit Agent Tree > New Folder window[1]

Edit Agent Tree > Rename window[1]

Edit Agent Tree window[1]

editing application definitions[1]

Edit window (Bookmarks)[1]

Edit window (Users)[1]

enabling

disabled alarm[1]

health check function[1]

IPv6 usage settings[1]

JP1/IM monitored object linkage function[1]

Environment Settings window[1]

erasing

data[1]

Event History window[1]

Show Options page[1]

View report page[1]

event log, Windows[1]

list of[1]

Event Monitor window[1]

Show Options page[1]

View report page[1]

Event page[1]

exporting

Agents tree definition information to file[1]

alarm definitions to specified file[1]

application definitions[1]

business group definition information[1]

data[1]

F

files and directories[1]

for PFM - Agent or PFM - RM[1]

for PFM - Base (in UNIX)[1]

for PFM - Base (in Windows)[1]

for PFM - Manager (in UNIX)[1]

for PFM - Manager (in Windows)[1]

for PFM - Web Console (in UNIX)[1]

for PFM - Web Console (in Windows)[1]

firewall

penetration directions[1]

font conventions[1]

format

application definition file[1]

G

glossary[1]

H

health check function

disabling[1]

displaying status[1]

enabling[1]

Help window[1]

historical report[1], [2]

I

identifiers[1]

importing[1]

business group definition information[1]

Import window

Alarms[1]

Reports[1]

information frame (Agents)[1]

information frame (Alarms)[1]

information frame (Bookmarks)[1]

information frame (Main)[1]

information frame (Reports)[1]

information frame (Services)[1]

information frame (Users)[1]

information output by the jpcparamdump command[1]

initialization file

config.xml[1]

example (config.xml)[1]

installation directories[1]

IPv6 usage settings

disabling[1]

displaying[1]

enabling[1]

J

JP1/IM monitored object linkage function

disabling[1]

enabling[1]

JP1 event, sending[1]

jpcaspsv output command[1]

jpcaspsv update command[1]

jpcasrec output command[1]

jpcasrec update command[1]

jpccfgbackup command[1]

jpcconf acc display command[1]

jpcconf acc setup command[1]

jpcconf acc unsetup command[1]

jpcconf agent setup command[1]

jpcconf agttree export command[1]

jpcconf agttree import command[1]

jpcconf bgdef check command[1]

jpcconf bgdef delete command[1]

jpcconf bgdef display command[1]

jpcconf bgdef export command[1]

jpcconf bgdef import command[1]

jpcconf bgdef list command[1]

jpcconf db define command[1]

jpcconf db display command[1]

jpcconf db vrset command[1]

jpcconf ha export command[1]

jpcconf ha import command[1]

jpcconf ha list command[1]

jpcconf ha setup command[1]

jpcconf ha unsetup command[1]

jpcconf hc disable command[1]

jpcconf hc display command[1]

jpcconf hc enable command[1]

jpcconf host hostmode command[1]

jpcconf host hostname command[1]

jpcconf im disable command[1]

jpcconf im enable command[1]

jpcconf inst list command[1]

jpcconf inst setup command[1]

jpcconf inst unsetup command[1]

jpcconf ipv6 disable command[1]

jpcconf ipv6 display command[1]

jpcconf ipv6 enable command[1]

jpcconf mgrhost define command[1]

jpcconf mgrhost display command[1]

jpcconf ov disable command[1]

jpcconf ov enable command[1]

jpcconf port define command[1]

jpcconf port list command[1]

jpcconf primmgr notify command[1]

jpcconf prodname disable command[1]

jpcconf prodname display command[1]

jpcconf prodname enable command[1]

jpcconf stat disable command[1]

jpcconf stat display command[1]

jpcconf stat enable command[1]

jpcconf target display command[1]

jpcconf target list command[1]

jpcconf target setup command[1]

jpcconf target unsetup command[1]

jpcimevt command[1]

jpcmkkey command[1]

jpcparamdump command[1]

jpcprocdef create command[1]

jpcprocdef delete command[1]

jpcprocdef list command[1]

jpcprocdef output command[1]

jpcras command[1]

jpcrdef create command[1]

jpcrdef delete command[1]

jpcrdef output command[1]

jpcrpt command[1]

jpcspm start command[1]

jpcspm stop command[1]

jpctool alarm active command[1]

jpctool alarm bind command[1]

jpctool alarm check command[1]

jpctool alarm copy command[1]

jpctool alarm delete command[1]

jpctool alarm export command[1]

jpctool alarm import command[1]

jpctool alarm inactive command[1]

jpctool alarm list command[1]

jpctool alarm unbind command[1]

jpctool config mgrexport command[1]

jpctool config mgrimport command[1]

jpctool config sync command[1]

jpctool db backup command[1]

jpctool db clear command[1]

jpctool db dmconvert command[1]

jpctool db dump command[1]

jpctool db import command[1]

jpctool db restore command[1]

jpctool monitor list command[1]

jpctool monitor resume command[1]

jpctool monitor status command[1]

jpctool monitor suspend command[1]

jpctool service delete command[1]

jpctool service list command[1]

jpctool service register command[1]

jpctool service sync command[1]

jpcwagtsetup command[1]

jpcwbackup command[1]

jpcwras command[1]

jpcwstart command[1]

jpcwstop command[1]

K

key file for authentication

creating[1]

L

listing

application definition names[1]

business group names[1]

logical host environment

creating[1]

deleting[1]

displaying settings for[1]

exporting settings[1]

importing definition file[1]

LOGIF Expression Editor window[1]

log information[1]

Login window[1]

M

Main window[1]

Manuals describing various messages[1]

mathematical expressions

conventions[1]

menu bar frame (Main)[1]

message[1]

description format[1]

format[1]

output destinations[1]

output format[1]

output to syslog and Windows event log, list of[1]

type[1]

message log, common[1]

method frame (Agents)[1]

method frame (Alarms)[1]

method frame (Bookmarks)[1]

method frame (Main)[1]

method frame (Reports)[1]

method frame (Services)[1]

method frame (Users)[1]

Monitoring Suspension Settings > Change Settings window[1]

Monitoring Suspension Settings > Check Changes window[1]

Monitoring Suspension Settings > Check Results window[1]

Monitoring Suspension Settings window[1]

N

navigation frame (Agents)[1]

navigation frame (Alarms)[1]

navigation frame (Bookmarks)[1]

navigation frame (Main)[1]

navigation frame (Reports)[1]

navigation frame (Services)[1]

navigation frame (Users)[1]

New Alarm > Action > Select a report window[1]

New Alarm > Action Definitions > JP1 Event Settings window[1]

New Alarm > Action Definitions window[1]

New Alarm > Action window[1]

New Alarm > Alarm Conditions > Search Fields window[1]

New Alarm > Alarm Conditions window[1]

New Alarm > Main Information window[1]

New Folder window

Bookmarks[1]

Reports[1]

New Report > Components window[1]

New Report > Drilldown > Edit Conditional Expression for Drilldown window[1]

New Report > Drilldown > Select Report window[1]

New Report > Drilldown window[1]

New Report > Field > Search Fields window[1]

New Report > Field window[1]

New Report > Filter window[1]

New Report > Graph window[1]

New Report > Indication Settings (Historical) window[1]

New Report > Indication Settings (Realtime) window[1]

New Report > Indication Settings window[1]

New Report > Name and Type window[1]

New User window[1]

NNM linkage facility

setup[1]

unsetup[1]

notes

commands that are executed in PFM - Web Console[1]

executing jpctool alarm commands[1]

specifying host and lhost options in jpctool db command or jpctool service command[1]

O

operation status log[1]

OS information

collecting[1]

outputting report definition to file in XML format[1]

outputting report to file in CSV format or HTML format[1]

P

parameter file

format (jpcaspsv update command)[1]

format (jpcasrec update command)[1]

format (jpcrdef create command)[1]

format (jpcrdef delete command)[1]

format (jpcrdef output command)[1]

format (jpcrpt command)[1]

PFM - Agent

registering information in PFM - Web Console[1]

PFM - Agent information

automatically registered with PFM - Manager[1]

PFM - RM

registering information in PFM - Web Console[1]

PFM - RM information

automatically registered with PFM - Manager[1]

PFM - Web Console

changing port numbers[1]

collecting data[1]

notes on commands[1]

starting services[1]

stopping services[1]

PFM - Web Console, list of windows[1]

port number[1]

changing used in PFM - Web Console[1]

displaying[1]

Performance Management[1]

setting[1]

Print Reports window[1]

process[1]

Process Monitoring Settings window[1]

Process Monitoring Settings > Application Definition Templates window[1]

Process Monitoring Settings > Create a New Application Definition Template window[1]

Process Monitoring Settings > Create a New Application Definition window[1]

Process Monitoring Settings > Delete an Application Definition Template window[1]

Process Monitoring Settings > Delete an Application Definition window[1]

Process Monitoring Settings > Edit an Application Definition Template window[1]

Process Monitoring Settings > Edit an Application Definition window[1]

product ID[1]

Properties window

Alarms[1]

Properties window (bookmarks tree)[1]

Properties window (Reports)[1]

Q

Quick Guide > Create Alarm window[1]

Quick Guide > Search Fields window[1]

Quick Guide window[1]

R

realtime report[1], [2]

Register Bookmark window[1]

Bookmark (folder name entry) window[1]

Bookmark window[1]

Regist Bookmark > Select Report window[1]

registering

information about PFM - Agent or PFM - RM host (in PFM - Web Console)[1]

Rename window

Bookmarks[1]

Reports[1]

report

outputting to file in CSV format or HTML format[1]

report definition

creating[1]

creating new[1]

deleting[1]

editing[1]

outputting to file in XML format[1]

Reports window[1]

restoring

database data[1]

S

Search results: List of number-of-fields field(s) found in record record-name window[1], [2], [3]

Search results: number-of-records record(s) window[1], [2], [3]

service

re-registering service information[1]

starting[1]

stopping[1]

service configuration and status

displaying[1]

service information

synchronizing (between PFM - Manager and PFM - Web Console)[1]

service key[1]

Service Properties window (agent)[1]

Service Properties window (services tree)[1]

Service status window[1]

services tree

Service Properties window[1]

Services window[1]

setting

application definitions[1]

host name of connection destination PFM - Manager host (Name Server service)[1]

port numbers[1]

setup

NNM linkage facility[1]

Store version 2.0 functionality[1]

Show Options page

realtime report[1]

starting PFM - Web Console services[1]

startup information file (jpccomm.ini)[1]

status management function

disabling[1]

displaying status[1]

enabling[1]

stopping PFM - Web Console services[1]

Store service

changing and displaying settings[1]

displaying information[1]

Store version

reverted from 2.0 to 1.0[1]

symbol conventions[1]

synchronizing

service information (between PFM - Manager and PFM - Web Console)[1]

syntax conventions[1]

syslog, UNIX[1]

list of[1]

T

table frame[1]

Tiling Display window[1]

display mode[1]

sort mode[1]

U

unbinding

alarm table[1]

unsetup

NNM linkage facility[1]

updating

Agents tree[1]

alarm table and alarm[1]

instance environment[1]

Users window[1]

V

version changes[1]

version number conventions[1]

View Report window[1]

Baseline window[1]

Description of Record and Fields window[1]

Edit Report Definition page[1]

historical report[1]

Properties page[1]

Save Report Definition window[1]

Show Options page[1]

View report page[1]

W

wildcard character[1]

Window for creating a new alarm table definition[1]

windows[1]

Windows for creating new alarm definition[1]

Windows for editing existing alarm definition[1]