JP1 Version 12 JP1/Integrated Management 2 - Manager Messages

3021-3-D56-20(E)

Notices

Relevant program products

For details about the supported OS versions, and about the OS service packs and patches required by JP1/Integrated Management 2 - Manager and JP1/Integrated Management 2 - View, see the release notes for the relevant product.

JP1/Integrated Management 2 - Manager (for Windows):

P-2A2C-8ECL JP1/Integrated Management 2 - Manager 12-50

The above product includes the following:

P-CC2A2C-9MCL JP1/Integrated Management 2 - Manager 12-50 (for Windows Server 2019, Windows Server 2016, Windows Server 2012)

P-CC2A2C-6HCL JP1/Integrated Management 2 - View 12-00 (for Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7)

JP1/Integrated Management 2 - Manager (for Linux):

P-812C-8ECL JP1/Integrated Management 2 - Manager 12-50

The above product includes the following:

P-CC812C-9MCL JP1/Integrated Management 2 - Manager 12-50 (for Linux 8, Linux 7, Linux 6 (x64), Oracle Linux 8, Oracle Linux 7, Oracle Linux 6 (x64), CentOS 7, CentOS 6 (x64))

P-CC9W2C-9MCL JP1/Integrated Management 2 - Manager 12-50 (for SUSE Linux 15, SUSE Linux 12)

P-CC2A2C-6HCL JP1/Integrated Management 2 - View 12-00 (for Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7)

Trademarks

HITACHI, HiRDB, JP1 are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and other countries.

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

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

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

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

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

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

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

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

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

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

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

RSA BSAFE is either a registered trademark or a trademark of EMC Corporation in the United States and/or other countries.

UNIX is a trademark of The Open Group.

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 trademark of Microsoft Corporation in the United States and/or other countries.

Other company and product names mentioned in this document may be the trademarks of their respective owners.

This product includes RSA BSAFE Cryptographic software of EMC Corporation.

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 Andy Clark.

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

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/)

Java is a registered trademark of Oracle and/or its affiliates.

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

Hyper-V

Microsoft(R) Windows Server(R) 2008 R2 Hyper-V(R)

Microsoft(R) Windows Server(R) 2012 Hyper-V(R)

IE

Windows Internet Explorer

Windows(R) Internet Explorer(R)

SCVMM

Microsoft(R) System Center Virtual Machine Manager 2008

Microsoft(R) System Center Virtual Machine Manager 2012

Windows 7

Microsoft(R) Windows(R) 7 Enterprise

Microsoft(R) Windows(R) 7 Professional

Microsoft(R) Windows(R) 7 Ultimate

Windows 8

Windows(R) 8 Enterprise

Windows(R) 8 Pro

Windows 8.1

Windows(R) 8.1 Enterprise

Windows(R) 8.1 Pro

Windows 10

Windows(R) 10 Enterprise 32-bit

Windows(R) 10 Enterprise 64-bit

Windows(R) 10 Home 32-bit

Windows(R) 10 Home 64-bit

Windows(R) 10 Pro 32-bit

Windows(R) 10 Pro 64-bit

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

Windows Server 2016

Microsoft(R) Windows Server(R) 2016 Datacenter

Microsoft(R) Windows Server(R) 2016 Standard

Windows Server 2019

Microsoft(R) Windows Server(R) 2019 Datacenter

Microsoft(R) Windows Server(R) 2019 Standard

Windows is often used generically to refer to Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, or Windows 7.

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.

Issued

Jan. 2021: 3021-3-D56-20(E)

Copyright

Copyright (C) 2019, 2021, Hitachi, Ltd.

Copyright (C) 2019, 2021, Hitachi Solutions, Ltd.

Colophon

Publisher

Hitachi, Ltd.

6-6, Marunouchi 1-chome, Chiyoda-ku, Tokyo, 100‒8280 Japan

Summary of amendments

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

Changes

Location

The following messages were added:

KAJY00021-E, KAJY00022-E, KAJY00023-W, KAJY02055-I, KAJY22018-E, KAJY22019-E, KAJY22020-E, KAJY22021-E, KAJY22022-E, KAJY22023-I, KAJY22024-I, KAJY22025-E, KAJY22026-W, KAJY22027-W, KAJY22028-W, KAJY22029-W, KAJY22030-E, KAJY22031-E, KAJY22033-E, KAJY22034-W, KAJY22035-W, KAJY22036-W, KAJY22037-W, KAJY22038-W, KAJY22039-W, KAJY22040-I, KAJY22041-W, KAJY22042-W, KAJY22043-E, KAJY22044-W, KAJY22045-W, KAJY22046-E, KAJY22047-E, KAJY24113-E, KAJY24114-E, KAJY24115-E, KAJY24116-E, KAJY24219-E, KAJY32005-W, KAJY32006-E, KAJY52019-W, KAJY52020-E, KAJY52021-E, KAJY52022-E, KAJY52023-E, KAJY52024-W, KAJY52025-W, KAJY52026-E, KAJY52027-E, KAJY52028-E, KAJY52029-E, KAJY52030-E, KAJY52031-W, and KAJY52032-W

1.2.16, 2.17

The actions were added to the following messages:

KAJY02000-E, KAJY02003-E, KAJY02023-E, KAJY24201-E, and KAJY32211-E

2.17

The description and actions for the following message were changed:

KAJY32211-E

2.17

The following applicable OSs were added:

Linux 8

Oracle Linux 8

--

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

Preface

This manual describes the messages output by JP1/Integrated Management 2 - Manager and JP1/Integrated Management2 - View. In this manual, JP1/Integrated Management 2 - Manager and JP1/Integrated Management 2 - View are generically referred to as JP1/Integrated Management or JP1/IM. In addition, in this manual, read JP1/Integrated Management - Manager and JP1/Integrated Management - View as JP1/Integrated Management 2 - Manager and JP1/Integrated Management 2 - View, respectively.

Intended readers

This manual is intended for users who want to investigate the information reported by JP1/IM messages and who want to know how to handle errors. More specifically, it is intended for:

System administrators and system operators who manage and operate JP1/IM to provide centralized monitoring of events that occur in a system.

System administrators and system operators who manage and operate JP1/IM to provide centralized monitoring of the status of the system management infrastructure associated with events that occur in the system.

Those who have knowledge of operating systems and applications

Organization of this manual

This manual is organized into the following chapters:

1. Message Overview

Chapter 1 provides an overview of the messages output by JP1/IM - Manager and JP1/IM - View, including their format and output destinations.

2. List of Messages

Chapter 2 describes the messages output by JP1/Integrated Management - Manager and JP1/Integrated Management - View.

Manual suite

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

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

Conventions: Fonts and symbols

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

Text formatting

Convention

Bold

Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:

From the File menu, choose Open.

Click the Cancel button.

In the Enter name entry box, type your name.

Italic

Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:

Write the command as follows:

copy source-file target-file

The following message appears:

A file was not found. (file = file-name)

Italic characters are also used for emphasis. For example:

Do not delete the configuration file.

Monospace

Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:

At the prompt, enter dir.

Use the send command to send mail.

The following message is displayed:

The password is incorrect.

The following table explains the symbols used in this manual:

Symbol

Convention

|

In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example:

A|B|C means A, or B, or C.

{ }

In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example:

{A|B|C} means only one of A, or B, or C.

[ ]

In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example:

[A] means that you can specify A or nothing.

[B|C] means that you can specify B, or C, or nothing.

...

In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted.

In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example:

A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.

()

Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.

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

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

Product name

Writing convention for installation folder

Default installation folder#

JP1/IM - View

View-path

system-drive:\Program Files\Hitachi\JP1CoView

JP1/IM - Manager

Manager-path

system-drive:\Program Files\Hitachi\JP1IMM

Console-path

system-drive:\Program Files\Hitachi\JP1Cons

Scope-path

system-drive:\Program Files\Hitachi\JP1Scope

JP1/Base

Base-path

system-drive:\Program Files\Hitachi\JP1Base

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

Conventions: Meaning of "Administrator permissions" in this manual

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

Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

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.

Online manuals

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

The HTML manual has the same contents as this manual.

To view the HTML manual:

In JP1/IM - View, choose Help and then Help Contents.

In Integrated Operation Viewer Window, choose Help and then Online manual.

Note:

If you use the Start menu, the HTML manual may be displayed in an existing browser window, depending on the related setting in the OS.

Output destinations of Integrated trace log file

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

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

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

IM database

Central Scope Service

Process management

Command execution

Automatic action

Installation and Setup

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

Event base service

Central Console viewer

Central Scope viewer

Event Genaration Service

IM Configuration Management

IM Configuration Management viewer

Intelligent Integrated Management Base

1 Message Overview

This chapter provides an overview of the messages output by JP1/IM - Manager and JP1/IM - View, including their format and output destinations.

1.1 About organization of messages

This section lists the manuals that provide information about the messages output by JP1/IM, JP1/Base, and JP1/AJS.

Table 1‒1: List of message IDs and the manuals in which the messages are described

Message ID

Manual in which the message is described

Messages beginning with KAJP

JP1/Base Messages

Messages beginning with KAVA

Messages beginning with KAIU

Messages beginning with KAVB

JP1/Integrated Management 2 - Manager Messages#

Messages beginning with KAJV

Messages beginning with KNAN

Messages beginning with KAJY

Messages beginning with KFPH

Messages beginning with KFPS

Messages beginning with KAJX

Job Management Partner 1/Integrated Management - Rule Operation System Configuration and User's Guide

Messages beginning with KAVS

JP1/Automatic Job Management System 3 Messages

Messages beginning with KAVT

Messages beginning with KAVU

KAVV001 to KAVV899

#

For details about messages KAJY04400 to KAJY04499 and messages KAJY024300 to KAJY024399, see the manual JP1/Operations Analytics Messages. For details about messages KAJY04500 to KAJY04599 and messages KAJY024400 to KAJY024499, see the Release Notes for JP1/Network Node Manager i.

1.2 Message output destinations

This section lists the output destinations of the messages output by JP1/IM.

In SUSE Linux 15 or later, messages for which the output destination is syslog are not output to syslog by default. Instead, such messages are output to a log file called a journal. Therefore, read syslog as journal.

1.2.1 Output destinations of messages related to Central Console - View (KAVB0001 to KAVB2000)

This subsection shows the output destinations of messages related to JP1/IM Central Console - View.

List of output destinations of messages related to Central Console - View

Table 1-2 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log file#

stdout: Standard output

stderr: Standard error

Dialog: Message dialog box

JP1 event: JP1 event

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒2: List of output destinations of messages related to Central Console - View

Message ID

Output destination

Viewer

Manager

Event log

Dialog

stdout

stderr

HNTR Lib2

JP1 event

syslog, event log

stdout

stderr

HNTR Lib2

KAVB0001

--

Y

--

--

Y

--

Y

--

--

Y

KAVB0002

--

Y

--

--

Y

--

--

--

--

--

KAVB0003

--

Y

--

--

--

--

--

--

--

--

KAVB0004

--

--

--

--

Y

--

--

--

--

--

KAVB0005

--

Y

--

--

--

--

--

--

--

--

KAVB0007

--

Y

--

--

--

--

--

--

--

--

KAVB0008 to KAVB0010

--

Y

--

--

Y

--

--

--

--

--

KAVB0011

--

Y

--

--

--

--

--

--

--

--

KAVB0013 to KAVB0015

--

Y

--

--

--

--

--

--

--

--

KAVB0061 to KAVB0063

--

Y

--

--

--

--

--

--

--

--

KAVB0101

--

Y

--

--

--

--

--

--

--

--

KAVB0104 to KAVB0107

--

Y

--

--

Y

--

--

--

--

--

KAVB0108

--

--

--

--

Y

--

--

--

--

--

KAVB0109 to KAVB0110

--

Y

--

--

Y

--

--

--

--

--

KAVB0111

--

Y

--

--

--

--

--

--

--

--

KAVB0112

--

--

--

--

Y

--

--

--

--

--

KAVB0121

--

Y

--

--

Y

--

--

--

--

--

KAVB0122

--

Y

--

--

--

--

--

--

--

--

KAVB0123

--

Y

--

--

Y

--

--

--

--

--

KAVB0201

--

Y

--

--

--

--

--

--

--

--

KAVB0204

--

Y

--

--

--

--

--

--

--

--

KAVB0207

--

Y

--

--

Y

--

--

--

--

--

KAVB0208 to KAVB0214

--

Y

--

--

--

--

--

--

--

--

KAVB0216 to KAVB0219

--

Y

--

--

--

--

--

--

--

--

KAVB0221

--

Y

--

--

--

--

--

--

--

--

KAVB0223

--

Y

--

--

--

--

--

--

--

--

KAVB0227

--

Y

--

--

--

--

--

--

--

--

KAVB0228

--

Y

--

--

Y

--

--

--

--

--

KAVB0229

--

Y

--

--

--

--

--

--

--

--

KAVB0230 to KAVB0231

--

Y

--

--

Y

--

--

--

--

--

KAVB0232 to KAVB0233

--

Y

--

--

--

--

--

--

--

--

KAVB0241

--

Y

--

--

--

--

--

--

--

--

KAVB0243 to KAVB0245

--

Y

--

--

--

--

--

--

--

--

KAVB0246

--

Y

--

--

--

Y#4

--

--

--

--

KAVB0247

--

Y

--

--

--

--

--

--

--

--

KAVB0248

--

Y

--

--

--

Y#4

--

--

--

--

KAVB0249 to KAVB0250

--

Y

--

--

--

--

--

--

--

--

KAVB0251

--

Y

--

--

--

Y#4

--

--

--

--

KAVB0252 to KAVB0253

--

Y

--

--

--

--

--

--

--

--

KAVB0255 to KAVB0267

--

Y

--

--

--

--

--

--

--

--

KAVB0270 to KAVB0271

--

Y

--

--

Y

--

--

--

--

--

KAVB0281 to KAVB0282

--

Y

--

--

--

--

--

--

--

--

KAVB0291

--

Y

--

--

Y

--

--

--

--

--

KAVB0292 to KAVB0293

--

Y#1

--

--

--

--

--

--

--

--

KAVB0301

--

Y

--

--

--

--

--

--

--

Y

KAVB0311 to KAVB0312

--

Y

--

--

--

--

--

--

--

--

KAVB0321 to KAVB0322

--

Y

--

--

--

--

--

--

--

--

KAVB0323 to KAVB0329

--

Y

--

--

Y

--

--

--

Y

Y

KAVB0341 to KAVB0342

--

Y#2

--

--

--

--

--

--

--

--

KAVB0343 to KAVB0347

--

Y

--

--

Y

--

--

--

--

--

KAVB0349 to KAVB0351

--

Y

--

--

Y

--

--

--

--

--

KAVB0352 to KAVB0354

--

Y#2

--

--

--

--

--

--

--

--

KAVB0361 to KAVB0364

--

Y

--

--

Y

--

--

--

--

--

KAVB0368

--

--

--

--

Y

--

--

--

--

--

KAVB0371 to KAVB0374

--

--

--

--

Y

--

--

--

--

--

KAVB0381

--

Y

--

--

Y

--

--

--

--

--

KAVB0391 to KAVB0397

--

--

--

--

--

--

--

--

--

Y

KAVB0401

--

Y

--

--

Y

--

--

--

--

--

KAVB0411

--

Y

--

--

Y

--

--

--

--

--

KAVB0412

--

--

--

--

Y

--

--

--

--

--

KAVB0413 to KAVB0414

--

Y

--

--

Y

--

--

--

--

--

KAVB0415 to KAVB0419

--

Y#5

--

--

--

--

--

--

--

--

KAVB0422 to KAVB0423

--

Y#5

--

--

--

--

--

--

--

--

KAVB0424

--

Y

--

--

--

--

--

--

--

--

KAVB0451 to KAVB0452

--

--

--

--

Y

--

--

--

--

--

KAVB0502 to KAVB0503

--

Y

--

--

--

--

--

--

--

--

KAVB0504 to KAVB0505

--

Y

--

--

Y

--

--

--

--

--

KAVB0507 to KAVB0518

--

Y

--

--

--

--

--

--

--

--

KAVB0531 to KAVB0533

--

Y

--

--

--

--

--

--

--

--

KAVB0535

--

Y

--

--

--

--

--

--

--

--

KAVB0536

--

Y

--

--

Y

--

--

--

--

--

KAVB0540 to KAVB0541

--

Y

--

--

Y

--

--

--

--

--

KAVB0551

--

Y#3

--

--

--

Y

--

--

--

--

KAVB0552 to KAVB0553

--

Y

--

--

--

--

--

--

--

--

KAVB0554 to KAVB0555

--

Y

--

--

Y

--

--

--

--

Y

KAVB0556

--

Y

--

--

--

--

--

--

--

--

KAVB0557

--

Y

--

--

Y

--

--

--

--

--

KAVB0558

--

Y

--

--

Y

--

--

--

--

Y

KAVB0559

--

Y

--

--

--

--

--

--

--

--

KAVB0560 to KAVB0563

--

Y

--

--

Y

--

--

--

--

Y

KAVB0611 to KAVB0612

--

Y

--

--

Y

--

--

--

--

--

KAVB0624

--

--

--

--

Y

--

--

--

--

--

KAVB0651 to KAVB0657

--

--

--

Y

--

--

--

--

--

--

KAVB0658

--

--

--

--

Y

--

--

--

--

--

KAVB0684

--

--

--

--

Y

--

--

--

--

--

KAVB0685

--

Y

--

--

Y

--

--

--

--

--

KAVB0686

--

--

--

--

--

--

--

--

--

Y

KAVB0687

--

--

--

--

Y

--

--

--

--

--

KAVB0688

--

Y

--

--

Y

--

--

--

--

--

KAVB0711 to KAVB0759

--

Y

--

--

Y

--

--

--

--

--

KAVB0760 to KAVB0761

--

--

--

--

--

--

--

--

--

Y

KAVB0762 to KAVB0763

--

Y

--

--

Y

--

--

--

--

--

KAVB0801

--

Y

--

--

--

--

--

--

Y

--

KAVB0802

--

--

--

--

--

--

--

--

Y

--

KAVB0803

--

Y

--

--

--

--

--

--

Y

--

KAVB0804 to KAVB0806

--

--

--

--

--

--

--

--

Y

--

KAVB0807

--

--

--

--

--

--

--

--

Y

--

KAVB0810

--

Y

--

--

--

--

--

--

Y

--

KAVB0811

--

Y

--

--

--

--

--

--

--

--

KAVB0821 to KAVB0823

--

--

--

--

--

--

--

--

Y

Y

KAVB0824

--

--

--

--

--

--

--

--

Y

--

KAVB0825

--

--

--

--

--

--

--

--

Y

Y

KAVB0826 to KAVB0827

--

--

--

--

--

--

--

--

Y

--

KAVB0828

--

Y

--

--

Y

--

--

--

--

--

KAVB0830

--

--

--

--

--

--

--

--

Y

--

KAVB0831 to KAVB0835

--

--

--

--

--

--

--

--

Y

Y

KAVB0836

--

--

--

--

--

--

--

Y

--

Y

KAVB0837 to KAVB0842

--

--

--

--

--

--

--

--

Y

Y

KAVB0851 to KAVB0854

--

--

--

--

--

--

--

--

Y

Y

KAVB0855 to KAVB0858

--

--

Y

--

--

--

--

--

--

--

KAVB0859 to KAVB0862

--

--

--

--

--

--

--

--

Y

Y

KAVB0863

--

--

--

--

--

--

--

--

Y

--

KAVB0864

--

--

--

--

--

--

--

Y

--

--

KAVB0866

--

--

--

--

--

--

--

--

Y

--

KAVB0868 to KAVB0869

--

--

--

--

--

--

--

Y

--

--

KAVB0870 to KAVB0881

--

--

--

--

--

--

--

--

Y

--

KAVB0882

--

--

--

--

--

--

--

Y

--

--

KAVB0883 to KAVB0888

--

--

--

--

--

--

--

--

Y

--

KAVB0889

--

--

--

--

--

--

--

Y

--

--

KAVB0890 to KAVB0896

--

--

--

--

--

--

--

--

Y

--

KAVB0893

--

--

--

--

--

--

--

--

Y

--

KAVB0894

--

--

--

--

--

--

--

Y

--

--

KAVB0895 to KAVB0888

--

--

--

--

--

--

--

Y

--

Y

KAVB0897

--

--

--

--

--

--

--

Y

--

--

KAVB0898

--

--

--

--

--

--

--

--

Y

Y

KAVB0899 to KAVB0900

--

--

--

--

--

--

--

--

Y

--

KAVB0902 to KAVB0903

--

--

--

--

--

--

--

--

Y

--

KAVB0961 to KAVB0962

--

--

--

--

--

--

--

--

--

Y

KAVB1002 to KAVB1003

--

--

Y

--

--

--

--

Y

--

--

KAVB1004

--

--

--

Y

Y

--

--

--

Y

Y

KAVB1005

--

--

Y

--

--

--

--

Y

--

--

KAVB1010 to KAVB1011

--

--

--

Y

--

--

--

--

Y

--

KAVB1012 to KAVB1017

--

--

--

--

--

--

--

--

--

Y

KAVB1018

--

Y

--

--

Y

--

--

--

--

--

KAVB1019

--

Y

--

--

--

--

--

--

--

--

KAVB1020 to KAVB1021

--

--

--

--

--

--

--

--

--

Y

KAVB1031 to KAVB1033

--

Y

--

--

--

--

--

--

--

--

KAVB1034 to KAVB1037

--

Y

--

--

--

--

--

--

--

--

KAVB1040 to KAVB1045

--

--

--

--

--

--

--

--

--

Y

KAVB1046

--

Y

--

--

Y

--

--

--

--

Y

KAVB1101 to KAVB1102

--

--

--

--

Y

--

--

--

--

--

KAVB1104 to KAVB1105

--

--

--

--

--

--

--

--

--

Y

KAVB1111

--

Y

--

Y

Y

--

--

--

--

--

KAVB1112 to KAVB1114

--

--

--

Y

--

--

--

--

--

--

KAVB1115

--

--

--

Y

--

--

--

--

--

Y

KAVB1116 to KAVB1121

--

--

--

Y

--

--

--

--

--

--

KAVB1130 to KAVB1141

--

--

--

--

--

--

--

--

--

Y

KAVB1148 to KAVB1149

--

Y

--

--

--

--

--

--

--

--

KAVB1150

--

--

--

--

--

Y

--

--

--

Y

KAVB1151 to KAVB1152

--

Y

--

--

--

--

--

--

--

--

KAVB1153 to KAVB1154

--

--

--

--

--

--

--

--

--

Y

KAVB1155

--

Y

--

--

--

--

--

--

--

--

KAVB1156

--

--

--

--

--

--

--

--

--

Y

KAVB1157

--

Y

--

--

--

--

--

--

--

--

KAVB1158 to KAVB1162

--

--

--

--

--

--

--

--

--

Y

KAVB1163

--

Y

--

--

Y

--

--

--

--

Y

KAVB1190

--

Y

--

--

Y

--

--

--

--

Y

KAVB1191 to KAVB1192

--

Y

--

--

Y

--

--

--

--

--

KAVB1200 to KAVB1205

--

Y

--

--

Y

--

--

--

--

--

KAVB1206

--

--

--

--

--

--

--

--

--

Y

KAVB1207 to KAVB1210

--

Y

--

--

Y

--

--

--

--

--

KAVB1211

Y

--

--

--

Y

--

Y

--

--

Y

KAVB1401

--

Y

--

--

Y

--

--

--

--

Y

KAVB1501 to KAVB1502

--

Y

--

--

Y

--

Y

--

--

--

KAVB1503 to KAVB1504

--

Y

--

--

Y

--

--

--

--

--

KAVB1506 to KAVB1507

--

Y

--

--

Y

--

--

--

--

--

KAVB1509

--

Y

--

--

Y

--

--

--

--

--

KAVB1510

--

Y

--

--

Y

--

Y

--

--

--

KAVB1512

--

Y

--

--

Y

--

--

--

--

--

KAVB1513

--

--

--

--

--

Y#4

--

--

--

--

KAVB1515

--

Y

--

--

Y

--

--

--

--

--

KAVB1516

--

--

--

--

--

Y#4

--

--

--

--

KAVB1517 to KAVB1522

--

--

--

--

--

--

Y

--

--

Y

KAVB1523 to KAVB1525

--

Y

--

--

Y

--

--

--

--

--

KAVB1526

--

--

--

--

--

--

--

--

Y

Y

KAVB1527

--

--

--

--

--

Y#4

--

--

--

--

KAVB1528 to KAVB1529

--

--

--

--

Y

--

--

--

--

Y

KAVB1531 to KAVB1536

--

--

--

--

--

--

--

--

--

Y

KAVB1538 to KAVB1539

--

--

--

--

Y

--

--

--

--

--

KAVB1540

--

--

--

--

--

Y

--

--

--

--

KAVB1541 to KAVB1543

--

Y

--

--

Y

--

--

--

--

--

KAVB1544

--

Y

--

--

Y

--

--

--

--

Y

KAVB1551 to KAVB1552

--

--

--

--

--

--

--

--

--

Y

KAVB1554

--

--

--

--

--

--

--

--

--

Y

KAVB1556

--

--

--

--

--

--

--

--

--

Y

KAVB1558

--

--

--

--

--

--

--

--

--

Y

KAVB1570 to KAVB1576

--

--

--

--

--

--

--

--

--

Y

KAVB1577

--

--

--

--

--

Y

--

--

--

--

KAVB1578 to KAVB1587

--

--

--

--

--

--

--

--

--

Y

KAVB1588

--

Y

--

--

--

--

--

--

--

--

KAVB1589

--

Y

--

--

Y

--

--

--

--

--

KAVB1590 to KAVB1591

--

--

--

--

--

--

--

--

--

Y

KAVB1593 to KAVB1596

--

--

--

--

--

--

--

--

--

Y

KAVB1597

--

Y

--

--

Y

--

--

--

--

--

KAVB1598

--

Y

--

--

--

--

--

--

--

--

KAVB1601 to KAVB1603

--

--

--

--

--

--

--

--

Y

Y

KAVB1604 to KAVB1608

--

--

--

--

--

--

--

--

--

Y

KAVB1611 to KAVB1614

--

--

--

--

--

--

--

--

Y

Y

KAVB1631 to KAVB1632

--

--

--

--

--

--

--

--

--

Y

KAVB1633 to KAVB1634

--

--

--

--

--

--

Y

--

--

Y

KAVB1635 to KAVB1640

--

--

--

--

--

--

--

--

--

Y

KAVB1647 to KAVB1651

--

--

--

--

--

--

--

--

--

Y

KAVB1652

--

--

--

--

--

--

Y

--

--

Y

KAVB1653 to KAVB1655

--

--

--

--

--

--

--

--

--

Y

KAVB1656

--

--

--

--

--

--

Y

--

--

Y

KAVB1657 to KAVB1658

--

Y

--

--

--

--

--

--

--

--

KAVB1660 to KAVB1665

--

Y

--

--

--

--

--

--

--

Y

KAVB1668

--

Y

--

--

--

--

--

--

--

Y

KAVB1669

--

--

--

--

--

Y

--

--

--

Y

KAVB1670

--

Y

--

--

Y

--

--

--

--

--

KAVB1671

--

Y

--

--

Y

Y

--

--

--

--

KAVB1672 to KAVB1678

--

Y

--

--

Y

--

--

--

--

Y

KAVB1680

--

Y

--

--

--

--

--

--

--

--

KAVB1681

--

--

--

--

Y

--

--

--

--

--

KAVB1682 to KAVB1683

--

Y

--

--

Y

--

--

--

--

--

KAVB1684

--

Y

--

--

--

--

--

--

--

--

KAVB1685

--

--

--

--

--

--

--

--

--

Y

KAVB1686 to KAVB1689

--

Y

--

--

--

--

--

--

--

--

KAVB1691

--

--

--

--

--

--

--

--

--

Y

KAVB1692

--

Y

--

--

Y

--

--

--

--

--

KAVB1694

--

Y

--

--

Y

--

--

--

--

--

KAVB1701 to KAVB1711

--

--

--

--

--

--

--

--

--

Y

KAVB1801 to KAVB1802

--

--

--

--

--

--

--

--

--

Y

KAVB1811 to KAVB1815

--

--

--

--

--

--

--

--

--

Y

KAVB1816

--

--

--

--

--

Y

--

--

--

--

KAVB1821

--

--

--

--

--

--

--

--

Y

Y

KAVB1831

--

--

--

--

--

--

--

--

--

Y

KAVB1832 to KAVB1833

--

--

--

--

--

Y

--

--

--

Y

KAVB1834

--

--

--

--

--

--

--

--

--

Y

KAVB1841 to KAVB1842

--

--

--

--

--

Y

--

--

--

Y

KAVB1843

--

Y

--

--

--

--

--

--

--

--

KAVB1844

--

--

--

--

--

--

Y

--

--

Y

KAVB1851

--

--

--

--

--

--

--

Y

--

Y

KAVB1852 to KAVB1862

--

--

--

--

--

--

--

--

Y

--

KAVB1863

--

--

--

--

--

--

--

--

Y

Y

KAVB1864

--

--

--

--

--

--

--

Y

--

--

KAVB1865

--

--

--

--

--

--

--

--

Y

--

KAVB1866

--

Y

--

--

Y

--

--

--

Y

Y

KAVB1867

--

--

--

--

--

--

--

--

Y

Y

KAVB1868

--

--

--

--

--

--

--

--

--

Y

KAVB1869

--

Y

--

--

Y

--

--

--

Y

Y

KAVB1870

--

--

--

--

--

--

--

--

Y

Y

KAVB1871

--

--

--

--

--

--

--

--

--

Y

KAVB1872

--

--

--

--

--

--

--

--

Y

Y

KAVB1873

--

--

--

--

--

--

--

--

--

Y

KAVB1874

--

Y

--

--

Y

--

--

--

--

--

KAVB1880

--

--

--

--

--

--

--

--

--

Y

KAVB1884 to KAVB1891

--

--

--

--

--

--

--

--

--

Y

KAVB1892 to KAVB1893

--

Y

--

--

--

--

--

--

--

--

KAVB1894 to KAVB1898

--

--

--

--

--

--

--

--

--

Y

KAVB1899

--

Y

--

--

Y

--

--

--

--

Y

KAVB1917 to KAVB1921

--

Y

--

--

Y

--

--

--

--

--

KAVB1922

--

--

--

--

--

--

--

--

--

Y

KAVB1923

--

Y

--

--

Y

--

--

--

--

--

KAVB1924 to KAVB1935

--

--

--

--

--

--

--

--

--

Y

KAVB1936 to KAVB1940

--

Y

--

--

Y

--

--

--

--

--

KAVB1941

--

--

--

--

--

--

--

--

--

Y

KAVB1942

--

Y

--

--

Y

--

--

--

--

--

KAVB1943 to KAVB1955

--

--

--

--

--

--

--

--

--

Y

KAVB1956 to KAVB1957

--

--

--

--

--

--

--

--

Y

Y

KAVB1958 to KAVB1965

--

Y

--

--

Y

--

--

--

--

--

KAVB1969

--

--

--

--

Y

--

--

--

--

--

KAVB1970

--

Y

--

--

Y

--

--

--

--

--

KAVB1971

--

--

--

--

Y

--

--

--

--

--

KAVB1972 to KAVB1975

--

--

--

--

--

--

--

--

Y

Y

KAVB1976 to KAVB1978

--

--

--

--

--

--

--

--

--

Y

KAVB1979

--

Y

--

--

--

--

--

--

--

--

KAVB1981

--

--

--

--

--

Y

--

--

--

Y

KAVB1982 to KAVB1988

--

--

--

--

--

--

--

--

--

Y

KAVB1990 to KAVB1991

--

--

--

--

--

--

--

--

--

Y

KAVB1993 to KAVB1994

--

--

--

--

--

--

--

--

--

Y

#1: Displayed in the Message area of the Event Details window.

#2: Displayed in the Message area of the Event Details window and in the Related Events area of the Related Events window.

#3: Displayed on the Response-Waiting Events page of the Event Console window.

#4: Displayed as a dummy event message. The following restrictions apply to the dummy event.

This event cannot be searched on the Search Events page of the Event Console window.

You cannot view this event in the Integrated Operation Viewer window.

You cannot search for this event by using the event search REST API.

If event details are displayed, the basic attribute or the extended attribute of a JP1 event is not displayed.

Even if automated action is set for this event, no action will be performed.

Even if event information mapping is defined for this event, no mapping will be performed.

This event is not subject to monitor startup.

This event is not subject to filtering by using an event acquisition filter.

This event is not subject to correlation event issuance processing.

#5: Displayed in the Log area of the Execute Command window.

1.2.2 Output destinations of messages related to command execution (KAVB2001 to KAVB2999)

This subsection shows the output destinations of messages related to execution of JP1/IM commands.

List of output destinations of messages related to command execution

Table 1-3 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log file#

stdout: Standard output

stderr: Standard error

Window: Execute Command window and/or Action Log Details window

Command: Command execution history storage directory (you can use the jcocmdlog command to check the output messages)

JP1 event: JP1 event

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒3: List of output destinations of messages related to command execution

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

Window

Command

JP1 event

KAVB2002

--

--

--

--

--

Y

Y

--

KAVB2003

--

--

Y

--

--

Y

Y

--

KAVB2005

--

--

Y

--

--

Y

Y

--

KAVB2012 to KAVB2013

--

--

--

--

--

Y

Y

--

KAVB2022 to KAVB2024

--

--

Y

--

--

Y

Y

--

KAVB2027

--

--

--

--

--

Y

Y

--

KAVB2029

--

--

Y

--

--

Y

Y

--

KAVB2031

--

--

Y

--

--

Y

Y

--

KAVB2037

--

--

Y

--

--

--

--

--

KAVB2041

--

--

Y

--

--

Y

Y

--

KAVB2042

--

--

Y

--

--

--

--

--

KAVB2051 to KAVB2052

--

--

Y

--

--

Y

Y

--

KAVB2053 to KAVB2054

--

--

Y

--

--

--

--

--

KAVB2055

--

--

Y

--

--

Y

Y

--

KAVB2056

--

--

Y

--

--

--

--

--

KAVB2057 to KAVB2062

--

--

Y

--

--

Y

Y

--

KAVB2063 to KAVB2064

--

--

Y

--

--

--

--

--

KAVB2065

--

--

--

--

--

Y

Y

--

KAVB2066 to KAVB2070

--

--

Y

--

--

Y

Y

--

KAVB2071 to KAVB2072

--

--

Y

--

--

Y

Y

Y

KAVB2100 to KAVB2102

--

--

--

--

--

--

--

Y

KAVB2103

--

--

Y

--

--

--

--

--

KAVB2200 to KAVB2208

--

--

--

--

Y

--

--

--

KAVB2209 to KAVB2210

--

--

Y

--

Y

--

--

--

KAVB2211

--

--

--

Y

--

--

--

--

KAVB2212

Y

--

Y

--

Y

--

--

--

KAVB2213

--

--

Y

--

--

--

--

--

KAVB2214 to KAVB2218

--

--

Y

--

Y

--

--

--

KAVB2221

--

--

Y

--

Y

--

--

--

KAVB2222 to KAVB2224

--

--

--

Y

--

--

--

--

KAVB2225

--

--

Y

--

Y

--

--

--

KAVB2227 to KAVB2228

--

--

Y

--

--

--

--

--

KAVB2229 to KAVB2231

--

--

--

--

Y

--

--

--

KAVB2232 to KAVB2237

--

--

Y

--

Y

--

--

--

KAVB2238

--

--

--

--

Y

--

--

--

KAVB2239 to KAVB2242

--

--

Y

--

Y

--

--

--

KAVB2243

--

--

--

--

Y

--

--

--

KAVB2244 to KAVB2245

--

--

Y

--

--

--

--

--

KAVB2246

Y

--

Y

--

Y

--

--

--

KAVB2247

--

--

Y

--

Y

--

--

--

KAVB2248

--

--

Y

--

--

--

--

--

KAVB2249

Y

--

Y

--

--

--

--

--

KAVB2250 to KAVB2251

--

--

--

Y

--

--

--

--

KAVB2252

--

--

--

--

Y

--

--

--

KAVB2253

--

--

Y

--

Y

--

--

--

KAVB2276 to KAVB2284

--

--

--

--

Y

--

--

--

KAVB2285 to KAVB2286

--

--

Y

--

Y

--

--

--

KAVB2287

--

--

--

Y

--

--

--

--

KAVB2288

Y

--

Y

--

Y

--

--

--

KAVB2289 to KAVB2290

--

--

--

--

Y

--

--

--

KAVB2291

--

--

--

Y

--

--

--

--

KAVB2292

--

--

Y

Y

--

--

--

--

KAVB2293 to KAVB2294

--

--

--

Y

--

--

--

--

KAVB2295

--

--

--

--

Y

--

--

--

KAVB2296

--

--

Y

--

--

--

--

--

KAVB2297 to KAVB2301

--

--

Y

--

Y

--

--

--

KAVB2304

--

--

Y

--

Y

--

--

--

KAVB2305 to KAVB2307

--

--

--

Y

--

--

--

--

KAVB2308

--

--

Y

--

Y

--

--

--

KAVB2310 to KAVB2311

--

--

Y

--

--

--

--

--

KAVB2312

--

--

--

Y

--

--

--

--

KAVB2313

--

--

--

--

Y

--

--

--

KAVB2314

--

--

Y

--

--

--

--

--

KAVB2316 to KAVB2321

--

--

Y

--

Y

--

--

--

KAVB2322

--

--

--

--

Y

--

--

--

KAVB2323 to KAVB2326

--

--

Y

--

Y

--

--

--

KAVB2327

--

--

--

--

Y

--

--

--

KAVB2328 to KAVB2329

--

--

Y

--

--

--

--

--

KAVB2330

Y

--

Y

--

Y

--

--

--

KAVB2331

--

--

Y

--

Y

--

--

--

KAVB2332

--

--

Y

--

--

--

--

--

KAVB2333

Y

--

Y

--

--

--

--

--

KAVB2334 to KAVB2335

--

--

--

Y

--

--

--

--

KAVB2336

--

--

--

--

Y

--

--

--

KAVB2337

--

--

Y

--

Y

--

--

--

KAVB2339

--

--

Y

--

Y

--

--

--

KAVB2356

--

--

Y

--

Y

--

--

--

KAVB2401

--

--

--

Y

--

Y

Y

--

KAVB2402

--

--

Y

--

--

--

--

Y

KAVB2500

--

--

--

Y

--

--

--

--

KAVB2501 to KAVB2529

--

--

--

--

Y

--

--

--

KAVB2530

--

--

Y

--

--

--

--

--

KAVB2531

--

--

Y

Y

--

--

--

--

KAVB2532

--

--

Y

Y

--

--

--

--

KAVB2534 to KAVB2539

--

--

--

--

Y

--

--

--

KAVB2540

--

--

Y

--

Y

--

--

--

KAVB2541

--

--

--

--

Y

--

--

--

KAVB2542

--

--

Y

--

Y

--

--

--

KAVB2543 to KAVB2547

--

--

--

--

Y

--

--

--

KAVB2548

--

--

--

Y

--

--

--

--

KAVB2549 to KAVB2552

--

--

--

--

Y

--

--

--

KAVB2553 to KAVB2557

--

--

--

Y

--

--

--

--

KAVB2559

--

--

Y

--

Y

--

--

--

KAVB2560 to KAVB2561

--

--

--

Y

--

--

--

--

KAVB2563

--

--

--

--

Y

--

--

--

KAVB2564

--

--

Y

--

Y

--

--

--

KAVB2565 to KAVB2567

--

--

--

--

Y

--

--

--

KAVB2600

--

--

Y

--

--

--

Y

--

KAVB2605 to KAVB2607

--

--

Y

--

--

Y

Y

--

KAVB2608 to KAVB2611

--

--

Y

--

--

--

--

--

KAVB2613 to KAVB2614

--

--

Y

--

--

--

--

--

KAVB2615 to KAVB2616

--

--

Y

--

--

Y

Y

--

KAVB2618 to KAVB2621

--

--

Y

--

--

--

--

--

KAVB2623

--

--

Y

--

--

Y

Y

--

KAVB2626

--

--

Y

--

--

Y

Y

--

KAVB2627

--

--

Y

--

--

--

--

--

KAVB2628

--

--

Y

--

--

Y

Y

--

KAVB2630

--

--

Y

--

--

Y

Y

--

KAVB2631 to KAVB2640

--

--

Y

--

--

--

--

--

1.2.3 Output destinations of messages related to configuration management (KAVB3001 to KAVB3200)

This subsection shows the output destinations of messages related to the JP1/IM Configuration Management component.

List of output destinations of messages related to JP1/IM configuration management

Table 1-4 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log file#

stdout: Standard output

stderr: Standard error

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒4: List of output destinations of messages related to configuration management

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

KAVB3001 to KAVB3004

Y

Y

--

--

--

KAVB3005 to KAVB3006

--

--

Y

--

Y

KAVB3007

Y

Y

Y

Y

--

KAVB3008

--

--

Y

--

Y

KAVB3010 to KAVB3013

--

--

Y

--

--

KAVB3015 to KAVB3018

--

--

Y

--

--

KAVB3023 to KAVB3025

--

--

Y

--

--

KAVB3031 to KAVB3035

--

--

Y

--

--

KAVB3049 to KAVB3057

--

--

Y

--

--

KAVB3059 to KAVB3060

--

--

Y

--

--

KAVB3073 to KAVB3074

--

--

Y

--

--

KAVB3078 to KAVB3079

--

--

Y

--

--

KAVB3080 to KAVB3089

--

--

Y

Y

--

KAVB3090 to KAVB3093

--

--

--

Y

--

KAVB3094 to KAVB3096

--

--

Y

Y

--

KAVB3097

--

--

--

Y

--

KAVB3098 to KAVB3115

--

--

Y

Y

--

KAVB3116

--

--

Y

--

--

KAVB3118 to KAVB3121

--

--

Y

Y

--

KAVB3123

--

--

Y

Y

--

KAVB3124

--

--

--

Y

--

KAVB3133 to KAVB3135

--

--

Y

--

--

KAVB3148 to KAVB3158

--

--

Y

--

--

KAVB3159

--

--

--

Y

--

KAVB3160 to KAVB3161

--

--

Y

--

--

KAVB3162

--

--

Y

Y

--

KAVB3163

--

--

--

--

Y

KAVB3164 to KAVB3173

--

--

Y

--

--

KAVB3180 to KAVB3181

--

--

Y

--

--

KAVB3185

--

--

Y

--

--

1.2.4 Output destinations of messages related to process management (KAVB3501 to KAVB3999)

This subsection shows the output destinations of messages related to JP1/IM process management.

List of output destinations of messages related to process management

Table 1-5 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log#

stdout: Standard output

stderr: Standard error

JP1 event: JP1 event

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace logs are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Note:

Messages such as internal error messages, that have a message ID but are not listed in the table, may also be output.

Table 1‒5: List of output destinations of messages related to process management

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

JP1 event

KAVB3501

Y

Y

--

--

--

--

KAVB3502

--

--

Y

--

Y

--

KAVB3503

--

--

--

--

Y

--

KAVB3504

--

--

Y

--

Y

--

KAVB3516

Y

--

--

--

Y

--

KAVB3552 to KAVB3554

--

--

Y

--

--

--

KAVB3564

--

--

Y

--

--

--

KAVB3574

--

--

Y

--

--

--

KAVB3577 to KAVB3578

--

--

Y

--

--

--

KAVB3586

--

--

Y

--

--

--

KAVB3597

--

--

Y

--

--

--

KAVB3599

--

--

Y

--

--

--

KAVB3602 to KAVB3605

--

--

Y

--

--

--

KAVB3608 to KAVB3610

--

--

Y

--

--

--

KAVB3612

--

--

Y

--

--

--

KAVB3613

Y

Y

Y

--

--

Y

KAVB3614

Y

Y

Y

--

--

--

KAVB3616

--

--

--

--

--

Y

KAVB3620

Y

Y

Y

Y

--

--

KAVB3621

Y

--

Y

--

--

--

KAVB3623

Y

--

Y

--

--

--

KAVB3624

Y

Y

Y

--

--

--

KAVB3625

--

--

Y

Y

--

--

KAVB3626

Y

Y

Y

Y

--

--

KAVB3627

--

--

Y

--

--

--

KAVB3631

--

--

Y

--

--

--

KAVB3642

--

--

Y

--

--

--

KAVB3643 to KAVB3644

Y

Y

Y

--

--

--

KAVB3645 to KAVB3646

--

--

Y

--

--

--

KAVB3647#

--

--

Y

--

--

--

KAVB3649

Y

Y

Y

Y

--

--

KAVB3651 to KAVB3662

--

--

Y

Y

--

--

KAVB3663

--

--

--

--

Y

--

KAVB3672

--

--

Y

Y

--

--

KAVB3674 to KAVB3678

--

--

Y

Y

--

--

KAVB3680 to KAVB3684

--

--

Y

Y

--

--

KAVB3685

--

--

--

Y

--

--

KAVB3690 to KAVB3694

--

--

--

Y

--

--

KAVB3705

--

--

Y

--

--

--

KAVB3732

--

--

Y

--

--

--

KAVB3736

--

--

Y

--

--

--

KAVB3737

Y

Y

Y

--

--

Y

KAVB3743 to KAVB3745

--

--

Y

--

--

--

KAVB3752

Y

Y

Y

--

--

--

KAVB3760 to KAVB3769

--

--

Y

--

--

--

KAVB3777 to KAVB3779

--

--

Y

--

--

--

KAVB3786

--

--

Y

--

--

--

KAVB3788

Y

Y

Y

--

--

--

KAVB3802

--

--

Y

--

--

--

KAVB3828#

--

Y

--

--

--

--

KAVB3840#

--

Y

--

--

--

--

KAVB3841#

--

Y

--

--

--

--

KAVB3846

--

--

Y

--

--

--

KAVB3855

--

--

Y

--

--

--

KAVB3862

Y

Y

Y

--

--

--

KAVB3863

--

--

Y

--

--

--

KAVB3870

Y

Y

--

Y

--

--

KAVB3871

--

--

--

Y

--

--

KAVB3872

Y

Y

--

Y

--

--

KAVB3873

--

--

--

Y

--

--

KAVB3874 to KAVB3875

Y

Y

--

Y

--

--

KAVB3899

--

--

--

Y

--

--

KAVB3905

--

--

Y

--

--

--

KAVB3908

--

--

Y

--

--

--

KAVB3910

--

--

Y

--

--

--

KAVB3911 to KAVB3914

--

--

Y

Y

--

--

KAVB3915 to KAVB3917

--

--

Y

--

--

--

KAVB3918

--

--

Y

--

Y

--

KAVB3935

--

--

Y

--

--

--

KAVB3960

--

--

--

Y

--

--

KAVB3961

--

--

Y

Y

--

--

KAVB3981

--

--

Y

--

--

--

KAVB3984

--

--

Y

--

--

--

KAVB3986

--

--

Y

Y

--

--

#: In UNIX, this is also output to standard error.

1.2.5 Output destinations of messages related to automated actions and event base service (KAVB4001 to KAVB6000)

This subsection shows the output destinations of messages related to JP1/IM automated actions and event base service.

List of output destinations of messages related to automated actions and event base service

Table 1-6 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log file#

stderr: Standard error

Dialog: Message dialog box

Event: JP1 event

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒6: List of output destinations of messages related to automated actions and event base service

Message ID

Output destination

Viewer

Manager

Dialog

HNTRLib2

Event

syslog, event log

stdout

stderr

HNTRLib2

KAVB4001

Y

Y

--

--

--

Y

Y

KAVB4002 to KAVB4003

--

--

--

--

--

--

Y

KAVB4004

Y

Y

--

Y

--

Y

--

KAVB4005 to KAVB4012

Y

Y

--

--

--

Y

--

KAVB4013

--

--

--

--

--

--

Y

KAVB4014

--

--

Y

--

--

--

Y

KAVB4015

Y

Y

--

--

--

Y

--

KAVB4016

--

--

--

--

--

Y

--

KAVB4020 to KAVB4021

Y

Y

--

--

--

Y

Y

KAVB4022

--

--

--

Y

--

Y

--

KAVB4023

--

--

--

--

--

Y

Y

KAVB4024

--

--

--

--

--

--

Y

KAVB4026 to KAVB4027

--

--

--

--

--

Y

--

KAVB4028 to KAVB4029

--

--

--

--

--

Y

Y

KAVB4050 to KAVB4051

--

--

--

Y

--

--

Y

KAVB4052 to KAVB4053

--

--

--

--

--

--

Y

KAVB4054

--

--

Y

Y

--

--

Y

KAVB4055 to KAVB4056

--

--

Y

--

--

--

Y

KAVB4057 to KAVB4060

--

--

--

--

--

--

Y

KAVB4101

--

--

--

--

--

Y

Y

KAVB4120 to KAVB4133

Y

Y

--

--

--

Y

Y

KAVB4134

--

Y

--

--

--

Y

Y

KAVB4135 to KAVB4147

Y

Y

--

--

--

Y

Y

KAVB4148

--

--

--

--

--

Y

--

KAVB4150

Y

Y

--

--

--

Y

Y

KAVB4151 to KAVB4152

--

--

--

--

--

--

Y

KAVB4153 to KAVB4154

Y

Y

--

Y

--

Y

Y

KAVB4155

--

--

--

--

--

--

Y

KAVB4180

Y

Y

--

--

--

Y

Y

KAVB4181

--

--

--

--

--

--

Y

KAVB4182

Y

Y

--

--

--

Y

Y

KAVB4250 to KAVB4251

--

--

--

Y

--

--

Y

KAVB4252 to KAVB4253

--

--

--

--

--

--

Y

KAVB4254

--

--

--

Y

--

--

Y

KAVB4350

--

--

--

--

--

--

Y

KAVB4400 to KAVB4405

--

--

Y

--

--

--

Y

KAVB4406 to KAVB4409

--

--

--

--

--

--

Y

KAVB4420 to KAVB4424

Y#

--

--

--

--

--

Y

KAVB4425

--

--

--

--

--

--

Y

KAVB4426 to KAVB4429

Y#

--

--

--

--

--

Y

KAVB4430 to KAVB4438

--

--

Y

--

--

--

--

KAVB4439

--

--

--

--

--

--

Y

KAVB4440 to KAVB4445

Y#

--

--

--

--

--

Y

KAVB4450 to KAVB4452

Y

Y

--

--

--

Y

Y

KAVB4500 to KAVB4508

--

--

--

--

--

--

Y

KAVB4550 to KAVB4551

Y

Y

--

--

--

Y

Y

KAVB4600

--

--

--

--

--

--

Y

KAVB4602 to KAVB4616

--

--

--

--

--

--

Y

KAVB4620 to KAVB4641

--

--

--

--

--

--

Y

KAVB4650 to KAVB4664

--

--

--

--

--

--

Y

KAVB4666 to KAVB4670

--

--

--

--

--

--

Y

KAVB4671

Y

--

--

--

--

--

--

KAVB4672

--

--

--

--

--

--

Y

KAVB4673 to KAVB4674

--

--

Y

--

--

--

Y

KAVB4675

--

--

--

--

--

--

Y

KAVB4676 to KAVB4679

--

--

Y

--

--

--

--

KAVB4700 to KAVB4702

--

--

--

Y

--

--

Y

KAVB4703 to KAVB4708

--

--

--

--

--

--

Y

KAVB4710 to KAVB4711

--

--

--

--

--

--

Y

KAVB4712

--

--

Y

--

--

--

Y

KAVB4713 to KAVB4715

--

--

--

--

--

--

Y

KAVB4750 to KAVB4762

--

--

--

--

--

--

Y

KAVB4764

--

--

Y

--

--

--

--

KAVB4765 to KAVB4767

--

--

--

--

--

--

Y

KAVB4768

--

--

--

Y

--

--

Y

KAVB4769 to KAVB4777

--

--

--

--

--

--

Y

KAVB4780

--

--

--

--

--

--

Y

KAVB4785 to KAVB4787

--

--

--

--

--

--

Y

KAVB4788

--

--

--

Y

--

--

Y

KAVB4789 to KAVB4790

--

--

--

--

--

--

Y

KAVB4802

--

--

--

--

--

--

Y

KAVB4803

--

--

Y

--

--

--

Y

KAVB4901 to KAVB4908

Y

Y

--

Y

--

Y

Y

KAVB4909

Y

Y

Y

Y

--

Y

Y

KAVB5000 to KAVB5002

Y

Y

--

--

--

--

Y

KAVB5050 to KAVB5068

Y

Y

--

--

--

--

--

KAVB5069

Y

Y

--

--

--

--

--

KAVB5070

Y

Y

--

--

--

--

Y

KAVB5104 to KAVB5105

Y

Y

--

--

--

Y

Y

KAVB5106

Y

Y

--

Y

--

Y

Y

KAVB5107 to KAVB5108

Y

Y

--

--

--

Y

Y

KAVB5109

--

--

--

--

--

Y

Y

KAVB5110

Y

Y

--

--

--

Y

Y

KAVB5111

--

--

--

--

--

Y

Y

KAVB5112

--

--

--

--

--

Y

--

KAVB5150 to KAVB5151

Y

--

--

--

Y

--

--

KAVB5152

--

--

--

--

--

--

Y

KAVB5200 to KAVB5201

--

--

--

--

--

Y

--

KAVB5202 to KAVB5203

--

--

--

--

--

Y

Y

KAVB5250 to KAVB5254

--

--

--

--

--

Y

Y

KAVB5300 to KAVB5304

Y

--

--

--

--

--

Y

KAVB5350

--

--

--

--

Y

--

Y

KAVB5400 to KAVB5403

--

--

--

--

--

Y

Y

KAVB5450 to KAVB5453

--

--

--

--

Y

--

--

KAVB5454 to KAVB5460

--

--

--

--

--

Y

Y

KAVB5461

--

--

--

--

Y

--

--

KAVB5500

--

--

--

--

--

Y

--

KAVB5502

--

--

--

--

--

Y

--

KAVB5504

--

--

--

--

--

Y

--

KAVB5505

--

--

--

--

--

Y

Y

KAVB5506

--

--

--

--

--

Y

--

KAVB5511 to KAVB5561

--

--

--

--

--

Y

Y

KAVB5711 to KAVB5758

--

--

--

--

--

--

Y

KAVB5759

--

--

--

--

--

Y

Y

KAVB5760 to KAVB5762

--

--

--

--

--

--

Y

KAVB5800

--

--

--

Y

--

--

--

KAVB5801

--

--

--

--

--

Y

Y

KAVB5802 to KAVB5803

--

--

--

--

--

Y

--

KAVB5804

--

--

Y

--

--

--

--

KAVB5806

--

--

--

--

--

--

Y

KAVB5809 to KAVB5810

--

--

--

--

--

--

Y

KAVB5820 to KAVB5821

--

--

--

--

--

Y

--

KAVB5822

--

--

--

--

--

--

Y

#: If the status of the automated action is Fail, the message is displayed in the message area of the Action Log Details window.

1.2.6 Output destinations of messages related to Central Scope - View (KAVB6001 to KAVB6999)

This subsection shows the output destinations of messages related to JP1/IM Central Scope - View.

List of output destinations of messages related to Central Scope - View

Table 1-7 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

HNTRLib2: Integrated trace log file#

Dialog: Message dialog box

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒7: List of output destinations of messages related to Central Scope - View

Message ID

Output destination

HNTRLib2

Dialog

KAVB6006 to KAVB6007

--

Y

KAVB6011

--

Y

KAVB6013 to KAVB6015

--

Y

KAVB6016

--

Y

KAVB6018

--

Y

KAVB6019

Y

Y

KAVB6020 to KAVB6021

--

Y

KAVB6022

Y

Y

KAVB6023

--

Y

KAVB6024 to KAVB6025

Y

Y

KAVB6029 to KAVB6033

--

Y

KAVB6034

Y

--

KAVB6036

--

Y

KAVB6041

Y

--

KAVB6042

Y

Y

KAVB6043 to KAVB6044

--

Y

KAVB6046

Y

Y

KAVB6052 to KAVB6054

--

Y

KAVB6056 to KAVB6058

--

Y

KAVB6059 to KAVB6060

Y

Y

KAVB6063 to KAVB6065

Y

Y

KAVB6066 to KAVB6068

--

Y

KAVB6069

Y

--

KAVB6070

Y

Y

KAVB6071

--

Y

KAVB6072 to KAVB6073

Y

Y

KAVB6078 to KAVB6079

--

Y

KAVB6082 to KAVB6083

--

Y

KAVB6085 to KAVB6088

--

Y

KAVB6090 to KAVB6093

--

Y

KAVB6096 to KAVB6097

--

Y

KAVB6099

--

Y

KAVB6100 to KAVB6111

Y

Y

KAVB6112

--

Y

KAVB6113 to KAVB6115

Y

Y

KAVB6120

Y

Y

KAVB6121

Y

--

KAVB6193 to KAVB6195

--

Y

KAVB6196

Y

Y

KAVB6210 to KAVB6216

Y

Y

KAVB6218 to KAVB6220

Y

Y

KAVB6240 to KAVB6241

Y

Y

KAVB6250 to KAVB6252

Y

Y

KAVB6299 to KAVB6302

Y

Y

KAVB6305

Y

--

KAVB6306 to KAVB6312

Y

Y

KAVB6401

Y

--

KAVB6441 to KAVB6442

Y

--

KAVB6500 to KAVB6509

Y

Y

KAVB6550 to KAVB6551

Y

Y

KAVB6560 to KAVB6561

Y

Y

KAVB6570 to KAVB6571

Y

Y

KAVB6601 to KAVB6604

Y

Y

KAVB6610 to KAVB6616

Y

Y

1.2.7 Output destinations of messages related to Central Scope Service (KAVB7001 to KAVB7999)

This subsection shows the output destinations of messages related to JP1/IM Central Scope Service.

List of output destinations of messages related to Central Scope Service

Table 1-8 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log file#1

stdout: Standard output

stderr: Standard error

Dialog: Message dialog box

Event: JP1 event

JCSSETUP: jcs_setup.log (log file used for setup)#2

Logical host JCSSETUP: logical-host/jcs_setup.log (log file used for setup)#3

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#1: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

#2: Installation log files are stored in the following directory:

Windows: Not applicable

UNIX: /var/opt/jp1scope/log/JCS_SETUP/

#3: Logical host installation log files are stored in the following directory:

Windows: Not applicable

UNIX: /var/opt/jp1scope/log/JCS_SETUP/logical-host-name/

Table 1‒8: List of output destinations of messages related to Central Scope Service

Message ID

Output destination

syslog, event log

HNTR Lib2

stdout

stderr

Dialog

Event

JCS SETUP

Logical host JCSSETUP

KAVB7001 to KAVB7003

Y

Y

--

--

--

--

--

--

KAVB7004 to KAVB7007

--

Y

--

--

--

--

--

--

KAVB7100 to KAVB7115

--

Y

--

--

--

--

--

--

KAVB7116

Y

Y

--

--

--

--

--

--

KAVB7117 to KAVB7124

--

Y

--

--

--

--

--

--

KAVB7127 to KAVB7142

--

Y

--

--

--

--

--

--

KAVB7144 to KAVB7146

--

Y

--

--

--

--

--

--

KAVB7148

--

Y

--

--

--

--

--

--

KAVB7150 to KAVB7161

--

Y

--

--

--

--

--

--

KAVB7175 to KAVB7180

--

Y

--

--

Y

--

--

--

KAVB7182 to KAVB7185

--

Y

--

--

Y

--

--

--

KAVB7187 to KAVB7193

--

Y

--

--

Y

--

--

--

KAVB7194

--

Y

--

--

--

--

--

--

KAVB7196 to KAVB7198

--

Y

--

--

Y

--

--

--

KAVB7201

--

Y

--

--

Y

--

--

--

KAVB7202

--

--

--

--

Y

--

--

--

KAVB7204

--

--

--

--

Y

--

--

--

KAVB7206 to KAVB7207

--

--

--

--

Y

--

--

--

KAVB7209 to KAVB7210

--

--

--

--

Y

--

--

--

KAVB7212 to KAVB7213

--

--

--

--

Y

--

--

--

KAVB7232

--

Y

--

--

--

--

--

--

KAVB7233 to KAVB7248

--

Y

--

--

Y

--

--

--

KAVB7249 to KAVB7250

--

Y

--

--

--

--

--

--

KAVB7252

--

--

--

--

Y

--

--

--

KAVB7253

--

Y

--

--

--

--

--

--

KAVB7254 to KAVB7256

--

Y

--

--

Y

--

--

--

KAVB7257

--

Y

--

--

--

--

--

--

KAVB7258 to KAVB7267

--

Y

--

--

Y

--

--

--

KAVB7268

--

Y

--

--

--

--

--

--

KAVB7269

--

Y

--

--

Y

--

--

--

KAVB7272 to KAVB7274

--

Y

--

--

--

--

--

--

KAVB7276 to KAVB7282

--

Y

--

--

Y

--

--

--

KAVB7283

--

--

--

--

Y

--

--

--

KAVB7302 to KAVB7307

--

Y

--

--

Y

--

--

--

KAVB7350 to KAVB7366

--

--

--

--

Y

--

--

--

KAVB7367

--

Y

--

--

--

--

--

--

KAVB7368

--

--

--

--

Y

--

--

--

KAVB7377 to KAVB7398

--

Y

--

--

--

--

--

--

KAVB7399

--

--

--

--

Y

--

--

--

KAVB7400 to KAVB7420

--

Y

--

--

--

--

--

--

KAVB7450 to KAVB7453

--

Y

--

--

--

--

--

--

KAVB7455

--

Y

--

--

--

--

--

--

KAVB7457 to KAVB7460

--

Y

--

--

--

--

--

--

KAVB7462 to KAVB7465

--

Y

--

--

--

--

--

--

KAVB7470 to KAVB7471

--

Y

--

--

--

--

--

--

KAVB7473

--

Y

--

--

--

--

--

--

KAVB7475

--

Y

--

--

--

--

--

--

KAVB7479 to KAVB7480

--

Y

--

--

--

--

--

--

KAVB7482 to KAVB7485

--

Y

--

--

--

--

--

--

KAVB7487 to KAVB7488

--

Y

--

--

--

--

--

--

KAVB7491 to KAVB7494

--

Y

--

--

--

--

--

--

KAVB7496 to KAVB7498

--

Y

--

--

--

--

--

--

KAVB7550

--

Y

--

--

--

--

--

--

KAVB7552

--

Y

--

--

--

--

--

--

KAVB7555 to KAVB7560

--

Y

--

--

--

--

--

--

KAVB7580 to KAVB7586

--

Y

--

--

--

--

--

--

KAVB7600 to KAVB7601

--

Y

--

Y

--

--

--

--

KAVB7602 to KAVB7611

--

--

--

Y

--

--

--

--

KAVB7612 to KAVB7616

--

Y

--

Y

--

--

--

--

KAVB7617

--

--

--

Y

--

--

--

--

KAVB7618

--

Y

--

Y

--

--

--

--

KAVB7619

--

--

--

Y

--

--

--

--

KAVB7620 to KAVB7623

--

Y

--

Y

--

--

--

--

KAVB7624 to KAVB7635

--

--

--

Y

--

--

--

--

KAVB7636

--

Y

--

--

--

--

--

--

KAVB7637 to KAVB7638

--

Y

--

Y

--

--

--

--

KAVB7640 to KAVB7642

--

--

--

Y

--

--

--

--

KAVB7643 to KAVB7658

--

--

--

Y

--

--

--

Y

KAVB7660 to KAVB7667

--

--

--

Y

--

--

--

--

KAVB7670 to KAVB7671

--

--

--

Y

--

--

--

--

KAVB7680 to KAVB7686

--

--

--

Y

--

--

--

--

KAVB7687 to KAVB7688

--

Y

--

Y

--

--

--

--

KAVB7689 to KAVB7696

--

--

--

Y

--

--

--

--

KAVB7697

--

Y

--

Y

--

--

--

--

KAVB7698 to KAVB7702

--

--

--

Y

--

--

--

--

KAVB7703 to KAVB7706

--

Y

--

Y

--

--

--

--

KAVB7707

--

--

--

Y

--

--

--

--

KAVB7708 to KAVB7709

--

Y

--

Y

--

--

--

--

KAVB7711

--

Y

--

Y

--

--

--

--

KAVB7712

--

--

--

Y

--

--

--

--

KAVB7713

--

Y

--

Y

--

--

--

--

KAVB7714 to KAVB7715

--

--

--

Y

--

--

--

--

KAVB7722

--

--

--

Y

--

--

--

--

KAVB7723 to KAVB7725

--

Y

--

Y

--

--

--

--

KAVB7726

--

--

--

Y

--

--

--

--

KAVB7727

--

Y

--

Y

--

--

--

--

KAVB7730

--

--

--

Y

--

--

Y

--

KAVB7731

--

--

--

--

--

--

Y

--

KAVB7732

--

--

--

Y

--

--

Y

--

KAVB7733

--

--

--

--

--

--

Y

--

KAVB7734 to KAVB7737

--

--

--

Y

--

--

Y

--

KAVB7750 to KAVB7751

--

--

--

Y

--

--

--

--

KAVB7753 to KAVB7755

--

--

--

Y

--

--

--

--

KAVB7765 to KAVB7767

--

--

--

Y

--

--

--

--

KAVB7770

--

--

Y

--

--

--

--

--

KAVB7771 to KAVB7779

--

--

--

Y

--

--

--

--

KAVB7780

--

--

Y

--

--

--

--

--

KAVB7781 to KAVB7782

--

--

--

Y

--

--

--

--

KAVB7790 to KAVB7802

--

--

--

Y

--

--

--

--

KAVB7810

--

Y

--

Y

--

--

--

--

KAVB7812 to KAVB7814

--

Y

--

Y

--

--

--

--

KAVB7818

--

Y

--

Y

--

--

--

--

KAVB7900

--

--

--

--

--

Y

--

--

KAVB7901

--

Y

--

--

--

Y

--

--

1.2.8 Output destinations of JP1/IM-related common messages (KAVB8000 to KAVB8999)

This subsection shows the output destinations of JP1/IM-related common messages.

List of output destinations of JP1/IM-related common messages

Table 1-9 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log file#

stdout: Standard output

stderr: Standard error

Dialog: Message dialog box

Event: JP1 event

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒9: List of output destinations of JP1/IM-related common messages

Message ID

Output destination

Viewer

Manager

Dialog

stdout

stderr

HNTR Lib2

syslog, event log

stdout

stderr

HNTR Lib2

Event

KAVB8000 to KAVB8003

Y

--

--

Y

--

--

Y

Y

--

KAVB8051 to KAVB8055

--

--

--

--

--

--

--

Y

--

KAVB8060 to KAVB8063

--

--

--

--

Y

--

--

Y

Y

KAVB8064

--

--

--

--

--

--

--

Y

--

KAVB8070

--

--

--

--

--

--

--

Y

--

KAVB8072

--

--

--

--

--

--

Y#1

Y

--

KAVB8073

--

--

--

--

--

Y#1

--

Y

--

KAVB8074

--

--

--

--

--

--

Y

Y

--

KAVB8080

--

--

--

--

Y

--

--

Y

--

KAVB8101 to KAVB8106

--

--

--

--

--

--

--

Y

--

KAVB8107

Y

--

--

Y

--

--

--

--

--

KAVB8108

--

--

--

--

--

--

Y

--

--

KAVB8109

--

--

Y

--

--

--

--

--

--

KAVB8201 to KAVB8208

--

--

--

--

--

--

Y

--

--

KAVB8301 to KAVB8303

--

--

--

--

--

--

--

Y

--

KAVB8304 to KAVB8307

--

--

--

--

--

--

--

Y

--

KAVB8400

--

--

--

--

--

--

Y

--

--

KAVB8402 to KAVB8405

--

--

Y

--

--

--

Y

--

--

KAVB8406

--

Y

--

--

--

Y

--

--

--

KAVB8407

--

--

--

--

--

Y

--

--

--

KAVB8408 to KAVB8409

--

--

Y

--

--

--

Y

--

--

KAVB8410

--

--

Y

--

--

--

--

--

--

KAVB8411 to KAVB8412

--

--

--

--

--

--

Y

--

--

KAVB8413

--

--

Y

--

--

--

Y

--

--

KAVB8414

--

Y

--

--

--

Y

--

--

--

KAVB8415

--

--

--

--

--

--

Y

--

--

KAVB8416 to KAVB8417

--

--

--

--

--

Y

--

--

--

KAVB8418 to KAVB8422

--

--

--

--

--

--

Y

--

--

KAVB8423 to KAVB8424

--

--

--

--

--

Y

--

--

--

KAVB8425

--

--

--

--

--

--

Y

--

--

KAVB8426 to KAVB8427

--

--

--

--

--

Y

--

--

--

KAVB8428

--

--

--

--

--

--

Y

--

--

KAVB8430

--

--

--

--

--

--

Y

Y

--

KAVB8450 to KAVB8451

--

--

--

--

--

--

--

Y

--

KAVB8452

Y

--

--

--

--

--

--

--

--

KAVB8453 to KAVB8454

--

--

--

--

--

--

--

Y

Y

KAVB8456

--

--

--

--

--

--

--

Y

Y

KAVB8457

Y

--

--

Y

--

--

--

--

--

KAVB8500

--

--

--

--

--

--

Y

--

--

KAVB8550 to KAVB8552

Y

--

--

--

--

--

--

--

--

KAVB8600 to KAVB8602

--

--

--

--

--

--

--

Y

--

KAVB8603

--

--

--

--

--

Y

--

--

--

KAVB8604 to KAVB8610

--

--

--

--

--

--

--

Y

--

KAVB8701 to KAVB8728

--

--

--

--

--

--

Y

--

--

KAVB8729 to KAVB8735

--

--

--

--

--

Y

--

--

--

KAVB8736 to KAVB8737

--

--

--

--

--

--

Y

--

--

KAVB8738 to KAVB8739

--

--

--

--

--

--

Y

Y

--

KAVB8740 to KAVB8741

--

--

--

--

--

--

Y

--

--

KAVB8800 to KAVB8801

--

--

--

--

--

Y

--

--

--

KAVB8810 to KAVB8812

--

--

--

--

--

--

--

Y

--

KAVB8813 to KAVB8819

--

--

--

--

--

--

Y#2

Y

--

KAVB8820

--

--

--

--

--

--

--

Y

--

KAVB8900 to KAVB8905

--

--

Y

--

--

--

Y

--

--

KAVB8906 to KAVB8907

--

--

--

--

--

--

Y

--

--

KAVB8908 to KAVB8912

--

--

Y

--

--

--

Y

--

--

KAVB8913 to KAVB8916

--

--

--

--

--

--

Y

--

--

KAVB8917

--

--

Y

--

--

--

Y

--

--

KAVB8918

--

Y

--

--

--

Y

--

--

--

KAVB8919

--

--

Y

--

--

--

Y

--

--

KAVB8920

--

--

--

--

--

Y

--

--

--

KAVB8921 to KAVB8922

--

Y

--

--

--

Y

--

--

--

KAVB8923

--

--

Y

--

--

--

Y

--

--

KAVB8924 to KAVB8926

--

Y

--

--

--

Y

--

--

--

KAVB8927 to KAVB8931

--

--

Y

--

--

--

Y

--

--

KAVB8932

--

--

--

--

--

--

Y

--

--

KAVB8933

--

--

Y

--

--

--

Y

--

--

KAVB8934

--

Y

--

--

--

Y

--

--

--

KAVB8935

--

--

--

--

--

Y

--

--

--

KAVB8936 to KAVB8937

--

--

Y

--

--

--

Y

--

--

KAVB8938

--

Y

--

--

--

Y

--

--

--

KAVB8939

--

--

--

--

--

--

Y

--

--

KAVB8940 to KAVB8942

--

--

--

--

--

Y

--

--

--

KAVB8943

--

--

--

--

--

--

Y

--

--

KAVB8944 to KAVB8945

--

--

--

--

--

Y

--

--

--

KAVB8946

--

Y

--

--

--

Y

--

--

--

KAVB8947

--

--

Y

--

--

--

Y

--

--

#1: Displayed when the jcohctest command is executed.

#2: In UNIX, this is also output to standard error.

1.2.9 Output destinations of messages related to installation and setup (KAVB9001 to KAVB9999)

This subsection shows the output destinations of messages related to installation and setup of JP1/IM.

List of output destinations of messages related to installation and setup

Table 1-10 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace log file#1

stdout: Standard output

stderr: Standard error

Dialog: Message dialog box

JCOSETUP: jco_setup.log (log file used for setup)#2

Logical host JCOSETUP: logical-host/jco_setup.log (log file used for setup)#3

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#1: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

#2: Installation log files are stored in the following directory:

Windows: Not applicable

UNIX: /var/opt/jp1cons/log/JCO_SETUP/

#3: Logical host installation log files are stored in the following directory:

Windows: Not applicable

UNIX: /var/opt/jp1cons/log/JCO_SETUP/logical-host-name

Table 1‒10: List of output destinations of messages related to installation and setup

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

Dialog

JCOSETUP

Logical host JCOSETUP

KAVB9032

--

--

--

--

--

Y

Y

--

KAVB9033

--

--

--

--

--

--

--

--

KAVB9034 to KAVB9036

--

--

--

Y

--

--

Y

--

KAVB9038

--

--

--

--

Y

Y

Y

--

KAVB9039

--

--

--

--

--

--

Y

--

KAVB9051

--

--

--

Y

--

--

Y

--

KAVB9053

--

--

--

--

--

--

Y

--

KAVB9054

--

--

--

Y

--

--

Y

--

KAVB9056

--

--

--

--

--

--

Y

--

KAVB9057

--

--

--

Y

--

--

Y

--

KAVB9059

--

--

--

Y

--

--

Y

--

KAVB9064

--

--

--

Y

--

--

Y

--

KAVB9072 to KAVB9080

--

--

--

--

--

--

--

Y

KAVB9101 to KAVB9118

--

--

--

Y

--

--

--

--

KAVB9119

--

--

--

--

Y

--

--

--

KAVB9120

--

--

--

--

--

Y

--

--

KAVB9121

--

--

--

--

--

Y

--

--

KAVB9201 to KAVB9202

--

--

--

Y

--

--

--

--

KAVB9251 to KAVB9252

--

--

--

--

--

Y

--

--

KAVB9255 to KAVB9256

--

--

--

--

--

Y

--

--

KAVB9301 to KAVB9302

--

--

--

--

--

Y

--

--

KAVB9901 to KAVB9903

--

--

--

--

--

Y

--

--

KAVB9906 to KAVB9908

--

--

--

--

--

Y

--

--

KAVB9910

--

--

--

--

--

Y

--

--

KAVB9912 to KAVB9920

--

--

--

--

--

Y

--

--

KAVB9925 to KAVB9929

--

--

--

--

--

Y

--

--

KAVB9933 to KAVB9943

--

--

--

--

--

Y

--

--

KAVB9950 to KAVB9956

--

--

--

--

--

Y

--

--

KAVB9958 to KAVB9959

--

--

--

--

--

Y

--

--

KAVB9990 to KAVB9991

--

--

--

--

--

Y

--

--

KAVB9998 to KAVB9999

--

--

--

--

--

Y

--

--

1.2.10 Output destinations of messages related to the event generation function (KAJV2001 to KAJV3999)

This subsection shows the output destinations of messages related to the event generation function.

List of output destinations of messages related to the event generation function

Table 1-11 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

syslog: System log

Event log: Windows event log

HNTRLib2: Integrated trace logs#

stdout: Standard output

stderr: Standard error

JP1 event: JP1 event

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace logs are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒11: List of output destinations of messages related to the event generation function

Message ID

Output destination

syslog

Event log

HNTRLib2

stdout

stderr

JP1 event

KAJV2002 to KAJV2004

--

--

Y

--

--

--

KAJV2006 to KAJV2008

--

--

Y

--

--

--

KAJV2010 to KAJV2011

Y

Y

--

--

--

--

KAJV2016 to KAJV2017

--

--

Y

--

--

--

KAJV2020 to KAJV2021

--

--

Y

--

--

--

KAJV2101 to KAJV2103

Y

Y

Y

--

--

--

KAJV2104 to KAJV2106

--

--

Y

--

--

--

KAJV2107

Y

Y

Y

--

--

--

KAJV2108

--

--

Y

--

--

--

KAJV2109

Y

Y

--

--

--

--

KAJV2110 to KAJV2112

Y

Y

Y

--

--

--

KAJV2151

--

--

Y

--

--

--

KAJV2152

Y

Y

Y

--

--

--

KAJV2153 to KAJV2157

--

--

Y

--

--

--

KAJV2161 to KAJV2163

--

--

Y

--

--

--

KAJV2164

Y

Y

Y

--

--

--

KAJV2165

--

--

Y

--

--

--

KAJV2166

Y

Y

Y

--

--

--

KAJV2167 to KAJV2176

--

--

Y

--

--

--

KAJV2177

Y

Y

Y

--

--

--

KAJV2178 to KAJV2180

--

--

Y

--

--

--

KAJV2188

--

--

Y

--

--

Y

KAJV2190 to KAJV2192

--

--

Y

--

--

--

KAJV2194

--

--

Y

--

--

--

KAJV2201 to KAJV2208

--

--

Y

--

--

--

KAJV2210

--

--

Y

--

--

--

KAJV2231 to KAJV2233

--

--

Y

--

--

--

KAJV2234

--

--

Y

--

--

Y

KAJV2235 to KAJV2236

--

--

Y

--

--

--

KAJV2238 to KAJV2240

--

--

Y

--

--

--

KAJV2242 to KAJV2243

--

--

Y

--

--

Y

KAJV2244 to KAJV2246

--

--

Y

--

--

--

KAJV2248 to KAJV2252

--

--

Y

--

--

--

KAJV2301 to KAJV2305

--

--

Y

--

--

--

KAJV2308 to KAJV2317

--

--

Y

--

--

--

KAJV2320 to KAJV2321

--

--

Y

--

--

--

KAJV2322

--

--

Y

--

--

Y

KAJV2324 to KAJV2325

--

--

Y

--

--

--

KAJV2401 to KAJV2404

--

--

Y

--

--

--

KAJV2901 to KAJV2904

Y

Y

Y

--

--

--

KAJV2905

--

--

Y

--

--

--

KAJV2906 to KAJV2907

Y

Y

Y

--

--

--

KAJV3002 to KAJV3004

--

--

Y

--

Y

--

KAJV2500 to KAJV2501

--

--

Y

--

--

--

KAJV2502

--

--

Y

--

--

Y

KAJV2503

--

--

Y

--

--

--

KAJV3010

Y

Y

--

--

Y

--

KAJV3021 to KAJV3027

--

--

--

--

Y

--

KAJV3040

--

--

--

--

Y

--

KAJV3041 to KAJV3044

--

--

Y

--

Y

--

KAJV3101 to KAJV3104

--

--

Y

--

Y

--

KAJV3201

--

--

--

Y

--

--

KAJV3205 to KAJV3206

--

--

Y

--

Y

--

KAJV3209

--

--

Y

--

Y

--

KAJV3211 to KAJV3212

--

--

Y

--

Y

--

KAJV3214 to KAJV3218

--

--

Y

--

Y

--

KAJV3261 to KAJV3262

--

--

--

Y

--

--

KAJV3263

--

--

Y

--

Y

--

KAJV3264

--

--

--

Y

--

--

KAJV3265

--

--

Y

--

Y

--

KAJV3281

--

--

--

Y

--

--

KAJV3282

--

--

Y

--

Y

--

KAJV3283 to KAJV3285

--

--

--

Y

--

--

KAJV3286

--

--

Y

--

Y

--

KAJV3291

--

--

Y

Y

--

--

KAJV3292

--

--

Y

--

Y

--

KAJV3293

--

--

--

--

Y

--

KAJV3301

--

--

Y

Y

--

--

KAJV3302

--

--

Y

--

Y

--

KAJV3303

--

--

--

--

Y

--

KAJV3311 to KAJV3312

--

--

--

Y

--

--

KAJV3313 to KAJV3314

--

--

Y

--

Y

--

KAJV3315

--

--

--

--

Y

--

KAJV3316 to KAJV3318

--

--

Y

--

Y

--

KAJV3801

Y

Y

Y

--

Y

--

KAJV3901

--#

--#

--#

--#

--#

--#

KAJV3902 to KAJV3905

Y

Y

--

--

--

--

#: This message is output to the output destination of messages for which generation failed.

1.2.11 Output destinations of messages related to IM Configuration Management - View (KNAN20000 to KNAN21999)

This subsection shows the output destinations of messages related to JP1/IM Configuration Management - View.

List of output destinations of messages related to JP1/IM Configuration Management - View

Table 1-12 lists the output destinations (indicated by the abbreviations listed under Legend).

Legend:

Event log: Windows event log

Int. trace: Integrated trace log

Process: Dialog box displayed while processing is ongoing

Message dialog: Message dialog box

stdout: Standard output

stderr: Standard error

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

Table 1‒12: List of output destinations of messages related to IM Configuration Management - View

Message ID

Output destination

Event log

Int. trace log

Window

stdout

stderr

Message dialog

Process

Confirmation

Request

KNAN20000

--

Y

Y

--

--

--

--

KNAN20001 to KNAN20003

--

--

Y

--

--

--

--

KNAN20004

--

Y

Y

--

--

--

--

KNAN20005 to KNAN20006

--

--

Y

--

--

--

--

KNAN20007

--

--

--

--

--

--

--

KNAN20008

--

--

Y

--

--

--

--

KNAN20009

--

Y

--

--

--

--

--

KNAN20010

--

Y

Y

--

--

--

--

KNAN20011

--

--

--

--

--

--

--

KNAN20020 to KNAN20024

--

Y

--

--

--

--

--

KNAN20025 to KNAN20026

--

--

--

--

--

--

--

KNAN20030

--

--

Y

--

--

--

--

KNAN20040 to KNAN20044

--

--

Y

--

--

--

--

KNAN20045

--

--

--

Y

--

--

--

KNAN20046

--

--

--

--

--

--

--

KNAN20048

--

--

--

--

--

--

--

KNAN20050 to KNAN20052

--

--

Y

--

--

--

--

KNAN20054

--

Y

Y

--

--

--

--

KNAN20055 to KNAN20057

--

--

Y

--

--

--

--

KNAN20100 to KNAN20105

--

Y

Y

--

--

--

--

KNAN20121 to KNAN20124

--

Y

Y

--

--

--

--

KNAN20131 to KNAN20137

--

Y

Y

--

--

--

--

KNAN20141 to KNAN20144

--

Y

Y

--

--

--

--

KNAN20151 to KNAN20157

--

Y

Y

--

--

--

--

KNAN20200 to KNAN20207

--

--

Y

--

--

--

--

KNAN20220 to KNAN20227

--

--

--

Y

--

--

--

KNAN20228

--

--

Y

--

--

--

--

KNAN20230 to KNAN20233

--

--

--

Y

--

--

--

KNAN20234

--

--

Y

--

--

--

--

KNAN20238

--

--

--

--

--

--

--

KNAN20240 to KNAN20242

--

--

--

Y

--

--

--

KNAN20300

--

--

Y

--

--

--

--

KNAN20301 to KNAN20302

--

--

--

Y

--

--

--

KNAN20303

--

--

--

--

--

--

--

KNAN20320 to KNAN20323

--

--

--

Y

--

--

--

KNAN20324 to KNAN20325

--

--

Y

--

--

--

--

KNAN20326

--

--

--

Y

--

--

--

KNAN20329

--

--

--

Y

--

--

--

KNAN20330 to KNAN20331

--

--

Y

--

--

--

--

KNAN20333

--

--

Y

--

--

--

--

KNAN20352

--

--

--

Y

--

--

--

KNAN20353

--

--

Y

--

--

--

--

KNAN20354 to KNAN20355

--

--

--

Y

--

--

--

KNAN20356 to KNAN20357

--

--

Y

--

--

--

--

KNAN20358 to KNAN20359

--

--

--

Y

--

--

--

KNAN20360

--

--

Y

--

--

--

--

KNAN20362

--

--

--

Y

--

--

--

KNAN20363

--

--

Y

--

--

--

--

KNAN20364 to KNAN20365

--

--

--

--

--

--

--

KNAN20400 to KNAN20401

--

--

--

Y

--

--

--

KNAN20402

--

--

Y

--

--

--

--

KNAN20403 to KNAN20405

--

--

--

Y

--

--

--

KNAN20407 to KNAN20409

--

--

Y

--

--

--

--

KNAN20410

--

--

--

Y

--

--

--

KNAN20411 to KNAN20415

--

--

Y

--

--

--

--

KNAN20416

--

--

--

Y

--

--

--

KNAN20418 to KNAN20421

--

--

--

Y

--

--

--

KNAN20422 to KNAN20423

--

--

Y

--

--

--

--

KNAN20424 to KNAN20425

--

--

--

Y

--

--

--

KNAN20426 to KNAN20432

--

--

Y

--

--

--

--

KNAN20433

--

--

--

--

--

--

--

KNAN20437 to KNAN20438

--

--

Y

Y

--

--

--

KNAN20440

--

--

--

--

--

--

--

KNAN20441

--

--

Y

Y

--

--

--

KNAN20480 to KNAN20482

--

--

--

Y

--

--

--

KNAN20483 to KNAN20484

--

Y

Y

--

--

--

--

KNAN20500

--

--

--

Y

--

--

--

KNAN20510

--

--

Y

--

--

--

--

KNAN20513

--

--

--

Y

--

--

--

KNAN20514

--

--

Y

--

--

--

--

KNAN20515

--

--

--

Y

--

--

--

KNAN20516

--

--

Y

--

--

--

--

KNAN20520

--

--

Y

--

--

--

--

KNAN20530

--

--

--

Y

--

--

--

KNAN20800 to KNAN20801

--

Y

--

--

--

--

Y

KNAN20802

--

--

--

--

--

--

Y

KNAN20803

--

--

--

--

--

--

--

KNAN20810 to KNAN20815

--

--

--

--

--

--

Y

KNAN20816

--

Y

--

--

--

--

--

KNAN20820

--

--

--

--

--

Y

--

KNAN20821 to KNAN20822

--

--

--

--

--

--

Y

KNAN20823

--

Y

--

--

--

--

Y

KNAN20824

--

--

--

--

--

--

Y

KNAN20825 to KNAN20826

--

Y

--

--

--

--

Y

KNAN21000 to KNAN21005

--

--

Y

--

--

--

--

KNAN21055

--

--

Y

--

--

--

--

KNAN21151

--

--

Y

--

--

--

--

KNAN21154

--

--

Y

--

--

--

--

KNAN21157

--

--

Y

--

--

--

--

KNAN21162

--

--

Y

--

--

--

--

KNAN21165

--

--

Y

--

--

--

--

KNAN21168 to KNAN21179

--

--

Y

--

--

--

--

KNAN21180 to KNAN21181

--

--

--

Y

--

--

--

KNAN21183 to KNAN21187

--

--

Y

--

--

--

--

KNAN21300

--

--

Y

--

--

--

--

KNAN21301 to KNAN21304

--

--

--

Y

--

--

--

KNAN21305 to KNAN21308

--

--

Y

--

--

--

--

KNAN21309

--

--

--

Y

--

--

--

KNAN21310

--

--

--

--

--

--

--

KNAN21311

--

--

Y

--

--

--

--

KNAN21400 to KNAN21401

--

Y

Y

--

--

--

--

KNAN21402

--

--

Y

--

--

--

--

KNAN21403 to KNAN21409

--

Y

Y

--

--

--

--

KNAN21410 to KNAN21412

--

--

Y

--

--

--

--

1.2.12 Output destinations of messages related to IM Configuration Management (KNAN22000 to KNAN26999)

This subsection shows the output destinations of messages related to IM Configuration Management.

List of output destinations of messages related to IM Configuration Management

Table 1-13 lists the output destinations, and uses Legend as follows:

Legend:

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

Table 1‒13: List of output destinations of messages related to IM Configuration Management (part 1)

Message ID

Output destination

Standard output

Standard error

syslog, event log

Integrated log

KNAN22000 to KNAN22003

--

--

--

--

KNAN22004

--

--

--

Y

KNAN22005

--

--

--

--

KNAN22006

--

--

--

Y

KNAN22007 to KNAN22017

--

--

--

--

KNAN22019 to KNAN22030

--

--

--

--

KNAN22031

--

--

--

Y

KNAN22032 to KNAN22033

--

--

--

--

KNAN22050 to KNAN22057

--

--

--

--

KNAN22058

--

--

--

Y

KNAN22060 to KNAN22062

--

--

--

--

KNAN22063

--

--

--

Y

KNAN22064 to KNAN22065

--

--

--

--

KNAN22066

--

--

--

Y

KNAN22067

--

--

--

--

KNAN22068

--

--

--

Y

KNAN22069

--

--

--

--

KNAN22070

--

Y

--

--

KNAN22071 to KNAN22073

--

--

--

--

KNAN22100 to KNAN22104

--

Y

--

--

KNAN22200 to KNAN22201

--

--

--

--

KNAN22202

--

--

--

Y

KNAN22203 to KNAN22209

--

--

--

--

KNAN22220 to KNAN22221

--

--

--

--

KNAN22223 to KNAN22225

--

--

--

--

KNAN22240 to KNAN22241

--

--

--

Y

KNAN22243 to KNAN22245

--

--

--

--

KNAN22247 to KNAN22255

--

--

--

--

KNAN22263 to KNAN22267

--

--

--

--

KNAN22270

--

--

--

--

KNAN22271 to KNAN22274

--

--

--

Y

KNAN22300

--

--

--

--

KNAN22301 to KNAN22302

--

--

--

Y

KNAN22303

--

--

--

--

KNAN22304 to KNAN22306

--

--

--

Y

KNAN22307

--

--

--

--

KNAN22308 to KNAN22315

--

--

--

Y

KNAN22316 to KNAN22320

--

--

--

--

KNAN22321

--

--

--

Y

KNAN22400 to KNAN22415

--

--

--

--

KNAN22421 to KNAN22430

--

--

--

--

KNAN22432 to KNAN22433

--

--

--

--

KNAN22435

--

--

--

--

KNAN22437 to KNAN22449

--

--

--

--

KNAN22451

--

--

--

--

KNAN22455 to KNAN22461

--

--

--

--

KNAN22463 to KNAN22469

--

--

--

--

KNAN22471 to KNAN22488

--

--

--

--

KNAN22491 to KNAN22503

--

--

--

--

KNAN22505 to KNAN22507

--

--

--

--

KNAN22510 to KNAN22511

--

--

--

--

KNAN22514 to KNAN22515

--

--

--

--

KNAN22517 to KNAN22518

--

--

--

--

KNAN22520 to KNAN22521

--

--

--

--

KNAN22523 to KNAN22524

--

--

--

--

KNAN22526 to KNAN22534

--

--

--

--

KNAN22600 to KNAN22608

--

--

--

--

KNAN22700 to KNAN22702

--

--

--

--

KNAN22800

--

Y

--

--

KNAN22801 to KNAN22802

--

Y

--

Y

KNAN22803 to KNAN22812

--

Y

--

--

KNAN22814

--

Y

--

--

KNAN22816 to KNAN22817

--

Y

--

--

KNAN22819

--

Y

--

--

KNAN22820 to KNAN22822

Y

--

--

--

KNAN22823 to KNAN22832

--

Y

--

--

KNAN22833

--

--

--

--

KNAN22834 to KNAN22844

--

Y

--

--

KNAN22845

--

--

--

Y

KNAN22846

--

Y

--

Y

KNAN22847 to KNAN22849

Y

--

--

--

KNAN22850

--

Y

--

--

KNAN22854

--

Y

--

--

KNAN22857 to KNAN22858

--

Y

--

Y

KNAN22859 to KNAN22860

--

Y

--

--

KNAN22861

--

--

--

--

KNAN22862 to KNAN22863

--

Y

--

Y

KNAN22875 to KNAN22876

--

--

--

--

KNAN22890

--

Y

--

--

Table 1‒14: List of output destinations of messages related to IM Configuration Management (part 2)

Message ID

Output destination

Standard output

Standard error

Integrated log

KNAN23000

--

--

--

KNAN23001 to KNAN23003

--

--

Y

KNAN23004 to KNAN23006

--

--

--

KNAN23008 to KNAN23010

--

--

--

KNAN23011

--

--

Y

KNAN24000

--

Y

--

KNAN24001 to KNAN24008

--

Y

Y

KNAN24009

--

--

Y

KNAN24010 to KNAN24011

--

Y

Y

KNAN24012 to KNAN24016

--

Y

--

KNAN24017

--

--

Y

KNAN24018

--

Y

--

KNAN24030 to KNAN24031

Y

--

Y

KNAN24032 to KNAN24039

--

Y

Y

KNAN24040

--

--

Y

KNAN24041 to KNAN24042

Y

--

Y

KNAN24050 to KNAN24052

Y

--

Y

KNAN24053

--

Y

Y

KNAN24060 to KNAN24063

--

Y

Y

KNAN24070

--

Y

Y

KNAN24100 to KNAN24107

Y

--

--

KNAN24150 to KNAN24151

--

Y

--

KNAN24153

--

Y

--

KNAN24155

--

Y

--

Table 1‒15: List of output destinations of messages related to IM Configuration Management (part 3)

Message ID

Output destination

Standard output

Standard error

Event log

syslog

Integrated log

JP1 event

Dialog

KNAN26000 to KNAN26001

--

--

--

--

Y

--

--

KNAN26002

--

--

--

--

Y

Y

--

KNAN26003

--

Y

--

--

Y

--

--

KNAN26006

--

--

--

--

Y

--

--

KNAN26025

--

--

--

--

Y

--

--

KNAN26026 to KNAN26028

--

--

--

--

Y

Y

--

KNAN26039

--

--

--

--

Y

--

Y

KNAN26050

Y

--

--

--

--

--

--

KNAN26055

--

--

--

--

Y

--

--

KNAN26056

Y

--

--

--

Y

--

--

KNAN26057

--

--

--

--

Y

Y

--

KNAN26058

--

Y

--

--

Y

--

--

KNAN26063

--

Y

--

--

Y

--

--

KNAN26069

--

Y

--

--

--

--

Y

KNAN26072 to KNAN26073

--

--

--

--

Y

--

--

KNAN26078

--

--

--

--

Y

--

--

KNAN26081

--

--

--

--

Y

--

Y

KNAN26091

--

--

--

--

Y

Y

--

KNAN26092

--

Y

--

--

Y

--

--

KNAN26093

--

--

--

--

Y

--

--

KNAN26094 to KNAN26095

--

--

--

--

Y

Y

--

KNAN26097

--

Y

--

--

Y

--

--

KNAN26098

--

Y

--

--

--

--

--

KNAN26099

--

Y

--

--

Y

--

--

KNAN26101

--

--

--

--

Y

--

--

KNAN26102

--

--

--

--

Y

Y

--

KNAN26103 to KNAN26104

--

--

--

--

Y

--

--

KNAN26106

--

--

--

--

Y

--

--

KNAN26107

--

--

--

--

Y

Y

--

KNAN26108 to KNAN26109

--

--

--

--

Y

--

--

KNAN26119

--

Y

--

--

Y

--

--

KNAN26140

--

--

--

--

Y

Y

--

KNAN26142

--

--

--

--

Y

Y

--

KNAN26143

--

--

--

--

Y

--

--

KNAN26153

--

--

--

--

Y

--

--

KNAN26155

--

Y

--

--

Y

--

--

KNAN26163

--

--

--

--

Y

--

Y

KNAN26181 to KNAN26182

--

Y

--

--

Y

--

--

KNAN26187

--

--

--

--

Y

--

--

KNAN26189

--

--

--

--

Y

--

--

KNAN26196

--

--

--

--

Y

--

--

KNAN26206

--

--

--

--

Y

--

Y

KNAN26208

--

--

--

--

Y

--

Y

KNAN26209

--

Y

--

--

Y

--

--

KNAN26210

--

Y

--

--

--

--

Y

KNAN26211

--

Y

--

--

Y

--

Y

KNAN26212

--

--

--

--

Y

--

Y

KNAN26214

Y

--

--

--

--

--

--

KNAN26216 to KNAN26217

Y

--

--

--

--

--

--

KNAN26223 to KNAN26226

Y

--

--

--

--

--

--

KNAN26230

Y

--

--

--

--

--

--

KNAN26239

Y

--

--

--

--

--

--

KNAN26243

--

Y

--

--

Y

--

--

KNAN26247

--

Y

--

--

Y

--

--

KNAN26249

Y

--

--

--

--

--

--

KNAN26251 to KNAN26252

Y

--

--

--

--

--

--

KNAN26256

Y

--

--

--

--

--

--

KNAN26258

--

Y

--

--

Y

--

--

KNAN26261

Y

--

--

--

--

--

--

KNAN26266 to KNAN26267

--

Y

--

--

Y

--

--

KNAN26269

Y

--

--

--

--

--

--

KNAN26271

Y

--

--

--

--

--

--

KNAN26274

Y

--

--

--

--

--

--

KNAN26278 to KNAN26279

Y

--

--

--

--

--

--

KNAN26281

Y

--

--

--

--

--

--

KNAN26285

Y

--

--

--

--

--

--

KNAN26287

Y

--

--

--

--

--

--

KNAN26293 to KNAN26294

--

Y

--

--

Y

--

--

KNAN26296 to KNAN26297

--

Y

--

--

Y

--

--

KNAN26317 to KNAN26318

Y

--

--

--

--

--

--

KNAN26319 to KNAN26320

--

Y

--

--

--

--

--

KNAN26322

--

Y

--

--

Y

--

--

KNAN26326 to KNAN26327

Y

--

--

--

--

--

--

KNAN26328 to KNAN26332

--

Y

--

--

Y

--

--

KNAN26334

--

Y

--

--

Y

--

--

KNAN26336

--

Y

--

--

--

--

--

KNAN26337

--

Y

--

--

Y

--

--

KNAN26338

--

Y

--

--

Y

Y

--

KNAN26339 to KNAN26343

--

--

--

--

Y

Y

--

KNAN26344

--

--

--

--

Y

--

--

KNAN26345 to KNAN26346

--

--

--

--

Y

Y

--

KNAN26350 to KNAN26353

--

--

--

--

Y

Y

--

KNAN26354

--

Y

--

--

Y

--

--

1.2.13 Output destinations of IM Configuration Management messages common to all components (KNAN29000 to KNAN29999)

This subsection shows the output destinations of IM Configuration Management messages common to all components.

List of output destinations of IM Configuration Management messages common to all components

Table 1-16 lists the output destinations, and uses Legend as follows:

Legend:

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

Table 1‒16: List of output destinations of IM Configuration Management messages common to all components

Message ID

Output destination

Standard output

Standard error

syslog, event log

Integrated log

KNAN29000 to KNAN29002

--

--

Y

Y

KNAN29003 to KNAN29007

--

--

--

Y

KNAN29008

--

--

--

--

KNAN29009

--

--

--

Y

KNAN29010

--

--

--

--

KNAN29011 to KNAN29012

--

--

--

Y

KNAN29013

--

--

--

--

KNAN29014

--

--

--

Y

KNAN29015 to KNAN29018

--

--

--

--

KNAN29019 to KNAN29020

--

--

--

Y

KNAN29021 to KNAN29022

--

--

--

--

KNAN29023

--

--

--

Y

KNAN29024

--

--

--

--

KNAN29025 to KNAN29027

--

--

--

Y

KNAN29028 to KNAN29029

--

--

--

--

KNAN29030 to KNAN29033

--

--

--

Y

KNAN29034

--

--

--

--

KNAN29036 to KNAN29037

--

--

--

Y

KNAN29038

--

--

--

--

KNAN29041

--

--

--

Y

KNAN29045 to KNAN29047

--

--

--

--

KNAN29048

--

--

--

Y

KNAN29049 to KNAN29056

--

--

--

--

KNAN29057 to KNAN29059

--

--

--

Y

KNAN29060 to KNAN29064

--

--

--

--

KNAN29065

--

--

--

Y

KNAN29066 to KNAN29067

--

--

--

--

KNAN29069

--

--

--

--

KNAN29070 to KNAN29071

--

--

--

Y

KNAN29080 to KNAN29082

--

--

--

Y

KNAN29083 to KNAN29084

--

Y

--

--

KNAN29085 to KNAN29088

--

--

--

--

KNAN29090 to KNAN29091

--

--

--

Y

KNAN29093 to KNAN29095

--

--

--

Y

KNAN29097 to KNAN29099

--

--

--

Y

KNAN29900 to KNAN29007

--

Y

--

--

KNAN29909 to KNAN29014

--

Y

--

--

KNAN29920

Y

--

--

--

KNAN29921

--

--

--

--

KNAN29922

Y

--

--

--

KNAN29923

--

--

--

--

KNAN29924

Y

--

--

--

KNAN29926 to KNAN29927

Y

--

--

--

1.2.14 Output destinations of messages output to operation logs (KNAN30000 to KNAN30003)

This subsection shows the output destinations of messages output to operation logs.

Operation log messages are output to the operation log file. The output destination is specified in the operation log definition file (imm_operationlog.conf). The following shows the initial values of the output destination.

In Windows:

Manager-path\log\operationlog\imm_operation[n#].log

In UNIX:

/var/opt/jp1imm/log/operationlog/imm_operation[n#].log

#

n is a decimal number in the range from 1 to 16.

For details about operation log output, see Appendix K. Operation Log Output in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.

1.2.15 Output destinations of messages from the IM database (KNAN11005 to KNAN11210, KFPH00212 to KFPH00213, KFPS01850, and KFPS05210)

This subsection shows the output destinations of messages from the IM database.

List of output destinations of messages from the IM database

Table 1-17 lists the output destinations, and uses Legend as follows:

Legend:

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

Table 1‒17: List of output destinations of messages from the IM database

Message ID

Output destination

Standard output

Standard error

syslog, event log

Integrated log

KNAN11005 to KNAN11020

Y

--

--

--

KNAN11021 to KNAN11027

--

Y

--

--

KNAN11028

Y

--

--

--

KNAN11029 to KNAN11065

--

Y

--

--

KNAN11066

Y

--

--

--

KNAN11067 to KNAN11071

--

Y

--

--

KNAN11074 to KNAN11075

Y

--

--

--

KNAN11076 to KNAN11077

--

Y

--

--

KNAN11078 to KNAN11079

--

Y

--

Y

KNAN11080 to KNAN11089

--

Y

--

--

KNAN11090 to KNAN11093

--

--

--

Y

KNAN11094

--

Y

--

--

KNAN11095

Y

--

--

--

KNAN11096 to KNAN11099

--

Y

--

--

KNAN11100 to KNAN11107

Y

--

--

--

KNAN11108 to KNAN11109

--

Y

--

--

KNAN11110 to KNAN11112

Y

--

--

--

KNAN11113 to KNAN11123

--

Y

--

--

KNAN11124 to KNAN11125

Y

--

--

--

KNAN11140 to KNAN11145

--

Y

--

--

KNAN11146 to KNAN11148

Y

--

--

--

KNAN11150 to KNAN11151

Y

--

--

--

KNAN11152

--

Y

--

--

KNAN11153 to KNAN11154

Y

--

--

--

KNAN11155 to KNAN11157

--

Y

--

--

KNAN11158 to KNAN11159

Y

--

--

--

KNAN11160 to KNAN11161

--

Y

--

--

KNAN11162

Y

--

--

--

KNAN11163 to KNAN11175

--

Y

--

--

KNAN11176 to KNAN11189

Y

--

--

--

KNAN11190 to KNAN11193

--

Y

--

--

KNAN11194

Y

--

--

--

KNAN11195 to KNAN11196

--

Y

--

--

KNAN11197 to KNAN11198

Y

--

--

--

KNAN11199

Y

--

--

Y

KNAN11200 to KNAN11203

Y

--

--

--

KNAN11204 to KNAN11206

--

Y

--

--

KNAN11207 to KNAN11209

Y

--

--

--

KNAN11210

--

Y

--

--

KNAN11211 to KNAN11213

Y

--

--

--

KFPH00212 to KFPH00213

--

--

Y

--

KFPS01850

--

--

Y

--

KFPS05210

--

--

Y

--

1.2.16 Output destinations of messages related to the Intelligent Integrated Management Base (KAJY00001 to KAJY52032)

This subsection shows the output destinations of messages for the Intelligent Integrated Management Base.

List of output destinations of messages for the Intelligent Integrated Management Base

Legend:

syslog: System log

stdout: Standard output

stderr: Standard error

HNTRLib2: Integrated trace log file#

Dialog: Message dialog box

Integrated operation viewer: Integrated operation viewer window

REST API return value: REST API return value

Y: Message is output to the indicated destination.

--: Message is not output to the indicated destination.

#: Integrated trace log files are stored in the following directory:

Windows (32-bit): system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\

Windows (64-bit): system-drive\Program Files\Hitachi\HNTRLib2\spool\

UNIX: /var/opt/hitachi/HNTRLib2/spool/

Table 1‒18: List of output destinations of messages for the Intelligent Integrated Management Base

Message ID

Output destination

syslog, event log

stdout

stderr

HNTRLib2

Dialog

Integrated operation viewer

REST API return value

Response action execution history file

KAJY00001-E

--

--

--

--

Y

--

--

--

KAJY00004-I to KAJY00008-E

Y

--

--

Y

--

--

--

--

KAJY00009-E to KAJY00010-E

--

--

--

Y

--

--

Y

--

KAJY00011-E to KAJY00014-E

Y

--

--

Y

--

--

--

--

KAJY00015-W to KAJY00016-W

--

--

Y

Y

--

--

--

--

KAJY00017-E

Y

--

--

Y

--

--

Y

--

KAJY00018-E

--

--

--

Y

--

--

--

--

KAJY00019-W to KAJY00020-W

--

--

--

--

Y

--

--

--

KAJY00021-E to KAJY00022-E

--

--

--

Y

--

--

--

--

KAJY00023-W

--

--

--

--

Y

--

--

--

KAJY01000-E

--

--

--

Y

Y

--

Y

--

KAJY01001-E

--

--

--

--

--

Y

--

--

KAJY02000-E to KAJY02003-E

--

--

Y

Y

--

--

--

--

KAJY02004-E to KAJY02006-W

--

--

Y

--

--

--

--

--

KAJY02007-I to KAJY02010-I

--

Y

--

--

--

--

--

--

KAJY02011-E

--

--

Y

--

--

--

--

--

KAJY02012-E to KAJY02024-E

--

--

Y

Y

--

--

--

--

KAJY02025-W to KAJY02028-W

--

--

Y

--

--

--

--

--

KAJY02029-E to KAJY02030-E

--

--

Y

Y

--

--

--

--

KAJY02032-E to KAJY02033-E

--

--

Y

--

--

--

--

--

KAJY02034-I to KAJY02035-I

--

Y

--

--

--

--

--

--

KAJY02038-E

--

--

Y

Y

--

--

--

--

KAJY02039-W to KAJY02041-E

--

--

Y

--

--

--

--

--

KAJY02043-E to KAJY02044-E

--

--

Y

Y

--

--

--

--

KAJY02045-W to KAJY02046-W

--

--

--

Y

--

--

--

--

KAJY02047-E to KAJY02048-E

--

--

--

--

--

--

Y

--

KAJY02049-E to KAJY02050-E

--

--

--

--

--

--

Y

--

KAJY02051-E to KAJY02054-W

--

--

Y

--

--

--

--

--

KAJY02055-I

--

--

--

Y

--

--

--

--

KAJY04100-E to KAJY04260-E#

--

--

--

--

--

--

--

--

KAJY22000-W

--

--

--

--

--

Y

Y

--

KAJY22001-E to KAJY22005-E

--

--

--

Y

--

--

Y

--

KAJY22006-E to KAJY22008-E

--

--

--

--

--

Y

Y

--

KAJY22009-E to KAJY22011-E

--

--

--

--

--

--

Y

--

KAJY22012-W

--

--

--

--

--

Y

Y

--

KAJY22015-E

--

--

--

--

--

--

--

--

KAJY22018-E

--

--

Y

--

--

--

Y

--

KAJY22019-E to

KAJY22022-E

--

--

--

--

--

--

Y

--

KAJY22023-I to KAJY22025-E

--

--

--

--

--

--

--

Y

KAJY22026-W to KAJY22028-W

--

--

--

--

--

Y

Y

--

KAJY22029-W to KAJY22033-E

--

--

--

--

Y

--

--

--

KAJY22034-W

--

--

Y

--

--

--

Y

--

KAJY22035-W to KAJY22041-W

--

--

--

Y

--

--

--

--

KAJY22042-W

--

--

Y

--

--

--

Y

--

KAJY22043-E

--

--

--

--

--

--

--

--

KAJY22044-W to KAJY22046-E

--

--

--

Y

--

--

--

--

KAJY22047-W

--

--

--

--

--

Y

Y

--

KAJY24100-E to KAJY24261-W#

--

--

--

--

--

--

--

--

KAJY32000-E to KAJY32008-E

--

--

--

Y

Y

--

Y

--

KAJY32010-W

--

--

--

--

--

Y

Y

--

KAJY32100-E to KAJY32109-E

--

--

--

Y

Y

--

Y

--

KAJY32110-W

--

--

--

--

Y

--

Y

--

KAJY32200-E to KAJY32210-E

--

--

--

Y

--

--

Y

--

KAJY32211-E

--

--

--

--

Y

--

Y

--

KAJY32220-E

--

--

--

Y

--

--

Y

--

KAJY32221-E

--

--

--

--

--

Y

Y

--

KAJY52001-E to KAJY52002-E

--

--

--

--

--

Y

Y

--

KAJY52003-E

--

--

--

--

--

Y

--

--

KAJY52004-E to KAJY52005-E

--

--

--

--

--

Y

Y

--

KAJY52010-E

--

--

--

--

--

--

Y

--

KAJY52012-E

--

--

--

--

--

--

Y

--

KAJY52013-E to KAJY52014-E

--

--

Y

--

--

--

Y

--

KAJY52015-W

--

--

Y

--

--

--

--

--

KAJY52016-W to KAJY52019-W

--

--

--

Y

--

--

--

--

KAJY52020-E to KAJY52021-E

--

--

Y

--

--

--

--

--

KAJY52022-E to KAJY52023-E

--

--

Y

--

--

--

Y

--

KAJY52024-W to KAJY52025-W

--

--

--

Y

--

--

--

--

KAJY52026-E

--

--

Y

--

--

--

Y

--

KAJY52027-E to KAJY52028-E

--

--

--

Y

--

Y

Y

--

KAJY52029-E

--

--

Y

--

--

--

--

--

KAJY52030-E

--

--

--

--

--

--

Y

--

KAJY52031-W

--

--

Y

Y

--

--

Y

--

KAJY52032-W

--

--

--

Y

--

--

Y

--

#

The messages are output as fill characters of JP1/AJS or JP1/PFM messages.

1.3 Overview of message format

JP1/IM supports both Japanese and English messages. This section discusses the format of messages that are output by JP1/IM with a message ID. For details about other messages, see 11. Troubleshooting in the manual JP1/Integrated Management 2 - Manager Administration Guide.

1.3.1 Message output format

Each message consists of a message ID followed by the actual message text.

Message output format

KAVBnnnn-Z message-text

KAJVnnnn-Z message-text

KNANnnnn-Z message-text

KAJYnnnn-Z message-text

KFPHnnnn-Z message-text

KFPSnnnn-Z message-text

(1) Message ID

The message ID consists of a system identifier, message serial number, and message type.

Message ID components

K

Denotes the system identifier.

AVB, AJV, NAN, AJY, FPH, or FPS

Indicates that the message is a JP1/IM message.

nnnn

Displays the message's serial number.

Z

Indicates the message type:

E: Denotes an error message. Processing is suspended.

W: Denotes a warning message. Processing is resumed after the message is output.

I: Denotes a notification message. Messages of this type provide information to the user.

Q: Denotes a notification message. Messages of this type prompt the user to select an action.

1.3.2 Detailed information about communications errors

Some messages may output detailed information in the message text. The table below lists the detailed information numbers displayed in communications error messages such as KAVB1200-E, and describes the cause and the corrective action to take when the message is displayed.

Detailed information for communications error messages

The following table shows detailed information, the cause, and the corrective action to take.

Table 1‒19: Detailed information about communications error messages

Detailed information

Cause

Corrective action

B00

The manager host on which JP1/IM - Manager operates cannot be reached from JP1/IM - View.

Check the network configuration.

B01

JP1/IM - Manager is not running.

Check whether JP1/IM - Manager has started.

B02

An error occurred during creation of a socket when JP1/IM - View attempted to connect to JP1/IM - Manager.

Check whether a shortage occurred in OS resources such as file descriptors. If a resource shortage occurred, resolve it.

B04

The host name cannot be resolved.

Check the network configuration.

B05

An I/O error occurred during creation of a socket when JP1/IM - View attempted to connect to JP1/IM - Manager.

Check whether a shortage occurred in OS resources such as file descriptors. If a resource shortage occurred, resolve it.

B06

The host name cannot be resolved.

Check the network configuration.

B32

A timeout occurred between JP1/IM - View and JP1/IM - Manager.

Increase the value set to SO_TIMEOUT.

H00

The host name cannot be resolved.

Check the network configuration.

H01

A connection cannot be established through the specified port.

Check the port settings.

H02

A connection cannot be established to JP1/IM - Manager.

Check whether the host on which JP1/IM - Manager operates has started.

H03

The manager host on which JP1/IM - Manager operates cannot be reached from JP1/IM - View.

Check the network configuration.

Other than above

--

For the displayed message, perform the action indicated under O.

Legend:

--: Not applicable

1.4 List of system logs (syslogs) and Windows event logs

The table below lists the system logs (syslogs) and Windows event logs output by JP1/IM.

List of system logs (syslogs) and Windows event logs

The following table shows the correspondence between message IDs and information output to syslogs and Windows event logs.

Table 1‒20: List of system logs (syslogs) and Windows event logs

Message ID

UNIX (syslogs)

Windows

(application logs)

Facility

Level

Type

Event ID

Source

KAVB0001-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1211-W

LOG_DAEMON, LOG_USER

LOG_WARNING

Warning

1

One of the following:

JP1/ConsoleManager

JP1/ConsoleCmd

JP1/IM View

KAVB1501-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1502-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1510-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1517-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAVB1518-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAVB1519-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAVB1520-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1521-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1522-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1633-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1634-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1652-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB1656-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAVB2212-E

LOG_USER

LOG_ERR

--

--

--

KAVB2246-E

LOG_USER

LOG_ERR

--

--

--

KAVB2249-E

LOG_USER

LOG_ERR

--

--

--

KAVB2288-E

LOG_USER

LOG_ERR

--

--

--

KAVB2330-E

LOG_USER

LOG_ERR

--

--

--

KAVB2333-E

LOG_USER

LOG_ERR

--

--

--

KAVB3001-E to KAVB3004-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3007-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3501-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3516-E

LOG_USER

LOG_ERR

--

--

--

KAVB3613-W

LOG_USER

LOG_WARNING

Warning

2

JP1/Console

KAVB3614-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3620-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3621-E

LOG_USER

LOG_ERR

--

--

--

KAVB3623-E

LOG_USER

LOG_ERR

--

--

--

KAVB3624-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3626-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3643-E to KAVB3644-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3649-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3737-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3752-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3788-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3862-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3870-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3872-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3874-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB3875-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4004-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4022-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4050-I

LOG_DAEMON

LOG_INFO

Information

3

JP1/Console

KAVB4051-I

LOG_DAEMON

LOG_INFO

Information

3

JP1/Console

KAVB4054-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4153-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/Console

KAVB4154-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4250-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/Console

KAVB4251-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/Console

KAVB4254-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/Console

KAVB4700-I

LOG_DAEMON

LOG_INFO

Information

3

JP1/Console

KAVB4701-I

LOG_DAEMON

LOG_INFO

Information

3

JP1/Console

KAVB4702-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/Console

KAVB4901-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4902-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4903-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4904-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4905-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4906-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4907-E

LOG_DAEMON, LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB4908-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/Console

KAVB4909-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB5106-E

LOG_USER

LOG_ERR

Error

1

JP1/Console

KAVB7001-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/CentralScope

KAVB7002-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/CentralScope

KAVB7003-E

--

--

Error

1

JP1/CentralScope

KAVB7116-E

--

--

Error

1

JP1/CentralScope

KAVB8060-E

LOG_DAEMON

LOG_ERR

Error

1

One of the following:

JP1/Console

JP1/ConsoleManager

KAVB8061-I

LOG_DAEMON

LOG_INFO

Information

1

One of the following:

JP1/Console

JP1/ConsoleManager

KAVB8062-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAVB8063-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAVB8080-W

LOG_DAEMON

LOG_WARNING

Warning

1

JP1/ConsoleManager

KAJV2010-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2011-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2101-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAJV2102-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAJV2103-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2107-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2109-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2110-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAJV2111-I

LOG_DAEMON

LOG_INFO

Information

1

JP1/ConsoleManager

KAJV2112-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2152-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2164-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2166-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2177-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2901-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2902-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2903-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2904-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2906-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV2907-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV3010-E

LOG_USER

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV3801-E

LOG_USER

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV3901-E

--#

--#

--#

--#

JP1/ConsoleManager

KAJV3902-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV3903-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV3904-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KAJV3905-E

LOG_DAEMON

LOG_ERR

Error

1

JP1/ConsoleManager

KFPH00212-I

--

--

Information

30000

One of the following:

JP1/IM-M_DB_Server

JP1/IM-M_DB_Server_logical-host-name

KFPH00213-W

--

--

Information

30000

One of the following:

JP1/IM-M_DB_Server

JP1/IM-M_DB_Server_logical-host-name

KFPS01850-I

--

--

Information

30000

One of the following:

JP1/IM-M_DB_Server

JP1/IM-M_DB_Server_logical-host-name

KFPS05210-I

--

--

Information

30000

One of the following:

JP1/IM-M_DB_Server

JP1/IM-M_DB_Server_logical-host-name

Legend:

--: Message is not output.

#: This message outputs the message IDs of messages for which generation failed.

1.5 Actions to be taken by the system administrator in the event of a problem during operation

In the event of a problem during operation, see 11. Troubleshooting in the JP1/Integrated Management 2 - Manager Administration Guide, collect log information, and then perform an initial investigation.

To perform an initial investigation into the cause of the problem, see the OS log information (for Windows: Windows event log; for UNIX: system log) and the log information output by JP1/IM. Check the log information that was output around the time that the problem occurred, and either formulate a workaround for the problem or take corrective action to resolve the problem.

Additionally, record the operations and techniques that were used leading up to the occurrence of the problem. At the same time, try to reproduce the problem, if possible.

2 List of Messages

JP1/Integrated Management - Manager and JP1/Integrated Management - View output the following message IDs and associated messages.

2.1 Message description format

The following shows the format used in this manual to describe messages.

message-ID

English-message-text

Text describing a message

S:

Text indicating the processing performed by the system

O:

Text indicating the action to be taken by the operator when a message is output

2.2 Messages related to Central Console - View (KAVB0001 to KAVB2000)

KAVB0001-E

System error occurred.

Details: detailed-information

An unexpected error was detected during processing.

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0002-E

Specify the input-information.

A required item in the window is not entered.

S:

Waits for re-entry of information.

O:

Enter the missing item.

KAVB0003-E

Specify the input-information ranging from condition-1 to condition-2.

A value outside the specifiable range was entered in the input item in the window.

S:

Waits for re-entry of information.

O:

Enter the input item correctly.

KAVB0004-E

Failed to obtain the user profile.

The user profile could not be obtained.

S:

Aborts processing.

O:

Contact a system administrator.

KAVB0005-I

Updated the settings.

Updating of the items entered in the window has ended normally.

KAVB0007-E

Specify the input-information ranging from condition-1 to condition-2.

input-information: input-value

A value outside the specifiable range was entered in the input item in the window.

S:

Waits for re-entry of information.

O:

Enter the input item correctly.

KAVB0008-E

Failed to obtain the definition-file file.

Details: detailed-information

Due to the following reason(s), a view filter or event search log could not be obtained during startup processing.

A communication error occurred.

The definition file is corrupted.

S:

Continues startup processing using a filter for which no condition has been set.

O:

Restart JP1/IM - View.

If a KAVB1531-E message was output in the integrated trace log of the connected manager host, take the corrective action given for that message.

KAVB0009-E

Failed to obtain the definition-file file.

Details: detailed-information

A severe event filter, event acquisition filter, or user filter could not be obtained because a communication error occurred.

S:

Aborts processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB0010-E

Failed to update the definition-file file.

Details: detailed-information

The definition file of the server could not be updated.

S:

Aborts processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB0011-E

Add the input-information.

A required item has not been added.

S:

Waits for re-entry of information.

O:

Add the required input information, and then retry the operation.

KAVB0013-E

The input-information conditions exceed the maximum size (maximum-size).

The length of the input item in the window exceeds the maximum size.

S:

Waits for re-entry of information.

O:

Enter the input item correctly.

KAVB0014-E

The business group or monitoring group is not defined.

Definition information

Group name = group-name

A business group or monitoring group that has not been defined is specified.

S:

Waits for re-entry of information.

O:

Carefully review the specified business group or monitoring group.

If there is no problem, check with a system administrator to see if the specified business group or monitoring group has been defined.

KAVB0015-W

The configuration of a business group or monitoring group was changed while the settings window was displayed.

Do you want to continue?

The configuration of a business group or monitoring group was changed while the settings window was displayed. If you specified the business group or monitoring group, check whether the business group name and monitoring group name are correct.

S:

Continues processing with the specified settings if the Yes button is clicked. If the No button is clicked, the system cancels processing and returns to the settings window.

O:

If you specified the business group or monitoring group, check whether the business group name and monitoring group name are correct.

KAVB0061-E

The product information could not be acquired because there was not enough memory.

Detailed information: function-name, return-value

An attempt to acquire product information failed due to insufficient resources.

S:

Suspends processing.

O:

Make sure that there are sufficient system resources.

Resolve insufficient resources, and then retry the operation.

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0062-E

The product information could not be acquired because the environment is invalid.

Detailed information: function-name, return-value

An attempt to acquire the product information failed due to an invalid environment.

S:

Suspends processing.

O:

Determine whether a system error has occurred.

Uninstall and reinstall the program, and then retry the operation.

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0063-E

A system error occurred during startup of product-name.

A system error occurred during startup of product-name.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0101-E

Cannot connect to the connecting host.

Connection to the connecting host failed due to the following reason(s):

The entered connecting host name is incorrect.

The connecting host is not running.

An error occurred in communication with the connecting host.

If you use an integrated monitoring database, the IM database service is not in operating status.

S:

Aborts processing.

O:

Check the following items, and then retry the operation.

Is the entered connecting host name correct?

Is the connecting host running?

Is there a problem communicating with the connecting host?

If you use an integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service of the manager host. Confirm that the IM database service is running, and then retry the operation. If a KAVB8602-E message was output in the integrated trace log of the manager, take the corrective action given for that message.

KAVB0104-E

Failed to authenticate the user.

User authentication failed. The entered user name or password is incorrect.

S:

Waits for re-entry of information.

O:

Check the user name and password, and then retry the operation.

KAVB0105-E

Failed to authenticate the user.

Details: detailed-information

An incorrect authentication server name was set, or the host at the connection destination is incorrect.

S:

Waits for re-entry of information.

O:

Set the correct authentication server name in the environment settings.

KAVB0106-E

An error occurred in looking into the access authorization to JP1 resources.

Details: detailed-information

An error occurred while inquiring about permission to access JP1 resources.

S:

Waits for re-entry of information.

O:

Check the following items, and then take the appropriate corrective action:

If you are using the communication encryption function, check its settings for errors.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB0107-E

Failed to obtain product information.

Details: detailed-information

An attempt to acquire product information failed.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0108-E

An error occurred in the logout processing.

Connecting host:connecting-host

Details: detailed-information

An error occurred during logout processing.

S:

Waits for re-entry of information.

O:

Check the following items, and then take the appropriate corrective action:

If you are using the communication encryption function, check its settings for errors.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB0109-E

Communication error occurred between the connecting host and the authentication server.

Connecting host:connecting-host

A communication error occurred between the connecting host and the authentication server.

S:

Waits for re-entry of information.

O:

Check the following items, and then take the appropriate corrective action:

Is the authentication server running?

Is communication between the connecting host and the authentication server possible?

Are the authentication server settings correct?

KAVB0110-E

Failed to authenticate the user.

An attempt to authenticate the user failed.

S:

Aborts processing.

O:

Request a system administrator to set the JP1 resource group and JP1 permission level for the JP1 user.

KAVB0111-E

A connection to the authentication server could not be established.

A connection to the authentication server cannot be established from the connecting host.

S:

Aborts processing.

O:

Check the following items, and then take the appropriate corrective action:

Is the authentication server running?

Is communication between the connecting host and the authentication server possible?

Are the authentication server settings correct?

If you are using the communication encryption function, check its settings for errors.

KAVB0112-E

A communication error occurred in the logout processing.

Connecting host:connecting-host

jp1user-name:jp1user-name

An attempt to log out failed.

S:

Aborts processing.

O:

Check the following items, and then take the appropriate corrective action:

Is JP1/IM - Manager running on the connection host?

Has a network error occurred?

KAVB0121-E

Central Scope is not installed on the connection host.

Connection host:connecting-host

If the connecting host is JP1/IM - Manager (version 08-00 or later), the setting to start Central Scope Service and to distribute events to Central Scope Service has not been enabled.

S:

Waits for re-entry of information.

O:

Check the following items, and then log in to the system again.

If the connection host is JP1/IM - Manager (version 08-00 or later), has the setting to start Central Scope Service and to distribute events to Central Scope Service been enabled at the connection host?

KAVB0122-I

Closing the windows makes you log out. Are you sure you want to log out?

Confirms that it is OK to log out.

O:

Click the Yes button to log out. Click the No button to cancel logout.

KAVB0123-W

Central Scope is writing a file, so logout is not possible. Wait until the file output is finished.

You cannot log out because JP1/IM - Manager is outputting a file.

S:

Aborts logout processing and displays the Monitoring Tree window in the foreground.

O:

Wait until JP1/IM - Manager finishes file output, and then log out.

KAVB0201-I

The event selected will be deleted. Are you sure you want to do this?

Confirms that it is OK to delete the selected event from the screen.

O:

Click the Yes button to delete the selected event from the screen. Click the No button to cancel deleting the selected event from the screen.

KAVB0204-I

Are you sure to log out?

Confirms that it is OK to log out.

O:

Click the Yes button to log out. Click the No button to cancel logout.

KAVB0207-W

Your user profile is set up incorrectly. (File:filename)

The default settings will be used.

The user profile has been defined incorrectly.

O:

Collect the user profile displayed in the message box, and then contact a system administrator.

KAVB0208-I

The selected events will be released. Do you want to continue?

Confirms that it is OK to release the selected severe event(s).

O:

Click the Yes button to release the selected severe event(s). Click the No button to cancel releasing the selected severe event(s).

KAVB0209-I

The status of the selected event will be changed to action-status.

Are you sure you want to do this?

Confirms that it is OK to change the selected event status to action-status.

O:

Click the Yes button to change the selected event status to action-status. Click the No button to cancel changing the selected event status to action-status.

KAVB0210-E

The conditions for input-information is either duplicated.

The same condition was specified more than once for an input item in the window.

When multiple conditions can be specified, you cannot specify the same condition more than once.

S:

Waits for re-entry of information.

O:

Carefully review the conditions, and then retry the operation.

KAVB0211-E

The conditions for input-information is either duplicated.

input-information: input-value

The same condition was specified more than once for an input item in the window.

When multiple conditions can be specified, you cannot specify the same condition more than once.

S:

Waits for re-entry of information.

O:

Enter the input item correctly.

KAVB0212-Q

One or more of the selected events was acquired while the integrated monitoring database was in an invalid state.

The selected events (not including any that were acquired while the integrated monitoring database was in an invalid state) will be changed to action-status.

Do you want to continue?

When changing the action status of the selected events, events were found that were acquired while the integrated monitoring database was invalid.

S:

If the Yes button is clicked, the system changes the status of events other than those that were acquired while the integrated monitoring database was invalid. If the No button is clicked, the system suspends processing.

O:

For events for which the status could not be changed, specify the event database for the search object, and then retry the operation.

KAVB0213-Q

One or more of the selected events was acquired while the integrated monitoring database was in an invalid state.

The selected events (not including any that were acquired while the integrated monitoring database was in an invalid state) will be deleted.

Do you want to continue?

One or more of the selected events was acquired while the integrated monitoring database was invalid.

S:

If the Yes button is clicked, the system changes the status of events other than those acquired while the integrated monitoring database was invalid. If the No button is clicked, the system suspends processing.

O:

Log in to the system again.

KAVB0214-Q

One or more of the selected events was acquired while the integrated monitoring database was in an invalid state.

The selected events (not including any that were acquired while the integrated monitoring database was in an invalid state) will be released.

Do you want to continue?

One or more of the selected events were acquired while the integrated monitoring database was invalid.

S:

If the Yes button is clicked, the system releases events other than those acquired while the integrated monitoring database was invalid. If the No button is clicked, the system suspends processing.

O:

Log in to the system again.

KAVB0216-E

The selected events were acquired while the integrated monitoring database was in an invalid state.

The statuses of these events cannot be changed.

When the status was changed, all selected events were found to be events acquired while the integrated monitoring database was invalid.

S:

Suspends processing.

O:

For events whose status could not be changed, search events by specifying the event database for the search object, and then retry the operation.

KAVB0217-E

The selected events were acquired while the integrated monitoring database was in an invalid state.

These events cannot be deleted.

All selected events were found to be events that were acquired while the integrated monitoring database was invalid.

S:

Suspends processing.

O:

Log in to the system again.

KAVB0218-E

The selected events were acquired while the integrated monitoring database was in an invalid state.

These events cannot be released.

All selected events were found to be events that were acquired while the integrated monitoring database was invalid.

S:

Suspends processing.

O:

Log in to the system again.

KAVB0219-E

The selected events were acquired while the integrated monitoring database was in an invalid state.

No information related to these events can be acquired.

All selected events were found to be events that were acquired while the integrated monitoring database was invalid.

S:

Suspends processing.

O:

For events that could not be displayed, search events by selecting the event database for the search object, and then retry the operation.

KAVB0221-E

A common extended attribute cannot be specified.

You can only specify a unique extended attribute.

S:

Waits for re-entry of information.

O:

Common extended attributes cannot be mapped because they can be displayed as display items. Specify a unique extended attribute.

KAVB0223-E

The mapping of the event information to the display item (display-item) of the event ID (event-ID) is already defined.

More than one mapping is set for one display item for one event.

S:

Waits for re-entry of information.

O:

Only one mapping can be set for one display item for one event. Carefully review the contents of the mapping destination display item and event ID to avoid duplicate mappings for one displayed item.

KAVB0227-W

Reflecting the settings into the manager will affect the JP1/IM - View linked to the manager. Are you sure you want to do this?

When applying the settings in the manager, events displayed in the connected JP1/IM - View may change.

O:

Click the Yes button to apply the settings. Click the No button to cancel applying the settings.

KAVB0228-E

The event-information mapping definition was reflected in the manager, but the attempt to save the definition failed. When the manager stops, the current settings will be lost.

The mapping definition was applied in the manager, but because save processing failed, the setting will be lost when the manager is stopped.

S:

Mapping is functional because it was applied in the manager, but the system aborts save processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0229-I

Are you sure you want to cancel the notification suppression of function-name?

Confirms that it is OK to release notification suppression.

O:

Click the Yes button to release notification suppression. Click the No button to cancel releasing notification suppression.

KAVB0230-E

An attempt to cancel the notification suppression of function-name has failed. (detailed code=code)

An attempt to cancel notification suppression failed.

S:

Aborts processing.

O:

Retry the operation. If the same message is displayed, collect data, and then contact a system administrator.

KAVB0231-E

An attempt to obtain the notification status has failed.

An attempt to acquire function notification status failed.

S:

Aborts processing.

O:

Refresh the display of the event list. If the same message is displayed, collect data, and then contact a system administrator.

KAVB0232-W

These settings will be added to the first line of the definition, so that the added definition will have the highest priority level. If these settings are applied to the manager, JP1/IM - View will be affected because it is linked to the manager. Are you sure you want to apply these settings?

The settings are added to the beginning of the definition file to give the highest priority to the added severity change definition. If the settings are applied to the manager, the events displayed in JP1/IM - View connected to the manager might change.

S:

Click the Yes button to apply the settings. Click the No button to cancel applying the settings.

KAVB0233-Q

The setting details will be added to the beginning of the definition so that the added display message change definitions will have priority. If these setting details are applied to the manager, JP1/IM - View, which is linked to the manager, will be affected. Do you want to continue?

The setting details will be added to the beginning of the definition file so that the added display message change definitions will have priority. Applying these setting details to the manager might change the events displayed by JP1/IM - View, which is linked to the manager.

S:

Click the Yes button to apply the settings. Click the No button to cancel applying the settings.

KAVB0241-E

input-information is not a correct date or time information.

Date or time information entered in the window is incorrect.

S:

Waits for re-entry of information.

O:

Enter the correct date and time, and then retry the operation.

KAVB0243-E

The settings for an event ID is incorrect.

Specify the event ID in 8-digits hexadecimal number.

The event ID information entered in the window is incorrect.

S:

Waits for re-entry of information.

O:

Enter the correct event ID, and then retry the operation.

KAVB0244-E

The settings for an event ID is incorrect.

Specify the event ID in 8-digits hexadecimal number.

input-information: input-value

The event ID information entered in the window is incorrect.

S:

Waits for re-entry of information.

O:

Enter the correct event ID, and then retry the operation.

KAVB0245-E

Specify conditions for input-information.

No condition was set in the window for an item that requires setting of conditions.

S:

Waits for re-entry of information.

O:

Set conditions, and then retry the operation.

KAVB0246-E

The filter condition exceeds the maximum length. (Maximum length:maximum-length)

The total length of the filter condition statement set in the window exceeds the maximum length.

For event search: With JP1/Base (version 06-00 or earlier), the maximum length is 4,096 bytes, and with JP1/Base (version 06-51), the maximum length is 65,536 bytes.

For event acquisition filter: If an exclusion-condition group or common exclusion-condition group being applied has been set, the maximum length is 65,536 bytes; if not, it is 61,440 bytes. However, if the operation mode of the common exclusion-conditions is extended mode, the maximum length is 65,536 bytes for event acquisition conditions, and the maximum length is 10,485,760 bytes for common exclusion conditions (extended).

For severe event(s) filter: 65,536 bytes

For user filter: 1,048,576 bytes

For view filter: 1,048,576 bytes

S:

Waits for re-entry of information.

O:

Set conditions again, and then retry the operation.

KAVB0247-E

input-information exceeds the maximum number of items that can be input. (Maximum number: maximum-number)

The specified conditions exceed the maximum number that can be entered for the item.

S:

Waits for re-entry of information.

O:

Set conditions again, and then retry the operation.

KAVB0248-E

The settings for a regular expression is incorrect.

The specified regular expression is incorrect.

S:

For event search, event search is not executed. In this case, the system closes the Event Search Conditions window and returns to the Event Console window.

In the following filter settings windows, a message dialog box appears and the system waits for re-entry of information.

Event acquisition filter

Severe event(s) filter

User filter

View filter

O:

Set conditions again, and then retry the operation.

KAVB0249-W

The filter condition exceeds the maximum length. (maximum-length)The filtercondition can beedited or deleted,but cannot be added or copied.

You cannot add to or copy the filter condition statement because the total length of the filter condition statement set in the window exceeds the maximum.

S:

Waits for re-entry of information.

O:

Set conditions again, and then retry the operation.

KAVB0250-I

Do you really want to delete this filter?

Confirms that it is OK to delete the selected filter.

O:

Click the Yes button to delete the selected filter. Click the No button to cancel deleting the selected filter.

KAVB0251-E

The search cannot be performed for the specified condition because the search host's JP1/Base does not support the exclusion condition.

Event search including the exclusion-condition could not be performed because the search host's JP1/Base is earlier than version 08-50.

S:

The system does not perform event search.

O:

Check the JP1/Base version of the host specified as the event search execution host. To specify exclusion-conditions, JP1/Base version 08-50 or later must have been installed.

KAVB0252-E

The input-information is either duplicated.

The specified value was already specified.

S:

Waits for re-entry of information.

O:

Review the situation, and then retry the operation.

KAVB0253-Q

Are you sure you want to delete the selected items?

This message asks you to confirm that you want to delete the selected items.

S:

Click the Yes button to delete the selected item.

Click the No button to cancel the deletion of the selected item.

KAVB0255-E

The common extended attribute is already defined.

The condition cannot be entered more than once because a unique extended attribute is entered using an AND condition.

S:

Waits for re-entry of information.

O:

Carefully review the conditions, and then reconfigure the settings.

KAVB0256-E

The specified condition group name already exists.

You cannot specify a condition group name more than once in the list of condition groups.

S:

Waits for re-entry of information.

O:

Set conditions again, and then retry the operation.

KAVB0257-I

Are you sure you want to delete this condition group?

Confirms that it is OK to delete the selected condition group(s).

O:

Click the Yes button to delete the selected condition group(s). Click the No button to cancel deleting the selected condition group(s).

KAVB0258-E

Specify the condition group name.

No condition group name was set.

S:

Waits for re-entry of information.

O:

Set a condition group name, and then retry the operation.

KAVB0259-E

The specified filter name already exists.

You cannot specify the same filter name more than once.

S:

Waits for re-entry of information.

O:

Set conditions again, and then retry the operation.

KAVB0260-E

A filter being applied cannot be deleted.

You cannot delete the specified filter because the filter is being applied.

S:

Terminates processing and returns to the Event Acquisition Conditions List window.

O:

Switch the filter being applied to another condition, and then retry the operation.

KAVB0261-I

The search is complete.

Reports the end of event search.

KAVB0262-I

The search reached the end of the event database.

Event search from the beginning to the end of the event database is complete. To search events that were registered later than the event database, click the Search for Next Event button.

S:

Terminates processing.

KAVB0263-I

The search reached the beginning of the event database.

Event search from the end to the beginning of the event database is complete.

S:

Terminates processing.

KAVB0264-I

The search is complete.

Event search for the number of events to acquire in one search is complete.

S:

Terminates processing.

KAVB0265-I

The search has reached the end of the Integrated Monitoring Database.

Event search from the beginning to the end of the integrated monitoring database is complete.

S:

Terminates processing.

KAVB0266-I

The search has reached the beginning of the Integrated Monitoring Database.

Event search from the end to the beginning of the integrated monitoring database is complete.

S:

Terminates processing.

KAVB0267-E

The size of a common exclusion condition (extended) filter exceeds the limit. (condition group maximum size = 65,536 bytes)

The size of a common exclusion-condition filter in extended mode set in the window exceeds the maximum size.

S:

Waits for re-entry of information.

O:

Re-set the conditions, and then retry the operation.

KAVB0270-E

An attempt to switch the event acquisition filter failed for some controls.

An attempt to switch the event acquisition filter failed for some controls.

S:

Aborts switching of the event acquisition filter.

O:

Check the integrated trace log of the manager to see if an error message was output. If an error message was output, take the corrective action given for that message. If no message was output, use the data collection tool to collect data, and then contact a system administrator.

KAVB0271-E

An attempt to switch the event acquisition filter has failed.

An attempt to switch the event acquisition filter failed.

S:

Aborts switching of the event acquisition filter.

O:

Check the integrated trace log of the manager to see if an error message was output. If an error message was output, take the corrective action given for that message. If no error message was output, make sure that the KAVB4003-I message was output to the integrated trace log, and then retry the operation. If the KAVB4003-I message was not output and you are using an integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service. When you have confirmed that the IM database service is running and the KAVB4003-I message is output to the integrated trace log, retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB0281-E

The user (input-information) is either duplicated in a field or defined in another user's filter.

The same user was specified multiple times. Another possibility is that the user has already been defined for another user filter. You can define one user for one user filter.

S:

Waits for re-entry of information.

O:

Enter the target user name correctly, and then retry the operation.

KAVB0282-E

You cannot use a space character as a delimiter to specify input-information.

A space character was used incorrectly as a delimiter to specify multiple users. Use a comma as a delimiter to specify multiple users.

S:

Waits for re-entry of information.

O:

Correct the invalid space character entry, and then retry the operation.

KAVB0291-E

Failed to obtain detailed event information.

An unexpected error was detected while acquiring the detailed event information to be displayed from Central Console Manager.

S:

Aborts display of detailed event information.

O:

Collect the JP1/IM - View and JP1/IM - Manager data, and then contact a system administrator.

KAVB0292-I

Details cannot be displayed because no event is selected.

Detailed information cannot be displayed in the Event Details window because no event is selected in the Event Console window.

O:

Select an event in the Event Console window.

KAVB0293-I

Details cannot be displayed because multiple events are selected.

Detailed information cannot be displayed in the Event Details window because multiple events are selected in the Event Console window.

O:

Select one event in the Event Console window.

KAVB0301-E

System error occurred in Tool Launcher.

An unexpected error was detected during processing of the Tool Launcher window.

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0311-W

An event that is not in the manager was in the repeated events.

An event that is not in the manager was in the repeated events.

S:

Continues processing.

KAVB0312-E

The maximum number of events that can be changed at a time is the-maximum-number-of-scroll-buffers.

Please select the events again.

The maximum number of events for which the action status can be changed at one time is 2,000 in the Event Console window of JP1/IM - View. The total number of selected events (including non-consolidation events, consolidation events, and repeated events) exceeds the maximum number of events.

S:

Suspends processing. The system does not change the action status.

O:

Select events so that the total number of selected events (including non-consolidation events, consolidation events, and repeated events) is no more than 2,000 in the Event Console window of JP1/IM - View.

KAVB0321-Q

Are you sure you want to save the CSV file now? (file=file-name)

Confirms that it is OK to save the file.

S:

If the Yes button is clicked, the system saves the file.

If the No button is clicked, the system does not save the file.

KAVB0322-Q

Are you sure you want to overwrite the existing CSV file? (file=file-name)

Confirms that it is OK to overwrite the file.

S:

If the Yes button is clicked, the system overwrites the file.

If the No button is clicked, the system does not overwrite the file.

KAVB0323-E

An attempt to open the CSV file has failed. (details = detailed-information)

An attempt to open the CSV file failed.

S:

Suspends CSV file output processing.

O:

Take the corrective action given for the detailed information, and then retry the CSV output operation. If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0324-E

An attempt to lock the CSV file has failed. (file=file-name)

An attempt to acquire exclusive permission for the file failed.

S:

Suspends CSV file output processing.

O:

Check the following items, and then retry the CSV output operation.

Is another application locking the file?

Is output being attempted simultaneously for another file?

KAVB0325-E

An attempt to output the CSV file has failed. (file=file-name)

An attempt to output the file failed.

S:

Suspends CSV file output processing.

O:

Make sure there is sufficient free space at the CSV file output destination, and then retry the CSV output operation.

KAVB0326-E

A memory shortage occurred during output of the CSV file. (file=file-name)

A memory shortage occurred during output of the CSV file.

S:

Suspends CSV file output processing.

O:

Make sure sufficient free space is allocated, and then retry the CSV output operation.

KAVB0327-E

The file cannot be saved because the file name is too long. (file=file-name)

The CSV file name in the absolute path exceeds 259 characters.

S:

Suspends CSV file output processing.

O:

Reduce the length of the file name in the absolute path to 259 characters or fewer, and then retry the CSV output operation.

KAVB0328-E

The file cannot be saved because of an invalid file name. (file=file-name)

The file cannot be saved because an invalid file name is used. Invalid file names are as follows:

The name includes :, ?, ", <, >, or |.

The name is a complete match to CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, or LPT9 (including lower case).

In addition to 1 and 2 above, the file name includes .xxx (where xxx are any characters).

Examples: CON.txt, PRN.txt.csv

S:

Suspends CSV file output processing.

O:

Change the file name, and then retry the CSV output operation.

KAVB0329-E

An I/O error occurred during output of the CSV file. (file=file-name)

An I/O error occurred during output of the CSV file.

S:

Suspends CSV file output processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0341-W

The event database on host-name does not contain the related event. (serial number=serial-number-in-event-database)

An attempt was made to display a related event that does not exist in the event database of the host name.

This message is displayed when a new event exceeds the capacity of the event database on the manager, or when the event database is deleted.

S:

Continues displaying the related event.

O:

Check the following items:

Has the event database been deleted?

Is the capacity of the event database a small value?

KAVB0342-W

The related event cannot be displayed because it is filtered by the user filter. (serial number in the event database= serial-number-in-event-database)

An attempt was made to display a related event that could not be displayed because it was filtered by the user filter.

S:

Continues processing.

O:

Carefully review the user filter conditions.

KAVB0343-E

A system error occurred on the server during acquisition of the related event. (server name = server-name, reason = reason)

A system error occurred on the server during acquisition of the related event.

S:

Suspends acquisition of the related event.

O:

Determine whether an error has occurred in the network.

If there is no error in the network, use the data collection tool to collect data, and then contact a system administrator.

KAVB0344-E

A memory shortage occurred on the server during acquisition of the related event. (server name = server-name)

A memory shortage occurred on the server during acquisition of the related event.

S:

Suspends acquisition of the related event.

O:

Make sure sufficient free space is allocated.

If there is no memory shortage, use the data collection tool to collect data, and then contact a system administrator.

KAVB0345-E

The event buffer on the server cannot accept the acquisition of the related event. (server name = server-name)

The event buffer on the server is not in a status in which it can accept acquisition of the related event.

S:

Suspends acquisition of the related event.

O:

Wait awhile, and then retry the operation.

KAVB0346-E

A system error occurred while acquiring the related event from the event service on host-name. (reason = reason)

A system error occurred while acquiring the related event from Event Service on host-name.

S:

Suspends acquisition of the related event.

O:

Determine whether Event Service is running.

If Event Service is not running, start Event Service, and then restart the manager to recover from the error.

If the cause of the problem cannot be identified, use the data collection tool to collect data, and then contact a system administrator.

KAVB0347-E

The related event could not be acquired because it was not possible to connect to the event service on host-name.

Connection between the manager and event service cannot be established.

S:

Suspends acquisition of the related event.

O:

Determine whether Event Service is running.

If Event Service is not running, start Event Service, and then restart the manager to recover from the error.

KAVB0349-E

The related event could not be acquired because a communication error occurred with the event service on host-name.

A communication error occurred while the related event was acquired from Event Service on host-name. The possible causes are as follows:

The manager is not running.

Event Service is not running.

The processing request load is temporarily high.

S:

Suspends acquisition of the related event.

O:

Take corrective action as follows according to the cause of the error.

Confirm that the manager is running.

Confirm that Event Service is running.

Retry the operation. If the operation is not successful after the specified number of retries, restart the viewer, and then retry the operation.

KAVB0350-W

Manager host identification processing failed. The status of the related event cannot be changed.

The action status cannot be changed because the host from which the related event is acquired and the manager host cannot be identified.

S:

Displays the related event but does not change the action status for the displayed related event.

O:

Confirm that communication is established with the host that issues the display target event, and then retry the operation. If the system still cannot recover, use the data collection tool to collect data, and then contact a system administrator.

KAVB0351-E

The related event cannot be displayed because the data necessary for acquiring the event is not present.

The related event cannot be displayed because an internal error occurred.

S:

Continues processing without displaying the related event.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0352-E

The related event could not be acquired because an error occurred. (serial number in the event database = serial-number-in-event-database)

The related event could not be acquired because an error occurred.

S:

Suspends acquisition of the related event.

O:

Check the message displayed in the dialog box or output in the integrated trace log, and take the corrective action given for that message.

KAVB0353-W

The integrated monitoring database on host-name does not contain a related event. (serial number = serial-number-in-event-database)

An attempt was made to display a related event that does not exist in the integrated monitoring database on host-name.

This message is displayed when a new event exceeds the capacity of the event database on the manager, or the status of the integrated monitoring database is changed from valid to invalid, or vice versa, during correlation or consolidation.

S:

Continues displaying the related event.

O:

If the status of the integrated monitoring database was changed from valid to invalid, log in to the system again.

KAVB0354-I

A related event (event database serial number = event-database-serial-number) cannot be displayed because the user does not have the permissions necessary to reference the event.

An attempt to display a related event failed because the user did not have the permissions necessary to reference the event.

S:

Continues processing.

KAVB0361-E

An attempt to copy to the clipboard failed because the clipboard is full (bytes bytes).

An attempt to copy to the clipboard failed because the information copied to the clipboard exceeds the limit value (bytes).

S:

Suspends copying to the clipboard.

O:

Reduce the number of selected items, and then retry the operation.

KAVB0362-E

An attempt to copy to the clipboard failed because the clipboard is being used.

An attempt to copy to the clipboard failed because another application is using the clipboard.

S:

Suspends copying to the clipboard.

O:

Make sure that another application is not using the clipboard, and then retry the operation.

KAVB0363-E

A memory shortage occurred during processing to copy to the clipboard.

A memory shortage occurred during copying to the clipboard.

S:

Suspends copying to the clipboard.

O:

Make sure sufficient free space is allocated, and then retry the operation.

KAVB0364-E

An attempt to copy to the clipboard has failed. (reason = reason)

An attempt to copy to the clipboard failed.

S:

Suspends copying to the clipboard.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0368-W

There are no events in the integrated monitoring database that were registered before the specified period.

No events in the integrated monitoring database were registered before the specified period because the viewer host's start time is later than the manager host's start time.

S:

Disables the event display start-time specification area and continues processing.

O:

The viewer host's start time is later than the manager host's start time. Carefully review the setting of the viewer host's start time.

KAVB0371-E

The IM-View configuration file does not exist.

There is no IM - View configuration file.

S:

Continues processing using the default value.

O:

Check the definition file, and then restart JP1/IM - View. If there is no error in the definition file, use the data collection tool to collect data, and then contact a system administrator.

KAVB0372-E

An attempt to read the IM-View configuration file has failed. (reason = reason)

An attempt to read the IM - View configuration file failed.

S:

Continues processing using the default value.

O:

Confirm that the access permission is set correctly, and then restart JP1/IM - View. If there is no error in the definition file, use the data collection tool to collect data, and then contact a system administrator.

KAVB0373-E

A value defined for an item (item-name) in the IM-View configuration file is invalid. The default value (default-value) will be used.

A value defined for an item in the IM - View configuration file indicated in the message is incorrect.

S:

Continues processing using the default value indicated in the message.

O:

Correct the value in the IM - View configuration file, and then restart JP1/IM - View.

KAVB0374-E

A value defined for an item (item-name) in the IM-View configuration file is outside the valid range. The default value (default-value) will be used.

A value defined for an item in the IM - View configuration file indicated in the message is outside the valid range.

S:

Continues processing using the default value indicated in the message.

O:

Correct the value in the IM - View configuration file, and then restart JP1/IM - View.

KAVB0381-W

An error occurred during initialization processing necessary for outputting to the integrated trace log.

An error occurred during initialization processing for output to the integrated trace log. The message cannot be output to the integrated trace log.

S:

Continues processing.

O:

Determine whether the following service is running.

Hitachi Network Objectplaza Trace Monitor 2

If the service is not running, start the service, and then restart JP1/IM - View.

If the service is running, close the message box, and then restart JP1/IM - View.

If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB0391-E

The definition of the settings file(file-name) for consolidated display of repeated events is invalid. (Maintenance information = maintenance-information)

An invalid value is set in the settings file (file-name) for consolidated display of repeated events.

S:

Stops reading data from the settings file for consolidated display of repeated events and continues processing without the settings in the settings file for consolidated display of repeated events.

O:

In the Preferences window, reconfigure the consolidated display of repeated events.

Alternatively, if the settings file for consolidated display of repeated events has been backed up, stop JP1/IM - Manager, restore the settings file, and then restart JP1/IM - Manager.

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0392-E

The definition of the view filter definition file(file-name) is invalid. (maintenance information = maintenance-information)

An invalid value is set in the view filter definition file.

S:

Stops reading data from the view filter definition file and continues processing without the settings of the view filter.

O:

In the View List of Filters window, reconfigure the view filter.

Alternatively, if the view filter definition file (file-name) has been backed up, stop JP1/IM - Manager, restore the definition file, and then restart JP1/IM - Manager.

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0393-E

The definition of the event acquisition filter definition file(file-name) is invalid. (maintenance information = maintenance-information)

An invalid value is set in the event acquisition filter definition file.

S:

Stops reading data from the event acquisition filter definition file and continues processing. The System Environment Settings window can no longer be started from JP1/IM - View.

O:

If the event acquisition filter definition file (file-name) has been backed up, stop JP1/IM - Manager, restore the definition file, and then restart JP1/IM - Manager.

If the event acquisition filter definition file has not been backed up, stop JP1/IM - Manager, and then use the following procedure to restore the initial status of the event acquisition filter (the filter that acquires events other than JP1/SES events). After that, start JP1/IM - Manager and reconfigure the event acquisition filter.

To restore the initial status of the event acquisition filter:

In Windows:

Restoring the physical host:

cd console_path\conf\console\filter

copy receive_filter.conf.model receive_filter.conf

Restoring the logical host:

cd shared_folder\jp1cons\conf\console\filter

copy receive_filter.conf.model receive_filter.conf

In UNIX:

Restoring the physical host:

cd /etc/opt/jp1cons/conf/console/filter

cp -p receive_filter.conf.model receive_filter.conf

Restoring the logical host:

cd common-directory/jp1cons/conf/console/filter

cp -p receive_filter.conf.model receive_filter.conf

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0394-E

The definition of the event acquisition filter list file(file-name) is invalid. (maintenance information = maintenance-information)

An invalid value is set in the storage file for the event acquisition filter lists.

S:

Stops reading data from the storage file for event acquisition filter lists and continues processing. The System Environment Settings window can no longer be started from JP1/IM - View.

O:

If the storage file for event acquisition filter lists (file-name) has been backed up, stop JP1/IM - Manager, restore the storage file, and then restart JP1/IM - Manager.

If the storage file for event acquisition filter lists has not been backed up, stop JP1/IM - Manager, and then use the following procedure to delete the storage file for event acquisition filter lists. After that, start JP1/IM - Manager and reconfigure the event acquisition filter.

To delete the storage file for event acquisition filter lists:

In Windows:

Deleting the physical host:

cd console_path\conf\console\filter

del file-name (receive_filter_list.conf)

Deleting the logical host:

cd common_folder\jp1cons\conf\console\filter

del file-name (receive_filter_list.conf)

In UNIX:

Deleting the physical host:

cd /etc/opt/jp1cons/conf/console/filter

rm file-name (receive_filter_list.conf)

Deleting the logical host:

cd shared_directory/jp1cons/conf/console/filter

rm file-name (receive_filter_list.conf)

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0395-E

The definition of the event search filter definition file(file-name) is invalid. (maintenance information = maintenance-information)

An invalid value is set in the event search filter definition file.

S:

Stops reading data from the event search filter definition file and continues processing without the event search condition settings.

O:

In the Event Search Conditions window, set the event search condition again.

Alternatively, if the event search filter definition file (file-name) has been backed up, stop JP1/IM - Manager, restore the definition file, and then restart JP1/IM - Manager.

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0396-E

The definition of the severe event(s) filter definition file(file-name) is invalid. (maintenance information = maintenance-information)

An invalid value is set in the event acquisition filter definition file.

S:

Terminates Event Console Service.

O:

If the severe event(s) filter definition file (file-name) has been backed up, stop JP1/IM - Manager, restore the definition file, and then restart JP1/IM - Manager.

If the severe event(s) filter definition file has not been backed up, stop JP1/IM - Manager, and then use the following procedure to delete the severe event(s) filter definition file. After that, start JP1/IM - Manager and reconfigure the severe event(s) filter.

To delete the severe event(s) definition file:

In Windows:

Deleting the physical host:

cd console_path\conf\console\filter

del file-name (serious_filter_ex.conf)

Deleting the logical host:

cd shared_folder\jp1cons\conf\console\filter

del file-name (serious_filter_ex.conf)

In UNIX:

Deleting the physical host:

cd /etc/opt/jp1cons/conf/console/filter

rm file-name (serious_filter_ex.conf)

Deleting the logical host:

cd shared_directory/jp1cons/conf/console/filter

rm file-name (serious_filter_ex.conf)

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0397-E

The definition of the event receiver filter definition file(file-name) is invalid. (maintenance information = maintenance-information)

An invalid value is set in the user filter definition file.

S:

Terminates Event Console Service.

O:

If the user filter definition file (file-name) has been backed up, stop JP1/IM - Manager, restore the definition file, and then restart JP1/IM - Manager.

If the user filter definition file has not been backed up, stop JP1/IM - Manager, and then use the following procedure to delete the user filter definition file. After that, start JP1/IM - Manager and reconfigure the user filter.

To delete the user filter definition file:

In Windows:

Deleting the physical host:

cd console_path\conf\console\filter

del file-name (user_filter_ex.conf)

Deleting the logical host:

cd shared_folder\jp1cons\conf\console\filter

del file-name (user_filter_ex.conf)

In UNIX:

Deleting the physical host:

cd /etc/opt/jp1cons/conf/console/filter

rm file-name (user_filter_ex.conf)

Deleting the logical host:

cd shared_directory/jp1cons/conf/console/filter

rm file-name (user_filter_ex.conf)

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB0401-E

System error occurred in the command execution screen.

An unexpected error was detected during processing of the Execute Command window.

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0411-E

Cannot initialize the command execution session.

Reason:reason

An error was detected during command execution session initialization.

S:

Aborts processing.

O:

If you are using the communication encryption function, check its settings for errors.

If you are not using the communication encryption function, check the following items depending on the reason that is displayed:

The port number is invalid.

Check the specified port number.

Fail to connect JP1/Base.

An attempt to connect to JP1/Base of the connected server failed. JP1/Base of the connected server may not be running. Check the connected server status. Also, a communication error may have occurred. Check the status of the connection with the server.

Connection has timed out.

A time-out occurred due to a high load on the server or network. Wait awhile, and then retry the operation.

There is a bad response from the server.

Socket error occurred.

Connection has failed.

A communication error occurred. Check the status of the connection with the server.

Reasons other than the above

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0412-E

An error occurred in terminating the command execution session.

Reason:reason

An error was detected during termination of the command execution session.

S:

Aborts processing.

O:

Refer to the KAVB0411-E message.

KAVB0413-E

An error occurred in executing the command.

Reason:reason

An error was detected in the command execution session during execution of a command.

S:

Aborts command processing.

O:

If you are using the communication encryption function, check its settings for errors.

If you are not using the communication encryption function, check the length of the values entered, depending on the reason that is displayed, and then retry the operation.

The length of the hostname is incorrect.

The length of the command is incorrect.

The length of the environment parameter is incorrect.

For other than the above, refer to the KAVB0411-E message.

KAVB0414-E

An error occurred while receiving the execution result of command.

Reason:reason

An error was detected in the command execution session during reception of the command execution result. The execution result of the command being executed or the preceding command cannot be acquired.

S:

Aborts processing.

O:

Refer to the KAVB0411-E message.

KAVB0415-E

The command cannot be executed because the business group or monitoring group specified for the execution host name is not defined. (execution host name = execution-host-name)

The command could not be executed because the business group or monitoring group specified for the execution host name was not defined.

You cannot use the JP1/Base jcocmdshow command to check this message.

S:

Aborts processing.

O:

Carefully review the business group or monitoring group specified for the execution host name, and then re-execute the command. If the command still cannot be executed, contact a system administrator and check the business group settings.

KAVB0416-E

The command cannot be executed because the host specified for the execution host name is not a management target. (execution host name = execution-host-name)

The command could not be executed because the host specified for the execution host name was not the management target.

You cannot use the JP1/Base jcocmdshow command to check this message.

S:

Aborts processing.

O:

Carefully review the host sepcified for the execution host name, and then re-execute the command. If the command still cannot be executed, contact a system administrator and check the business group settings.

KAVB0417-E

The command cannot be executed because the user does not have the permissions necessary to execute it on the business group specified in the execution host name. (execution host name = execution-host-name)

The command could not be executed because the user did not have the permissions necessary to execute the command for the business group specified for the execution host name.

You cannot use the JP1/Base jcocmdshow command to check this message.

S:

Aborts processing.

O:

Carefully review the business group or monitoring group specified for the execution host name, and then re-execute the command. If the command still cannot be executed, contact a system administrator and check the business group settings.

KAVB0418-E

The command cannot be executed because the user does not have the permissions necessary to execute on the host specified in the execution host name. (execution host name = execution-host-name)

The command could not be executed because the user did not have the permissions necessary to execute the command on the host specified for the execution host name.

You cannot use the JP1/Base jcocmdshow command to check this message.

S:

Aborts processing.

O:

Carefully review the host sepcified for the execution host name, and then re-execute the command. If the command still cannot be executed, contact a system administrator and check the business group settings.

KAVB0419-E

The command cannot be executed because a host group is defined with the same name as the host name specified for the execution host name. (execution host name = execution-host-name)

The command cannot be executed for a host group.

S:

Aborts processing.

O:

Contact a system administrator and check the host group settings.

KAVB0422-E

A host is not defined for the business group or monitoring group. (group name = group-name)

The command could not be executed because no host was defined for the business group or monitoring group.

S:

Does not execute the command.

O:

Carefully review the specified business group or monitoring group.

If there is no problem, check with a system administrator to see if a host is defined for the specified business group or monitoring group.

KAVB0423-E

The business group or monitoring group is not defined. (group name = group-name)

The command could not be executed because the business group or monitoring group was not defined.

S:

Does not execute the command.

O:

Carefully review the specified business group or monitoring group.

If there is no problem, check with a system administrator to see if the specified business group or monitoring group has been defined.

KAVB0424-E

A execution host name is invalid.

Processing could not continue because the execution host name was invalid.

S:

Suspends processing.

O:

Carefully review the execution host name, and then re-execute the command.

KAVB0451-W

Failed to read the input history.

An attempt to read the input history failed.

S:

Continues processing without the input history information.

KAVB0452-W

Failed to save the input history.

An attempt to write the input history failed.

S:

Continues processing without the input history information.

KAVB0502-I

Are you sure to close without pressing the "Apply" button?

The settings are not valid until you click the Apply button. You are closing the window without clicking the Apply button.

If you click the Yes button, the window is closed without applying the settings. If you click the No button, the window remains open.

O:

Click the Yes button to close the window without applying the settings. Click the No button to cancel closing the window.

KAVB0503-I

Are you sure to delete this line?

Confirms that it is OK to delete the selected line.

O:

Click the Yes button to delete the selected line. Click the No button to cancel deleting the selected line.

KAVB0504-E

Failed to obtain the result of an action.

An attempt to acquire the action result information failed.

S:

Aborts processing.

O:

Perform the operation again.

KAVB0505-E

Failed to read/write/update the action definition.

An attempt to read, write, or update the action definition failed.

S:

Aborts processing.

O:

Perform the operation again.

KAVB0507-E

Do not input \ at the end of an action.

A backslash (\) was entered at the end of the action.

S:

Waits for re-entry of information.

O:

Carefully review the action to be input, and then perform the operation again.

KAVB0508-E

The settings for setting-item are incorrect.

The settings for setting-item are incorrect.

S:

Waits for re-entry of information.

O:

Perform the operation again.

KAVB0509-E

The extended attribute name was specified incorrectly.

You can use capital letters, numerics, and underlines only.

The name must begin with a capital letter.

The extended attribute was specified incorrectly.

S:

Waits for re-entry of information.

O:

Perform the operation again.

KAVB0510-E

You can specify up to 100 discretionary extend attributes.

The number of specified extended attributes exceeds 100 items.

S:

Waits for re-entry of information.

O:

Specify a maximum of 100 extended attributes.

KAVB0511-E

An action name is duplicated.

An action with the same action name has already been set.

You cannot specify an action name that is already being used.

S:

Waits for re-entry of information.

O:

Specify the action name again, and then retry the operation.

KAVB0512-E

The combination of comparison conditions among multiple event attributes that have the same name is invalid.

The combination of comparison keywords of event conditions for multiple attributes is invalid.

S:

Waits for re-entry of information.

O:

Specify another event condition, and then retry the operation.

KAVB0513-Q

One or more event conditions have not been set up.

The event conditions that have not been set up will be excluded. Do you want to continue?

Confirms that it is OK to exclude unspecified event conditions.

S:

If the Yes button is clicked, the system excludes the unspecified event conditions and continues processing.

If the No button is clicked, the system suspends processing.

O:

Delete the unspecified event conditions, or specify event conditions.

KAVB0514-E

The total number of characters (bytes) in the operands exceeds the maximum (maximum-length).

The total length of the attribute value of the specified event condition exceeds the maximum length.

S:

Waits for re-entry of information.

O:

Specify the event condition again, and then retry the operation.

KAVB0515-E

When you specify an execution-option, specify an action.

You specified an execution option without specifying an action.

S:

Waits for re-entry of information.

O:

Carefully review the execution details, and then retry the operation.

KAVB0516-E

The number of characters (bytes) in the operands exceeds the maximum (maximum-length).

The attribute value of the specified event condition exceeds the maximum length.

S:

Waits for re-entry of information.

O:

Specify the event condition again, and then retry the operation.

KAVB0517-W

Using the regular expression you specified, the processing to match JP1 events will take a long time. This will affect the performance of event reception. Are you sure you want to apply this expression?

cause: cause

If you use the specified regular expression, the processing to match JP1 events will take a while. This will affect the performance of event reception.

S:

Click the Yes button to apply the specified regular expression. Click the No button to cancel applying the specified regular expression.

O:

Correct the regular expression for which the processing to match JP1 events will take a while.

".*" is specified at the beginning or the end.

Delete the asterisk (*) specified at the beginning or the end.

".*" is specified repeatedly.

Use only one instance of .* at the location where it is repeated.

KAVB0518-E

An action ID is duplicated.

An action with the same action ID has already been set.

You cannot set the same action ID.

S:

Waits for re-entry of information.

O:

Set a different action ID and re-execute.

KAVB0531-I

Are you sure to require re-execution?

Confirms that it is OK to send a request for re-execution to the selected automated action.

O:

Click the Yes button to send the request for re-execution. Click the No button to cancel sending the request for re-execution.

KAVB0532-I

The list of action results was updated.

Updating of the list of action results finished normally.

KAVB0533-I

No action result corresponds to the update setting.

There is no action result that corresponds to the update condition.

The possible causes are as follows:

There is no action result that corresponds to the update condition.

The information in the action information file was overwritten.

O:

Carefully review the update condition.

If the update condition is correct, carefully review the capacity of the action information file.

KAVB0535-I

The cancel request will be executed. Is this OK?

Confirms that it is OK to send a cancel request to the selected automated action.

O:

Click the Yes button to send the cancel request. Click the No button to cancel sending the cancel request.

KAVB0536-I

The action is not in a re-executable state. Click the Refresh button in the window-title window, and then check the status.

After re-execution of an action, re-execution of the action was requested again before you clicked the Refresh button. Another possibility is that the action cannot be re-executed because the data for that action does not exist in the action information file.

S:

Aborts processing.

O:

Click the Refresh button in window-title to check the latest action status.

KAVB0540-E

The rule cannot be specified for the action.

You cannot manually specify <RULE> in the action specification area because it is an action for a rule startup request.

S:

Waits for re-entry of information.

O:

Specify the input item correctly.

KAVB0541-E

An attempt to start the Rule Log Details window of JP1/IM - Rule Operation has failed.

An attempt to open the Rule Log Details window of JP1/IM - Rule Operation failed.

S:

Does not open the Rule Log Details window of JP1/IM - Rule Operation.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB0551-E

The number of accumulated response-waiting events on the manager exceeded the maximum (2000).

The oldest response-waiting event on the manager was released from the hold-and-accumulate state because the maximum number of response-waiting events that can be accumulated on the manager was exceeded.

S:

Continues processing.

O:

Check the integrated trace log of the manager, and then take the corrective action given for the KAVB1801-E message, which indicates that the response-waiting event was released from the hold-and-accumulate state.

After the corrective action is completed, restart the notification function for monitoring of the accumulation state in the Event Console window so that a notification is issued if the maximum number of response-waiting events that can be accumulated is exceeded again.

KAVB0552-I

The response was successful.

Response processing was successful.

S:

Terminates the response processing, and then updates the Enter Response window.

KAVB0553-Q

A response will now be executed. Is this OK?

This message confirms that you want to send a response.

O:

Click the Yes button to send a response. Click the No button to cancel sending a response.

KAVB0554-E

An attempt to respond failed.

(reason = reason)

Response processing failed.

S:

Aborts response processing.

O:

Check the following items depending on the reason that is displayed.

Fail to connect server.

A connection could not be established with JP1/Base on the server that issued the response-waiting event. JP1/Base might not be running on that server. Check the status of the server. In addition, a communication error might have occurred. Check the status of the connection with the server that issued the response-waiting event.

Connection has timed out.

A timeout occurred because the server or network that issued the response-waiting event was in high load status. Wait a while and then retry the operation. If this message is output frequently, revise the timeout value specified for the response or status check of response-waiting events.

Socket error occurred.

A communication error occurred. Check the status of the network of the server that issued the response-waiting event.

Invalid data was received from the program product that sent the response-waiting event.

Collect the following data, and then contact a system administrator:

• Data of the product that issued the response-waiting event

• JP1/IM - Manager data (collected by using the data collection tool)

A message for the product that issued the response-waiting event is indicated in reason:

Take the corrective action given for the message indicated in reason.

Server is busy.

The request was not accepted because the connected server was busy. Wait a while, and then retry the operation.

There is no valid receiver for the response.

Processing could not be executed because the product that issued the response-waiting event was in an invalid environment. Revise the environment of the product.

The reason is other than the above:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0555-E

An attempt to check the status failed.

(reason = reason)

An attempt to check the status of the destination corresponding to the response-waiting event failed.

S:

Aborts display of the Enter Response window.

O:

Check the following items depending on the reason that is displayed.

Fail to connect server.

A connection could not be established with JP1/Base on the server that issued the response-waiting event. JP1/Base might not be running on that server. Check the status of the server. In addition, a communication error might have occurred. Check the status of the connection with the server that issued the response-waiting event.

Connection has timed out.

A timeout occurred because the server or network that issued the response-waiting event was in high load status. Wait a while and then retry the operation. If this message is output frequently, revise the timeout value specified for the response or status check of response-waiting events.

Socket error occurred.

A communication error occurred. Check the status of the network of the server that issued the response-waiting event.

Invalid data was received from the program product that sent the response-waiting event.

Collect the following data, and then contact a system administrator.

• Data of the product that issued the response-waiting event

• JP1/IM - Manager data (collected by using the data collection tool)

A message for the product that issued the response-waiting event is indicated in reason:

Take the corrective action given for the message indicated in reason.

Server is busy.

The request was not accepted because the connected server was busy. Wait a while, and then retry the operation.

There is no valid receiver for the response.

Processing could not be executed because the product that issued the response-waiting event was in an invalid environment. Revise the environment of the product.

The reason is other than the above:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0556-I

The response cannot be accepted.

No response was sent because the destination was unable to accept a response.

S:

Terminates the response processing, and then updates the Enter Response window.

KAVB0557-E

The selected response-waiting event does not exist in the file for accumulated response-waiting events.

The selected response-waiting event does not exist in the file for accumulated response-waiting events because the event was released from the hold-and-accumulate state.

S:

Suspends processing.

O:

Search for the response-waiting event and check the status.

If the response-waiting event is not displayed after an event search is executed, the event does not exist in the event database. In this case, you cannot perform any operation for that event from JP1/IM - View. If you want to respond to a response-waiting event for which operation is no longer possible from JP1/IM - View, take the corrective action for the product that issued the event.

KAVB0558-E

Failed to obtain the selected response-waiting event. Cannot continue processing.

An attempt to obtain the response-waiting event has failed.

S:

Suspends processing.

O:

Check the integrated trace log of the manager to see if an Event Console Service error message was output (error messages from KAVB0001 to KAVB2000).

If a message was output, take the corrective action given for that message.

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB0559-Q

The selected events will now be released from the hold-and-accumulate state. Is this OK?

This message asks you to confirm that you want to release the selected event from the hold-and-accumulate state.

O:

Click the Yes button to release the selected event from the hold-and-accumulate state. Click the No button to cancel releasing the selected event from the hold-and-accumulate state.

KAVB0560-E

An attempt to release an event from the hold-and-accumulate state has failed.

An attempt to release the event from the hold-and-accumulate state has failed.

S:

Stops releasing the event from the hold-and-accumulate state.

O:

Check the integrated trace log of the manager to see if an Event Console Service error message was output (error messages from KAVB0001 to KAVB2000).

If a message was output, take the corrective action given for that message.

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB0561-E

The operation (operation) cannot be performed because response-waiting event management function is disabled.

The operation indicated in operation cannot be performed because the response-waiting event management function is disabled.

S:

Cancels the indicated operation.

O:

To use the response-waiting event, use the jcoimdef command to enable the response-waiting event management function, and then restart JP1/IM - View.

If you do not want to use the response-waiting event, restart JP1/IM - View.

KAVB0562-E

A response was successful, but an attempt to release a response-waiting event from the hold-and-accumulate state has failed.

A response for the response-waiting event was successful, but the response-waiting event could not be released from the hold-and-accumulate state because an error occurred during deletion of the event from the file for accumulated response-waiting events.

S:

Aborts response processing.

O:

Check the integrated trace log of the manager to see if an Event Console Service error message was output (error messages from KAVB0001 to KAVB2000).

If a message was output, take the corrective action given for that message.

After the problem is resolved, if you want to manually delete the response-waiting event for which a response was successful, use the following procedure:

Set the status of the response-waiting event to Processed.

On the Response-Waiting Events page, release the response-waiting event from the hold-and-accumulate state.

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB0563-E

The response and the release from the hold-and-accumulate state of the response-waiting event were successful, but an attempt to change the action status failed.

A response for the response-waiting event was successful and the response-waiting event was released from the hold-and-accumulate state, but an attempt to change the action status has failed.

S:

Aborts response processing.

O:

Check the integrated trace log of the manager to see if an Event Console Service error message was output (error messages from KAVB0001 to KAVB2000).

If a message was output, take the corrective action given for that message.

After the problem is resolved, if you want to manually change the action status of the response-waiting event, use the following procedure:

Search for the response-waiting event for which a response was successful.

Change the status of the retrieved response-waiting event to Processed.

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB0601-E

System error occurred in analyzing the definition.

An unexpected error was detected during processing of the definition information analysis.

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0602-E

Memory shortage occurred in analyzing the definition.

A memory shortage occurred during processing of the definition information analysis.

S:

Aborts processing.

O:

Allocate sufficient memory, and then retry the operation.

KAVB0611-E

Failed to execute the application.

Command name :executed-command

Details: detailed-information

An error occurred during execution of the application.

S:

Aborts application processing.

O:

Make sure that the execution path name and access permission specified in the definition file are correct, and then retry the operation.

KAVB0612-E

Failed to execute the application due to error in command line specifications.

Command Name : executed-command

An error occurred during generation of the command line.

S:

Aborts application processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0624-W

A failure occurred in obtaining the application(application-execution-ID) output-destination result.

Details: detailed-information

An error occurred during processing to acquire the application execution result.

S:

Aborts acquisition of the application execution result.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0651-W

The block(identifier) is multiply specified. The newer block is effective. (definition-file-name: line-number)

A block that defines the same identifier is specified multiple times.

S:

Invalidates the previously defined block, validates the new block, and continues analysis processing.

O:

Check the specification of the identifier, and then retry the operation.

KAVB0652-W

An invalid descriptor (identifier) is specified. processing-contents (definition-file-name:line-number)

An invalid identifier is specified. The possible causes are as follows:

An identifier that is already registered in the system is specified.

default_browser, root

No identifier is specified.

S:

Executes processing-contents and continues analysis processing.

O:

Check the specification of the identifier, and then retry the operation.

KAVB0653-W

An invalid path name (path-name) is specified. processing-contents (definition-file-name:line-number)

The specified path name or file does not exist.

S:

Executes processing-contents and continues analysis processing.

O:

Check the specification of the path name, and then retry the operation.

However, if the message is output because the linkage product is not installed, corrective action is not necessary.

KAVB0654-W

Failed to convert the registry definition (registry-definition). processing-contents (definition-file-name:line-number)

Conversion of the registry failed.

S:

Executes processing-contents and continues analysis processing.

O:

Check the specification of the registry, and then retry the operation.

KAVB0655-W

The descriptor(identifier) specified is not defined. processing-contents (definition-file-name:line-number)

The specified identifier is not defined.

S:

Executes processing-contents and continues analysis processing.

O:

Check the block definition in the application definition file or function menu definition file, and then retry the operation.

However, if the message is output because the linkage product is not installed, corrective action is not necessary.

KAVB0656-W

The application execution definition is not specified for the block (identifier). processing-contents (definition-file-name:line-number)

The application execution definition is not specified for the specified definition block.

S:

Invalidates the definition block and continues analysis processing.

O:

Specify the application execution definition for the definition block, and then retry the operation.

However, if the message is output because the linkage product is not installed, corrective action is not necessary.

KAVB0657-W

The default browser is not registered.

The default Web browser is not registered.

S:

Invalidates the default Web browser definition and continues analysis processing.

O:

Assign a Web browser to the extension (html), and then retry the operation.

KAVB0658-W

Failed to read the image file.

An attempt to read the image file failed.

S:

Continues processing without displaying the image.

O:

Check the image file name specified in the definition file, and then retry the operation.

KAVB0682-I

The Select Registration Process Workboard window in JP1/IM - Service Support has started. (event database serial number = event-database-serial-number)

The Select the process work board as the registration target window in JP1/IM - Service Support has started.

KAVB0683-E

The Select Registration Process Workboard window in JP1/IM - Service Support could not be started. (event database serial number = event-database-serial-number, cause = cause)

An attempt to start the Select the process work board as the registration target window in JP1/IM - Service Support has failed.

S:

Aborts starting of the Select the process work board as the registration target window in JP1/IM - Service Support.

O:

Cause: The URL is invalid.

Make sure that the URL of the JP1/IM - Service Support specified in the definition file for manually registering incidents is correct. If the URL is not correct, correct it.

Cause: The browser could not be started.

Revise the settings of the applications associated with the HTML file of the OS.

If a message other than the above is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB0684-I

The default browser has started. (link = link-destination, host name = host-name, event database serial number = event-database-serial-number)

The window of the linked product has started.

KAVB0685-E

The default browser could not be started. (link = link-destination, host name = host-name, event database serial number = event-database-serial-number, cause = cause)

The OS's default browser could not be started.

S:

Aborts processing.

O:

If The URL is invalid. is displayed for cause, make sure that the URL of the linked product specified in the event guide message file is correct. If the URL is not correct, correct it.

KAVB0686-W

The syntax of a parameter is invalid. cause (file name = file-name)

A parameter in the incident manual registration definition file was incorrectly specified.

S:

Ignores the parameter, and continues processing.

O:

Correct the error in the incident manual registration definition file indicated in cause.

KAVB0687-I

The Select Report Window in JP1/PFM - Web Console has started. (event database serial number = event-database-serial-number, host displaying performance report = name-of-host-displaying-performance-report)

The Select Report window of JP1/PFM - Web Console was launched.

KAVB0688-E

The Select Report Window in JP1/PFM - Web Console could not be started. (event database serial number = event-database-serial-number, host displaying performance report = name-of-host-displaying-performance-report, cause = cause)

The Select Report window of JP1/PFM - Web Console could not be launched.

S:

Aborts launching of the Select Report window of JP1/PFM - Web Console.

O:

Revise the OS setting for the application associated with HTML files.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB0711-E

More than 10 AND conditions have been specified. (line = line-number, file = file-name)

More than 10 AND conditions have been specified.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0712-E

An ampersand (&) cannot be specified for a parameter group of an action block at the front of an AND condition. (line = line-number, file = file-name)

You cannot specify an ampersand (&) for a parameter group of an action block at the front of an AND condition.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0713-E

More than 256 event conditions have been specified. (action = action-name, line = line-number, file = file-name)

More than 256 event conditions have been specified.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0714-E

The parameter parameter-name cannot be specified because a rule has been specified for the action. (action = action-name, line = line-number, file = file-name)

If you have specified an action for rule startup, you cannot specify a user name, target host name/group name, or environment variable file name.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0715-E

The location of the version of the automatic action definition file is invalid. (line = line-number, file = file-name)

The version of the automated action definition file is specified in a location other than the beginning of the file.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0716-E

The version information for the automatic action definition file is invalid. (line = line-number, file = file-name)

The version information is invalid.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0717-E

The parameter parameter is missing. (action = action-name, line = line-number, file = file-name)

The parameter is not specified.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0718-E

The shared block has been duplicated. (line = line-number, file = file-name)

The shared block is duplicated.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0719-E

An invalid parameter is specified. (invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified in the automated action definition file.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0720-E

An invalid parameter is specified in an action block. (action = action-name, invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified in an action block.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0721-E

An action block does not end with an "end-act" statement. (action = action-name, line = line-number, file = file-name)

An action block does not have an end.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0722-E

An action name is not specified. (line = line-number, file = file-name)

An action name is not specified.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0723-E

If an ampersand (&) is specified in a parameter group, an action name cannot be specified. (action = action-name, line = line-number, file = file-name)

If you specify an ampersand (&) in a parameter group, you cannot specify an action name.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0724-E

An action name is duplicated. (action = action-name, line = line-number, file = file-name)

An action name is duplicated.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0725-E

An action name exceeds the maximum length. (line = line-number, file = file-name)

An action name exceeds the maximum length.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0726-E

The parameter parameter-name is invalid. (action = action-name, line = line-number, file = file-name)

The description of the displayed parameter is unsuitable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0727-E

No value is specified for the parameter parameter-name. (action = action-name, line = line-number, file = file-name)

No value is specified following the displayed parameter.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0728-E

The parameter parameter-name is specified more than once. (action = action-name, line = line-number, file = file-name)

The displayed parameter is specified more than once.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0729-E

No value is specified for the parameter parameter-name. (action = action-name, line = line-number, file = file-name)

No value is specified following the displayed parameter.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0730-E

The parameter parameter-name is specified more than once. (action = action-name, line = line-number, file = file-name)

The displayed parameter is specified more than once.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0731-E

The number of characters (bytes) in the parameter parameter-name exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The value of the displayed parameter exceeds the maximum number of bytes.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0732-E

The number of characters (bytes) in the parameter parameter-name exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The value of the displayed parameter exceeds the maximum number of bytes.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0733-E

An event condition block does not end with an "end-act" statement. (action = action-name, line = line-number, file = file-name)

An event condition block does not have an end.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0734-E

The event condition block is invalid. (action = action-name, line = line-number, file = file-name)

The description of the event condition is unsuitable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0735-E

The event condition block attribute name is invalid. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The attribute name of the event condition is unsuitable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0736-E

The attribute name is not specifiable. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

An attribute name that cannot be specified was specified.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0737-E

The comparison key word for the event conditions is invalid. (attribute name = attribute-name, comparison key word = comparison-keyword, action = action-name, line = line-number, file = file-name)

The comparison keyword of the event condition is unsuitable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0738-E

The comparison key word is not specifiable. (attribute name = attribute-name, comparison key word = comparison-keyword, action = action-name, line = line-number, file = file-name)

A comparison keyword that cannot be specified is specified.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0739-E

The number of event condition operands exceeds the maximum number. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The number of event condition operands exceeds the maximum.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0740-E

An event condition operand is duplicated. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

An event condition operand is duplicated.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0741-E

An event ID operand is invalid. (operand = operand, action = action-name, line = line-number, file = file-name)

An event ID operand is unsuitable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0742-E

A regular expression is invalid. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

The specification of a regular expression is unsuitable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0743-E

A critical operand is invalid. (operand = operand, action = action-name, line = line-number, file = file-name)

A critical operand is unusable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0744-E

An operand is invalid. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

An operand is unusable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0745-E

The combination of comparison conditions among multiple event attributes that have the same name is invalid. (attribute = attribute-name, action = action-name, line = line-number, file = file-name)

The combination of comparison conditions among multiple event attributes that have the same name is invalid.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0746-E

The number of characters (bytes) in an operand exceeds the maximum. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The operand exceeds the maximum number of bytes.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0747-E

The total number of characters (bytes) in the operands exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The total number of bytes in the operands exceeds the maximum.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0748-E

The specified value for the parameter parameter-name is outside the valid range. (specified value = specified-value, action = action-name, line = line-number, file = file-name)

The value specified for the displayed parameter is outside the valid range.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0749-E

If an ampersand (&) is specified in a parameter group, det cannot be specified. (action = action-name, line = line-number, file = file-name)

If you specify an ampersand (&) in a parameter group, you cannot specify det.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0750-E

Version information of an action definition file is specified more than once. (line = line-number, file = file-name)

Version information of an action definition file is specified multiple times.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0751-E

A shared block is specified after an action block. (line = line-number, file = file-name)

A shared block is specified after an action block.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0752-E

A shared block does not end with an "end-act" statement. (line = line-number, file = file-name)

A shared block does not have an end.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0753-E

An invalid parameter is specified for a shared block. (invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified for a shared block.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0754-E

The parameter parameter-name is specified more than once. (line = line-number, file = file-name)

The displayed parameter is specified more than once.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0755-E

No value is specified for the parameter parameter-name. (line = line-number, file = file-name)

No value is specified following the displayed parameter.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0756-E

The parameter parameter-name is invalid. (line = line-number, file = file-name)

The description of the displayed parameter is unusable.

S:

Terminates processing.

O:

Correct the automated action definition file of the manager, and then perform the operation again.

KAVB0757-E

An error occurred while reading a action definition file. (reason = reason, line = line-number, file = file-name)

An unexpected error occurred while reading a definition file.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0758-E

The size of the action definition file exceeds the upper limit. (file name: file-name, upper limit = maximum-size)

The size of the action definition file exceeds the maximum value.

S:

Terminates processing without reading the action definition file.

O:

Carefully review the contents of the action definition file to see if it contains extra comments or redundant definitions, and correct the file so that its size is no greater than the maximum value. After correcting the file, retry the operation.

KAVB0759-E

The same action ID is specified more than once. (action = action-name, line = line-number, file = file-name)

The same action ID is specified more than once.

S:

Terminates processing.

O:

Correct the error in the automated action definition file of the manager, and then retry the operation.

KAVB0760-W

The action setting was discarded from JP1/IM - View because an action definition in which a business group or a monitoring group was specified as an execution host name is set in JP1/IM - Manager.

The action setting from JP1/IM - View was discarded because an action definition in which a business group or a monitoring group was specified for an execution host name was set in JP1/IM - Manager.

S:

Invalidates the settings from JP1/IM - View and continues processing.

O:

If an action definition in which a business group or a monitoring group is specified for an execution host name is set in JP1/IM - Manager, use JP1/IM - View version 09-50 or later.

KAVB0761-W

The setting was discarded from JP1/IM - View because an definition in which a business group or a monitoring group was specified is set in JP1/IM - Manager. (definition type = definition-type)

The setting from JP1/IM - View was discarded because a business group or a monitoring group was specified in the JP1/IM - Manager settings. If a business group or a monitoring group is specified in the JP1/IM - Manager settings, you cannot use JP1/IM - View earlier than version 09-50 to specify settings.

S:

Invalidates the settings from JP1/IM - View and continues processing.

O:

Use JP1/IM - View version 09-50 or later to specify settings.

KAVB0762-E

You cannot specify an action ID if you specified an ampersand (&) for the parameter group. (line = line-number, file = file-name)

When an ampersand (&) is specified for the parameter group, you cannot specify an action ID.

S:

Terminates processing.

O:

Correct the error in the automated action definition file of the manager, and then retry the operation.

KAVB0763-E

You cannot specify "valid" if you specified an ampersand (&) for the parameter group. (line = line-number, file = file-name)

When an ampersand (&) is specified for the parameter group, you cannot specify valid.

S:

Terminates processing.

O:

Correct the error in the automated action definition file of the manager, and then retry the operation.

KAVB0801-E

The option (option) is invalid.

An invalid option is specified.

S:

Terminates processing.

O:

Specify the option correctly.

KAVB0802-E

An essential option (option) is not specified.

A required option is not specified.

S:

Terminates processing.

O:

Specify the option correctly.

KAVB0803-E

The option (option) is duplicated.

The option is specified more than once.

S:

Terminates processing.

O:

Specify the option correctly.

KAVB0804-E

The argument of the option (option) is insufficient.

The argument of the option is insufficient.

S:

Terminates processing.

O:

Carefully review the specified argument.

KAVB0805-E

The argument value (argument) of the option (option) is invalid.

The argument value of the option is incorrect.

S:

Terminates processing.

O:

Specify the value of the option correctly.

KAVB0806-E

The maximum number of serial numbers in the event DB is 100. (Option : option)

The number of serial numbers in the event database specified by the option exceeds 100.

S:

Terminates processing.

O:

Reduce the number of specified serial numbers in the event database to no more than 100.

KAVB0807-E

The option option and the option option cannot be specified at the same time.

Processing cannot be executed because options that cannot be specified at the same time are specified.

S:

Terminates processing.

O:

Specify the options correctly.

KAVB0810-E

Specify an argument (argument-value) after the option (option).

Processing cannot be executed because an argument value is not specified following the displayed option.

S:

Terminates processing.

O:

Specify an argument value following the displayed option.

KAVB0811-E

When you specify a password, specify a host_name and a user_name.

To specify a password, also specify a host name and user name.

S:

Terminates processing.

O:

When specifying a password, specify a host name and user name as well.

KAVB0821-E

The manager does not have the specified event. (Serial number: serial-number-in-event-database)

The corresponding status of following events could not be changed.

The specified event does not exist in the manager. The action statuses after this event are not changed.

S:

Terminates processing.

KAVB0822-E

The event status of the specified event (Serial number: serial-number-in-event-database) could not be changed.

The corresponding status of following events could not be changed.

The action status of the specified event could not be applied in the manager. The action statuses after this event are not changed.

S:

Terminates processing.

O:

Determine whether Event Service is running.

If Event Service is not running, start Event Service, and then retry the operation.

If you are using an integrated monitoring database, check the integrated trace log of the manager to see if any of the following messages was output. If a message was output, take the corrective action given for that message.

• KAVB1663-E

• KAVB1664-E

• KAVB1665-E

• KAVB1674-E

• KAVB1675-E

• KAVB1676-E

If no message is output, contact a system administrator.

KAVB0823-E

The specified key (key-value) is invalid. Check the specified value.

The specified key value is incorrect.

S:

Terminates processing.

O:

Specify the key value correctly.

KAVB0824-E

The specified event is not an updateable event. (Serial number :serial-number-in-event-database)

This command will now stop.

An event that cannot be updated is specified.

S:

Terminates processing.

O:

Carefully review the specification of the serial numbers in the event database.

KAVB0825-E

A memory shortage occurred during execution of the command. (command-name)

A memory shortage occurred during execution of the command.

S:

Terminates processing.

O:

Allocate sufficient memory to execute the command, and then re-execute analysis processing.

KAVB0826-E

An exception occurred while the log output was being prepared.

A system error occurred while executing the command.

S:

Terminates processing.

O:

Collect the trace information output to standard error, use the data collection tool to collect data, and then contact a system administrator.

KAVB0827-E

An exception occurred while an error message was being created.

An unexpected exception occurred while an error message was being created.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0828-E

Memory became insufficient during execution of JP1/IM - View.

JP1/IM - View could not start because a memory shortage occurred.

S:

Terminates processing.

O:

Allocate sufficient memory to start JP1/IM - View, and then restart JP1/IM - View.

KAVB0830-E

An invalid logical host name (logical-host-name) is specified.

The specified logical host name is invalid.

S:

Terminates processing.

O:

Specify the correct logical host name, and then retry the operation.

KAVB0831-E

JP1/IM - Manager has started.

The command cannot be executed because JP1/IM - Manager is running.

S:

Terminates processing.

O:

Stop JP1/IM - Manager, and then retry the operation.

KAVB0832-E

Common definition information setting has failed.

An attempt to set common definition information failed.

S:

Terminates processing.

O:

Retry the operation. If an error still occurs, use the data collection tool to collect data, and then contact a system administrator.

KAVB0833-E

An attempt to read the event acquisition settings in the system profile has failed.

The event acquisition condition settings in the system profile could not be read because of the following reason(s).

Another application is using the .system file.

Unable to read the .system file.

The contents of the .system.conf file are corrupted.

S:

Terminates processing.

O:

Check the following items, and then retry the operation.

Is another application using the .system file?

Can the .system file be read?

If the reason for the error is neither of the above, the contents of the .system.conf file may be corrupted. Overwrite the .system.conf file with the .system.conf.model file to return the setting information to its initial status, and then reconfigure the system environment.

KAVB0834-E

An attempt to move the event acquisition filter has failed.

The event acquisition filter could not be moved because of the following reason(s).

Another application is using the receive_filter.conf file.

Unable to write to the receive_filter.conf file.

Insufficient disk space.

S:

Terminates processing.

O:

Check the following items, and then retry the operation.

Is another application using the receive_filter.conf file?

Can the receive_filter.conf file be written to?

Is there sufficient disk space to move the event acquisition filter?

KAVB0835-E

Only one jcochafmode command can be executed at one time.

The jcochafmode command is being executed.

S:

Terminates processing.

O:

After processing of the current jcochafmode command is complete, retry the operation.

KAVB0836-I

The event acquisition filter was switched from interchangeability to the ordinary mode.

The event acquisition filter was switched from compatible mode to ordinary mode.

S:

Continues processing.

KAVB0837-E

The start of JP1/IM - Manager was not able to be confirmed. Please confirm whether JP1/IM - Manager has stopped and execute the command again.

Startup of JP1/IM - Manager could not be confirmed.

S:

Terminates processing.

O:

Use the jco_spmd_status command to determine whether JP1/IM - Manager has stopped, and then retry the operation.

If you specified a logical host, make sure that the shared disk of the logical host has been mounted.

KAVB0838-E

The settings for common definition information are incorrect. Key:(key-value) param:(acquired-value)

The values set for common definition information are invalid.

S:

Terminates processing.

O:

Retrieve the file corresponding to key-value from the backup file, and use the jbssetcnf command to reset the common definition.

KAVB0839-E

Failed to read common definition information. Key:(key-value)

An attempt to read common definition information failed.

S:

Terminates processing.

O:

Retrieve the file corresponding to key-value from the backup file, and use the jbssetcnf command to reset the common definition.

KAVB0840-E

A system error occurred while executing the command (command-name).

Details:(detailed-information)

A system error occurred while executing the command.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0841-E

No executing permission.

There is no permission to execute the command.

S:

Terminates processing.

O:

Log in again as an administrator who has execution permission, and then retry the operation.

KAVB0842-E

Setting information in the system profile is invalid.

Details:(detailed-code)

Setting information in the system profile is invalid.

S:

Terminates processing.

O:

Overwrite the .system file with the .system.model file to return the setting information to its initial status, and then reconfigure the system environment.

KAVB0851-E

JP1/IM - Manager is not running.

Switching cannot be executed because JP1/IM - Manager is not running.

S:

Terminates processing.

O:

Make sure that JP1/IM - Manager is running, and then retry the operation.

KAVB0852-E

The startup status of JP1/IM - Manager could not be checked.

Switching cannot be executed because the running status of JP1/IM - Manager cannot be confirmed.

S:

Terminates processing.

O:

Make sure that JP1/IM - Manager is running, and then retry the operation.

KAVB0853-E

The event acquisition filter is operating in a compatible mode

Switching cannot be executed because the event acquisition filter is operating in compatible mode.

S:

Terminates processing.

O:

Check the event acquisition filter mode, and then retry the operation.

KAVB0854-E

The specified filter does not exist.(filterID: filter-ID)

Switching cannot be executed because a filter condition with the filter ID specified by the argument does not exist.

S:

Terminates processing.

O:

Display the list of event acquisition filters, make sure the filter with the specified ID exists, and then retry the operation.

KAVB0855-I

The aquisition filter in hostname will now be switched.(filterID: filter-ID)

Indicates that switching of the event acquisition filter will start.

S:

Continues processing.

KAVB0856-I

The list of event acquisition filters will now be displayed. (host name: host-name)

Display of the event acquisition filter list will start.

S:

Continues processing.

KAVB0857-I

A connection to JP1/IM - Manager has been established.

JP1/IM - Manager was connected.

S:

Continues processing.

KAVB0858-I

The event acquisition filter was switched successfully.

Switching of the event acquisition filter finished normally.

S:

Continues processing.

KAVB0859-E

An attempt to switch the event acquisition filter has failed. (service = control)

An attempt to switch the event acquisition filter for the displayed control failed.

S:

Continues switching processing of the event acquisition filter for other controls.

O:

Determine whether the displayed control is running. If the displayed control is running, check the integrated trace log to see if an error message was output. If an error message was output, take the corrective action given for that message. If no message was output, use the data collection tool to collect data, and then contact a system administrator.

KAVB0860-I

Switching of the event acquisition filter was successful. (service = control)

The event acquisition filter for the displayed control was switched.

KAVB0861-I

Switching of the event acquisition filter has finished.

Switching of the event acquisition filter is complete.

KAVB0862-E

An attempt to switch the event acquisition filter has failed.

An attempt to switch the event acquisition filter failed.

S:

Aborts processing to switch the event acquisition filter.

O:

Check the integrated trace log to see if an error message was output. If an error message was output, take the corrective action given for that message. If no error message was output, make sure that the KAVB4003-I message was output to the integrated trace log, and then retry the operation. If the KAVB4003-I message was not output and you are using an integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service. When you have confirmed that the IM database service is running and the KAVB4003-I message is output to the integrated trace log, retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB0863-E

The specified common exclusion condition does not exist. (common exclusion condition ID = common-exclusion-conditions-group-ID)

Switching cannot be executed because common exclusion-conditions with the common exclusion-conditions group ID specified by the argument do not exist.

S:

Terminates processing.

O:

Display the list of event acquisition filters and the list of common exclusion-conditions, make sure that the common exclusion-conditions of the specified ID exist, and then retry the operation.

KAVB0864-I

The common exclusion condition will now be enabled. (common exclusion condition ID = common-exclusion-conditions-group-ID[,common-exclusion-conditions-group-ID...])

A common exclusion-condition is enabled.

S:

Continues processing.

KAVB0866-E

A common exclusion condition ID is duplicated.

The specified common exclusion-conditions group ID is duplicated.

S:

Terminates processing.

O:

Carefully review the specification.

KAVB0868-I

All common exclusion conditions will now be enabled.

All specified common exclusion-conditions group IDs are enabled.

S:

Continues processing.

KAVB0869-I

All common exclusion conditions will now be disabled.

All specified common exclusion-conditions group IDs are disabled.

S:

Continues processing.

KAVB0870-E

The common exclusion conditions could not be set because the maximum length of the event acquisition filter (65536 bytes) was exceeded.

The event acquisition filter exceeds the maximum length that can be specified.

S:

Terminates processing.

O:

Reduce the event acquisition filter or common exclusion-condition to a length no greater than the maximum.

KAVB0871-E

The common exclusion condition does not exist.

Processing to switch between enabling and disabling of a common exclusion-condition is terminated because the common exclusion-condition does not exist.

S:

Terminates processing.

O:

Display a list of common exclusion-conditions, make sure that the common exclusion-condition exists, and then retry the operation.

KAVB0872-E

The JP1/Base instance on the manager host does not support the common exclusion condition.

The version of JP1/Base on the manager host does not support the common exclusion-condition.

S:

Terminates processing.

O:

Check the version of the JP1/Base on the manager host. To configure support for common exclusion-conditions, a version of JP1/Base that supports common exclusion-conditions must be installed.

KAVB0873-E

Information about the event cannot be output because the IM Database service is not running.

The event cannot be acquired because the integrated monitoring database is not running.

S:

Terminates processing.

O:

Start the integrated monitoring database, and then retry the operation.

KAVB0874-E

Information about the event cannot be output because the Integrated Monitoring Database has not been set up.

The event to be output does not exist because the integrated monitoring database has not been set up.

S:

Terminates processing.

O:

Set up the integrated monitoring database, and then retry the operation.

KAVB0875-E

The file-type file file-name does not exist.

The specified file does not exist.

S:

Terminates processing.

O:

Make sure the specified file name is correct, and then retry the operation.

KAVB0876-E

An attempt to read the file-type file file-name has failed.

An I/O error occurred during reading of the file.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB0877-E

The syntax of an item file is invalid. reason (line = line-number, file name = file-name)

There is an error in the contents of the item file.

S:

Terminates processing.

O:

Identify the cause based on the invalid contents, carefully review the item file, and then retry the operation.

KAVB0878-E

The syntax of a filter file is invalid. reason (line = line-number, file name = file-name)

There is an error in the contents of the filter.

S:

Terminates processing.

O:

Identify the cause based on the invalid contents, carefully review the filter, and then retry the operation.

KAVB0879-E

The format specified for specification-item is invalid.

The entered date and time is not specified as numeric characters in YYYYMMDDhhmmss format.

S:

Terminates processing.

O:

Carefully review the entered date and time, and then retry the operation.

KAVB0880-E

The value specified for specification-item is outside the valid range.

The entered date and time is before 1970/01/01 00:00:00 or after 2038/01/19 03:14:07.

S:

Terminates processing.

O:

Carefully review the entered date and time, and then retry the operation.

KAVB0881-E

The value specified for specification-item is not valid date and time information.

The entered date and time does not exist.

S:

Terminates processing.

O:

Carefully review the entered date and time, and then retry the operation.

KAVB0882-I

Number-of-output-events events were successfully output in the function-name.

Output of event reports was successful.

S:

Terminates processing.

KAVB0883-E

The function-name failed. (detailed information = detailed-information)

An attempt to output the event report failed.

S:

Terminates processing.

O:

Take the corrective action given for the detailed information in the error message that was displayed after executing the command.

detailed-information

4: File I/O error

101: The integrated monitoring database is not set up.

102: The IM database service is not running.

103: An error occurred in connecting to the IM database service.

254: Memory shortage

255: System error

KAVB0884-E

Multiple instances of the jcoevtreport command cannot be executed at the same time.

More than one jcoevtreport command cannot be executed at the same time.

S:

Terminates processing.

O:

Wait until processing of the current jcoevtreport command is complete, and then retry the jcoevtreport command.

KAVB0885-E

The file cannot be saved because the file name is too long. (file = file-name)

A file name using an absolute path exceeds 250 characters.

S:

Terminates processing.

O:

Correct the file name in an absolute path so that it is no more than 250 characters, and then retry the operation.

KAVB0886-E

The serial number of the output file reached the maximum value.

The serial number of the output file reached the maximum value.

S:

Terminates processing.

O:

Change the output file name, and then retry the operation.

KAVB0887-E

The size of the file-type file exceeds the upper limit. (file name = file-name, upper limit = upper-limit)

The size of the specified file exceeds the maximum value.

S:

Terminates processing without reading the specified file.

O:

Carefully review the contents of the file to see if it contains extra comments or redundant definitions, and correct the file so that its size is no greater than the maximum value. After correcting the file, retry the operation.

KAVB0888-E

The common exclusion condition group (extended) cannot be changed.

The common exclusion-condition group in extended mode cannot be changed because the common exclusion-conditions have not been extended.

S:

Terminates processing.

O:

Use the -e option to enable or disable the common exclusion-conditions.

Alternatively, change the operation mode for the common exclusion-conditions to extended mode, and then re-execute the command.

KAVB0889-I

The common exclusion condition will now be disabled. (common exclusion condition group IDs = common-exclusion-condition-group-ID[,common-exclusion-condition-group-ID...])

The common exclusion-conditions will be disabled.

S:

Continues processing.

KAVB0890-E

The common exclusion condition group cannot be extended because the event acquisition filter (for compatibility) is being used.

The common exclusion-condition group could not be extended because the event acquisition filter (for compatibility) was being used.

S:

Terminates processing.

O:

To extend the common exclusion-condition group, you need to change the location of the event acquisition filter from Event Console Service to Event Base Service. Use the jcochafmode command to change the location of the filter, and then re-execute the command.

KAVB0891-E

The common exclusion condition group cannot be extended because a JP1/Base regular expression is not extended. Revise the prerequisite regular expressions.

The common exclusion-condition group could not be extended because a regular expression used for JP1/Base was not extended.

S:

Terminates processing.

O:

To extend the common exclusion-condition group, the regular expression used for JP1/Base must be an extended regular expression.

Change the setting of the regular expression used for JP1/Base, and then re-execute the command.

KAVB0893-E

The common exclusion conditions extended definition file (file-name) cannot be opened.

The common-exclusion-conditions extended definition file was not found.

S:

Terminates processing.

O:

Make sure that the specified file exists and that you have the access permission for the specified file. Then, retry the operation.

KAVB0894-I

The operation mode of the common exclusion conditions will be displayed. (host name = host-name)

operation mode = operation-mode

The operation mode of the common exclusion-conditions will be displayed.

S:

Continues processing.

KAVB0895-I

The operation mode of the common exclusion conditions was changed to basic mode.

The operation mode of the common exclusion-conditions was changed to basic mode.

S:

Continues processing.

KAVB0896-I

The operation mode of the common exclusion conditions was changed to extended mode.

The operation mode of the common exclusion-conditions was changed to extended mode.

S:

Continues processing.

KAVB0897-I

The common exclusion conditions extended definition file was output.

The common-exclusion-conditions extended definition file was output normally.

S:

Continues processing.

KAVB0898-E

The operation mode of the common exclusion conditions could not be changed. (cause = cause)

An attempt to output the common-exclusion-conditions extended definition file failed.

S:

Terminates processing.

O:

Cause:An I/O error has occurred.

Check the three items described below in the following directories, and then retry the operation.

In Windows:

Physical host: Console-path\conf\console\filter\

Logical host: shared-folder\JP1Cons\conf\console\filter\

In UNIX:

Physical host: /etc/opt/jp1cons/conf/console/filter/

Logical host: shared-directory/jp1cons/conf/console/filter/

Item 1. Make sure that you can write to the common-exclusion-conditions extended definition file. If you cannot, assign write permission.

Item 2. If the common-exclusion-conditions extended definition file (common_exclude_filter_logical-host-name.conf) exists, check whether any other application is using the file. Exit any other application that is using the file.

Item 3. Make sure that there is sufficient free space on the disk to output the common-exclusion-conditions extended definition file.

Cause:A I/O error has occurred while loading the event acquisition filter., A I/O error has occurred while updating the event acquisition filter.

Check the two items described below in the following directories, and then retry the operation.

In Windows:

Physical host: Console-path\conf\console\filter\

Logical host: shared-folder\JP1Cons\conf\console\filter\

In UNIX:

Physical host: /etc/opt/jp1cons/conf/console/filter/

Logical host: shared-directory/jp1cons/conf/console/filter/

Item 1. Make sure that you can write to the event acquisition filter definition list file. If you cannot, assign write permission.

Item 2. If the event acquisition filter definition list file (receive_filter_list.conf) exists, check whether any other application is using the file. Exit any other application that is using the file.

If neither of the above items apply, the event acquisition filter definition file might have been corrupted. If you have backed up the event acquisition filter definition file, restore that file, and then retry the operation. If you have not backed up the file, execute the following command to create a file, and then retry the operation.

In Windows:

copy Console-path\conf\console\filter\receive_filter.conf.model Console-path\conf\console\filter\receive_filter.conf

In UNIX:

cp -p /etc/opt/jp1cons/conf/console/filter/receive_filter.conf.model /etc/opt/jp1cons/conf/console/filter/receive_filter.conf

Cause:A memory shortage occurred.

Allocate sufficient memory, and then retry the operation.

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in other OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB0899-W

A regular expression that cannot be used was specified. (line number = line-number)

A regular expression that cannot be used is specified.

S:

Continues processing.

O:

Use the following procedure to take corrective actions:

Execute the jcochfilter command with the -check option specified as follows to check the contents of the definition.

jcochfilter -check output-common-exclusion-conditions-extended-definition-file

Based on the execution result of the jcochfilter command, correct the common-exclusion-conditions extended definition file.

Execute the jcochfilter command with the -ef option specified as follows to apply the corrections to the system.

jcochfilter -ef corrected-common-exclusion-conditions-extended-definition-file [ -h logical-host-name]

KAVB0900-E

The specified operation mode of the common exclusion conditions is already set.

The operation mode of the specified common exclusion-conditions has already been set.

S:

Aborts processing.

O:

Carefully review the operation mode of the specified common exclusion-conditions.

KAVB0902-W

The business group or monitoring group is not defined. (group name = group-name)

The command could not be executed because the business group or monitoring group was not defined.

S:

Continues processing.

O:

Define the specified business group or monitoring group, or carefully review the specified business group or monitoring group. Then, retry the operation.

KAVB0903-E

The business group or monitoring group is not defined. (group name = group-name)

The command could not be executed because the business group or monitoring group was not defined.

S:

Aborts processing.

O:

Carefully review the specified business group or monitoring group.

If there is no problem, check with a system administrator to see if the specified business group or monitoring group has been defined.

KAVB0961-E

Reading of the system color definition file was stopped. (detailed information = detailed-information)

An error occurred during reading of the system color definition file.

S:

Stops reading of the system color definition file.

O:

Check whether the system color definition file exists. If the file does not exist, create the file.

Check whether there is read permission for the system color definition file. If there is no read permission, set read permission for the system color definition file.

In any other case, contact a system administrator.

KAVB0962-W

A parameter in the system color definition file being read will be ignored. detailed-information (line number = line-number)

A parameter in the system color definition file being read was ignored.

S:

Invalidates the parameter in the system color definition file that is being read, and continues reading.

O:

There is an error in the specified parameter. Carefully review and correct the definition in the system color definition file referencing the detailed information and line number indicated in the message.

If an unnecessary parameter is specified, delete or comment out that parameter based on the line number in the message.

If no value is specified for the parameter, specify a value for the parameter.

If an invalid value is specified for the parameter, check and correct the value.

If the value specified for the parameter is outside the specifiable range, check and correct the value.

If multiple parameters are specified, delete or comment out unnecessary parameters.

If an invalid severity is specified, review and correct the severity.

KAVB1002-I

The command (command-name) terminates normally.

The command ended normally.

KAVB1003-I

The command (command-name) terminates abnormally.

The command ended abnormally.

KAVB1004-E

System error occurred in executing the command (command-name).

A system error occurred while executing the command.

S:

Stops command execution.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1005-I

The command (command-name) has started.

The command has started.

KAVB1010-E

Extra arguments (identifier) are specified.

Extra arguments are specified for the command.

S:

Stops command execution.

O:

Determine the correct use of the command, and then enter the command again.

KAVB1011-E

Arguments are missing.

Arguments specified for the command are missing.

S:

Stops command execution.

O:

Determine the correct use of the command, and then enter the command again.

KAVB1012-E

The reading of the command button definition file was stopped. (detailed information = detailed-information)

An error occurred during reading of the command button definition file.

S:

Stops reading of the command button definition file.

O:

Check whether the command button definition file exists. If the file does not exist, create the file.

Check whether there is read permission for the command button definition file. If there is no read permission, set read permission for the command button definition file.

In any other case, contact a system administrator.

KAVB1013-E

The reading of the command button definition file was stopped. detailed-information (line number = line-number)

An error occurred during reading of the command button definition file.

S:

Stops reading of the command button definition file.

O:

There is an error in the specification of the def or end-def parameter. Review and correct the definition in the command button definition file referencing the detailed information and line number indicated in the message.

KAVB1014-W

The command button definition was disabled while being read. detailed-information (line number = line-number)

The command button definition being read was invalidated.

S:

Invalidates the command button definition that is being read, and continues reading.

O:

There is an error in the specified parameter. Review and correct the definition in the command button definition file referencing the detailed information and line number indicated in the message.

If the number of command button definitions exceeds the maximum value, delete or comment out unnecessary command button definitions.

If the target user name is not specified for the usr parameter, delete the usr parameter or specify the target user name for the usr parameter.

If there is an error in the specification of the btn or end-btn parameter, check the combination of the btn and end-btn parameters, and then correct the error.

If there is an error in the specification of the def or end-def parameter, check the combination of the def and end-def parameters, and then correct the error.

KAVB1015-W

A parameter in the command button definition file being read will be ignored. detailed-information (line number = line-number)

A parameter in the command button definition file being read was ignored.

S:

Ignores the parameter in the command button definition file that is being read, and continues reading.

O:

There is an error in the specified parameter. Review and correct the definition in the command button definition file referencing the detailed information and line number indicated in the message.

If an unnecessary parameter is specified, delete or comment out that parameter based on the line number in the message.

If multiple parameters are specified, delete or comment out unnecessary parameters.

KAVB1016-W

An error exists in a parameter in the command button definition file being read. detailed-information (line number = line-number)

There was an error in a parameter in the command button definition file being read.

S:

Changes the parameter setting in the command button definition file that is being read, and continues reading.

O:

There is an error in the specified parameter. Review and correct the definition in the command button definition file referencing the detailed information and line number indicated in the message.

If no value is specified for the parameter, specify a value for the parameter.

If an invalid value is specified for the parameter, check and correct the value.

If the length of the comment for the host group exceeds the maximum number of characters, change the comment so that its length does not exceed the maximum.

If the number of target user names for the host group exceeds the maximum value, divide the host group or delete unnecessary target users.

If the length of the target user name for the host group exceeds the maximum number of bytes or if the same target user name is specified more than once, correct the target user name.

If the length of the comment for a command button exceeds the maximum number of characters, change the comment so that its length does not exceed the maximum.

KAVB1017-W

The Command button being loaded was disabled. detailed-information (line number = line-number)

The command button being loaded was disabled.

S:

Disables the command button that is being read, and continues loading.

O:

There is an error in the specified parameter. Review and correct the definition in the command button definition file referencing the detailed information and line number indicated in the message.

If the number of command buttons exceeds the maximum value, delete or comment out unnecessary command buttons.

If a command button name is not specified, specify a command button name.

If the length of a command button name exceeds the maximum number of characters, reduce the characters in the command button name to less than the maximum.

If the cmd parameter is not specified, specify it.

If a command line is not specified, specify a command line.

If the command line length exceeds the maximum number of bytes, change the command line so that its length does not exceed the maximum.

If an environment variable file name is not specified, specify the environment variable file name.

If the length of an environment variable file name exceeds the maximum number of bytes, change the file name so that its length does not exceed the maximum.

If an execution host name is not specified, specify the execution host name.

If the length of an execution host name exceeds the maximum number of bytes, change the execution host name so that its length does not exceed the maximum.

If the same command button name is specified more than once, change the command button name.

If a command button name contains control characters, delete them from the command button name.

If there is an error in the specification of the btn or end-btn parameter, check the combination of the btn and end-btn parameters, and then correct the error.

KAVB1018-E

The command button definition file could not be read.

The Execute Command window could not be displayed because the command button definition file could not be read.

S:

Stops display of the Execute Command window.

O:

Carefully review the definition in the command button definition file referencing the messages from KAVB1012-E to KAVB1017-W, and then retry displaying the Execute Command window.

KAVB1019-Q

command-button-name will be executed. Do you want to continue?

Comment: command-button-comment

This message asks you whether you want to execute the command assigned to the command button.

S:

Executes the command assigned to the command button if Yes is clicked. If No is clicked, the system does not execute the command.

KAVB1020-W

The location of the command button definition file version is invalid. (line = line-number, file = file-name)

The command button definition file does not begin with the file version.

S:

Assumes the default file version and continues processing.

O:

Specify the file version at the beginning of the command button definition file.

KAVB1021-W

The version information for the command button definition file is invalid. (line = line-number, file = file-name)

The version information is invalid.

S:

Assumes the default file version and continues processing.

O:

Correct the error in the command button definition file, and then retry the operation.

KAVB1031-Q

The values below will be set. Do you want to continue?

Button name = [Command] button name

Comment = [Command] button comment

This message asks you whether you want to execute the command.

S:

Executes the command if the Execute button is clicked. If the Cancel button is clicked, the system closes the Preview Command Execution Content window without executing the command.

KAVB1032-W

The specified string could not be converted or is too long.

The values below will be set. Are you sure you want to continue?

Button name = [Command] button name

Comment = [Command] button comment

An item could not be replaced with a variable, or the value of an item was truncated because the upper limit was exceeded.

S:

Executes the command if the Execute button is clicked. If the Cancel button is clicked, the system closes the Preview Command Execution Content window without executing the command.

O:

Check the information displayed in the Preview Command Execution Content window.

KAVB1033-I

The client application started. (command = command-line)

The client application started.

KAVB1034-E

The client application failed to start. (command = command-line)

An attempt to start the client application failed.

S:

Suspends processing.

O:

Check whether the command indicated by command-line can be executed from the command prompt.

If the command can be executed, re-execute the command.

KAVB1035-E

The command cannot be executed because a JP1 event that references information is not specified.

The command cannot be executed because a JP1 event to be inherited is not specified.

S:

Suspends execution of the command.

O:

Specify the JP1 event to be inherited, and then re-exeucte the command.

KAVB1036-W

The input exceeded the size of the input area. The part exceeding the limit will be truncated. (maximum size = maximum-size)

The value before truncation exceeds the maximum size of the input area. The part exceeding the maximum size will not be resumed.

S:

Displays the value from which the part exceeding the upper limit was truncated.

O:

Carefully review the input value that was present before the JP1 event attribute value was inherited.

KAVB1037-E

The command cannot be executed because the value specified for item exceeds the maximum. (maximum size = maximum-size)

The value specified for item exceeds the maximum value. Alternatively, the value obtained by converting the event information exceeds the maximum value for item.

If item is an execution host name, the maximum value is 255 bytes (or 2,048 bytes if IM Configuration Management Service is running and a business group name or monitoring group name is specified for the execution host name). The maximum value is 4,096 bytes for an execution command, and 255 bytes for an environment variable file.

S:

Suspends execution of the command.

O:

Adjust the length of the execution host name, execution command, or environment variable file so that the length does not exceed the maximum value for the item during execution of the command.

KAVB1040-W

The unconverted string specified in the definition-file already exists. (line number = line-number)

The same pre-conversion character is specified more than once in the definition file.

S:

Ignores the duplicate defition, and continues processing.

O:

Correct the error at the location indicated by the line number in the message.

KAVB1041-W

The unconverted string specified in the definition-file is invalid. (line number = line-number)

The pre-conversion character specified in the definition file is invalid.

S:

Ignores the invalid defition, and continues processing.

O:

Correct the error at the location indicated by the line number in the message.

KAVB1042-W

The converted string specified in the definition-file is invalid. (line number = line-number)

The converted character specified in the definition file is invalid.

S:

Ignores the invalid defition, and continues processing.

O:

Correct the error at the location indicated by the line number in the message.

KAVB1043-W

The number of definitions in the definition-file exceeds the limit. (maximum-number items)

The number of definitions specified in the definition file exceeds the maximum value.

S:

Ignores the definitions exceeding the maximum, and continues processing.

O:

Carefully review and correct the number of definitions.

KAVB1044-W

The format of a definition in the definition-file is invalid. (line number = line-number)

A definition specified in the definition file is invalid.

S:

Ignores the invalid defition, and continues processing.

O:

Correct the error at the location indicated by the line number in the message.

KAVB1045-I

The definition-file was loaded.

The definition file was loaded.

KAVB1046-E

The definition-file failed to load.

An attempt to load the definition file failed.

S:

Stops loading of the definition file, and does not start the Execute Command window.

O:

Check whether the definition file can be read.

If the file can be read, check the following OS log items to see if a shortage has occurred in other OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a shortage has not occurred in any OS resources, use the data collection tool to collect data, and then contact a system administrator.

KAVB1101-E

System error occurred in analyzing the definition file.

A system error occurred during analysis of the definition file.

S:

Stops analysis of the definition file.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1102-E

Memory shortage occurred in analyzing the definition file.

A memory shortage occurred during analysis of the definition file.

S:

Stops analysis of the definition file.

O:

Allocate sufficient memory for command execution, and then re-execute analysis processing.

KAVB1104-W

The business group or monitoring group is not defined. (definition type = definition-type, filter name = filter-name, definition name = definition-name, group name = group-name)

The business group or monitoring group is not defined.

S:

Continues processing.

O:

Define the specified business group or monitoring group, or carefully review the specified business group or monitoring group.

KAVB1105-W

The business group or monitoring group is not defined. (definition type = definition-type, filter name = filter-name, definition name = definition-name)

The business group or monitoring group specified for the definition indicated in the message is not defined.

S:

Invalidates the specification of the business group or monitoring group, and continues processing.

O:

Carefully review the definition, and set it again.

KAVB1111-E

An I/O error occurred in analyzing the file (file-name).

An I/O error occurred during analysis of the definition file.

S:

Stops analysis of the definition file or analysis of the file where the I/O error occurred and continues processing.

O:

Make sure the value in the encode file is correctly set, or use the data collection tool to collect data, and then contact a system administrator.

KAVB1112-E

Cannot access the directory (directory-name).

The directory does not exist, or a file name is specified. Another possibility is that there is no access permission for the directory.

S:

Stops analysis of the directory.

O:

Specify the directory correctly.

KAVB1113-W

Cannot access the file (file-name).

The file does not exist, or a directory name is specified. Another possibility is that there is no access permission for the file.

S:

Stops analysis of the file specified by file-name and continues processing other files.

O:

Specify the file correctly.

KAVB1114-W

The block is constructed incorrectly. processing-contents, Cause cause-information (file-name:line-number)

processing-contents is executed because the block in the definition file is constructed incorrectly.

S:

Stops analysis of the specified file and continues processing other files.

O:

Construct the block correctly according to cause-information.

KAVB1115-W

The record is constructed incorrectly. processing-contents, Cause cause-information (file-name:line-number)

processing-contents is executed because the record in the definition file is constructed incorrectly.

S:

Executes processing-contents and continues processing.

O:

Construct the record correctly according to cause-information.

KAVB1116-W

Mandatory parameters(identifier) are not specified. processing-contents, (file-name:line-number)

processing-contents is executed because the required parameters are not specified in the definition file or a record in the definition file.

S:

Executes processing-contents and continues processing.

O:

Specify the missing parameters.

However, if a message is output because the linkage product is not installed, corrective action is not necessary.

KAVB1117-W

Extra parameters (identifier) are specified. processing-contents:(file-name:line-number)

Processing indicated in processing-contents is executed because extra parameters are specified in the definition file or a record in the definition file.

S:

Executes processing-contents and continues processing.

O:

Delete extra parameters.

KAVB1118-W

Undefined parameters(identifier) are specified. processing-contents:(file-name:line-number)

Processing indicated in processing-contents is executed because undefined parameters are specified in the definition file or a record in the definition file.

S:

Executes processing-contents and continues processing.

O:

Check the version of JP1/IM - Manager and define parameters using the contents supported by the version.

KAVB1119-W

Invalid value (identifier) is specified. processing-contents:(file-name:line-number)

Processing indicated in processing-contents is executed because invalid values are specified in the definition file or a record in the definition file.

S:

Executes processing-contents and continues processing.

O:

Define correct values.

KAVB1120-W

The value(identifier) is duplicated. processing-contents (file-name:line-number)

Processing indicated in processing-contents is executed because a value that is already defined is specified in the definition file or a record in the definition file.

S:

Executes processing-contents and continues processing.

O:

Change the value that is already defined or the current definition.

KAVB1121-W

"identifier-1" and "identifier-2" cannot be specified at the same time. processing-contents: (file-name:line-number)

Processing indicated in processing-contents is executed because values that cannot be specified at the same time are specified in the definition file or a record in the definition file.

S:

Executes processing-contents and continues processing.

O:

Delete identifier-1 or identifier-2.

KAVB1130-W

An attempt to read the file that defines which items are displayed for event conditions has failed. (file: file-name)

An attempt to read the file that defines which items are displayed for event conditions failed.

S:

Stops reading the file and continues processing.

O:

Check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1131-W

The display item is not specified. (file = file-name)

The default value is specified because the display item is not specified in the file that defines which items are displayed for event conditions.

S:

Uses the default value to continue processing.

O:

Specify the display item in the file that defines which items are displayed for event conditions, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1132-W

More than 256 display item have been specified. (line = line-number, file = file-name)

More than 256 display items are specified in the file that defines which items are displayed for event conditions.

S:

Stops reading data and continues processing, ignoring the 257th and subsequent display items.

O:

Correct the file that defines which items are displayed for event conditions, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1133-W

The display item has been duplicated. (line = line-number, file = file-name)

The display item specified in the file that defines which items are displayed for event conditions is duplicated.

S:

Ignores the line where the item is duplicated and continues processing.

O:

Correct the file that defines which items are displayed for event conditions, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1134-W

An invalid display item is specified. (line = line-number, file = file-name)

An invalid display item is specified in the file that defines which items are displayed for event conditions.

S:

Ignores the line where the invalid item is specified and continues processing.

O:

Correct the file that defines which items are displayed for event conditions, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1135-E

The file that defines which items are displayed for event conditions was not found.

The file that defines which items are displayed for event conditions was not found.

S:

Stops reading of the file that defines which items are displayed for event conditions and continues processing.

O:

Check the following items, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Determine whether the file that defines which items are displayed for event conditions exists. If the file does not exist, create the file.

Determine whether there is read permission for the file that defines which items are displayed for event conditions. If there is no read permission, set read permission for the file that defines which items are displayed for event conditions.

KAVB1136-W

Reading of the common exclusion conditions display item definition file failed. (file name = file-name)

An attempt to read the common-exclusion-conditions display item definition file failed.

S:

Stops reading and continues processing.

O:

Check the following OS log items to see if a shortage has occurred in other OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1137-W

The display item is not specified. (file = file-name)

The default value is specified because the display item is not specified in the common-exclusion-conditions display item definition file.

S:

Continues processing using the defalut value.

O:

Specify the display item in the common-exclusion-conditions display item definition file, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1138-W

More than 256 display item have been specified. (line = line-number, file = file-name)

More than 256 display items are specified in the common-exclusion-conditions display item definition file.

S:

Stops reading data and continues processing, ignoring the 257th and subsequent display items.

O:

Correct the common-exclusion-conditions display item definition file, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1139-W

The display item has been duplicated. (line = line-number, file = file-name)

A duplicate display item is specified in the common-exclusion-conditions display item definition file.

S:

Ignores the line where the duplicate item is specified and continues processing.

O:

Correct the common-exclusion-conditions display item definition file, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1140-W

An invalid display item is specified. (line = line-number, file = file-name)

An invalid display item is specified in the common-exclusion-conditions display item definition file.

S:

Ignores the line where the invalid item is specified and continues processing.

O:

Correct the common-exclusion-conditions display item definition file, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1141-E

The common exclusion conditions display item definition file was not found.

The common-exclusion-conditions display item definition file is not found.

S:

Stops trying to read the common-exclusion-conditions display item definition file, and continues processing.

O:

Check the following items, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Check whether the common-exclusion-conditions display item definition file exists. If the file does not exist, create the file.

Check whether there is read permission for the common-exclusion-conditions display item definition file. If there is no read permission, set read permission for the file.

KAVB1148-Q

The selected item-1 will be changed to item-2. Do you want to continue?

This message asks you whether you want to change the selected item 1 to item 2.

S:

Continues processing if the Yes button is clicked.

If the No button is clicked, the system cancels processing and returns to the previous window.

KAVB1149-Q

Are you sure you want to delete the selected filters?

This message asks you whether you want to delete all the selected filters.

S:

Deletes the selected filters if the Yes button is clicked. If the No button is clicked, the system does not delete the selected filters.

KAVB1150-I

An additional common exclusion conditions group was registered. (common exclusion conditions group ID = common-exclusion-conditions-group-ID, common exclude conditions group name = common-exclude-conditions-group-name, registering user = user-name)

An additional common exclusion-condition group was registered.

KAVB1151-Q

Are you sure you want to delete the selected conditions groups?

This message asks you whether you want to delete all the selected condition groups.

S:

Deletes the selected condition groups if the Yes button is clicked. If the No button is clicked, the system does not delete the selected condition groups.

KAVB1152-Q

The selected additional common exclusion conditions groups will be changed to common exclusion conditions groups. Do you want to continue?

This message asks you whether you want to change the selected additional common exclusion-condition group to a common exclusion-condition group.

S:

Changes the selected additional common exclusion-condition group to a common exclusion-condition group if the Yes button is clicked. If the No button is clicked, the system does not change anything.

KAVB1153-E

The auto-input definition file for common exclusion conditions was not found.

The common-exclusion-conditions auto-input definition file is not found.

S:

Stops trying to read the common-exclusion-conditions auto-input definition file, and continues processing.

O:

Check the following items, and then execute the jco_spmd_reload command to reload JP1/IM - Manager or restart JP1/IM - Manager.

Check whether the common-exclusion-conditions auto-input definition file exists. If the file does not exist, create the file.

Check whether there is permission for the common-exclusion-conditions auto-input definition file. If there is no read permission, set read permission for the common-exclusion-conditions auto-input definition file.

KAVB1154-W

The auto-input definition file for common exclusion conditions failed to load. (file name = file-name)

An attempt to read the common-exclusion-conditions auto-input definition file failed.

S:

Stops trying to read the common-exclusion-conditions auto-input definition file, and continues processing.

O:

Check the following OS log items to see if a shortage has occurred in other OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a shortage has not occurred in any OS resources, use the data collection tool to collect data, and then contact a system administrator.

KAVB1155-E

No more definitions can be added because the number of definitions in the common exclusion conditions group (extended) has reached the maximum. (maximum number of definitions in the conditions group = maximum-number)

No more definitions can be added because the number of common exclusion-condition groups (extended) has reached the maximum.

O:

Delete unnecessary common exclusion-condition groups.

KAVB1156-W

The event acquisition filter settings from JP1/IM - View were discarded because the settings for event acquisition filters that use additional common exclusion conditions are configured in JP1/IM - Manager.

The event acquisition filter settings from JP1/IM - View were discarded because the event acquisition filters using additional common exclusion-conditions were set in JP1/IM - Manager.

S:

Invalidates the settings from JP1/IM - View and continues processing.

O:

To set filters in JP1/IM - Manager in which filters that use an additional common exclusion-condition group are specified, use JP1/IM - View version 10-00 or later.

KAVB1157-E

No more definitions can be added because the size of the additional exclusion conditions group (extended) filters has reached the maximum. (conditions group maximum size = maximum-size)

No more definitions can be added because the size of the common exclusion-condition group (extended) filters has reached the maximum.

O:

Delete unnecessary common exclusion-condition groups, or define the condition group so that the size does not exceed the maximum.

KAVB1158-W

An attribute name has not been specified. (file name = file-name)

The default value is used because the attribute name is not specified in the common-exclusion-conditions auto-input definition file.

S:

Continues processing using the default value.

O:

Specify the attribute name in the common-exclusion-conditions auto-input definition file, and then reload the file by executing the jco_spmd_reload command, or restart JP1/IM - Manager.

KAVB1159-W

An invalid attribute name is specified. (line number = line-number, file name = file-name)

An invalid attribute name is specified in the common-exclusion-conditions auto-input definition file.

S:

Ignores the line where the invalid attribute name is specified and continues processing.

O:

Correct the error in the common-exclusion-conditions auto-input definition file, and then reload the file by executing the jco_spmd_reload command, or restart JP1/IM - Manager.

KAVB1160-W

The attribute name is specified multiple times. (line number = line-number, file name = file-name)

An duplicate attribute name is specified in the common-exclusion-conditions auto-input definition file.

S:

Ignores the line where the duplicate attribute name is specified and continues processing.

O:

Correct the error in the common-exclusion-conditions auto-input definition file, and then reload the file by executing the jco_spmd_reload command, or restart JP1/IM - Manager.

KAVB1161-W

The common exclusion conditions group name was truncated because it exceeded maximum-length bytes.

The length of the common exclusion-condition group name specified in the common-exclusion-conditions auto-input definition file exceeds the maximum length.

S:

Deletes the excess character string, and continues processing.

O:

Correct the error in the common-exclusion-conditions auto-input definition file, and then reload the file by executing the jco_spmd_reload command, or restart JP1/IM - Manager.

KAVB1162-W

The value of the parameter parameter is invalid. (line = line-number, file = file-name)

The value of the indicated parameter is invalid.

S:

Ignores the line where the invalid value is specified and continues processing.

O:

Correct the error in the common-exclusion-conditions auto-input definition file, and then reload the file by executing the jco_spmd_reload command, or restart JP1/IM - Manager.

KAVB1163-E

The common exclusion conditions could not be set. (cause = cause)

An error occurred during setting of the common exclusion-conditions.

S:

Terminates processing.

O:

If one of the following messages is displayed for cause, check the operation mode for the JP1/IM - Manager common exclusion-conditions, restart JP1/IM - View, and then retry the operation.

JP1/IM - Manager is running in compatibility mode.

The common exclusion conditions is operating in a basic mode.

If the message shown below is displayed for cause, the definition file might be corrupted. Stop JP1/IM - Manager, change the operation mode for the common exclusion-conditions to basic mode, and then change it back to extended mode to initialize the definition of the common exclusion-conditions (extended).

The common exclusion extended definition file is invalid.

If the message shown below is displayed for cause, the IM database service is not running. Make sure that the KAVB4003-I message was output to the integrated trace log of the manager, and then retry the operation. If the KAVB4003-I message was not output and you are using the integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service. When you have confirmed that the IM database service is running and the KAVB4003-I message is output to the integrated trace log, retry the operation.

An attempt to switch the event acquisition filter has failed.

If the message shown below is displayed for cause, the definition includes a character that might cause character corruption when the definition is stored. Ensure that any environment-dependent character or other character that might cause character corruption is not used, and then apply the definition again.

A character that cannot be stored successfully is included.

If a message other than the above is displayed for cause or if the problem cannot be resolved, check the following OS log items.

In Windows: Windows event log

In UNIX: System log (syslog)

After checking the OS log items, check whether a shortage has occurred in other OS resources such as file descriptors. If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1190-E

An error occurred while reading the system definition file. (cause = cause, file name = file-name)

An error occurred while the system definition file was being read.

S:

Ignores the contents of the system definition file, and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1191-E

An error occurred while reading the severity change definition file. (cause = cause, file name = file-name)

An error occurred while the severity change definition file was being read.

S:

Ignores the contents of the severity change definition file, and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1192-E

An error occurred while reading the display message change definition file. (cause = cause, file name = file-name)

An error occurred while reading the display message change definition file.

S:

Ignores the contents of the display message change definition file, and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1200-E

Communication error occurred in establishing the connection.

Host name: host-name, Port number: port-number

Details: detailed-information

An attempt to connect to the specified host failed.

S:

Suspends processing.

O:

Check the following items, and then retry the operation.

Is the entered connecting host name correct?

Is the host to be connected running?

Is there a communication problem with the host to be connected to?

KAVB1201-E

Communication error occurred in receiving data.

Host name: host-name, Port number: port-number

Details: detailed-information

Reception processing failed during communication.

S:

Suspends processing.

O:

Perform the operation again. IPv6 addresses cannot be used for connection. If a KAVB1880-E message was output to the integrated trace log of the connected manager host, see the instructions provided in that message.

KAVB1202-E

Communication error occurred in sending data.

Host name: host-name, Port number: port-number

Details: detailed-information

Send processing failed during communication.

S:

Suspends processing.

O:

Perform the operation again. IPv6 addresses cannot be used for connection. If a KAVB1880-E message was output to the integrated trace log of the connected manager host, see the instructions provided in that message.

If you are using the communication encryption function, check its settings for errors.

KAVB1203-E

Communication error occurred during communication.

Host name: host-name, Port number: port-number

Details: detailed-information

An error occurred during communication.

S:

Suspends processing.

O:

Perform the operation again. IPv6 addresses cannot be used for connection. If a KAVB1880-E message was output to the integrated trace log of the connected manager host, see the instructions provided in that message.

If you are using the communication encryption function, check its settings for errors.

KAVB1204-E

An error occurred in the communication processing.

Host name: host-name, Port number: port-number

Details: detailed-information

An error occurred during communication processing at the viewer side.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1205-E

Timeout occurred in the server processing.

Host name: host-name, Port number: port-number

A time-out occurred during processing at the server side.

S:

Suspends processing.

O:

Carefully review the communication time-out setting. IPv6 addresses cannot be used for connection. If a KAVB1880-E message was output to the integrated trace log of the connected manager host, see the instructions provided in that message.

If you are using the communication encryption function, check its settings for errors.

KAVB1206-E

An error occurred in starting the server.

Host name: host-name, Port number: port-number

Details: detailed-information

An attempt to start the server failed.

S:

Suspends processing.

O:

Contact a network administrator.

KAVB1207-E

An error occurred in the communication processing on the server side.

Host name: host-name, Port number: port-number

Details: detailed-information

An error occurred during communication processing at the server side.

If you are using an integrated monitoring database, the integrated monitoring database is not in operating status.

S:

Suspends processing.

O:

When this message is displayed while using the jcochstat command:

You cannot use the jcochstat command with JP1/IM - Central Console (Satellite Console) version 06-00. Check the version of the specified JP1/IM - Central Console (Satellite Console).

When an integrated monitoring database is used:

Execute the jimdbstatus command to check the status of the IM database service of the manager host. If you are able to confirm that the IM database service is operating, retry the operation. If a KAVB8602-E message was output in the integrated trace log of the manager host, take the corrective action given for that message.

In cases other than the above:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1208-E

An error occurred in communication processing.

Details: detailed-information

An error occurred during communication processing at the server side.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator. IPv6 addresses cannot be used for connection. If a KAVB1880-E message was output to the integrated trace log of the connected manager host, see the instructions provided in that message.

KAVB1209-E

An error occurred in the server side communication processing.

Details: detailed-information

An error occurred during communication processing at the server side.

S:

Suspends processing.

O:

When this message is displayed during login to JP1/IM - Console View version 06-51:

JP1/IM - Console View version 06-51 cannot be connected to JP1/IM - Central Console (Satellite Console) version 06-00. Check the version of the specified JP1/IM - Central Console (Satellite Console).

In cases other than the above:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1210-E

A communication error occurred while establishing a connection.

Cannot convert the host name into an IP address.

Confirm the host name.

Host name:host-name, Port number:port-number

Details: detailed-information

A communication error occurred while establishing a connection.

S:

Continues processing.

O:

If you are using the system in a DNS environment, check the DNS settings.

If you are using the system using the hosts file, check the hosts file settings.

KAVB1211-W

The port number of the service-name service could not be acquired.

The default port number port-number will be used now and the system will run.

Confirm the setting.

An attempt to acquire the port number failed while starting JP1/IM - Manager.

S:

Uses the default port number and continues processing.

O:

Carefully review the port number setting.

KAVB1401-E

Failed to build a message due to an exception (exception-class-name).

An attempt to build a message failed because an exception occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1501-E

Cannot execute the request. Invalid data is included in the request to the server.

Server name=server-name

Request to server=request-to-server

Invalid information is included in the request to the server.

S:

Suspends processing.

O:

Retry the operation. If the same message is displayed, collect data, and then contact a system administrator.

KAVB1502-E

System error occurred in the server.

Server name=server-name

A system error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1503-E

Memory shortage occurred in the server.

Server name=server-name

A memory shortage occurred in the server.

S:

Suspends processing.

O:

In the unit at the manager side, exit applications that are not being used.

KAVB1504-E

An error occurred in the communication between the server and Event Service.

Server name=server-name

The possible causes are as follows:

The manager is not running.

Event Service is not running.

The processing request load is temporarily high.

S:

Suspends processing.

O:

Take corrective action according to the cause of the error.

Make sure that the manager is running.

Make sure that Event Service is running.

Retry the operation. If repeated retrying does not work, restart the viewer, and then retry the operation.

KAVB1506-E

Cannot find the file in the server.

Server name=server-name

File name=file-name

An error occurred in the manager.

S:

Suspends processing.

O:

Contact a system administrator.

KAVB1507-E

The object on the server is not in the state to be able to accept the request.

Server name=server-name

Object=object

Status=status

Request=request

The object on the server is not in a state able to accept the request.

S:

Suspends processing.

O:

Wait awhile, and then retry the operation.

KAVB1509-E

Failed to communicate with the server.

Server name=server-name

The possible causes are as follows:

The manager is not running.

Event Service is not running.

The processing request load is temporarily high.

The IM database service is not in operating status.

The settings of the communication encryption function are not correct.

An error occurred in communication with the connecting host.

S:

Suspends processing.

O:

Take corrective action according to the cause of the error.

Make sure that the manager is running.

Make sure that Event Service is running.

Retry the operation. If repeated retrying does not work, restart the viewer, and then retry the operation.

If you are using an integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service of the manager host. If you are able to confirm that the IM database service is operating, retry the operation. If a KAVB8602-E message was output in the integrated trace log of the manager host, take the corrective action given for that message.

If you are using the communication encryption function, check its settings for errors.

Check communication with the connecting host for problems.

KAVB1510-E

Failure either in the file or network I/O on the server.

Server name=server-name

An error occurred in the manager.

S:

Suspends processing.

O:

Check the integrated trace log of the manager to see if an Event Console Service error message was output (error messages KAVB0001 to KAVB2000).

If a message was output, take the corrective action given for that message.

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1512-E

System error occurred.

A system error occurred.

S:

Suspends processing.

O:

Contact a system administrator.

KAVB1513-W

Cannot display some event(s).

There were no events to obtain from the event buffer on the connecting host.

All the events except the above will be displayed.

To search for an event which was not displayed, specify the search conditions in the event search condition settings dialog as follows:

(1) In "Search host", specify the name of the connecting host.

(2) In "Registered timeframe", specify the times when the events before and after this event were registered.

Check to see if the following conditions are met when this event appears frequently.

(1) The "Interval" value that was set for "Automatic refresh" in the Preferences window is too long.

(2) The "Num. of events to acquire at update" value that was set in the Preferences window is too small.

(3) The "Event buffer" value for the Manager that was set in the System Environment Settings window is too small.

The event could not be displayed because the event that the system tried to acquire was not in the event buffer of the connected host.

S:

Continues processing.

O:

If this message is displayed frequently, carefully review the settings to see if any of the following conditions apply.

The Interval setting for Automatic refresh specified in the Preferences window is too long.

The Num. of events to acquire at update setting specified in the Preferences window is too small.

The Event buffer setting of the manager specified in the Preferences window is too small.

KAVB1515-E

Failed to obtain the information about the event selected. Cannot continue processing.

Information about the selected event could not be obtained from the event service or integrated monitoring database.

S:

Suspends processing.

O:

Check the contents of the selected event, the position in the scroll buffer, and whether Event Service is running. Also, make sure that the selected event is on the event database.

If you are using an integrated monitoring database, determine whether any of the following messages is displayed in the integrated trace log of the manager. If a message is output, take the corrective action given for that message.

• KAVB1660-E

• KAVB1661-E

• KAVB1662-E

• KAVB1678-E

If no message is output, contact a system administrator.

KAVB1516-W

An error occurred in acquiring an event from the event service.

Cannot recover the error after attempting the number of retries specified in the system profile.

No more events will be displayed from now on due to this error. Please check if the event service is running or not.

If not, recover the error by re-executing the manager after starting the event service.

An error occurred while acquiring an event from Event Service.

S:

Continues processing.

O:

Determine whether Event Service is running.

If Event Service is not running, start Event Service, and then start the manager to recover from the error.

If this message appears in the Search Events page of the Event Console window after event search is executed, confirm that the search host name is correct.

Make sure that the address of the connecting host name and search host name can be resolved on the manager.

KAVB1517-I

Started the manager.

The manager was started.

KAVB1518-I

Stopped the manager.

The manager was stopped.

KAVB1519-I

Stopping the manager because a termination request was received.

The manager was stopped because a termination request was received.

KAVB1520-E

Stopping the manager because an interruption.

Details: detailed-information

An error occurred in the manager.

S:

Stops the manager.

O:

Contact a system administrator.

KAVB1521-E

Stopping the manager because an error occurred.

Details: detailed-information

An error occurred in the manager.

S:

Stops the manager.

O:

Contact a system administrator.

KAVB1522-E

JP1/Base Event Service could not be connected so no further events will be displayed.

Connection between the manager and Event Service cannot be established.

O:

Determine whether Event Service is running.

If Event Service is not running, start Event Service, and then start the manager to recover from the error.

If this message is output after event search is executed, confirm that the search host name is correct.

If you are using the communication encryption function, review the settings to see if any of the following conditions apply:

Is there a configuration of the communication encryption feature between the manager and the host that match the destination host?

Does the settings in the non-SSL communication host configuration file on the manager's JP1/Base match the destination host?

Does the root certificate correspond to the server certificate of the manager's destination host?

KAVB1523-E

Some of the events selected no longer exist in the event DB on the Manager host.

So, their event attributes have not been changed.

An attempt was made to change the action status of an event or to delete an event that does not exist in the event database. Therefore, the event attributes could not be updated. This occurs when a new event exceeds the capacity of the event database on the manager, or when the event database is deleted.

S:

Refreshes the display on the active event console and continues processing.

KAVB1524-E

Could not apply the changes in the selected JP1 event attributes to the event DB on the Manager host.

An attempt to communicate with Event Service of JP1/Base failed.

S:

Continues processing.

O:

Make sure that Event Service of JP1/Base is running. If it is not running, start Event Service, and then perform the operation again.

If you are using an integrated monitoring database, check the integrated trace log of the manager to see if any of the following messages is displayed. If a message is output, take the corrective action given for that message.

• KAVB1663-E

• KAVB1664-E

• KAVB1665-E

• KAVB1674-E

• KAVB1675-E

• KAVB1676-E

If no message is output, contact a system administrator.

KAVB1525-E

An internal definition file is invalid. (detailed-information)

The definition information in the internal definition file is incorrect.

S:

Terminates processing of JP1/IM - Manager and JP1/IM - View. Also terminates the jcochstat command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1526-E

The specified event cannot change the corresponding conditions. Confirm the specified number of the serial number in the event DB.

A serial number in the event database of an event that cannot be updated is specified.

S:

Terminates processing.

O:

Carefully review the specified serial number in the event database.

KAVB1527-E

A condition that cannot be received by the search host is included.

Event search was executed by specifying either of the following, which are not supported by Event Service version 06-00 or earlier.

Is contained or Is not contained is specified.

More than one action status is specified.

Another possibility is that a regular expression that is not supported by Event Service version 06-00 or earlier is specified.

S:

Closes the Event Search Conditions window and returns to the Event Console window.

O:

Specify Match, Does not match, or First characters, and then retry the search.

Specify only one action status, and then retry the operation.

KAVB1528-E

The specified value of a definition setting is out of range. (setting item:setting)

The setting is out of range.

S:

Operates by rounding up the setting.

O:

Carefully review the setting.

KAVB1529-E

The value of a common definition setting is out of range. (label:setting)

The setting is out of range.

S:

Ignores the setting and continues processing using the default value.

O:

Carefully review the setting.

KAVB1531-E

definition-file is corrupt.

filename: file-name

An attempt to read the definition file failed because the definition file is corrupted.

S:

Terminates processing.

O:

Restore the definition file from the backup of the definition file displayed for file-name, and then restart JP1/IM - Manager. If the definition file has not been backed up, perform the following for each definition file.

For an event acquisition filter definition file, use the following method to copy the event acquisition definition file. After that, restart JP1/IM - Manager and reconfigure the event acquisition filter definition.

In Windows:

copy Console_path\conf\console\filter\receive_filter.conf.model Console_path\conf\console\filter\receive_filter.conf

In UNIX:

cp -p /etc/opt/jp1cons/conf/console/filter/receive_filter.conf.model /etc/opt/jp1cons/conf/console/filter/receive_filter.conf

For other definition files, delete the definition file, and then restart JP1/IM - Manager.

KAVB1532-E

The specified value of a definition setting is out of range.(setting item:setting)

The setting is outside the specifiable range.

S:

Ignores the setting and continues processing using the default value.

O:

Carefully review the setting.

KAVB1533-E

A value defined for an item (setting-item) is invalid. The default value (default-value) will be used.(jp1user-name = jp1user-name)

The setting is invalid.

S:

Ignores the setting and continues processing using the default value.

O:

In the Preferences window for the JP1 user, reconfigure the setting items.

KAVB1534-E

A value defined for an item (setting-item) is outside the valid range. The default value (default-value) will be used.(jp1user-name = jp1user-name)

The setting is outside the specifiable range.

S:

Ignores the setting and continues processing using the default value.

O:

In the Preferences window for the JP1 user, reconfigure the setting items.

KAVB1535-E

A connection to the authentication server could not be established.

The authentication server cannot be connected.

S:

Continues processing.

O:

Check the following items, and then take the appropriate corrective action:

Is the authentication server running?

Is communication with the authentication server possible?

Are the authentication server settings correct?

If you are using the communication encryption function, check its settings for errors.

KAVB1536-E

setting-item is invalid. The default value (default-value) will be used.

The set value is invalid.

S:

Ignores the set value, and continues processing using the default value.

O:

In the Preferences window for the JP1 user, reconfigure the setting items.

KAVB1538-W

The page that was displayed at the last logout could not be displayed. The Monitor Events page will be displayed.

The page that was displayed at the last logout could not be displayed.

S:

Displays the Monitor Events page.

O:

Check whether the relevant page can be displayed. Note that the Response-Waiting Events page is displayed when the response-waiting event management function is enabled and the setting that allows users to respond to and work with response-waiting events is enabled.

KAVB1539-W

The View filter that was selected at the last logout was not found. The View filter will be disabled and a screen will be displayed. (page = page, View filter name = view-filter-name)

The view filter that was selected on the page at the last logout was not found because the view filter has been deleted or renamed.

S:

Invalidates the view filter of the page, and then displays the window.

O:

Check whether the view filter that was selected at the last logout has been deleted or changed.

KAVB1540-W

Cannot display some event(s). (page = page)

There were no events to obtain from the event buffer on the connecting host.

All the events except the above will be displayed.

To search for an event which was not displayed, specify the search conditions in the event search condition settings dialog as follows:

(1) In "Search host", specify the name of the connecting host.

(2) In "Registered timeframe", specify the times when the events before and after this event were registered.

Check to see if the following conditions are met when this event appears frequently.

(1) The "Interval" value that was set for "Automatic refresh" in the Preferences window is too long.

(2) The "Num. of events to acquire at update" value that was set in the Preferences window is too small.

(3) The "Event buffer" value for the Manager that was set in the System Environment Settings window is too small.

The event could not be displayed on the page because the event (including hidden events) that the system tried to acquire was not in the event buffer of the connected host.

S:

Continues processing.

O:

If this message is displayed frequently, review the settings to see if any of the following conditions apply:

The Interval setting for Automatic refresh specified in the Preferences window is too long.

The Num. of events to acquire at update setting specified in the Preferences window is too small.

The Event buffer setting of the manager specified in the Preferences window is too small.

KAVB1541-E

The start position for event collection could not be obtained. The range of events to be collected at login will be disabled, and the Event Console will appear.

The start position for event collection at login could not be obtained. The possible causes are as follows:

A communication error occurred between JP1/IM - View and JP1/IM - Manager.

A connection cannot be established with the IM database service.

S:

Invalidates the range of events to be collected at login, and then displays the window.

O:

Check the following:

Check the integrated trace log to see if a JP1/IM - View error message was output before this message. If an error message was output, take the corrective action given for that message.

Check whether the IM database service is running. If the IM database service is not running, start it.

If you are using the communication encryption function, check its settings for errors.

After checking the above items, restart JP1/IM - View. If the problem persists, contact a system administrator.

KAVB1542-E

An error occurred during the collection of events from the integrated monitoring database. The range of events to be collected at login will be disabled, and the Event Console will appear.

Events cannot be acquired from the integrated monitoring database because a connection cannot be established with the IM database service.

S:

Invalidates the range of events to be collected at login, and then displays the window.

O:

Check whether the IM database service is running. If the IM database service is not running, start it.

After checking the above items, restart JP1/IM - View. If the problem persists, contact a system administrator.

KAVB1543-E

Event information could not be obtained from the integrated monitoring database, because that database is currently inactive. The range of events to be collected at login will be disabled, and the Event Console will appear.

Events cannot be acquired from the integrated monitoring database because the integrated monitoring database is disabled.

S:

Invalidates the range of events to be collected at login, and then displays the window.

O:

Check and, if necessary, correct the integrated monitoring database settings, and then restart JP1/IM - View.

KAVB1544-W

The function-name is enabled, but the prerequisite function-name is disabled. To use the function-name, enable the prerequisite function-name.

The function is enabled, but a prerequisite function is disabled. To use the enabled function, enable its prerequisite functions.

S:

Terminates processing.

O:

To use the function shown in the message, enable the function's prerequisite functions.

KAVB1551-E

An attempt to save the event-information mapping definition failed.

An attempt to write to the mapping definition file failed.

S:

Stops saving the mapping definitions and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1552-E

An attempt to read the event-information mapping definition failed.

An attempt to read the mapping definition file failed.

S:

Uses the default mapping definitions and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1554-E

A nonnumeric attribute value (attribute-value) cannot be mapped to a time-related display item (attribute-name).

For a time-related display item, a non-numeric value (number of seconds from UTC 01/01/1970 0:00:00) is specified.

S:

Ignores this time-related display item and continues mapping processing.

O:

For a time-related display item, specify numeric values (0 to 2,147,483,647 = UTC 01/01/1970 00:00:00 to 01/19/2038 3:14:07).

KAVB1556-E

During mapping of event information, a system error occurred.

An unexpected error was detected during mapping processing.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1558-E

An attempt to update the notification status has failed. (function ID = ID, detailed code = code)

An attempt to update notification status failed.

S:

Suspends update processing of notification status.

O:

If the same message appears repeatedly, collect data, and then contact a system administrator.

KAVB1570-I

A connection request from JP1/IM - View was refused because startup of the IM database service has not finished yet.

A connection request from JP1/IM - View was rejected because the system is waiting for startup of the IM database service to finish.

S:

Continues processing.

KAVB1571-I

A connection request from JP1/IM-Console View V6 (6i) was refused.

Connection was rejected because the setting to reject connection requests from JP1/IM - Console View V6 (6i) took effect.

KAVB1572-I

A connection request from jcochstat was refused.

Connection was rejected because the setting to reject connection requests from the jcochstat command took effect.

KAVB1573-W

The filter setting from JP1/IM - View was discarded, because an event receiver filter that uses OR is specified in JP1/IM - Manager.

The user filter setting from JP1/IM - View version 07-00 or earlier was discarded because a user filter using OR is set in JP1/IM - Manager.

S:

Invalidates the user filter setting and continues processing.

O:

To specified a user filter for JP1/IM - Manager in which a user filter using OR is set, use JP1/IM - View version 07-10 or later.

KAVB1574-W

The event acquisition settings in the system environment settings were discarded, because the version of JP1/IM - View currently in use is version 07-00 or earlier.

The event acquisition settings in the system environment settings are invalid because the version of JP1/IM - View being used is 07-00 or earlier. The event acquisition settings cannot be referenced or used.

S:

Ignores the event acquisition settings and continues processing.

O:

To set an event acquisition filter, use JP1/IM - View version 07-10 or later.

KAVB1575-W

The filter setting from JP1/IM - View was discarded, because a severe event definitions that uses OR is specified in JP1/IM - Manager.

The severe event setting from JP1/IM - View version 07-00 or earlier was discarded because severe event definitions using OR are set in JP1/IM - Manager.

S:

Invalidates the severe event definition setting and continues processing.

O:

To set a severe event definition in JP1/IM - Manager where a severe event definition using OR is set, use JP1/IM - View version 07-10 or later.

KAVB1576-E

The filtering process for severe event definitions has failed. (Serial number: serial-number-in-event-database, Event ID: event-ID)

An attempt to perform filtering process for severe event definitions failed because the severe event definitions could not be acquired. The event for which filtering process for severe event definitions failed is not displayed in the Severe Events page of the Event Console window even though it matches the severe event definitions.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1577-I

A status operation was performed. (user who performed the operation = JP1-user, event ID = event-ID, status before operation = status-before-operation, status after operation = status-after-operation)

The action status operation was performed.

S:

Continues processing.

KAVB1578-E

An attempt to read the status event definition file (processupdate.conf) has failed. The default value will be used. (reason = reason)

An attempt to read the status event definition file (processupdate.conf) failed. The default value Do not issue the status event (00003F11) is used to continue processing.

S:

Assumes the default value Do not issue the status event (00003F11) and continues processing.

O:

When The file does not exist. is displayed for the reason:

Use the processupdate.conf name to copy the model file (processupdate.conf.model) of the status event definition file, change definitions as necessary, and then restart JP1/IM - Manager.

If the file exists, make sure that the access permission is correctly set, and then restart JP1/IM - Manager.

When A file I/O error occurred. is displayed for the reason:

Use the data collection tool to collect data, and then contact a system administrator.

When a reason other than the above is displayed:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1579-E

There is an error in the status event definition file (processupdate.conf). The default value will be used. (line line-number = detailed-information)

Because an invalid value is set in the status event definition file (processupdate.conf), the default value Do not issue the status event (00003F11) is used to continue processing.

S:

Assumes the default value Do not issue the status event (00003F11) and continues processing.

O:

Make sure that the definition file is correctly set, and then restart JP1/IM - Manager.

KAVB1580-I

A JP1 event (event-ID) was issued.

A JP1 event was issued.

S:

Continues processing.

KAVB1581-E

Information necessary for the status event (event-ID) could not be acquired from the event DB. (reason = reason)

The status event (00003F11) could not be issued because information required for the status event could not be retrieved from the event database.

S:

Continues processing.

O:

Determine whether JP1/Base Event Service is running. If it is not running, start the service.

If JP1/Base Event Service is running, use the data collection tool to collect data, and then contact a system administrator.

KAVB1582-E

A JP1 event (event-ID) could not be issued. (reason = reason)

A JP1 event could not be issued.

S:

Stops issuing the JP1 event.

O:

Determine whether JP1/Base Event Service is running. If it is not running, start the service.

If JP1/Base Event Service is running, use the data collection tool to collect data, and then contact a system administrator.

KAVB1583-W

The filter setting (filter) from JP1/IM - View was discarded because the filter setting (filter) that uses the exclusion condition is specified in JP1/IM - Manager.

The setting from JP1/IM - View was discarded because a filter that uses the exclusion-condition is specified in JP1/IM - Manager.

S:

Invalidates the setting from JP1/IM - View and continues processing.

O:

To use a filter in JP1/IM -Manager in which the exclusion-condition is specified, use JP1/IM - View version 08-50 or later.

KAVB1584-W

The setting of the event acquisition filter from JP1/IM - View was discarded because the event acquisition filter setting that uses the common exclusion condition is specified in JP1/IM - Manager.

The setting from JP1/IM - View was discarded because a filter that uses the common exclusion-condition is specified in JP1/IM - Manager.

S:

Invalidates the setting from JP1/IM - View and continues processing.

O:

To use a filter in JP1/IM - Manager in which the common exclusion-condition is specified, use JP1/IM - View version 08-50 or later.

KAVB1585-I

Reading of the guide information file has finished. (file-name)

Number of guide information items: number-of-guide-information-items

The event guide information items for the number indicated in number-of-guide-information-items were read from the event guide information file (file-name).

S:

Continues processing.

KAVB1586-W

An error occurred while reading a guide information file. (file-name)

Line: line-number

Guide information: tag-name

Details: reason-code

There is an error in the description in the event guide information file or event guide message file.

S:

Continues processing.

O:

According to the following reason codes, correct the description error (line-number) of the file name, and then restart or reload (execute the jco_spmd_reload command) JP1/IM - Manager.

Reason code: 000

Description: Other error

Corrective action: Contact a system administrator.

Reason code: 001

Description: Unsupported syntax was found. The description up to END is ignored. The tags are output if tags other than EV_GUIDE_event-guide-number are described.

Corrective action: Correct the relevant location.

Reason code: 002

Description: Unsupported syntax was found. This line is ignored.

Corrective action: Correct the relevant location.

Reason code: 101

Description: DESC_VERSION is specified multiple times. This DESC_VERSION is ignored.

Corrective action: Specify only one DESC_VERSION.

Reason code: 201

Description: The specification of the EV_GUIDE_event-guide-number tag is invalid. The event guide number must be a number between 1 and 9999. This event guide information is ignored.

Corrective action: Change the event guide number to a number between 1 and 9999.

Reason code: 202

Description: More than one EV_GUIDE_event-guide-number tag exists. This event information is ignored.

Corrective action: Specify a unique EV_GUIDE_event-guide-number tag in the event guide information file.

Reason code: 203

Description: The number of definitions of the event guide information exceeds the maximum value.

Corrective action: Set the number of definitions to no more than the maximum value.

Reason code: 204

Description: END is not used. The subsequent event guide information is ignored.

Corrective action: Use END to close EV_GUIDE_event-guide-number.

Reason code: 205

Description: EV_GUIDE, EV_FILE is not used.

Corrective action: Use EV_GUIDE, EV_FILE to specify the event guide message.

Reason code: 301

Description: The number of definitions of EV_COMP exceeds the maximum value. This comparison condition is ignored.

Corrective action: Set the number of definitions to no more than the maximum value.

Reason code: 302

Description: The EV_COMP attribute value is invalid. The attribute-name:attribute-value format is not used.

Corrective action: Use the attribute-name:attribute-value format for the description.

Reason code: 303

Description: The EV_COMP is not specified. This event guide information is invalidated.

Corrective action: Specify EV_COMP.

Reason code: 304

Description: The regular expression of the comparison condition is invalid.

Corrective action: Correct the regular expression of the comparison condition.

Reason code: 305

Description: The attribute name does not begin with B. or E..

Corrective action: For the attribute name, specify a basic attribute of a JP1 event beginning with B. or an extended attribute of a JP1 event beginning with E..

Reason code: 401

Description: The EV_GUIDE attribute is specified multiple times. This EV_GUIDE attribute is ignored.

Corrective action: Specify only one EV_GUIDE attribute.

Reason code: 402

Description: The length of the event guide message exceeds the maximum value.

Corrective action: Reduce the length of the event guide message so that it is no more than the maximum value.

Reason code: 403

Description: Only one $ is described.

Corrective action: To specify $, describe it as \$.

Reason code: 404

Description: Only one \ is described.

Corrective action: To specify \, describe it as \\.

Reason code: 405

Description: There is an error in the specified replacement character.

Corrective action: Carefully review and correct the specified replacement character.

Reason code: 501

Description: The EV_FILE attribute is specified multiple times. This EV_FILE attribute is ignored.

Corrective action: Specify only one EV_FILE attribute.

Reason code: 502

Description: The length of the event guide message file name exceeds the maximum value. This EV_FILE attribute is ignored.

Corrective action: Reduce the length of the event guide message file name so that it is no more than the maximum value.

Reason code: 601

Description: The EV_USER attribute is specified multiple times. These EV_USER attributes are ignored.

Corrective action: Specify only one EV_USER attribute.

Reason code: 602

Description: There is an error in a JP1 user name specified for the EV_COMP attribute.

Corrective action: A JP1 user name can contain a maximum of 31 bytes. Carefully review and correct the JP1 user name.

Reason code: 603

Description: More than 100 JP1 users are specified for the EV_USER attribute. The 101st and subsequent JP1 user names are ignored.

Corrective action: Specify no more than 100 JP1 user names for the EV_USER attribute.

Reason code: 604

Description: A JP1 user name is not specified for the EV_USER attribute.

Corrective action: Specify at least one JP1 user name for the EV_USER attribute.

KAVB1587-E

An error occurred while reading a guide information file. (file-name)

Details: reason-code

An error occurred while reading an event guide information file or event message file.

S:

Stops reading file-name and continues processing.

O:

According to the following reason codes, check the storage location of file-name or the access permission, and then restart or reload (execute the jco_spmd_reload command) JP1/IM - Manager.

Reason code: 000

Description: Other error

Reason code: 001

Description: Unable to open the file.

Reason code: 002

Description: The file size is larger than the maximum value.

Corrective action: Reduce the file size so that it is no more than the maximum value.

Reason code: 003

Description: An I/O error occurred.

Reason code: 004

Description: The file version is not supported.

Corrective action: For versions 07-51 to 09-10, specify 1. For version 09-50 or later, specify 1 or 2.

KAVB1588-I

There is no matching guide information.

There was no event guide information corresponding to the event.

S:

Continues processing.

O:

To set event guide information corresponding to an event, define the event guide information in the event guide information file.

KAVB1589-E

An attempt to start the default browser has failed.

The OS's default browser could not be started.

S:

Aborts processing.

O:

Assign a Web browser to the extension (html), and then retry the operation.

KAVB1590-E

The definition file for manually registering incidents was not found. The function for manually registering incidents cannot be used.

The definition file for manually registering incidents was not found. The function for manually registering incidents cannot be used.

S:

Aborts reading of the definition file for manually registering incidents.

O:

If the definition file for manually registering incidents exists, check whether the file can be read. If the file does not exist, re-create it from the incident.conf.model file.

KAVB1591-E

An attempt to read the definition file for manually registering incidents has failed. The function for manually registering incidents cannot be used. (reason = cause)

An attempt to read the definition file for manually registering incidents has failed. The function for manually registering incidents cannot be used.

S:

Aborts reading of the definition file for manually registering incidents.

O:

Check the points listed below. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload the file.

If the message A memory shortage occurred. is displayed for cause, allocate sufficient memory.

If any other message is displayed for cause, check whether a shortage has occurred in other OS resources such as file descriptors.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB1593-W

The event acquisition filter settings cannot be removed from JP1/IM - View because an event acquisition filter that uses common exclusion conditions (extended) is set for JP1/IM - Manager.

The settings from JP1/IM - View were discarded because a filter using a common exclusion-condition group in extended mode was set in JP1/IM - Manager.

S:

Invalidates the settings from JP1/IM - View and continues processing.

O:

To set filters in JP1/IM - Manager in which a filter using a common exclusion-condition group in extended mode has been set, use JP1/IM - View version 09-50 or later.

KAVB1594-W

The event acquisition filter settings from JP1/IM - View were discarded because common exclusion conditions are set for the event acquisition filter settings from JP1/IM - View.

The event acquisition filter settings from JP1/IM - View were discarded because common exclusion-conditions were set in those filter settings.

S:

Invalidates the settings from JP1/IM - View and continues processing.

O:

To set a common exclusion-condition group, change the operation mode for the common exclusion-conditions to basic mode.

KAVB1595-W

filter setting from JP1/IM - View was discarded because filter-name setting that uses an event-source-host name is specified in JP1/IM - Manager.

The setting from JP1/IM - View was discarded because a filter using an event-source host name as a filter condition was set in JP1/IM - Manager.

S:

Invalidates the settings from JP1/IM - View and continues processing.

O:

To set filters in JP1/IM - Manager in which a filter using an event-source host name as a filter condition has been set, use JP1/IM - View version 09-50 or later.

KAVB1596-W

JP1/IM - Manager discarded settings for the filter "filter" in a version of JP1/IM - View earlier than 11-00 because a filter (filter) that uses the program-specific extended attributes is specified in JP1/IM - Manager.

JP1/IM - Manager discarded settings for a filter in a version of JP1/IM - View earlier than 11-00, because a filter that uses program-specific extended attributes is specified in JP1/IM - Manager.

S:

Disables the settings from JP1/IM - View and continues processing.

O:

To set a filter for JP1/IM - Manager that specifies a program-specific extended attribute as a condition, use version 11-00 or later of JP1/IM - View.

KAVB1597-E

The filter "filter" cannot be specified in versions of JP1/IM - View earlier than 11-00 because a filter (filter) that uses the program-specific extended attributes is specified in JP1/IM - Manager.

A filter cannot be specified in a version of JP1/IM - View earlier than 11-00, because a filter that uses program-specific extended attributes is specified in JP1/IM - Manager.

S:

Suspends processing of JP1/IM - View.

O:

To set a filter for JP1/IM - Manager that specifies a program-specific extended attribute as a condition, use version 11-00 or later of JP1/IM - View.

KAVB1598-Q

The specified attribute name "attribute-name" is set as the item name "item-name". Do you want to continue?

Check whether the program-specific extended attribute entered as the attribute name can be specified as an item name.

S:

Click the Yes button to set the specified program-specific extended attribute.

Click the No button to not set the specified program-specific extended attribute.

KAVB1601-W

The basic definition can not be extended. (file-name:line-number)

The basic definition cannot be extended in an extended attribute definition file.

S:

Invalidates the block and continues processing.

O:

Change the extension flag of the relevant block to false or change the platform name to one other than base.

KAVB1602-W

Import definition is incorrect.

Import source:file-name

Import destination:file-name

There is no import file, or a directory name is specified. Another possibility is that there is no access permission for the import file.

You cannot import the import source file.

S:

Continues processing without importing the file.

O:

Define the correct import file name or change the extension flag of blocks which will not be extended to false.

KAVB1603-W

The attribute(identifier) for the attribute name is not found.

product name : product-name

block type : block-type

block platform : platform-name

The attribute value for the attribute name is not described in the extended attribute definition file.

S:

Invalidates the record and continues processing.

O:

Define the attribute value corresponding to identifier. Also, delete the relevant record.

KAVB1604-E

The configuration file for inheriting incident information could not be found. The function for manually registering incidents cannot be used.

The configuration file for incident inheritance information was not found.

S:

Aborts reading of the configuration file for incident inheritance information.

O:

If the configuration file for incident inheritance information exists, ensure that the configuration file is allowed to be read. If the configuration file for incident inheritance information does not exist, recreate the configuration file from the incident_info.conf.model file.

KAVB1605-E

Failed to read the configuration file for inheriting incident information. The function for manually registering incidents cannot be used. (reason = cause)

The function for manually registering incidents cannot be used because the configuration file for incident inheritance information could not be read.

S:

Aborts reading of the configuration file for incident inheritance information.

O:

Check the points listed below. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload the file.

If the message An I/O error occurred. is displayed for cause, check whether a shortage has occurred in other OS resources such as file descriptors.

If the message A memory shortage occurred. is displayed for cause, allocate sufficient memory.

If any other cause is displayed or the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB1606-W

The syntax of a definition is invalid. cause (definition-file-name: line-number)

The definition is invalid.

S:

Ignores the invalid lines and continues processing.

O:

Correct the configuration file for incident inheritance information, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload the file.

KAVB1607-W

The item field ID (item-element-specification-ID) is specified more than once. (definition-file-name: line-number)

The same item element specification ID is specified more than once.

S:

Ignores the invalid lines and continues processing.

O:

Correct the configuration file for incident inheritance information, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload the file.

KAVB1608-E

The function for manually registering incidents cannot be used, because there are no valid definitions in the configuration file for inheriting incident information.

The function for manually registering incidents cannot be used because there is no valid definition in the configuration file for incident inheritance information.

S:

Disables the function for manually registering incidents.

O:

Ensure that one or more valid definitions exist in the configuration file for incident inheritance information. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload the file.

KAVB1611-W

The table version is not previously defined. processing-contents(file-name:line-number)

processing-contents is executed because the table version is not defined at the beginning of the interface definition file.

S:

Executes processing-contents and continues processing.

O:

Define the table version at the beginning of the definition file.

KAVB1612-W

The number of defined attributes exceeds the limit (maximum-number-of-attribute-name-definitions). The definition after this line will be ignored. (file-name:line-number)

Subsequent definitions are invalidated because the number of attribute definitions exceeds the maximum value in the interface definition file.

S:

Invalidates subsequent records after the maximum number is reached and continues processing.

O:

Delete extra attribute names from the relevant definition file.

KAVB1613-W

No definition for the value(identifier). (file-name)

The corresponding interface record or subkey record is not described in the interface definition file.

S:

Invalidates the record and continues processing.

O:

Describe the interface record or subkey record in the relevant definition file.

KAVB1614-W

Invalid version (version) is specified. (PRODUCT_NAME="product-name":EVENT_ID="event-ID")

The specified version value is incorrect, or the context is described in reverse in the interface definition file.

Another possibility is that a definition with the same product name, version, and event ID already exists in the same file or another file.

S:

If the version value is incorrect, continues processing using the default value. If the context is in reverse, continues processing as is. If the definition is duplicated, uses the definition that is read first based on alphabetic order.

O:

Define the correct version for the relevant definition file.

KAVB1631-E

An event color scheme file was not found. (File: file-name)

The default file does not exist, or there is no access permission.

S:

Uses the default setting of the system and continues processing. If there is no file for each JP1 user or no access permission, the system does not output the file and reads the default file.

O:

Check the presence of the file and the access permission. If there is no access permission, grant it. If there is no file, install again. If the file still does not appear after installation, use the data collection tool to collect data, and then contact a system administrator.

KAVB1632-E

An I/O error occurred during the reading of an event color scheme file. (File: file-name)

An I/O error occurred during reading of a file. Retry was executed three times; all failed.

S:

If the error occurs during reading of the file for each JP1 user, the system reads the default file. If the error occurs during reading of the default file, the system uses the default setting of the system and continues processing.

O:

Determine whether the file system is normal. If it is normal, use the data collection tool to collect data, and then contact a system administrator.

KAVB1633-E

A memory shortage occurred during the reading of an event color scheme file. (File: file-name)

A memory shortage occurred during reading of a file.

S:

Suspends file reading and continues processing using the default setting of the system.

O:

Check the memory usage of the unit where the server is operating. If memory is insufficient, allocate sufficient memory, and then log in to the system again. If memory is sufficient, use the data collection tool to collect data, and then contact a system administrator.

KAVB1634-E

A system error occurred during the reading of an event color scheme file. (File: file-name)

A system error occurred.

S:

Suspends file reading and continues processing using the default setting of the system.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1635-E

An attempt to read the system profile has failed. The default value will be used. (cause = reason)

An attempt to read the system profile failed.

S:

Suspends reading of the system profile and uses the system default setting to continue processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1636-E

An invalid value is specified for data-name in the system profile. The default value will be used. (invalid value = invalid-value,default value = default-value)

An invalid value is set for data in the system profile.

S:

Sets the default value for the invalid data and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1637-E

An I/O error occurred during reading of the system profile. A retry was performed but the file could not be read. The default values will be used. (file: file-name)

An I/O error occurred during reading of the system profile.

S:

Suspends reading of the system profile and uses the system default setting to continue processing.

O:

Determine whether the file system is abnormal. If it is normal, use the data collection tool to collect data, and then contact a system administrator.

KAVB1638-E

An attempt to read the severe-event attribute-value definition file has failed. The default settings will be used. (cause = reason)

An attempt to read the severe event attribute definition file failed.

S:

Suspends reading of the severe event attribute definition file and uses the system default setting to continue processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1639-E

A setting in the severe-event attribute-value definition file is invalid. The default settings will be used. (cause = reason)

An invalid value is set for data in the severe event attribute value definition file.

S:

Sets the default values for the invalid data and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1640-E

An I/O error occurred during reading of the severe-event attribute-value definition file. The default settings will be used. (file: file-name)

An I/O error occurred during reading of the severe event attribute value definition file.

S:

Suspends reading of the severe event attribute value definition file and uses the system default setting to continue processing.

O:

Determine whether the file system is abnormal. If it is normal, use the data collection tool to collect data, and then contact a system administrator.

KAVB1647-E

An I/O error occurred during reading of the user filter definition file. A retry was performed, but the file could not be read. Startup will use the default values.

An I/O error occurred during reading of the user filter definition file.

S:

Suspends reading of the user filter definition file and uses the system default setting to continue processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1648-E

An I/O error occurred during reading of the severe-event filter definition file. A retry was performed, but the file could not be read. Startup will use the default values.

An I/O error occurred during reading of the severe event filter definition file.

S:

Suspends reading of the severe event filter definition file and uses the system default setting to continue processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1649-E

Binding failed for at least one IP address. (IP address of successful bind = IP-address, IP address of failed bind = IP-address)

Some IP addresses could not be bound.

S:

Uses the bound socket to continue processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1650-E

An attempt to read common definition information has failed. Startup will use the default values. (key = key-name, default value = default-value)

An attempt to read common definition information failed.

S:

Suspends reading of the common definition information and uses the default value to continue processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1651-E

An invalid value is specified for key-name common definition information has failed. Startup will use the default values. (invalid data = invalid-value)

An invalid value is specified for the key name of common definition information.

S:

Suspends reading of the common definition information and uses the default value for the key name to continue processing.

O:

Reconfigure the value for the key name, and then restart JP1/IM - Manager.

KAVB1652-E

Failed to initialize the Event Console Service. The Event Console Service terminates abnormally. Details: detailed-information

An attempt to initialize Event Console Service failed.

S:

Terminates Event Console Service.

O:

Check the integrated trace log to determine if an Event Console Service error message (KAVB0001 to KAVB2000), KAVB8605-E, KAVB8606-E, or KAVB8607-E was output.

If a message is output, take the corrective action given for that message.

The settings for the communication encryption function might have changed to invalid values after JP1/Base started. Stop JP1/IM - Manager and JP1/Base, carefully review the communication encryption function settings, and then restart JP1/Base and JP1/IM - Manager.

If the problem cannot be resolved, check the following OS log items to determine whether a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1653-E

An error occurred during communication processing of the event console service. A retry was performed, but recovery was not successful. Communication processing will now be initialized.

Communication processing will be initialized again.

S:

Re-initializes communication processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1654-E

An error occurred during re-initialization of communication processing of the event console service. The error prevents re-initialization from continuing.

Event Console Service ended abnormally.

S:

Terminates Event Console Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1655-E

An error occurred during a connection request from JP1/IM-View.

An error occurred while processing a connection request from JP1/IM - View.

S:

Suspends connecting to JP1/IM - View.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB1656-I

Reloading the manager because a reload request was received.

A reload request was accepted.

S:

Starts reloading the manager.

KAVB1657-I

A request request was received.

For request selected in the window, execution was requested to the connected server.

S:

Continues processing.

KAVB1658-I

The max. number of concurrent executions which can be processed by the server was exceeded.

Wait a while, perform request again.

(max. number = maximum-number)

For request selected in the window, execution was requested to the connected server, but the request was not executed because the maximum number of simultaneous executions by the connected server was exceeded.

S:

Continues processing.

O:

Wait awhile, and then retry the operation.

KAVB1660-E

The event base service cannot be connected to.

Event information could not be acquired.

The event could not be obtained because a connection could not be established to Event Base Service.

S:

Stops acquiring the event.

O:

Execute the jco_spmd_status command to make sure that Event Base Service is running on the manager host, and then retry the operation.

KAVB1661-E

The IM Database service cannot be connected to.

Event information could not be acquired.

The event could not be acquired because a connection could not be established with the IM database service.

S:

Stops acquiring the event.

O:

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it and then retry the operation. If the IM database service is running, the integrated monitoring database might be busy due to other JP1/IM - View operations. Wait a while and then retry the operation.

KAVB1662-E

The selected event no longer exists in the Integrated Monitoring Database.

Information about the selected event could not be acquired.

Information about the selected event could not be acquired because the selected event no longer exists in the integrated monitoring database.

S:

Stops acquiring information about the event.

KAVB1663-E

The event base service cannot be connected to.

The effects of the operation operation-name could not be applied to the Integrated Monitoring Database.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because a connection could not be established to Event Base Service.

S:

Suspends processing.

O:

Execute the jco_spmd_status command to make sure that Event Base Service is running on the manager host, and then retry the operation.

KAVB1664-E

The IM Database service cannot be connected to.

The effects of the operation operation-name could not be applied to the Integrated Monitoring Database.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because a connection could not be established to the IM database service.

S:

Suspends processing.

O:

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start the service and then retry the operation. If the IM database service is running, the integrated monitoring database might be busy due to other JP1/IM - View operations. Wait a while and then retry the operation.

KAVB1665-E

The selected event no longer exists in the Integrated Monitoring Database.

An event exists for which the effects of the operation operation-name could not be applied to the Integrated Monitoring Database.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because the selected event no longer exists in the integrated monitoring database.

S:

Suspends processing.

KAVB1668-E

The selected event no longer exists in the Integrated Monitoring Database.

The effects of the operation operation-name could not be applied to the Integrated Monitoring Database.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because the selected event no longer exists in the integrated monitoring database.

S:

Suspends processing.

KAVB1669-I

The severe event definition file has been read. Next, processing will be performed using the definition read from the acquired event. (Event acquired at the end:Arrival time = arrival-time-of-the-event-acquired-at-the-end, serial number in event DB = serial-number-in-event-database-of-the-event-acquired-at-the-end)

This message is output when a severe event definition file is read.

KAVB1670-W

An attempt to perform manager host identification processing has failed.

The response status cannot be changed from the Search Event page.

The response status cannot be changed because search host and manager host identification processing failed. The response status can only be changed using the search results from the event database of the manager host that has logged in.

S:

Continues processing without changing the response status from the Event Search page.

O:

Determine whether there is a communication problem with the search host, and then retry the operation.

If the system does not recover from the error after retrying the operation, use the data collection tool to collect data, and then contact a system administrator.

KAVB1671-W

An error occurred in acquiring an event from the integrated monitoring database.

Cannot recover the error after attempting the number of retries specified in the system profile.

No more events will be displayed from now on due to this error.

An error occurred during acquisition of an event from the integrated monitoring database.

S:

Stops event search processing.

O:

Make sure that the IM database service is running. If it is not running, start the IM database service, and then retry the operation.

KAVB1672-E

Memo entries could not be set because the function that sets the memo entries is disabled.

The edited memo entries could not be applied to the integrated monitoring database because the memo entry setting function is disabled.

S:

Stops processing.

O:

Enable the memo entry setting function, and then retry the operation.

KAVB1673-E

The operation-name operation could not be performed on the integrated monitoring database because that database is currently inactive.

The operation contents of the Event Console window could not be applied to the integrated monitoring database because the integrated monitoring database is inactive.

S:

Continues processing.

O:

Activate the integrated monitoring database or log in to the system again, and then retry the operation.

KAVB1674-E

The operation-name operation could not be performed on the integrated monitoring database because an error occurred in that database.

The operation contents of the Event Console window could not be applied to the integrated monitoring database because an error occurred during operation of the integrated monitoring database.

S:

Continues processing.

O:

Make sure that the IM database service is running. If it is not running, start the service, and then retry the operation.

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact a system administrator.

KAVB1675-E

The operation-name operation could not be performed on the integrated monitoring database because the event service could not connect to that database.

The operation contents of the Event Console window could not be applied to the integrated monitoring database because a connection could not be established to Event Service.

S:

Continues processing.

O:

Make sure that Event Service is running on the manager. If it is not running, start Event Service, and then retry the operation.

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact a system administrator.

KAVB1676-E

The operation-name operation could not be performed on the integrated monitoring database because an error occurred in the event database.

The operation contents of the Event Console window could not be applied to the integrated monitoring database because an error occurred during operation of the event database.

S:

Continues processing.

O:

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact a system administrator.

KAVB1677-E

Information about the selected events could not be acquired because the integrated monitoring database is currently inactive.

Information about the selected events could not be acquired because the integrated monitoring database is inactive.

S:

Stops processing.

O:

Activate the integrated monitoring database or log in to the system again, and then retry the operation.

KAVB1678-E

Information about the selected events could not be acquired because an error occurred in the integrated monitoring database.

Information about the selected events could not be acquired because an error occurred during operation of the integrated monitoring database.

S:

Stops processing.

O:

Make sure that the IM database service is running. If it is not running, start the service, and then retry the operation.

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact a system administrator.

KAVB1680-Q

The event search will be canceled. Is this OK?

Confirms that it is OK to cancel event search.

O:

Click the Yes button to cancel event search. Click the No button to continue event search.

KAVB1681-I

The event search was canceled.

Event search cancellation processing was completed normally.

KAVB1682-E

An attempt to cancel the event search has failed.

An attempt to cancel search processing failed even though event search was canceled.

S:

Stops cancellation processing.

O:

Check the following items:

Is Event Service running on the searched host?

Has a network error occurred?

Is sufficient memory allocated?

If you are using the communication encryption function, check its settings for errors.

If there is no problem with the above items, use the data collection tool to collect data, and then contact a system administrator.

KAVB1683-W

processing is not possible during an event search.

Wait until the event search has ended.

processing cannot be performed because event search is in progress in JP1/IM - Manager.

S:

Displays the message box in the foreground.

O:

Cancel event search, or wait until event search ends.

KAVB1684-I

The event search has already ended.

Search processing had already ended even though event search was canceled.

S:

Terminates cancellation processing.

KAVB1685-W

The event acquired from the event service during the event search will be ignored because the event contains invalid information. (event database serial number = serial-number-in-event-database, reason code = reason-code)

The acquired event was ignored because invalid information was included in the event acquired from Event Service during event search.

S:

Ignores the event that contains invalid information and continues processing.

O:

Confirm the following.

When the reason code is 3:

The event arrival time is invalid. Make sure that the time is set correctly.

When the reason code is 4:

The event registered time is invalid. Use the manager to determine whether the system time is set correctly.

If the above time is correct or the cause is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAVB1686-E

A connection cannot be established with the event service specified for the search host name. (search host name = search-host-name)

Event search was impossible because a connection with the host specified for the search host name could not be established.

S:

Aborts processing.

O:

Carefully review the host specified for the search host name, and then retry the operation. If the event search is still impossible, contact a system administrator and check the business group settings.

KAVB1687-E

A business group or monitoring group cannot be specified for the name of a search host (the host to be searched for events). (search host name = search-host-name)

A business group or monitoring group cannot be specified for the search host name.

S:

Aborts processing.

O:

Carefully review the host specified for the search host name, and then retry the operation.

KAVB1688-W

The conditions for the event-source host name have been specified by [event-source host name] and [program-specific extended attributes]. Do you want to continue?

E.JP1_SOURCEHOST is specified in the conditions of a specific extended attribute. Delete E.JP1_SOURCEHOST from the conditions.

S:

Continues processing if the Yes button is clicked.

If the No button is clicked, the system cancels processing and returns to the previous window.

O:

Delete E.JP1_SOURCEHOST from the conditions of the specific extended attribute, and then retry the operation.

KAVB1689-W

The input-information have been specified by item-1 and item-2. Do you want to continue?

The input information is specified for both item 1 and item 2.

S:

Continues processing if the Yes button is clicked.

If the No button is clicked, the system cancels processing and returns to the previous window.

O:

If the message indicates that repeated event conditions have been specified by Repeated events and Extended attribute, delete JP1_IMSUPPRESS_TYPE from the conditions of the specific extended attribute, and then retry the operation.

If Conditions for suppressed event IDs have been specified by [Suppressed event ID] and [program-specific extended attributes]. is displayed, delete JP1_IMSUPPRESS_ID from the conditions of the program-specific extended attributes, and then retry the operation.

KAVB1691-W

The filter setting from JP1/IM - View was discarded because filter that use the action type are specified in JP1/IM - Manager.

The setting from JP1/IM - View was invalidated because a filter using the action type is set in JP1/IM - Manager.

S:

Invalidates the setting from JP1/IM - View and continues processing.

O:

To set a filter for which the action type is specified in JP1/IM - Manager, use JP1/IM - View version 08-00 or later.

KAVB1692-W

An operation could not be performed for an event because the user does not have the permissions necessary to perform the operation. (operation name = operation-name)

An operation for an event could not be performed.

S:

Performs operations only for the events for which the user has necessary permissions.

O:

Check whether you have the permissions necessary to perform the operation on the event.

KAVB1694-E

The user does not have the permissions necessary to perform the operation on the selected event. (operation name = operation-name)

The user does not have the permissions necessary to perform the operation on the selected event.

S:

Cancels the operation.

O:

Check whether you have the permissions necessary to perform the operation on the selected event.

KAVB1701-E

An attempt to write data to the action profile (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the action profile failed.

S:

Stops writing data to the action profile and restores the previous status of the action profile.

O:

To update the action profile, open the Conditions for Updating List of Action Results window, and then close it.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\actprofile

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\actprofile

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/actprofile

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/actprofile

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1702-E

An attempt to write data to the settings file (file-name) for consolidated display of repeated events has failed. (detailed information = detailed-information)

An attempt to write data to the settings file for consolidated display of repeated events failed.

S:

Stops writing data to the settings file for consolidated display of repeated events and restores the previous status of the settings file for consolidated display of repeated events.

O:

In the Preferences window, reconfigure consolidated display of repeated events.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\correlation

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\correlation

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/correlation

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/correlation

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1703-E

An attempt to write data to the view filter definition file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the view filter definition file failed.

S:

Stops writing data to the view filter definition file, restores the previous status of the view filter definition file, and continues processing.

O:

In the Settings for View Filter window, reconfigure the view filter.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\filter

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\filter

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/filter

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/filter

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1704-E

An attempt to write data to the event acquisition filter definition file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the event acquisition filter definition file failed.

S:

Stops writing data to the event acquisition filter definition file and restores the previous status of the event acquisition filter definition file.

Continues processing without updating the settings in the manager.

O:

In the System Environment Settings window, reconfigure the event acquisition filter.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\filter

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\filter

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/filter

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/filter

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1705-E

An attempt to write data to the event acquisition filter list file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the event acquisition filter list storage file failed.

S:

Stops writing data to the event acquisition filter list storage file and restores the previous status of the event acquisition filter list storage file.

Continues processing without updating the settings in the manager.

O:

In the System Environment Settings window, reconfigure the event acquisition filter.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\filter

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\filter

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/filter

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/filter

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1706-E

An attempt to write data to the event search filter definition file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the event search filter definition file failed.

S:

Stops writing data to the event search filter definition file, restores the previous status of the event search filter definition file, and continues processing.

O:

In the Event Search Conditions window, reconfigure the event search conditions.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\filter

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\filter

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/filter

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/filter

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1707-E

An attempt to write data to the severe event(s) filter definition file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the event acquisition filter definition file failed.

S:

Stops writing data to the severe event filter definition file and restores the previous status of the severe event filter definition file.

Continues processing without updating the settings in the manager.

O:

In the Severe Event Definitions window, reconfigure the severe event filter.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\filter

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\filter

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/filter

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/filter

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1708-E

An attempt to write data to the event receiver filter definition file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the user filter definition file failed.

S:

Stops writing data to the user filter definition file and restores the previous status of the user filter definition file.

Continues processing without updating the settings in the manager.

O:

In the Settings for Event Receiver Filter window, reconfigure the user filter.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\filter

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\filter

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/filter

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/filter

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1709-E

An attempt to write data to the event-information mapping definition file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the event information mapping definition file failed.

S:

Stops writing data to the event information mapping definition file and restores the previous status of the event information mapping definition file.

Continues processing without updating the settings in the manager.

O:

In the Event-Information Mapping Definitions window, reconfigure the event information mapping definitions.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\mapping

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\mapping

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/mapping

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/mapping

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1710-E

An attempt to write data to the system profile (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the system profile failed.

S:

Stops writing data to the system profile and restores the previous status of the system profile.

Continues processing without updating the settings in the manager.

O:

In the System Environment Settings window, reconfigure the system environment.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\profile

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\profile

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/profile

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/profile

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1711-E

An attempt to write data to the user profile (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the user profile failed.

S:

Stops writing data to the user profile and restores the previous status of the user profile.

Continues processing without updating the settings in the manager.

O:

In the Preferences window, reconfigure the user environment.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission set for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console_path\conf\console\profile

- Console_path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\console\profile

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/console/profile

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/console/profile

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB1801-E

The oldest response-waiting event was released from the hold-and-accumulate state because the maximum number of response-waiting events that can be accumulated was exceeded. (event ID = event ID, host that sent response-waiting event = host that sent response-waiting event, name of product that sent response-waiting event = name of product that sent response-waiting event, response ID = response ID, event database serial number for response-waiting event = event database serial number for response-waiting event)

The oldest response-waiting event on the manager was released from the hold-and-accumulate state because the maximum number of response-waiting events that can be accumulated was exceeded.

S:

Continues processing.

O:

For the product that issues response-waiting events, review the estimate of the number of response-waiting events that can be issued.

If the number of response-waiting events issued by the product exceeds the estimate, contact the supplier of the product.

To respond to a response-waiting event that has been released from the hold-and-accumulate state, use the Search Events page to find the target event.

A response from JP1/IM - View is not possible unless the response-waiting event exists in both the event database and the file for accumulated response-waiting events. If you want to respond to the response-waiting event for which a response from JP1/IM - View is no longer possible, take the corrective action for the product that issued the event.

KAVB1802-W

The filter setting (filter) from JP1/IM - View was discarded because the filter setting (filter) that uses the response-waiting event condition is specified in JP1/IM - Manager.

The setting from JP1/IM - View was discarded because a filter for response-waiting events was set in JP1/IM - Manager.

S:

Invalidates the setting from JP1/IM - View and continues processing.

O:

To specify the setting for JP1/IM - Manager in which a filter with response-waiting events specified is set, use JP1/IM - View version 09-00 or later.

KAVB1811-E

An attempt to open the file for accumulated response-waiting events has failed. (detailed information = detailed information)

An attempt to open the file for accumulated response-waiting events has failed.

S:

Because an attempt to open the file for accumulated response-waiting events has failed, response-waiting events are not displayed on the Response-Waiting Events page of the Event Console window.

In addition, the response-waiting events are not saved in file for accumulated response-waiting events.

O:

To check the response-waiting events that could not be displayed, specify the following search conditions in the Event Search Conditions window:

For Search host, specify the name of the connected host.

Select the target event as the response-waiting event.

For Arrived timeframe, specify the arrival time of an event that precedes or follows the JP1 event (event ID: 00003F42) on the Monitor Events page.

Also check the following items:

Is sufficient disk space allocated?

Are sufficient system physical memory and virtual memory allocated?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host: Console-path\log\response

- Logical host: shared-folder\jp1cons\log\response

In UNIX:

- Physical host: /var/opt/jp1cons/log/response

- Logical host: shared-directory/jp1cons/log/response

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1812-E

The area to be destroyed (corrupted-data-area) of the file for accumulated response-waiting events has been destroyed.

An attempt to read data has failed because the contents of the file for accumulated response-waiting events were invalid.

S:

Saves the corrupted file for accumulated response-waiting events, and then creates a new file for accumulated response-waiting events.

Note that the response-waiting events are not displayed on the Response-Waiting Events page of the Event Console window because an attempt to read the file for accumulated response-waiting events failed.

O:

To check the response-waiting events that could not be displayed, specify the following search conditions in the Event Search Conditions window:

For Search host, specify the name of the connected host.

Select the target event as the response-waiting event.

For Arrived timeframe, specify the arrival time of an event that precedes or follows the JP1 event (event ID: 00003F42) on the Monitor Events page.

Also check the following items:

Is sufficient disk space allocated?

Are sufficient system physical memory and virtual memory allocated?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host: Console-path\log\response

- Logical host: shared-folder\jp1cons\log\response

In UNIX:

- Physical host: /var/opt/jp1cons/log/response

- Logical host: shared-directory/jp1cons/log/response

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1813-E

The event data in the file for accumulated response-waiting events has been destroyed. (index ID of the event data = index ID of the event data)

An attempt to read data has failed because the contents of the file for accumulated response-waiting events were invalid.

S:

Stops reading of the corrupted response-waiting event data, and continues processing.

Note that the response-waiting events that could not be read are not displayed on the Response-Waiting Events page of the Event Console window because an attempt to read the file for accumulated response-waiting events failed.

O:

To check the response-waiting events that could not be displayed, specify the following search conditions in the Event Search Conditions window:

For Search host, specify the name of the connected host.

Select the target event as the response-waiting event.

For Arrived timeframe, specify the arrival time of an event that precedes or follows the JP1 event (event ID: 00003F42) on the Monitor Events page.

Also check the following items:

Is sufficient disk space allocated?

Are sufficient system physical memory and virtual memory allocated?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host: Console-path\log\response

- Logical host: shared-folder\jp1cons\log\response

In UNIX:

- Physical host: /var/opt/jp1cons/log/response

- Logical host: shared-directory/jp1cons/log/response

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1814-E

An attempt to read data from the file for accumulated response-waiting events has failed. (detailed information = detailed information)

An attempt to read data from the file for accumulated response-waiting events has failed.

S:

The response-waiting events are not displayed on the Response-Waiting Events page of the Event Console window because an attempt to read the file for accumulated response-waiting events has failed.

O:

To check the response-waiting events that could not be displayed, specify the following search conditions in the Event Search Conditions window:

For Search host, specify the name of the connected host.

Select the target event as the response-waiting event.

For Arrived timeframe, specify the arrival time of an event that precedes or follows the JP1 event (event ID: 00003F42) on the Monitor Events page.

Also check the following items:

Is sufficient disk space allocated?

Are sufficient system physical memory and virtual memory allocated?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host: Console-path\log\response

- Logical host: shared-folder\jp1cons\log\response

In UNIX:

- Physical host: /var/opt/jp1cons/log/response

- Logical host: shared-directory/jp1cons/log/response

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1815-E

An attempt to write data to the file for accumulated response-waiting events has failed. (detailed information = detailed information)

An attempt to write data to the file for accumulated response-waiting events has failed.

S:

The response-waiting events are not displayed on the Response-Waiting Events page of the Event Console window because an attempt to write data to the file for accumulated response-waiting events has failed.

O:

To check the response-waiting events that could not be displayed, specify the following search conditions in the Event Search Conditions window:

For Search host, specify the name of the connected host.

Select the target event as the response-waiting event.

For Arrived timeframe, specify the arrival time of an event that precedes or follows the JP1 event (event ID: 00003F42) on the Monitor Events page.

Also check the following items:

Is sufficient disk space allocated?

Are sufficient system physical memory and virtual memory allocated?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host: Console-path\log\response

- Logical host: shared-folder\jp1cons\log\response

In UNIX:

- Physical host: /var/opt/jp1cons/log/response

- Logical host: shared-directory/jp1cons/log/response

If the problem cannot be resolved, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1816-W

A response-waiting event could not be displayed.

To search for the event, specify the search conditions in the dialog box for setting the event search conditions as follows:

(1) As the host to be searched for, specify the name of the connected host.

(2) As the response-waiting event, specify the target event.

(3) As the arrival timeframe, specify the times when the events before and after this event arrived.

A response-waiting event could not be displayed on the Response-Waiting Events page because an attempt to input to or output data from the file for accumulated response-waiting events failed.

S:

Continues processing.

O:

To check the response-waiting events that could not be displayed, specify the following search conditions in the Event Search Conditions window:

For Search host, specify the name of the connected host.

Select the target event as the response-waiting event.

For Arrived timeframe, specify the arrival time of an event that precedes or follows this JP1 event.

KAVB1821-E

Memory shortage occurred.

A memory shortage occurred.

S:

Suspends processing.

O:

Check memory usage of the machine where JP1/IM - Manager is running. If memory is insufficient, restart JP1/IM - Manager. If there is no memory shortage, use the data collection tool to collect data, and then contact a system administrator.

KAVB1831-E

An attempt to establish a connection to the IM database service has failed.

An attempt to connect to the IM database service failed.

S:

Suspends processing.

O:

Use the jimdbstatus command to determine whether the IM database service is running. If it is not running, start the service.

If the IM database service is running, use the data collection tool to collect data, and then contact a system administrator.

KAVB1832-E

An error occur while attempting to register an event into the integrated monitoring database. The system will retry registering the event. (detailed information = detailed-information)

An error occurred during registration of an event in the integrated monitoring database.

S:

Retries event registration processing.

O:

Use the jimdbstatus command to determine whether the IM database service is running. If it is not running, start the service.

If the IM database service is running, determine whether a 3F54 event that notifies recovery of event registration processing was issued or a KAVB1833-I message was output in the integrated trace log.

If the system does not recover from the error, collect data, and then contact a system administrator.

KAVB1833-I

An error occur while attempting to register an event into the integrated monitoring database. However, after several retries, the event was registered into the database. The event base service is restarting event acquisition.

The system recovered from an error that occurred while registering an event in the integrated monitoring database.

S:

Resumes registering the event in the integrated monitoring database.

KAVB1834-E

A system error occur while attempting to register an event into the integrated monitoring database.

A system error occurred during registration of an event in the integrated monitoring database.

S:

Suspends processing.

O:

Collect data, and then contact a system administrator.

KAVB1841-I

The events from deletion-target-start-date-and-time to deletion-target-end-date-and-time were deleted from the integrated monitoring database.

Events from the deletion target start date to the deletion target end date were deleted from the integrated monitoring database.

KAVB1842-W

Events not output for preservation have exceeded the deletion warning level (deletion-warning-level%).

The ratio of JP1 events that have not been output and saved for preservation in the integrated monitoring database exceeded the deletion warning notification level.

KAVB1843-Q

An event condition that has not been specified in the Event Condition list has been added. Would you like to delete this condition?

Confirms that it is OK to delete unspecified event conditions from the definition because event conditions that have not been specified in the Event conditions list have been added.

O:

Click the Yes button to delete events. Click the No button to cancel deleting events.

KAVB1844-E

An abnormal the IM database termination has been detected.

Abnormal stop of the IM database service was detected.

S:

Retries connecting to the IM database service.

O:

Restart the IM database service.

KAVB1851-I

A common exclusion conditions extended definition file (file-name) was applied to JP1/IM - Manager.

The definition of the common exclusion-condition group in extended mode was applied to JP1/IM - Manager.

S:

Continues processing.

KAVB1852-W

The version information of the common exclusion conditions extended definition file is invalid. (line number = line-number)

The file version information of the common-exclusion-conditions extended definition is invalid.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1853-E

The location of the version of the common exclusion conditions extended definition file is invalid. (line number = line-number)

The file version is not specified at the beginning of the common-exclusion-conditions extended definition file.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1854-E

The condition group name is too long. (line number = line-number)

The condition group name for the common-exclusion-conditions extended definition file exceeds the maximum length.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1855-E

The condition group name does not exist. (line number = line-number)

The condition group name for the common-exclusion-conditions extended definition file is not specified.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1856-E

The condition group name is duplicated. (condition group name = condition-group-name, line number = line-number)

The condition group name for the common-exclusion-conditions extended definition file is duplicated.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1857-E

An invalid parameter is specified. (invalid parameter = parameter-name, line number = line-number)

A parameter that cannot be used is specified in the common-exclusion-conditions extended definition file, or a parameter is specified outside the definition block.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1858-E

The syntax of a common exclusion conditions extension definition is invalid. cause (condition group name = condition-group-name, line number = line-number)

There is an invalid definition in the condition block in the common-exclusion-conditions extended definition file.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

Cause 001: An event condition block is not specified.

Specify an event condition block.

Cause 002: An event condition block is specified more than once.

Delete unnecessary event condition blocks.

Cause 003: An event condition block does not end with an "end-cnd" statement.

Specify the end of the event condition block.

Cause 004: The parameter is invalid.

Review and correct the specified parameter.

Cause 006: An invalid parameter is specified.

- Review and correct the specified file version.

- Review and correct the specified parameter.

Cause 007: "end-cnd" statement is invalid.

Review and correct the end of the event condition.

Cause 100: The number of event condition exceeds the maximum number.

Delete unnecessary event conditions.

Cause 101: The event condition block is invalid.

Review and correct the specified event condition.

Cause 102: The event condition block attribute name is invalid.

Review and correct the specified attribute name of the event condition.

Cause 103: The attribute name is not specifiable.

Review and correct the specified attribute name of the event condition.

Cause 104: The comparison key word for the event conditions is invalid.

Review and correct the specified comparison keyword of the event condition.

Cause 105: The comparison key word is not specifiable.

Review and correct the specified comparison keyword of the event condition.

Cause 106: An event condition operand exceeds the maximum number.

Delete unnecessary operands.

Cause 107: An event condition operand is duplicated.

Delete duplicated operands.

Cause 108: The syntax of an event ID is invalid.

Review and correct the syntax of the event ID.

Cause 109: A regular expression is invalid.

Review and correct the specified regular expression.

Cause 110: The syntax of a severity level is invalid.

Review and correct the syntax of the severity level.

Cause 111: An operand is invalid.

Review and correct the specification of the operand.

Cause 112: The combination of comparison conditions among multiple event attributes that have the same name is invalid.

Review and correct the event condition.

Cause 113: The total number of bytes used for the event conditions in the event conditions block exceeds the limit.

Review and correct the event condition so that the total number of bytes in the event conditions in the event condition block does not exceed the maximum number of bytes.

Cause 116: The time range is invalid.

Review and correct the specified time range.

Cause 201: A character that cannot be stored successfully is included.

The definition includes a character that might cause character corruption when the definition is stored. Do not use environment-dependent characters or other characters that might cause character corruption. Note that condition-group-name is set to a hyphen (-) when this message is displayed for cause.

KAVB1859-E

The syntax of parameter-name parameter is invalid. cause (condition group name = condition-group-name, line number = line-number)

The description of the indicated parameter is invalid.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

Cause 001: A parameter has not been specified.

Specify a parameter.

Cause 002: A parameter has been specified multiple times.

Delete unnecessary parameters.

Cause 003: The common exclusion condition ID is outside the allowable range.

Review and correct the condition group ID.

Cause 004: The condition group ID is invalid.

Review and correct the condition group ID.

Cause 005: The syntax of the common exclusion condition ID is invalid.

Specify the condition group ID.

Cause 006: A condition group ID has not been specified.

Review and correct the value of the parameter.

Cause 007: The parameter value is invalid.

Specify the value of the parameter.

Cause 008: A parameter value has not been specified.

Correct the comment so that its length does not exceed the maximum number of bytes.

Cause 009: The number of bytes in the comment exceeds the limit.

Specify a comment after cmt, or delete the line containing cmt.

Cause 010: The period is outside the allowable range.

Review and correct the specification of the period.

Cause 011: The specified start or end date is invalid.

Review and correct the specified start date and end date.

Cause 012: The format of the date parameter is invalid.

Use start-date-end-date format to specify the start date and end date.

Cause 013: A start or end date has not been specified.

Specify the start date and end date.

Cause 014: The number to display for the day of the week is outside the allowable range.

Review and correct the specified day of the week.

Cause 015: The specified day of the week is invalid.

Review and correct the specified day of the week.

Cause 016: A day of the week has not been specified.

Specify the day of the week.

Cause 018: The specified start or end time is outside the allowable range.

Review and correct the specified start time and end time.

Cause 019: The specified start or end time is invalid.

Review and correct the specified start time and end time.

Cause 020: The format of the rtime parameter is invalid.

Use start-time-end-time format to specify the start time and end time.

Cause 021: A start time has not been specified.

Specify the start time.

Cause 032: The specified start or end date is not a correct date or time information.

Review and correct the specified start date and end date.

Cause 033: The specified common exclusion condition ID already exists.

Correct the condition group ID so that it does not duplicate with any other condition group ID.

KAVB1860-E

No "end-def" statement exists in a definition block. (condition group name = condition-group-name, line number = line-number)

The definition block for the common-exclusion-conditions extended definition file is not closed.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1861-E

The "end-def" statement of a definition block is invalid. (condition group name = condition-group-name, line number = line-number)

The end of the definition block in the common-exclusion-conditions extended definition file is invalid.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1862-E

The condition group name is invalid. (line number = line-number)

The definition of the condition group name is invalid.

S:

Terminates processing.

O:

Correct the error in the corresponding line in the common-exclusion-conditions extended definition file.

KAVB1863-E

Updating of a common exclusions condition extended definition failed. (cause = cause)

An attempt to update the common-exclusion-conditions extended definition failed.

S:

Terminates processing.

O:

Cause:The specified common exclusion extended definition file is invalid.

Use the jcochfilter command with the check option specified to check the common-exclusion-conditions definition file and correct the error. Then retry the operation.

Cause:A memory shortage occurred.

Allocate sufficient memory, and then retry the operation.

Cause:A file I/O error has occurred.

Check whether a shortage has occurred in other OS resources such as file descriptors.

Cause: A character that cannot be stored successfully is included.

The definition includes a character that might cause character corruption when the definition is stored. Use the jcochfilter command with the check option specified to check the common-exclusion-conditions definition file and correct the error. Then retry the operation.

If the problem cannot be resolved or if a message other than the above is displayed for cause, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1864-I

No syntax errors were found in the common exclusion conditions extended definition file (file-name).

No errors were found in the common-exclusion-conditions extended definition file.

S:

Terminates command processing.

KAVB1865-E

Only one jcochcefmode command can be executed at one time.

The jcochcefmode command is being executed.

S:

Terminates command processing.

O:

After the current jcochcefmode command processing terminates, retry the operation.

KAVB1866-E

An error occurred during reading of the common exclusion conditions extended definition file. (cause = cause)

An error occurred while reading the common-exclusion-conditions extended definition file.

S:

Terminates processing.

O:

If the message shown below is displayed for cause, the definition file might be corrupted. Stop JP1/IM - Manager, change the operation mode for the common exclusion-conditions to basic mode, and then change it back to extended mode to initialize the definition of the common exclusion-conditions (extended).

The common exclusion extended definition file is invalid.

If the following message is displayed for cause, allocate sufficient memory, and then retry the operation.

A memory shortage occurred while loading was being performed.

If the following message is displayed for cause, check whether a shortage has occurred in other OS resources such as file descriptors.

An I/O error occurred while loading was being performed.

If a message other than the above is displayed for cause or if the problem cannot be resolved, check the following OS log items.

In Windows: Windows event log

In UNIX: System log (syslog)

After checking the OS log items, check whether a shortage has occurred in other OS resources such as file descriptors. If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1867-E

The size of a common exclusion condition group (extended) filter exceeds the limit. (condition group maximum size = maximum-size)

The filter size for the common exclusion-condition group that is to be applied to JP1/IM - Manager exceeds the maximum size.

S:

Terminates command processing.

O:

Define the condition group so that the filter size does not exceed the maximum size.

KAVB1868-W

The number of common exclusion condition groups (extended) exceeds the limit. (maximum number of condition groups = maximum-number)

The number of common exclusion-condition groups defined in JP1/IM - Manager exceeds the maximum value.

S:

Continues processing with the predefined number of condition groups.

O:

Increase the maximum number of common exclusion-condition groups in extended mode or delete unnecessary condition groups.

KAVB1869-E

The common exclusion condition group could not be updated. (cause = cause)

An error occurred when an attempt to update the common-exclusion-conditions extended definition file was made.

S:

Terminates definition update processing.

O:

If one of the following messages is displayed for cause, check the operation mode for the JP1/IM - Manager common exclusion-conditions, restart JP1/IM - View, and then retry the operation.

JP1/IM - Manager is running in compatibility mode.

The common exclusion conditions is operating in a basic mode.

The common exclusion conditions is operating in a extended mode.

If one of the following messages is displayed for cause, delete unnecessary common exclusion-condition groups.

The number of common exclusion condition group (extended) definitions exceeds the limit.

The filter size of the common exclusion condition group (extended) exceeds the limit.

If the message shown below is displayed for cause, the definition file might be corrupted. Stop JP1/IM - Manager, change the operation mode for the common exclusion-conditions to basic mode, and then change it back to extended mode to initialize the definition of the common exclusion-conditions (extended).

The common exclusion extended definition file is invalid.

If the following message is displayed for cause, allocate sufficient memory, and then retry the operation.

A memory shortage occurred while loading was being performed.

If the following message is displayed for cause, check whether a shortage has occurred in other OS resources such as file descriptors.

An I/O error occurred while loading was being performed.

If the message shown below is displayed for cause, the definition includes a character that might cause character corruption when the definition is stored. Ensure that any environment-dependent character or other character that might cause character corruption is not used, and then apply the definition again.

A character that cannot be stored successfully is included.

If a message other than the above is displayed for cause or if the problem cannot be resolved, check the following OS log items.

In Windows: Windows event log

In UNIX: System log (syslog)

After checking the OS log items, check whether a shortage has occurred in other OS resources such as file descriptors. If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1870-E

The number of common exclusion condition groups (extended) exceeds the limit. (maximum number of condition groups = maximum-number)

The number of common exclusion-condition groups defined in JP1/IM - Manager exceeds the maximum value.

S:

Terminates command processing.

O:

Increase the maximum number of common exclusion-condition groups in extended mode or delete unnecessary condition groups.

KAVB1871-W

The size of a common exclusion condition group (extended) filter exceeds the limit. (condition group maximum size = maximum-size)

The filter size for the common exclusion-condition group that is to be applied to JP1/IM - Manager exceeds the maximum size.

S:

Continues processing with the predefined number of condition groups.

O:

Increase the maximum size for the common exclusion-condition group in extended mode or delete unnecessary condition groups.

KAVB1872-W

Backup of the common exclusion conditions group (extended) failed.

An attempt to back up the common exclusion-condition group in extended mode failed.

S:

Continues processing, and changes the operation mode of the common exclusion-conditions to basic mode. The common-exclusion-conditions extended definition file is output as a blank file.

O:

The system common-exclusion-conditions extended definition file (common_exclude_filter.conf) in the following directory might be in use by another application, or might not exist.

If another application is using this file, exit the application, and then back up the common exclusion-condition group manually.

In Windows:

Physical host: Console-path\conf\console\filter\

Logical host: shared-folder\JP1Cons\conf\console\filter\

In UNIX:

Physical host: /etc/opt/jp1cons/conf/console/filter/

Logical host: shared-directory/jp1cons/conf/console/filter/

KAVB1873-W

The event acquisition filter settings from JP1/IM - View were discarded, because common exclusion condition groups (which are used to suppress the execution of automatic actions for events that meet the conditions) are specified in JP1/IM - Manager.

The event acquisition filter settings from JP1/IM - View were discarded because a common exclusion-conditions group is configured in JP1/IM - Manager to exclude events from automated-action execution.

S:

Disables the settings from JP1/IM - View and continues processing.

O:

To configure an event acquisition filter in JP1/IM - Manager when a common exclusion-conditions group is configured to exclude events from automated-action execution, use version 11-50 or later of JP1/IM - View.

KAVB1874-E

The event acquisition filter settings cannot be configured from JP1/IM - Viewer 11-50 or earlier, because common exclusion condition groups (which are used to suppress the execution of automatic actions for events that meet the conditions) are specified in JP1/IM - Manager.

An event acquisition filter cannot be configured in a version of JP1/IM - View earlier than 11-50 because a common exclusion-conditions group is configured in JP1/IM - Manager to exclude events from automated-action execution.

S:

Suspends processing of JP1/IM - View.

O:

To configure an event acquisition filter in JP1/IM - Manager when a common exclusion-conditions group is configured to exclude events from automated-action execution, use version 11-50 or later of JP1/IM - View.

KAVB1880-E

The received request was aborted because it was sent from an IPv6 address. (source IP address = IPv6-address)

The request was aborted because IPv6 addresses are not supported.

S:

Terminates processing.

O:

Check the following items, and then retry the operation:

Can the host acquire IPv4 addresses?

Are any IPv6 addresses specified?

KAVB1884-W

An attempt to read the display item definition file for the repeated event condition failed. (file name = file-name)

An attempt to read the display item definition file for the repeated event condition has failed.

S:

Stops reading data and continues processing.

O:

Check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1885-W

The display item is not specified. (file = file-name)

The default value is specified because the display item is not specified in the display item definition file for the repeated event condition.

S:

Continues processing using the defalut value.

O:

Specify the display item in the display item definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1886-W

More than 256 display item have been specified. (line = line-number, file = file-name)

More than 256 display items are specified in the display item definition file for the repeated event condition.

S:

Stops reading data and continues processing, ignoring the 257th and subsequent display items.

O:

Correct the display item definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1887-W

The display item has been duplicated. (line = line-number, file = file-name)

A duplicate display item is specified in the display item definition file for the repeated event condition.

S:

Ignores the line where the duplicate item is specified, and continues processing.

O:

Correct the display item definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1888-W

An invalid display item is specified. (line = line-number, file = file-name)

An invalid display item is specified in the display item definition file for the repeated event condition.

S:

Ignores the line where the invalid item is specified and continues processing.

O:

Correct the display item definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1889-E

The display item definition file for the repeated event condition was not found.

The display item definition file for the repeated event condition was not found.

S:

Stops trying to read the display item definition file for the repeated event condition, and continues processing.

O:

Check the following items, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Check whether the display item definition file for the repeated event condition exists.

If the file does not exist, create the file.

Check whether there is read permission for the display item definition file for the repeated event condition.

If there is no read permission, set read permission for the file.

KAVB1890-E

The auto-input definition file for the repeated event condition was not found.

The auto-input definition file for the repeated event condition was not found.

S:

Stops trying to read the auto-input definition file for the repeated event condition, and continues processing.

O:

Check the following items, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Check whether the auto-input definition file for the repeated event condition exists.

If the file does not exist, create the file.

Check whether there is read permission for the auto-input definition file for the repeated event condition.

If there is no read permission, set read permission for the file.

KAVB1891-W

The auto-input definition file for the repeated event condition failed to load. (file name = file-name)

An attempt to read the auto-input definition file for the repeated event condition has failed.

S:

Stops trying to read the auto-input definition file for the repeated event condition, and continues processing.

O:

Check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1892-E

No more definitions can be added because the number of definitions in the repeated event condition has reached the maximum (maximum-number).

O:

Delete unnecessary definitions in the repeated event condition.

KAVB1893-E

No more definitions can be added because the size of the repeated event condition has reached the maximum (maximum-size).

No more definitions can be added because the repeated event condition has reached the maximum size.

O:

Delete unnecessary definitions in the repeated event condition.

KAVB1894-W

An attribute name has not been specified. (file name = file-name)

The default value is used because an attribute name is not specified in the auto-input definition file for the repeated event condition.

S:

Continues processing using the defalut value.

O:

Specify an attribute name in the auto-input definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1895-W

An invalid attribute name is specified. (line number = line-number, file name = file-name)

An invalid attribute name is specified in the auto-input definition file for the repeated event condition.

S:

Ignores the line where the invalid attribute name is specified, and continues processing.

O:

Correct the error in the auto-input definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1896-W

The attribute name is specified multiple times. (line number = line-number, file name = file-name)

A duplicate attribute name is specified in the auto-input definition file for the repeated event condition.

S:

Ignores the line where the duplicate attribute name is specified, and continues processing.

O:

Correct the error in the auto-input definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1897-W

The repeated event condition name was truncated because it exceeded maximum-length bytes.

The length of the repeated event condition name specified in the auto-input definition file for the repeated event condition exceeds the maximum length.

S:

Deletes the excess character string, and continues processing.

O:

Correct the error in the auto-input definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1898-W

The value of the parameter parameter is invalid. (line = line-number, file = file-name)

The value of the indicated parameter is invalid.

S:

Ignores the line where the invalid value is specified, and continues processing.

O:

Correct the error in the auto-input definition file for the repeated event condition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1899-E

The repeated event condition could not be set. (cause = cause)

An error occurred during setting of the repeated event condition.

S:

Terminates processing.

O:

If The repeated event monitoring suppression function is currently disabled. is displayed for cause, check and, if necessary, correct the JP1/IM - Manager settings and restart JP1/IM - View. Then retry the operation.

If The version of the currently-defined repeated event condition is incompatible with JP1/IM - View. is displayed for cause, use a version that is compatible with JP1/IM - View to establish a connection.

If the problem cannot be resolved or if a message other than the above is displayed for cause, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1917-E

The severity change definition could not be set. (cause = cause)

An error occurred while the severity change definition was being set.

S:

Terminates processing.

O:

If The definition file is invalid. is displayed for cause, check the invalid definition message output to the integrated trace log of JP1/IM - Manager, and then correct the severity change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

If The definition file could not be opened. is displayed for cause, check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager:

- Check if you have write permission for the severity change definition file. If you do not have write permission for the file, set write permission for the severity change definition file.

If The severity change function is currently disabled. is displayed for cause, check and, if necessary, correct the JP1/IM - Manager settings and restart JP1/IM - View. Then, retry the operation.

If the problem cannot be resolved, or if a message other than the above is displayed for cause, check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1918-E

No more definitions can be added because the number of severity change definition has reached the maximum (maximum-number).

No more definitions can be added because the number of severity change definitions has reached the maximum.

S:

Terminates processing.

O:

Delete unnecessary severity change definitions.

KAVB1919-E

No more definitions can be added because the size of the severity change definition has reached the maximum (maximum-size).

No more definitions can be added because the size of the event condition in the severity change definition file has reached the maximum.

S:

Terminates processing.

O:

Delete unnecessary severity change definitions.

KAVB1920-E

The severity change definition was not found.

The severity change definition is not found.

S:

Terminates processing.

O:

Check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Check whether the severity change definition file exists. If the file does not exist, create the file.

Check whether there is read permission for the severity change definition file. If there is no read permission, set read permission for the file.

KAVB1921-E

There is an error in The severity change definition.

There is an error in the severity change definition file.

S:

Terminates processing.

O:

Check the invalid definition message output to the integrated trace log of JP1/IM - Manager, and then correct the error in the corresponding line in the severity change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1922-E

The display item definition file for the severity change definition was not found.

The display item definition file for the severity change definition is not found.

S:

Stops reading the display item definition file for the severity change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, in order to continue processing, the system uses the settings that existed before the read.

O:

Check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Check whether the display item definition file for the severity change definition exists. If the file does not exist, create the file.

Check whether there is read permission for the display item definition file for the severity change definition. If there is no read permission, set read permission for the file.

KAVB1923-E

The severity change definition exceeds the maximum length (maximum-length).

No more definitions can be added because the size of the event condition in the severity change definition file has reached the maximum.

S:

Terminates processing.

O:

Delete unnecessary definitions in the severity change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1924-W

An attempt to read the display item definition file for the severity change definition failed. (file name = file-name)

An attempt to read the display item definition file for the severity change definition has failed.

S:

Stops reading the display item definition file for the severity change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, in order to continue processing, the system uses the settings that existed before the read.

O:

Check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1925-W

More than 256 display item have been specified. (line = line-number, file = file-name)

More than 256 display items are specified in the display item definition file for the severity change definition.

S:

Stops reading data and continues processing. The maximum of 256 items are used, and subsequent items are ignored.

O:

Correct the display item definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1926-W

An invalid display item is specified. (line = line-number, file = file-name)

An invalid display item is specified in the display item definition file for the severity change definition.

S:

Ignores the line where the invalid item is specified, and continues processing.

O:

Correct the display item definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1927-W

The display item has been duplicated. (line = line-number, file = file-name)

The display item specified in the display item definition file for the severity change definition is duplicated.

S:

Ignores the line where the item is duplicated, and continues processing.

O:

Correct the display item definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1928-W

The display item is not specified. (file = file-name)

The default value is specified because the display item is not specified in the display item definition file for the severity change definition.

S:

Uses the default value to continue processing.

O:

Specify the display item in the display item definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1929-E

The auto-input definition file for the severity change definition was not found.

The auto-input definition file for the severity change definition is not found.

S:

Stops reading the auto-input definition file for the severity change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, in order to continue processing, the system uses the settings that existed before the read.

O:

Check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager:

Check whether the auto-input definition file for the severity change definition exists.

If the file does not exist, create the file.

Check whether there is read permission for the auto-input definition file for the severity change definition.

If there is no read permission, set read permission for the file.

KAVB1930-W

The auto-input definition file for the severity change definition failed to load. (file name = file-name)

An attempt to read the auto-input definition file for the severity change definition has failed.

S:

Stops reading the auto-input definition file for the severity change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, in order to continue processing, the system uses the settings that existed before the read.

O:

Check the following OS log items to see if a shortage has occurred in OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1931-W

The severity change definition name was truncated because it exceeded maximum-length bytes.

The length of the severity change definition name specified in the auto-input definition file for the severity change definition exceeds the maximum length.

S:

Deletes the excess character string, and continues processing.

O:

Correct the error in the auto-input definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1932-W

The value of the parameter parameter is invalid. (line = line-number, file = file-name)

The value of the indicated parameter is invalid.

S:

Ignores the line where the invalid value is specified, and continues processing.

O:

Correct the error in the auto-input definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1933-W

An attribute name has not been specified. (file name = file-name)

The default value is used because an attribute name is not specified in the auto-input definition file for the severity change definition.

S:

Uses the default value to continue processing.

O:

Specify an an attribute name in the auto-input definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1934-W

An invalid attribute name is specified. (line number = line-number, file name = file-name)

An invalid attribute name is specified in the auto-input definition file for the severity change definition.

S:

Ignores the line where the invalid attribute name is specified, and continues processing.

O:

Correct the error in the auto-input definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1935-W

The attribute name is specified multiple times. (line number = line-number, file name = file-name)

A duplicate attribute name is specified in the auto-input definition file for the severity change definition.

S:

Ignores the line where the duplicate attribute name is specified, and continues processing.

O:

Correct the error in the auto-input definition file for the severity change definition, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1936-E

The display message change definition could not be set. (cause = cause)

An error occurred when an attempt was made to set the display message change definition.

S:

Terminates processing.

O:

If The definition file is invalid. is displayed for cause, correct the display message change definition based on the invalid message output to the integrated trace log of JP1/IM - Manager. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

If The definition file could not be opened. is displayed for cause, check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager:

• Check if you have write permission for the display message change definition file. If not, set write permission for the display message change definition file.

If The display message change function is disabled. is displayed for cause, check and, if necessary, correct the JP1/IM - Manager settings and restart JP1/IM - View. Then, retry the operation.

If the problem cannot be resolved, check the appropriate OS log listed below to determine if a shortage has occurred in an OS resource such as file descriptors.

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

In Windows: Windows event log

In UNIX: System log (syslog)

KAVB1937-E

No more definitions can be added because the number of display message change definition has reached the maximum (maximum).

No more definitions can be added, because the number of display message change definitions has reached the maximum.

S:

Terminates processing.

O:

Delete any display message change definitions that are not needed.

KAVB1938-E

No more definitions can be added because the size of the display message change definition has reached the maximum (maximum).

No more definitions can be added, because the size of the display message change definition has reached the maximum.

S:

Terminates processing.

O:

Delete any display message change definitions that are not needed.

KAVB1939-E

The display message change definition was not found.

The display message change definition file was not found.

S:

Terminates processing.

O:

Check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager:

Check whether the display message change definition file exists. If the file does not exist, create the file.

Check whether you have read permission for the display message change definition file. If not, set read permission for the file.

KAVB1940-E

There is an error in the display message change definition.

There is an error in the display message change definition file.

S:

Terminates processing.

O:

Check the invalid message output to the integrated trace log of JP1/IM - Manager and correct the error in the corresponding line in the display message change definition. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1941-E

The display item definition file for a display message change definition was not found.

The display item definition file for a display message change definition was not found.

S:

Stops reading the display item definition file for a display message change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, the system uses the settings that existed before the read to continue processing.

O:

Check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager:

Check whether the display item definition file for the display message change definition exists. If the file does not exist, create the file.

Check whether you have read permission for the display item definition file for the display message change definition. If not, set read permission for the file.

KAVB1942-E

The display message change definition exceeds the maximum length (maximum).

The display message change definition cannot be defined, because it has reached the maximum length.

S:

Terminates processing.

O:

Delete any display message change definitions in the display message change definition file that are not needed. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1943-W

An attempt to read the display item definition file for a display message change definition failed. (file name = file-name)

An attempt to read the display item definition file for a display message change definition failed.

S:

Stops reading the display item definition file for the display message change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, the system uses the settings that existed before the read in order to continue processing.

O:

Check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as file descriptors:

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1944-W

The number of specified display items in a display item definition file for a display message change definition exceeds the maximum (maximum). (line number = line-number, file = file-name)

The number of specified display items in a display item definition file for a display message change definition exceeds the maximum.

S:

Stops reading the display item definition file for the display message change definition and continues processing. The system uses up to the maximum number of display items and ignores subsequent items.

O:

Correct the display item definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1945-W

An invalid display item is specified in a display item definition file for a display message change definition. (line number = line-number, file = file-name)

A display item in a display item definition file for a display message change definition is invalid.

S:

Ignores the invalid display item and continues processing.

O:

Correct the display item definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1946-W

A display item in a display item definition file for a display message change definition is duplicated. (line number = line-number, file = file-name)

A display item in a display item definition file for a display message change definition is duplicated.

S:

Disables the duplicated line and continues processing.

O:

Correct the display item definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1947-W

No display items are specified in a display item definition file for a display message change definition. (file = file-name)

No display items are specified in a display item definition file for a display message change definition, so the default value will be used.

S:

Continues processing using the default value.

O:

Specify a display item in the display message change definition file, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1948-E

The automatic input definition file for a display message change definition was not found.

The automatic input definition file for a display message change definition was not found.

S:

Stops reading the automatic input definition file for a display message change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, the system uses the settings that existed before the read in order to continue processing.

O:

Check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager:

Check whether the automatic input definition file for the display message change definition exists. If the file does not exist, create the file.

Check whether you have read permission to the automatic input definition file for the display message change definition. If not, set read permission to the automatic input definition file for the display message change definition.

KAVB1949-W

The automatic input definition file for a display message change definition failed to load. (file name = file-name)

The automatic input definition file for a display message change definition failed to load.

S:

Stops reading the automatic input definition file for the display message change definition. If JP1/IM - Manager is running, the system uses the default value to continue processing. If the jco_spmd_reload command is being executed, the system uses the settings that existed before the read in order to continue processing.

O:

Check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as file descriptors:

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1950-W

The length of the name for a display message change definition for an automatic input definition file for a display message change definition will be truncated because it exceeds the maximum number of bytes (maximum).

The length of the name for a display message change definition for an automatic input definition file for a display message change definition exceeds the maximum number of bytes.

S:

Deletes the part of the character string that was too long, and then continues processing.

O:

Correct the automatic input definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1951-W

The value of the parameter "parameter" in an automatic input definition file for a display message change definition is invalid. (line number = line-number, file = file-name)

The value of the parameter displayed in an automatic input definition file for a display message change definition is invalid.

S:

Ignores the line where the invalid value is specified and continues processing.

O:

Correct the automatic input definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1952-W

No attribute names are specified in an automatic input definition file for a display message change definition. (file = file-name)

No attribute names are specified in an automatic input definition file for a display message change definition, so the default will be used.

S:

Uses the default value and continues processing.

O:

Specify the attribute name in the automatic input definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1953-W

An invalid attribute name is specified in an automatic input definition file for a display message change definition. (line number = line-number, file = file-name)

An invalid attribute name is specified in an automatic input definition file for a display message change definition.

S:

Ignores the invalid attribute name and continues processing.

O:

Correct the automatic input definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1954-W

An attribute name in an automatic input definition file for a display message change definition is duplicated. (line number = line-number, file = file-name)

A duplicate attribute name was specified in an automatic input definition file for a display message change definition.

S:

Disables the duplicated line and continues processing.

O:

Correct the automatic input definition file for the display message change definition, and then either restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB1955-E

An error occurred during the initialization of the communication encryption function for Event Console Service. (cause = cause)

An error occurred during the initialization of the communication encryption function for Event Console Service.

S:

Terminates Event Console Service.

O:

Check the following:

If A private key or server authentication certificate for the keystore could not be read. is displayed for cause, check the following, and then restart JP1/IM - Manager:

• Check whether the server certificate and the private key that corresponds to the server certificate are in place.

If A system error occurred. is displayed for cause, restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB1956-E

An error occurred during the initialization of the communication encryption function for the command "command-name". (cause = cause, file = file-name)

An error occurred during the initialization of the communication encryption function for the command.

S:

Does not execute the command.

O:

If The root authentication certificate was not found. was found is displayed for cause, check the following, and then re-execute the command:

Check whether the root certificate exists.

• If the root certificate exists, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• If the certificate does not exist, put a root certificate in place.

If The root authentication certificate could not be read. is displayed for cause, check the following, and then re-execute the command:

• Check for problems in the root certificate file.

• Check the appropriate OS log listed below to determine if a shortage has occurred in an OS resource such as file descriptors.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

In Windows: Windows event log

In UNIX: System log (syslog)

KAVB1957-E

Failed to encrypt communications by using the communication encryption function for the command "command-name". (host name of connection destination = connection-destination-host-name, cause = cause)

An attempt to encrypt communications to the connection destination failed.

S:

Does not execute the command.

O:

If The CN or SAN of the server authentication certificate does not match with the host name of the connection destination. is displayed for cause, verify that the CN or SAN in the server certificate of the manager host at the connection destination matches the manager host name specified by the jcochstat command with the -h option, and then re-execute the command.

If A communication error occurred. is displayed for cause, check the possible causes listed below, and then re-execute the command. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

• For the jcochstat command, check whether the root certificate that corresponds to the server certificate of the manager host specified with the -h option has been saved on the host that executed the command. If not, copy it to the host.

• For the jcochstat command, check whether the communication encryption function of the manager host specified with the -h option is enabled. If not, enable it.

• For the jcochstat command, check whether the server certificate of the manager host specified with the -h option is still valid. If it is no longer valid, update the server certificate.

• The setting of the communication encryption function might have changed since JP1/IM - Manager started up. Restart JP1/Base and JP1/IM - Manager to apply the communication encryption function settings.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB1958-E

An error occurred during the initialization of the communication encryption function for JP1/IM - View. (cause = cause, directory = directory-name)

An error occurred during the initialization of the communication encryption function for JP1/IM - View.

S:

Terminates processing.

O:

If No root authentication certificates were found. is displayed for cause, check the possible causes listed below, and then log in again.

Check whether the root certificate exists.

• If the root certificate exists, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• If there is no root certificate, put a root certificate in place.

If None of the root authentication certificates could be read. is displayed for cause, check the following, and then log in again:

• Check whether the root certificate exists. If the root certificate exists, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• Check for problems in the root certificate file.

• Check the Windows event log to determine if a shortage has occurred in an OS resource such as file descriptors.

If The placement directory for root authentication certificates could not be found. is displayed for cause, create the directory, and then place the root certificate in it.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB1959-E

Failed to encrypt communications by using the communication encryption function for JP1/IM - View. (host name of connection destination = connection-destination-host-name, cause = cause)

An attempt to encrypt communications to the connection destination failed.

S:

Terminates processing.

O:

If The CN or SAN of the server authentication certificate does not match with the host name of the connection destination. is displayed for cause, verify that the CN or SAN in the server certificate of the manager host at the connection destination matches the host name of the connection destination of the central console viewer, and then log in again.

If A communication error occurred. is displayed for cause, check the possible causes listed below, and then log in again. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

• Check whether the communication encryption function of the manager host at the connection destination is enabled. If it is, confirm that the manager host name of the connection destination is not stated in the host configuration file for non-encrypted communication.

• Check whether Failed to read some of the root authentication certificates was output to the integrated trace log. If so, take the corrective action given for that message.

• Check whether the root certificate that corresponds to the server certificate of the manager host at the connection destination has been saved in JP1/IM - View. If not, copy it there.

• Check whether the server certificate of the manager host at the connection destination is still valid. If it is no longer valid, update the server certificate.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB1960-E

A non-encryption communication host configuration file for JP1/IM - View was not found. (file = file-name)

No non-encryption communication host configuration file for JP1/IM - View was found.

S:

Terminates processing.

O:

Check the following, and then log in again:

Check whether the non-encryption communication host configuration file exists. If it does not, create the file.

Check whether you have read permission for the non-encryption communication host configuration file. If not, set read permission for the file.

KAVB1961-E

The non-encryption communication host configuration file for JP1/IM - View failed to load. (file = file-name)

An attempt to read the non-encryption communication host configuration file for JP1/IM - View failed.

S:

Terminates processing.

O:

Check the Windows event log to see if a shortage has occurred in an OS resource such as file descriptors. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB1962-E

The first line of the non-encryption communication host configuration file for JP1/IM - View is not "[NO_SSL_HOST]". (file = file-name)

[NO_SSL_HOST] is not on the first line of a non-encryption communication host configuration file for JP1/IM - View.

S:

Terminates processing.

O:

Enter [NO_SSL_HOST] on the first line of the non-encryption communication host configuration file, and then log in again.

KAVB1963-E

The number of manager host names specified in the non-encryption communication host configuration file for JP1/IM - View exceeds the maximum (maximum). (file = file-name)

Too many manager host names are specified in the non-encryption communication host configuration file for JP1/IM - View.

S:

Terminates processing.

O:

Carefully review the number of manager host names in the non-encryption communication host configuration file. Correct the problem, and then log in again.

KAVB1964-E

The length of a manager host name specified in the non-encryption communication host configuration file for JP1/IM - View exceeds the maximum (maximum). (line number = line-number, file = file-name)

A manager host name specified in the non-encryption communication host configuration file for JP1/IM - View is too long.

S:

Terminates processing.

O:

Correct the manager host name on the corresponding line of the non-encryption communication host configuration file, and then log in again.

KAVB1965-E

The syntax for asterisks (*) in the manager host name for the non-encryption communication host configuration file for JP1/IM - View is invalid. (file = file-name)

An asterisk (*) was incorrectly entered for the manager host names in the non-encryption communication host configuration file for JP1/IM - View.

S:

Terminates processing.

O:

Correct the non-encryption communication host configuration file, and then log in again.

To set an asterisk (*) for the manager host names, enter a single asterisk on the line that follows [NO_SSL_HOST].

Note that if you enter an asterisk (*), communication with all manager hosts will be in the clear (will not be encrypted).

KAVB1969-W

Failed to read some of the root authentication certificates used by the communication encryption function for JP1/IM - View. (directory = directory-name, file = file-name, file-name, ...)

An attempt to read a root certificate used by the communication encryption function for JP1/IM - View failed.

S:

Ignores the file that could not be read and continues processing.

O:

Check the possible causes listed below, and then log in again. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

Check the Windows event log to determine if a shortage has occurred in an OS resource such as file descriptors.

Check for problems in the root certificate file.

KAVB1970-E

A manager host name in the non-encryption communication host settings file is duplicated. (line number = line-number, file = file-name)

A manager host name in the non-encryption communication host configuration file is duplicated.

S:

Terminates processing.

O:

Correct the manager host name on the corresponding line of the non-encryption communication host configuration file, and then log in again.

KAVB1971-W

The root authentication certificate used by the communication encryption function for JP1/IM - View is no longer valid.(directory = directory-name, file = file-name, file-name, ...)

The root certificate used by the communication encryption function for JP1/IM - View is no longer valid.

S:

Continues processing.

O:

Check whether operating with an expired root certificate will cause a problem. If it will, update the root certificate.

KAVB1972-W

The root authentication certificate used by the communication encryption function for the command "command-name" is no longer valid. (file = file-name)

The root certificate used by the communication encryption function for the command is no longer valid.

S:

Continues processing.

O:

Check whether operating with an expired root certificate will cause a problem. If it will, update the root certificate.

KAVB1973-E

A parameter of the communication encryption function for the command "command-name" is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function for the command is invalid.

S:

Does not execute the command.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A valid value is not specified for a parameter. is displayed for cause, set a valid value for the parameter in the common definitions of JP1/Base.

If The value of a parameter is null. is displayed for cause, set a value for the parameter in the common definitions of JP1/Base.

If The value of a parameter exceeds the maximum. is displayed for cause, set a value no longer than the maximum length allowed for the parameter in the common definitions of JP1/Base.

If The value of a parameter is not a full path. is displayed for cause, set a full path as the value for the parameter in the common definitions of JP1/Base.

KAVB1974-E

Parameters for the communication encryption function for the command "command-name" could not be collected. (parameter = parameter-name, cause = cause)

Parameters for the communication encryption function for the command could not be acquired.

S:

Does not execute the command.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A parameter is not defined. is displayed for cause, set the parameter in the common definitions of JP1/Base.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB1975-E

A file or directory specified for a parameter of the communication encryption function for the command "command-name" was not found. (parameter = parameter-name, parameter value = parameter-value)

A file or directory was not found at the path specified for a parameter of the communication encryption function for the command.

S:

Does not execute the command.

O:

Save the file corresponding to the parameter at the path specified by the parameter, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB1976-E

A parameter of the communication encryption function for the Event Console Service is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function for the Event Console Service is invalid.

S:

Terminates Event Console Service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A valid value is not specified for a parameter. is displayed for cause, set a valid value for the parameter in the common definitions.

If The value of a parameter is null. is displayed for cause, set a value for the parameter in the common definitions.

If The value of a parameter exceeds the maximum. is displayed for cause, set a value no longer than the maximum length allowed for the parameter in the common definitions.

If The value of a parameter is not a full path. is displayed for cause, set a full path as the value for the parameter in the common definitions.

KAVB1977-E

Parameters for the communication encryption function for the Event Console Service could not be collected. (parameter = parameter-name, cause = cause)

Parameters for the communication encryption function for the Event Console Service could not be acquired.

S:

Terminates Event Console Service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A parameter is not defined. is displayed for cause, set the parameter in the common definitions.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB1978-E

The keystore used by the communication encryption function for the Event Console Service could not be read. (file = file-name)

The keystore used by the communication encryption function for the Event Console Service could not be read.

S:

Terminates Event Console Service.

O:

Check the possible causes listed below, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If the directory where the keystore is to be stored does not exist, create it.

If the keystore exists, check whether you have read permission for the keystore. If not, set read permission for the keystore.

If no keystore exists, check whether the message An attempt to create a keystore failed has been output to the integrated trace log. If so, take the corrective action given for that message.

KAVB1979-E

The following item was specified incorrectly: input-information

corrective-action

input-information: input-value

The specified value contains an error.

S:

Waits for re-entry of information after the message dialog box is displayed.

O:

Correct the specified value, and then retry the operation.

KAVB1981-I

The definition file for opening monitor windows was applied to JP1/IM - Manager.

The definition file for opening monitor windows was applied to JP1/IM - Manager.

S:

Continues processing.

KAVB1982-E

An attempt to read the definition file for opening monitor windows has failed. (cause = cause)

An attempt to read the definition file for opening monitor windows failed.

S:

The definition file for opening monitor windows operates based on the definition used before the jco_spmd_reload command was executed.

O:

Take the corrective action that is appropriate to the cause displayed, as described below.

If An I/O error occurred. is displayed for cause, make sure that there are sufficient OS resources such as file descriptors.

If A memory shortage occurred. is displayed for cause, allocate sufficient memory, and then retry the operation.

If the problem cannot be resolved or if a message other than the above is displayed for cause, check the following OS logs to see if a shortage has occurred in OS resources such as file descriptors:

In Windows: Windows event log

In UNIX: System log (syslog)

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1983-I

The definition file for displaying performance reports was read successfully. The function for displaying performance reports of event-source hosts can now be used. (file = file-name)

The definition file for displaying performance reports was read successfully. The function for displaying performance reports can now be used.

KAVB1984-E

An attempt to read the definition file for displaying performance reports failed. The function for displaying performance reports of event-source hosts cannot be used. (cause = cause, file = file-name)

The definition file for displaying performance reports could not be read. The function for displaying the performance reports of event-source hosts cannot be used.

S:

Aborts reading of the definition file for displaying performance reports.

O:

Investigate the following possible causes. Then, restart JP1/IM - Manager, or execute the jco_spmd_reload command to reload JP1/IM - Manager.

If the following is displayed for cause, check whether a shortage occurred with OS resources such as file descriptors: An I/O error occurred.

If the following is displayed for cause, allocate sufficient memory: A memory shortage occurred.

If the problem cannot be resolved or if neither of the preceding reasons is displayed for cause, check the OS logs listed below to determine whether a shortage occurred with an OS resource such as file descriptors. If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

In Windows: Windows event log

In UNIX: syslog

KAVB1985-E

There is an error in the definition file for displaying performance reports. The function for displaying performance reports of event-source hosts cannot be used. (cause = cause, file = file-name)

There is an error in the definition file for displaying performance reports. The function for displaying performance reports cannot be used.

S:

Aborts reading of the definition file for displaying performance reports.

O:

Investigate the following possible causes. Then, restart JP1/IM - Manager, or execute the jco_spmd_reload command to reload JP1/IM - Manager.

If the following is displayed for cause, check and, if necessary, revise the URL listed in the definition file for displaying performance reports: The URL is invalid.

If the following is displayed for cause, make sure only one URL is specified in the definition file for displaying performance reports: Multiple URLS have been specified.

KAVB1986-E

The root certificate used by the communication-encryption function of the event console service has expired. (file name: filename)

The root certificate used by the communication-encryption function of the event console service has expired.

S:

Continues processing after a warning message is displayed.

O:

Check whether operating with an expired root certificate will cause a problem. If it will, update the root certificate.

KAVB1987-E

The number of host names in the non-SSL communication host configuration file has exceeded the upper limit (maximum-number). (file name: filename)

The number of host names in the non-SSL communication host configuration file has exceeded the upper limit.

S:

Ignores the definitions exceeding the upper limit (10,000), and continues processing.

O:

Carefully review and correct the number of host names in the non-encryption communication host configuration file.

KAVB1988-W

The length of a host name in the non-SSL communication host configuration file exceeds the upper limit (upper limit). (line number: line-number, file name: filename)

The length of a host name in the non-SSL communication host configuration file exceeds the maximum length.

S:

Ignores the definitions exceeding the maximum length of the host name, and continues processing.

O:

Correct the host name in the applicable line of the non-encryption communication host configuration file.

KAVB1990-E

Failed to read the non-SSL communication host configuration file. (file name: filename)

Failed to read the non-SSL communication host configuration file.

S:

Terminates event search processing.

O:

Check if a shortage has occurred in OS resources such as file descriptors.

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB1991-E

[NO_SSL_HOST] is not specified at the beginning of the non-SSL communication host configuration file. (file name: filename)

[NO_SSL_HOST] is not found at the start of the JP1/Base non-encryption communication host configuration file.

S:

Terminates event search processing.

O:

Add [NO_SSL_HOST] to the start of the non-encryption communication host configuration file.

KAVB1993-E

An error occurred during initialization of the communication-encryption function. (cause: reason, file name: filename)

The request from the client is ignored due to a failure to initialize the communication encryption function.

S:

Terminates event search processing.

O:

If the cause is No root certificate was found, put a root certificate in place.

If the cause is The root certificate could not be read, check whether you have read permissions for the root certificate. If not, set read permissions for the root certificate.

KAVB1994-E

The SSL communication processing failed. (cause: reason, connection-destination host name: connection-destination-host-name)

The request from the client is ignored due to a failure in SSL communication processing.

S:

Terminates event search processing.

O:

If the cause is The CN or SAN of the server certificate does not match with the host name of the connection destination:

Verify that the CN or SAN in the server certificate of the host at the connection destination matches the host name specified as the destination for event search.

If the cause is SSL handshake failed:

Check the network environment.

If the manager does not use the communication encryption function, the communication encryption function on the search must be disabled. If the communication encryption function is enabled, add the manager host name in the non-SSL communication host configuration file of the search host.

If the manager uses the communication encryption function and the function is disabled on the search host, check that the search host name is registered in the non-SSL communication host configuration file of the manager. If not, register the name.

If both the manager and the search host use the communication encryption function, check that the host names of both are not registered in the non-SSL communication host configuration files of them. If the names are found, remove both the host names.

Check that a root certificate as a counterpart of the server certificate for the connected host is found in the manager. If not, put it in place.

If there is no problem with the above settings, check the following on the search host:

Check if the communication encryption function is enabled on the connected host. If it is enabled, check that the non-SSL communication host configuration file does not contain the host name of the connection destination.

If the cause is There is no common SSL version or common encryption suite:

Specify the common SSL version or common encryption suite.

If the cause is The server certificate of the connection destination has expired:

Check if the server certificate of the connected host is not expired.

If it is expired, update the server certificate.

2.3 Messages related to command execution (KAVB2001 to KAVB2999)

KAVB2002-I

Command issued to host-name host was not received within the specified time (Command : command-name).

The entered command was not accepted within the specified time.

S:

Continues executing the entered command.

However, if this message is output the first time the command is executed after the host host-name is restarted due to a physical disconnection (such as an interruption to the power supply), the system does not execute the command.

O:

This message may be output if the official name of the host that outputs this message cannot be resolved in host-name host. For the name displayed in host-name, the host name in the level that is defined in the configuration definition is displayed.

Check the hosts file of host-name host, registration of DNS, and configuration definition information.

If this message is output the first time the command is executed after the host host-name is restarted due to a physical disconnection (such as an interruption to the power supply), re-execute the command.

If this does not apply, check for problems in the communication environment or check the system log, the log of the communications equipment, or other logs.

KAVB2003-E

Cannot connect to host-name host; so, the command-name command cannot be executed.

The command cannot be executed because a connection could not be established to the host to which the command is transferred.

S:

Does not execute the command.

O:

Check the environment for one of the following possible causes:

Is the network status normal?

Does the version of the IP address (IPv4 or IPv6) match that of the command transfer-destination host?

Is JP1/Base running at the command transfer-destination host?

If the problem cannot be resolved, use the data collection tool to collect data at the local host and the command transfer-destination host, and then contact a system administrator.

For details about how to check the version of an IP address (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the JP1/Base User's Guide.

KAVB2005-E

The command-name command was rejected because it could not be relayed to the local host.

The host of JP1/IM - Manager that issued a command execution request matches the IP address of the command forwarding destination host.

S:

Does not execute the command.

O:

Check the following items:

Is there a problem resolving the IP address of the command forwarding destination host defined in the configuration definition?

Are the host name and IP address of the host that output the message set correctly?

KAVB2012-I

Received the command-name command.

The command was accepted.

S:

Continues processing.

KAVB2013-I

Terminated the command-name command. pid=process-ID terminate code=termination-code

Execution of the command indicated by command-name was completed. In Windows, the entered command is executed as cmd.exe, and in UNIX, the entered command is executed as an argument of the shell of the user that executed the command. Therefore, the displayed values are output for the process ID and termination code.

KAVB2022-E

Reception of the command was rejected because it exceeds the maximum length of 1024 bytes.

The length of the command including the argument exceeds 1,024 bytes.

S:

Does not execute the command.

O:

Carefully review the length of the command including the argument.

KAVB2023-E

Could not find the command-name command.

The corresponding command cannot be found.

S:

Does not execute the command.

O:

In Windows, determine whether cmd.exe exists, and in UNIX, determine whether the shell of the user that will execute the command exists.

KAVB2024-E

Command cannot be executed because the corresponding host(host-name) is not registered in hosts.

The address of the host indicated by host-name cannot be resolved.

S:

Does not execute the command.

O:

Take the necessary steps so that the address of host-name can be resolved.

KAVB2027-E

Cannot execute the command. Failed to simulate the user user-name environment.

The command could not be executed because user mapping failed.

S:

Does not execute the command.

O:

Check the following items:

Is the JP1 user (user-name) the same user that is defined in the user mapping definition of the command execution host?

Does the OS user defined in user mapping exist? Is that OS user confused with the domain user and local user?

Is an asterisk (*) or the manager host name set as the server host name of the JP1 user defined in user mapping (user-name)?

In Windows, is the Log on as a service or Allow log on locally permission assigned to the OS user that is defined in user mapping? #1

In Windows, has the password of the OS user defined in user mapping been changed?

If Windows and the physical and logical hosts are running simultaneously, was the jp1hosts information or the jp1hosts2 information set?#2

In UNIX, is the user ID of the OS user that is defined in user mapping valid?

If the OS user defined in user mapping is the domain user, was the domain controller not restarted?

#1: For details about configuring user permissions, see the chapter about user management setup in the JP1/Base User's Guide.

#2: For details about how to set up the JP1 hosts files, see the chapter about setting up JP1/Base for use in a cluster system in the JP1/Base User's Guide.

KAVB2029-I

Executed the command-name command. pid=process-ID

The command was executed.

KAVB2031-E

Cannot execute the command. The host (host-name) is not managed by JP1/Console.

Command execution was attempted by a host that is not a management target.

Another possibility is that the host name of the target host cannot be resolved.

S:

Does not execute the command.

O:

Use the configuration definition to define the specified host as the target host.

For the target host, specify a host at a lower level than the manager host that is logged in and defined in the system configuration definition.

Configure settings so that the host name of the target host and the host name defined in the configuration definition can be resolved.

KAVB2037-I

Terminated Command Control.

Command control was stopped.

KAVB2041-E

Could not find the Environment file (file-name).

The environment variable file specified in the Execute Command window or the action definition was not found.

O:

Make sure that the specified file is on the target host and that the path is correct.

KAVB2042-E

Jcocmd received an illegal request from process manager.

Command control received an unusable request from the process manager.

S:

Terminates the remote command.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

In UNIX, is sufficient disk space allocated under /var/opt/jp1base?

In UNIX, are permissions under /var/opt/jp1base appropriate?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2051-I

A timeout has occurred, since no reply has been obtained from the host [host-name]. Common configuration value RSPTIME_START = [internal-code]

There is no response from the host at the connection destination.

S:

Continues executing the entered command.

O:

Make sure that JP1/Base is running on the host host-name.

KAVB2052-I

Since the connection with host [host-name] was released, command response processing was interrupted.

Command response processing was suspended because connection with the host was released. This message may be output if JP1/Base on the host-name host stops during command execution, or if command execution takes a long time.

S:

Suspends command response processing because connection with the host was released. If command execution takes a long time, temporarily releases the connection but executes the command normally.

O:

If the system is not executing a command that takes a long time to be executed, determine whether JP1/Base has stopped on host-name host. If JP1/Base is running, check the network for problems.

KAVB2053-E

Socket bind error. An attempt to bind the socket on host [host-name] to the port number [port-number] and address [IP-address] has failed. [internal-message]

An attempt to bind to the output IP address failed.

S:

Unable to start using the output IP address; or does not execute the command.

O:

Determine whether the output IP address is available.

KAVB2054-E

Socket listen error. An attempt to listen to the host [host-name] has failed. [internal-message].

An attempt to perform a listen system call failed.

S:

Unable to receive communications using the output IP address of the host.

O:

Determine whether a resource shortage occurred.

KAVB2055-E

Cannot execute the command, since the host name [host-name] cannot be resolved.

The IP address of the host name cannot be resolved.

S:

Does not execute the command.

O:

Take the necessary steps so that the address can be resolved.

KAVB2056-E

The request [ID] from host [host-name] was invalid, and has been rejected.

Invalid data was received.

S:

Does not execute the command.

O:

Determine whether there is an invalid packet flow in the communication environment.

KAVB2057-E

Cannot send the execution results of the command [command-name] from the host [host-name]. [internal-message].

An attempt to send the command execution results failed.

S:

Does not send the command execution results.

O:

Determine whether a resource shortage occurred in the command execution host.

KAVB2058-E

The command request has been rejected, since the command queueing limit has been exceeded.

A command execution request exceeded the command queuing limit.

S:

Does not execute the command.

O:

Use the jcocmddef command to increase the command queuing limit.

If the same message appears after the command queuing limit is increased, perform the following:

Reduce requests for commands that require a long execution time.

Reduce the number of requested commands.

KAVB2059-E

Due to an internal error, an attempt to execute the command [command-name] has failed. [internal-message].

An attempt to execute a system call failed during command execution at the command execution host.

S:

Does not execute the command.

O:

Determine whether a resource shortage occurred at the command execution host.

KAVB2060-E

An internal error occurred while the results were being received.

An error occurred during transfer of the command execution results between internal processes in the command execution host.

S:

Does not display the command execution results.

O:

Determine whether a resource shortage occurred in the command execution host.

KAVB2061-E

Due to an internal error, the command request [command-name] has been rejected.

An error occurred during transfer of a command request between internal processes in the command execution host.

S:

Does not execute the command.

O:

Determine whether a resource shortage occurred in the command execution host.

KAVB2062-E

The command [command-name] cannot be sent from host [host-name] to host [host-name].

An error occurred while sending the command execution request.

S:

Does not execute the command.

O:

Determine whether a resource shortage occurred in the destination host.

KAVB2063-I

Failed to acquire the port number of [service-name]. The default port number is used. [internal-message].

The port number could not be acquired.

S:

Uses the default port to start.

O:

Check the port number of the jp1imcmda or jp1imcmdc service name in the services file.

KAVB2064-E

Error in writing execution results to Command execution log.

An error occurred during an attempt to write to the command execution log file.

S:

Does not save the command execution results in the command execution log file.

O:

Check the following items. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Are sufficient system resources allocated?

Is the OS operating normally?

Has a disk space shortage occurred at the command execution log file output destination?

Are permissions for the command execution log file output destination appropriate?

It is possible that the command execution log file has been corrupted. For details about how to check the command execution log file for damage and how to recover the command execution log file, see 11.5.1(9) Actions to take when a command execution log file is damaged in the manual JP1/Integrated Management 2 - Manager Administration Guide.

If the command execution log file is normal, execute the data collection tool of JP1/IM, and then contact a system administrator.

KAVB2065-W

Failed to load the Environment file (file-name).

An attempt to read the environment variable file failed.

S:

Executes the command but does not enable the environment variable file settings.

O:

Make sure that a folder name or directory name is not specified for the file name and that the access permissions are correct.

KAVB2066-I

A process under execution was deleted. command=[command-name], pid=[process-ID].

The command was deleted successfully.

KAVB2067-I

A process under queuing was deleted. command=command-name

A queued command was deleted.

KAVB2068-E

The [command-name] command could not be executed. (maintenance-information)

The command could not be executed because an error occurred.

S:

Does not execute the command.

O:

The maintenance information is in the form of termination-code:error-information. Based on this information, check the following items:

When termination-code is 10000, or termination-code is between 10011 and 10099:

Determine whether a resource shortage occurred in the command execution host.

When a signal is output for error-information:

In the command execution host, determine whether another process has issued the signal.

If the cause is other than the above or the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2069-E

command-name was rejected because forward transmission processing could not be performed. (host-name)

command-name being transmitted was rejected because commands being transmitted are accumulated in command execution control of host-name and transmitting additional commands could cause transmission processing problems.

S:

Does not execute the command.

O:

Determine whether a network problem occurred between host-name host and the execution host.

KAVB2070-W

Acquisition of the command execution results was interrupted because the specified maximum of xx lines was reached.

Acquisition of command execution results was aborted because the maximum number of lines was acquired.

S:

Executes command processing without acquiring execution results.

KAVB2071-W

In target-host-name, the number of queued commands requested from source-host-name has exceeded the threshold (xx).

In target-host-name, the number of queued automated action requests from source-host-name reached the threshold [xx entries]. It is possible that automated action from source-host-name is delayed.

S:

Continues processing.

O:

Check the following items:

Determine whether a significant number of automated actions have occurred on source-host-name. If so, consider suppressing automated actions, or increase the number of commands to be executed concurrently.

Use the jcocmdshow command to determine whether commands that have not been terminated remain on target-host-name. If so, use the jcocmddel or other similar command to terminate the commands.

KAVB2072-I

In target-host-name, the number of queued commands requested from source-host-name has become 0.

On target-host-name, the number of queued automated action requests from source-host-name is 0.

S:

Continues processing.

KAVB2100-I

[host-name:JP1-user-name] Command execution started.

Execution of the command started.

KAVB2101-I

[host-name:JP1-user-name] Command execution ended normally.

Execution of the command ended.

KAVB2102-E

[host-name:JP1-user-name] Command execution ended abnormally.

Execution of the command ended abnormally.

S:

Stops command execution.

O:

Refer to the error message displayed in the Execute Command window, and take the corrective action given for that message.

KAVB2103-E

An attempt to send a command execution operation event failed. (ret = [return-code])

An attempt to send a command execution operation event failed.

S:

Stops sending the event and continues processing.

O:

Check the following:

Is Event Service running? (Check with the jevstat command.)

Is the name of the service specified as the AP port by the ports parameter of the event server configuration file (conf) set up in the services file?

Is the address specified by the ports parameter in the event server configuration file (conf) and the addresses configured by the server and client parameters of the API configuration file able to communicate?

If operating on an IPv6 host while configured for ANY binding, is the IPv6 address of the local host assigned to jp1hosts2?

KAVB2200-E

The [option] option is invalid.

The option specified by the command line is invalid.

S:

Suspends command processing.

O:

Correct the syntax, and then re-execute the command.

KAVB2201-E

The [option] option is defined more than once.

The specified option is duplicated.

S:

Suspends command processing.

O:

Eliminate the duplication of the option, and then re-execute the command.

KAVB2202-E

The value for the [option] option is not specified.

The value is not specified for the option.

S:

Suspends command processing.

O:

Correct the syntax, and then re-execute the command.

KAVB2203-E

Specify between 1 and number-of-bytes bytes for Connected Host | Logical Host | Source Host Name.

The range of values specified by the option is invalid.

S:

Suspends command processing.

O:

Check the length of the following host names based on the information given in the message:

Connected Host: Host name specified by the -s option

Logical Host: Host name specified by the -h option

Source Host Name: Host name specified by the -ph option

KAVB2204-E

The number of arguments is invalid.

The number of arguments is too large or too small.

S:

Suspends command processing.

O:

Correct the syntax, and then re-execute the command.

KAVB2205-E

jcocmdshow was interrupted.

Command execution was interrupted.

S:

Suspends command processing.

O:

The command was interrupted by a user instruction. If necessary, re-execute the command.

KAVB2206-E

Super user privilege is required to execute the command.

The user executing the command does not have Administrator permissions.

S:

Suspends command processing.

O:

Execute the command as a user with Administrator or root permissions.

KAVB2207-E

The specified logical host [host-name] does not exist.

The logical host value is invalid.

S:

Suspends command processing.

O:

Check the logical host name specified by -h.

KAVB2208-E

The specified connected host [host-name] is unknown.

The name of the connected host does not exist.

S:

Suspends command processing.

O:

Check the name of the connected host specified by -s.

KAVB2209-E

An error occurred during retrieval of host information for the specified logical host [host-name].

The logical host name is invalid or does not exist.

S:

Suspends command processing.

O:

There is a problem in the common definition information settings of the logical host. Check the logical host settings, and, if necessary, reconfigure the logical host.

KAVB2210-E

No response has been received from the connected host [host-name].

The specified connected host did not respond.

S:

Suspends command processing.

O:

Make sure that:

JP1/Base is running on the connected host.

The specified host exists.

Network communication with the connected host is possible.

KAVB2211-I

No commands exist in the command execution control for the specified request.

The command specified in command execution control does not exist.

KAVB2212-E

Memory is insufficient at the jcocmdshow command executing host.

A memory allocation error occurred.

S:

Suspends command processing.

O:

Resolve the memory shortage, and then retry the operation.

KAVB2213-E

The maximum number of connections has been exceeded.

The number of connections exceeded the maximum number of available connections.

S:

Suspends command processing.

O:

The maximum number of available connections was exceeded at the connected host. Wait awhile, and then retry the operation.

KAVB2214-E

Processing at the connected host has been interrupted.

The adapter command on the connected host stopped due to an interruption.

S:

Suspends command processing.

O:

The command was interrupted at the connected host. Re-execute the command.

KAVB2215-E

Command execution control is not responding at the connected host.

The adapter command at the connected host did not respond.

S:

Suspends command processing.

O:

Make sure that JP1/Base is running on the connected host.

KAVB2216-E

An error during access to command execution control at the connected host.

The adapter command of the logical host is not operating normally.

S:

Suspends command processing.

O:

There is a problem with the logical host settings of the connected host. Reconfigure the logical host of the connected host.

KAVB2217-E

The connected host environment is invalid.

The adapter command on the connected host is not operating due to a lack of permission.

S:

Suspends command processing.

O:

Make sure that JP1/Base is running on the connected host in the administrator role.

KAVB2218-E

Invalid protocol data was received from command execution control.

The adapter command on the connected host received invalid data.

S:

Suspends command processing.

O:

Invalid data was included during communication. Retry the operation.

KAVB2221-E

The contents of the configuration definition are corrupted. "[key]\\JP1BASE" key does not exist.

The common definition key JP1BASE does not exist.

S:

Suspends command processing.

O:

The environment is invalid. Re-install JP1/Base.

KAVB2222-W

Log directory information from the configuration definition under logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire the log directory from the common definition information failed.

S:

Continues command processing without outputting the log.

KAVB2223-W

Log settings information from the configuration definition under logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire log output settings from the common definition information failed.

S:

Continues command processing without outputting the log.

KAVB2224-W

An attempt to initialize the HNTR library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 failed.

S:

Continues command processing without outputting the log.

KAVB2225-E

Invalid protocol data was received from command execution control.

Invalid data was received from command execution control.

S:

Suspends command processing.

O:

Invalid data was included during communication. Retry the operation.

KAVB2227-I

jcocmdshow started.

The jcocmdshow command started.

KAVB2228-I

jcocmdshow terminated. return code: [return-code].

The jcocmdshow command stopped.

KAVB2229-E

Invalid source host name

An invalid character is contained in the argument specified by the -ph option.

S:

Suspends command processing.

O:

Check the argument specified using the -ph option.

KAVB2230-E

The value for the -state option [argument] is invalid.

Characters other than r or q are used in the -state option.

S:

Suspends command processing.

O:

Check the argument specified using the -state option.

KAVB2231-E

The maximum number of connections at the connected host has been exceeded. Wait a while, and then retry.

The maximum number of allowable concurrent connections was exceeded.

O:

The maximum number of connections has been reached. Wait awhile, and then retry the operation.

KAVB2232-E

An error occurred during initialization of communication with the plug-in service at the jcocmdshow command executing host.

An attempt to initialize the plug-in service API failed.

S:

Suspends command processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

Is there a problem in the network with the host specified by the -s option?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2233-E

An error occurred in the plug-in service on the jcocmdshow command executing host.

An invalid parameter was passed to the plug-in API, or an unexpected error occurred.

S:

Suspends command processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

Is there a problem in the network with the host specified by the -s option?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2234-E

An error occurred while a request was being processed on the connected host.

The environment of the connected host is invalid.

S:

Suspends command processing.

O:

Reconfigure JP1/Base on the connected host.

KAVB2235-E

An error occurred while data was being received from command execution control.

The following error occurred in the plug-in API:

Data reception error

S:

Suspends command processing.

O:

Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2236-E

An error occurred during data transmission to command execution control.

The following error occurred in the plug-in API:

Data transmission error

S:

Suspends command processing.

O:

Make sure that:

JP1/Base is running on the connected host.

The status of the network with the connected host and the network settings allow normal operation.

KAVB2237-E

The connected host version does not support this command.

The following error(s) occurred in the plug-in API:

Invalid version

Lack of required components

S:

Suspends command processing.

O:

Make sure that the version of JP1/Base on the connected host is 07-10 or later.

KAVB2238-E

The connection with the connected host terminated. Try again.

The following error occurred in the plug-in API:

Connection was ended.

S:

Suspends command processing.

O:

Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2239-E

A network connection with the connected host could not be established.

The following error(s) occurred in the plug-in API:

Connection error

The plug-in service is busy.

S:

Suspends command processing.

O:

Check the environment for one of the following possible causes:

Is the network status normal?

Does the version of the IP address (IPv4 or IPv6) match that of the connection-destination host?

Is JP1/Base running at the connection-destination host?

If the problem cannot be resolved, use the data collection tool to collect data at the local host and the connection-destination host, and then contact a system administrator.

For details about how to check the version of an IP address (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the JP1/Base User's Guide.

KAVB2240-E

The environment is invalid on the jcocmdshow command executing host.

The following error(s) occurred in the plug-in API:

Syntax error in settings file

Unable to find settings file

Unable to find command definition information of logical host

S:

Suspends command processing.

O:

The common definition information of the host that executed the jcocmdshow command or the settings in the plug-in service settings file were invalid. Re-install JP1/Base.

KAVB2241-E

Invalid protocol data was transmitted through the plug-in service.

The following error occurred in the plug-in API:

Invalid data was received.

S:

Suspends command processing.

O:

Invalid data was included during communication. Retry the operation.

KAVB2242-E

JP1/Base does not support this command.

The following error occurred in the plug-in API:

Unable to find the plug-in

S:

Suspends command processing.

O:

Make sure that the version of JP1/Base on the connected host is 07-10 or later. If the version is not the problem, it is possible that the environment is invalid. Re-install JP1/Base to recover from the error.

KAVB2243-E

A timeout occurred during communication with the plug-in service. Try after a while.

The following error(s) occurred in the plug-in API:

A time-out request occurred.

The plug-in service is busy.

Connection to the plug-in service failed.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB2244-E

The connection with connected host terminated.

The following error occurred in the plug-in API:

Connection with the plug-in service was ended.

S:

Suspends command processing.

O:

Make sure that JP1/Base is running on the connected host.

KAVB2245-E

A timeout occurred during communication with the plug-in service.

The following error occurred in the plug-in API:

A time-out request occurred.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB2246-E

Failed to open catalog file /opt/jp1base/lib/nls/C/jp1BsCmdShow.cat

An attempt to open the catalog file failed.

S:

Does not execute the jcocmdshow command.

O:

In UNIX, check the items below. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Does the catalog file exist under the /opt/jp1base/lib/nls directory?

Is there read permission for the catalog and path to /opt/jp1base/lib/nls?

KAVB2247-W

Unable to get message from the catalog file

The message could not be acquired from the catalog file. It is possible that the catalog file is corrupted.

S:

Does not output the message.

O:

Change the LANG environment variable, and then re-execute the command. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2248-E

Memory allocation failed due to insufficient memory.

An attempt to allocate an area of memory failed due to a memory shortage.

S:

Suspends command processing.

O:

Resolve the memory shortage, and then retry the operation.

KAVB2249-E

catopen() API failed. Error number: error-code

An attempt to open the catalog file failed.

S:

Does not execute the jcocmdshow command.

O:

In UNIX, check the items below. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Does the catalog file exist under the /opt/jp1base/lib/nls directory?

Is there read permission for the catalog and path to /opt/jp1base/lib/nls?

KAVB2250-W

An attempt to initialize an individual trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:

Continues processing without outputting the log.

KAVB2251-W

An attempt to initialize an integrated trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:

Continues processing without outputting the log.

KAVB2252-E

The specified host to be connected is not subject to configuration management.

A connection could not be established to the host because the host is not being managed.

S:

Suspends command processing.

O:

Check the name of the connected host specified by the -s option.

KAVB2253-E

A reply was not returned during communication processing at the host where the jcocmdshow command was executed.

An attempt to communicate with the connected host failed during communication processing.

S:

Suspends command processing.

O:

At the host where the command was executed, execute the jbs_spmd_status command to determine whether all services are running, and then retry the operation.

KAVB2276-E

The [option] option is invalid.

The option specified by the command line is invalid.

S:

Suspends command processing.

O:

Correct the syntax, and then re-execute the command.

KAVB2277-E

The [option] option is defined more than once.

The specified option is duplicated.

S:

Suspends command processing.

O:

Eliminate the duplication of the option, and then re-execute the command.

KAVB2278-E

The value for the [option] option is not specified.

A value is not specified for the option.

S:

Suspends command processing.

O:

Correct the syntax, and then re-execute the command.

KAVB2279-E

Specify between 1 and [number-of-bytes] bytes for Connected Host.

The value specified for the option is outside the valid range.

S:

Suspends command processing.

O:

Execute the command using a correct value.

KAVB2280-E

The number of arguments is invalid.

The number of arguments is too large or too small.

S:

Suspends command processing.

O:

Correct the syntax, and the re-execute the command.

KAVB2281-E

jcocmddel was interrupted.

An interruption occurred during command execution.

S:

Suspends command processing.

O:

The command was interrupted by a user instruction. If necessary, re-execute the command.

KAVB2282-E

Superuser privilege is required to execute the command.

The user executing the command does not have Administrator permissions.

S:

Suspends command processing.

O:

Execute the command as a user with Administrator or root permissions.

KAVB2283-E

The specified logical host host-name does not exist.

The logical host value is invalid.

S:

Suspends command processing.

O:

Check the logical host name specified by -h.

KAVB2284-E

The specified connected host [host-name] is unknown.

The name of the connected host does not exist.

S:

Suspends command processing.

O:

Check the name of the connected host specified by -s.

KAVB2285-E

The specified logical host [host-name] does not exist.

The logical host name is invalid or does not exist.

S:

Suspends command processing.

O:

There is an error in the common definition information settings of the logical host. Check the logical host settings, and, if necessary, reconfigure the logical host.

KAVB2286-E

No response has been received from the connected host [host-name].

The specified connected host did not respond.

S:

Suspends command processing.

O:

Make sure that:

JP1/Base is running on the connected host.

The specified host exists.

Network communication with the connected host is possible.

KAVB2287-I

No command exists in command execution control.

The command specified in command execution control does not exist.

KAVB2288-E

Memory is insufficient on the jcomddel command executing host.

A memory allocation error occurred.

S:

Suspends command processing.

O:

Resolve the memory shortage, and then retry the operation.

KAVB2289-E

<CommandID(S)>/ALL option is required.

The command ID or ALL option is not specified.

S:

Suspends command processing.

O:

Specify either the command ID or ALL option (if you wish to delete all).

KAVB2290-E

Command ID(S) cannot be specified with the ALL option.

Both the command ID and ALL option are specified at the same time.

S:

Suspends command processing.

O:

Specify either the command ID or ALL option (if you wish to delete all) but not both.

KAVB2291-Q

Do you want to delete the specified command ID(S) [Y/y or N/n] ->

Confirms that it is OK to delete the command.

S:

Stops command processing and waits for a response.

O:

Enter Y or y to continue processing. Enter N or n to suspend processing.

KAVB2292-I

The user cancelled the deletion of command(S).

The jcocmddel command was suspended.

KAVB2293-I

The command(S) were deleted successfully from command execution control.

The specified command ID was deleted successfully.

KAVB2294-W

The command ID(S) [command-ID] do not exist in command execution control.

The specified command does not exist.

S:

Cannot find the specified command ID.

KAVB2295-E

Invalid command ID. Specify a command ID between 0 and 4294967295.

An invalid command ID is specified.

S:

Suspends command processing.

O:

Specify a command ID that is within the allowed range.

KAVB2296-E

The maximum number of connections on the connected host has been exceeded.

The number of connections exceeded the maximum number of connections available on the connected host.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB2297-E

Processing on the connected host was interrupted.

The adapter command stopped due to an interruption at the connected host.

S:

Suspends command processing.

O:

The command was interrupted at the connected host. Re-execute the command.

KAVB2298-E

Command execution control is not responding on the connected host.

The adapter command is not responding on the connected host.

S:

Suspends command processing.

O:

Make sure that JP1/Base is running on the connected host.

KAVB2299-E

An error occurred during access to command execution control on the connected host.

The adapter command on the logical host is not operating normally.

S:

Suspends command processing.

O:

There is an error in the logical host settings of the connected host. Reconfigure the logical host of the connected host.

KAVB2300-E

The connected host environment is invalid.

The adapter command on the connected host is not operating due to a lack of permission.

S:

Suspends command processing.

O:

Make sure that JP1/Base is running in the administrator role on the connected host.

KAVB2301-E

Invalid protocol data was received in command execution control.

The adapter command on the connected host received invalid data.

S:

Suspends command processing.

O:

Invalid data was included during communication. Retry the operation.

KAVB2304-E

The contents of the configuration definition are corrupted. The "[key]\\JP1BASE" key does not exist.

The common definition key JP1BASE does not exist.

S:

Suspends command processing.

O:

The environment is invalid. Re-install JP1/Base.

KAVB2305-W

Log directory information from the configuration definition under the logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire the log directory from the common definition information failed.

S:

Continues command processing without outputting the log.

KAVB2306-W

Log settings information from configuration definition under logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire the log output settings from the common definition information failed.

S:

Continues command processing without outputting the log.

KAVB2307-W

An attempt to initialize the hntr library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 failed.

S:

Continues command processing without outputting the log.

KAVB2308-E

Invalid protocol data was received from command execution control.

Invalid data was received from command execution control.

S:

Suspends command processing.

O:

Invalid data was included during communication. Retry the operation.

KAVB2310-I

jcocmddel started.

The jcocmddel command started.

KAVB2311-I

jcocmddel terminated. return code: [return-code].

The jcocmddel command stopped.

KAVB2312-W

ID(S) [command-ID] is (are) specified more than once. Processing will continue with unique ID(S).

The command ID is specified more than once.

KAVB2313-E

The maximum number of connections at the connected host has been exceeded. Try after a while.

The maximum number of connections allowed at one time was exceeded.

S:

Ends the connection and suspends processing.

O:

The maximum number of connections was reached. Wait awhile, and then retry the operation.

KAVB2314-E

An invalid command ID was specified.

An invalid command ID was specified.

S:

Suspends command processing.

O:

Specify a command ID value between 0 and 4,294,967,295.

KAVB2316-E

An error occurred during initialization of communication with the plug-in service on the jcocmddel command executing host.

An attempt to initialize the plug-in service API failed.

S:

Suspends command processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

Is there a problem in the network with the host specified by the -s option?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2317-E

An error occurred in the plug-in service on the jcocmddel command executing host.

An invalid parameter was passed to the plug-in API, or an unexpected error occurred.

S:

Suspends command processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

Is there a problem in the network with the host specified by the -s option?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2318-E

An error occurred during request processing on the connected host.

The environment of the connected host is invalid.

S:

Suspends command processing.

O:

Reconfigure JP1/Base on the connected host.

KAVB2319-E

An error occurred during data reception from command execution control.

The following error occurred in the plug-in API:

Data reception error

S:

Suspends command processing.

O:

Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2320-E

An error occurred during data transmission to command execution control.

The following error occurred in the plug-in API:

Data transmission error

S:

Suspends command processing.

O:

Make sure that:

JP1/Base is running on the connected host.

The status of the network with the connected host and the network settings allow normal operation.

KAVB2321-E

The connected host version does not support this command.

The following error(s) occurred in the plug-in API:

Invalid version

Lack of required components

S:

Suspends command processing.

O:

Make sure that the version of JP1/Base on the connected host is 07-10 or later.

KAVB2322-E

Connection with the connected host terminated. Try again.

The following error occurred in the plug-in API:

Connection was ended.

S:

Suspends command processing.

O:

Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2323-E

A network connection with the connected host could not be established.

The following error(s) occurred in the plug-in API:

Connection error

The plug-in service is busy.

S:

Suspends command processing.

O:

Check the environment for one of the following possible causes:

Is the network status normal?

Does the version of the IP address (IPv4 or IPv6) match that of the connection-destination host?

Is JP1/Base running at the connection-destination host?

If the problem cannot be resolved, use the data collection tool to collect data at the local host and the connection-destination host, and then contact a system administrator.

For details about how to check the version of an IP address (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the JP1/Base User's Guide.

KAVB2324-E

The environment is invalid on the jcocmddel command executing host.

The following error(s) occurred in the plug-in API:

Syntax error in settings file

Unable to find settings file

Unable to find common definition information of logical host

S:

Suspends command processing.

O:

The common definition information of the host that executed the jcocmdshow command or the contents of the plug-in service settings file are invalid. Re-install JP1/Base.

KAVB2325-E

Invalid protocol data was transmitted through the plug-in service.

The following error occurred in the plug-in API:

Reception of invalid data

S:

Suspends command processing.

O:

Invalid data was included during communication. Retry the operation.

KAVB2326-E

JP1/Base does not support this command.

The following error occurred in the plug-in API:

Unable to find the plug-in

S:

Suspends command processing.

O:

Make sure that the version of JP1/Base on the connected host is 07-10 or later. If the version is not the problem, it is possible that the environment is invalid. Re-install JP1/Base to recover from the error.

KAVB2327-E

A timeout occurred during communication with the plug-in service. Try after a while.

The following error(s) occurred in the plug-in API:

Request time-out occurred.

Plug-in service is busy.

Connection to plug-in service failed.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB2328-E

The connection with the connected host terminated.

The following error occurred in the plug-in API:

Connection with plug-in service was ended.

S:

Suspends command processing.

O:

Make sure that JP1/Base is running on the connected host.

KAVB2329-E

A timeout occurred during communication with the plug-in service.

The following error occurred in the plug-in API:

Request time-out occurred.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB2330-E

Failed to open catalog file /opt/jp1base/lib/nls/C/jp1BsCmdDel.cat

An attempt to open the catalog file failed.

S:

Does not execute the jcocmddel command.

O:

In UNIX, determine whether the catalog file exists in the /opt/jp1base/lib/nls directory.

KAVB2331-W

A message could not be acquired from the catalog file.

The message could not be acquired from the catalog file. It is possible that the catalog file is corrupted.

S:

Does not output the message.

O:

Change the LANG environment variable, and then re-execute the command. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2332-E

Memory allocation failed due to insufficient memory.

An attempt to allocate an area of memory failed due to a memory shortage.

S:

Suspends command processing.

O:

Resolve the memory shortage, and then retry the operation.

KAVB2333-E

catopen() API failed. Error number: error-code

An attempt to open the catalog file failed.

S:

Does not execute the jcocmddel command.

O:

In UNIX, determine whether the catalog file exists in the /opt/jp1base/lib/nls directory.

KAVB2334-W

An attempt to initialize an individual trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:

Continues processing without outputting the log.

KAVB2335-W

An attempt to initialize an integrated trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:

Continues processing without outputting the log.

KAVB2336-E

The specified host to be connected is not subject to configuration management.

The host could not be connected because the host to be connected is not subject to configuration management.

S:

Suspends command processing.

O:

Check the name of the connected host specified by the -s option.

KAVB2337-E

A reply was not returned during communication processing at the host where the jcocmddel command was executed.

An attempt to communicate with the connected host failed during communication processing.

S:

Suspends command processing.

O:

On the host where the command was executed, execute the jbs_spmd_status command to determine whether all services are running, and then retry the operation.

KAVB2339-E

An attempt to delete the commands has failed. Try again.

An error occurred during command deletion processing.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB2356-E

The value for the logical logical-host-name is invalid.

The logical host value is invalid.

S:

Suspends command processing.

O:

Check the logical host name specified by the -h option.

KAVB2401-I

The logs of commands executed are not displayed for a setup which do not save them.

The command execution log is not saved because it is set up not to be saved.

S:

Continues command processing.

O:

To save the command execution log, execute the following command on the host where JP1/IM - Manager is running:

jcocmddef -actresult ON

KAVB2402-W

[host-name]The execution time of command execution exceeded the regulation value (numeric-value sec)

The execution time of the command being executed exceeds the regulation value.

S:

Continues command execution.

O:

Processing of command execution is taking a long time. Execute the jcocmdshow command to check the details of the command, and execute the jcocmddel command to delete the command being executed.

KAVB2500-E

An attempt to open a catalog file has failed. A default message is used.

An attempt to read the message resource failed.

S:

Suspends processing.

O:

Re-install JP1/Base.

KAVB2501-E

A value is invalid. (option = option-name value)

The displayed option and value are invalid.

S:

Suspends processing.

O:

Specify the correct option and value.

KAVB2502-E

A value is invalid. The option [-host: logical host name (host-name)] is too long.

The logical host name is too long.

S:

Suspends processing.

O:

Specify a logical host name using no more than 255 characters.

KAVB2503-E

The logical host host-name does not exist on this host.

The specified logical host does not exist.

S:

Suspends processing.

O:

Specify an existing logical host name.

KAVB2504-E

The host group file file-name cannot be opened.

The specified host group file cannot be found.

S:

Suspends processing.

O:

Make sure that the host group file exists.

KAVB2505-E

The host group name is not defined.

The host group name is not defined in the host group file.

S:

Suspends processing.

O:

Make sure that the host group name is specified correctly in the host group file.

KAVB2506-E

The format is invalid. (line: line-number)

The format of the host group file is invalid.

S:

Suspends processing.

O:

There is a syntax error in the host group file. Check the following items:

Are the characters { and } used correctly in the host group definition?

Is more than one host group name specified before the character { in the host group definition?

Correct the syntax error in the host group file, and then retry the operation.

KAVB2507-E

The group name group-name is too long.

The group name specified in the host group file is too long.

S:

Suspends processing.

O:

Specify a group name using no more than 32 characters.

KAVB2508-E

Access permission is lacking.

An access permission error occurred while accessing the common definition.

S:

Suspends processing.

O:

The environment is invalid. Re-install JP1/Base.

KAVB2509-E

The host name host-name is too long.

The host name is too long.

S:

Suspends processing.

O:

Specify a host name using no more than 255 characters.

KAVB2510-E

The value is invalid. The option [-group: group file name (file-name)] is too long.

The host group file name is too long.

S:

Suspends processing.

O:

The group file name can contain a maximum of 1,023 characters. Modify the file name, and then retry the operation.

KAVB2511-E

An error occurred at the API of the common definition. (Access permission was lacking.)

An error occurred while accessing the common definitions.

S:

Suspends processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2512-E

An error occurred at the API of the common definitions. (No entry was found.)

An error occurred while accessing the common definitions.

S:

Suspends processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB2513-E

An error occurred at the API of the common definitions. (An invalid parameter was used.)

An error occurred while accessing the common definitions.

S:

Suspends processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2514-E

An error occurred at the API of the common definitions. (An internal error occurred.)

An error occurred while accessing the common definitions.

S:

Suspends processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2515-E

An error occurred at the API of the common definitions. (An initialization error occurred.)

An error occurred while accessing the common definitions.

S:

Suspends processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2516-E

An error occurred at the API of the common definitions. (A logic conflict occurred.)

An error occurred while accessing the common definitions.

S:

Suspends processing.

O:

Check the following items:

Are sufficient system resources and memory allocated?

Is the OS operating normally?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2517-E

Super user privilege is required to execute the command.

The user executing the command does not have sufficient permission.

S:

Suspends processing.

O:

Execute the command as a user with Administrator or root permissions.

KAVB2518-E

The specified directory path (directory-name) is too long.

The specified directory path is too long.

S:

Does not execute the command.

O:

Shorten the length of the path to the directory where the command execution log file is stored.

KAVB2519-E

The specified host name (host-name) is too long.

The specified host name is too long.

S:

Does not execute the command.

O:

Make sure that the specified logical host name is correct.

KAVB2520-E

The specified logical host (host-name) does not exist.

The specified logical host has not been set up.

S:

Does not execute the command.

O:

Make sure that the specified logical host name is correct.

KAVB2521-E

The specified directory (directory-name) does not exist.

The specified directory could not be found.

S:

Does not execute the command.

O:

Check the name of the directory where the command execution log file is stored.

KAVB2522-W

The command-execution log file for the executed command does not exist.

The log file of a command executed in the Execute Command window does not exist.

S:

Does not output the log of the command that was executed in the Execute Command window.

O:

Execute the command in the Execute Command window, and then retry the operation.

KAVB2523-E

The command-execution log file for the executed command cannot be opened.

The log file of a command executed in the Execute Command window could not be opened.

S:

Does not output the log of the command executed in the Execute Command window.

O:

Check the following items. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Make sure that the permission for the storage destination of the command execution log file is appropriate.

It is possible that the command execution log file is corrupted. For details about how to check the log file for damage and how to recover the command execution log file, see 11.5.1(9) Actions to take when a command execution log file is damaged in the manual JP1/Integrated Management 2 - Manager Administration Guide.

If the command execution log file is normal, execute the JP1/IM data collection tool, and then contact a system administrator.

KAVB2524-W

The command-execution log file for the automatic action does not exist.

There is no log file of a command executed by automated action.

S:

Does not output the log of the command executed by automated action.

O:

Execute the automated action, and then retry the operation.

KAVB2525-E

The command-execution log file for the automatic action cannot be opened.

The log file of a command executed by automated action could not be opened.

S:

Does not output the log of the command executed by automated action.

O:

Check the following items. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Make sure that the permission for the storage destination of the command execution log file is appropriate.

It is possible that the command execution log file is corrupted. For details about how to check the log file for damage and how to recover the command execution log file, see 11.5.1(9) Actions to take when a command execution log file is damaged in the manual JP1/Integrated Management 2 - Manager Administration Guide.

If the command execution log file is normal, execute the JP1/IM data collection tool, and then contact a system administrator.

KAVB2526-W

Reading of the command-execution log file was interrupted.

Read processing was suspended because an exclusive operation was performed on the command execution log file by another process.

S:

Suspends output of the command execution log.

O:

Determine whether the following processing was executed, and then re-execute the jcocmdlog command.

Execution of automated action

Execution of a command in the Execute Command window

Execution of another jcocmdlog command

KAVB2527-E

An attempt to read the command-execution log file has failed.

Processing stopped because an error occurred during reading of the command execution log file.

S:

Stops outputting the command execution log.

O:

It is possible that the command execution log file is corrupted. For details about how to check the log file for damage and how to recover the command execution log file, see 11.5.1(9) Actions to take when a command execution log file is damaged in the manual JP1/Integrated Management 2 - Manager Administration Guide.

If the command execution log file is normal, execute the JP1/IM data collection tool, and then contact a system administrator.

KAVB2528-E

The date is invalid.(date)

There is an error in the specified date/time. Check the following items:

Date error: The specified date is not in the calendar.

Time error: The specified hour, minute, or second is inappropriate.

(Hour: 00 to 23, Minute: 00 to 59; Second: 00 to 59)

S:

Does not execute the command.

O:

Specify appropriate values in the date and time format (YYYYMMDDhhmmss), and then retry the operation.

KAVB2529-E

The range specified for the date is invalid.

A date later than the end date is specified as the start date.

S:

Does not execute the command.

O:

Specify a start date that is earlier than the end date, and then retry the operation.

KAVB2530-I

The jcocmdconv command started.

Processing of the jcocmdconv command started.

S:

Executes the command.

KAVB2531-I

The jcocmdconv command terminated. (Return code: return-code)

The jcocmdconv command ended.

S:

Finishes command processing.

KAVB2532-I

The user cancelled the conversion of the command-execution log file.

Processing of the jcocmdconv command was stopped by the user.

S:

Suspends command processing.

KAVB2534-E

The specified option option-name is invalid.

The option specified by the command line is invalid.

S:

Suspends command processing.

O:

Specify the correct option, and then re-execute the command.

KAVB2535-E

The number of arguments is invalid.

The argument of the option is incorrect.

S:

Suspends command processing.

O:

Specify the correct option, and then re-execute the command.

KAVB2536-E

The option option-name is specified more than once.

An option that can only be specified once is specified multiple times.

S:

Suspends command processing.

O:

Specify the correct option, and then re-execute the command.

KAVB2537-E

The value for the option option-name is not specified.

The specified option value is invalid.

S:

Suspends command processing.

O:

Specify the correct option, and then re-execute the command.

KAVB2538-E

The directory does not exist. (directory-path = directory-name)

The specified source or target execution directory does not exist.

S:

Suspends command processing.

O:

Specify the correct directory path, and then re-execute the command.

KAVB2539-E

The specified directory is too long. (directory-path = directory-name)

The specified directory is too long.

S:

Suspends command processing.

O:

Specify the correct directory path, and then re-execute the command.

KAVB2540-E

The specified logical host does not exist. (logical-host-name = logical-host-name)

The logical host name is invalid or does not exist.

S:

Suspends command processing.

O:

There is an error in the common definition information settings of the logical host. Check the logical host settings, and, if necessary, reconfigure the logical host.

KAVB2541-E

The specified logical host name is too long. (logical-host-name = logical-host-name)

The specified logical host name is too long.

S:

Suspends command processing.

O:

Check the logical host name specified by the -h option.

KAVB2542-E

Superuser permissions are required to execute the command.

The user executing the command does not have Administrator permissions.

S:

Suspends command processing.

O:

Execute the command as a user with Administrator or root permissions.

KAVB2543-E

Command execution will now stop because memory is insufficient.

An error occurred during memory allocation.

S:

Suspends command processing.

O:

Stop other processes that are using memory, and then re-execute the command.

KAVB2544-E

Command execution will now stop because disk space is insufficient.

There is insufficient disk space at the executing directory path.

S:

Suspends command processing.

O:

Increase the available disk space, and re-execute the command.

KAVB2545-E

The user does not have access permission for the file file-name.

The command could not be executed because there is no access permission for the command execution log file.

S:

Suspends command processing.

O:

Make sure that there is access permission for the command execution log file.

KAVB2546-E

The jcocmdconv command was interrupted.

Command processing was suspended.

S:

Suspends command processing.

O:

Re-execute the command.

KAVB2547-E

Another jcocmdconv command is already running.

Processing of the jcocmdconv command stopped because another jcocmdconv command is being executed on the same logical host.

S:

Suspends command processing.

O:

Determine whether a jcocmdconv command is already being executed.

KAVB2548-I

The specified file file-name contains no data to be converted.

There is no valid record in the specified execution log file.

S:

Suspends command processing.

KAVB2549-E

The source file file-name could not be deleted.

The specified command execution log file in an older format could not be deleted after file conversion.

S:

Finishes command processing without deleting the execution file.

O:

Make sure that there is access permission for the command execution log file in the older format.

KAVB2550-E

A file with the name of the command-execution log file after conversion (file-name) already exists.

The command could not be executed because the post-conversion command execution log file cannot be found in the specified path.

S:

Suspends command processing.

O:

Delete the command execution log file in the specified path, or specify a different path, and then re-execute the command.

KAVB2551-W

The command-execution log file for the executed command does not exist.

Conversion is not performed because the log of the command in an older format executed in the Execute Command window does not exist.

S:

Does not convert the log file of the command executed in the Execute Command window.

KAVB2552-W

The command-execution log file for the automatic action does not exist.

Conversion is not performed because the command execution log file for automated action does not exist.

S:

Does not convert the command execution log file for automated action.

KAVB2553-Q

Do you want to convert the command-execution log file? [Y/y or N/n] ->

Confirms that it is OK to process the command execution log file.

S:

Stops command processing and waits for a response.

O:

To continue command processing, specify Y or y. To stop command processing, specify N or n.

KAVB2554-Q

Do you want to delete the old-format command-execution log file file-name? [Y/y or N/n] ->

Confirms that it is OK to delete the command execution log file.

S:

Stops command processing and waits for a response.

O:

Specify Y or y to delete the command execution log file in the older format and continue processing. Specify N or n to continue processing without deleting the command execution log file in the older format.

KAVB2555-W

An attempt to initialize the HNTR library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 failed.

S:

Continues command execution without outputting the log.

KAVB2556-W

An attempt to initialize an individual trace log has failed. Processing will continue without logging messages.

An attempt to initialize an individual trace log failed.

S:

Continues command execution without outputting the log.

KAVB2557-W

An attempt to initialize integrated and individual trace logs has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 and an individual trace log has failed.

S:

Continues command execution without outputting the log.

KAVB2559-E

The contents of the common configuration definition are corrupted. The logical-host-name\\JP1BASE key does not exist.

The common definition key JP1BASE does not exist.

S:

Suspends command processing.

O:

The environment is invalid. Re-install JP1/Base.

KAVB2560-W

Log directory information could not be obtained from the common configuration definition of the logical host logical-host-name. Processing will continue without logging messages.

An attempt to obtain log directory information from the common definition information failed.

S:

Executes command processing without outputting the log.

KAVB2561-W

Log settings information could not be obtained from the common configuration definition of the logical host logical-host-name. Processing will continue without logging messages.

An attempt to obtain log settings information from the common definition information failed.

S:

Executes command processing without outputting the log.

KAVB2563-E

An attempt to get user input has failed.

An attempt to obtain user confirmation from standard output failed.

S:

Suspends command processing.

O:

Re-execute the command. If the problem cannot be resolved by re-executing the command, contact a system administrator.

KAVB2564-E

An attempt to initialize the common definition information has failed.

An attempt to initialize the common definition information failed.

S:

Suspends command processing.

O:

Make sure that the product is installed correctly. If the problem cannot be resolved, contact a system administrator.

KAVB2565-E

An error occurred during command processing.

One of the following errors occurred during processing:

Unable to read common definition information

Unable to open or read the executive file

Failed to create or delete the lck file used during processing

S:

Suspends command processing.

O:

Execute the Jischk command to determine whether the command execution log file is corrupted. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2566-E

Execute the command from the administrator console.

The command must be executed on the administrator console.

S:

Terminates command processing.

O:

Re-execute the command on the administrator console.

KAVB2567-E

Root privileges or JP1/Base administrator privileges are required to execute the command.

Execute with root or JP1/Base administrator privileges.

S:

Suspends command processing.

O:

Re-execute the command as a user with root or JP1/Base administrator privileges.

KAVB2600-I

New [process-name] Process with PID:[process-ID] is created.

The process name and process ID were created.

KAVB2605-E

The request to execute the command was rejected because the number of connected hosts to be managed has reached the maximum. (host = host-name)

The number of connections between managed hosts exceeded the maximum number that can be processed safely.

S:

Rejects the command execution request.

O:

Carefully review the configuration based on the restriction values given below for the number of hosts that a single JP1/IM can manage.

When close is specified as the communication type of the JP1/Base's event server configuration file (conf) on the manager host: 2,500

When a type other than close is specified as the communication type of the JP1/Base's event server configuration file (conf) on the manager host: 100 (UNIX) or 62 (Windows)

These numbers of units are the maximum that can be configured. The number of hosts that can actually be managed is limited depending on the system configuration and the network traffic.

KAVB2606-E

The automatic-action request command-name was rejected because the maximum number of processing requests was exceeded. (host = host-name, process = process-name, pid = process-ID)

The number of commands being executed exceeded the maximum number that can be processed safely. The automated action request will not be processed until the number of commands being executed is reduced to less than the maximum set by the system.

S:

Ignores the automated action request.

O:

Execute the jcocmdshow and jcocmddel commands to determine the number of commands currently being executed, and delete any unnecessary commands.

Make sure that the network connection to the execution host is functioning.

KAVB2607-E

The command-execution request command-name was rejected because the maximum number of processing requests was exceeded. (host = host-name, process = process-name, pid = process-ID)

The number of commands being executed exceeded the maximum number that can be processed safely. The automated action request will not be processed until the number of commands being executed is reduced to less than the maximum set by the system.

S:

Ignores the command execution request.

O:

Execute the jcocmdshow and jcocmddel commands to determine the number of commands currently being executed, and delete any unnecessary commands.

Make sure that the network connection to the execution host is functioning.

KAVB2608-E

The process process-name with the pid process-ID terminated abnormally. (Return code: return-code)

The process stopped abnormally due to a system error.

S:

If the process name is any of the following, the system terminates the command execution control abnormally:

jcocmdrouter

jcocmdexe

jcocmdcom

If the process name is the following, stops subsequent command processing of each client:

jcocmdapi

O:

Check the following items. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Is JP1/Base installed correctly?

Is the OS operating normally?

KAVB2609-I

The process process-name with the pid process-ID has started.

process-name process started.

KAVB2610-I

The process process-name with the pid process-ID finished normally.

process-name process ended normally.

KAVB2611-E

An attempt to create the process process-name has failed.

An attempt to create the process failed.

S:

Could not start the process due to a system restriction or internal error.

O:

Make sure that sufficient system resources are allocated. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2613-E

An attempt to allocate memory has failed. (process = process-name, pid = process-ID)

An attempt to allocate memory failed.

S:

Continues processing.

O:

Stop other processes that are using memory, and then re-execute the command.

KAVB2614-E

An attempt to load the message file has failed.

An attempt to open the message catalog file failed.

S:

Terminates command execution control.

O:

For UNIX, check the following. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Is there a message catalog file (Jcocmdmsg.cat) under the /opt/jp1base/lib/nls directory?

KAVB2615-E

An attempt to execute the command command-name failed due to a memory shortage. (error code = error-code)

An attempt to execute the command failed due to a memory shortage.

S:

Does not execute the command.

O:

Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Are sufficient memory and system resources allocated to execute the command?

KAVB2616-E

An attempt to execute the command command-name has failed. (pid = process-ID). (internal-message)

An attempt to execute the command failed for a reason other than a nonexistent command or a lack of resources.

S:

Does not execute the command.

O:

Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Is there appropriate permission to execute the command?

KAVB2618-E

An internal error occurred while processing the results.

An error occurred during processing of the command execution results. This error occurs on the host that requests command execution.

S:

Does not output the command execution result log to the command execution history file.

O:

Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Are sufficient resources allocated on the host that requests command execution?

KAVB2619-E

An attempt to initialize the log has failed. (Function name: function-name, error code = error-code)

An attempt to initialize log output failed while running the process due to one of the following reasons:

Unable to find the common definition parameter, or the parameter is incorrect.

A large number of processes are being executed concurrently.

S:

Continues command execution control processing without outputting the log.

O:

Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Use the jcocmdshow and jcocmddel commands to check the commands that are currently executing, and then delete unimportant commands.

KAVB2620-E

An error occurred during startup of the process process-name. (internal-message)

An error occurred while starting the service due to one of the following reasons:

The length of the JP1_HOSTNAME environment variable is 256 characters or more.

Insufficient resources at the time of process startup.

An internal error occurred while starting the process.

S:

Terminates the process abnormally.

O:

Check the following items. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Is the length of the environment variable 255 characters or fewer?

Are sufficient memory and system resources allocated to execute the command?

KAVB2621-E

An attempt to acquire the message from the message file has failed.

An attempt to acquire the message from the catalog file failed.

S:

Does not output the message.

O:

For UNIX, check the item below. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Is there a message catalog file (Jcocmdmsg.cat) under the /opt/jp1base/lib/nls directory?

KAVB2623-E

The command cannot be forwarded to the host host-name because the command length is numeric-value bytes or more. This length is not supported by the earlier JP1/Base version on the host. (process = process-name, pid = process-ID).

The version of JP1/Base installed on the execution host does not support the length of the specified command.

S:

Does not execute the command.

O:

Check the version of JP1/Base on the host specified as the execution host for the command. JP1/Base version 08-00 or later must be installed.

KAVB2626-E

The command request [command-name] from host [host-name] contained the invalid command transmission option [%d], and has been rejected.

The manager host has rejected a command execution request.

S:

Does not execute the command.

O:

Check whether there is a shortage of resources at the manager host. If not, run the data collection tools of JP1/Base and JP1/IM, and then contact a system administrator.

KAVB2627-E

The jcocmdconv command is accessing the command execution log file.

The jcocmdapi process was started during execution of the jcocmdconv command.

S:

Stops the jcocmdapi process.

O:

Determine whether the jcocmdconv command was executed. The jcocmdconv command must be executed while JP1/Base is in stop status.

KAVB2628-E

Reception of the command was rejected because it exceeds the maximum length of 4096 bytes.

A command request that exceeds 4,096 bytes was received.

S:

Does not execute the command.

O:

Check the length of the command specified in the Execute Command window or a command specified by automated action.

KAVB2630-E

A request from a host without access permissions was rejected. (request-source-host-name-or-IP-address)

A request was received from a host without the requisite permissions.

If the source IP address can be converted (by reverse lookup) into a host name, the host name is displayed for the request-source-host-name-or-IP-address. If reverse lookup is not possible, the source IP address is displayed.

S:

Suspends command processing.

O:

Determine whether a higher-level host has been configured in the configuration definition. If so, determine whether it matches the source host name.

If you plan on receiving requests from sources other than the higher-level host, specify the host name or IP address for the source in the common definition ALT_CLIENT_HOSTS.

KAVB2631-W

An attempt to acquire the common definition information has failed. (label=label-name,code=error-number)

An attempt to acquire the common definition information of a label failed.

S:

At startup: Assumes the common definition for the label is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Check the following:

Are there any problems with the settings of the common definition information of the label?

Are there sufficient system resources and memory?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2632-W

An invalid value is specified for UPPER_ONLY in the common definition.

An invalid value is specified for UPPER_ONLY in the common definitions.

S:

At startup: Assumes UPPER_ONLY in the common definitions is 0 and continues processing.

At reload: Continues processing using the value set prior to reload.

O:

Carefully review and, if necessary, correct, the value set in the common definition for UPPER_ONLY.

KAVB2633-W

An invalid host name is specified. (host=host-name)

An invalid host name is specified for ALT_CLIENT_HOSTS in the common definitions.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Check the following:

Has a host name of 256 bytes or more been specified?

Has an IP address been assigned to the host in the hosts, DNS, or jp1hosts2 settings?

KAVB2634-W

The specified host (host-name) already exists.

The host name specified for ALT_CLIENT_HOSTS in the common definition is a duplicate.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Carefully review and, if necessary, correct the definition of ALT_CLIENT_HOSTS in the common definitions.

KAVB2635-W

The number of specified hosts exceeds the maximum number allowed. (maximum).

The number of hosts specified for ALT_CLIENT_HOSTS in the common definitions exceeds the maximum.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Carefully review and, if necessary, correct the definition of ALT_CLIENT_HOSTS in the common definitions.

KAVB2636-W

An attempt to resolve the name of an upper-host (host-name) failed. (code=error-number)

An attempt to resolve the name of a higher-level host failed.

S:

Continues processing. However, further requests sent from the higher-level host are rejected.

O:

Check whether an IP address has been assigned to the higher-level host in the hosts, DNS, or jp1hosts2 settings.

KAVB2637-W

The IP address for the upper-host (host-name) could not be obtained.

IP address information could not be acquired for a higher-level host. This occurs primarily when there is a shortage of memory.

S:

Continues processing. However, further requests sent from the higher-level host are rejected.

O:

Determine whether the system is short of memory.

KAVB2638-W

An error occurred while the IP address information was being obtained.

An error occurred while acquiring IP address information for the host set for ALT_CLIENT_HOSTS in the common definitions. This occurs primarily when there is a shortage of memory.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Determine whether the system is short of memory. Secure sufficient memory, and then execute the jbs_spmd_reload command.

KAVB2639-W

SSL communication processing failed.[maintenance-information]

SLL communication processing failed, so the command was not executed.

S:

Continues with the next process.

O:

Check the following settings of the communication encryption function (SSL communication):

Is the parameter that specifies the character string longer than the maximum?

Is the value of the ENABLE parameter 0 or 1?

Are the values of the ENABLE parameters the same at connection source and connection target?

Are the correct files specified by the CERTIFICATEFILE and PRIVATEKEYFILE parameters?

Is the certificate CSR specified by the CERTIFICATEFILE parameter issued by the private key specified by the PRIVATEKEYFILE parameter?

Is the correct file specified by the CACERTIFICATEFILE parameter?

Is the version of the SSL communication specified by the SSLPROTOCOL parameter correct?

Is the encryption suite specified by the SSLCIPHERS parameter correct?

Is the service specified by the BASESSL parameter correct?

Can the version of the SSL communication specified on the server side by the SSLPROTOCOL parameter be used on the client side?

Can the encryption suite specified on the server side by the SSLCIPHERS parameter be used on the client side?

KAVB2640-W

A certificate expired.

The server certificate or root certificate has expired.

S:

Continues processing.

O:

Check the expiration dates of the server certificate and root certificate.

2.4 Messages related to Configuration Management (KAVB3001 to KAVB3200)

Note:

Messages with message IDs such as internal error messages may be output in addition to the messages shown in the message list.

KAVB3001-E

Fail to get conf directory path. jp1BsCnfGetStringValue fail.

The conf directory path could not be obtained from the common definition.

S:

Terminates processing.

O:

Determine whether the conf directory path of JP1/Base is defined in the common definition.

KAVB3002-E

Fail to get log directory path. jp1BsCnfGetStringValue fail.

The log directory could not be obtained from the common definition.

S:

Terminates processing.

O:

Determine whether the log directory path of JP1/Base is defined in the common definition.

KAVB3003-E

HNTRLib Initialize fail. bslog NULL.

An attempt to initialize message output failed.

S:

Does not output the message.

O:

Make sure that JP1/Base setup was completed normally.

KAVB3004-E

HNTRLib Initialize fail.

An attempt to initialize message output failed.

S:

Does not output the message.

O:

Make sure that JP1/Base setup was completed normally.

KAVB3005-E

Fail to open message file.

An attempt to open the message file failed.

S:

Does not output the message.

O:

In UNIX, determine whether the catalog file exists in the /opt/jp1base/lib/nls directory.

KAVB3006-E

Fail to load resource.

An attempt to read the message file failed.

S:

Does not output the message.

O:

Make sure that JP1/Base setup was completed normally.

KAVB3007-E

Fail to load catalog file.

An attempt to read the message file failed.

S:

Does not output the message.

O:

In UNIX, make sure that the message file (jbsrt.cat) exists in the /opt/jp1base/lib/nls directory and that the access permission is appropriate.

KAVB3008-E

vsprintf error.

An error occurred during internal processing of message output.

S:

Does not output the message.

O:

Make sure that sufficient system resources are allocated.

KAVB3010-I

Cannot move to the log directory.

Could not move data to the log output directory.

S:

Does not move data to the log directory.

KAVB3011-E

Failed to initialize JP1/IM communication infrastructure. Error Type = JBS_EJP1HOSTS

An attempt to initialize the communication infrastructure failed. Read processing failed because the jp1hosts data is invalid.

S:

Terminates processing.

O:

Carefully review the value of jp1hosts in the common definition.

KAVB3012-E

Failed to initialize JP1/IM communication infrastructure. jp1BsCommInit Error Code = error-code. Terminating

An attempt to initialize the communication infrastructure failed.

S:

Aborts processing.

O:

Make sure that JP1/Base setup was completed normally.

KAVB3013-I

Failed to acquire the port number. The default port number is used.

The port number could not be acquired.

S:

Uses the default port to start.

O:

Determine whether the port number for Configuration Management exists in the services file.

KAVB3015-E

Failed to initialize JP1/IM communication infrastructure. Terminating.

An attempt to initialize communication failed. It is possible that the port is already in use.

S:

Terminates processing.

O:

Determine whether the port for Configuration Management is already in use.

If IP bind is specified as the communication method, determine whether an invalid IP address is specified for a local IP host address.

KAVB3016-E

Failed to create a thread communication to the process management. Terminating.

An attempt to create a thread for communicating with process management failed.

S:

Terminates Configuration Management.

O:

Make sure that there is sufficient memory, and then retry the operation.

KAVB3017-E

jbsspm_getfd function failed. Terminating

An attempt to acquire a file descriptor for communication failed.

S:

Terminates the operation.

O:

Close other programs, and then retry the operation.

KAVB3018-I

jbsroute is running.

Configuration Management started.

S:

Configuration Management enters operating status.

KAVB3023-I

Reload request was received.

A reload request was received from process management.

S:

Starts reload processing.

KAVB3024-I

jbsroute terminate.

Configuration Management ended.

S:

Terminates Configuration Management.

KAVB3025-E

Cannot get JP1_BIND_ADDR. jp1BsCnfGetStringValue = function-return-value

The JP1_BIND_ADDR value of the common definition could not be acquired.

S:

Binds using ANY.

O:

Determine whether JP1_BIND_ADDR exists in the common definition.

KAVB3031-I

There is no definition of conf directory path for JP1/IM - Console.

The conf directory definition of JP1/IM - Manager could not be acquired.

S:

Starts as JP1/Base.

O:

If only JP1/Base is installed on the machine ignore this message.

KAVB3032-I

There is not JP1/IM - Console product Information.

The product type (JP1/IM - Manager) of JP1/IM cannot be acquired.

This message is always output when only JP1/Base is installed on a machine.

S:

Starts as JP1/Base.

O:

If only JP1/Base is installed on the machine, ignore this message.

KAVB3033-I

JP1/IM - Central Console

JP1/IM - Manager has been installed.

S:

Configuration Management operates as JP1/IM - Manager.

KAVB3034-I

JP1/IM - Satellite Console

JP1/IM - Satellite Console has been installed.

S:

Configuration Management operates as JP1/IM - Satellite Console.

KAVB3035-I

JP1/Base

JP1/Base has been installed.

S:

Configuration Management operates as JP1/Base.

KAVB3049-E

Failed to create communication data. jbsroute_make_rtdata Error Code = error-code. error-code-explanation

An attempt to create communication data failed.

S:

Continues processing.

O:

Make sure that there is sufficient memory.

KAVB3050-E

Failed to send communication data. jbsroute_send_rtdata Error Code = error-code. error-code-explanation

An attempt to send communication data failed.

S:

Continues processing.

O:

Determine whether there is a lower-level host in the configuration definition that is unable to communicate.

KAVB3051-E

Received configuration distribution request from JP1/Base

A definition distribution request was received from JP1/Base. Definitions cannot be distributed from a machine on which only JP1/Base is installed.

S:

Stops definition distribution.

O:

Carefully review the configuration definition file to determine whether a lower-level host is defined on a machine on which only JP1/Base is installed.

KAVB3052-E

JP1/IM - Central Console received configuration distribution request from JP1/IM - Satellite Console.

JP1/IM - Manager is defined at a lower level than JP1/IM - Satellite Console in the configuration definition.

S:

Does not distribute the definition to the host.

O:

Correct the configuration definition file so that JP1/IM - Manager is not defined at a lower level than JP1/IM - Satellite Console.

KAVB3053-E

JP1/Base defines lower-level hosts.

Lower-level hosts are defined in JP1/Base in the configuration definition.

S:

Does not distribute the definition to the lower-level hosts.

O:

Check the following items:

Correct the configuration definition file so that hosts are not defined under JP1/Base.

If this message is output on a logical host, make sure that logical host setup has been completed. If not, execute the following setup programs to set up the logical host.

Windows: jp1cohasetup.exe

UNIX: jp1cc_setup_cluster

KAVB3054-E

Failed to get lower-level host in the definition file. jbsroute_get_under_host Error Code = error-code. error-code-explanation

An attempt to acquire lower-level hosts in the definition file failed. This error occurs primarily when there is a memory shortage.

S:

Cannot perform definition distribution and other operations at the lower-level hosts.

O:

Determine whether a memory shortage occurred.

KAVB3055-E

Wrong attempt to distribute the configuration definition to the highest-level host from other host.

A separately defined definition file was sent from another host to a host that was defined as the highest-level host.

S:

Cannot perform definition distribution and other operations at the highest-level host.

O:

Another host cannot distribute configuration definition to a host defined as the highest-level host. Delete the configuration information at the highest-level host, and then re-execute the definition distribution command.

KAVB3056-E

Failed to get upper-level host. jbsroute_get_parent_host Error Code = error-code. error-code-explanation

The highest-level host could not be acquired.

S:

Cannot perform definition distribution and other operations.

O:

Determine whether a memory shortage occurred.

KAVB3057-E

Failed to get lower-level host. jbsroute_get_child_host Error Code = error-code. error-code-explanation

A lower-level host could not be acquired.

S:

Cannot perform definition distribution and other operations.

O:

Determine whether a memory shortage occurred.

KAVB3059-E

Failed to write data to configuration information file. jbsroute_write_rtdata Error Code = error-code. error-code-explanation

An attempt to write to the configuration definition file failed.

S:

Cannot perform definition distribution and other operations.

O:

Make sure that there is write permission for the conf/route/ directory.

KAVB3060-E

Failed to send communication data. jbsroute_send_rtdata_hosts Error Code = error-code. error-code-explanation

An attempt to send communication data failed.

S:

Cannot perform definition distribution and other operations at the transmission destination host.

O:

Make sure that JP1/Base is running on the transmission destination host. Also make sure that the host is able to communicate.

KAVB3073-E

Failed to get lower-level host information. jbsrt_getunderhost Error Code = error-code. error-code-explanation

A lower-level host could not be acquired.

S:

Terminates the Configuration Management command.

O:

Make sure that sufficient memory is allocated.

KAVB3074-E

Failed to delete configuration information file. jbsroute_del_rtdata Error Code = error-code. error-code-explanation

The configuration definition file could not be deleted.

S:

Terminates the jbsrt_distrib command.

O:

Make sure that there is write permission for the conf/route/ directory.

KAVB3078-E

Failed to communication initialization. jbsroute_send_rtdata_init Error Code = error-code. error-code-explanation

An attempt to initialize communication failed.

S:

Terminates the jbsrt_distrib or jbsrt_sync command.

O:

Check the environment for one of the following possible causes:

Is the network status normal?

Do the server and IP address versions (IPv4 or IPv6) match?

Is JP1/Base running on the server?

If the problem cannot be resolved, use the data collection tool to collect data at the local host and the server, and then contact a system administrator.

For details about how to check the version of an IP address (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the JP1/Base User's Guide.

KAVB3079-E

Failed to receive communication data. jbsroute_recv_rtdata Error Code = error-code. error-code-explanation

An attempt to receive communication data failed.

S:

Terminates the jbsrt_distrib or jbsrt_sync command.

O:

Determine whether an error occurred at the transmission destination host.

KAVB3080-E

Failed to open the definition file.

An attempt to open the definition file failed.

S:

Terminates the jbsrt_distrib command.

O:

Determine whether the configuration definition file is in the conf/route/ directory.

Also make sure that there is read permission for the configuration definition file.

KAVB3081-E

Memory allocation failed.

Memory could not be allocated.

S:

Configuration control continues processing. Terminates the command abnormally.

O:

Make sure that sufficient memory is allocated.

KAVB3082-E

A line with more than two entries exists.

The same host name is defined multiple times in the definition file.

S:

Terminates the jbsrt_distrib command.

O:

Determine whether the same host is defined multiple times in the configuration definition file.

KAVB3083-E

No entries in a line.

The definition file does not contain any host name line.

S:

Terminates the jbsrt_distrib command.

O:

Check the configuration definition file.

KAVB3084-E

Length of host name exceeds 256 characters. host-name

The length of the host name in the definition file is 256 characters or more.

S:

Terminates the jbsrt_distrib command.

O:

Carefully revise the configuration file so that the host name is no longer than 255 characters.

KAVB3085-E

Definition of management host is invalid. management-host-name

The definition of the management host in the definition file is invalid.

S:

Terminates the jbsrt_distrib command.

O:

Make sure that the displayed management host name is correctly enclosed by [ and ].

KAVB3086-E

The host is specified more than once. host-name

The same host is defined multiple times in the definition file.

S:

Terminates the jbsrt_distrib command.

O:

Carefully revise the configuration definition file so that the same host is not defined multiple times.

KAVB3087-E

Managed host does not exist. host-name

A management host is defined without the managed host.

S:

Terminates the jbsrt_distrib command.

O:

Carefully review the configuration definition file, and define the managed host for the management host.

KAVB3088-E

The host is in a loop status. host-name

The definition file contains a looped definition.

S:

Terminates the jbsrt_distrib command.

O:

Carefully review the configuration definition file, and correct the looped system configuration.

KAVB3089-E

The highest-level host is different. host-name host-name

Two or more highest-level hosts are defined in the definition file.

S:

Terminates the jbsrt_distrib command.

O:

Carefully review the configuration definition file, and make sure that only one host is defined as the highest-level host.

KAVB3090-E

Cannot get conf path from common definition.

The conf path could not be acquired from the common definition.

S:

Terminates Configuration Management or the command.

O:

Determine whether the conf directory of JP1/Base is defined in the common definition.

KAVB3091-E

HNTRLib could not be initialized.

An attempt to initialize message output failed.

S:

Does not output the message.

O:

Make sure that JP1/Base setup was completed normally.

KAVB3092-E

HNTRLib could not be initialized.

An attempt to initialize message output failed.

S:

Does not output the message.

O:

Make sure that JP1/Base setup was completed normally.

KAVB3093-E

No execution authorization.

The user who attempted to execute the command does not have operator permissions (in Windows, Administrators group permission; in UNIX, root permission or JP1/Base administrator permission).

S:

Cannot execute processing.

O:

Execute the command as a user with operator permissions.

KAVB3094-I

Failed to acquire the port number. The default port number is used.

The port number could not be acquired.

S:

Uses the default port to start.

O:

Determine whether the port number of Configuration Management exists in the services file.

KAVB3095-E

Failed to load definition file.

An attempt to read the definition file failed.

S:

Does not execute the jbsrt_distrib command.

O:

Make sure that the configuration definition file is placed in the correct location.

KAVB3096-E

Cannot get the current host name from the definition file.

The local host is not defined in the definition file.

S:

Does not execute the jbsrt_distrib command.

O:

Define the local host in the configuration definition file.

KAVB3097-E

Failed to get the lower-level host name in the definition file.

An error occurred while acquiring a lower-level host from the definition file.

S:

Does not execute the Configuration Management command.

O:

Make sure that sufficient memory is allocated.

KAVB3098-E

JP1/Base defines lower-level hosts.

Lower-level hosts are defined in JP1/Base.

S:

Does not distribute configuration definitions to the lower-level hosts.

O:

Check the following items:

Correct the configuration definition file so that hosts are not defined under JP1/Base.

If this message is output in a logical host, make sure that logical host setup has been completed. If not, execute the following setup programs to set up the logical host.

Windows: jp1cohasetup.exe

UNIX: jp1cc_setup_cluster

KAVB3099-E

Failed to get the definition data.

An I/O error occurred while reading the configuration definition file.

S:

Does not execute the Configuration Management command.

O:

Make sure that there is write permission for the conf/route/ directory.

KAVB3100-E

Failed to create communication data.

An attempt to create communication data failed. This error occurs primarily when there is a memory shortage.

S:

Does not execute the Configuration Management command.

O:

Make sure that sufficient memory is allocated.

KAVB3101-E

Failed to connect to the server.

An attempt to connect to the server failed.

S:

Does not execute the Configuration Management command.

O:

Check the environment for one of the following possible causes:

Is the network status normal?

Do the server and IP address versions (IPv4 or IPv6) match?

Is JP1/Base running on the server?

If the problem cannot be resolved, use the data collection tool to collect data at the local host and the server, and then contact a system administrator.

For details about how to check the version of an IP address (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the JP1/Base User's Guide.

KAVB3102-E

Failed to send the data. Error Code = error-code. error-code-explanation

An attempt to send data to the Configuration Management server failed.

S:

Terminates the jbsrt_distrib or jbsrt_sync command.

O:

Determine whether Configuration Management is running and whether a memory shortage occurred.

KAVB3103-E

Failed to receive the data.

An attempt to receive data from the Configuration Management server failed.

S:

Places the jbsrt_distrib or jbsrt_sync command in error status.

O:

Check the following items:

After JP1/IM was installed, was JP1/Base restarted?

Has a memory shortage occurred?

Is there write or read permission for the conf/route/ directory?

KAVB3104-W

Cannot delete configurations for the host and its lower-level hosts. Try again after deleting each definition separately.host-name

Configuration information could not be deleted from certain hosts.

O:

Execute the jbsrt_del command to delete configuration information individually from the displayed host and its lower-level hosts.

KAVB3105-E

The server is processing.

An attempt was made to distribute definitions during processing of the Configuration Management server.

S:

Places the jbsrt_distrib or jbsrt_sync command in error status.

O:

Wait awhile, and then retry the operation.

KAVB3106-I

Deleted the current configuration definition

The jbsrt_distrib command was used to delete configuration information.

S:

Continues processing.

KAVB3107-E

Cannot set configuration in the host. host-name

Configuration information could not be set in certain hosts during configuration definition confirmation.

S:

Places the jbsrt_distrib command in error status.

O:

On the host that has the error, check the following items:

Is JP1/Base running? (Can be checked with the jbs_spmd_status command.)

Is the configuration management port (initialized to 20237/tcp) running? (Can be checked with the netstat command.)

Is the configuration management port (initialized to 20237/tcp) being filtered by a firewall or similar utility?

Is it possible to resolve the name of the host that has the error from a higher-level host than the host that has the error? (Can be checked with the jp1ping command.)

Is the IP address found by resolving the name of the intended IP address?

Was the host that has the error previously defined as the highest-level host? (Can be checked with the jbsrt_get command.) If the configuration definition information from when it was the highest-level host remains, execute the jbsrt_del command to delete the configuration information.

Has a memory shortage occurred?

Are there write and read permissions for the conf/route/ directory?

If the problem is other than the above, check the following items in the host that has the error:

Execute the jbsrt_get command.

Determine whether any of the following have occurred:

• Was a KAVB3162-E message output?

• Did the jbsrt_get command end abnormally?

• Is the local host name displayed as a higher-level host or a lower-level host?

• Is a host name other than the local host name displayed as the local host?

• Is the host name misspelled?

If any of the above occurred, use the following method to recover from the error:

1. Execute the jbsrt_del command to delete the configuration definition information.

2. On the manager host, execute the jbsrt_distrib command to redistribute the configuration definition information.

KAVB3108-E

Failed in definition distribution. Cannot set configuration information in the host. host-name

Configuration information could not be distributed to certain hosts during configuration distribution.

O:

Re-execute the jbsrt_distrib command, distributing the definition without deleting the configuration information. If you can confirm that the definition was distributed to hosts and lower-level hosts for which errors occurred previously, it means that the configuration definition was distributed to the entire system.

KAVB3109-I

Succeed the jbsrt_distrib command

The definition distribution command ended normally.

S:

Ends the jbsrt_distrib command normally.

KAVB3110-E

Definition data is not found.

The configuration information has not been defined.

S:

Does not execute the jbsrt_sync command.

O:

Execute the jbsrt_distrib command, and then execute the jbsrt_sync command.

After the jbsrt_sync command is executed, make sure that the conf/route/ directory exists and that there is read and write permission for it.

If operating in a cluster environment, make sure that the defined conf directory exists and that there is read and write permission for it.

KAVB3111-E

Failed to execute the jbsrt_sync command. An error occurred in the host. host-name

An error occurred during execution of the jbsrt_sync command.

S:

Displays the host that has the error.

O:

Make sure that JP1/Base is running on the host that has the error. If it is running, check the following items:

Execute the jbsrt_get command.

Determine whether any of the following occurred:

• Was a KAVB3162-E message output?

• Did the jbsrt_get command end abnormally?

• Is the local host name displayed as a higher-level host or a lower-level host?

• Is a host name other than the local host name displayed as the local host?

• Is the host name misspelled?

If any of the above occurred, use the following method to recover from the error:

Execute the jbsrt_del command to delete the configuration definition information.

On the manager host, execute the jbsrt_distrib command to redistribute the configuration definition information.

KAVB3112-I

Succeed the jbsrt_sync command

The synchronization command ended normally.

S:

Ends the jbsrt_sync command normally.

KAVB3113-I

Definition does not exist.

The configuration information has not been defined.

S:

Terminates the jbsrt_get and jbsrt_del commands.

O:

Execute the jbsrt_distrib command, and then retry the operation.

After the jbsrt_distrib command is executed, make sure that the conf/route/ directory exists and that there is read and write permission for it.

If operating in a cluster environment, make sure that the defined conf directory exists and that there is read and write permission for it.

KAVB3114-E

Cannot access definition.

An attempt to read the configuration information failed.

S:

Terminates the jbsrt_get and jbsrt_del commands.

O:

Make sure that there is write permission for the conf/route/ directory.

KAVB3115-I

Deleted the definition data.

The jbsrt_del command ended normally.

S:

Ends the jbsrt_del command.

KAVB3116-I

Get the logical host name from the environment variable of JP1_HOSTNAME

The logical host name was obtained from the JP1_HOSTNAME environment variable.

S:

Starts as a logical host of the name obtained from the JP1_HOSTNAME environment variable.

O:

To start as a physical host, cancel the JP1_HOSTNAME environment variable setting.

KAVB3118-E

jbsrt_distrib command is time out.

An error occurred in the host. host-name

A time-out of the jbsrt_distrib command occurred.

S:

Places the jbsrt_distrib command in error status and terminates the command.

O:

Check the following points, and then re-execute the command:

Determine whether an error occurred in a lower-level host. When host-name includes a submanager, a host under the submanager might take time for the processing. Check the integrated trace log of the submanager.

Wait until processing by the submanager and a host under the submanager is completed, and then re-execute the command. To know whether the processing is completed, check whether the KAVB3185-I message was issued on the submanager host after the timeout.

If there is no error on lower-level hosts but this message is issued, the duration of processing by the submanager and a host under the submanager might exceed the communication timeout period. Adjust the communication timeout period or review the system configuration by referring to the processing duration described in the KAVB3185-I message that is issued on the submanager host.

KAVB3119-E

jbsrt_sync command is time out.

An error occurred in the host. host-name

A time-out of the jbsrt_sync command occurred.

S:

Places the jbsrt_sync command in error status and terminates the command.

O:

Check the following points, and then re-execute the command:

Determine whether an error occurred in a lower-level host. When host-name includes a submanager, a host under the submanager might take time for the processing. Check the integrated trace log of the submanager.

Wait until processing by the submanager and a host under the submanager is completed, and then re-execute the command. To know whether the processing is completed, check whether the KAVB3185-I message was issued on the submanager host after the timeout.

If there is no error on lower-level hosts but this message is issued, the duration of processing by the submanager and a host under the submanager might exceed the communication timeout period. Adjust the communication timeout period by referring to the processing duration described in the KAVB3185-I message that is issued on the submanager host.

KAVB3120-E

Failed to initialize JP1/IM communication infrastructure. Error Type = JBS_EJP1HOSTS

An attempt to initialize the communication infrastructure failed. Read processing failed because the jp1hosts data is invalid.

S:

Terminates processing.

O:

Carefully review the value of the jp1hosts common definition.

KAVB3121-E

Failed to initialize JP1/IM communication infrastructure. jp1BsCommInit Error Code = error-code

An attempt to initialize the communication infrastructure failed.

S:

Terminates the Configuration Management command.

O:

Make sure that JP1/Base setup was completed normally.

Collect data, and then contact a system administrator.

KAVB3123-E

Too many lower-level host. The maximum number is the-maximum-number-of-lower-level-hosts-directly-underneath

The number of hosts specified directly underneath as lower-level hosts in the configuration definition exceeds the maximum.

S:

Does not set the configuration information for the lower-level hosts.

O:

Make sure that no more than 5 hosts are defined immediately underneath JP1/IM - Central Console 5 Node and that no more than 10 hosts are defined immediately underneath JP1/IM - Central Console 10 Node.

KAVB3124-E

Cannot get conf path from common definition with specified logical host name.

The conf path to the logical host name specified in the common definition could not be acquired.

S:

Terminates Configuration Management or the command.

O:

Make sure that the specified logical host name is correct, and that the conf directory of JP1/Base is defined in the common definition of the specified logical host name.

KAVB3133-E

Failed to execute jevreload command.

The jevreload command could not be executed.

S:

Does not execute the jevreload command.

O:

Determine whether a memory shortage occurred.

KAVB3134-E

Failed to get install path.

In Windows, the installation path of JP1/Base could not be acquired.

S:

Does not execute the jevreload command.

O:

Make sure that JP1/Base has been correctly installed and configured.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB3135-E

Failed to create jevreload process.

The jevreload command could not be executed.

S:

Does not execute the jevreload command.

O:

Determine whether a memory shortage occurred.

KAVB3148-E

An attempt to use the jp1gethostname function has failed.

An attempt to perform initialization processing for communication failed.

S:

Suspends processing.

O:

For a physical host, make sure that the local host name setting is correct. For a logical host, make sure that the logical host name setting is correct.

KAVB3149-E

An attempt to use the jp1gethostbyname(hostname:host-name) function has failed.

An attempt to resolve an IP address from the host name failed.

S:

Suspends processing.

O:

Determine whether it is possible to jp1ping the host name. If you are using DNS, determine whether there is trouble on the network.

KAVB3150-E

An attempt to create a socket has failed.

A communication socket could not be generated.

S:

Suspends processing.

O:

Make sure that sufficient system resources are allocated.

KAVB3151-E

An attempt to set socket options has failed.

An attempt to specify socket options failed.

S:

Suspends processing.

O:

Make sure that sufficient system resources are allocated.

KAVB3152-W

An attempt to bind has failed (IP address: IP-address).

A failure occurred during initialization processing for communication.

S:

Continues processing.

O:

Make sure that the relevant IP address is correctly assigned to the network card.

KAVB3153-W

An attempt to listen has failed (IP address: IP-address).

A failure occurred during initialization processing for communication.

S:

Continues processing until wait response processing has been tried for all IP addresses defined in the local host.

O:

Make sure that the relevant IP address is correctly assigned to the network card and that the communication environment is ready.

KAVB3154-I

Bind and listen attempt has succeeded (IP address: IP-address).

Initialization of the communication environment was successful.

S:

Continues processing.

KAVB3155-E

No appropriate bind and listen IP address was found.

A failure occurred during initialization processing for communication.

S:

Suspends processing.

O:

Prepare the communication environment, and then retry the operation.

KAVB3156-W

An attempt to connect has failed (hostname: host-name, IP address: IP-address).

A failure occurred during initialization processing for communication.

S:

Continues processing until connection has been tried to all IP addresses defined by the host name.

O:

Check the environment for one of the following possible causes:

Is the network status normal?

Do the server and IP address versions (IPv4 or IPv6) match?

Is JP1/Base running on the server?

If the problem cannot be resolved, use the data collection tool to collect data at the local host and the server, and then contact a system administrator.

For details about how to check the version of an IP address (IPv4 or IPv6), see the description of the jp1ping command in the chapter on commands in the JP1/Base User's Guide.

KAVB3157-I

An attempt to connect has succeeded (hostname: host-name, IP address: IP-address).

An attempt to establish a communication connection was successful.

S:

Continues processing.

KAVB3158-E

No appropriate bind and connect IP address was found.(hostname: host-name)

A failure occurred during initialization processing for communication.

S:

Suspends processing.

O:

Carefully review the OS settings for hosts information, DNS, and jp1hosts2, and determine whether an IP address has been assigned to the host at the connection destination. Assign an IP address to the local host that is of the same version (IPv4 or IPv6) as the IP address assigned to the connection-destination host and at least one higher.

KAVB3159-E

Please set the logical host name to within 255 characters.

A string of 256 characters or more was specified for a logical host name.

S:

Suspends processing.

O:

Specify a logical host name that contains no more than 255 characters.

KAVB3160-W

Part of TCP/IP wait response processing has failed, but jbsroute processing will continue.

An attempt to perform part of TCP/IP wait response processing failed.

S:

Continues processing.

O:

Part of the IP address may have been specified incorrectly. Configuration Management processing of JP1/Base continues in impaired status. However, in this status, part of communication processing is not performed correctly. Resolve the problem, and then restart JP1/Base.

KAVB3161-E

An error occurred in system call.:maintenance-information

An error occurred in an OS system call.

S:

Suspends processing.

O:

Check the following items. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Are sufficient system resources allocated?

Is the OS operating normally?

Is the communication environment operating normally?

KAVB3162-E

The configuration information file is invalid.

The configuration definition file cannot be read because it is invalid.

S:

Configuration Management continues processing. Terminates the jbsrt_distrib, jbsrt_sync, and jbsrt_get commands.

O:

Use the following procedure to recover from the error:

To delete the configuration definition information, execute the jbsrt_del command on the host where the message is output.

Execute the jbsrt_distrib command to redistribute configuration definition information from the highest-level host.

KAVB3163-E

Execute the command from the administrator console.

This command must be executed from the administrator console.

S:

Terminates command processing.

O:

Re-execute the command from the administrator console.

KAVB3164-E

A request from a host without access permissions was rejected. (request-source-host-name-or-IP-address)

A request was received from a host without the requisite permissions.

If the source IP address can be converted (by reverse lookup) into a host name, the host name is displayed for the request-source-host-name-or-IP-address. If reverse lookup is not possible, the source IP address is displayed.

S:

Suspends command processing.

O:

Determine whether the source host name matches the higher-level host configured in the configuration definition.

If you plan on receiving requests from sources other than the higher-level host, specify the host name or IP address for the source in the common definition ALT_CLIENT_HOSTS.

KAVB3165-W

An attempt to acquire the common definition information has failed. (label=label-name,code=error-number)

An attempt to acquire the common definition information of the label failed.

S:

At startup: Assumes the common definition for the label is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Check the following:

Are there any problems with the settings of the common definition information of the label?

Are there sufficient system resources and memory?

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB3166-W

An invalid value is specified for UPPER_ONLY in the common definition.

An invalid value is specified for UPPER_ONLY in the common definitions.

S:

At startup: Assumes UPPER_ONLY in the common definitions is 0 and continues processing.

At reload: Continues processing using the value set prior to reload.

O:

Carefully review and, if necessary, correct, the value set in the common definition for UPPER_ONLY.

KAVB3167-W

An invalid host name is specified. (host=host-name)

An invalid host name is specified for ALT_CLIENT_HOSTS in the common definitions.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Check the following:

Has a host name of 256 bytes or more been specified?

Has an IP address been assigned to the host in the hosts, DNS, or jp1hosts2 settings?

KAVB3168-W

The specified host (host-name) already exists.

The host name specified for ALT_CLIENT_HOSTS in the common definitions is a duplicate.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Carefully review and, if necessary, correct the definition of ALT_CLIENT_HOSTS in the common definition.

KAVB3169-W

The number of specified hosts exceeds the maximum number allowed. (maximum).

The number of hosts specified for ALT_CLIENT_HOSTS in the common definitions exceeds the maximum.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Carefully review and, if necessary, correct the number of hosts specified.

KAVB3170-W

An attempt to resolve the name of an upper-host (host-name) failed. (code=error-number)

S:

Continues processing. However, further requests sent from a higher-level host are rejected.

O:

Check whether an IP address has been assigned to the higher-level host in the hosts, DNS, or jp1hosts2 settings.

KAVB3171-W

The IP address for the upper-host (host-name) could not be obtained.

IP address information could not be acquired for a higher-level host. This occurs primarily when there is a shortage of memory.

S:

Continues processing. However, further requests sent from the higher-level host are rejected.

O:

Determine whether the system is short of memory.

KAVB3172-W

An error occurred while the IP address information was being obtained.

An error occurred while acquiring IP address information for the host set for ALT_CLIENT_HOSTS in the common definitions. This occurs primarily when there is a shortage of memory.

S:

At startup: Assumes ALT_CLIENT_HOSTS in the common definitions is undefined and continues processing.

At reload: Continues processing using the definition set prior to reload.

O:

Determine whether the system is short of memory. Secure sufficient memory, and then execute the jbs_spmd_reload command.

KAVB3173-W

There is an incorrect value in the common definition information. (label= label-name, value= value)

An incorrect value is set on a label in the common definition.

S:

At startup: Continues processing by using the default value.

At reload: Continues processing by using the definition set prior to the reload.

O:

Check the specified values in the common definition.

KAVB3180-W

Communication with the host host-name timed out. (timeout period= time-out-seconds seconds)

Communication with host-name timed out.

S:

Continues processing.

O:

Check the following points:

Check the network configuration and status.

When an indicated host is a lower-level submanager host, a host under the submanager might take time for the processing. Check the integrated trace log of the submanager.

If there is no error on lower-level hosts including the submanager but this message is issued, the duration of processing might exceed the communication timeout period. Adjust the communication timeout period by referring to the processing duration described in the KAVB3185-I message that is issued on the submanager host.

KAVB3181-W

An error occurred during communication with the host host-name.

An error occurred with the communication with host-name.

S:

Continues processing.

O:

Check the network configuration and status. Make sure that JP1/Base is running on the connected host.

KAVB3185-I

Processing of the request-name sent to lower-level hosts is complete. (host name=host-name, processing time=processing-duration seconds)

The request-name processing sent to lower-level hosts is complete in processing-time seconds. The request-name indicates configuration check, configuration distribution, configuration deletion, or configuration synchronization. This message is output on the manager host defined in the configuration. However, this message is not output when the processing sent to lower-hosts is suspended due to an error.

S:

Continues processing.

2.5 Messages related to process management (KAVB3501 to KAVB3999)

Note:

Messages with message IDs such as internal error messages may be output in addition to the messages shown in the message list.

Messages related to process management may be output from JP1/Base or JP1/AJS (if installed) on the same host. For more information about messages output by JP1/Base and JP1/AJS, see the manual JP1/Base User's Guide.

KAVB3501-E

An attempt to open the message file has failed.

An attempt to open the message file failed.

S:

Terminates process management.

O:

In Windows:

Use the data collection tool to collect data, and then contact a system administrator.

In UNIX:

The possible causes are as follows. Check the environment.

• There may be no read permission for files in the /opt/jp1base/lib/nls directory. Assign read permission.

• The maximum number of files that can be opened in the system may have been reached. Review the kernel parameter.

• There may be a temporary memory shortage. Retry the operation. Also stop unnecessary processes.

• A directory or file may have been deleted. Re-install JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB3502-E

An attempt to read the message file has failed.

An attempt to read the message file failed.

S:

Does not output the message.

O:

Make sure that JP1/Base setup was completed normally.

KAVB3503-E

An attempt to read the message file has failed.

An attempt to read the message file failed.

S:

Does not output the message.

O:

Make sure that the message file (jbsspm.cat) exists in the /opt/jp1base/lib/nls directory and that the access permission is appropriate.

KAVB3504-E

An error occurred in internal processing to output a message.

An error occurred during internal processing to output a message.

S:

Does not output the message.

O:

Make sure that sufficient system resources are allocated.

KAVB3516-E

An attempt to start the process management has failed. (errno = request-code)

An attempt to start process management failed.

S:

Terminates process management.

O:

Make sure that the product is correctly installed.

KAVB3552-E

component-name managed-process-name has timed out.

The request timed out. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

O:

For a reload request, increase the time-out value, and then retry the operation. For other requests, wait awhile, and then retry the request. If the same message is displayed after re-execution, use the data collection tool to collect data, and then contact a system administrator.

KAVB3553-E

SIGKILL was sent to managed-process-name of component-name, but termination could not be detected.

SIGKILL was sent to the managed process, but termination could not be detected. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Terminates process management.

O:

Determine whether managed-process-name stopped. If managed-process-name did not stop, manually stop it.

KAVB3554-I

A component-name reload request has finished.

A reload request was completed. component-name is JP1_CONS.

S:

Continues processing.

KAVB3564-I

jxx_spmd: component-name will now start all inactive processes.

All inactive managed processes will be started. jxx is jco. component-name is JP1_CONS.

S:

Continues processing.

KAVB3574-I

jxx_spmd_reload: A reload request will now be sent to all running processes of component-name.

A reload request will be sent to all running managed processes. jxx is jco. component-name is JP1_CONS.

S:

Continues processing.

KAVB3577-I

jxx_spmd_stop: A stop request will now be sent to all processes of component-name

A stop request will be sent to all managed processes. jxx is jco. component-name is JP1_CONS.

S:

Continues processing.

KAVB3578-I

component-name has ended.

Terminates process management. component-name is JP1_CONS.

S:

Terminates process management.

KAVB3586-I

component-name has terminated.

Terminates process management. component-name is JP1_CONS.

S:

Terminates process management.

KAVB3597-I

jxx_spmd_stop -kill: A forced stop (kill) will be performed on all processes of component-name.

A forced stop will be performed on all managed processes. jxx is jco. component-name is JP1_CONS.

S:

Continues processing.

KAVB3599-E

main_loop: An invalid request was received for Service Control Manager. (event ID = request-type)

An invalid request was received.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB3602-I

component-name received a startup report from managed-process-name.

A startup report was received. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

KAVB3603-I

All processes of component-name are running.

All managed processes are running. component-name is JP1_CONS.

S:

Continues processing.

KAVB3604-I

component-name startup has finished.

Service startup was completed. component-name is JP1_CONS.

S:

Continues processing.

KAVB3605-I

component-name completed to send the start up request to the managed-process-name.

Restart of the managed process that ended abnormally was completed. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

KAVB3608-I

component-name received a reload-completed notification from managed-process-name.

A reload-completed notification was received from a managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

KAVB3609-I

A component-name reload request has finished.

Reload processing for a managed process was completed. component-name is JP1_CONS.

S:

Continues processing.

KAVB3610-I

component-name received an termination notification from managed-process-name.

Termination notification was received from a managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

KAVB3612-I

A stop request will now be sent to all processes of component-name.

A stop request will be sent to all managed processes. component-name is JP1_CONS.

S:

Continues processing.

KAVB3613-W

A component-name timeout occurred in managed-process-name. Processing continues.

A startup time-out occurred in a managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

O:

In Windows:

Wait a while. If startup of the managed process has not finished and the service does not start, stop and then restart the service.

In UNIX:

Wait a while. If startup of the managed process has not finished and the service does not start, use jco_stop to stop the service, and then restart the service.

KAVB3614-E

Process management will now stop because an invalid component-name status occurred.

Process management will stop due to an invalid status. component-name is JP1_CONS.

S:

Terminates process management.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB3616-I

Restart of the component-name managed-process-name has finished.

Restart of the managed process that ended abnormally was completed. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

KAVB3620-E

The user does not have permission to execute the command execution-command-name.

The user executing the command does not have Administrator permissions.

S:

Does not execute the command.

O:

Execute the command as a user with Administrator permissions.

KAVB3621-E

A fork system call failed during initialization: component-name

An attempt to perform a fork system call to be executed in the background failed during startup of process management. component-name is JP1_CONS.

S:

Terminates process management.

O:

Make sure that sufficient system memory has been allocated. Also make sure that the OS is operating normally.

KAVB3623-E

The setsid function failed. (error-explanation)

A setsid system call failed.

S:

Terminates process management.

O:

Make sure that sufficient system memory has been allocated. Also make sure that the OS is operating normally.

KAVB3624-E

An attempt to create a process management table has failed.

An attempt to create a process management table failed.

S:

Terminates the process management command.

O:

Make sure that sufficient system memory is allocated, that the product is correctly installed, and that the settings in the extended startup process definition file (jp1co_service.conf) are specified correctly. Also determine whether any processes managed by process management remain after ending abnormally.

Delete the extended startup process definition file, and then restart process management.

KAVB3625-E

An internal error occurred. Execution Command names differ. execution-command-name

The execution command names do not match.

S:

Terminates process management.

O:

Check execution-command-name. The command no longer operates if execution-command-name is changed.

KAVB3626-E

An attempt to create a lock file has failed. path-to-lock-file - error-explanation

An attempt to create a lock file failed.

S:

Terminates the process management command.

O:

Make sure that the conf directory exists and that there is read and write permission for it. If operating in a cluster environment, make sure that the defined conf directory exists and that there is read and write permission for it.

KAVB3627-I

component-name is already running.

The service was started twice. component-name is JP1_CONS.

S:

Terminates the process management command.

KAVB3631-E

build_proc_table : The return value NULL was returned to the getfield function. setting

Entries in the extended startup process definition file (jp1co_service.conf) are not specified correctly.

S:

Terminates process management.

O:

Make sure that the entries in the extended startup process definition file are specified correctly.

KAVB3642-E

An internal error occurred. Component names differ. component-name

The component names do not match. component-name is JP1_CONS.

S:

Terminates process management.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB3643-E

An attempt to open the environment definition file file-name has failed.

An attempt to open the environment definition file failed.

S:

Terminates process management.

O:

Make sure that the product is correctly installed.

KAVB3644-E

An attempt to expand the environment variables has failed.

An attempt to read the environment variable from jxx_spmd_env.conf failed. jxx is jco.

S:

Terminates process management.

O:

Make sure that sufficient system memory is allocated.

KAVB3645-I

The logical hostname for process management is logical-host-name.

Process management starts on a logical host.

S:

Continues processing.

KAVB3646-I

The option-name option is specified.

Process management starts with an option.

S:

Continues processing.

KAVB3647-E

The expiration of the time limit. product-name

The evaluation version has expired.

S:

Suspends processing.

KAVB3649-E

The environment variable of JP1_HOSTNAME is empty.

The setting of the JP1_HOSTNAME environment variable is incorrect.

S:

Terminates the process management command.

O:

Specify the correct logical host name for the JP1_HOSTNAME environment variable, or delete the JP1_HOSTNAME environment variable.

KAVB3651-I

Startup processing for component-name has started.

Process management will start a managed process. component-name is JP1_CONS.

S:

Process management will start the managed process.

KAVB3652-E

A timeout occurred during the wait for a response. (timeout period = time-out-seconds seconds)

A time-out occurred while waiting for a response.

S:

Terminates the process management command.

O:

Change the time-out value, and then retry the operation.

KAVB3653-E

An attempt to send a request to the process management has failed.

An attempt by the process management command to communicate with process management failed.

S:

Terminates the process management command.

O:

Make sure that the /var/opt/jp1base/tmp directory exists.

KAVB3654-E

An attempt to receive a response from the process management has failed.

An attempt by the process management command to receive data from process management failed.

S:

Terminates the process management command.

O:

Restart process management, and then retry the operation.

KAVB3655-E

Invalid data was received from process management.

The process management command received invalid data from process management.

S:

Terminates the process management command.

O:

Invalid data may have been received temporarily. Restart process management, and then retry the operation.

KAVB3656-I

The startup command terminated normally.

The process management startup command ended normally.

S:

Terminates the process management command.

KAVB3657-E

The startup command terminated abnormally

The startup command ended abnormally.

S:

Terminates the process management command.

O:

Execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.

KAVB3658-E

The startup command terminated abnormally due to an inconsistent state.

This message is output when the command is executed while process management is performing other processing.

S:

Terminates the process management command.

O:

Wait awhile, execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.

KAVB3659-I

There were no processes that could run.

No processes can be run.

S:

Terminates the process management command.

KAVB3660-E

Invalid data was received.

The process management command received invalid data from process management.

S:

Terminates the process management command.

O:

Invalid data may have been received temporarily. Restart process management, and then retry the operation.

KAVB3661-E

An unexpected result code was received. (Return code: return-code)

The process management command received an inappropriate result code from process management.

S:

Terminates the process management command.

O:

Execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.

KAVB3662-I

The process management is not running.

Process management stopped.

S:

Terminates the process management command.

KAVB3663-E

Execute the command from the administrator console.

This command must be executed from the administrator console.

S:

Terminates command processing.

O:

Re-execute the command from the administrator console.

KAVB3672-I

A forced termination (kill) of component-name has started.

Forced termination processing of process management will start. component-name is JP1_CONS.

S:

Terminates the process management command.

KAVB3674-I

Termination processing of component-name has started.

Termination processing of process management will start. component-name is JP1_CONS.

S:

Terminates the process management command.

KAVB3675-I

The stop command terminated normally.

The stop command of process management ended normally.

S:

Terminates the process management command.

KAVB3676-E

The stop command terminated abnormally.

The stop command ended abnormally.

S:

Terminates the process management command.

O:

Wait awhile, execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.

KAVB3677-E

The stop command terminated abnormally due to an inconsistent state.

The command was executed while process management was performing other processing.

S:

Terminates the process management command.

O:

Wait awhile, and then retry the operation.

KAVB3678-I

There were no processes that could terminate.

No processes can be terminated.

S:

Terminates the process management command.

KAVB3680-I

Reload processing for component-name has started.

Reload processing for a process being managed by process management will start. component-name is JP1_CONS.

S:

Terminates the process management command.

KAVB3681-I

The reload command terminated normally.

The reload command of process management ended normally.

S:

Terminates the process management command.

KAVB3682-E

The reload command terminated abnormally.

The reload command ended abnormally.

S:

Terminates the process management command.

O:

Determine whether any managed processes failed during reload processing.

KAVB3683-E

The reload command terminated abnormally due to an inconsistent state.

The command was executed while process management was performing other processing.

S:

Terminates the process management command.

O:

Wait awhile, and then retry the operation.

KAVB3684-E

There were no processes that could be reloaded.

No processes can be reloaded.

S:

Terminates the process management command.

O:

Determine whether managed processes are running.

KAVB3685-E

A timeout occurred in process-name.

Reload processing of the process indicated by process-name timed out.

S:

Terminates the process management command.

O:

Determine whether any managed processes failed during reload processing.

KAVB3690-I

Processing to report the status of component-name has started.

Processing to report process management status will start. component-name is JP1_CONS.

S:

Terminates the process management command.

KAVB3691-I

All the processes have started.

All managed processes have started.

S:

Terminates the process management command.

KAVB3692-I

Some of the processes have started.

Some managed processes have started.

S:

Terminates the process management command.

KAVB3693-I

All of the processes have stopped.

All managed processes have stopped.

S:

Terminates the process management command.

KAVB3694-I

Part of the process is now restarting.

Part of process management is restarting.

S:

Terminates the status notification command of process management.

KAVB3705-I

managed-process-name is now starting. (process ID = process-ID)

The managed process is starting. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the managed process being started.

S:

Continues processing.

KAVB3732-I

component-name detected the termination of managed-process-name. (process ID = process-ID)

Termination of the managed process was detected. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the managed process being started.

S:

Continues processing.

KAVB3736-I

All processes of component-name have stopped.

All managed processes have stopped. component-name is JP1_CONS.

S:

Terminates process management.

KAVB3737-E

The component-name managed-process-name terminated abnormally.

Abnormal termination of the managed process was detected. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

O:

Refer to the integrated trace log output by the managed process that stopped abnormally, and remove the cause of the problem. Execute the jxx_spmd_status command to check the status, and then restart process management. jxx is jco. If there is no message output by the managed process, use the data collection tool to collect data, and then contact a system administrator.

KAVB3743-I

component-name has terminated.

Terminates process management. component-name is JP1_CONS.

S:

Terminates process management.

KAVB3744-I

component-name startup has finished.

Startup of the service was completed. component-name is JP1_CONS.

S:

Continues processing.

KAVB3745-I

The component-name startup request has finished.

The startup request was completed. component-name is JP1_CONS.

S:

Continues processing.

KAVB3752-E

An attempt to start managed-process-name has finished. (return code = return-code, detail code = request-code)

An attempt to start the managed process failed. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB3760-I

The changes to file-name were not applied.

The changes to the settings in the extended startup process definition file (jp1co_service.conf) were not accepted.

S:

Continues processing.

O:

Revise the settings, and then retry the operation.

KAVB3761-E

In the file file-name, the restart-or-not value is invalid. ( restart-or-not = setting)

The restart-or-not value specified in the extended startup process definition file (jp1co_service.conf) is invalid.

S:

Continues processing.

O:

Revise the setting, and then retry the operation.

KAVB3762-I

Set 0 or 1 for the restart-or-not value.

Specify 0 or 1 for the restart-or-not value set in the extended startup process definition file (jp1co_service.conf).

S:

Continues processing.

O:

Specify 0 or 1 for the restart-or-not value.

KAVB3763-E

In the file file-name, the number-of-restarts value is invalid. (restart num. = setting)

The number-of-restarts value specified in the extended startup process definition file (jp1co_service.conf) is invalid.

S:

Continues processing.

O:

Revise the setting, and then retry the operation.

KAVB3764-I

Set 0 to 99 for the number-of-restarts value.

Specify a value between 0 and 99 for the number-of-restarts value set in the extended startup process definition file (jp1co_service.conf).

S:

Continues processing.

O:

Specify a value between 0 and 99 for the number-of-restarts value.

KAVB3765-E

In the file file-name, the restart interval value is invalid. (restart interval = setting)

The restart interval value specified in the extended startup process definition file (jp1co_service.conf) is invalid.

S:

Continues processing.

O:

Revise the setting, and then retry the operation.

KAVB3766-I

Set 0 to 3600 for the restart interval value.

Specify a value between 0 and 3,600 for the restart interval value set in the extended startup process definition file (jp1co_service.conf).

S:

Continues processing.

O:

Specify a value between 0 and 3,600 for the restart interval value.

KAVB3767-E

In the file file-name, the restart-count reset time is invalid. (restart-count reset time = setting)

The restart-count reset time specified in the extended startup process definition file (jp1co_service.conf) is invalid.

S:

Continues processing.

O:

Revise the setting, and then retry the operation.

KAVB3768-I

Set 3600 to 2147483647 for the restart-count reset time.

Specify a value between 3,600 and 2,147,483,647 for the restart-count reset time set in the extended startup process definition file (jp1co_service.conf).

S:

Continues processing.

O:

Specify a value between 3,600 and 2,147,483,647 for the restart-count reset time.

KAVB3769-I

In file-name, check the entries: process-name|path|startup-option|restart-or-not|number-of-restarts|restart-interval|restart-count-reset-time|

Check the entries in the extended startup process definition file (jp1co_service.conf).

S:

Continues processing.

O:

Check the entries in the extended startup process definition file.

KAVB3777-I

component-name: The stopped managed-process-name will be restarted. (restart count = restart-count)

The stopped managed-process-name will be restarted. component-name is JP1_CONS. The managed process name is the process name that constitutes each component managed by process management.

S:

Restarts the managed process.

KAVB3778-I

component-name: A startup request was sent to the process managed-process-name.

A startup request was sent to the managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

KAVB3779-I

component-name: An attempt to send a startup request to the process managed-process-name failed.

An attempt to send a startup request to a managed process failed. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

KAVB3786-E

To process child-process-ID-of-managed-process, the system sent the signal signal-name.

The signal is sent to the child process of the managed process. child-process-ID-of-managed-process is the process ID of the process generated by the running managed process.

S:

Continues processing.

KAVB3788-E

component-name: The number of restarts of managed-process-name exceeded the specified restart count.

The number of restarts of the managed process exceeded the specified value. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.

S:

Continues processing.

O:

Refer to the integrated trace log output by the managed process that stopped abnormally, and remove the cause of the problem. Execute the jxx_spmd_status command to check the status, and then restart process management. jxx is jco. If there is no message output by the managed process, use the data collection tool to collect data, and then contact a system administrator.

KAVB3802-W

The process manager will not be monitored because an attempt to initialize the health check function failed.

Process management will not be monitored because initialization of the health check function failed.

S:

Continues processing.

O:

To use the health check function to monitor process management, restart process management.

KAVB3828-E

A system error occurred during startup of product-name.

A system error occurred during startup of product-name.

S:

Suspends processing.

O:

Check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as available memory or file descriptors, and then restart JP1/IM - Manager.

In Windows: Windows event log

In UNIX: System log (syslog)

If restarting JP1/IM - Manager does not resolve the problem, collect JP1/IM data, and then contact a system administrator.

KAVB3840-E

The product information could not be acquired because there was not enough memory. (Detailed information: function-name, return-value)

Acquisition of product information failed due to insufficient resources.

S:

Suspends processing.

O:

Make sure that sufficient system resources are allocated.

Resolve the resource insufficiency, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB3841-E

The product information could not be acquired because the environment is invalid. (Detailed information: function-name, return-value)

An attempt to acquire product information failed due to an invalid environment.

S:

Suspends processing.

O:

Determine whether a system error occurred.

Uninstall the program, re-install it, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB3846-I

component-name completed the reload request.

Reload processing was completed. component-name is JP1_CONS.

S:

Continues processing.

KAVB3855-I

The process managed-process-name will be terminated by SIGKILL. (process ID = process-ID)

SIGKILL was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the running managed process.

S:

Continues processing.

KAVB3862-E

component-name: No processes could be started.

No managed processes could be started. component-name is JP1_CONS.

S:

Terminates process management.

O:

Make sure that sufficient system memory is allocated. Also make sure that the product is correctly installed.

KAVB3863-E

component-name: No processes can be reloaded.

No managed processes were ready to be reloaded. component-name is JP1_CONS.

S:

Continues processing.

O:

Wait awhile, and then retry the operation.

KAVB3870-E

The conf directory path cannot be obtained from the common definition.

The conf directory path could not be obtained from the common definition.

S:

Terminates the process management command.

O:

The common definition information has not been specified. Make sure that the settings are correct.

If operating in a cluster environment

Make sure that the logical host of the argument specified by the process management command is correct. Also make sure that the logical host specified by the JP1_HOSTNAME environment variable is correct.

If not operating in a cluster environment

Determine whether the JP1_HOSTNAME environment variable was specified and the process is running. If the JP1_HOSTNAME environment variable was not specified, perform the following operation to recover from the error.

• In Windows:

Perform overwrite installation.

• In UNIX:

Execute the jp1cc_setup or jp1cs_setup command.

KAVB3871-E

The conf directory path cannot be obtained by using the specified logical hostname.

The conf directory path could not be obtained from the common definition using the specified logical host name.

S:

Terminates the process management command.

O:

Use of a cluster system is a precondition. Make sure that the specified logical host name is correct and that setup was completed normally.

KAVB3872-E

The log directory path cannot be obtained from the common definition information.

The log directory path could not be obtained from the common definition.

S:

Terminates the process management command.

O:

If a cluster system is used:

Make sure that the specified logical host name is correct and that setup has completed normally.

If a cluster system is not used:

Perform the following operation for recovery.

• In Windows:

Perform corrective installation.

• In UNIX:

Execute the setup command.

KAVB3873-E

The log directory path cannot be obtained by using the specified logical hostname.

The log directory path could not be obtained from the common definition using the specified logical host name.

S:

Terminates the process management command.

O:

Use of a cluster system is a precondition. Make sure that the specified logical host name is correct and that setup was completed normally.

KAVB3874-E

HNTRLib could not be initialized.

HNTRLib2 could not be initialized. A log is not output.

S:

Continues processing.

O:

If process management is running, stop process management, and then restart it.

KAVB3875-E

HNTRLib could not be initialized.

HNTRLib2 could not be initialized. A log is not output.

S:

Continues processing.

O:

If process management is running, stop process management, and then restart it.

KAVB3899-E

The work directory path cannot be acquired from the common definition information. (Return code: return-code)

The work directory path could not be acquired from the common definition.

S:

Terminates the process management command.

O:

If operating in a cluster environment, make sure that the logical host name setting is correct and that setup was completed normally. If not operating in a cluster environment, perform the following operation to recover from the error.

• In Windows:

Perform corrective installation.

• In UNIX:

Execute the setup command.

KAVB3905-I

A stop request was sent to the process managed-process-name. (process ID = process-ID)

A stop request was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the running managed process.

S:

Continues processing.

KAVB3908-I

A reload request was sent to the process managed-process-name. (process ID = process-ID)

A reload request was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. The process ID is process-ID of the running managed process.

S:

Continues processing.

KAVB3910-I

SIGTERM will terminate the process managed-process-name. (process ID = process-ID)

SIGTERM was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. The process ID is process-ID of the running managed process.

S:

Continues processing.

KAVB3911-E

The process management daemon is busy.

The command is being processed.

S:

Terminates the process management command.

O:

Wait awhile, and then retry the operation. If this message is output when the jxx_spmd, jxx_spmd_stop, or jxx_spmd_reload command was executed during startup, stop, or reload processing, wait until processing finishes, and then retry the operation. jxx is jco.

KAVB3912-I

The process is running.

S:

Terminates the process management command.

KAVB3913-I

The process is not running.

S:

Terminates the process management command.

KAVB3914-E

An attempt to open the lock file under the conf directory has failed.

The lock file of the conf directory could not be opened.

S:

Terminates the process management command.

O:

Make sure that the conf directory exists and that there is write permission for it.

If operating in a cluster environment, make sure that the defined conf directory exists and that there is write permission for it.

KAVB3915-E

An error exists in the parameter-name.

An error exists in the communication encryption function (SSL communication).

S:

Terminates the process management command.

O:

Determine whether the file or directory of the parameter displayed can be accessed.

Also check the following settings of the communication encryption function (SSL communication).

Is the value of the ENABLE parameter 0 or 1?

Has a pass phrase been set up in the file specified by the PRIVATEKEYFILE parameter?

Is the certificate CSR specified by the CERTIFICATEFILE parameter issued by the private key specified by the PRIVATEKEYFILE parameter?

Is the version of the SSL communication specified by the SSLPROTOCOL parameter correct?

Is the encryption suite specified by the SSLCIPHERS parameter correct?

Is the service specified by the BASESSL parameter correct?

If jp1imcmda has been specified as the BASESSL parameter, have values been set for the PRIVATEKEYFILE, CERTIFICATEFILE, and SSLPROTOCOL parameters?

KAVB3916-I

SSL communication is enabled.

KAVB3917-I

SSL communication is disabled.

KAVB3918-E

Initialization of SSL communication failed. (maintenance-information)

Initialization of SSL communication failed.

S:

Suspends the process management command.

O:

An error might exist in the communication encryption function (SSK communication), or there might be a severe shortage of OS resources or available memory.

KAVB3935-E

create_pre_process_entry: Memory allocation failed. (request-code)

An attempt to create a startup preprocessing management table failed. Startup preprocessing is not performed.

S:

Continues processing.

O:

Determine whether a memory shortage occurred.

KAVB3960-I

Startup preprocessing is being performed.

Process management is performing startup preprocessing.

S:

Terminates the process management status notification command.

KAVB3961-E

The request could not be accepted because startup preprocessing is being performed.

Process management could not accept a command request because process management is performing startup preprocessing.

S:

Terminates the process management command.

O:

Wait awhile, and then retry the operation.

KAVB3981-I

jxx_spmd_stop -job: A request to stop job restrictions will be sent to all processes of component-name.

A request to stop job restrictions will be sent to all managed processes. jxx is jco. component-name is JP1_CONS.

S:

Continues processing.

KAVB3984-I

A request to stop job restrictions has been sent to the process managed-process-name. (process ID = process-ID)

A request to stop job restrictions was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the running managed process.

S:

Continues processing.

KAVB3986-I

Processing to stop component-name job restrictions has started.

Processing to stop job restrictions of process management will start. component-name is JP1_CONS.

S:

Terminates the process management command.

2.6 Messages related to automated actions and Event Base Service (KAVB4001 to KAVB6000)

KAVB4001-W

Cannot open specified file (file-name). : system-error-message

The file cannot be opened. There may be no access permission for the specified file.

S:

Stops processing for the specified file.

O:

Take the corrective action given for the system error message.

KAVB4002-W

Event Server cannot be connected.

The event server is not running or has stopped.

S:

Attempts to reconnect to the event server.

O:

Restart the event server.

KAVB4003-I

Event Server is connected.

The event server is connected successfully.

KAVB4004-E

An invalid logical host name(logical-host-name) is specified.

The JP1_HOSTNAME environment variable or the logical host name specified by the -h option is incorrect.

S:

Aborts processing.

O:

Correct the JP1_HOSTNAME environment variable or the setting of the -h option of the command, and then retry the operation.

KAVB4005-W

No Logical Host Name is specified.

No logical host name is specified for the JP1_HOSTNAME environment variable.

S:

Continues processing using the default logical host name.

O:

If a logical host name must be specified, specify an environment variable, and then retry the operation.

KAVB4006-W

An illegal option(-option) was specified.

An invalid option was specified.

S:

Ignores the specified option value and continues processing.

O:

Correct the option setting, and then retry the operation.

KAVB4007-W

No value is specified for option (-option).

No value is specified for an option that requires a value.

S:

Aborts command processing.

O:

Correct the option setting, and then retry the operation.

KAVB4008-W

Extra argument(S) exist.

Extra argument(s) are specified.

S:

Aborts processing.

O:

Correct the argument(s), and then retry the operation.

KAVB4009-W

Invalid value for option(-specified-option).

There is an error in the value of the specified option.

S:

Aborts command processing.

O:

Correct the option value, and then retry the operation.

KAVB4010-W

Option(-specified-option) appears twice or more.

The same option is specified more than once.

S:

Ignores the specified option and continues processing.

O:

Correct the option value, and then retry the operation.

KAVB4011-W

An invalid option combination exists.

Options that cannot be specified at the same time are specified.

S:

Ignores the specified options and continues processing.

O:

Specify the options correctly.

KAVB4012-W

An invalid host name is specified for the JP1_HOSTNAME environment variable.

The logical host name specified for the JP1_HOSTNAME environment variable exceeds 255 bytes, or the logical host name is not specified in the command definition as a logical host.

S:

Aborts processing.

O:

Correct the JP1_HOSTNAME environment variable setting, and then retry the operation.

KAVB4013-I

Filtering will be performed according to the event acquisition filter.

Filtering is performed according to the event acquisition filter.

KAVB4014-I

The event acquisition filter definition file was read. The read definitions will be used for processing from the next received event. (filter name = filter-name, last received event = arrival-time, serial number in event DB = serial-number-in-event-DB)

The event acquisition condition definition file was read by the jcochfilter command or an operation from JP1/IM - View. For events subsequent to the event indicated by the displayed serial number in the event database, event acquisition processing is performed according to the read definition information. If the event infrastructure service has not received an event, hyphens (--) are displayed in place of the event arrival time and serial number.

KAVB4015-W

An essential option (essential-option) is not specified.

A required option is not specified.

S:

Terminates processing.

O:

Specify the option correctly, and then retry the operation.

KAVB4016-W

The function-name is enabled, but a prerequisite function is disabled. To use the function-name, enable its prerequisite functions. (prerequisite functions: prerequisite-function-name-list)

The function is enabled, but a prerequisite function is disabled. To use the enabled function, enable its prerequisite functions.

S:

Terminates processing.

O:

To use the function indicated in the message, enable its prerequisite functions.

KAVB4020-W

Failed to get Common Defined Information(information-name). : maintenance-information

An attempt to acquire the displayed common definition information failed.

S:

Continues processing using the default value.

O:

Correct the value of the common definition information, and then retry the operation.

KAVB4021-W

File name is too long.

The full name of the file is 256 bytes or longer because the installation path or the directory or file name specified in the command definition is too long.

S:

Assumes that there is no file and continues processing.

O:

Shorten the installation path, and then re-install JP1/IM - Manager, or shorten the specified value in the command definition.

KAVB4022-E

No executing permission

There is no permission to execute the command.

S:

Aborts processing.

O:

Log in as a user with execution permission, such as an administrator, and then retry the operation.

KAVB4023-W

An invalid value is specified for common definition information.(common-definition-name=value)

A common definition information setting is incorrect.

S:

Continues processing using the default value.

O:

Correct the common definition information value, and then retry the operation.

KAVB4024-I

regular-expression-method(unique-to-JP1-or-extended-normal-expression) will be used for the regular expression.

The regular expression method fetched as the command definition information will be output.

KAVB4026-E

The argument value (argument) of the option (option) is invalid.

The argument value of the option is not correct.

S:

Terminates processing.

O:

Specify the value of the option correctly.

KAVB4027-E

The same action ID is specified for -on and -off. (action ID = action-ID)

The same action ID is specified in the -on and -off options of the jcachange command.

S:

Terminates processing.

O:

Specify the value of the option correctly.

KAVB4028-E

The specified action ID is not defined in the action definition file. (action ID = action-ID)

S:

Terminates processing.

O:

Check the action definition file and specify an action ID that is defined in the file.

KAVB4029-E

The condition for executing the action is not defined. (file = file-name)

The action execution condition cannot be enabled or disabled because it is not defined.

S:

Terminates processing.

O:

Specify the action execution condition in the action definition file.

KAVB4050-I

Automatic Action was started. : logical-host-name

Automated action processing will start.

S:

Subsequent events are subject to automated action processing. However, subsequent events are not processed when the system switching function is used.

KAVB4051-I

Automatic Action was terminated. : logical-host-name

Automated action processing will end.

S:

Stops automated action processing.

KAVB4052-I

Reading Action Definition File(automated-action-definition-file-name).

The automated action definition file will be reloaded because the jcachange command was executed.

S:

Reloads the automated action definition file and operates according to the displayed automated action definition file information.

KAVB4053-I

Suspended Automatic Action.

Automated action is suspended due to the specification of the -n option of the jcachange command. Automated action is also suspended if the loaded automated action definition file does not contain any valid action definitions.

S:

Suspends execution of the automated action.

KAVB4054-E

Automatic Action was terminated abnormally. (Hostname : host-name)

The automated action of the host (host-name) ended abnormally due to an error that prevents the automated action from continuing.

O:

On the host where automated action ended abnormally, collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4055-I

The action definition file was read and the automatic action function status was changed to operating. The processing will be based on the definitions read from the subsequently received (arrival-time-of-most-recently-processed-event (YYYY/MM/DD HH:MM:SS)) events. (Definition=total-number-of-effective-definitions/total-number-of-definitions-in-file, SEQNO=serial-number-of-most-recently-processed-event)

The automated action definition file was read by the jcachange command, or the automated action function was placed in operating status. For events subsequent to the event indicated by the displayed serial number in the event database, action processing is performed according to the read action information.

If the automated action function has not received an event, hyphens (--) are displayed in place of the event arrival time and serial number.

KAVB4056-I

Automatic action was suspended. Automatic actions cannot be executed for the subsequently received (arrival-time-of-most-recently-processed-event (YYYY/MM/DD HH:MM:SS)) events. (SEQNO=serial-number-of-most-recently-processed-event)

Automated action is suspended due to the specification of the -n option of the jcachange command. For events subsequent to the event indicated by the displayed serial number in the event database, action processing is performed.

If the automated action function has not received an event, hyphens (--) are displayed in place of the event arrival time and serial number.

S:

Suspends execution of the automated action for subsequent events

KAVB4057-I

The event base service was connected.

Event Base Service was connected from Automatic Action Service.

KAVB4058-E

An attempt to connect to the event base service failed.

An attempt to connect to Automatic Action Service from Event Base Service failed.

S:

Stops waiting for a connection from Event Base Service and continues processing.

O:

Execute the jco_spmd_status command to determine whether Event Base Service is running. If it is running, Automatic Action Service may be waiting for a connection because startup processing of Event Base Service is taking a long time. Carefully review the retry setting of Event Base Service. If a connection cannot be made after the retry setting is changed, or if Event Base Service is not running, collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4059-I

The event base service was disconnected.

The Connection between Automatic Action Service and Event Base Service was ended.

S:

Does not accept further action requests from Event Base Service.

KAVB4060-E

An attempt to receive an action request from the event base service failed. :(Last SEQNO: serial-number-that-Automatic-Action-Service-most-recently-received-from-Event-Base-Service)

An attempt to receive an action request from Event Base Service failed.

S:

Ends the connection with Event Base Service and does not accept action requests until the next time Event Base Service is connected.

O:

Collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4101-W

Action Definition file (file-name) does not exist.

There is no automated action definition file.

S:

Suspends processing of the automated action definition file.

O:

Correct the error, and then retry the operation.

KAVB4120-W

Invalid Event AND condition. (line: line-number, file: file-name)

An event AND condition is specified at the beginning of the line or for an invalid action definition. Another possibility is that a blank space is missing following the description of the event AND condition.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4121-W

Action Definition file (file-name) ends with Continuation character.

The automated action definition file ends with a continuation character (\).

S:

Ignores the automated action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4122-W

Length of parameter exceeds maximum-length bytes. (line: line-number, file: file-name)

The length of the parameter (including the continuation character (\)) of the action definition exceeded the maximum length in bytes.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4123-W

Invalid Parameter Group Number. (line: line-number, file: file-name)

The parameter group number of the action definition is other than 0 to 9, or a blank space is missing after the description of the parameter group number.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4124-W

Cannot specify Event AND Condition when Parameter Group Number is specified. (line: line-number, file: file-name)

Both a parameter group number and an event AND condition are specified for the action definition.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4125-W

Invalid Event ID. (line: line-number, file: file-name)

There is no description of the event ID of an action definition, or the description is incorrect, or a blank space is missing after the description of the event ID.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4126-W

Invalid character specified. (line: line-number, file: file-name)

An invalid character is specified for the action definition.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4127-W

Invalid regular expression. (line: line-number, file: file-name)

There is an error in the description of the regular expression of the action definition.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4128-W

Punctuation mark(S) (:) not specified. (line: line-number, file: file-name)

The action cannot be checked because no colon (:) is specified.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4129-W

Action not specified. (line: line-number, file: file-name)

A user name, environment variable file name, or execution host or group name is specified, but an action is not specified.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4130-W

Invalid User Name. (line: line-number, file: file-name)

The description of the user name is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4131-W

Invalid Environment File name. (line: line-number, file: file-name)

The description of the environment variable file name is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4132-W

Invalid Execution Host or Group. (line: line-number, file: file-name)

The description of the execution host or group name is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4133-W

More than 10 event AND conditions are specified in Action Definitions. (line: line-number, file: file-name)

An event AND condition is specified for more than 10 action definitions.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4134-W

There is no effective Action Definition for the Action Definition File. (file: file-name)

There is no effective action definition in the automated action definition file.

S:

Continues processing without setting the automated action definition.

O:

Correct the error, and then retry the operation.

KAVB4135-W

Invalid Severity of Event Extended Attribute. (line: line-number, file: file-name)

In an action definition, there is an error in the specification of the severity level of an extended event attribute.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4136-W

More than 100 Event Extended Attributes are specified. (line: line-number, file: file-name)

More than 100 extended event attributes are specified for one action definition.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4137-W

Invalid Event Extended Attribute Name. (line: line-number, file: file-name)

The specification of an extended event attribute name is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4138-W

Invalid Event Extended Attribute Value. (line: line-number, file: file-name)

The specification of an extended event attribute name is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4139-W

The version of the action definition file is invalid. (line: line-number, file: file-name)

The version information is incorrect.

S:

Assumes that the version of the automated action definition file is 2 and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4140-W

The location of the action status monitoring parameter is invalid. (line: line-number, file: file-name)

The location of the description of the automated action status monitoring parameter is incorrect.

S:

Ignores the automated action status monitoring parameter at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4141-W

The action status monitoring parameter is invalid. (line: line-number, file: file-name)

The description of the automated action status monitoring parameter is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4142-W

The suppression time is invalid. (line: line-number, file: file-name)

The description of the suppression time is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4143-W

The delay monitoring time is invalid. (line: line-number, file: file-name)

The description of the delay monitoring time is incorrect.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4144-W

The location of the action definition file version is invalid. (line: line-number, file: file-name)

The location of the description of the automated action definition file version is incorrect.

S:

Ignores the version of the automated action definition file at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4145-W

The Suppression Time cannot be specified because event AND conditions are specified. (line: line-number, file: file-name)

The suppression time is specified for the action definition where the event AND condition is specified.

S:

Ignores the action definition specified for the event AND condition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB4146-W

The length of Action parameter exceeds maximum-length bytes. (line: line-number, file: file-name)

The length of the action parameter of the action definition exceeds maximum-length bytes.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error in the relevant line in the action definition file.

KAVB4147-W

The length of the event monitoring condition parameter exceeds maximum-length bytes. (line = line-number, file = file-name)

The length of the parameter that can be specified for the event monitoring condition of the automated action definition parameter exceeds maximum-length bytes.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error in the relevant line in the action definition file.

KAVB4148-E

The action ID is duplicated. (action ID = action-ID)

The same action ID is specified more than once.

S:

Does not update the action definition file.

O:

Change the duplicate action ID, and then retry the operation.

KAVB4150-W

Failed to read data from Action Information file (file-name). : system-error-message

An attempt to acquire data from the action information file failed.

S:

Aborts processing of the action information file.

O:

Take the corrective action given for the system error message.

KAVB4151-W

Failed to write data to Action Information file (file-name). : system-error-message

An attempt to write data to the action information file failed.

S:

Aborts processing of the action information file.

O:

Take the corrective action given for the system error message.

KAVB4152-I

Information for an unfinished action was erased.

Data was overwritten because the capacity of the action information file reached the upper limit. The data for the unfinished action in the action information file prior to overwriting was deleted.

S:

Overwrites data. Actions for which information was deleted are not re-executed when system switching occurs.

O:

Carefully review the capacity of the action information file.

KAVB4153-E

Failed to open Action Information File(action-information-file-name). : system-error-message

An attempt to open the specified action information file failed.

S:

Terminates the process where the error occurred.

O:

Take the corrective action given for the system error message.

KAVB4154-E

Specified file(action-information-file-name) is not Action Information File.

The file specified by the argument of the common definition or the command is not an action information file, or the file is corrupted.

S:

Terminates the process where the error occurred.

O:

Specify the correct action information file, or re-create the action information file.

KAVB4155-E

The version of the action definition file is invalid. (line: line-number, file: file-name)

The action definition could not be enabled or disabled because DESC_VERSION is less than 4.

S:

Aborts updating of the action definition file.

O:

Make sure that DESC_VERSION in the automated action definition file is set to 4.

When DESC_VERSION is set to 1, 2, or 3, use the jcadefconv command to change to an action definition with DESC_VERSION of 4.

KAVB4180-W

Failed to open Action Host Name file (file-name). : system-error-message

An attempt to open the action host name file failed.

S:

Does not back up the action and host name to the action host name file.

O:

Take the corrective action given for the system error message.

KAVB4181-W

Failed to write data to Action Host Name file (file-name). : system-error-message

An attempt to write data to the action host name file failed.

S:

Aborts processing of the action host name file.

O:

Take the corrective action given for the system error message.

KAVB4182-W

Failed to read data from Action Host Name file (file-name). : system-error-message

An attempt to acquire data from the action host name file failed.

S:

Aborts processing of the action host name file.

O:

Take the corrective action given for the system error message.

KAVB4250-E

Cannot connect with Command Control because the logical host name could not be obtained. : maintenance-information

A connection could not be made to command control because the logical host name could not be obtained.

S:

Terminates the process where the error occurred.

O:

Specify the correct logical host name.

KAVB4251-E

Error that prevented processing occurred in Command Execution. : maintenance-information

Processing cannot continue because an error occurred while (re)connecting to command execution.

S:

Terminates the process where the error occurred.

O:

Check the status of command execution, and take the corrective action given.

KAVB4252-I

Established connection with Command Execution.

A connection with command execution has been made.

KAVB4253-W

Failed to connect with Command Execution. : maintenance-information

An attempt to connect to command execution failed.

S:

Attempts to reconnect to command execution.

O:

Check for the errors indicated below and then take the appropriate corrective action. Then, check the status of command execution. If command execution is not running, start it.

If you are using the communication encryption function, check for errors in the function settings.

KAVB4254-E

Failed to initialize communication Infrastructure. : maintenance-information

An attempt to initialize the communication infrastructure failed.

S:

Terminates the process where the error occurred.

O:

Check the settings file, and take the corrective action given.

KAVB4350-W

Error occurred in Environment File(environment-variable-file-name). : system-error-message

An error occurred during operation of the environment variable file when an attempt was made to execute an action related to transition.

S:

Does not execute the action and continues processing.

O:

Refer to the system error message to resolve the error.

KAVB4400-E

The run time of an action for an event exceeded the action delay monitoring time.(Event_ID=event-ID, SEQNO=serial-number-in-event-database, Execution Host=action-execution-host, Action Serial Number=action-serial-number) Delay monitoring notifications will not be sent until suppression of the function for sending notifications to the action delay monitor is canceled.

The monitoring time elapsed, but the monitored action did not end.

S:

Executes the notification function.

O:

Check the settings of the target action to determine whether the monitoring time for the action is appropriate.

If the monitoring time is not appropriate, specify an appropriate monitoring time.

If the monitoring time is appropriate, the action is delayed. Take corrective action.

KAVB4401-I

Suppression of the function for sending notifications to the action delay monitor was canceled.

Suppression of the function for sending notifications to the action delay monitor was canceled.

S:

Executes the notification function when the action monitoring time elapses.

KAVB4402-E

An event status is abnormal.(event ID = event-ID, event serial number = serial-number-in-event-database, execution host = action-execution-host, action serial number = action-serial-number) Status monitoring notifications will not be sent until suppression of the function for sending notifications to the action status monitor is canceled

The action was placed in Fail or Error status.

S:

Executes the notification function.

O:

The target action cannot be executed. Remove the cause of the problem, and then retry the action.

KAVB4403-I

Suppression of the function for sending notifications to the action status monitor was canceled.

Suppression of the function for sending notifications to the action status monitor was canceled.

S:

Executes the notification function when an action is placed in abnormal status.

KAVB4404-E

Although the run time of an action exceeded the action delay monitoring time, an action delay notification event could not be sent because no action information exists in the action information file.(action serial number = action-serial-number) Delay monitoring notifications will not be sent until suppression of the function for sending notifications to the action delay monitor is canceled.

An attempt was made to issue an action delay notification event, but the action delay notification event could not be issued because the action information file does not contain any action information.

S:

Continues processing.

O:

Determine whether the capacity of the action information file is sufficient. If it is not, re-estimate the required capacity of the action information file, and specify an appropriate capacity.

KAVB4405-E

Although an action status is abnormal, an action state notification event could not be sent because no action information exists in the action information file. Status monitoring notifications will not be sent until suppression of the function for sending notifications to the action status monitor is canceled.: maintenance-information

An attempt was made to issue an action error status notification event, but the action error status notification event could not be issued because no action information exists in the action information file.

S:

Continues processing.

O:

Determine whether the capacity of the action information file is sufficient. If it is not, re-estimate the required capacity of the action information file, and specify an appropriate capacity.

KAVB4406-W

Information about actions for delay monitoring have been overwritten in the action information file.

The monitored action was wrapped from the action information file. Therefore, notification could not be sent when the delay monitoring time elapsed.

S:

Reports that a monitored action was overwritten due to information being wrapped around the action information file.

O:

The monitored action was wrapped from the action information file. Notification cannot be sent even though this action is delayed. To check the execution status of this action, execute the jcocmdshow command.

KAVB4407-E

The definition file for automatic action notification(file-name) cannot be opened. : maintenance-information

The automatic action notification definition file cannot be opened.

S:

If starting JP1/IM - Manager, uses the default value for operation.

If executing the jco_spmd_reload command, takes over the current definition and continues processing.

O:

Check the following items, and then execute the jco_spmd_reload command.

Does the automatic action notification definition file exist?

Is access permission assigned correctly?

KAVB4408-E

There is an error in the definition file for automatic action notification(file-name). The default value will be used. (line line-number) : detailed-information

The default value is used for operation because an invalid value is specified in the automatic action notification definition file.

S:

If starting JP1/IM - Manager, uses the default value for operation.

If executing the jco_spmd_reload command, takes over the current definition and continues processing.

O:

Make sure that the definition file is defined correctly, and then execute the jco_spmd_reload command.

KAVB4409-E

The notification command (command) could not be executed.: maintenance-information

The notification command could not be executed.

S:

Continues processing.

O:

Make sure that the automatic action notification definition file is defined correctly, and then execute the jco_spmd_reload command.

KAVB4420-W

Cannot execute action because substrings could not be obtained. (line: line-number) : maintenance-information

The action corresponding to line-number in the automated action definition file could not be executed because an attempt to obtain substrings failed.

S:

Does not execute the action.

O:

Check the contents of the automated action definition file.

KAVB4421-W

Cannot execute action because command line is too long. (line: line-number) : maintenance-information

The action corresponding to line-number in the automated action definition file could not be executed because the command line was too long.

S:

Does not execute the action.

O:

Check the contents of the automated action definition file.

KAVB4422-W

Cannot execute action because the host name could not be obtained. (line: line-number) : maintenance-information

The action corresponding to line-number in the automated action definition file could not be executed because the host name assigned to execute the action could not be obtained.

S:

Does not execute the action.

O:

Check the contents of the automated action definition file.

KAVB4423-W

Cannot execute action because Command Execution is not running. (line: line-number, host: host-name) : maintenance-information

The action corresponding to line-number in the automated action definition file could not be executed on the host because command execution was not running.

Note that -1 is shown in the line-number if an automated action was re-executed.

S:

Does not execute the action.

O:

Check the contents of the automated action definition file.

KAVB4424-W

Cannot execute action. (line: line-number, host: host-name) : maintenance-information

The action corresponding to line-number in the automated action definition file could not be executed on the host.

S:

Does not execute the action.

O:

Check the contents of the automated action definition file.

KAVB4425-I

Expired AND events were abandoned. (number of events: number-of-events)

Expired events were discarded because the AND event storage period elapsed.

KAVB4426-W

Cannot execute action because Execution Host or Group name is too long. (line: line-number) : maintenance-information

The action corresponding to the line number in the automated action definition file could not be executed because the execution host name/group name after conversion to the information in the received event was too long.

S:

Does not execute the action.

O:

Check the automated action definition file and the event that triggered action execution.

KAVB4427-W

Cannot execute action because User Name is too long. (line: line-number) : maintenance-information

The action corresponding to the line number in the automated action definition file could not be executed because the user name after conversion to the information in the received event was too long.

S:

Does not execute the action.

O:

Check the automated action definition file and the event that triggered action execution.

KAVB4428-W

Cannot execute action because Environment Definition File name is too long. (line: line-number) : maintenance-information

The action corresponding to the line number in the automated action definition file could not be executed because the environment variable file name after conversion to the information in the received event was too long.

S:

Does not execute the action.

O:

Check the automated action definition file and the event that triggered action execution.

KAVB4429-W

The action could not be executed because a memory shortage occurred. (line = line-number) maintenance-information

The action corresponding to line-number in the automated action definition file could not be executed because a memory shortage occurred during conversion to the information in the received event.

S:

Does not execute the action.

O:

Make sure that sufficient system memory is allocated. Also make sure that the OS is operating normally.

KAVB4430-I

Execution of the action for an event was requested.(Event_ID=event-ID, SEQNO=serial-number-in-event-database)

The action execution request was registered in the command control queue.

KAVB4431-I

Execution of the action for an event ended normally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database, Return_code=termination-code)

Execution completion notification for the action was received from command control. The status is action completed.

KAVB4432-E

Automatic action or command control of the action for an event ended abnormally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database)

Automated action or command control of the action ended abnormally and the action was placed in Error or Fail status.

KAVB4433-I

Execution of the action for an action state notification event was requested.(Event_ID=event-ID, SEQNO=serial-number-in-event-database)

The execution request of an action was registered in the command control queue.

KAVB4434-I

Execution of the action for an action state notification event ended normally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database, Return_code=termination-code)

The action was ended by an execution completion notification from command control.

KAVB4435-E

Automatic action or command control of the action for an action state notification event ended abnormally.(EVENT_ID=event-ID, SEQNO=serial-number-in-event-database)

Automated action or command control of the action ended abnormally and the action was placed in Error or Fail status.

KAVB4436-W

Although Execution of the action for an event was requested, an action state notification event could not be sent because no action information exists in the action information file. : maintenance-information

Execution of the action was requested, but an action state notification event could not be sent because the action information file does not contain any action information.

S:

Continues processing.

O:

Determine whether the capacity of the action information file is sufficient. If it is not, re-estimate the required capacity of the action information file, and specify an appropriate capacity.

If the capacity of the action information file is appropriate, there may have been a delay in execution of the action. Consider the following factors.

When more than one action is performed for one event, you can improve execution efficiency and reduce execution delay by placing those actions in one batch file (shell script) and executing the batch file.

If output to standard output or standard error that is not necessary for the action is performed, consider suppressing output. Suppressing output can improve execution efficiency and reduce execution delay.

When using the default setting to execute a command by automated action, an execution delay occurs because the next command is not executed until execution of the current command is completed. To reduce execution delay, see 12.4 Considerations for automated actions in the manual JP1/Integrated Management 2 - Manager Overview and System Design Guide for the procedure to change the setting to parallel.

KAVB4437-W

Although Execution of the action for an event ended normally, an action state notification event could not be sent because no action information exists in the action information file. : maintenance-information

Execution of the action ended, but the action state notification event could not be sent because the action information file does not contain any action information.

S:

Continues processing.

O:

Determine whether the capacity of the action information file is sufficient. If it is not, re-estimate the required capacity of the action information file, and specify an appropriate capacity.

If the capacity of the action information file is appropriate, there may have been a delay in execution of the action. Consider the following factors.

When more than one action is performed for one event, you can improve execution efficiency and reduce execution delay by placing those actions in one batch file (shell script) and executing the batch file.

If output to standard output or standard error that is not necessary for the action is performed, consider suppressing output. Suppressing output can improve execution efficiency and reduce execution delay.

When using the default setting to execute a command by automated action, an execution delay occurs because the next command is not executed until execution of the current command is completed. To reduce execution delay, see 12.4 Considerations for automated actions in the manual JP1/Integrated Management 2 - Manager Overview and System Design Guide for the procedure to change the setting to parallel.

KAVB4438-E

Although automatic action or command control of the action for an event ended abnormally, an action state notification event could not be sent because no action information exists in the action information file. : maintenance-information

Automated action or command control of the action ended abnormally, but an action state notification event could not be issued because the action information file does not contain any action information.

S:

Continues processing.

O:

Determine whether the capacity of the action information file is sufficient. If it is not, re-estimate the required capacity of the action information file, and specify an appropriate capacity.

If the capacity of the action information file is appropriate, there may have been a delay in execution of the action. Consider the following factors.

When more than one action is performed for one event, you can improve execution efficiency and reduce execution delay by placing those actions in one batch file (shell script) and executing the batch file.

If output to standard output or standard error that is not necessary for the action is performed, consider suppressing output. Suppressing output can improve execution efficiency and reduce execution delay.

When using the default setting to execute a command by automated action, an execution delay occurs because the next command is not executed until execution of the current command is completed. To reduce execution delay, see 12.4 Considerations for automated actions in the manual JP1/Integrated Management 2 - Manager Overview and System Design Guide for the procedure to change the setting to parallel.

KAVB4439-E

An attempt to write data to the action re-execution file has failed. (action serial number = action-serial-number, detailed information = detailed-information)

An attempt to write data to the action re-execution file failed.

S:

Stops writing data to the action re-execution file of the action indicated by the action serial number. Continues processing.

O:

Check the execution results of the action indicated by the action serial number, and, if necessary, retry the operation.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host: Console-path\log\action

- Logical host: shared-folder\jp1cons\log\action

In UNIX:

- Physical host: /var/opt/jp1cons/log/action

- Logical host: shared-directory/jp1cons/log/action

If the problem cannot be resolved, check the following OS log items to determine whether a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB4440-W

The action could not be executed because a host is not defined for the business group or monitoring group. (execution host name = execution-host-name)

The action could not be executed because no host was defined for the business group or monitoring group.

S:

Does not execute the action.

O:

Define a host for the specified business group or monitoring group, or carefully review the business group name or monitoring group name. Then retry the operation.

KAVB4441-W

The action could not be executed because the business group or monitoring group is not defined. (execution host name = execution-host-name)

The action could not be executed because the business group, or monitoring group was not defined.

S:

Does not execute the action.

O:

Define the specified business group or monitoring group, or carefully review the business group name or monitoring group name. Then, retry the operation.

KAVB4442-W

The action cannot be executed because the execution host name is invalid. (execution host name = execution-host-name)

The action could not be executed because the name of the execution host is invalid.

S:

Does not execute the action.

O:

Carefully review the execution host name for the action.

KAVB4443-E

The action could not be executed because a host is not defined for the business group or monitoring group. (execution host name = execution-host-name)

The action could not be executed because no host was defined for the business group or monitoring group.

S:

Does not execute the action.

O:

Carefully review the specified business group or monitoring group.

If there is no problem, check with a system administrator to see if a host is defined for the specified business group or monitoring group.

KAVB4444-E

The action could not be executed because the business group or monitoring group is not defined. (execution host name = execution-host-name)

The action could not be executed because the business group or monitoring group was not defined.

S:

Does not execute the action.

O:

Carefully review the specified business group or monitoring group.

If there is no problem, check with a system administrator to see if the specified business group or monitoring group has been defined.

KAVB4445-E

The action cannot be executed because the execution host name is invalid. (execution host name = execution-host-name)

The action could not be executed because the name of the execution host is invalid.

S:

Does not execute the action.

O:

Carefully review the execution host name for the action.

KAVB4450-E

I/O error occurred. : maintenance-information

An I/O error occurred in Automatic Action Service, Event Base Service or Event Console Service while defining an action or re-executing an action from JP1/IM - View or executing the jcastatus or jcachange command. When the above window operation or command is executed, a request for processing is sent to Automatic Action Service, Event Base Service or Event Console Service. However, because more than one window operation or command execution occurred simultaneously, each service was unable to handle processing.

When sending of a request for processing failed, execution of the command was retried. All retries failed.

S:

Aborts processing.

O:

Wait awhile, and then re-execute the command.

KAVB4451-E

Because acquisition of exclusive rights failed. action definition file cannot be updated.

The automated action definition file could not be updated because exclusive rights for the automated action definition file could not be acquired.

S:

Terminates the update processing of the automated action definition file due to competing with the reference or update operation of another user and failing to lock the automated action definition file after waiting some time.

The automated action function operates using the previous definitions.

O:

Perform the operation again.

If the problem cannot be resolved after multiple attempts, collect data then contact a system administrator.

KAVB4452-E

Because acquisition of exclusive rights failed. action definition file cannot be read.

The automated action definition file could not be read because exclusive rights for the automated action definition file could not be acquired.

S:

Terminates the read processing of the automated action definitions due to competing with the update operation of another user and failing to lock the automated action definition file after waiting some time.

If the error message is output while executing the jcachange command with -on, -off, or -e specified or while applying the Action Parameter Definitions window, the automated action definitions file was successfully updated, but reflection in the automated action function failed. The automated action function operates using the previous definitions.

O:

Perform the operation again.

If the problem cannot be resolved after multiple attempts, collect data then contact a system administrator.

KAVB4500-W

Duplicate pre-conversion characters have been specified in the configuration file for converting information during event succession. (line = line-number)

Pre-conversion characters specified in the configuration file for converting information are duplicated.

S:

Ignores duplicated definitions and continues processing.

O:

The line number indicated in the message is incorrect. Correct the error.

KAVB4501-W

An invalid pre-conversion character has been specified in the configuration file for converting information during event succession. (line = line-number)

A pre-conversion character specified in the configuration file for converting information is invalid.

S:

Ignores the invalid definition and continues processing.

O:

The line number indicated in the message is incorrect. Correct the error.

KAVB4502-W

An invalid post-conversion character string has been specified in the configuration file for converting information during event succession. (line = line-number)

A post-conversion character string specified in the configuration file for converting information is invalid.

S:

Ignores the invalid definition and continues processing.

O:

The line number indicated in the message is incorrect. Correct the error.

KAVB4503-W

The number of definitions specified in the configuration file for converting information during event succession has exceeded the maximum of maximum-number.

The number of definitions specified in the configuration file for converting information exceeds the maximum number allowed (maximum-number items).

S:

Ignores definitions beyond the maximum number allowed and continues processing.

O:

Carefully review and correct the number of definitions.

KAVB4504-W

The syntax of a definition, specified in the configuration file for converting event succession information, is invalid. (line = line-number)

A definition specified in the configuration file for converting information is invalid.

S:

Ignores the invalid definition and continues processing.

O:

The line number in the message indicates the location of the error. Correct the error.

KAVB4505-I

The configuration file for converting event succession information was read.

The configuration file for converting information was read.

KAVB4506-W

An attempt to read the configuration file for converting event succession information has failed. (cause = reason)

An attempt to read the configuration file for converting information failed.

S:

Stops reading of the configuration file for converting information and continues processing.

O:

Determine whether the configuration file for converting information can be read. If the file can be read, check the OS log to determine whether a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB4507-W

The number of common exclusion condition groups (extended) exceeds the limit. (maximum number of condition groups = maximum-number)

The number of common exclusion-condition groups defined in JP1/IM - Manager exceeds the maximum size.

S:

Continues processing with the predefined number of condition groups.

O:

Increase the maximum number of common exclusion-condition groups in extended mode or delete unnecessary condition groups.

KAVB4508-W

The size of a common exclusion condition group (extended) filter exceeds the limit. (condition group maximum size = maximum-size)

The filter size for the common exclusion-condition group defined in JP1/IM - Manager exceeds the maximum size.

S:

Continues processing with the predefined filter size.

O:

Define the condition group so that the filter size does not exceed the maximum size.

KAVB4550-W

The item cannot be specified because a rule is specified for the action. (line = line-number, file = file-name)

If an action for rule startup request is specified, you cannot specify the user name, target host name or group name, and environment variable file name.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error in the corresponding line in the action definition file.

KAVB4551-E

The rule cannot be specified for the action. (line = line-number)

You cannot specify <RULE> for the action because it is an action for rule startup request.

S:

Suspends creation of the action definition.

O:

Correct the error in the corresponding line in the action definition file.

KAVB4600-I

The severity change definition has been read. Next, processing will be performed using the definition read from the received event. (arrival time of the last received event = arrival-time, serial number in the event database = serial-number-in-event-database)

The severity changing definition file was read. For events subsequent to the event indicated by the serial number in the event database, the severity will be changed according to the contents of the read definition.

KAVB4602-W

The version information for the severity changing definition file is invalid. (line = line-number, file = file-name)

The version information of the severity changing definition file is invalid.

S:

Assumes that the version of the severity changing definition file is 2, and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4603-W

The location of the severity changing definition file version is invalid. (line = line-number, file = file-name)

The file version is not specified at the beginning of the severity changing definition file.

S:

Assumes the default file version and continues processing.

O:

Specify the file version at the beginning of the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4604-W

The name of a definition in the severity changing definition file exceeds the maximum length. (line = line-number, file = file-name)

The length of the definition name specified in the definition block exceeds the maximum length.

S:

Ignores the definition block and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4605-W

No name has been defined for the severity changing definition file. (line = line-number, file = file-name)

A definition name is not specified in the definition block.

S:

Ignores the definition block and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4606-W

The name of a definition in the severity changing definition file has been duplicated. (definition name = definition-name, line = line-number, file = file-name)

The definition name of the definition block is duplicated.

S:

Ignores the definition block that is read later and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4607-W

The invalid parameter parameter-name has been specified. (line = line-number, file = file-name)

A parameter that cannot be used is specified in the severity changing definition file. Also, a parameter is specified outside the definition block.

S:

Ignores the corresponding line and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4608-W

The syntax of a severity level change definition is invalid. cause (definition name = definition-name, line = line-number, file name = file-name)

An event condition block contains an error.

S:

Ignores the definition block and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4609-W

The syntax of a parameter is invalid. cause (definition name = definition-name, line = line-number, file name = file-name)

A parameter in the severity changing definition file is specified incorrectly.

S:

Ignores the definition block and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4610-E

An error occurred while reading the severity changing definition file (file-name): reason

An error occurred during reading of the severity changing definition file.

S:

Ignores the definition file and continues processing.

O:

Check the definition file according to the reason code in the message, and then restart JP1/IM - Manager.

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KAVB4611-E

An error occurred during severity change definition processing. (serial number in the event database = serial-number-in-event-database, arrival time = arrival-time, cause = reason)

An error occurred during severity changing definition processing.

S:

Ignores the definition file and continues processing.

O:

Take the corrective action given for the reason code in the message.

001: A severity definition that contains more than 256 bytes cannot be changed. Review the method of issuing JP1 events.

002: The total size of the extended attribute values exceeds 10,000 bytes. Review the method used for issuing JP1 events.

003: A memory shortage occurred. Check memory usage, and then restart JP1/IM - Manager. If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

255: Collect data, and then contact a system administrator.

KAVB4612-W

There is no "end-def" statement in the severity change definition block. (definition name = definition-name, line = line-number, file name = file-name)

The definition block is not closed.

S:

Ignores the definition block and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4613-W

"end-def" statement in the severity change definition block is invalid. (definition name = definition-name, line = line-number, file name = file-name)

The end of the definition block contains an error.

S:

Ignores the definition block and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4614-W

The name of a definition in the severity changing definition file is invalid. (line =line-number, file name =file-name)

The definition name of the definition block contains an error.

S:

Ignores the definition block and continues processing.

O:

Correct the error in the corresponding line in the severity changing definition file. Then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4615-E

The size of the severity changing definition file exceeds the upper limit. (file name = file-name, upper limit =maximum-size)

The size of the severity changing definition file exceeds the maximum value.

S:

Does not read the severity changing definition file and continues processing.

O:

Carefully review the severity changing definition file to determine whether it contains extra comments or redundant definitions, and reduce the file size so that it is no greater than the maximum value. After correcting the file size, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4616-E

The severity change definition was not found.

The severity changing definition file cannot be found.

S:

Does not change the severity of all JP1 events if this error occurs during startup of JP1/IM - Manager.

If the error occurs during execution of the jco_spmd_reload command, continues processing using the severity changing definition that was in effect prior to execution of the jco_spmd_reload command.

O:

Check the following items, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Determine whether a severity changing definition file exists. If a severity changing definition file does not exist, create one.

Determine whether there is read permission for the severity changing definition file. If there is no read permission, assign read permission for the file.

KAVB4620-W

A JP1 event contains an extension attribute that could not be specified. cause (serial number in the event database = serial-number-in-event-database, arrival time = arrival-time, attribute name = attribute-name)

A JP1 event contains an extension attribute that cannot be specified.

S:

Issues the JP1 event without setting the extension attribute in question.

O:

Carefully review and, if necessary, correct how the JP1 event is issued.

KAVB4621-E

An event after the display message was changed could not be issued. cause (serial number in the event database = serial-number-in-event-database, arrival time = arrival-time)

The event after a display message was changed could not be issued.

S:

Suspends issue of an event after a display message is changed.

O:

If An event service is not running. is displayed for cause, determine whether Event Service is running, and if not, start it.

If Event Service is running, use the data collection tool to collect data, and then contact a system administrator.

If A memory shortage occurred. is displayed for cause, check memory usage, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A system error occurred. is displayed for cause, collect data, and then contact a system administrator.

KAVB4622-W

An attribute that could not have "E_" added to the beginning of the attribute name during the processing to issue an event after a display message was changed exists. (serial number in the event database = serial-number-in-event-database, arrival time = arrival-time, attribute name = attribute-name)

An extension attribute that cannot have E_ added to the beginning of its name exists in the processing to issue an event after a display message is changed.

S:

Issues the JP1 event without adding E_ to the start of the name of the extension attribute in question.

O:

Carefully review and, if necessary, correct how the JP1 event is issued.

KAVB4623-I

The display message change definition has been read. Next, processing will be performed using the definition read from the received event. (arrival time of the last received event = arrival-time, serial number in the event database = serial-number-in-event-database)

A display message change definition file has been read.

S:

Changes the display message, as dictated by the definition that was read, starting after the event indicated by the serial number within the event database shown.

KAVB4624-W

The version information for the display message change definition file is invalid. (line = line-number, file = file-name)

The version information of the display message change definition file is invalid.

S:

Assumes the version information of the display message change definition file is 1 and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4625-W

The location of a display message change definition file is invalid. (line number = line-number, file = file-name)

The version of the display message change definition file is not at the beginning of the file.

S:

Assumes the default value and continues processing.

O:

Set the file version at the beginning of the display message change definition file. After setting the version, either restart JP1/IM - Manager, or execute the jco_spmd_reload command to reload it.

KAVB4626-W

The length of a definition name specified in a definition block in a display message change definition exceeds the maximum. (line number = line-number, file = file-name)

The length of a definition name specified in a definition block in a display message change definition exceeds the maximum.

S:

Ignores the definition block in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4627-W

The definition name does not exist in a definition block in a display message change definition. (line number = line-number, file = file-name)

No definition name is specified in a definition block in a display message change definition.

S:

Ignores the definition block in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4628-W

A definition name in a definition block in a display message change definition is duplicated. (definition name = definition-name, line number = line-number, file = file-name)

A definition name of a definition block in a display message change definition is duplicated.

S:

Ignores the definition block that contains the duplicate name and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4629-W

An invalid parameter is specified in a display message change definition file. (invalid parameter = parameter-name, line number = line-number, file = file-name)

A parameter that cannot be used is specified in a display message change definition file or a parameter is used outside of a definition block.

S:

Ignores the line in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4630-W

An event condition block in a display message change definition is invalid. cause (definition name = definition-name, line number = line-number, file = file-name)

An event condition block in a display message change definition is invalid.

S:

Ignores the definition block in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4631-W

A parameter in a display message change definition file is invalid. cause (definition name = definition-name, line number = line-number, file = file-name)

A parameter specification of a display message change definition file contains an error.

S:

Ignores the definition block in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4632-E

An error occurred while reading the display message change definition file. (cause = cause, file = file-name)

An error occurred while reading a display message change definition file.

S:

If this happens when JP1/IM - Manager restarts, does not change the messages of any JP1 event.

If this happens when the jco_spmd_reload command is executed, continues processing in accordance with the definition for display message change set prior to execution of the jco_spmd_reload command.

O:

Take corrective action based on the cause indicated in the message.

001: A memory shortage has occurred. Check memory usage, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

255: Collect data and then contact a system administrator.

KAVB4633-E

An error occurred during display message change definition processing. (serial number in the event database = serial-number-in-event-database, arrival time = arrival-time, cause = cause)

An error occurred in change processing for a message.

S:

Ignores the definition file and continues processing.

O:

Take corrective action based on the cause indicated in the message.

001: A memory shortage has occurred. Check memory usage, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

255: Collect data and then contact a system administrator.

KAVB4634-W

There is no "end-def" statement in the display message change definition block. (definition name = definition-name, line = line-number, file name = file-name)

A definition block in a display message change definition is not closed.

S:

Ignores the definition block in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4635-W

"end-def" statement in the display message change definition block is invalid. (definition name = definition-name, line = line-number, file name = file-name)

The end of a display message change definition block is invalid.

S:

Ignores the definition block in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4636-W

The name of a definition in the display message change definition file is invalid. (line = line-number, file = file-name)

The name of a definition in a display message change definition file is invalid.

S:

Ignores the definition block in question and continues processing.

O:

Correct the error on the line in question in the display message change definition file. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4637-E

The size of a display message change definition file exceeds the maximum (maximum). (file = file-name)

The size of a display message change definition file exceeds the maximum.

S:

Continues processing without reading the display message change definition file.

O:

Carefully review the content of the display message change definition file for unnecessary comments, redundant definitions, and the like, and then correct the file so that its size does not exceed the maximum. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4638-E

The display message change definition was not found.

The display message change definition file was not found.

S:

If there is no display message change definition file when JP1/IM - Manager restarts, does not change the messages of any JP1 event.

If there is no display message change definition file when the jco_spmd_reload command is executed, continues processing in accordance with the definition for display message change set prior to execution of the jco_spmd_reload command.

O:

Check the following, and then restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

Check whether the display message change definition file exists. If the file does not exist, create the file.

Check whether you have read permission for the display message change definition file. If not, set read permission for the file.

KAVB4639-W

The display message after the change will be truncated and then registered because its size exceeds the maximum. (serial number in the event database = serial-number-in-event-database, arrival time = arrival-time)

The display message after the change exceeds the maximum size, so the part of the message character string that exceeds the maximum size will be deleted, and then the message will be registered.

S:

Continues processing.

O:

Carefully review and, if necessary, correct how the JP1 event is issued.

KAVB4640-W

The number of display message change definition exceeds the maximum (maximum). (file = file-name)

The number of display message change definitions exceeds the maximum.

S:

Ignores the excess display message change definitions and continues processing.

O:

Delete any display message change definitions that are not needed. Then, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4641-W

Using the regular expression you specified, the processing to match JP1 events will take a long time. This will affect the performance of event reception. (attribute name = attribute-name, definition name = definition-name, line = line-number, file = file-name, cause = cause)

The regular expression you have specified will cause the processing to match JP1 events to take a while. This will affect the performance of event reception.

S:

Continues processing.

O:

Correct the regular expression that will take a while for the processing to match JP1 events.

If .* is specified at the beginning or end is displayed for cause, delete the .* specified at the beginning or end.

If .* is specified repeatedly is displayed for cause, use only one instance of .* at the location where it is repeated.

KAVB4650-I

An event-source-host mapping definition was read. Processing will be performed by the definition read from the next received event. (last received event: reception time = reception-time, event database serial number = event-database-serial-number)

The event-source-host mapping definition file was read. For events subsequent to the event indicated by the serial number in the event database, the event-source host will be mapped according to the contents of the read definition.

KAVB4651-W

The version information of the event-source-host mapping definition file is invalid. (line number = line-number, file name = file-name)

The version information for the event-source-host mapping definition file is invalid.

S:

Assumes 1 as the version information for the event-source-host mapping definition file, and continues processing.

O:

Correct the error in the event-source-host mapping definition file, and then retry the operation.

KAVB4652-W

The location of the version of the event-source-host mapping definition file is invalid. (line number = line-number, file name = file-name)

The file version is not specified at the beginning of the event-source-host mapping definition file.

S:

Assumes the default file version and continues processing.

O:

Specify the file version at the beginning of the event-source-host mapping definition file.

KAVB4653-W

The name of a definition in the event-source-host mapping definition is too long. (line number = line-number, file name = file-name)

The length of a name in the event-source-host mapping definition exceeds the maximum length.

S:

Ignores the too-long name in the event-source-host mapping definition and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4654-W

There is no definition name for an event-source-host mapping definition. (line number = line-number, file name = file-name)

The name of an event-source-host mapping definition is not specified.

S:

Ignores the event-source-host mapping definition and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4655-W

The name of a definition in the event-source-host mapping definition has been duplicated. (definition name = definition-name, line number = line-number, file name = file-name)

The name of the event-source-host mapping definition is duplicated.

S:

Ignores the event-source-host mapping definition that was read last, and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4656-W

An invalid parameter is specified. (invalid parameter = parameter-name, line number = line-number, file name = file-name)

A parameter that cannot be used is specified in the event-source-host mapping definition file, or a parameter is specified outside the definition block.

S:

Ignores the line indicated in the message and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4657-W

The syntax of an event-source-host mapping definition is invalid. cause (definition name = definition-name, line number = line-number, file name = file-name)

There is an error in the syntax of the event-source-host mapping definition file.

S:

Ignores the event-source-host mapping definition and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4658-W

The syntax of a parameter is invalid. cause (definition name = definition-name, line number = line-number, file name = file-name)

The syntax of the mapping-source attribute value in the event-source-host mapping definition is invalid.

S:

Ignores the event-source-host mapping definition and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4659-E

An error occurred during reading of the event-source-host mapping definition file. (cause = cause, file name = file-name)

An error occurred during reading of the event-source-host mapping definition file.

S:

Ignores the event-source-host mapping definition file and continues processing.

O:

Check the definition file based on the cause of the error indicated in the message, and then restart JP1/IM.

Collect data and then contact a system administrator.

KAVB4660-E

An error occurred during the mapping of the event-source-host. (event database serial number = event-database-serial-number, reception time = reception-time, cause = cause)

An error occurred during mapping of the event-source host.

S:

Continues processing.

O:

Take corrective action based on the cause indicated in the message.

Cause: 001

A memory shortage occuured. Check memory usage, and then restart JP1/IM.

Cause: 255

Collect data and then contact a system administrator.

KAVB4661-W

No "end-def" statement exists in a definition block. (definition name = definition-name, line number = line-number, file name = file-name)

The event-source-host mapping definition is not closed.

S:

Ignores the event-source-host mapping definition and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4662-W

The "end-def" statement of a definition block is invalid. (definition name = definition-name, line number = line-number, file name = file-name)

The end of the event-source-host mapping definition is invalid.

S:

Ignores the event-source-host mapping and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4663-W

The name of an event-source-host mapping definition is invalid. (line number = line-number, file name = file-name)

The name of an event-source-host mapping definition is invalid.

S:

Ignores the event-source-host mapping definition and continues processing.

O:

Correct the error in the corresponding line in the event-source-host mapping definition file.

KAVB4664-E

The size of the event-source-host mapping definition file (file-name) exceeds the limit (maximum-size).

The size of the event-source-host mapping definition file exceeds the maximum value.

S:

Continues processing without reading the event-source-host mapping definition file.

O:

Carefully review the contents of the event-source-host mapping definition file for extra comments or redundant definitions, and correct the file so that its size does not exceed the maximum value.After correcting the file, restart JP1/IM - Manager or execute the jco_spmd_reload command to reload JP1/IM - Manager.

KAVB4666-W

A host name of no more than 255 bytes can be specified for the event-source-host name. (event database serial number = event-database-serial-number, reception time = reception-time)

The host name specified for the event-source host name contains more than 255 bytes. The event-source host could not be mapped.

S:

Sets the message ID for the event-source host name and continues processing.

O:

Carefully review the method of issuing JP1 events.

KAVB4667-W

The attribute specified for the source_attr parameter was not found. (event database serial number = event-database-serial-number, reception time = reception-time, cause = cause)

The attribute value specified for the mapping-source attribute value is not found. The event-source host could not be mapped.

S:

Sets the message ID for the event-source host name and continues processing.

O:

Carefully review the mapping-source attribute value in the definition file.

KAVB4668-W

An error occurred during the mapping of the event-source-host. (event database serial number = event-database-serial-number, reception time = reception-time, cause = cause)

An error occurred during the mapping of the event-source host.

S:

Continues processing.

O:

Take corrective action based on the following cause codes.

Cause code: 001

The number of program-specific extended attribute values exceeds 100. Carefully review the method of issuing JP1 events.

Cause code: 002

The total size of extended attribute values exceeds 10,000 bytes. Carefully review the method of issuing JP1 events.

KAVB4669-E

An error occurred during reading of the system's event-source-host mapping definition file. (cause = cause, file name = file-name)

An error occurred during reading of the event-source-host mapping definition file of the system.

S:

Ignores the contents of the system's event-source-host mapping definition file and continues processing.

O:

Contact a system administrator.

KAVB4670-W

No more repeated events can be suppressed because the number of suppressed repeated events has reached the maximum (maximum-number).

The number of suppressed repeated events has reached the maximum.

S:

Continues processing.

KAVB4671-E

The repeated event condition exceeds the maximum length (maximum-length).

No more definitions can be added because the repeated event condition has reached the maximum size.

S:

Waits for re-entry of information.

O:

Delete unnecessary definitions in the repeated event condition.

KAVB4672-I

The repeated event monitoring suppression function was enabled.

The repeated event monitoring suppression function was enabled.

KAVB4673-I

A repeated event condition was registered. (repeated event condition name = repeated-event-condition-name, registering user = user-name)

An additional repetition event condition was registered.

KAVB4674-I

The definition file for the repeated event condition was updated. Next, processing will be performed using the definition read from the received event. (arrival time of the last received event = arrival-time-of-the-last-received-event, serial number in the event database = serial-number-in-the-event-database)

This message is output when a repeated event condition is updated.

KAVB4675-W

Prerequisite functionality for the repeated event monitoring suppression function is not enabled. (cause = cause)

To use the repeated event monitoring suppression function, enable the event storage function.

S:

Continues processing.

O:

Take corrective action based on the message displayed for cause.

The integrated monitoring database is currently disabled.

Use the jcoimdef command to enable the event storage function, and then restart JP1/IM.

KAVB4676-I

Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) has started. (arrival time of the first suppressed event = arrival-time-of-the-first-suppressed-event, event database serial number of the first suppressed event = event-database-serial-number-of-the-first-suppressed-event)

Suppression of the repeated events that match the repeated event condition has started.

KAVB4677-I

Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) has ended. (arrival time of the suppressed event = arrival-time-of-the-first-suppressed-event(YYYY/MM/DD HH:MM:SS) - arrival-time-of-the-last-suppressed-event(YYYY/MM/DD HH:MM:SS), event database serial number of the suppressed event = event-database-serial-number-of-the-first-suppressed-event - event-database-serial-number-of-the-last-suppressed-event)

Suppression of the repeated events that match the repeated event condition has ended.

KAVB4678-I

Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) has terminated. (arrival time of the suppressed event = arrival-time-of-the-first-suppressed-event(YYYY/MM/DD HH:MM:SS) - arrival-time-of-the-last-suppressed-event(YYYY/MM/DD HH:MM:SS), event database serial number of the suppressed event = event-database-serial-number-of-the-first-suppressed-event - event-database-serial-number-of-the-last-suppressed-event)

Suppression of the repeated events that match the repeated event condition was canceled, and then suppression was started again.

KAVB4679-I

Suppression of repeated events that match the repeated event condition (repeated-event-condition-name) will continue. (arrival time of the suppressed event = arrival-time-of-the-first-suppressed-event(YYYY/MM/DD HH:MM:SS) - arrival-time-of-the-last-suppressed-event(YYYY/MM/DD HH:MM:SS), event database serial number of the suppressed event = event-database-serial-number-of-the-first-suppressed-event - event-database-serial-number-of-the-last-suppressed-event)

Suppression of the repeated events that match the repeated event condition continues.

KAVB4700-I

The event base service was started. : logical-host-name

Event Base Service was started.

KAVB4701-I

The event base service was terminated. : logical-host-name

Event Base Service was stopped.

S:

Stops executing automated action processing and event distribution processing.

KAVB4702-E

The event base service was terminated abnormally. (Hostname : host-name)

Event Base Service of the host (host-name) was stopped abnormally due to an error that prevents the service from continuing.

O:

Check the integrated trace log to see if a KAVB4780-E, KAVB8605-E, KAVB8606-E, or KAVB8607-E message was output. If a message was output, take the corrective action given for that message.

If no message was output, collect JP1/Base and JP1/IM data on the host where Event Base Service stopped abnormally, and then contact a system administrator.

KAVB4703-E

Failed to read the event acquisition filter definition file. (File name : file-name)

An attempt to read the event acquisition filter definition file during startup of JP1/IM - Manager failed.

S:

Terminates processing.

O:

Check the following items:

Is there a displayed file?

If not, use the definition file creation procedure described below to create a file.

Does the displayed file have administrator (in Windows) or root (in UNIX) read and write permissions?

If permissions are not assigned, assign them.

If the problem is other than the above, the definition file may be corrupted. Use the definition file creation procedure to create a file.

To create a definition file:

Execute the jco_spmd_status command to determine whether JP1/IM - Manager has stopped.

If the event acquisition filter definition file is backed up, restore the file, and then restart JP1/IM - Manager.

If the event acquisition filter definition file is not backed up, use the following procedure to restore the event acquisition filter (the filter that acquires events other than JP1/SES events) to initial status. Then start JP1/IM - Manager, and reconfigure the definition of the event acquisition filter.

To restore the event acquisition filter to initial status:

In Windows:

copy Console-path\conf\console\filter\receive_filter.conf.model Console-path\conf\console\filter\receive_filter.conf

In UNIX:

cp -p /etc/opt/jp1cons/conf/console/filter/receive_filter.conf.model /etc/opt/jp1cons/conf/console/filter/receive_filter.conf

KAVB4704-E

The event acquisition filter could not be created. :maintenance-information

An attempt to create the event acquisition filter failed.

S:

Terminates processing.

O:

The definition file may be corrupted.

If the event acquisition filter definition file is backed up, restore the file, and then restart JP1/IM - Manager.

If the event acquisition filter definition file is not backed up, use the following procedure to restore the event acquisition filter (the filter that acquires events other than JP1/SES events) to initial status. Then start JP1/IM - Manager, and reconfigure the definition of the event acquisition filter.

To restore the event acquisition filter to initial status:

In Windows:

cd Console-path\conf\console\filter

copy Console-path\conf\console\filter\receive_filter.conf.model Console-path\conf\console\filter\receive_filter.conf

In UNIX:

cd /etc/opt/jp1cons/conf/console/filter

cp -p /etc/opt/jp1cons/conf/console/filter/receive_filter.conf.model /etc/opt/jp1cons/conf/console/filter/receive_filter.conf

KAVB4705-E

An attempt to write data to the action definition backup file has failed. (detailed information = detailed-information)

An attempt to write data to the action definition backup file failed. The execution results displayed by the -d option of the jcastatus command may become invalid.

S:

Stops writing data to the action definition backup file and continues processing.

O:

Check the following items, and then re-execute the jcachange command.

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host: Console-path\log\action

- Logical host: shared-folder\jp1cons\log\action

In UNIX:

- Physical host: /var/opt/jp1cons/log/action

- Logical host: shared-directory/jp1cons/log/action

If the problem cannot be resolved, check the following OS log items to determine whether a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB4706-W

The business group or monitoring group is not defined. (definition type = definition-type, definition name = definition-name, group name = group-name)

The business group or monitoring group is not defined.

S:

Continues processing.

O:

Define the specified business group or monitoring group, or carefully review the business group name or monitoring group name.

KAVB4707-E

The business group or monitoring group is not defined. (definition type = definition-type, definition name = definition-name, group name = group-name)

The business group or monitoring group is not defined.

S:

Continues processing without applying the contents of the definition.

O:

Carefully review the specified business group or monitoring group.

If there is no problem, check with a system administrator to see if the specified business group or monitoring group has been defined.

KAVB4708-W

The business group or monitoring group is not defined. (definition type = definition-type, definition name = definition-name)

The business group or monitoring group specified for the definition indicated in the message is not defined.

S:

Invalidates the specification of the business group or monitoring group, and continues processing.

O:

Carefully review the definition, and then set it again.

KAVB4710-I

The event base service will use the common-exclusion-condition-to-use. : logical-host-name

Event Base Service will use common-exclusion-condition-to-use.

S:

Continues processing.

KAVB4711-W

The event base service cannot use common exclusion condition groups (extended) because an event acquisition filter (for compatibility) is set.

Event Base Service cannot use common exclusion-condition groups in extended mode because an event acquisition filter (for compatibility) is set.

S:

Continues processing using the event acquisition filter (for compatibility).

O:

To extend common exclusion-condition groups, you need to change the location of the event acquisition filter from Event Console Service to Event Base Service.

Use the jcochafmode command to change the location of the filter, and then restart JP1/IM - Manager.

Note that you cannot undo the jcochafmode command that changes the location of the event acquisition filter.

If you do not want to extend the common exclusion-condition groups, execute the jcochcefmode command in JP1/IM - Manager as shown below to set the operation mode for the common exclusion-condition groups to basic mode.

jcochcefmode -m default [-h logical-host-name]

KAVB4712-W

The event base service cannot use common exclusion condition groups (extended) because a regular expression used by JP1/Base is not extended. The event base service will start without any common exclusion condition groups (extended) being set.

Event Base Service cannot use common exclusion-condition groups in extended mode because a regular expression used by JP1/Base is not extended.

S:

Assumes that common exclusion-condition groups are not defined, and continues processing.

O:

To extend common exclusion-condition groups, you need to extend the regular expressions used by JP1/Base. Extend the regular expressions for JP1/Base, and then restart JP1/IM - Manager.

Extending regular expressions will affect the JP1/Base and JP1/IM functions. For details about how to extend regular expressions, see the JP1/Base manual.

If you do not want to extend the common exclusion-condition groups, execute the jcochcefmode command in JP1/IM - Manager as shown below to set the operation mode for the common exclusion-condition groups to basic mode. Then restart JP1/IM - Manager.

jcochcefmode -m normal [-h logical-host-name]

KAVB4713-E

An error occurred during reading of the common exclusion conditions extended definition file. (cause = cause)

An error occurred during reading of the common-exclusion-conditions extended definition file.

S:

If the error occurred during switching of the event acquisition filter, the system continues processing using the event acquisition filter that was in use prior to switching.

If the error occurred during startup of Event Generation Service, the system continues processing with no definition specified in the event acquisition filter.

O:

If the message shown below is displayed for cause, the definition file might be corrupted. Stop JP1/IM - Manager, change the operation mode for the common exclusion-conditions to basic mode, and then change it back to extended mode to initialize the definition of the common exclusion-conditions (extended).

The common exclusion extended definition file is invalid.

If the following message is displayed for cause, allocate sufficient memory, and then retry the operation.

A memory shortage occurred while loading was being performed.

If the following message is displayed for cause, check whether a shortage has occurred in other OS resources such as file descriptors.

An I/O error occurred while loading was being performed.

If a message other than the above is displayed for cause or if the problem cannot be resolved, check the following OS log items.

In Windows: Windows event log

In UNIX: System log (syslog)

After checking the OS log items, check whether a shortage has occurred in other OS resources such as file descriptors. If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB4714-E

The file-name (file-path) could not be created. The history cannot be output. (reason = reason)

The file could not be created. The history cannot be output.

S:

Continues processing without outputting the history.

O:

Take the following corrective actions:

When the message An I/O error occurred. is displayed for cause

- Check for a directory that has the same name as the file. Delete it, if any.

- Check whether the write permission is set on the directory where the file will be stored. Set the write permission if it is not yet set.

Check if the file is opened (or locked) in a different application. If the file is opened (or locked), close the file to unlock it.

When the message A memory shortage occurred. is displayed for cause

Allocate sufficient memory.

If any other cause is displayed or the problem is not resolved, check the following OS log:

In Windows: Windows event log

In UNIX: System log (syslog)

After you check the OS log, check whether any other shortage has occurred in an OS resource such as file descriptors. If no shortage is found, use the data collection tool to collect data, and then contact a system administrator.

KAVB4715-E

The history could not be output, because an error occurred during the output of the file-name (file-path). (reason = reason)

An error occurred while outputting the history. The history could not be output.

S:

Continues processing without outputting the history.

O:

Take the following corrective actions:

When the message An I/O error occurred. is displayed for cause

Check the following points:

- Check whether the write permission is set on the file. Set the write permission if it is not yet set.

- Check if the file is opened (or locked) in a different application. If the file is opened (or locked), close the file to unlock it.

When the message A memory shortage occurred. is displayed for cause

Allocate sufficient memory.

If any other cause is displayed or the problem is not resolved, check the following OS log:

In Windows: Windows event log

In UNIX: System log (syslog)

After you check the OS log, check whether any other shortage has occurred in an OS resource such as file descriptors. If no shortage is found, use the data collection tool to collect data, and then contact a system administrator.

KAVB4750-I

The automatic action process was connected.

Automatic Action Service was connected from Event Base Service.

KAVB4751-E

An attempt to connect to the automatic action process failed.

An attempt to connect to Automatic Action Service from Event Base Service failed. The specified number of retries were attempted, but a connection could not be established.

S:

Stops connecting to Automatic Action Service and continues processing.

O:

Execute the jco_spmd_status command to determine whether Automatic Action Service is running. If Automatic Action Service is running, it is possible that a connection could not be established within the retry time and the specified number of retries because startup processing of Automatic Action Service is taking too much time. Carefully review the retry setting. If a connection still cannot be established after changing the retry setting, or if Automatic Action Service is not running, collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4752-I

Central Scope was connected.

Central Scope Service was connected from Event Base Service.

KAVB4753-E

An attempt to connect to Central Scope failed.

An attempt to connect to Central Scope Service from Event Base Service failed. The specified number of retries were attempted, but a connection could not be established.

S:

Stops connecting to Central Scope Service and continues processing.

O:

Execute the jco_spmd_status command to determine whether Central Scope Service is running. If Central Scope Service is running, it is possible that a connection could not be established within the retry time and the specified number of retries because startup processing of Central Scope Service is taking too much time. Carefully review the retry setting.

If a connection still cannot be established after changing the retry setting, or if Central Scope Service is not running, collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4754-I

Event Console Server was connected.

Event Console Service was connected from Event Base Service.

KAVB4755-E

An attempt to connect to Event Console Server failed.

An attempt to connect to Event Console Service from Event Base Service failed. The specified number of retries were attempted, but a connection could not be established.

S:

Stops connecting to Event Console Service and continues processing.

O:

Execute the jco_spmd_status command to determine whether Event Console Service is running. If Event Console Service is running, it is possible that a connection could not be established within the number of retries and the retry time because startup processing of Central Scope Service is taking too much time. Carefully review the retry setting. If a connection still cannot be established after changing the retry setting, or if Event Console Service is not running, collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4756-I

The automatic action process was disconnected.

The connection between Event Base Service and Automatic Action Service was ended.

S:

Stops sending automated action requests to Automatic Action Service.

KAVB4757-I

Central Scope was disconnected.

The connection between Event Base Service and Central Scope Service was ended.

S:

Stops sending events to Central Scope Service.

KAVB4758-I

Event Console Server was disconnected.

The connection between Event Base Service and Event Console Service was ended.

S:

Stops sending events to the event console.

KAVB4759-E

An attempt to request transmission to the automatic action process failed.:(SEQNO: serial-number-in-event-database-of-trigger-event-of-automated-action-that-failed-to-be-sent, Command: command-of-automated-action-that-failed-to-be-sent)

An attempt to send an action request to the automated action process failed. The specified number of retries were attempted, but failed.

S:

Does not send the action of the displayed event and continues processing.

O:

Collect JP1/Base and JP1/IM data, and then contact a system administrator. If you must execute the command, execute the displayed command manually.

KAVB4760-E

Event transmission to Central Scope failed.:(SEQNO: serial-number-in-event-database-of-trigger-event-of-automated-action-that-failed-to-be-sent)

An attempt to send an event to Central Scope Service failed. The specified number of retries were attempted, but failed.

S:

Does not send the displayed event and continues processing.

O:

Collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4761-E

Event transmission to Event Console Server failed.:(SEQNO: serial-number-in-event-database-of-trigger-event-of-automated-action-that-failed-to-be-sent)

An attempt to send an event to Event Console Server failed. The specified number of retries were attempted, but failed.

S:

Does not send the displayed event and continues processing.

O:

Collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4762-W

The response to the request timed out.

The response from the process to which a request was sent timed out.

S:

Ends the connection with the timed-out process and continues processing.

KAVB4764-W

An error occurred in acquiring an event from the event service. Please check if the event service is running or not. If not, recover the error by starting the event service.

An error occurred during acquisition of an event from Event Service. Event Service was unable to distribute the event to Event Console Service and Automatic Action Service.

S:

Continues processing.

O:

Determine whether Event Service is running. If Event Service is not running, start Event Service. If Event Service is running, collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4765-I

Event Flow Control Service detected the refused connection from the automatic action process. An attempt to request transmission to the automatic action process was stopped.:(SEQNO: serial-number-in-event-database-of-trigger-event-of-automated-action-that-failed-to-be-sent, Command: command-of-automated-action-that-failed-to-be-sent)

Event Base Service detected a disconnection of communication with Automatic Action Service.

S:

Does not send the action request to Automatic Action Service until connection is re-established.

KAVB4766-I

Event Flow Control Service detected the refused connection from Central Scope Server. Event transmission to Central Scope Server was stopped.:(SEQNO: serial-number-in-event-database)

Event Base Service detected a disconnection of communication with Central Scope Service.

S:

Does not distribute the event to Central Scope Service until connection is re-established.

KAVB4767-I

Event Flow Control Service detected the refused connection from Event Console Server. Event transmission to Event Console Server was stopped.:(SEQNO: serial-number-in-event-database)

Event Base Service detected disconnection of communication with Event Console Service.

S:

Does not distribute the event to Event Console Service until connection is re-established.

KAVB4768-E

An attempt to initialize communication processing has failed. (reason: reason)

An attempt to initialize communication processing of Event Base Service failed.

S:

Stops Event Base Service.

O:

The network setting may be incorrect. Check the integrated trace log or command message log, and take the corrective action given for the message that was output preceding this message. If the network setting is correct, use the data collection tool to collect data, and then contact a system administrator.

KAVB4769-E

An attempt to initialize communication processing for the event base service has failed. (IP address = IP-address, port number = port-number, reason = reason)

An attempt to initialize communication processing of Event Base Service failed.

S:

If a multiple LAN configuration is used, ignores the IP address where the error occurred and continues processing.

In configurations other than multiple LANs, stops Event Base Service.

O:

Make sure that the port number of service name jp1imfcs defined in the services file is not being used for other services. If the port number is duplicated, change the port number to a unique number. Also check the OS settings and log to determine whether the network is available.

If the problem is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAVB4770-W

An attempt at event acquisition processing from the specified event acquisition start location has failed. Acquisition will begin from the events (events after serial number serial-number-in-event-database in the event database) that are registered after JP1/IM - Central Console is started.(maintenance-information)

During startup of JP1/IM - Manager, an error occurred when Event Base Service attempted to acquire an event from Event Service at the specified event acquisition start location.

If the event to be registered after startup of JP1/IM - Manager is an event for internal communication for JP1/Base and JP1/IM - Manager, the event displayed in the message may not be acquired. Also, the event displayed in the message may be filtered by the event acquisition filter or user filter.

S:

After JP1/IM - Manager has started, begins acquiring events registered in Event Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4771-I

The event database has been switched, so the events from serial numbers serial-number-in-event-database-1-to-serial-number-in-event-database-2 cannot be acquired.

Events stored in the previous event database could not be acquired because the event database has been switched.

S:

Begins acquiring events from the beginning of the event database.

KAVB4772-I

Acquisition will be started from the events registered after JP1/IM - Central Console is started, because no event exists in the event database.

The event specified at the event acquisition start location could not be acquired because no event exists in the event database.

S:

After JP1/IM - Manager has started, begins acquiring events registered in Event Service.

KAVB4773-E

Connection to the Event Server is not possible because the permission was not set.

The event server could not be connected because permission to connect to the event server was not assigned.

S:

Stops JP1/IM - Manager because the event cannot be acquired.

O:

Set either *or SYSTEM (in Windows) or root (in UNIX) for the users parameter in the event server settings file of JP1/Base, and then restart JP1/Base or JP1/IM - Manager.

KAVB4774-W

Acquisition will now be started from the events (events after serial number serial-number-in-event-database in the event database) registered after JP1/IM - Central Console is started, because the event acquisition start location (serial number in the event database: serial-number-in-event-database) of control-name is invalid.

The control displayed in the message detected that the event acquisition start location is invalid. For the control name, automated action service, event console service, central scope service, or event generation function is displayed.

S:

After JP1/IM - Manager has started, the control displayed in the message begins acquiring events registered in the event server.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4775-I

The event database has been switched, so the event acquisition start location (serial number in the event database: serial-number-in-event-database) of control-name was not found. Acquisition will now start from the start of the event registered in the event database (serial number in the event database: serial-number-in-event-database).

The event acquisition start location of the control displayed in the message could not be found because the event database has been switched. For the control name, automated action service, event console service, central scope service, or event generation function is displayed.

If the event registered at the beginning of the event database is an event for internal communication for JP1/Base and JP1/IM - Manager, the event displayed in the message may not be acquired. Also, the event displayed in the message may be filtered by the event acquisition filter or user filter.

S:

The control displayed in the message begins acquiring events from the beginning of the event database.

KAVB4776-W

The event acquired from the event service will be ignored because the event contains invalid information. (event database serial number: serial-number-in-event-database, reason code = reason-code)

An event acquired from Event Service will be ignored because it contains invalid information.

S:

Ignores the event that contains invalid information and continues processing.

O:

Check the following items:

If the reason code is 3:

The event arrival time is invalid. Use the manager to check the system time to determine whether the time is set correctly.

If the reason code is 4:

The event registration time is invalid. On the host where the event was registered, check the system time to determine whether the time is set correctly.

If the problem is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAVB4777-E

An attempt to switch the event acquisition filter failed because the event database contains an invalid event.

An attempt to switch the event acquisition filter failed because the event database contained an invalid event.

S:

Continues processing using the event acquisition filter that was in use prior to switching.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4780-E

The Integrated Monitoring database is not set up.

The integrated monitoring database is not set up.

S:

Stops Event Base Service.

O:

Execute the jcodbsetup command to set up the integrated monitoring database, and then restart JP1/IM - Manager. If you are not using the integrated monitoring database, specify the -db option of the jcoimdef command to disable the event storage function, and then restart JP1/IM - Manager.

KAVB4785-E

An error occurred in the communication with process-name. (reason = reason)

An error occurred in socket communication between Event Base Service and the displayed process.

S:

Ends the connection with the displayed process and stops processing.

O:

Collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4786-E

Communication processing timed out because the process (process-name) did not respond.

Event Base Service accepted a processing request from the displayed process and attempted to send the results to the process, but a communication processing time-out occurred because the process did not respond.

S:

Event Base Service ends the connection with the displayed process and stops processing.

O:

Determine whether the manager host is in high load status. If it is not in high load status, use the data collection tool to collect data, and then contact a system administrator.

KAVB4787-E

An error occurred that prevented communication of the event base service from continuing. (reason = reason)

Socket communication of Event Base Service could not continue due to an error.

S:

If a multiple LAN configuration is used, stops socket communication where the error occurred and continues processing.

In configurations other than multiple LANs, stops Event Base Service if there is no socket available for communication.

O:

Collect JP1/Base and JP1/IM data, and then contact a system administrator.

KAVB4788-W

The port number of the service-name service could not be acquired. The default port number port-number will be used now and the system will run. Confirm the setting.

An attempt to acquire the port number failed during startup of JP1/IM - Manager.

S:

Uses the default port number and continues processing.

O:

Carefully review the port number setting.

KAVB4789-W

A definition could not be reflected in Event Console Service because a communication error occurred. (details = cause)

The following definition could not be applied in Event Console Service due to a communication error.

Enabling and disabling of memo entry setting function

S:

Continues reload processing.

O:

Check the following items, and then re-execute reload processing.

Is Event Console Service running?

Is the manager in high load status?

If the same message is displayed after re-execution of reload processing, use the data collection tool to collect data, and then contact a system administrator.

KAVB4790-W

Saving of a business group ID failed. (event database serial number = event-database-serial-number, reception time = reception-time, business group name = business-group-name, cause = cause)

This JP1 event cannot be reported to the JP1 user for the business group because an attempt to save the business group ID failed when the reference/operation permission function of the business group was enabled.

S:

Terminates processing.

O:

Notify the JP1 user for the business group that a JP1 event could not be reported.

Take corrective action based on the cause indicated in the message.

Cause: 001

The number of program-specific extended attribute values exceeds 100. Carefully review the method of issuing JP1 events.

Cause: 002

The total size of extended attribute values exceeds 10,000 bytes. Carefully review the method of issuing JP1 events.

Cause: 003

A memory shortage occurred. Check memory usage, and then restart JP1/IM.

Cause: 255

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4802-I

A severity change definition was registered. (severity change definition name = severity-change-definition-name, registering user = user-name)

An additional severity change definition was registered.

KAVB4803-I

A display message change definition was registered. (display message change definition name = display-message-change-definition-name, registering user = user-name)

An additional display message change definition was registered.

KAVB4901-E

I/O error occurred. : maintenance-information

An I/O error occurred in file input or output.

S:

Aborts processing where the error occurred.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4902-E

Insufficient memory. : maintenance-information

A memory shortage occurred.

S:

Aborts processing where the error occurred.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4903-E

System error occurred. : maintenance-information

A system error occurred.

S:

Aborts processing where the error occurred.

O:

Take the corrective action given for the system error message. If necessary, collect data, and then contact a system administrator.

KAVB4904-E

System error occurred. : maintenance-information

A system error occurred.

S:

Aborts processing where the error occurred.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4905-E

Failed to put message(message-ID). : maintenance-information

An attempt to output a message failed.

S:

Continues processing.

O:

Take corrective action according to the maintenance information.

KAVB4906-E

System file (file-name) is corrupt. : maintenance-information

The file managed by the system is corrupted or was deleted.

S:

Aborts processing where the error occurred.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4907-E

No more space in file (file-name).

There is no available space to which data can be written in the file system or device.

S:

Aborts processing where the error occurred.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB4908-E

Error that prevented processing occurred in Event Server. : maintenance-information event-function-return-code

Unable to connect to the event server, register an event, or acquire an event due to an error.

S:

Aborts processing where the error occurred.

O:

Check the status of the event server, and take corrective action.

KAVB4909-E

An attempt to set locale information has failed.

An attempt to set locale information failed because a locale that is not supported by the OS was set.

S:

If the error message is output during startup of the manager, the system assumes that the locale is C and continues processing, but operation is inconsistent.

If the error message is output while opening the Action Parameter Definitions window or clicking the Apply button in the Action Parameter Definitions window, the system terminates the operation.

If the error message is output during execution of the jcamakea command, the system aborts processing.

O:

If the error message is output during startup of the manager, make sure that the LANG value in the jp1co_env.conf file is a value that can be specified, and then restart the manager.

If the error message is output while opening the Action Parameter Definitions window or clicking the Apply button in the Action Parameter Definitions window, check the environment variable value, restart, and then try the operation again.

If the error message is output during execution of the jcamakea command, make sure that the LANG environment variable value of the execution environment is a value that can be specified.

If the locale environment variable (LC_ALL, LC_COLLATE, LC_CTYPE, LC_MONETARY, LC_NUMERIC, LC_TIME, LC_MESSAGES) was specified, execute the unset command for the locale environment variable, and then retry the operation.

If the system is unable to recover after corrective action is taken, execute the locale -a command to determine whether the locale (the value of the LANG environment variable) was specified in the OS. If the locale was not specified, specify it.

KAVB5000-W

The Action Parameter Definitions window cannot be displayed because an item(item-name) not displayable by the connected IM-View is set. (line: line-number, file: file-name)

The Action Parameter Definitions window could not be displayed because an action definition that cannot be processed by the version of the connected JP1/IM - View was specified.

S:

Suspends reading of the action definition.

O:

Open the Action Parameter Definitions window using a version of JP1/IM - View that can display the required item(s).

Status monitoring can be displayed by JP1/IM - View version 07-11 or later.

Suppression time monitoring can be displayed by JP1/IM - View version 07-11 or later.

Delay monitoring time can be displayed by JP1/IM - View version 07-11 or later.

Rule can be displayed by JP1/IM - View version 08-00 or later when the JP1/IM - Rule Operation linkage function is enabled.

KAVB5001-E

The Action Parameter Definitions window could not be displayed because the version of the current automatic action definition is incompatible with the connected JP1/IM - View.

The Action Parameter Definitions window could not be displayed because the version of the action definition defined in JP1/IM - Console on the connected host is incompatible.

S:

Suspends reading of the automated action definition.

O:

Open the Action Parameter Definitions window using a version of JP1/IM - View that can display the currently defined automated action definition.

If the version of the automated action definition is 3, you can use JP1/IM - View version 09-00 or later to display the window.

If the version of the automated action definition is 4, you can use JP1/IM - View version 11-50 or later to display the window.

KAVB5002-E

The Action Parameter Definitions window could not be updated because the version of the current automatic action definition is incompatible with the connected JP1/IM - View.

The automated action definition could not be updated because the version of the action definition defined in Central Console (JP1/IM - Console) on the connected host is incompatible.

S:

Suspends updating of the automated action definition.

O:

Open the Action Parameter Definitions window using a version of JP1/IM - View that can display the currently defined automated action definition, and then update the definition.

If the version of the automated action definition is 3, you can use JP1/IM - View version 09-00 or later to display the window.

If the version of the automated action definition is 4, you can use JP1/IM - View version 11-50 or later to display the window.

KAVB5050-W

No Action Definition Information is specified.

The header information or action definition information of the action definition to be input is not specified.

S:

Suspends creation of the action definition.

O:

Re-enter the definition in the Action Parameter Detailed Definitions window.

KAVB5051-W

An invalid Parameter Group Number or an invalid event AND condition is specified. (line: line-number)

An event AND condition is specified at the starting action definition, or a value between 0 and 9 or a character other than & is specified for the parameter group in the Action Parameter Detailed Definitions window.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5052-W

An invalid Event ID is specified. (line: line-number)

The event ID in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5053-W

Invalid Message Text is specified. (line: line-number)

The regular expression specified in the message in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5054-W

Invalid Event Basic Information is specified. (line: line-number)

The regular expression specified for the basic event information in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5055-W

Invalid Event Detail Information is specified. (line: line-number)

The regular expression specified for the detailed event information in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Specify the action definition information correctly, and then re-open the Action Parameter Detailed Definitions window.

KAVB5056-W

An invalid severity for Event Expansion Information is specified. (line: line-number)

The value specified for the severity of the extended event information in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5057-W

An invalid User Name is specified. (line: line-number)

The executing user name specified in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5058-W

An invalid Environment Definition File is specified. (line: line-number)

The environment variable file name specified in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5059-W

An invalid Execution Host or Group is specified. (line: line-number)

The target host name specified in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5060-W

The length of one parameter exceeds maximum-length bytes. (line: line-number)

The length of the action definition parameter exceeds maximum-length bytes.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5061-W

More than 100 Event Extended Attributes are specified. (line: line-number)

More than 100 extended event attributes are specified for one action definition.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5062-W

An invalid Event Extended Attribute is specified. (line: line-number)

A regular expression of an extended event attribute specified in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5063-W

No action is specified. (line: line-number)

The user name, environment variable file name, or execution host or group name is specified, but the action is not specified.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB5064-W

More than 10 event AND conditions are specified in Action Definitions. (line: line-number)

Event AND conditions are specified for more than 10 action definitions.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB5065-W

Invalid Event Extended Attribute Name. (line: line-number)

An extended event attribute name specified in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Specify the action definition information correctly, and then re-open the Action Parameter Detailed Definitions window.

KAVB5066-W

An invalid Suppression Time is specified. (line: line-number)

The suppression time value specified in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Specify the action definition information correctly, and then re-open the Action Parameter Detailed Definitions window.

KAVB5067-W

An invalid Delay Monitoring Time is specified. (line: line-number)

The delay monitoring time value specified in the Action Parameter Detailed Definitions window is incorrect.

S:

Suspends creation of the action definition.

O:

Specify the action definition information correctly, and then re-open the Action Parameter Detailed Definitions window.

KAVB5068-W

The length of Action parameter exceeds maximum-length bytes. (line: line-number)

The length of the action parameter specified in the Action Parameter Detailed Definitions window exceeds maximum-length bytes.

S:

Suspends creation of the action definition.

O:

Specify the action definition information correctly, and then re-open the Action Parameter Detailed Definitions window.

KAVB5069-W

The length of the event monitoring condition parameter exceeds maximum-length bytes. (line: line-number)

The length of the parameter that can be specified for an event monitoring condition in the Action Parameter Detailed Definitions window exceeds maximum-length bytes.

S:

Suspends creation of the action definition.

O:

Re-enter the action definition information correctly in the Action Parameter Detailed Definitions window.

KAVB5070-E

An attempt to write data to the action definition file (file-name) has failed. (detailed information = detailed-information)

An attempt to write data to the automated action definition failed.

S:

Stops writing data to the automated action definition file and restores the previous status of the file. Continues processing without updating the settings in the manager.

O:

Reconfigure the automated action in the Action Parameter Definitions window.

Also check the following items:

Is sufficient disk space allocated?

Is sufficient system physical memory and virtual memory allocated?

Does a file with the same name, not a folder (directory), exist in the paths below?

Is access permission assigned for any of the folders (directories) in the paths below?

In Windows:

- Physical host:

- Console-path\conf\action

- Console-path\conf\tmp

- Logical host:

- shared-folder\jp1cons\conf\action

- shared-folder\jp1cons\conf\tmp

In UNIX:

- Physical host:

- /etc/opt/jp1cons/conf/action

- /etc/opt/jp1cons/conf/tmp

- Logical host:

- shared-directory/jp1cons/conf/action

- shared-directory/jp1cons/conf/tmp

If the problem cannot be resolved, check the following OS log items to determine if a shortage occurred with OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: syslog

If a resource shortage did not occur, use the data collection tool to collect data, and then contact a system administrator.

KAVB5104-W

The Action Definition file includes an invalid parameter.

There is an inappropriate description in the automated action definition file.

S:

Ignores the invalid action definition and continues processing.

O:

Check the definition details of the automated action definition file, and then retry the operation.

KAVB5105-W

Failed to change the Action Definition file.

An attempt to modify the automated action definition file failed.

S:

Aborts processing.

O:

Check the following points to resolve any problems, and then retry the operation:

Whether the automated action definition file exists

Whether no other processes access the automated action definition file

Whether the automated action definition file is readable and writable

Whether the device has enough available space

If the retry results in the same message, use the data collection tool to collect data and then contact a system administrator.

KAVB5106-E

Current Directory is too long.

The current directory is too long.

S:

Aborts processing.

O:

Shorten the current directory + file name to no more than 255 bytes, and then retry the operation.

KAVB5107-W

Cannot connect to Automatic Action process.

The automated daemon (service) could not be connected.

S:

Aborts processing.

O:

Make sure that the process is running and that it is not in busy status, and then retry the operation.

KAVB5108-W

Cannot receive response from Automatic Action process.

There is no response from the automated action daemon (service).

S:

Aborts processing.

O:

Make sure that the process is operating correctly, and then retry the operation.

KAVB5109-W

Cannot receive response from the Event Console Service.

There is no response from the Event Console Service.

S:

Aborts processing.

O:

Make sure that the process is operating correctly, and then retry the operation.

KAVB5110-W

Cannot receive response from the event base service.

This is no response from Event Base Service.

S:

Aborts processing.

O:

Make sure that the process is operating correctly, and then retry the operation

KAVB5111-W

The value for an option specified together with the -i option was invalid.

The value of the option specified together with the -i option could not be applied.

S:

Continues processing without applying the value of the option specified together with the -i option.

O:

If a KAVB4901-E or KAVB4789-W message is displayed in the integrated trace log, take the corrective action given for that error message.

If a message is not output, use the data collection tool to collect data, and then contact a system administrator.

KAVB5112-E

Failed to change the automatic action definition file because there is a mistake in the automatic action definition file.

The automated action definition file could not be changed because the definition file was written incorrectly.

S:

Aborts processing.

O:

Correct the error in the automated action definition file of the manager, and then retry the operation. To identify the error cause, check the integrated trace log.

KAVB5150-W

There is no applicable data in the Command Executed log file.

An attempt to acquire the command execution log failed because there is no applicable data.

S:

Ignores the inapplicable data and continues processing.

O:

If the error message is output when an action in wait status is canceled, no corrective action is needed because deletion processing by the automated action daemon (service) was completed before queuing the action execution request in JP1/Base at the command execution destination. If the error message is output in a circumstance other than the above, take appropriate corrective action such as increasing the size of the command execution log.

KAVB5151-W

Failed to get data from Command Executed log file. : maintenance-information

An attempt to acquire the command execution log of the automated action failed due to an error in operation of the command execution log file.

S:

Ignores the requested data and continues processing.

O:

Check the following items according to the reason code displayed in maintenance-information. maintenance-information is displayed as error-location-number-1 error-location-number-2 reason-code.

If the reason code is 1:

The command execution file of the automated action is locked. Wait awhile, and then retry the operation.

If the reason code is 2:

The number of opened files exceeds the maximum number allowed by the system. Allocate appropriate OS resources, and then retry the operation.

If the reason code is 4:

The command execution log file of the automated action may be corrupted. For details about how to check the log file for damage and how to recover the command execution log file of the automated action, see Section 11.5.1(9) Actions to take when a command execution log file is damaged in the manual JP1/Integrated Management 2 - Manager Administration Guide.

If the command execution log file of the automated action is normal, execute the JP1/IM data collection tool, and then contact a system administrator.

If the reason code is 5:

A memory shortage occurred. Allocate appropriate OS resources, and then retry the operation.

KAVB5152-W

An invalid response was received when the command was executed. (source host name = host-name, action serial number = action-serial-number, cid = cid, reason code = reason-code)

The time information in the response received from command control is invalid. The start time or end time of the automated action results may not be displayed.

S:

Ignores the invalid location and continues processing.

O:

Check the system time on the host where the action was executed to determine whether the time is set correctly.

If there is no error in the time, use the data collection tool to collect data, and then contact a system administrator.

KAVB5200-W

No Action Definition File is specified.

The automated action definition file name is not specified for the argument of the command.

S:

Aborts processing.

O:

Specify the automated action definition file, and then retry the operation.

KAVB5201-W

More than 100 Action Definition Files are specified.

More than 100 automated action definition files are specified for the argument of the command.

S:

Ignores file names specified after the 100th file name and continues processing.

O:

Use a text editor to reduce the number of files by consolidating automated action definition files, and then retry the operation. Alternatively, specify an automated action definition file that is created by merging up to 100 files and the 101st and subsequent automated action definition files, and then retry the operation.

KAVB5202-W

The specified Action Definition file (file-name) has no parameters.

There are no parameters to be checked in the specified automated action definition file. The file contains only blank spaces, linefeeds, and command lines.

S:

Suspends processing of the automated action definition file. If multiple files are specified, processes the next file.

O:

Correct the error, and then retry the operation.

KAVB5203-W

An invalid Action Definition exists. (line: line-number to line-number, file: file-name)

All action definitions specified for event AND conditions are invalid because there is an inappropriate action definition.

S:

Ignores the action definition at the relevant line and continues processing.

O:

Correct the error, and then retry the operation.

KAVB5250-W

Invalid Label name(label-name).

An inappropriate label name is specified.

S:

Aborts processing.

O:

Correct the error, and then retry the operation.

KAVB5251-W

Invalid value to Label name(label-name) is specified.

An inappropriate value is specified for the label name.

S:

Aborts processing.

O:

Correct the error, and then retry the operation.

KAVB5252-W

No value to Label name (label-name) is specified.

No value is specified for the label name.

S:

Aborts processing.

O:

Correct the error, and then retry the operation.

KAVB5253-W

No Label name is specified.

No label name is specified.

S:

Aborts processing.

O:

Correct the error, and then retry the operation.

KAVB5254-W

Failed to set value of Label name(label-name). : maintenance-information

An attempt to specify the value for the label name failed.

S:

Aborts processing.

O:

Determine whether the command definition settings were deleted.

KAVB5300-I

A request to re-execute an action was accepted.

A request to re-execute an action was accepted.

S:

Continues processing.

KAVB5301-W

There is no applicable data in the Action Information file.

An attempt to acquire action information from the action information file failed because there is no data.

S:

Aborts processing.

O:

This message appears if no action has been performed after installation of JP1/IM - Manager or after deletion of the action information file. This message also appears if the desired action information is not found because information is wrapped in the action information file.

If this message appears due to wrapping in the action information file, check whether the capacity of the action information file is sufficient. If it is not, estimate the required capacity of the action information file, and then specify an appropriate capacity. If the capacity of the file is sufficient, processing might have stopped (hung up) due to a deadlock or an infinite loop in Automatic Action Service (jcamain). If Automatic Action Service has stopped, collect data, and then restart JP1/IM - Manager.

Execute the jco_spmd_status command to check whether Automatic Action Service is running. If it is running, check the following items:

If the health check function is enabled:

Refer to the event arrival time of the event displayed in the KAVB5301-W message, and see if a KAVB8060-E message was output in the integrated trace log file around the same time.

If the health check function is disabled:

Determine whether action details are displayed correctly for events received prior to the event displayed in the KAVB5301-W message.

KAVB5302-W

A request to re-execute an action could not be accepted.

A request to re-execute an action failed because an action that was executed using JP1/IM - Console version 06-51 or earlier cannot be re-executed.

S:

Aborts processing.

O:

Check the contents of the action. If you wish to re-execute the action, execute it in the Execute Command window.

KAVB5303-W

The action's status does not allow re-execution.

Please click the "Update" button and check the status.

After re-execution of an action was requested, re-execution was requested again before clicking the Update button. It is also possible that the action could not be re-executed because there is no data for that action in the action information file.

S:

Aborts processing.

O:

Wait awhile, and then click the Update button in the List of Action Results window to check the latest status of the action.

If the same message is displayed, data for the action does not exist in the action information file. Increase the size of the action information file as needed.

KAVB5304-W

A request to re-execute an action failed.

An attempt to request re-execution of an action failed.

S:

Aborts processing.

O:

On the connected host of JP1/IM - View, make sure that JP1/Base is operating correctly.

KAVB5350-I

No displayable action definition exists because an automatic action process is in the automated-action-status (stop or pause) state.

No action definitions can be displayed because the automated action process is in stop or pause status.

S:

Aborts processing.

KAVB5400-E

Changing of the event distribution option was not possible.(Target file name: destination-file-name, Original file name: source-file-name): error-details

The event distribution option setting could not be changed because copying of the file failed.

S:

Does not change the event distribution option setting.

O:

Check the status of the destination and source files according to the displayed error information. If a file does not exist, contact a system administrator.

KAVB5401-E

Changing of the event distribution option was not possible. (file: file-name)

The event distribution option setting could not be changed.

S:

Does not change the event distribution option setting.

O:

Determine whether you can read from and write to the extended startup process definition file.

KAVB5403-E

An attempt to specify startup settings for the correlation event generation service has failed. (option = -egs-option-specification-value, reason = reason, file name = file-name)

An attempt to specify starting or not starting the event generation function upon starting JP1/IM - Manager failed.

S:

Restores the previous status.

O:

If reason is [I/O Error]:

Determine whether you can read from and write to the file indicated by the file name.

If reason is [System Error]:

Collect data, and then contact a system administrator.

KAVB5450-I

A request to cancel an action was received.

A request to cancel an action was accepted.

S:

Continues processing.

KAVB5451-I

Action cancellation processing has finished.

Action cancellation processing has finished.

S:

Terminates processing.

KAVB5452-I

Action cancellation processing has been canceled.

Action cancellation processing was suspended.

S:

Terminates processing.

KAVB5453-I

Cancellation processing was not performed because the action did not exist in the Execution Host.(Action Serial Number=action-serial-number, Execution Host=action-execution-host-name)

Cancellation processing was not executed because no action exists in the execution host.

S:

Terminates processing.

O:

Take corrective action according to the status of the canceled action.

If the status of the canceled action is Ended, cancellation processing cannot be performed because execution of the action is already completed.

If the status of the canceled action is other than End, make sure that the action execution host is running.

KAVB5454-E

Action cancellation processing has failed.

An attempt to perform cancellation processing of the action failed.

S:

Terminates processing.

O:

Check the following items, and then retry the operation.

Is the action execution host running?

Is JP1/IM - Manager that requested the action running?

Has a network error occurred?

KAVB5455-W

The Action Serial Number(action-serial-number) is specified more than once.

The action serial number is duplicated.

S:

Terminates processing.

O:

Eliminate duplication of the action serial number, and then retry the operation.

KAVB5456-W

A maximum of 20 Action Serial Numbers can be specified.

More than 20 action serial numbers are specified for the argument.

S:

Terminates processing.

O:

Reduce the specified action serial numbers to no more than 20, and then retry the operation.

KAVB5457-W

The action for the specified Action Serial Number(action-serial-number) does not exist.

The action serial number specified for the argument does not exist.

S:

Terminates processing.

O:

Specify the correct action serial number, and then retry the operation.

KAVB5458-W

An invalid Execution Host Name(action-execution-host-name) is specified.

The action execution host name specified for the argument is invalid.

S:

Terminates processing.

O:

Specify the correct action execution host name, and then retry the operation.

KAVB5459-W

Cancellation is not possible because the action with the specified Action Serial Number(action-serial-number) is not in a cancelable state.

Cancellation processing was not executed because it is not possible to cancel the action of the action serial number specified for the argument.

S:

Terminates processing.

O:

Specify an action that can be canceled, and then retry the operation.

KAVB5460-E

A request to cancel an action could not be processed by the Execution Host.

(Execution Host=action-execution-host-name, Action Serial Number=action-serial-number)

The action execution host could not process a request to cancel an action.

S:

Terminates processing.

O:

Check the following items:

Is the version of JP1/Base on the action execution host 07-10 or later?

Is the action execution host running?

KAVB5461-I

Any action will be cancelled. Is this OK? [Y or N]

Confirms that it is OK to cancel the specified action.

S:

Waits for input.

O:

Enter Y or y to cancel the action. Enter N or n not to cancel the action.

KAVB5500-E

The specified action definition file cannot be converted because its format is invalid.

The conversion cannot be performed because the format of the specified action definition file is incorrect.

S:

Terminates processing.

O:

Execute the jcamakea command to see if there is an error in the action definition file, correct the error, and then re-execute the jcadefconv command.

KAVB5502-E

The pre-conversion name of the action definition file matches its post-conversion name.

The pre-conversion action definition file name and post-conversion action definition file name are the same.

S:

Terminates processing.

O:

Change the name of the post-conversion action definition file.

KAVB5504-E

The name of the post-conversion action definition file cannot be used because a file with that name already exists.

The action definition file cannot be converted because a file with the same name as the post-conversion action definition file already exists.

S:

Terminates processing.

O:

Change the name of the post-conversion action definition file, and then retry the operation.

KAVB5505-W

After conversion, the action definition file contains an item that is invalid in version 11-50 or later.

The output action definition file contains a definition item that is invalid for a format of version 11-50 or later.

S:

Terminates processing.

O:

Correct the invalid item in the action definition file that was output as a version 11-50 format file. Then execute the jcamakea command to see if the definition file contains invalid items.

KAVB5506-W

The action definition file cannot be converted because the specified value of DESC_VERSION is 4 or more.

The action definition file to be converted has DESC_VERSION set to 4 or more.

S:

Terminates processing.

O:

Check the name of the action definition file to be converted. Correct the error and then retry the jcadefconv command.

KAVB5511-W

More than 10 AND conditions have been specified. (line = line-number, file = file-name)

More than 10 AND conditions are specified.

S:

Ignores the action block that contains the error and continues processing.

O:

Correct the error in the automated action definition file, and then retry the operation.

KAVB5512-W

An ampersand (&) cannot be specified for a parameter group of an action block at the front of an AND condition. (line = line-number, file = file-name)

You cannot specify an ampersand (&) for the parameter group of the action block at the beginning of an AND condition.

S:

Ignores the action block that contains the error and continues processing.

O:

Correct the error in the automated action definition file, and then retry the operation.

KAVB5513-W

More than 256 event conditions have been specified. (action = action-name, line = line-number, file = file-name)

More than 256 event conditions are specified.

S:

Ignores the action block that contains the invalid definition and continues processing.

O:

Correct the error in the automated action definition file, and then retry the operation.

KAVB5514-W

The parameter parameter-name cannot be specified because a rule has been specified for the action. (action = action-name, line = line-number, file = file-name)

If an action for starting a rule was specified, no user name, target host name/group name, or environment variable file name can be specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5515-W

The location of the version of the automatic action definition file is invalid. (line = line-number, file = file-name)

The version of the automated action definition file is defined at a location other than the start of the file.

S:

Ignores the version of the automated action definition file with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5516-W

The version information for the automatic action definition file is invalid. (line = line-number, file = file-name)

The version information is invalid.

S:

Assumes that the automated action definition file version number is 3 and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5517-W

The parameter parameter is missing. (action = action-name, line = line-number, file = file-name)

A parameter is not specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5518-W

The shared block has been duplicated. (line = line-number, file = file-name)

A shared block is duplicated.

S:

Ignores shared blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5519-W

An invalid parameter is specified. (invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified in the automated action definition file.

S:

Ignores the invalid parameter and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5520-W

An invalid parameter is specified in an action block. (action = action-name, invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified in an action block.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5521-W

An action block does not end with an "end-act" statement. (action = action-name, line = line-number, file = file-name)

An action block has no end.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5522-W

An action name is not specified. (line = line-number, file = file-name)

No action name is specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5523-W

If an ampersand (&) is specified in a parameter group, an action name cannot be specified. (action = action-name, line = line-number, file = file-name)

If an ampersand (&) is specified in a parameter group, an action name cannot be specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5524-W

An action name is duplicated. (action = action-name, line = line-number, file = file-name)

An action name is duplicated.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5525-W

An action name exceeds the maximum length. (line = line-number, file = file-name)

An action name exceeds the maximum length.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5526-W

The parameter parameter-name is invalid. (action = action-name, line = line-number, file = file-name)

The specification for the indicated parameter is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5527-W

No value is specified for the parameter parameter-name. (action = action-name, line = line-number, file = file-name)

No value is specified after the indicated parameter.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5528-W

The parameter parameter-name is specified more than once. (action = action-name, line = line-number, file = file-name)

The indicated parameter is specified more than once.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5529-W

No value is specified for the parameter parameter-name. (action = action-name, line = line-number, file = file-name)

No value is specified after the parameter shown.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5530-W

The parameter parameter-name is specified more than once. (action = action-name, line = line-number, file = file-name)

The indicated parameter is specified more than once.

S:

Ignores parameters with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5531-W

The number of characters (bytes) in the parameter parameter-name exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The value of the indicated parameter exceeds the maximum number of bytes.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5532-W

The number of characters (bytes) in the parameter parameter-name exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The value of the indicated parameter exceeds the maximum number of bytes.

S:

Specifies a valid character string of no more than the maximum byte count and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5533-W

An event condition block does not end with an "end-act" statement. (action = action-name, line = line-number, file = file-name)

An event condition block has no end.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5534-W

The event condition block is invalid. (action = action-name, line = line-number, file = file-name)

The description of an event condition is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5535-W

The event condition block attribute name is invalid. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The event condition attribute-name is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5536-W

The attribute name is not specifiable. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

An attribute name that cannot be specified was specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5537-W

The comparison key word for the event conditions is invalid. (attribute name = attribute-name, comparison key word = comparison-keyword, action = action-name, line = line-number, file = file-name)

The event condition comparison-keyword is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5538-W

The comparison key word is not specifiable. (attribute name = attribute-name, comparison key word = comparison-keyword, action = action-name, line = line-number, file = file-name)

A comparison keyword that cannot be specified was specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5539-W

The number of event condition operands exceeds the maximum number. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The number of event condition operands exceeds the maximum.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5540-W

An event condition operand is duplicated. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

An event condition operand is duplicated.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5541-W

An event ID operand is invalid. (operand = operand, action = action-name, line = line-number, file = file-name)

An event ID operand is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5542-W

A regular expression is invalid. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

The specification of a regular expression is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5543-W

A critical operand is invalid. (operand = operand, action = action-name, line = line-number, file = file-name)

A critical operand is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5544-W

An operand is invalid. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

An operand is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5545-W

The combination of comparison conditions among multiple event attributes that have the same name is invalid. (attribute = attribute-name, action = action-name, line = line-number, file = file-name)

The combination of comparison conditions among multiple specified event attributes that have the same name is invalid.

S:

Ignores action blocks with definition errors and continues processing.

O:

Revise any sections of the action definition file that are invalid. After revision, use the jcamakea command to verify the definition file.

KAVB5546-W

The number of characters (bytes) in an operand exceeds the maximum. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

An operand exceeds the maximum number of bytes.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5547-W

The total number of characters (bytes) in the operands exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The total number of bytes in the operands exceeds the maximum.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5548-W

The specified value for the parameter parameter-name is outside the valid range. (specified value= specified-value, action = action-name, line = line-number, file = file-name)

The value specified for the indicated parameter is outside the valid range.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5549-W

If an ampersand (&) is specified in a parameter group, det cannot be specified. (action = action-name, line = line-number, file = file-name)

If an ampersand (&) is specified in a parameter group, det cannot be specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5550-W

Version information of an action definition file is specified more than once. (line = line-number, file = file-name)

The version information of an action definition file is specified more than once.

S:

Ignores version information with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5551-W

A shared block is specified after an action block. (line = line-number, file = file-name)

A shared block is specified after an action block.

S:

Ignores the shared block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5552-W

A shared block does not end with an "end-act" statement. (line = line-number, file = file-name)

A shared block has no end.

S:

Ignores the shared block with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5553-W

An invalid parameter is specified for a shared block. (invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified for a shared block.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5554-W

The parameter parameter-name is specified more than once. (line = line-number, file = file-name)

The indicated parameter is specified more than once.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5555-W

No value is specified for the parameter parameter-name. (line = line-number, file = file-name)

No value is specified after the parameter shown.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5556-W

The parameter parameter-name is invalid. (line = line-number, file = file-name)

The description of the indicated parameter is invalid.

S:

Ignores parameters with definition errors and continues processing.

O:

Correct the automated action definition file error, and then retry the operation.

KAVB5557-W

An error occurred while reading an action definition file. (reason = reason, line = line-number, file = file-name)

An error occurred while reading a definition file.

S:

Ignores the affected action block or parameter and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB5558-E

The size of the action definition file exceeds the upper limit. (file name = file-name, upper limit = maximum-size)

The size of the action definition file exceeds the upper limit.

S:

Terminates processing without reading the action definition file.

O:

Carefully review the contents of the action definition file to see if it contains extraneous comments or redundant definitions, and correct the file so that its size does not exceed the upper limit. After correcting the file, use the jcamakea command to confirm that there are no errors in the definition file.

KAVB5559-W

The same action ID is specified more than once. (action = action-name, line = line-number, file = file-name)

The same action ID is specified more than once.

S:

Ignores the action ID that has an invalid definition, and continues processing.

O:

Correct the error, and then reload the automated action definition file.

KAVB5560-W

You cannot specify an action ID if you specified an ampersand (&) for the parameter group. (line = line-number, file = file-name)

When an ampersand (&) is specified for the parameter group, you cannot specify an action ID.

S:

Ignores the parameter group that has an invalid definition, and continues processing.

O:

Correct the error, and then reload the automated action definition file.

KAVB5561-W

You cannot specify "valid" if you specified an ampersand (&) for the parameter group. (line = line-number, file = file-name)

When an ampersand (&) is specified for the parameter group, you cannot specify valid.

S:

Ignores the parameter group that has an invalid definition, and continues processing.

O:

Correct the error, and then reload the automated action definition file.

KAVB5711-W

More than 10 AND conditions have been specified. (line = line-number, file = file-name)

More than 10 AND conditions have been specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5712-W

An ampersand (&) cannot be specified for a parameter group of an action block at the front of an AND condition. (line = line-number, file = file-name)

An ampersand (&) cannot be specified for a parameter group of an action block at the beginning of an AND condition.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5713-W

More than 256 event conditions have been specified. (action = action-name, line = line-number, file = file-name)

More than 256 event conditions have been specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5714-W

The parameter parameter-name cannot be specified because a rule has been specified for the action. (action = action-name, line = line-number, file = file-name)

If an action for starting a rule is specified, no user name, target host name/group name, or environment variable file name can be specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5715-W

The location of the version of the automatic action definition file is invalid. (line = line-number, file = file-name)

The version of the automated action definition file is defined at a location other than the start of the file.

S:

Ignores the version of the automated action definition file with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5716-W

The version information for the automatic action definition file is invalid. (line = line-number, file = file-name)

The version information is invalid.

S:

Assumes that the automated action definition file version number is 3 and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5717-W

The parameter parameter is missing. (action = action-name, line = line-number, file = file-name)

A parameter is not specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5718-W

The shared block has been duplicated. (line = line-number, file = file-name)

A shared block is duplicated.

S:

Ignores the shared block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5719-W

An invalid parameter is specified. (invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified in an automated action definition file.

S:

Ignores the invalid parameter and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5720-W

An invalid parameter is specified in an action block. (action = action-name, invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified in an action block.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5721-W

An action block does not end with an "end-act" statement. (action = action-name, line = line-number, file = file-name)

An action block has no end.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5722-W

An action name is not specified. (line = line-number, file = file-name)

No action name is specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5723-W

If an ampersand (&) is specified in a parameter group, an action name cannot be specified. (action = action-name, line = line-number, file = file-name)

If an ampersand (&) is specified in a parameter group, an action name cannot be specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5724-W

An action name is duplicated. (action = action-name, line = line-number, file = file-name)

An action name is duplicated.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5725-W

An action name exceeds the maximum length. (line = line-number, file = file-name)

An action name exceeds the maximum length.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5726-W

The parameter parameter-name is invalid. (action = action-name, line = line-number, file = file-name)

The specification for the indicated parameter is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5727-W

No value is specified for the parameter parameter-name. (action = action-name, line = line-number, file = file-name)

No value is specified after the parameter shown.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5728-W

The parameter parameter-name is specified more than once. (action = action-name, line = line-number, file = file-name)

The indicated parameter is specified more than once.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5729-W

No value is specified for the parameter parameter-name. (action = action-name, line = line-number, file = file-name)

No value is specified after the parameter shown.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5730-W

The parameter parameter-name is specified more than once. (action = action-name, line = line-number, file = file-name)

The indicated parameter is specified more than once.

S:

Ignores parameters with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5731-W

The number of characters (bytes) in the parameter parameter-name exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The value of the indicated parameter exceeds the maximum number of bytes.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5732-W

The number of characters (bytes) in the parameter parameter-name exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The value of the indicated parameter exceeds the maximum number of bytes.

S:

Treats a character string whose length is no greater than the maximum number of bytes as valid, and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5733-W

An event condition block does not end with an "end-act" statement. (action = action-name, line = line-number, file = file-name)

An event condition block does not have an end.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5734-W

The event condition block is invalid. (action = action-name, line = line-number, file = file-name)

The description of an event condition is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5735-W

The event condition block attribute name is invalid. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The event condition attribute-name is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5736-W

The attribute name is not specifiable. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

An attribute name that cannot be specified is specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5737-W

The comparison key word for the event conditions is invalid. (attribute name = attribute-name, comparison key word = comparison-keyword, action = action-name, line = line-number, file = file-name)

The event condition comparison-keyword is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5738-W

The comparison key word is not specifiable. (attribute name = attribute-name, comparison key word = comparison-keyword, action = action-name, line = line-number, file = file-name)

A comparison keyword that cannot be specified is specified.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5739-W

The number of event condition operands exceeds the maximum number. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The number of event condition operands exceeds the maximum number.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5740-W

An event condition operand is duplicated. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

An event condition operand is duplicated.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5741-W

An event ID operand is invalid. (operand = operand, action = action-name, line = line-number, file = file-name)

An event ID operand is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5742-W

A regular expression is invalid. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

The specification of a regular expression is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5743-W

A critical operand is invalid. (operand = operand, action = action-name, line = line-number, file = file-name)

A critical operand is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5744-W

An operand is invalid. (attribute name = attribute-name, operand = operand, action = action-name, line = line-number, file = file-name)

An operand is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5745-W

The combination of comparison conditions among multiple event attributes that have the same name is invalid. (attribute = attribute-name, action = action-name, line = line-number, file = file-name)

The combination of comparison conditions among multiple specified event attributes that have the same name is invalid.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5746-W

The number of characters (bytes) in an operand exceeds the maximum. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name)

The number of bytes in an operand exceeds the maximum.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5747-W

The total number of characters (bytes) in the operands exceeds the maximum. (action = action-name, line = line-number, file = file-name)

The total number of bytes in the operands exceeds the maximum.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5748-W

The specified value for the parameter parameter-name is outside the valid range. (specified value= specified-value, action = action-name, line = line-number, file = file-name)

The specified value for the indicated parameter is outside the valid range.

S:

Ignores the action block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5749-W

If an ampersand (&) is specified in a parameter group, det cannot be specified. (action = action-name, line = line-number, file = file-name)

If an ampersand (&) is specified in a parameter group, det cannot be specified.

S:

Ignores action blocks with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5750-W

Version information of an action definition file is specified more than once. (line = line-number, file = file-name)

The version information of an action definition file is specified more than once.

S:

Ignores version information with a definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5751-W

A shared block is specified after an action block. (line = line-number, file = file-name)

A shared block is specified after an action block.

S:

Ignores the shared block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5752-W

A shared block does not end with an "end-act" statement. (line = line-number, file = file-name)

A shared block has no end.

S:

Ignores the shared block with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5753-W

An invalid parameter is specified for a shared block. (invalid parameter = parameter-name, line = line-number, file = file-name)

An invalid parameter is specified for a shared block.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5754-W

The parameter parameter-name is specified more than once. (line = line-number, file = file-name)

The indicated parameter is specified more than once.

S:

Ignores parameters with definition errors and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5755-W

No value is specified for the parameter parameter-name. (line = line-number, file = file-name)

No value is specified after the parameter shown.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5756-W

The parameter parameter-name is invalid. (line = line-number, file = file-name)

The description of the indicated parameter is invalid.

S:

Ignores the parameter with the definition error and continues processing.

O:

Correct the error, and then read the automated action definition file again.

KAVB5757-W

An error occurred while reading an action definition file. (reason = reason, line = line-number, file = file-name)

An error occurred while reading a definition file.

S:

Ignores the affected action block or parameter and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB5758-E

The size of the action definition file exceeds the upper limit. (file name = file-name, upper limit = maximum-size)

The size of the action definition file exceeds the upper limit.

S:

Continues processing without reading the action definition file.

O:

Carefully review the contents of the action definition file to see if it contains extraneous comments or redundant definitions, and correct the file so that its size does not exceed the upper limit. After correcting the file, restart JP1/IM - Manager or update the action definitions.

KAVB5759-W

Using the regular expression you specified, the processing to match JP1 events will take a long time. This will affect the performance of event reception. (attribute name = attribute-name, action = action-name, line = line-number, file = file-name, cause = cause)

The regular expression you have specified will cause the processing to match JP1 events to take a while. This will affect the performance of event reception.

S:

Continues processing.

O:

Correct the regular expression that will take a while for the processing to match JP1 events.

.* is specified at the beginning or the end.

Delete the .* specified at the beginning or end.

.* is specified repeatedly.

Use only one instance of .* at the location where it is repeated.

KAVB5760-W

The same action ID is specified more than once. (action = action-name, line = line-number, file = file-name)

The same action ID is specified more than once.

S:

Ignores the action block that has an invalid definition, and continues processing.

O:

Correct the error, and then reload the automated action definition file.

KAVB5761-W

You cannot specify an action ID if you specified an ampersand (&) for the parameter group. (line = line-number, file = file-name)

When an ampersand (&) is specified for the parameter group, you cannot specify an action ID.

S:

Ignores the action block that has an invalid definition, and continues processing.

O:

Correct the error, and then reload the automated action definition file.

KAVB5762-W

You cannot specify "valid" if you specified an ampersand (&) for the parameter group. (line = line-number, file = file-name)

When an ampersand (&) is specified for the parameter group, you cannot specify valid.

S:

Ignores the action block that has an invalid definition, and continues processing.

O:

Correct the error, and then reload the automated action definition file.

KAVB5800-I

The definition file for extended event attributes was read in to JP1/IM - Manager.

The definition file for extended event attributes was read into JP1/IM - Manager.

O:

Restart JP1/IM - View to apply the content of the definition file that was read into JP1/IM - View.

KAVB5801-E

An error occurred while the definition file for extended event attributes was being read. (cause = cause, file = file-name)

An error occurred while reading an extended file for an extended event attribute definition file.

S:

Ignores the extended file for the extended event attribute definition file and continues processing.

O:

If An I/O error occurred while loading the definition file. is displayed for cause, determine whether the file can be read.

If it can, check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as file descriptors.

• In Windows: Windows event log

• In UNIX: System log (syslog)

If A memory shortage occurred while loading was being performed. is displayed for cause, ensure sufficient memory is available, and then retry the operation.

If the problem cannot be resolved or if another cause is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB5802-W

An attribute name specified in an extend file for the definition file for extended event attributes is duplicated in the standard file for the definition file for extended event attributes. (line number = line-number, file = file-name)

An attribute name specified in an extended file for an extended event attribute definition file duplicates an attribute name specified in the standard file for the extended event attribute definition file.

The only attribute names that can be specified in an extended file for an extended event attribute definition file are names of program-specific extended attributes that are not specified in the standard file for the extended event attribute definition file.

S:

Ignores the line in question and continues processing.

O:

Delete the line in question in the extended file for the extended event attribute definition file. After the line is deleted, use the jcoattrfcheck command to check the description in the extended file for the extended event attribute definition file.

KAVB5803-W

There is an error in an extend file for the definition file for extended event attributes. cause (maximum value = maximum-value, line number = line-number, file = file-name)

There is an error in the description in an extended file for an extended event attribute definition file.

S:

Ignores the line in question and continues processing.

O:

Correct the error in the line number in question in the extended event attribute definition file as indicated by one of the following causes:

cause: The total number of attr statements exceeds the maximum.

Delete unnecessary attr statements.

cause: The byte count of the name parameter exceeds the maximum count.

Correct the byte count of the name parameter to not exceed the maximum count.

cause: The byte count of the title parameter exceeds the maximum count.

Correct the byte count of the title parameter to not exceed the maximum count.

After the error is corrected, use the jcoattrfcheck command to check the description in the extended file for the extended event attribute definition file.

KAVB5804-E

An attempt to read the definition file for extended event attributes failed because part of the definition file for extended event attributes could not be read.

An attempt to read an extended event attribute definition file failed because part of the definition file for extended event attributes could not be read.

S:

Applies only that part of the extended event attribute definition file that was successfully read into JP1/IM - Manager, and continues processing.

O:

Check the manager's integrated trace log, and determine whether an error message was output for the extended event attribute definition file (KAVB5801-E).

If so, take corrective action as indicated by that message.

KAVB5806-E

Failed to encrypt communications by using the communication encryption function for Event Base Service. (host name of connection destination = connection-destination-host-name, cause = cause)

An attempt to encrypt communication with a communication target failed.

S:

Closes the connection to Event Console Service, and then continues processing.

O:

Restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB5809-E

A parameter of the communication encryption function for the Event Base Service is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function for Event Base Service is invalid.

S:

Terminates Event Base Service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A valid value is not specified for a parameter. is displayed for cause, set a valid value for the parameter in the common definitions of JP1/Base.

If The value of a parameter exceeds the maximum. is displayed for cause, set a value no longer than the maximum length for the parameter in the common definitions of JP1/Base.

KAVB5810-E

Parameters for the communication encryption function for the Event Base Service could not be collected. (parameter = parameter-name, cause = cause)

Parameters for the communication encryption function for Event Base Service could not be acquired.

S:

Terminates Event Base Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB5820-W

Some attributes are not specified in an extend file for the definition file for extended event attributes. (attribute name = attribute-name, file = file-name)

Attributes specified in another extended file are not specified in an extended file for an extended event attribute definition file. Attributes specified in an extended file for an extended event attribute definition file must match in all extended files.

Attributes specified in other extended files are deemed specified in the file in question, and their attribute names are displayed or output.

S:

Considers unspecified attributes to be specified in the file in question and continues processing.

O:

Specify the unspecified attributes in the extended file for the extended event attribute definition file.

KAVB5821-W

There is an error in an extend file for the definition file for extended event attributes. cause (line number = line-number, file = file-name)

There is an error in the description in an extended file for an extended event attribute definition file.

S:

Ignores the line in question and continues processing.

O:

Correct the error on the line number in question in the extended event attribute definition file as indicated by the following cause:

cause: The attribute name cannot be specified.

Delete the attr statements that specified the attribute name that is not allowed.

After the error is corrected, use the jcoattrfcheck command to check the description in the extended file for the extended event attribute definition file.

KAVB5822-W

There is an error in an extend file for the definition file for extended event attributes. (file = file-name)

There is an error in the description in an extended file for an extended event attribute definition file.

S:

Ignores the description that contains the error and continues processing.

O:

Use the jcoattrfcheck command to check the description in the extended file for the extended event attribute definition file, and then correct it.

After the error is corrected, use the jcoattrfcheck command to check the description in the extended file for the extended event attribute definition file.

2.7 Messages related to Central Scope - View (KAVB6001 to KAVB6999)

KAVB6006-E

Please enter input-information.

A required item has not been input in the window.

S:

Waits for re-entry of information.

O:

Enter the required item.

KAVB6007-I

processing

Please wait a while...

processing is being executed.

S:

Processing is executed until it finishes.

O:

Wait until processing finishes.

KAVB6011-I

Do you want to exit (logout)?

Confirms that it is OK to log out.

S:

When the Yes button is clicked, the system logs out. When the No button is clicked, the system does not log out.

KAVB6013-I

Do you want to change the status of all child monitoring nodes to status-or-monitoring-status?

Confirms that you want to change all child monitoring nodes to status-or-monitoring-status.

S:

When the Yes button is clicked, the system changes the statuses of the child monitoring nodes to status-or-monitoring-status. When the No button is clicked, the system does not change the statuses of the child monitoring nodes.

KAVB6014-I

Do you want to change the status of monitoring-node-and-all-child-monitoring-nodes to status-or-monitoring-status?

Confirms that you want to change monitoring-node-and-all-child-monitoring-nodes to status-or-monitoring-status.

S:

When the Yes button is clicked, the system changes monitoring-node-and-all-child-monitoring-nodes to status-or-monitoring-status. When the No button is clicked, the system does not change the monitoring node status.

KAVB6015-I

data with the same name already exists on the server. Do you want to overwrite it?

Confirms that you want to overwrite server data.

S:

When the Yes button is clicked, the system overwrites data. When the No button is clicked, the system does not overwrite data.

KAVB6016-E

The input number for input-information exceeds the maximum input number (number-of-items).

The number of items for input-information exceeds the maximum input number.

S:

Waits for re-entry of information.

O:

Enter the correct number of items.

KAVB6018-I

Do you want to delete data?

Confirms that you want to delete the selected data.

S:

When the Yes button is clicked, the system deletes the selected data from the display area. When the No button is clicked, the system does not delete the selected data from the display area.

KAVB6019-E

An attempt to start the application has failed.

Startup command: start-command

Details: detailed-information

An error occurred during application startup.

S:

Aborts startup of the application.

O:

Confirm that the executed application is still at the location where it was installed.

KAVB6020-I

Do you want to change the status of monitoring-node to status?

Confirms that you want to change the status of the selected monitoring node to status.

S:

When the Yes button is clicked, the system changes the status of the selected monitoring node to status. When the No button is clicked, the system does not change the status of the selected monitoring node.

KAVB6021-I

Updated data has not been saved to the server. Do you want to continue?

Confirms that you want to exit without saving the updated data to the server.

S:

When the Yes button is clicked, the system closes the window without saving the updated data. When the No button is clicked, the system does not close the window.

KAVB6022-E

The file-type was not found.

file-name

There is no local file.

S:

Continues all processing possible without the identified file.

O:

Confirm that file-type exists.

KAVB6023-I

Do you want to update the server's data?

Confirms that you want to save updated data on the server.

S:

When the Yes button is clicked, the system saves updated data on the server. When the No button is clicked, the system does not save updated data.

KAVB6024-E

The file is not supported. Please see online Help.

An attempt to perform preview processing failed because an image file in an unsupported format was specified for a visual icon.

S:

Suspends preview processing.

O:

Check the following items to see if the specified file is a supported visual icon. Then correct the specification of the file as necessary.

File format is *.gif, *.jpg, or *.png.

Size is between 24 x 24 pixels and 2,048 x 2,048 pixels.

File name (including path) does not exceed 260 bytes.

KAVB6025-W

A visual icon is invalid.

file-name

An image file file-name in an unsupported format was specified for a visual icon.

If there are multiple monitoring nodes configured with invalid visual icons in the same window, only the first invalid file name will be displayed in the dialog box. All invalid file names are output to the integrated trace log.

S:

Uses the icon selected in the Icon (normal) field of the Properties window and continues processing.

O:

Check the following items to see if the specified file is a supported visual icon. Then correct the specification of the file as necessary.

File format is *.gif, *.jpg, or *.png.

Size is between 24 x 24 pixels and 2,048 x 2,048 pixels.

File name (including path) does not exceed 260 bytes.

KAVB6029-I

Do you want to clear the background image?

Confirms that you want to clear the setting for the background image.

S:

When the Yes button is clicked, the system clears the background image. When the No button is clicked, the system does not change the background image.

KAVB6030-I

The Apply button has not been clicked. Do you want to continue?

Configuration data is enabled when the Apply button is clicked. You are attempting to close a window without clicking the Apply button. This message confirms that you want to close the window without saving the configuration data.

S:

When the Yes button is clicked, the system closes the window without saving the configuration data. When the No button is clicked, the system does not close the window.

KAVB6031-I

Do you want to read "file-name"?

Confirms that you want to read a local file.

S:

When the Yes button is clicked, the system reads the file. When the No button is clicked, the system does not read the file.

KAVB6032-I

Do you want to save "file-name"?

Confirms that you want to save a local file.

S:

When the Yes button is clicked, the system saves the file. When the No button is clicked, the system does not save the file.

KAVB6033-I

Do you want to replace "file-name"?

Confirms that you want to overwrite a local file.

S:

When the Yes button is clicked, the system overwrites and saves the local file. When the No button is clicked, the system does not overwrite and save the file.

KAVB6034-E

An I/O error has occurred during analysis of the "data" file.

An I/O error occurred during analysis of a local definition file.

S:

Continues all processing possible without the identified file.

O:

Determine whether the data definition file was modified.

KAVB6036-I

Do you want to replace the tree configuration information being edited?

Confirms that you want to read new tree configuration information without saving the tree configuration information currently being modified on the server.

S:

When the Yes button is clicked, the system replaces the existing tree configuration information with new tree configuration information. When the No button is clicked, the system returns to the startup window without making any changes.

KAVB6041-E

A system error occurred while processing.

An error was detected during processing.

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6042-E

A memory shortage occurred while processing.

Processing could not continue due to a memory shortage during processing.

S:

Aborts processing.

O:

Close all windows that can be closed, and then retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6043-E

The monitoring node cannot be moved to itself.

A monitoring group was dragged to the identical monitoring group in the tree area. A monitoring node on a monitoring tree cannot be moved to itself.

S:

Aborts processing.

O:

Perform the operation again properly.

KAVB6044-E

The monitoring group cannot be moved to its own child monitoring group.

A monitoring group on a tree cannot be moved to its own child monitoring group.

S:

Aborts processing.

O:

Perform the operation again properly.

KAVB6046-E

The user (user) does not have administrator permissions necessary for operations.

The user does not have the administrator permission necessary for the operation.

S:

Aborts processing.

O:

Log in as a user who has the administrator permission.

If this message is displayed when saving changes made in the Monitoring Tree (Editing) window, see 11.5.1(15) Actions to take when an earlier version of JP1/IM - Manager or JP1/IM - View is being used in the manual JP1/Integrated Management 2 - Manager Administration Guide.

KAVB6052-I

The latest status will be acquired because the configuration of the monitoring tree has changed.

If any properties are being displayed, please close them after closing this message.

Reports that the monitoring tree configuration will be updated. When the monitoring tree's monitoring range setting is enabled, this message is also displayed when the connection destination server restarts.

S:

When OK is clicked, acquires the latest status of the monitoring tree.

KAVB6053-E

The regular expression specification is incorrect.

The regular expression specification is incorrect.

S:

Waits for re-entry of information.

O:

Check the regular expressions that can be used, reconfigure the conditions, and then retry the operation.

KAVB6054-E

The same monitoring node attribute name is already registered.

Duplicate conditions cannot be entered because extended attributes are input with an AND condition.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6056-I

The visual monitoring data in the Visual Monitoring window has changed.

The latest status will now be acquired.

The visual monitoring data in the Visual Monitoring window will be updated.

S:

When OK is clicked, acquires the latest status of the visual monitoring data.

KAVB6057-I

Do you want to replace the tree configuration being edited?

Confirms that you want to read new visual monitoring data without saving the visual monitoring data being modified on the server.

S:

When the Yes button is clicked, the system replaces the displayed visual monitoring data with new visual monitoring data. When the No button is clicked, the system returns to the startup window without making any changes.

KAVB6058-I

Do you want to close this window, and then logout?

Confirms that you want to log out.

S:

When the Yes button is clicked, the system logs out. When the No button is clicked, the system does not log out.

KAVB6059-I

A corresponding event was not found.

There was no status change event in the monitoring target specified in the status change event search.

S:

Ignores the operation.

O:

Specify a monitoring target that has a status change event, and then execute the operation.

KAVB6060-E

The connection destination server did not respond.

The connection destination server did not respond.

S:

Suspends processing.

O:

Check the version of the connection destination server.

If this message is displayed when saving changes made in the Monitoring Tree (Editing) window, see 11.5.1(15) Actions to take when an earlier version of JP1/IM - Manager or JP1/IM - View is being used in the manual JP1/Integrated Management 2 - Manager Administration Guide.

KAVB6063-E

Undo processing has failed.

An error occurred in processing to undo a monitoring tree editing operation.

S:

Ignores the operation.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6064-E

Redo processing has failed.

An error occurred in processing that cancels processing to undo a monitoring tree editing operation.

S:

Ignores the operation.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6065-E

An attempt to open the file-type file has failed.

file-name

An attempt to open a CSV file while writing or reading failed.

S:

Ignores the operation.

O:

Check the following items:

If reading, does the file to be read exist?

If saving, does the file to be written have a read-only attribute?

If saving, has another program opened the file?

If saving, does file-name contain a character that the system cannot use?

KAVB6066-E

The monitoring node can be copied or moved only to a monitoring group.

Monitoring nodes on a monitoring tree can only be copied or moved to monitoring groups.

S:

Ignores the operation.

O:

Make sure that the destination of the move is a monitoring group.

KAVB6067-I

This operation cannot be undone. Do you want to continue?

Confirms that you want to perform an operation that cannot be undone.

S:

When the Yes button is clicked, the system performs the operation. When the No button is clicked, the system does not perform the operation.

KAVB6068-E

The number of data setup exceeds the maximum value (value).

No new data can be registered because the number of data items that have been specified has reached the maximum.

S:

Ignores the operation.

O:

Delete unnecessary data from the existing data, and then perform the operation again.

KAVB6069-E

An attempt to close the file-type file has failed.

file-name

An attempt to close a CSV file while writing or reading failed.

S:

Continues processing.

O:

Determine whether another program is using the file being read or written.

KAVB6070-E

The number of window running exceeds the maximum value (value).

No new instance of window can be started because the instances of window that are running has reached the maximum.

S:

Ignores the operation.

O:

Close any unnecessary window that is running, and then perform the operation again.

KAVB6071-E

Performing this copy operation might take several minutes. Do you want to continue?

Copying with large numbers of monitoring nodes take time. This message confirms that you want to perform the copy.

S:

When the Yes button is clicked, the system performs the copy. When the No button is clicked, the system does not perform the copy.

KAVB6072-E

The following file is not supported:

file-name

The file file-name that was specified as a background image is an image file in an unsupported format or an image file that exceeds the maximum size (2,048 x 2,048 pixels).

S:

Ignores the operation.

O:

Change the background image selection to an image in a supported format (*.gif, *.jpg, or *.png) no larger than the maximum size (2,048 x 2,048 pixels).

KAVB6073-E

The background image file is invalid.

file-name

The file file-name that was specified as a background image is an image file in an unsupported format or an image file that exceeds the maximum size (2,048 x 2,048 pixels).

S:

Continues processing without displaying the background image.

O:

Change the background image selection to an image in a supported format (*.gif, *.jpg, or *.png) no larger than the maximum size (2,048 x 2,048 pixels).

KAVB6078-I

Do you want to change all child monitoring nodes to monitoring-or-not-monitoring?

Confirms that you want to change all child monitoring nodes to monitoring-or-not-monitoring.

S:

When the Yes button is clicked, the system updates the displayed properties and changes the statuses of the child monitoring nodes to monitoring-or-not-monitoring. When the No button is clicked, the system updates the open properties and does not change the statuses of the child monitoring nodes. When the Cancel button is clicked, the system does not update the properties and returns processing to the Properties window.

KAVB6079-I

Do you want to change monitoring-node and all child monitoring nodes to monitoring-or-not-monitoring?

Confirms that you want to change monitoring-node and all child monitoring nodes to monitoring-or-not-monitoring.

S:

When the Yes button is clicked, the system updates the displayed properties and changes the statuses of monitoring-node and all of its child monitoring nodes to monitoring-or-not-monitoring. When the No button is clicked, the system updates the statuses of the open properties other than the monitoring status, and does not change the monitoring status. When the Cancel button is clicked, the system does not update the properties and returns processing to the Properties window.

KAVB6082-E

A maximum of maximum-number event issue conditions can be specified.

The number of event issue conditions specified exceeds the maximum.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6083-W

If this operation is continued, the monitoring node type will become monitoring-node-type.

Do you want to continue?

Confirms that you want to change the monitoring node type to monitoring-node-type by performing the operation.

S:

When the Yes button is clicked, the system changes the monitoring node type to monitoring-node-type and continues the operation. When the No button is clicked, the system does not change the monitoring node type and does not continue the operation.

KAVB6085-E

The monitoring node name has not been entered.

The monitoring node name, which is a required item, has not been entered.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6086-E

Invalid individual conditions were specified.

Cause: comparison-condition condition for identical attribute already exists.

Invalid individual conditions were specified.

S:

Waits for re-entry of information.

O:

Correct the individual conditions as needed, and then re-enter them.

KAVB6087-E

data has not been entered.

The required item data has not been entered.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6088-E

The same condition-name has already been registered.

Duplicate conditions cannot be entered because condition-name is entered with an AND condition.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6090-E

condition-name is not specified correctly. The usable characters are usable-characters

The name must start with an upper-case character.

The specified condition-name contains an error.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6091-E

A status change condition with the same condition name is already registered.

Multiple status change conditions with the same condition name cannot be specified.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6092-W

Common conditions cannot be restored once deleted. Do you want delete the common condition common-condition-name?

Confirms that you want to delete the specified common condition.

S:

When the Yes button is clicked, the system deletes the common condition. When the No button is clicked, the system does not delete the common condition.

KAVB6093-E

The input range for condition-name is from minimum-value to maximum-value.

Values smaller than minimum-value or larger than maximum-value cannot be specified for condition-name.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6096-E

Please set the conditions of condition-name.

No conditions are specified for condition-name.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6097-E

value of condition-name allows up to maximum characters in total.

The total of value for condition-name exceeds maximum characters.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6099-E

A backslash (\) is entered alone. To specify a backslash, please enter two backslashes (\\).

A single backslash (\) is entered within a condition.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6100-E

More than maximum-number-of-items items of Visual Monitoring window information have been acquired.

Items beyond maximum-number-of-items+1 will not be displayed.

More than maximum-number-of-items items of Visual Monitoring window information have been acquired.

S:

Displays up to maximum-number-of-items and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6101-W

In the central console, processing cannot be performed during an event search.

Please wait until the event search finished.

processing cannot be performed because JP1/IM - Manager is executing an event search.

S:

Displays the Event Console window as the top window.

O:

Wait until the event search has finished.

KAVB6102-W

In the central console view, processing cannot be performed while saving the display event.

During output processing of a CSV file, a logout was executed by Central Scope - View, or a status change event search is running.

The following values are displayed in processing.

Logout

Status change event search

S:

Suspends processing of the logout or status change event search.

O:

Terminate the CSV output processing, and then retry the operation.

KAVB6103-E

Common condition of the selected status change condition is not found. Acquire the latest status.

Monitoring window

A common condition with the selected status change event could not be acquired. Another possibility is that the character string bold is not displayed.

Editing window

The latest definitions have not been acquired, or a common condition with the selected status change event could not be acquired.

S:

Cancels selection of common conditions and opens a window for setting status change conditions.

O:

Monitoring window

Use the data collection tool to collect data, and then contact a system administrator.

Editing window

Acquire the latest definitions. If the same message is displayed after acquiring the latest definitions, use the data collection tool to collect data, and then contact a system administrator.

KAVB6104-E

A system error occurred during a search.

A system error occurred during search processing.

S:

Suspends search processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6105-E

Property acquisition has failed.

An attempt to acquire a property failed because an error occurred at an unforeseen location.

S:

Suspends processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6106-E

An attempt to acquire the Visual Monitoring window has failed.

An attempt to acquire the Visual Monitoring window failed because an error occurred at an unforeseen location.

S:

Suspends processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6107-E

Guide acquisition has failed.

An attempt to acquire the guide failed because an error occurred at an unforeseen location.

S:

Suspends processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6108-W

There are 0 common conditions in the server.

Processing was executed to acquire a list of common conditions, but no common conditions were acquired from the server.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6109-W

There are 0 common conditions in the server.

After registering common conditions, processing was executed to acquire a list of common conditions, but no common conditions were acquired from the server.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6110-W

There are 0 common conditions in the server.

After deleting common conditions, processing was executed to acquire a list of common conditions, but no common conditions were acquired from the server.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6111-E

An attempt to acquire common conditions has failed.

An attempt to acquire common conditions failed.

S:

Suspends processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6112-E

A search cannot be performed from search-target (node-ID).

The search-target (node-ID) that you tried to start a search for may have been deleted.

S:

Cancels search processing.

O:

Specify the search start location again, and then search again.

KAVB6113-E

A common condition with the same common condition name is already registered.

The same common condition name cannot be specified again.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6114-W

Icons cannot be displayed because the selected monitoring group has more than number-of-child-nodes child nodes.

Details will be displayed.

This message will not displayed until the next startup.

Icons cannot be displayed because the number of child nodes must be less than number-of-child-nodes to display icons.

S:

Displays details. However, the system can display icons if a monitoring group with less than number-of-child-nodes child nodes is selected.

O:

Reduce the number of monitoring nodes in the monitoring group to less than number-of-child-nodes.

KAVB6120-E

Operations cannot be performed because another user is using CSV-file-name.

The file operation cannot be performed because another user is using CSV-file-name.

S:

Suspends the CSV file operation.

O:

Determine whether another user is using the CSV file, and then perform the operation again

KAVB6121-W

CSV-file-name cannot be locked.

An attempt to create a local file failed.

S:

Continues the CSV file operation.

O:

Confirm that you have permission to write to the target folder.

KAVB6193-E

The input range for condition-name is from minimum-value to maximum-value.

condition-name: invalid-input-value

Input exceeded the input range for condition-name.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6194-E

The condition-name condition is duplicated.

condition-name: invalid-input-value

The condition-name condition is duplicated.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6195-E

condition-name is not specified correctly.

Please set an 8-digit hexadecimal number.

condition-name: invalid-input-value

A condition name that is not an 8-digit hexadecimal number was specified.

S:

Waits for re-entry of information.

O:

Reconfigure the condition, and then retry the operation.

KAVB6196-E

A common event monitoring condition cannot be deleted because it is in use.

An attempt to delete a common event monitoring condition failed because the condition is in use.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the common event monitoring condition you tried to delete is not in use as a user monitoring object in a tree, and then retry the operation.

KAVB6210-E

A communication error occurred while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

Details: detailed-information

An attempt to connect to the specified host failed.

Detailed information:

N100: No connection host name was specified.

N101: A message that the ICMP port is unreachable was received at a connected datagram.

N104: Socket communication is not allowed by the security manager.

N105: Another communication error of unknown cause occurred.

N106: An attempt to log in after connection failed.

S:

Suspends processing to connect to the host.

O:

Check the following items, and then perform the operation again.

Was the correct connection host name entered?

Can the port number be used?

Is the connection host running?

Is there a problem communicating with the connection host?

If the communication encryption function is enabled at the connection host, has encrypted communication been configured in JP1/IM - View?

You can also use the jco_smpd_status command to confirm that that the connection host is running.

KAVB6211-E

An error occurred at input stream creation while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Perform the operation again.

KAVB6212-E

An error occurred in creation of the output stream while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Perform the operation again.

KAVB6213-E

A communication error occurred while attempting to establish a connection. The host name cannot be converted to an IP address.

Please confirm the host name.

Host name: connecting-host

Port number: connection-port-number

Details: detailed-information

An attempt to connect to the specified host failed.

Detailed information:

N102: The host IP address could not be identified.

N103: The IP address could not be resolved from the host name.

S:

Suspends processing to connect to the host.

O:

Check the following items, and then retry the operation.

Was the correct connection host name entered?

Can the port number be used?

Is the connection host running?

Is there a problem communicating with the connection host?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6214-E

A TCP communication error occurred while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Check the following items, and then retry the operation.

Was the correct connection host name entered?

Can the port number be used?

Is the connection host running?

Is there a problem communicating with the connection host?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6215-E

A communication error occurred while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Check the following items, and then retry the operation.

Was the correct connection host name entered?

Can the port number be used?

Is the connection host running?

Is there a problem communicating with the connection host?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6216-E

A communication error occurred while attempting to establish a connection.

Please confirm that the server has started up.

Port number: connection-port-number

Details: detailed-information

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Check the following items, and then retry the operation.

Was the correct connection host name entered?

Can the port number be used?

Is the connection host running?

Is there a problem communicating with the connection host?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6218-E

An error occurred at socket creation while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Check the following items, and then retry the operation.

Was the correct connection host name entered?

Can the port number be used?

Is the connection host running?

Is there a problem communicating with the connection host?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6219-E

An I/O error occurred at socket creation while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Check the following items, and then retry the operation.

Was the correct connection host name entered?

Can the port number be used?

Is the connection host running?

Is there a problem communicating with the connection host?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6220-E

An error occurred at timeout value setup while attempting to establish a connection.

Host name: connecting-host

Port number: connection-port-number

An attempt to connect to the specified host failed.

S:

Suspends processing to connect to the host.

O:

Collect data, and then contact a network administrator.

KAVB6240-E

An error occurred during data transmission.

Host name: connecting-host

Port number: connection-port-number

Details: detailed-information

Transmission processing failed during communications.

The possible causes are as follows:

Detailed information:

N201: No transmission data

N202: Generation of transmission data failed.

N203: Acquisition of transmission data failed.

N204: No output stream

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6241-E

A communication error occurred during transmission.

Host name: connecting-host

Port number: connection-port-number

A communication error occurred during transmission.

S:

Suspends processing.

O:

Check the following items, and then retry the operation.

Is the connection host running?

Is there a problem communicating with the connection host?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6250-E

An error occurred while receiving data.

Host name: connecting-host

Port number: connection-port-number

Details: detailed-information

Reception processing failed during communications.

The possible causes are as follows:

Detailed information:

N300: An invalid datagram was received.

N301: Acquisition of reception data failed.

N302: No input stream

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6251-E

A communication error occurred while receiving data.

Host name: connecting-host

Port number: connection-port-number

A communication error occurred while receiving data.

S:

Suspends processing.

O:

Check the following items, and then retry the operation.

Is the connection host running?

Is there a problem communicating with the connection host?

Has the upper limit for the number of instances of JP1/IM - View connected to the connection host been reached?

If the communication encryption function is enabled at the connection host, has encrypted communication been configured in JP1/IM - View?

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6252-E

A timeout occurred while receiving data.

Host name: connecting-host

Port number: connection-port-number

A time-out occurred while receiving data.

S:

Suspends processing.

O:

Check the following items, and then retry the operation.

Is the connection host running?

Is there a problem communicating with the connection host?

Is there an OS problem in the CPU and memory usage status?

Did a large disk I/O operation occur?

Alternatively, contact a network administrator.

You can also use the jco_smpd_status command to confirm that the connection host is running.

KAVB6299-E

A memory shortage occurred while receiving data.

A memory shortage occurred during communications.

S:

Suspends processing.

O:

Close all windows that can be closed, and then retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6300-E

CSV format is incorrect.

Details: detailed-information.

File name: file-name.

Error occurrence location: line-number line column-number

Processing could not continue due to an error in the CSV format.

S:

Suspends processing.

O:

Correct the file as instructed in the detailed information, and then retry the operation.

KAVB6301-E

A memory shortage occurred during CSV I/O processing.

File name: file-name

Processing could not continue due to a memory shortage during CSV I/O processing.

S:

Suspends processing.

O:

Close all windows that can be closed, and then retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6302-E

An I/O error occurred while parsing a CSV file.

File name: file-name

An I/O error occurred during analysis of a CSV file.

S:

Suspends processing.

O:

Make sure that the CSV file is closed, and then retry the operation.

KAVB6305-E

An attempt to reference common change conditions has failed.

An attempt to reference common change conditions failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6306-E

A system error occurred while configuring the Visual Monitoring window.

An attempt to configure the Visual Monitoring window failed due to an error.

S:

Suspends processing.

O:

Close the Visual Monitoring window, and then display it again. If the same message appears, use the data collection tool to collect data, and then contact a system administrator.

KAVB6307-W

Icons not linked with monitoring nodes was extracted.

Visual Monitoring window name: Visual-Monitoring-window-title

Monitoring nodes that are not linked to a monitoring tree were detected in the Visual Monitoring window information that was read.

S:

Continues processing.

O:

Use a Visual Monitoring window compatible with the current monitoring tree or use the original monitoring tree that created the Visual Monitoring window.

KAVB6308-E

A common change condition cannot be set.

An attempt to set common change conditions failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6309-E

The specified Visual Monitoring window information cannot be referenced.

Visual Monitoring window ID: Visual-Monitoring-window-ID

An attempt to reference Visual Monitoring window information (ID: Visual-Monitoring-window-ID) failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6310-E

Tree information cannot be set.

An attempt to set tree information failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6311-E

Tree information cannot be referenced.

TreeID: tree-ID

An attempt to reference tree information (ID: tree-ID) failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6312-E

Information that cannot be used in the connection destination server is included in the tree information.

For details, please refer to the log file.

File name: log-file-name

Processing could not continue because information that cannot be used in the connection destination server was included in the tree information.

The possible causes are as follows:

If the detail code is 0A, a background image was set up.

If the detail code is 0B, icon coordinates were set up.

If the detail code is 0C, the number of status change conditions exceeds the maximum of 4.

If the detail code is 0D, a condition other than Match was set in individual conditions for the status change conditions.

If the detail code 0E, a common condition that does not exist in the status change conditions was set up.

S:

Suspends processing.

O:

Correct the tree according to the detailed information below.

If the detail code 0A, in the Property window click Background Image Setting, and in the window that is displayed click No background image.

If the detail code 0B, select the parent monitoring node, and then click Set in Equal Intervals.

If the detail code 0C, set the number of status change conditions to 4.

If the detail code 0D, change the individual conditions of the status change conditions to Match.

If the detail code 0E, acquire the latest definitions. Alternatively, reset the common conditions.

KAVB6401-E

An exception (exception-class-name) occurred and message construction failed.

An exception occurred, but an attempt to construct a message failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6441-E

An error occurred while creating the log file "log-file-name".

An attempt to create a log file failed.

S:

Suspends creation of the log file and continues processing.

O:

Make sure that the file system or device to be written to has sufficient free space and that the log file has access permission, and then contact a system administrator.

KAVB6442-E

An error occurred while outputting to the log file "log-file-name".

An attempt to write to a log file failed.

S:

Suspends write processing to the log file and continues processing.

O:

Make sure that the file system or device to be written to has sufficient free space and that the log file has access permission, and then contact a system administrator.

KAVB6500-E

A system error occurred during internal processing.

A system error occurred during data processing.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6501-E

A memory shortage occurred during internal processing.

A memory shortage occurred during data processing.

S:

Suspends processing.

O:

Close all windows that can be closed, and then retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6502-E

A system error occurred during internal processing.

A system error occurred during data processing.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6503-E

A memory shortage occurred during internal processing.

A memory shortage occurred during data processing.

S:

Suspends processing.

O:

Close all windows that can be closed, and then retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB6504-E

An error occurred while sending data.

Details: detailed-information

An error occurred while creating a transmission datagram.

Detailed information:

Datagram type

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6505-E

An error occurred while receiving data.

Details: detailed-information

An error occurred while parsing a received datagram.

Detailed information:

Datagram type

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6506-E

An error occurred while receiving data.

Details: detailed-information-1

Details: detailed-information-2

An error occurred while parsing a received datagram.

Detailed information:

Datagram type

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6507-E

An error occurred while receiving error messages.

Details: detailed-information

An error occurred while parsing an error message datagram.

Detailed information:

Datagram type

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6508-E

An irrecoverable system error occurred. Please log in again.

An unrecoverable system error occurred. Log in again.

S:

Suspends processing.

O:

Restart JP1/IM - Manager.

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6509-E

A monitoring node was not found. Please acquire the latest monitoring tree.

A monitoring node may have been deleted from the monitoring tree.

S:

Suspends processing.

O:

Monitoring Tree window

On the menu bar, click Update Tree to Latest Status.

Monitoring Tree (Editing) window

Create a new tree.

KAVB6550-E

An error occurred when reading the system environment setup file.

Details: Row line-number

An error occurred while reading the system environment setup file.

Detailed information:

Line number where error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6551-E

An error occurred when reading the system environment setup file.

Details: item

An error occurred while reading the system environment setup file.

Detailed information:

Item where error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6560-E

An error occurred when reading the user environment setup file.

Details: Row line-number

An error occurred while reading the user environment setup file.

Detailed information:

Line number where error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6561-E

Error occurred when reading the setup file of user environment.

Details: item

An error occurred while reading the user environment setup file.

Detailed information:

Item where error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6570-E

An error occurred when reading the system monitoring object definition file.

Details: Row line-number

An error occurred while reading the system monitoring object definition file.

Detailed information:

Line number where error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6571-E

An error occurred when reading the system monitoring object definition file.

Details: item

An error occurred while reading the system monitoring object definition file.

Detailed information:

Item where error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB6581-W

The definition file (file-name) corresponding to the language type does not exist.

The definition file (file-name) corresponding to the language type does not exist.

S:

Continues processing to display the window.

O:

Check whether the definition file indicated by file-name exists.

KAVB6601-E

An error occurred during the initialization of the communication encryption function for JP1/IM - View. (cause = cause, directory = directory)

An error occurred during initialization of the communication encryption function for JP1/IM - View.

S:

Suspends processing.

O:

If No root authentication certificates were found. is displayed for cause, check the following, and then log in again:

Check whether the root certificate exists.

• If the root certificate exists, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• If there is no root certificate, put a root certificate in place.

If None of the root authentication certificates could be read. is displayed for cause, check the following, and then log in again:

• Check whether the root certificate exists. If the root certificate exists, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• Check for problems in the file of the root certificate.

• Check the Windows event log to determine if a shortage has occurred in an OS resource such as file descriptors.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If The placement directory for root authentication certificates could not be found. is displayed for cause, create the directory, and then place the certificate there.

KAVB6602-E

Failed to encrypt communications by using the communication encryption function for JP1/IM - View. (host name of connection destination = connection-destination-host-name, cause = cause)

An attempt to encrypt communications by using the communication encryption function of JP1/IM - View failed.

S:

Suspends processing.

O:

If The CN or SAN of the server authentication certificate does not match with the host name of the connection destination. is displayed for cause, verify that the CN or SAN in the server certificate of the manager host at the connection destination matches the connection destination host name of the Central Scope viewer, and then log in again.

If A communication error occurred. is displayed for cause, check the following, and then log in again. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

• Check whether the communication encryption function is enabled at the manager host of the connection target. If it is, confirm that the manager host name of the connection destination is not indicated in the host configuration file for non-encrypted communication.

• Check whether Failed to read some of the root authentication certificates was output to the integrated trace log. If so, take the corrective action given for that message.

• Check whether the root certificate that corresponds to the server certificate of the manager host at the connection destination has been placed in JP1/IM - View. If not, place it at the host.

• Check whether the server certificate of the manager host at the connection destination is still valid. If it is no longer valid, update the server certificate.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB6603-W

Failed to read some of the root authentication certificates used by the communication encryption function for JP1/IM - View. (directory = directory-name, file = file-name, file-name, ...)

An attempt by the communication encryption function for JP1/IM - View to read some of the root certificates to be used failed.

S:

Ignores the file or files that failed to be read and continues processing.

O:

Check the items below, and then log in again. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

Check the Windows event log to see if a shortage has occurred in an OS resource such as file descriptors.

Check for problems in the file of the root certificate.

KAVB6604-W

The root authentication certificate used by the communication encryption function for JP1/IM - View is no longer valid. (directory = directory-name, file = file-name)

The root certificate to be used by the communication encryption function for JP1/IM - View has expired.

S:

Continues processing.

O:

Check whether operating with an expired root certificate will cause a problem. If it will, update the root certificate.

KAVB6610-E

A non-encryption communication host configuration file for JP1/IM - View was not found. (file = file-name)

A non-encryption communication host configuration file for JP1/IM - View was not found.

S:

Suspends processing.

O:

Check the following, and then log in again:

Check whether the non-encryption communication host configuration file exists. If it does not, create the file.

Check whether you have read permission for the non-encryption communication host configuration file. If not, set read permission for the file.

KAVB6611-E

The non-encryption communication host configuration file for JP1/IM - View failed to load. (file = file-name)

An attempt to read a non-encryption communication host configuration file for JP1/IM - View failed.

S:

Suspends processing.

O:

Check the Windows event log to determine if a shortage has occurred in an OS resource such as file descriptors.

If no shortage has occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB6612-E

The first line of the non-encryption communication host configuration file for JP1/IM - View is not "[NO_SSL_HOST]". (file = file-name)

[NO_SSL_HOST] is not entered on the first line of a non-encryption communication host configuration file for JP1/IM - View.

S:

Suspends processing.

O:

Enter [NO_SSL_HOST] on the first line of the non-encryption communication host configuration file, and then log in again.

KAVB6613-E

The number of manager host names specified in the non-encryption communication host configuration file for JP1/IM - View exceeds the maximum (maximum). (file = file-name)

The number of manager host names specified in the non-encryption communication host configuration file for JP1/IM - View exceeds the maximum.

S:

Suspends processing.

O:

Carefully review the number of manager host names in the non-encryption communication host configuration file. Correct the problem, and then log in again.

KAVB6614-E

The length of a manager host name specified in the non-encryption communication host configuration file for JP1/IM - View exceeds the maximum (maximum). (line number = line-number, file = file-name)

The length of a manager host name specified in the non-encryption communication host configuration file for JP1/IM - View exceeds the maximum.

S:

Suspends processing.

O:

Correct the manager host name on the specified line of the non-encryption communication host configuration file, and then log in again.

KAVB6615-E

The syntax for asterisks (*) in the manager host name for the non-encryption communication host configuration file for JP1/IM - View is invalid. (file = file-name)

An asterisk (*) was incorrectly entered for the manager host names in the non-encryption communication host configuration file for JP1/IM - View.

S:

Suspends processing.

O:

Correct the non-encryption communication host configuration file, and then log in again.

To set an asterisk (*) for the manager host names, enter a single asterisk on the line that follows [NO_SSL_HOST].

Note that if you enter an asterisk (*), communication with all manager hosts will be in the clear (will not be encrypted).

KAVB6616-E

A manager host name in the non-encryption communication host settings file is duplicated. (line number = line-number, file = file-name)

A manager host name specified in the non-encryption communication host configuration file for JP1/IM - View is duplicated.

S:

Suspends processing.

O:

Correct the manager host name on the specified line of the non-encryption communication host configuration file, and then log in again.

2.8 Messages related to Central Scope Service (KAVB7001 to KAVB7999)

KAVB7001-I

The JP1/IM - Central Scope daemon has started. (Logical hostname: logical-host-name)

Central Scope Service started. If it is running on a physical host, logical-host-name is set to JP1_DEFAULT.

S:

Starts Central Scope Service.

KAVB7002-I

The JP1/IM - Central Scope daemon terminated normally. (Logical hostname: logical-host-name)

Central Scope Service stopped normally. If it is running on a physical host, logical-host-name is set to JP1_DEFAULT.

S:

Stops Central Scope Service normally.

KAVB7003-E

The JP1/IM - Central Scope daemon terminated abnormally. (Logical hostname: logical-host-name, End code: reason-code)

Central Scope Service stopped abnormally. If it is running on a physical host, logical-host-name is set to JP1_DEFAULT.

S:

Stops Central Scope Service abnormally.

O:

Check the system status based on the reason code. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 4

Description: An attempt to initialize the JP1/Base communications base failed.

Action: Refer to the JP1/Base User's Guide to confirm that the communications base is set correctly.

Reason code: 7

Description: An ANSI exception occurred during startup processing.

Action: Make sure that memory or resources are sufficient.

Reason code: 8

Description: An HCCLib exception occurred during startup processing.

Action: Make sure that memory or resources are sufficient.

Reason code: 9

Description: An error occurred during Central Scope Service initialization.

Action: Take the corrective action given for the message that was output preceding this message. It is also possible that the settings for the communication encryption function were changed to invalid values after JP1/Base started up. Stop JP1/IM - Manager and JP1/Base, carefully review the communication encryption function settings and, if necessary, correct them. Then, restart JP1/Base and JP1/IM - Manager.

Reason code: 10

Description: Startup notification could not be sent to the process management daemon.

Action: Determine whether the daemon was started from a start script (in Windows, a service) rather than directly.

Reason code: 255

Description: A problem occurred while Central Scope Service was running, and the service stopped abnormally.

Action: Take the corrective action given for the message that was output preceding this message.

KAVB7004-E

JP1/IM - Central Scope daemon will now stop because the logical hostname is invalid.

Central Scope Service will stop because the logical host name received from the process management daemon was invalid.

S:

Stops Central Scope Service.

O:

Check the logical host name definitions for errors.

KAVB7005-E

The JP1/IM - Central Scope daemon will now stop because the initialization of the JP1/Base common configuration failed.

Central Scope Service will stop because an attempt to initialize the JP1/Base common definitions failed.

S:

Stops Central Scope Service.

O:

Check the JP1/Base configuration for errors.

KAVB7006-E

The JP1/IM - Central Scope daemon will now stop because an attempt to initialize the internal trace log has failed.

Central Scope Service will stop because an attempt to initialize the internal log file failed.

S:

Stops Central Scope Service.

O:

Determine whether JP1/Base was uninstalled after installing JP1/IM - Manager. If it was not uninstalled, check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7007-E

The JP1/IM - Central Scope daemon will now stop because an attempt to initialize the message log file has failed.

Central Scope Service will stop because an attempt to initialize the log file for messages with IDs failed.

S:

Stops Central Scope Service.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7100-I

The initialization of the JP1/Base communication base has been completed.

The initialization of the JP1/Base communication base is complete.

S:

Completes initialization of the JP1/Base communication base.

KAVB7101-W

The jp1hosts cannot be validated, because the definition of jp1host is invalid.

jp1hosts cannot be validated because the definitions in jp1hosts are incorrect.

S:

Continues processing.

O:

Check the definitions in jp1hosts for errors.

KAVB7102-E

An attempt to initialize the JP1/BASE communication base failed. (Error code: reason-code)

Central Scope Service will stop because an attempt to initialize the JP1/BASE communication base failed.

S:

Stops Central Scope Service.

O:

Check the JP1/Base configuration for errors, and take action according to the error code.

Reason code: -1

Description: No logical host key exists in the common definitions.

Action: Refer to the JP1/Base User's Guide to determine whether logical host definitions exist for services started up with common definitions.

Reason code: -2

Description: JP1/Base communications base definition information is invalid.

Action: Refer to the JP1/Base User's Guide to determine whether there are errors in the JP1/Base communications base definition information.

Reason code: -4

Description: No logical host key exists in the common definitions, and the jp1hosts definition is incorrect.

Action: Refer to the JP1/Base User's Guide to determine whether logical host definitions exist for services started up with common definitions. Also check the jp1hosts definition for errors.

Reason code: -5

Description: JP1/Base communications base definition information is invalid, and the jp1hosts definition is incorrect.

Action: Refer to the JP1/Base User's Guide to determine whether there are errors in the JP1/Base communications base definition information and jp1hosts definition.

KAVB7103-W

The JP1/IM - Central Scope daemon will be started using the default port number (20305), because an attempt to acquire the port number has failed.

Central Scope Service will start using the default port number (20305) because an attempt to acquire a port number failed.

S:

Continues processing.

O:

Determine whether there are errors in the service file definitions.

KAVB7104-W

The JP1/IM - Central Scope daemon will be started using the default port number (20305), because OS reserves the defined port number (within 1023).

Central Scope Service will start using the default port number (20305) because the OS reserves the acquired port number (1023 or lower).

S:

Continues processing.

O:

Check the service file definitions for errors.

KAVB7105-I

The data in the JP1/IM - Central Scope daemon will be updated due to the reload request from the process management daemon.

The data in Central Scope Service is updated due to a reload request from the process management daemon.

S:

Updates the data in Central Scope Service.

KAVB7106-I

The updating of the data within the JP1/IM - Central Scope daemon succeeded.

Updating of the data in Central Scope Service was successful.

S:

Finishes updating the data in Central Scope Service normally.

KAVB7107-W

An attempt to update the data within JP1/IM - Central Scope has failed. The processing will continue using the old data.

An attempt to update the data in Central Scope Service failed. Processing continues using the previous data.

S:

Continues processing.

O:

Some data was not reloaded. Take the corrective action given for the message that was output preceding this message.

KAVB7108-I

The JP1/IM - Central Scope daemon will be stopped because a stop request was sent from the process management daemon.

Central Scope Service will stop because a stop request was sent from the process management daemon.

S:

Begins stop processing for Central Scope Service.

KAVB7109-E

The JP1/IM - Central daemon will be stopped because an invalid request was sent from the process management daemon.

Central Scope Service will stop because an invalid request was sent from the process management daemon.

S:

Begins stop processing for Central Scope Service.

O:

Process management daemon operation is abnormal. Take the corrective action given for the message that was output preceding this message.

KAVB7110-E

An attempt to report the startup to the process management daemon failed.

An attempt to report the startup to the process management daemon failed.

S:

Stops Central Scope Service.

O:

Process management daemon operation is abnormal. Take the corrective action given for the message that was output preceding this message.

KAVB7111-I

The creation of all the threads waiting for TCP/IP communication succeeded.

The creation of all threads waiting for TCP/IP communication was successful.

S:

The creation of all threads waiting for TCP/IP communication succeeded.

KAVB7112-W

The process continues even though a part of a thread waiting for TCP/IP communication has failed.

An attempt to create part of a thread waiting for TCP/IP communication failed, and processing continues.

S:

An attempt to create part of a thread waiting for TCP/IP communication failed. Continues processing.

O:

An attempt to create a TCP/IP socket failed for some IP addresses. Refer to the KAVB7115-E message that was output preceding this message, and then determine whether the problematic IP addresses can be used.

KAVB7113-E

The JP1/IM - Central Scope daemon will now stop because the creation of all the threads waiting TCP/IP communication has failed.

Central Scope Service will stop because an attempt to create all threads waiting for TCP/IP communication failed.

S:

Stops Central Scope Service.

O:

Refer to the KAVB7115-E message that was output preceding this message, and then determine whether the problematic IP addresses can be used.

KAVB7114-I

The creation of the threads waiting for the TCP/IP communication by IP address (IP-address) succeeded.

The creation of threads waiting for TCP/IP communication by IP address was successful.

S:

The creation of threads waiting for TCP/IP communication by IP address (IP-address) was successful.

KAVB7115-E

An attempt to create the thread for waiting for the TCP/IP communication by the IP address (IP-address) has failed.

An attempt to create a thread waiting for TCP/IP communication by IP address failed.

S:

Fails to create a thread waiting for TCP/IP communication by IP address.

O:

Make sure that you can use IP addresses on the server system that will run JP1/IM - Manager. Also make sure that the definitions of server names and IP addresses on the system and JP1/Base are correct.

KAVB7116-E

The JP1/IM - Central Scope daemon was stopped, because the database version is too old.

Service startup was canceled because the database version is not supported.

S:

Stops Central Scope Service.

O:

Convert the database by running the jp1csverup command (on a physical host) or the jp1cshaverup command (on a logical host).

KAVB7117-I

Startup will use the environment variable LANG (environment-variable-LANG) and the character encoding (character-code).

A server or command starts with an environment variable LANG (environment-variable-LANG) and character code (character-code). Windows normally does not output environment variable LANG.

S:

Continues processing.

KAVB7118-E

An attempt to set the message file has failed.

An attempt to set the message file failed.

S:

Suspends processing.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7119-E

An attempt to initialize the database has failed.

An attempt to initialize the database failed.

S:

Stops Central Scope Service.

O:

An attempt to build the database may have failed at installation. Check the installation log, execute the jcsdbsetup command to rebuild the database, and then restart JP1/IM - Manager. If the database was built correctly, there may be insufficient kernel parameters. Check the settings for kernel parameters, and then restart JP1/IM - Manager.

KAVB7120-E

An attempt to initialize the plugin service has failed. (err code: reason-code)

Central Scope Service will stop because an attempt to initialize the JP1/Base plug-in service failed.

S:

Stops Central Scope Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7121-W

The database will be recovered from the backup because the database is corrupt.

The database will be recovered from backup because damage to the database was detected when Central Scope Service started.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7122-E

The JP1/IM-Central Scope daemon will be stopped because an attempt to recover the database failed. (Cause: reason-code)

An attempt to recover the database failed because damage to the database was detected when Central Scope Service started. Central Scope Service stops.

S:

Stops Central Scope Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7123-I

Startup will use the monitored object DB version CSV-version-of-monitored-object-DB.

Startup will use the monitored object DB version CSV-version-of-monitored-object-DB.

S:

Continues processing.

KAVB7124-W

Startup will use compatibility mode.

Startup will use compatibility mode. Only functionality predating the version upgrade can be used.

S:

Continues processing.

O:

To use all functionality from after the version upgrade, convert the database by executing the jp1csverup command (for a physical host) or the jp1cshaverup command (for a logical host).

KAVB7127-E

The event monitoring thread ended abnormally (Cause:reason-code)

The service stopped because an abnormality was detected in the event monitoring thread.

S:

Stops the service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7128-E

An attempt to initialize the event monitoring has failed because the memory was insufficient.

An attempt to initialize event monitoring while starting the service failed because the memory was insufficient.

S:

Stops Central Scope Service.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7129-E

An attempt to initialize the event monitoring has failed because the resources were insufficient.

An attempt to initialize event monitoring while starting the service failed because resources such as file descriptors were insufficient.

S:

Stops Central Scope Service.

O:

Make sure that system resources such as file descriptors are sufficient, and then restart JP1/IM - Manager.

KAVB7130-E

An attempt to initialize the event monitoring has failed because the IM-CC (event flow control) was not started.

An attempt to initialize event monitoring while starting the service failed because JP1/IM - Manager (event flow control) stopped or was not running.

S:

Stops the service.

O:

Make sure that JP1/IM - Manager (event flow control) is running, and then restart JP1/IM - Manager.

KAVB7131-E

An attempt to initialize the event monitoring has failed. (Cause: reason-code)

An attempt to initialize event monitoring while starting the service failed.

S:

Stops the service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7132-E

An attempt to monitor the event monitoring has failed because the memory was insufficient.

Memory became insufficient during event monitoring, preventing event monitoring. When the memory insufficiency is resolved, event monitoring will continue.

S:

Event monitoring continues.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7133-E

An attempt to monitor the event has failed. (Cause:reason-code)

An attempt to monitor an event failed.

S:

Event monitoring continues.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7134-E

The event (event-ID) has failed to change the node condition because the memory was insufficient

The received event failed to change the node status condition because a memory shortage occurred.

S:

Cancels the status change of the monitoring node by the received event and continues event monitoring.

O:

Check the free space in system memory., Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7135-E

The event (event-ID) has failed to change the node condition because the database was not accessible.

The event failed to change the node status condition because the database was not accessible.

S:

Cancels the status change of the monitoring node by the received event and continues event monitoring.

O:

Check access permissions for database files and directories.

KAVB7136-E

The event (event-ID) has failed to change the node condition. (Cause:reason-code).

The event could not change the node status condition.

S:

Cancels the status change of the monitoring node by the received event and continues event monitoring.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7137-E

An attempt to create the condition change event message for the monitoring node (node name: node-ID) has failed because the memory was insufficient.

The status change of the monitoring node was successful, but the message for the status change event could not be created because a memory shortage occurred.

S:

Cancels issuing of the status change event set for the monitoring node by the received event and continues event monitoring.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7138-E

An attempt to create the condition change event message for the monitoring node (node name: node-ID) has failed. (Cause: reason-code)

The status change of the monitoring node was successful, but the message for the status change event could not be created.

S:

Cancels issuing of the status change event set for the monitoring node by the received event and continues event monitoring.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7139-W

The extended information of the monitoring node (node-name) was dropped because the size of the received event is too large (event-ID).

The monitoring node whose status was changed could not be embedded in the status change event because the size of the extended information of the received event was too large. The part that exceeded the maximum size (10 kilobytes) was dropped.

S:

Continues event monitoring.

O:

If no attempt is made to access the extended information of the event that was dropped, no action is necessary. If you must access the extended information of the event that was dropped, access the directly received event instead.

KAVB7140-E

The status change event of the node (node-name) was not issued because the memory was insufficient.

The status change of the monitoring mode was successful, but the status change event was not issued because a memory shortage occurred.

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7141-E

The status change event of the node (node-name) was not issued because the resource were insufficient

The status change of the monitoring mode was successful, but the status change event could not be issued because resources such as file descriptors were insufficient.

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Make sure that system resources such as file descriptors are sufficient, and then stop unnecessary processes.

KAVB7142-E

The status change event of the node (node-name) was not issued. (Cause:reason-code).

The status change of the monitoring mode was successful, but the status change event could not be issued.

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Check system conditions according to the error codes. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 10 IMEV_S_PARAM_ERROR

Description: Parameter of Event Service API is invalid.

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Reason code: 11 IMEV_S_SEQUENCE_ERROR

Description: Issue sequence of Event Service API is invalid.

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Reason code: 40 IMEV_S_CONNECT_ERROR

Description: Cannot connect to Event Service.

Action: Make sure that JP1/Base (Event Service) is running.

Reason code: 43 IMEV_S_IO_ERR

Description: I/O error occurred in communication with Event Service.

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Reason code: 51 IMEV_S_NOMEMORY

Description: Memory insufficient.

Action: Check system memory.

Reason code: 52 IMEV_S_MAXOPEN

Description: The system could not connect to Event Service because the number of open files reached its limit.

Action: Check the system's limit value for the number of open files.

Reason code: 60 IMEV_S_NOT_LOADING

Description: Communication with Event Service has not been initialized.

Action: Determine whether JP1/Base has been installed.

Reason code: 70 IMEV_S_SYSTEM_ERROR

Description: A system error occurred in Event Service API.

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7144-E

An attempt to monitor the event has failed because the resources were insufficient.

An attempt to monitor the event failed because resources such as file descriptors were insufficient.

S:

Cancels reception of the event and continues event monitoring.

O:

Make sure that system resources such as file descriptors are sufficient, and stop unnecessary processes.

KAVB7145-E

An attempt to monitor the event has failed because it was not possible to connect with the event flow control.

An attempt to monitor the event failed because it was not possible to connect to JP1/IM - Manager (event flow control).

S:

Cancels reception of the event and continues event monitoring.

O:

Make sure that JP1/IM - Manager (event flow control) is running.

KAVB7146-E

An attempt to monitor the event has failed because the event could not be received.

Initialization of the event has failed because the system could not connect to JP1/Base (Event Service control).

S:

Stops the service.

O:

Make sure that JP1/Base (Event Service control) is running, and then restart Central Scope Service.

KAVB7148-E

Status change event for Node: node-name can't be launched. Because connection failed with Event service.

The status change of the monitoring mode was successful, but no status change event could be issued because the system could not connect to JP1/Base (Event Service control).

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Make sure that JP1/Base (Event Service control) is running.

KAVB7150-I

The TCP/IP communication waiting thread started.

The TCP/IP communication waiting thread has started.

S:

Starts the TCP/IP communication waiting thread.

KAVB7151-I

The TCP/IP communication waiting thread terminated normally.

The TCP/IP communication waiting thread ended normally.

S:

Terminates the TCP/IP communication waiting thread normally.

KAVB7152-E

The TCP/IP communication waiting thread terminated abnormally.

The TCP/IP communication waiting thread ended abnormally.

S:

Stops Central Scope Service.

O:

Take the corrective action given for the message that was output preceding this message.

KAVB7153-W

The connection from JP1/IM - View will now be closed because the number of connection requests exceeds the maximum (64).

No further connections can be made because more than 64 JP1/IM - View units are connected.

S:

Closes the connection to JP1/IM - View.

O:

No new connections can be made. Close any unnecessary connections, and then reconnect to JP1/IM - View.

KAVB7154-W

An attempt too generate the communication request processing thread has failed, because there are not enough resources. The connection from JP1/IM - View will now be closed.

An attempt to generate the communication request processing thread failed because resources were insufficient.

S:

Closes the connection to JP1/IM - View.

O:

No new connections can be made. Exit unnecessary applications to resolve the resource insufficiency or close any unnecessary connections, and then re-connect to JP1/IM - View.

KAVB7155-E

The connection from JP1/IM - View will now be closed because the protocol was incorrect.

The connection to JP1/IM - View closed because the protocol was incorrect.

S:

Closes the connection to JP1/IM - View.

O:

Determine whether the settings of the communication encryption function were changed after JP1/IM - Manager was started up.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB7156-E

The request processing object cannot be created because an unsupported request has been sent from JP1/IM - View.

A request could not be processed because an unsupported request was sent from JP1/IM - View.

S:

Closes the connection to JP1/IM - View.

O:

Confirm that the version of JP1/IM - Manager is the version required by JP1/IM - View.

KAVB7157-E

The connection from JP1/IM - View will now be closed because an attempt to create the request processing object has failed.

The connection to JP1/IM - View closes because an attempt to create a request processing object failed.

S:

Closes the connection to JP1/IM - View.

O:

Confirm that the version of JP1/IM - Manager is the version required by JP1/IM - View.

KAVB7158-E

The connection from JP1/IM - View will now be closed because the login authentication has not been performed.

The connection to JP1/IM - View closes because the login authentication was not performed.

S:

Closes the connection to JP1/IM - View.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7159-E

The connection from JP1/IM - View will now be closed because an error occurred during the request processing.

The connection to JP1/IM - View closes because an error occurred during request processing.

S:

Closes the connection to JP1/IM - View.

O:

Take the corrective action given for the message that was output preceding this message.

KAVB7160-W

The communication process will now end because the closing of the connection to JP1/IM-View has been detected.

The communication process stopped because closing of the connection to JP1/IM - View was detected.

S:

Terminates the communication process with JP1/IM - View.

O:

Determine whether JP1/IM - View has generated a time-out or whether there is a problem in the communication environment.

KAVB7161-W

The communication process will now end because the waiting request from JP1/IM - View timed out.

The communication process stopped because a waiting request from JP1/IM - View timed out.

S:

Terminates the communication process with JP1/IM - View.

O:

Determine whether there is a problem in the communication environment.

KAVB7175-W

JP1/IM-CS (JP1/IM-Central-Scope-version) cannot process the request from JP1/IM-View (JP1/IM-View-version).

Requests from JP1/IM - View JP1/IM-View-version cannot be processed.

S:

Terminates the communication process with JP1/IM - View.

O:

Check the JP1/IM - View version.

KAVB7176-E

JP1/IM-CS (JP1/IM-Central-Scope-version) cannot process the request from JP1/IM-View (JP1/IM-View-version).

Requests from JP1/IM - View JP1/IM-View-version cannot be processed.

S:

Terminates the communication process with JP1/IM - View.

O:

Check the JP1/IM - View version.

KAVB7177-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be operated during backup, reason-code)

An operation request from JP1/IM - View failed because a database operation failed during backup.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7178-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: Memory was insufficient during backup.)

An operation request from JP1/IM - View failed because memory became insufficient during backup.

S:

Cancels the requested operation.

O:

Stop the service, and check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory.

The database may have been corrupted. After restoring the database, restart the service.

KAVB7179-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found during backup.)

An operation request from JP1/IM - View failed because a database file was not found during backup.

S:

Cancels the requested operation.

O:

Determine whether the database file and directory exist. Stop the service, create a new database, and then restart the service.

KAVB7180-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient during backup.)

An operation request from JP1/IM - View failed because disk space became insufficient during backup.

S:

Cancels the requested operation.

O:

Check the free space in the disk where the database is stored, and delete any unnecessary files.

The database may have been corrupted. Stop the service, restore the database, and then restart the service.

KAVB7182-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be accessed during backup.)

An operation request from JP1/IM - View failed because an access of the database failed during backup.

S:

Cancels the requested operation.

O:

Check access permissions for database files and directories.

KAVB7183-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: Resources were insufficient during backup.)

An operation request from JP1/IM - View failed because resources such as file descriptors were insufficient.

S:

Cancels the requested operation.

O:

Make sure that file descriptors are sufficient, and stop unnecessary processes.

The database may have been corrupted. Stop the service, restore the database, and then restart the service.

KAVB7184-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: Memory was insufficient.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because of insufficient memory. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Stop the service, and check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory.

The database may have been corrupted. After restoring the database, restart the service.

KAVB7185-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient to update the database.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because of insufficient disk space. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Check the free space in the disk where the database is stored, and delete any unnecessary files.

The database may have been corrupted. Stop the service, restore the database, and then restart the service.

KAVB7187-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be accessed.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because an access of the database failed during backup. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Check access permissions for database files and directories.

KAVB7188-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because a database file was not found. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Determine whether the database file and directory exist. Stop the service, create a new database, and then restart the service.

KAVB7189-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be operated. error-code-for-recovery-failure) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because an attempted operation using the database failed. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7190-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: the memory is insufficient.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because of insufficient memory, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7191-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient to update the database.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because of insufficient disk space, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7192-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be accessed.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because an access of the database failed, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7193-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because a database file was not found, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7194-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be operated, reason-code), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because an operation using the database failed, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7196-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The requested operation is not authorized for the node ID (node-ID) )

The node ID (node-ID) is a virtual root node. Virtual root nodes cannot handle operation requests (request-name) from JP1/IM - View.

S:

Continues processing.

O:

Virtual root nodes cannot handle operation requests (request-name). Specify a child node of the virtual root node, and then perform the operation again.

KAVB7197-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The JP1/IM -View version (version-for-View) is not compatible with the JP1/IM-CS monitored object DB version (monitored-object-DB-version) )

JP1/IM - Central Scope could not execute the operation request from JP1/IM - View because the JP1/IM - View version is not compatible with the JP1/IM - Central Scope monitored object DB version.

S:

Continues processing.

O:

Recheck the JP1/IM - View version and JP1/IM - Central Scope monitored object DB version, and then perform the operation from a JP1/IM - View that is compatible with the monitored object DB version of the JP1/IM - Central Scope. See 10.2.2 Connectivity between JP1/IM products in the manual JP1/Integrated Management 2 - Manager Overview and System Design Guide for combinations of JP1/IM - View and JP1/IM - Central Scope that can work together.

KAVB7198-W

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The status of the node ID (monitoring-node-ID) could not be changed to the monitored status because its group is in the unmonitored status)

The JP1/IM - View operation request failed because the monitoring group above the monitoring node on which the operation was attempted is in non-monitoring status. When the higher monitoring group is in non-monitoring status, the monitoring node cannot change from monitoring status to non-monitoring status. Operation permission for the higher monitoring group is necessary to change a monitoring node from monitoring status to non-monitoring status.

S:

Continues processing.

O:

Perform the operation as a JP1 user that has operation permission for the monitoring group above the monitoring node whose operation was attempted.

KAVB7201-E

A system error occurred while an operation request (login process) from JP1/IM-View was executing. (Detailed information: An error occurred during the login processing)

An error occurred during login processing.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7202-E

An attempt to authenticate the user has failed.

An attempt to authenticate the user failed.

S:

Waits for re-entry of information.

O:

Check the user name and password, and then retry the operation.

KAVB7204-E

JP1/IM-CS cannot connect to the authentication server.

Cannot connect to the authentication server.

S:

Waits for re-entry of information.

O:

Check the connection path to the authentication server (authentication server address, network, etc.). If using the communication encryption function, check whether the settings of the function are incorrect. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

KAVB7206-E

A system error occurred the operation request (logout processing) of JP1/IM-View was executing. (Detailed information: An error occurred during the logout processing)

An error occurred during logout processing.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7207-E

A system error occurred while the operation request (logout processing) of JP1/IM-View was executing. (Detailed information: A communication error occurred between the connecting host and the authentication server)

A communication error occurred between the connecting host and the authentication server.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7209-E

A system error occurred while the operation request (user list acquiring processing) of JP1/IM-View was executing. (Detailed information: An error occurred in user list acquiring processing)

An error occurred in user list acquisition processing.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7210-E

A system error occurred while the operation request (user list acquiring processing) of JP1/IM-View was executing. (Detailed information: An attempt to acquire the user list has failed)

A user list could not be acquired.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7212-E

A system error occurred while the operation request (user environment acquiring processing) of JP1/IM-View was executing. (Detailed information: An error occurred in user environment acquiring processing)

An error occurred in user environment settings acquisition processing.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7213-E

A system error occurred while the operation request (user environment acquiring processing) of JP1/IM-View was executing. (Detailed information: The user environment file does not exist)

A user environment settings file does not exist.

S:

Waits for re-entry of information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7232-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View.

An operation request from JP1/IM - View could not be executed due to an error.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the log for the message that was output preceding this message, and take the corrective action given for that message.

KAVB7233-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (cause: the data format was invalid)

The format of the operation request data from JP1/IM - View is invalid.

S:

Cancels the requested operation and continues to accept requests.

O:

Determine whether there was an invalid access of the server system where JP1/IM - Manager is running. Also check the JP1/IM - View log to make sure that no problems have occurred. If the server system and log show no problems, a system error may have occurred. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7234-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The tree ID (tree-ID) was not registered)

The operation request data from JP1/IM - View contained a tree ID that the service does not support.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the tree ID of the CSV file read by JP1/IM - View is correct.

KAVB7235-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The visual monitoring screen ID (Visual-Monitoring-window-ID) is not registered)

The operation request data from JP1/IM - View contained a Visual Monitoring window ID that the service does not support.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the Visual Monitoring window ID is within the supported range (1 to 64).

KAVB7236-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The common event monitoring condition ID (common-event-monitoring-condition-ID) is not registered)

The operation request data from JP1/IM - View contained a common event monitoring condition ID that the service does not support.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the common event monitoring condition ID is within the supported range (1 to 255).

KAVB7237-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The memory is insufficient)

The operation request from JP1/IM - View failed because a memory shortage occurred.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7238-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The resource was insufficient)

An operation request from JP1/IM - View failed because there were insufficient resources such as file descriptors.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that system resources such as file descriptors are sufficient, and stop any unnecessary processes.

KAVB7239-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient to update the database)

An operation request from JP1/IM - View failed because there was not enough space on the disk where the database is stored.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the free space on the disk where the database is stored, and delete any unnecessary files.

KAVB7240-W

JP1/IM-CS temporarily failed in executing the operation request (request-name) from JP1/IM-View. (Cause: The database is used)

An operation request from JP1/IM - View temporarily failed because the database was being used by another process.

S:

Cancels the requested operation.

O:

Wait awhile, and then retry the operation.

KAVB7241-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be accessed)

An operation request from JP1/IM - View failed because a database access failed.

S:

Cancels the requested operation.

O:

Check access permissions for database files and directories.

KAVB7242-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found)

An operation request from JP1/IM - View failed because a database file was not found.

S:

Cancels the requested operation.

O:

Determine whether the database file and directory exist. Stop the service, create a new database, and then restart the service.

KAVB7243-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The tree ID (tree-ID) is not registered)

The operation request data from JP1/IM - View contained a tree ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the tree ID of the CSV file read by JP1/IM - View is correct.

KAVB7244-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The node ID (node-ID) is not registered)

The operation request data from JP1/IM - View contained a node ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

Display the properties of the monitoring tree in JP1/IM - View, and confirm that the node ID exists.

KAVB7245-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The visual monitoring screen ID (Visual-Monitoring-window-ID) is not registered)

The operation request data from JP1/IM - View contained a Visual Monitoring window ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

In JP1/IM - View, close the Edit Visual Monitoring Window List window or the Open Visual Monitoring Window window, and then retry the operation.

KAVB7246-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The common event monitoring ID (common-event-monitoring-condition-ID) is not registered)

The operation request data from JP1/IM - View contained a common event monitoring condition ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

Close the Common Condition Settings window in JP1/IM - View, and then open it again.

KAVB7247-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The record in the database is invalid)

An operation request from JP1/IM - View failed because the record was not found in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7248-E

JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be operated, reason-code)

An operation request from JP1/IM - View failed because an operation using the database failed.

S:

Cancels the requested operation and continues to accept requests.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7249-E

JP1/IM-CS could not create the result response data for the operation request (request-name) from JP1/IM-View. (Cause: Memory was insufficient)

The operation request from JP1/IM - View was executed correctly, but JP1/IM-Central Scope could not create the response data because a memory shortage occurred.

S:

Closes the connection to JP1/IM - View and continues to accept service requests.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7250-E

JP1/IM-CS could not create the result response data for the operation request (request-name) from JP1/IM-View. (Cause: reason-code)

The operation request from JP1/IM - View was executed correctly, but JP1/IM - Central Scope could not create the response data.

S:

Closes the connection to JP1/IM - View and continues to accept service requests.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7252-W

A part of the tree cannot be created, because the definition information of a linked product could not be acquired. (host=host-name, product=product-name)

Part of the monitoring tree could not be created because definition information of a linked product could not be acquired by automatic generation of the monitoring tree.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the following items. If the issue is not resolved, use the data collection tool to collect data, and then contact a system administrator.

Has the linked product's service been stopped?

Is the linked product running?

KAVB7253-W

A part of the tree cannot be created because the definition information of a linked product could not be acquired.

Part of the monitoring tree could not be created because definition information of a linked product could not be acquired by automatic generation of the monitoring tree.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the following items. If the issue is not resolved, use the data collection tool to collect data, and then contact a system administrator.

Has the linked product's service been stopped?

Is the linked product running?

KAVB7254-E

A tree could not be created. (Cause number=reason-number)

A monitoring tree could not be created automatically.

S:

Cancels the requested operation and continues to accept requests.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7255-E

An attempt to execute (request-name) from JP1/IM - View has failed. (Cause number=reason-number)

A request from JP1/IM - View failed.

S:

Cancels the requested operation and continues to accept requests.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7256-E

(request-name) will now stop, because the tree was updated.

The requested operation was not performed because the monitoring tree has already been updated.

S:

Cancels the requested operation and continues to accept requests.

O:

Update the tree to the latest status using JP1/IM - View, and then retry the operation.

KAVB7257-I

(request-name) cannot be executed because no update has been done.

The requested operation was not performed because no update has been performed.

S:

Cancels the requested operation and continues to accept requests.

KAVB7258-E

An attempt to execute (request-name) from JP1/IM - View has failed because the number of visual monitoring windows exceeded the limit.

An attempt to execute the requested operation from JP1/IM - View failed because the number of visual monitoring windows reached its limit.

S:

Cancels the requested operation and continues to accept requests.

O:

Close unnecessary visual monitoring windows, and then retry the operation.

KAVB7259-E

An attempt to execute (request-name) from JP1/IM - View has failed because the number of nodes exceeded the limit.

An attempt to execute the requested operation from JP1/IM - View failed because the number of nodes reached its limit.

S:

Cancels the requested operation and continues to accept requests.

O:

Delete unnecessary nodes, and then retry the operation.

KAVB7260-E

An attempt to execute (request-name) from JP1/IM - View has failed because the number of common event monitoring conditions exceeded the limit.

An attempt to execute the requested operation from JP1/IM - View failed because the number of common event monitoring conditions reached its limit.

S:

Cancels the requested operation and continues to accept requests.

O:

Delete unnecessary common event monitoring conditions, and then retry the operation.

KAVB7261-E

An attempt to execute (request-name) from JP1/IM - View has failed because the system definition file could not be read.

An attempt to execute the requested operation from JP1/IM - View failed because the system definition file could not be read.

S:

Cancels the requested operation and continues to accept requests.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7262-E

An attempt to execute (request-name) from JP1/IM - View has failed because the common event monitoring condition ID (common event monitoring condition ID =common-event-monitoring-condition-ID) is in use.

An attempt to execute the requested operation from JP1/IM - View failed because the common event monitoring condition ID is in use.

S:

Cancels the requested operation and continues to accept requests.

O:

Determine whether the common event monitoring condition you attempted to delete is in use as a user monitoring object in the tree, and then retry the operation.

KAVB7263-E

(request-name) will now stop because the visual monitoring window is updated.

The requested operation from JP1/IM - View was not performed because the Visual Monitoring window has been updated.

S:

Cancels the requested operation and continues to accept requests.

O:

Update the Visual Monitoring window to the latest status using JP1/IM - View, and then retry the operation.

KAVB7264-E

The same event monitoring condition name is already registered.

Duplicate common condition names cannot be registered.

S:

Suspends updating of the common event monitoring condition and continues to accept requests.

O:

Reconfigure the common condition names, and then retry the operation.

KAVB7265-E

Another user is making a tree.

Automatic generation cannot be executed because another user is running automatic generation.

S:

Suspends automatic generation and continues to accept requests.

O:

Wait until the other user has finished running automatic generation, and then retry the operation.

KAVB7266-W

An invalid common event monitoring condition is included in the node. (monitoring-node-ID)

A monitoring node of the tree includes an unregistered common event monitoring condition.

S:

Places the affected monitoring node in non-monitoring status.

O:

Check the status change condition settings of the monitoring node.

KAVB7267-W

JP1/IM - CS could not create the tree completely. (reason)

Part of a tree could not be created.

S:

Cancels the requested operation and continues to accept requests.

O:

Perform the check indicated by the reason, and then take corrective action.

KAVB7268-W

JP1/IM - CS could not completely execute the operation request (request-name) of JP1/IM - View completely.

Part of an operation request from JP1/IM - View could not be executed.

S:

Continues processing.

O:

Check the log for the message that was output preceding this message, and take the corrective action given for that message.

KAVB7269-W

Failed to resolve hostname. Tree generation may have gone wrong in part. (host: host-name).

Generation of part of a tree may have failed because the host name could not be resolved.

S:

Continues processing.

O:

Determine whether the host name is set in the jcs_hosts file or the hosts file.

KAVB7272-E

JP1/IM - CS could not execute the operation request (request-name) from command.

An operation request from a command was not executed because of an error.

S:

Cancels the requested operation.

O:

Check the log for the message that was output preceding this message, and take the corrective action given for that message.

KAVB7273-W

JP1/IM - CS could not completely execute the operation request (request-name) of command.

JP1/IM could not execute part of an operation request from a command.

S:

Continues processing.

O:

Check the log that indicates the cause of the immediately previous error, and then take corrective action.

KAVB7274-W

An attempt to acquire the name of the destination host, for acquiring the definition information of the linked product (product-name), has failed.

An attempt to acquire the name of the host at the destination for acquiring definition information failed.

S:

Uses the definition information acquisition destination host as its host and continues processing.

O:

If linked to another host, set up the information acquisition destination host.

KAVB7276-E

No linked product (product-name) has been installed or set up on the host (host-name).

Definition information could not be acquired because the linked product has not been installed or set up.

S:

Cancels processing.

O:

Install or set up the linked product.

KAVB7277-E

The service for the linked product (product-name) of the host (host-name) is not running.

The linked product could not be acquired because the service for the linked product is not running.

S:

Cancels processing.

O:

Start the linked product service.

KAVB7278-E

User (JP1-user-name) does not have permission to acquire the definition information of the linked product (product-name) of the host (host-name).

The definition information of the linked product could not be acquired because the user does not have permission to acquire the definition information of the linked product.

S:

Cancels processing.

O:

Log in as a user with permission to acquire the definition information of the linked product, and execute automatic generation. Alternatively, assign permission to the user.

KAVB7279-E

An attempt to acquire the definition information of the linked product (product-name) of the host (host-name) has failed. (details: detailed-information)

The definition information of a linked product could not be acquired because the linked product returned an error.

S:

Cancels processing.

O:

The message output by the linked product is displayed in the detailed information. Refer to the linked product documentation and take the corrective action indicated for that message.

KAVB7280-E

The host (host-name), which was specified as the destination host for acquiring the definition information of the linked product (product-name), does not exist.

The specified host name is invalid.

S:

Cancels processing.

O:

Make sure that the host name is correct. If an incorrect host was specified, specify the destination host for acquiring the definition information again.

KAVB7281-E

An attempt to acquire the definition information of the linked product (product-name) of the host (host-name) has failed. (cause number=reason-number)

The definition information of a linked product could not be acquired because JP1/Base returned an error.

S:

Cancels processing.

O:

Check the system status as directed by the reason number. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

reason-number: 50

Description: The processing limit has been reached.

Action: Wait awhile, and then try the operation again.

reason-number: 101

Description: A parameter is invalid.

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

reason-number: 103

Description: The JP1/Base environment is invalid.

Action: Make sure that JP1/Base is installed correctly.

reason-number: 105

Description: An error occurred while acquiring linked product information.

Action: Use the data collection tool to collect data, and then contact a system administrator.

reason-number: 107

Description: A common definition value is invalid.

Action: Make sure that JP1/Base was set up correctly.

reason-number: 108

Description: A logical host name is invalid.

Action: Check the logical host name for errors.

reason-number: 114

Description: The network is unreachable, or a connection error occurred during communication.

Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 115

Description: An error occurred during transmission processing.

Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 116

Description: An error occurred during reception processing.

Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 117

Description: A connection was ended.

Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 118

Description: The protocol of the received transmission was incorrect.

Action: Temporarily invalid data may have been received. Retry the operation.

reason-number: 119

Description: Initialization was not performed.

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

reason-number: 199

Description: An error occurred.

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Any other reason number

Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7282-E

A timeout occurred while acquiring the definition information of the linked product (product-name) of the host (host-name).

A time-out occurred while acquiring the definition information of a linked product.

S:

Cancels processing.

O:

Wait awhile, and then retry the operation.

KAVB7283-E

In (mid-sized-item-type:mid-sized-item-name), the (small-item-type) has exceeded the restricted value (byte-count byte), (large-item-name) updation is failed.

An attempt to update (large-item-name) failed because the (small-item-type) of (mid-sized-item-type:mid-sized-item-name) exceeded the limit value (byte-count bytes).

The following values are displayed as the message text variables.

mid-sized-item-type

Node ID, common condition name, or Visual Monitoring window

mid-sized-item-name

The actual name corresponding to the mid-sized-item-type item

small-item-type

Monitoring node name, attribute value of basic information, attribute value of common condition, condition name of status change condition, individual attribute value of individual condition, common condition name, attribute value of common condition, window title of the Visual Monitoring window, or comment of the Visual Monitoring window

byte-count

The maximum length (in bytes) of the small-item-type item

large-item-name

Monitoring tree, monitoring node, Visual Monitoring window, or common condition

S:

Suspends processing.

O:

Check the character string specified in small-item-type of mid-sized-item-name of mid-sized-item-type, shorten it so that it is within the limits for UTF-8 encoding, and then update large-item-name again.

KAVB7302-E

JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment. (Cause: An attempt to read the system environment setting file has failed)

Data cannot be acquired from the system environment settings file.

S:

Cancels the requested operation.

O:

The system environment settings file does not exist, or the user does not have access permission. Check the details of the message that was output preceding this message.

KAVB7303-E

JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment (Cause: The data format of the system environment setting file was invalid)

The description of the system environment settings information is incorrect.

S:

Cancels the requested operation.

O:

Check the system environment settings file for errors.

KAVB7304-E

JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment settings. (Cause: Memory was insufficient)

An attempt to acquire system environment settings information failed because a memory shortage occurred.

S:

Cancels the requested operation.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7305-E

JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment settings.

An attempt to acquire system environment settings information failed due to an internal error.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7306-E

JP1/IM-CS could not create the result response data for the request from JP1/IM-View for acquiring the system environment settings. (Cause: Memory was insufficient)

Result response data for a request to acquire system environment settings information cannot be created due to insufficient memory.

S:

Cancels processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7307-E

JP1/IM-CS could not create the result response data for the request from JP1/IM-View for acquiring the system environment settings.

An attempt to create result response data for a request to acquire system environment settings information failed.

S:

Cancels processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7350-I

The guide information cannot be acquired because the definition of the guide information does not exist.

Guide information cannot be acquired because the guide information definition does not exist.

S:

Cancels the requested operation.

O:

Determine whether the guide information file exists in the prescribed folder. If it exists, check the startup log of Central Scope Service to see if there are errors in the guide information file.

KAVB7351-I

The guide information cannot be acquired because the event history does not exist.

Guide information cannot be acquired because the specified monitoring node status has not changed.

S:

Cancels the requested operation.

O:

Execute the guide function targeting a monitoring node whose status has changed.

KAVB7352-I

The guide information cannot be acquired because the event does not exist.

Guide information cannot be acquired because no event whose monitoring node status has changed exists yet in the event database.

S:

Cancels the requested operation.

O:

Either delete the event database contents after the monitoring node status changes, or make sure that the event database has sufficient capacity.

KAVB7353-E

The guide information cannot be acquired because an attempt to acquire the event history has failed.

Guide information cannot be acquired because an attempt to acquire the event history failed.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7354-E

The guide information cannot be acquired because an attempt to acquire the event has failed.

Guide information cannot be acquired because an attempt to acquire an event failed.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7355-I

The corresponding guide information does not exist.

No guide information that matches the conditions was found.

S:

Cancels the requested operation.

O:

To output guide information, add a description to the guide information file.

KAVB7356-E

Guide information cannot be acquired because an attempt to acquire the guide message has failed.

Guide information cannot be acquired because an attempt to acquire a guide message failed.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7357-E

Guide information cannot be acquired because a message development processing has failed.

Guide information cannot be acquired because an attempt to expand text beginning with $ in a guide message failed.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7358-W

The guide message file name is not specified.

The guide message file name is not specified in EV_FILE.

S:

Ignores the specified guide message and continues processing.

O:

Carefully review the configuration of the guide message file.

KAVB7359-E

Guide information could not be acquired because acquisition of the guide title message has failed.

Guide information cannot be acquired because an attempt to acquire the guide title message failed.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7360-W

The guide message file (file-name) does not exist.

The guide message file specified in EV_FILE or the default guide message file does not exist.

S:

Ignores the specified guide message and continues processing.

O:

Carefully review the contents of EV_FILE and the configuration of the guide message file.

KAVB7361-E

An error occurred during reading of the guide message file.

An error occurred while reading the guide message file.

S:

Cancels guide display processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7362-W

The file name length of the guide message file (file-name) exceeds the limit of 1024 bytes.

The length of the guide message file name specified in the EV_FILE tag of the guide information file exceeds 1,024 bytes.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information file.

KAVB7363-E

The file size of the guide message file (file-name) exceeds the limit of size bytes.

The guide message file exceeds the maximum readable file size.

S:

Cancels guide display processing.

O:

Carefully review the amount of description in the guide message file.

KAVB7364-E

The user does not have permission to read the file file-name.

You do not have permission to read the guide message file.

S:

Cancels guide display processing.

O:

Carefully review read permissions in the guide message file for system accounts (in Windows) or superusers (in UNIX).

KAVB7365-E

Memory became insufficient during processing of the guide message file.

Processing cannot continue due to insufficient memory.

S:

Cancels guide display processing.

O:

Check the amount of free space in system memory. Use the following methods to ensure sufficient memory for execution, and then restart JP1/IM - Manager.

Increase available memory by stopping unnecessary processes.

Add memory based on a re-estimate of the required memory.

KAVB7366-E

The guide message file (file-name) is not a file.

A character string that is not a file (such as a directory) was specified in the guide message file specified by the EV_FILE tag of the guide information file.

S:

Cancels guide display processing.

O:

In the guide message file, specify a text file written in the language code of the Central Scope Service LANG environment.

KAVB7367-E

The version of the guide information definition file is invalid (DESC_VERSION = version).

The version of the specified guide information file is invalid. For DESC_VERSION, specify 1 or 2.

S:

Disables guide functionality.

O:

Specify 1 or 2 for DESC_VERSION in the guide information file.

KAVB7368-E

An invalid guide message file is specified.

An invalid guide message file was specified.

S:

Cancels guide display processing.

O:

In the guide message file, specify a text file written in the language code of the Central Scope Service LANG environment.

KAVB7377-W

The guide information definition could not be acquired because the guide information definition file does not exist.

The guide information file does not exist.

S:

Disables guide functionality and continues processing.

O:

To enable guide functionality, create a guide information file.

KAVB7378-W

The guide information definition could not be acquired because the user does not have access permission for the guide information definition file.

You do not have permission to access the guide information file.

S:

Disables guide functionality and continues processing.

O:

Check access permissions for the guide information definition file.

KAVB7379-W

The guide information definition could not be acquired because an attempt to read the guide information definition file has failed.

An attempt to read the guide information file failed.

S:

Disables guide functionality and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7380-W

The guide information definition could not be acquired because the guide information definition was not defined in the guide information definition file.

There are no guide information definitions in the guide information file.

S:

Disables guide functionality and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7381-W

The specified guide information definition was not validated because the number (number-of-conditional-expression-definitions) of conditional expression definitions specified by the guide information definition (guide-information-definition) is invalid.

An invalid value was specified in a conditional expression definition specified in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7382-W

The specified conditional expression (conditional-expression) was not validated because the attribute name (attribute-name) of the conditional expression definition (number-of-conditional-expression-definitions) specified by the guide information definition (guide-information-definition) is an invalid enhancement regular expression (detailed information: detailed-information).

An invalid enhancement regular expression is specified by the guide information definition.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Refer to the following detailed information, and then carefully review the contents of the guide information definition file.

detailed-information

Invalid pattern.

A regular expression is invalid.

Corrective action

Make sure that the described regular expressions are correct.

detailed-information

Invalid contents within the {} pair.

The specified value for the number of iterations is invalid.

Corrective action

Make sure that the number of iterations specified within the curly brackets is correct.

detailed-information

Last character cannot be \.

The last character is an escape character (\).

Corrective action

Make sure that the expression does not end with \.

detailed-information

Invalid range within [] expression.

The end specified for a range is invalid.

Corrective action

Make sure that the range specified between square brackets is correct.

detailed-information

Invalid subexpression backreference number.

A specification indicating a number contains an invalid character.

Corrective action

Make sure that number statements are appropriate.

detailed-information

?, *, +, or {} is not preceded by a valid regular expression.

?, *, +, {, or } is not preceded by a valid regular expression.

Corrective action

Make sure that ?, *, +, {, and } are preceded by valid regular expressions.

detailed-information

() imbalance.

The numbers of open and close parentheses do not match.

Corrective action

Make sure that the numbers of open and close parentheses match.

detailed-information

{} imbalance.

The numbers of open and close curly brackets do not match.

Corrective action

Make sure that the number of open and close curly brackets match.

detailed-information

[] imbalance.

The numbers of open and close square brackets do not match.

Corrective action

Make sure that the numbers of open and close square brackets match.

detailed-information

Invalid character class type referenced.

An invalid character class was specified.

Corrective action

Make sure that character class specifications are appropriate.

detailed-information

Invalid collating element referenced.

An invalid collating element class was specified.

Corrective action

Determine whether an invalid collating element was specified.

detailed-information

The REG_EXTENDED flag is not specified.

The REG_EXTENDED flag for specifying extended regular expressions was not specified.

Corrective action

System error. Use the data collection tool to collect data, and then contact a system administrator.

detailed-information

Out of memory.

Memory has become insufficient.

Corrective action

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

detailed-information

Internal error.

An internal error occurred.

Corrective action

System error. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7383-W

The content of the guide information definition (guide-information-definition) was not validated because the guide information message is not defined.

No guide information message is defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7384-W

The content of the guide information definition (guide-information-definition) was not validated because the guide information message title is not defined.

No guide information message title is defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7385-W

The content of the guide information definition (guide-information-definition) was not validated because the number of conditional expression definitions is not defined.

The number of conditional expression definitions is not defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7386-W

The conditional expression definition was not validated because the conditional expression definition (conditional-expression-definition) of the guide information definition (guide-information-definition) is not defined.

No conditional expression definitions are defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7387-W

The conditional expression definition was not validated because the conditional contents (definition-content) of the expression definition (conditional-expression-definition) of the guide information definition (guide-information-definition) are invalid.

The definition contents of a conditional expression definition in the guide information definitions is invalid.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7388-W

The guide information definition could not be acquired because the format of the guide information definition file is invalid.

The format of the guide information definition file is invalid.

S:

Disables guide functionality and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7389-W

The guide information definition could not be acquired because an attempt to acquire the path of the guide information definition file has failed.

An attempt to acquire the path of the guide information file failed.

S:

Disables guide functionality and continues processing.

O:

Make sure that setup is correct.

KAVB7390-W

The tag name is invalid, so the content of the guide information definition (guide-information-definition) does not become effective.

An invalid tag was specified in the guide information file.

S:

Ignores the tag that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7391-W

The content of the guide information definition (guide-information-definition) was not validated because the escape string (escape-character-string) of the guide information message is invalid.

An invalid escape character was specified in the guide information file.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7392-W

The content of the guide information definition (guide-information-definition) was not validated because the last character of the guide information message is an escape character.

An escape character was specified at the end of a guide information message.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7393-I

The guide information definition was initialized successfully.

Guide information definitions were initialized successfully.

S:

Continues processing.

KAVB7394-I

The guide information definition was reloaded successfully.

Guide information definitions were reloaded successfully.

S:

Continues processing.

KAVB7395-W

The length of the guide information message exceeds the limit of (guide-information-message-maximum-size) bytes.

The length of the guide information message exceeds the limit.

S:

Displays the message without the part that exceeds the limit.

O:

Carefully review the contents of the guide information definition file.

KAVB7396-W

An attempt to initialize the guide information definition has failed.

An attempt to initialize guide information definitions failed.

S:

Disables guide functionality and continues processing.

O:

Take the corrective action given for the message that was output preceding this message.

KAVB7397-W

The old guide information definition will be used because an attempt to reload the guide information definition has failed.

An attempt to reload guide information definitions failed.

S:

Uses guide information definitions registered prior to reloading and continues processing.

O:

Take the corrective action given for the message that was output preceding this message.

KAVB7398-W

The guide information definition cannot be used because an attempt to reload the guide information definition has failed.

An attempt to reload guide information definitions failed.

S:

Disables guide functionality and continues processing.

O:

Take the corrective action given for the message that was output preceding this message.

KAVB7399-E

Guide information cannot be acquired because an attempt to acquire the maximum value of the guide message has failed.

An attempt to acquire the maximum length of the guide message failed.

S:

Cancels the requested operation.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7400-E

A system error occurred. (function: function-name, errorcode: reason-code, reason: reason)

An error occurred during automatic generation processing.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7401-E

A system error occurred. (function: function-name, errorcode: reason-code)

An error occurred during automatic generation processing.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7402-W

A system error occurred. (function: function-name, errorcode: reason-code, reason: reason)

An error occurred during automatic generation processing.

S:

Continues automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7403-W

A system error occurred. (function: function-name, errorcode: reason-code)

An error occurred during automatic generation processing.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7404-E

Memory became insufficient.

There is not enough memory for command execution.

S:

Cancels automatic generation processing.

O:

Check the amount of free space in system memory. Increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7405-E

An argument is invalid.

An API argument contains an error.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7406-E

An attempt to create the tree failed because a definition file (file-name) is invalid.

An invalid format was found in the contents of a definition file used by automatic generation.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7407-E

Information from a linked product is invalid. (Host: host-name, identifier=ID)

An invalid format was found in information acquired by a JP1/Base plug-in service.

S:

Ignores the invalid information and continues automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7408-E

An attempt to collect information from a linked product failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7409-E

Failed to collect the information from cooperation products. (function: function-name, errorcode: reason-code)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7410-W

An attempt to collect information from a linked product failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7411-W

An attempt to collect information from a linked product failed. (function: function-name, errorcode: reason-code)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7412-E

An attempt to collect the configuration definition of JP1/IM failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire JP1/IM configuration definition information failed.

S:

Cancels automatic generation processing.

O:

Make sure that the JP1/IM system configuration (configuration definition) is configured correctly.

KAVB7413-E

An attempt to collect the configuration definition of JP1/IM failed. (function: function-name, errorcode: reason-code)

An attempt to acquire JP1/IM configuration definition information failed.

S:

Cancels automatic generation processing.

O:

Make sure that the JP1/IM system configuration (configuration definition) is configured correctly.

KAVB7414-W

An attempt to collect the configuration definition of JP1/IM failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire JP1/IM configuration definition information failed.

S:

Continues automatic generation processing only for the local host.

O:

Make sure that the JP1/IM system configuration (configuration definition) is configured correctly.

KAVB7415-W

An attempt to collect the configuration definition of JP1/IM failed. (function: function, errorcode: errorcode, reason: reason)

An attempt to acquire JP1/IM configuration definition information failed.

S:

Continues automatic generation processing only for the local host.

O:

Make sure that the JP1/IM system configuration (configuration definition) is configured correctly.

KAVB7416-E

An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7417-E

An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7418-W

An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7419-W

An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7420-W

An attempt to resolve the host name (host-name) failed.

An attempt to resolve the host name acquired from a linked product failed.

S:

Continues automatic generation processing for hosts other than the one whose host name was not resolved.

O:

Make sure that the host name is specified in the jcs_hosts file or hosts file.

KAVB7450-E

An attempt to convert the character code has failed because the memory was insufficient.

Processing cannot continue because there is not enough memory.

S:

Cancels character code conversion processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7451-E

A system error occurred. (Detailed information: An attempt to convert the character code has failed)

An attempt to convert character code failed.

S:

Cancels character code conversion processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7452-E

A system error occurred. (Detailed information: The character code was invalid)

A character code conversion was attempted between unsupported character codes.

S:

Cancels character code conversion processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7453-E

A system error occurred. (Detailed information: The buffer area for storing the converted character string was insufficient)

Insufficient buffer area was secured to store the converted character string.

S:

Cancels character code conversion processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7455-E

The file operation processing has failed because the memory was insufficient.

Processing cannot continue because there is not enough memory.

S:

Cancels file operation processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7457-E

The default value (default-monitored-object-DB-version) will be used because the value specified for the monitored object DB version (monitored-object-DB-version) is invalid.

The monitored object database version is invalid. Assumes the default monitored object database version.

S:

Assumes the default monitored object database version and continues processing.

O:

The version may have been downgraded by an installation. Stop the service, and then set up the monitored object database again.

KAVB7458-E

The user does not have access permission for the definition file (file-name).

You do not have access permission for the specified file.

S:

Cancels file operation processing.

O:

Check access permissions for the specified file.

KAVB7459-E

The monitored object DB has not been set up.

An attempt to start Central Scope Service failed because the monitored object database was not set up.

S:

Stops Central Scope Service.

O:

Execute the jcsdbsetup command, and then set up the monitored object database.

KAVB7460-E

The definition file (file-name) cannot be opened.

The specified file cannot be opened.

S:

Cancels processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7462-E

A system error occurred. (Detailed information: An attempt to initialize the lock has failed)

An attempt to initialize a lock failed.

S:

Cancels file operation processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7463-W

English (Lang=C) is assumed as the language type because the language type could not be identified.

The setting for language type (LANG) cannot be acquired.

S:

Assumes English (LANG=C) as the language type and continues processing.

O:

Carefully review the language type (LANG) setting defined in JP1/Base.

KAVB7464-W

The definition file (file-name) corresponding to the language type does not exist.

The definition file (file-name) corresponding to the language type does not exist.

S:

If the language code used for operating JP1/IM - Manager is not English (LANG=C), the system assumes English (LANG=C), and continues processing on the relevant definition file.

If the language code used for operating JP1/IM - Manager is English (LANG=C), the system aborts processing.

O:

Check whether the definition file indicated by file-name exists.

KAVB7465-E

An attempt to acquire the size of the definition file (file-name) has failed.

An attempt to acquire the size of the specified file failed.

S:

Cancels processing to acquire the file size.

O:

Check the file status. Also refer to the message that was output for the preceding file operation.

KAVB7470-E

The contents of the definition information assigned to the file(file-name) is invalid (character string information: first-64-bytes-of-printable-characters)

An attempt to set definition information failed because the syntax of the specified character string data is incorrect. first-64-bytes-of-printable-characters is embedded text.

S:

Cancels processing to specify definition information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7471-E

An attempt to write the specified character string to the file (file-name) has failed (character string information: first-64-bytes-of-printable-characters)

An error occurred in processing to write the specified character string data in a file (only the first 64 bytes of printable characters is output). first-64-bytes-of-printable-characters is embedded text.

S:

Cancels processing to specify definition information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7473-E

An attempt to acquire the attribute value that corresponds to the section (section-name) and the attribute name (attribute-name) of the definition file (file-name) has failed.

An error occurred while searching for an attribute value that corresponds to the specified section and attribute name.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7475-E

A system error has occurred. (Detailed information: An attempt to acquire the section name list has failed. Definition file: file-name, Section: section-name)

An error occurred in processing to acquire a list of section names under the specified section.

S:

Cancels processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7479-E

The file size of the definition file (file-name) exceeds the limit ((size) bytes).

The definition file exceeds the readable file size limit.

S:

Terminates processing.

O:

Shorten the definition file size so that it is no greater than the upper limit.

KAVB7480-E

A format error of the definition file occurred. The invalid code is included in the tag name and the attribute name. (line number: line-number, file name: file-name)

Definition file format error. Use single-byte code rather than double-byte code for tag names and labels.

S:

Terminates command processing.

O:

Use single-byte code rather than double-byte code for tag names and labels.

KAVB7482-E

A syntax error exists in the definition file. The section does not start with the starting tag. (line number: line-number, file name: file-name)

A section in the definition file does not start with a starting tag.

S:

Cancels processing.

O:

Make sure that the starting tag in the definition file is described correctly.

KAVB7483-E

A syntax error exists in the definition file. An invalid character is in the starting tag. (line number: line-number, file name: file-name)

There is no tag name between the square brackets of the starting tag in the definition file, or an invalid character code was used.

S:

Cancels processing.

O:

Make sure that the starting tag in the definition file is described correctly.

KAVB7484-E

A format error exists in the definition file. The nesting of the section in the definition file exceeds the maximum value. (Detailed information: Maximum number of nests: maximum-number-of-nests, line number: line-number, file name: file-name)

The number of nesting levels in the definition file exceeds the maximum.

S:

Cancels processing.

O:

Make sure that the number of nesting levels in the section of the definition file does not exceed the maximum.

KAVB7485-E

A format error exists in the definition file. The characters in one line exceed the maximum value. (Detailed information: Maximum number of characters: maximum-number-of-characters, line number: line-number, file name: file-name)

The maximum number of characters that can be defined per line in the definition file was exceeded.

S:

Cancels processing.

O:

Check the number of characters defined per line in the definition file.

KAVB7487-E

A syntax error exists in definition file. The starting tag or the ending tag does not exist. (Line number: line-number, file name: file-name)

Definition file syntax error. The starting tag or the ending tag does not exist.

S:

Cancels processing.

O:

Make sure that the starting tag and ending tag are described correctly in the definition file.

KAVB7488-E

A syntax error exists in the definition file. An attribute name does not exist in front of equal (=). (Line number: line-number, file name: file-name)

An equal sign in the definition file is not preceded by an attribute name definition.

S:

Cancels processing.

O:

Make sure that attribute information is described correctly in the definition file.

KAVB7491-E

A syntax error exists in the definition file. The format is invalid. (Line number: line-number, file name: file-name)

The definition file format is invalid.

S:

Cancels processing.

O:

Make sure that the definition file is described using the correct format.

KAVB7492-E

A syntax error exists in the definition file. The definition tag does not correspond to the ending tag. (Line number: line-number, file name: file-name)

Definition file format error. The definition tag does not correspond to the ending tag.

S:

Cancels processing.

O:

Make sure that the number of definition tags and ending tags and the nesting are configured correctly in the definition file.

KAVB7493-E

A syntax error exists in the definition file. The definition cannot be updated. (Line number: line-number, file name: file-name)

Definitions could not be updated because the definition file format is incorrect.

S:

Cancels processing.

O:

Make sure that the definition file is described using the correct format.

KAVB7494-E

The definition file processing cannot be executed because the memory is insufficient.

Processing cannot continue because there is not enough memory.

S:

Cancels processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7496-E

A system error occurred. (Detailed information: An attempt to lock was executed even though the initialization of the lock has failed)

An attempt to lock was executed even though the initialization of the lock failed.

S:

Cancels processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7497-E

A system error occurred. (Detailed information: An attempt to unlock was executed even though the initialization of a lock has failed)

An attempt to unlock was executed even though the initialization of the lock failed.

S:

Cancels processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7498-E

A system error occurred. (Detailed information: The initialization of a lock has failed)

Initialization of a lock failed.

S:

Cancels processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7550-E

An attempt to read the common definition associated with jcs_hosts has failed (Cause: reason-code).

An attempt to read common definition information associated with jcs_hosts failed.

S:

Terminates processing.

O:

Check the system status as directed by the reason code, and take corrective action. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 2

Description: Key does not exist.

Action: Make sure that setup is correct.

Reason code: Other

Description: System error.

Action: Use the data collection tool to collect data, and then contact a system administrator.

KAVB7552-W

The value of the common definition (JCSHOSTS_TYPE) is out of range (value: value).

A value that is outside the specifiable range was specified for the common definition information (JCSHOSTS_TYPE) value.

S:

Continues processing using the default value (caching enabled).

O:

Check the value specified in the common definition information (JCSHOSTS_TYPE).

KAVB7555-W

jcs_hosts does not exist. The service will be continued with the jp1hosts or system hosts information.

jcs_hosts does not exist.

S:

Disables jcs_hosts and continues running the service using jp1hosts or /etc/hosts.

O:

If a jcs_hosts definition is required, create a jcs_hosts definition, and then reload jcs_hosts.

KAVB7556-I

jcs_hosts was reloaded successfully.

jcs_hosts was reloaded successfully.

S:

Central Scope Service runs with a new jcs_hosts definition.

KAVB7557-W

The old jcs_hosts will be used because an attempt to reload the jcs_hosts has failed.

An attempt to reload jcs_hosts failed due to a syntax error in the definition file.

S:

Uses the previously loaded jcs_hosts and continues processing.

O:

Determine whether jcs_hosts was excluded by the jcshostsimport command, and then reload jcs_hosts. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB7558-E

The jcs_hosts cannot be used because an attempt to reload the jcs_hosts has failed.

An attempt to reload jcs_hosts failed.

S:

Disables jcs_hosts and continues processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7559-E

An attempt to initialize jcs_hosts has failed.

An attempt to initialize jcs_hosts failed.

S:

Disables jcs_hosts and continues processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7560-I

jcs_hosts was initialized successfully.

jcs_hosts was initialized successfully.

KAVB7580-E

An error occurred during the initialization of the communication encryption function for the Central Scope Service. (cause = cause)

An error occurred during the initialization of the communication encryption function for Central Scope Service.

S:

Terminates Central Scope Service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A memory shortage has occurred. is displayed for cause, check the OS logs, and then check for memory shortages. If a memory shortage has occurred, secure sufficient memory, and then restart JP1/IM - Manager.

If A system error occurred. is displayed for cause, restart JP1/IM - Manager.

KAVB7581-E

A parameter of the communication encryption function for the Central Scope Service is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function for Central Scope Service is invalid.

S:

Terminates Central Scope Service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A valid value is not specified for a parameter. is displayed for cause, set a valid value for the parameter in the common definitions of JP1/Base.

If The value of a parameter is null. is displayed for cause, set a value for the parameter in the common definitions of JP1/Base.

If The value of a parameter exceeds the maximum. is displayed for cause, set a value no longer than the maximum length for the parameter in the common definitions of JP1/Base.

If The value of a parameter is not a full path. is displayed for cause, set a full path as the value for the parameter in the common definitions of JP1/Base.

KAVB7582-E

Parameters for the communication encryption function for the Central Scope Service could not be collected. (parameter = parameter-name, cause = cause)

Parameters for the communication encryption function for Central Scope could not be acquired.

S:

Terminates Central Scope Service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A parameter is not defined. is displayed for cause, set the parameter in the common definitions of JP1/Base.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB7583-E

A file or directory specified for a parameter of the communication encryption function for the Central Scope Service could was not found. (parameter = parameter-name, parameter value = parameter-value)

A file or directory specified for a parameter of the communication encryption function for Central Scope Service was not found.

S:

Terminates Central Scope Service.

O:

Check the following, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Determine whether the file or directory corresponding to the parameter exists at the path specified by the parameter. If the file or directory corresponding to the parameter does not exist, create it.

If the path specified by a parameter is for a private key or server certificate, check whether you have read permission for the file. If not, set read permission for the file.

KAVB7584-E

A file specified for a parameter of the communication encryption function for the Central Scope Service could not be read. (parameter = parameter-name, parameter value = parameter-value)

A file specified for a parameter of the communication encryption function for Central Scope Service could not be read.

S:

Terminates Central Scope Service.

O:

Check the following, and then restart JP1/IM - Manager.

Check for problems with the format of the file at the path specified by the parameter.

Check the OS logs listed below to see if a shortage has occurred in an OS resource such as file descriptors. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

In Windows: Windows event log

In UNIX: System log (syslog)

KAVB7585-E

A private key specified for a parameter of the communication encryption function for the Central Scope Service does not correspond to the server authentication certificate. (private key parameter = private-key-parameter-name, private key parameter value = private-key-parameter-value, server certificate parameter = server-certificate-parameter-name, server certificate parameter value = server-certificate-parameter-value)

A private key specified for a parameter of the communication encryption function for Central Scope Service could not be read.

S:

Terminates Central Scope Service.

O:

Check the following, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Check whether the server certificate and private key are paired. If not, put a paired private key and server certificate in place.

Check for problems with the format of the private key file.

If a pass phrase has been set for the private key, cancel the pass phrase.

Check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as file descriptors.

• In Windows: Windows event log

• In UNIX: System log (syslog)

KAVB7586-E

A library required for the Central Scope Service was not found.

A library required for Central Scope Service was not found.

S:

Terminates Central Scope Service.

O:

Re-install JP1/Base, and then restart JP1/IM - Manager.

KAVB7600-E

The logical hostname (logical-host-name) does not exist.

The specified logical host does not exist.

S:

Suspends command processing.

O:

Carefully review the specified logical host name to make sure that it is correct, and then re-execute the command.

KAVB7601-E

The user does not have execution permission.

You do not have execution permission.

S:

Suspends command processing.

O:

Log in as a user with Administrator permissions (in Windows) or superuser permission (in UNIX), and execute the command.

KAVB7602-E

Command execution will stop because memory is insufficient.

There is not enough memory to execute the command.

S:

Suspends command processing.

O:

Check the amount of free space in system memory. Increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7603-E

Command execution will stop because disk capacity is insufficient.

There is not enough disk space to execute the command.

S:

Suspends command processing.

O:

Check the amount of free disk space, delete unnecessary files, and then re-execute the command.

KAVB7604-E

An error occurred during initialization of the database.

An error occurred during initialization of the database.

S:

Suspends command processing.

O:

Check the user's read and write permissions for files and directories in the database directory.

KAVB7605-E

An error occurred during database access.

An error occurred during database access.

S:

Suspends command processing.

O:

Check the user's read and write permissions for files and directories in the database directory.

KAVB7606-E

A connection could not be established with the JP1/IM - Central Scope daemon.

An attempt to connect to Central Scope Service failed.

S:

Suspends command processing.

O:

Make sure that Central Scope Service is running. If it is not running, start Central Scope Service, and then re-execute the command.

KAVB7607-E

The connection with the JP1/IM - Central Scope Service has been lost.

Communication with Central Scope Service ended.

An error occurred in the common definition API of JP1/Base.

An error occurred during definition file I/O.

S:

Suspends command processing.

O:

Check both of the following:

Make sure that Central Scope Service is running. If it is not running, start Central Scope Service, and then re-execute the command.

Determine whether the settings of the communication encryption function have changed since JP1/IM - Manager was started.

KAVB7608-E

The request could not be performed because a communication timeout error occurred.

A communication time-out occurred.

S:

Suspends command processing.

O:

Check the integrated trace log (HNTRLib2) to see if errors occurred in Central Scope Service.

KAVB7609-E

The response received from the JP1/IM - Central Scope Service is not valid.

The response data received from Central Scope Service is invalid.

S:

Suspends command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7610-E

The command (command-name) has been interrupted.

Processing was suspended by a user's suspension instruction.

S:

Suspends command processing.

O:

Processing was suspended by a user's suspension instruction. Execute the command again.

KAVB7611-E

An attempt to connect to the JP1/IM - Central Scope Service has failed because the jp1hosts definition for the specified logical host (logical-host-name) is invalid.

The definition of jp1hosts for the specified logical host is incorrect.

S:

Suspends command processing.

O:

Carefully review the definition of jp1hosts for the specified logical host.

KAVB7612-E

The command option is invalid. (option-name)

An incorrect command option was specified.

S:

Suspends command processing.

O:

Specify the correct command option, and then re-execute the command.

KAVB7613-E

The option-name option is specified more than once.

An option was specified more than once.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7614-E

The value for the option-name option is not specified.

No value was specified for an option.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7615-E

The option-name option is mandatory.

A required option was not specified.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7616-E

The length of the value for the option-name option cannot be greater than numeric-value.

The character string length of the value specified in the option exceeds the maximum value.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7617-E

Execute the command from the administrator console.

This command must be executed from the administrator console.

S:

Terminates command processing.

O:

Re-execute the command from the administrator console.

KAVB7618-E

An invalid value is specified for the option-name option.

An invalid value is specified for an option.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7619-E

A system error occurred.

A system error occurred.

S:

Suspends command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7620-E

An error occurred during an attempt to set the locale.

A system error occurred during an attempt to set the locale.

S:

Suspends command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7621-W

Locale C is assumed because an attempt to set the locale has failed.

The default locale C was used because an attempt to set the locale failed. An invalid value might have been set for environment variable LANG or for a key that starts with LC_.

S:

Continues command processing.

O:

Carefully review the values set for environment variables, and correct invalid settings.

KAVB7622-E

An attempt to initialize the log has failed.

An attempt to initialize the log failed.

S:

Suspends command processing.

O:

Check the following items. If the issue cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

In UNIX, refer to the JP1/IM - Manager release notes, and make sure that file-related kernel parameters are set correctly.

Make sure that there is sufficient memory.

Make sure that there is sufficient disk space.

KAVB7623-E

An attempt to initialize the common definition has failed.

An attempt to initialize common definitions failed.

S:

Suspends command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7624-I

The command-name command finished successfully.

Command execution finished normally.

S:

The command finishes normally.

KAVB7625-E

A service or another command is already running.

Central Scope Service is running, or the version upgrade command is already running.

S:

Suspends command processing.

O:

If the service is running, the version upgrade is complete, so there is no need to execute the command.

If another version upgrade command is running, wait until that command finishes. If that command fails, retry the operation.

KAVB7626-E

An internal error occurred during execution of the command.

An internal error occurred during execution of a command.

S:

Suspends command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7627-E

Another command, command-name, is already running.

The command is already being executed.

S:

Suspends command processing.

O:

Wait for the command being executed to finish, and then retry the operation.

KAVB7628-E

The user does not have permission to read or write the file file-name.

You do not have read or write permission for the file.

S:

Suspends command processing.

O:

Check file access permissions.

KAVB7629-E

An attempt to execute has failed because another user is using the database.

Command execution failed because the database is being used by another function.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB7630-I

The status of the monitoring node (monitoring-node-ID) has been set to status.

Reports that the status of the monitoring node has changed.

S:

Terminates the command.

KAVB7631-E

The specified monitoring node (monitoring-node-ID) does not exist in the monitoring tree.

No monitoring node in the monitoring tree has the specified monitoring node ID.

S:

Suspends command processing.

O:

Make sure that the monitoring node with the specified monitoring node ID exists in the monitoring tree.

KAVB7632-E

The status of the specified monitoring node (monitoring-node-ID) cannot be changed because it is unmonitored.

The status of the monitoring node cannot be changed because the specified monitoring node is unmonitored.

S:

Suspends command processing.

O:

Start monitoring of the specified monitoring node, and then re-execute the command.

KAVB7633-E

The status of the specified monitoring node (monitoring-node-ID) cannot be changed to status, because the monitoring node is a group node. Group nodes can only be changed to "Initial" status.

The specified monitoring node can only be changed to initial status because it is a monitoring group.

S:

Suspends command processing.

O:

To change to a status other than initial, specify a monitored object.

KAVB7634-E

The jcschstat command ended abnormally.

The jcschstat command ended abnormally. This message is output following the message that was output during execution.

S:

Suspends command processing.

O:

Take the corrective action given for the message that was output during execution.

KAVB7635-E

The maximum number of monitoring nodes that can be specified with the command is numeric-value.

The number of monitoring nodes exceeded the maximum that can be specified with the command.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7636-E

The operation could not be executed because the central scope service or another command is already executing.

Central Scope Service is running, or another command is now executing.

S:

Suspends command processing.

O:

The jcsdbsetup command cannot be executed while the service is running. Stop the service. If another command is now executing, wait for it to finish.

KAVB7637-E

An attempt to create the lock file has failed.

An attempt to create the lock file failed.

S:

Suspends command processing.

O:

If the command was executed on a logical host, make sure that the shared disk is mounted, and then re-execute the command.

KAVB7638-W

An error occurred during initialization of the database, The database recovery operation succeeded.

An error occurred during database access processing on the server. Recovery was successful.

S:

Terminates command processing.

O:

The contents of the tree configuration information file were not saved on the server. Check the integrated trace log to find the source of the processing error on the server, and then re-execute the command.

KAVB7640-I

The database creation succeeded.

Creation of the monitored object database was successful.

S:

Creates a monitored object database.

KAVB7641-E

The parameter is invalid.

An argument is invalid.

S:

Terminates command processing.

O:

Carefully review the command arguments, and then retry the operation.

KAVB7642-E

The database creation could not be created. (return value : return-value)

The monitored object database could not be created.

S:

Terminates command processing.

O:

Check the system status according to the return value, and take corrective action. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Return value: 1

Description: Logical host name is invalid.

Action: Make sure that the logical host name specified by the argument is correct.

Return value: 4

Description: No permission to execute command.

Action: Make sure that the login account has Administrator permissions.

Return value: 10

Description: The JP1/IM - Manager definition information is not set up.

Action: Make sure that JP1/IM - Manager is installed correctly.

Return value: 12

Description: Not enough memory.

Action: Check the system memory.

Return value: 13

Description: Not enough disk space.

Action: Check the amount of free space on the disk.

Return value: 20

Description: Database already exists.

Action: To re-create the database, re-execute the command with the -f option specified.

Return value: 99

Description: Error with some other cause occurred.

KAVB7643-I

The processing to set up the JP1/IM-CS logical host will now start.

Processing to set up the Central Scope logical host will start.

S:

Starts processing to set up the Central Scope logical host.

KAVB7644-I

Processing to copy the definition file has started.

Processing to copy the logical host configuration file to the shared disk started.

S:

Starts processing to copy the logical host configuration file to the shared disk.

KAVB7645-I

JP1/IM Central Scope cluster environment setup completed successfully.

The logical host environment was set up successfully.

S:

Terminates command processing.

KAVB7646-E

Logical host of JP1/IM-CC is not setup.

The Central Console logical host environment is not set up.

S:

Terminates command processing.

O:

Set up the logical host environment for Central Console, and then re-execute the command.

KAVB7647-E

Specified shared directory does not exist

The specified shared directory does not exist.

S:

Terminates command processing.

O:

Carefully review the specified shared directory, and then re-execute the command.

KAVB7648-E

Failed to get default configuration data

An attempt to acquire the configuration information failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed and set up correctly on the physical host.

KAVB7649-E

Failed to register configuration data

An attempt to register configuration information failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed and set up correctly on the physical host.

KAVB7650-E

cannot create directory-name

An attempt to create a directory failed.

S:

Terminates command processing.

O:

Check the name of the specified shared directory and the access permissions, and then re-execute the command.

KAVB7651-E

cannot create database for logical host

An attempt to create a database failed.

S:

Terminates command processing.

O:

Make sure that the shared directory has enough disk space.

KAVB7652-E

Failed to update JP1/IM-CC conf files

An attempt to set up Central Console failed.

S:

Terminates command processing.

O:

Make sure that the shared disk of Central Console is mounted, and then execute setup again.

KAVB7653-E

Logical host of JP1/IM-CS is not setup

Setup of a standby server was attempted for a logical host for which the active server has not been set up.

S:

Terminates command processing.

O:

Set up the active server, and then set up the standby server.

KAVB7654-E

Failed to setup socket bind configuration

An attempt to set up the common definitions of the physical host failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed and set up correctly on the physical host.

KAVB7655-I

The logical host database will now be created.

Processing to create the logical host database will start.

S:

Starts processing to create the logical host database.

KAVB7656-I

Update processing of the JP1/IM-CC definition file will now start.

Processing to update the Central Console definition file will start.

S:

Starts processing to update the Central Console definition file.

KAVB7657-I

Physical host communications will now be set up.

Setup of physical host communications will start.

S:

Starts setup of physical host communications.

KAVB7658-I

The JP1/IM-CS logical host will now be set up.

Central Scope logical host configuration processing will start.

S:

Starts Central Scope logical host configuration processing.

KAVB7660-I

Importing of the monitoring tree definition from the file file-name was successful.

Monitoring tree definitions were imported successfully.

S:

Terminates command processing.

KAVB7661-E

There is an error in the specified file. (file-name)

There is an error in the specified file.

S:

Suspends command processing.

O:

Use the jcsdbexport command to specify the file output.

KAVB7662-E

The specified input file (file-name) does not exist.

The specified file does not exist.

S:

Suspends command processing.

O:

Determine whether the specified file exists.

KAVB7663-E

A monitoring tree definition does not exist in the specified file.

A monitoring tree definition does not exist in the specified file.

S:

Suspends command processing.

O:

Use the jcsdbexport command to specify the file output.

KAVB7664-W

An invalid common event monitoring condition is included in the node.

An unregistered common event monitoring condition is included in the tree's monitoring node.

S:

Places the monitoring node in non-monitoring status and executes the command.

O:

Check the configuration of the status change conditions of the monitoring node.

KAVB7665-E

The specified definition file file-name is not a file.

The file specified as an argument is not a file.

S:

Suspends command processing.

O:

The specified file is not a file. Make sure that a file is specified, and then re-execute the command.

KAVB7666-E

The file (file-name) could not be imported because the file version is not compatible with the JP1/IM-CS monitored object DB version.

The file version of the file (file-name) is not compatible with JP1/IM - Central Scope. The specified file may have been created with a more recent version of JP1/IM - Central Scope.

S:

Suspends command processing.

O:

Check the file version, and then import monitoring tree definitions for JP1/IM - Central Scope that are compatible with that file version.

KAVB7667-E

In (mid-sized-item-type: mid-sized-item-name), the (small-item-type) has exceeded the restricted value (byte-count byte), import is failed.

An attempt to import failed because the (small-item-type) of (mid-sized-item-type: mid-sized-item-name) exceeds the limit (byte-count bytes).

The following values are displayed as the message text variables:

mid-sized-item-type

Node ID, common condition name, or Visual Monitoring window

mid-sized-item-name

The actual names corresponding to the items of mid-sized-item-type

small-item-type

Monitoring node name, attribute value of basic information, attribute value of common conditions, condition name of status change condition, individual attribute value of individual condition, common condition name, attribute value of common condition, window title of the Visual Monitoring window, or comment of the Visual Monitoring window

byte-count

The maximum length (in bytes) of the small-item-type item

S:

Suspends processing.

O:

Check the character string specified in small-item-type of mid-sized-item-name of mid-sized-item-type in the environment that exported the configuration file for monitoring tree, and shorten it so that it is within the limits for UTF-8 encoding. Then export the configuration file for monitoring tree again.

Move the exported configuration file for monitoring tree to the environment you want to import, and then import again.

KAVB7670-I

Exporting of the monitoring tree definition to the file file-name was successful.

Output of the monitoring tree definition to the file (file-name) was successful.

S:

Terminates command processing.

KAVB7671-E

There is no data in the database for the specified tree ID.

The specified tree ID cannot be found in the database.

S:

Suspends command processing.

O:

Make sure that the monitoring tree of the specified tree ID is in the database.

KAVB7680-E

An attempt to create jcs_hosts has failed (Cause: reason-code)

An attempt to create jcs_hosts failed.

S:

Terminates command processing.

O:

Check the system status as directed by the reason code, and take corrective action. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 1024

Description: The number of files that can be opened has been exceeded.

Action: Check the status of the system's file resources.

Reason code: Other

Description: System error

Action: Use the data collection tool to collect data, and then contact a system administrator.

KAVB7681-E

A syntax error exists in the definition file. Specify the host name within 1-255 characters. (Line number: line-number, file name: file-name)

The host name described in the definition file exceeds 255 bytes.

S:

Terminates command processing.

O:

Correct the definition file syntax error, and then re-execute the command.

KAVB7682-E

A syntax error exists in the definition file. The maximum number of hosts that can be specified for one IP address is (number-of-hosts). (Line number: line-number, file name: file-name)

The number of hosts specified by the IP address described in the definition file exceeds the maximum.

S:

Terminates command processing.

O:

Correct the definition file syntax error, and then re-execute the command.

KAVB7683-E

A syntax error exists in the definition file. (character-string) is not an IP address. (Line number: line-number, file name: file-name)

A character string that is not recognized as an IP address is specified as an IP address in the definition file.

S:

Terminates command processing.

O:

Correct the definition file syntax error, and then re-execute the command.

KAVB7684-W

A syntax error exists in the definition file. Multiple hosts (host-name) are specified for an IP address (IP-address). (Line number: line-number, file name: file-name)

A host name is specified multiple times for a single IP address in the definition file.

S:

Continues processing.

O:

Check the contents of the definition file.

KAVB7685-W

A syntax error exists in the definition file. Only the first definition of IP address is validated because the IP address (IP-address) is specified several times. (Line number: line-number, file name: file-name)

An IP address is specified multiple times in the definition file.

S:

Continues processing.

O:

Check the contents of the definition file.

KAVB7686-E

A system error occurred while the command was executing.

A system error occurred while a command was being executed.

S:

Suspends command processing.

O:

Collect maintenance data while the command is being executed, and then contact a system administrator.

KAVB7687-E

The command option specification is invalid. You must specify the -o, -r, or -d option.

A required option is not specified.

S:

Suspends command processing.

O:

Specify the -o, -r, or -d option, and then re-execute the command.

KAVB7688-E

The command option specification is invalid. The -o, -r, and -d options cannot be specified simultaneously.

The -o, -r, or -d options have been specified simultaneously.

S:

Suspends command processing.

O:

The -o, -r, and -d options cannot be specified simultaneously. Review the specified options.

KAVB7689-E

An attempt to open jcs_hosts has failed. (Cause: reason-code).

An attempt to open jcs_hosts failed.

S:

Terminates command processing.

O:

Check the system status as directed by the reason code, and take corrective action. If the system does not recover normally, collect maintenance data while the command is being executed, and then contact a system administrator.

Reason code: 1024

Description: The number of files that can be opened has been exceeded.

Action: Check the status of the system's file resources.

Reason code: Other

Description: System error

Action: Use the data collection tool to collect data, and then contact a system administrator.

KAVB7690-E

An error occurred while jcs_host was being accessed. (cause: reason-code)

An error occurred while accessing jcs_hosts.

S:

Suspends command processing.

O:

Collect maintenance data while the command is being executed, and then contact a system administrator.

KAVB7691-E

The command execution will be stopped because the memory is insufficient.

There is not enough memory to execute the command.

S:

Suspends command processing.

O:

Check the amount of free space in system memory. Increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7692-E

The user does not have the access permission for accessing the specified definition file (file-name) for jcs_hosts.

The user cannot access the file.

S:

Suspends command processing.

O:

Check the access permission for the specified file.

KAVB7693-E

The specified definition file (file-name) for jcs_hosts does not exist.

The file does not exist.

S:

Suspends command processing.

O:

The file name specified as an argument does not exist. Check the file name, and then re-execute the command.

KAVB7694-E

A system error occurred. (Detailed information: An error occurred in system call)

An error occurred in a system call.

S:

Suspends command processing.

O:

Check the amount of free space in system memory, increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7695-E

The user does not have execution permission.

The user executing the command does not have Administrator permissions.

S:

Suspends command processing.

O:

Log in as a user with Administrator permissions, and then execute the jcshostsimport command.

KAVB7696-E

The jcs_hosts is invalid.

jcs_hosts is corrupted.

S:

Suspends command processing.

O:

jcs_hosts is corrupted. Set it up again. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

KAVB7697-E

An attempt to initialize the log has failed (Cause: reason-code)

An attempt to initialize the log failed.

S:

Suspends command processing.

O:

Make sure that setup is correct, and, if necessary, perform setup again. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

KAVB7698-E

The Jcs_hosts is busy.

jcs_hosts is being used by another process.

S:

Suspends command processing.

O:

Determine whether jcs_hosts is being used by another process.

KAVB7699-E

No entry is in the definition file (file name: file-name)

Processing will stop because no key is specified in the definition file.

S:

Suspends command processing.

O:

Specify the key in the definition file, and then re-execute the command.

KAVB7700-E

The process will be terminated because an attempt to read the definition file failed. (file name: file-name)

Command processing will stop because an attempt to read the definition file failed.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7701-I

The jcshostsimport command successfully ended.

Command processing ended normally.

KAVB7702-E

A syntax error exists in the definition file. The host is not specified. (Line number: line-number file name: file-name).

The definition file contains a line that does not specify a host name.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7703-E

An attempt to initialize the common definition has failed. (Cause: reason-code).

An attempt to initialize common definition information failed.

S:

Suspends command processing.

O:

Make sure that setup is correct.

Reason code: -2

Description: An attempt to initialize common definition information failed.

Action: Make sure that setup is correct.

KAVB7704-E

An attempt to set the locale has failed.

S:

Terminates command processing.

O:

Check the locale settings in the OS.

KAVB7705-W

C is assumed because an attempt to set the Local has failed.

S:

Continues processing using the default locale C.

O:

Check the locale settings in the OS.

KAVB7706-E

The logical host (logical-host-name) does not exist.

The specified logical host does not exist.

S:

Suspends command processing.

O:

Check the specified logical host name to see if it contains errors.

KAVB7707-E

The number of IP addresses specified for one host exceeds the limit (maximum-number). (file name: file-name).

The number of IP addresses specified for one host name exceeds the maximum that can be specified.

S:

Terminates command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7708-E

An attempt to acquire the common definition has failed.

There is no key in the common definitions.

S:

Suspends command processing.

O:

Make sure that the key is specified.

KAVB7709-E

A system error occurred. (Cause: reason-code)

A fatal error occurred while analyzing arguments.

S:

Suspends command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7711-E

The command option specification is invalid.

A command argument is incorrect.

S:

Suspends command processing.

O:

A command argument is incorrect. Carefully review the arguments, and then re-execute the jcshostsexport command.

KAVB7712-E

The jcs_hosts does not exist.

jcs_hosts does not exist.

S:

Suspends command processing.

O:

Specify the correct database file name, and then execute jcshostsexport.

KAVB7713-E

JP1/IM-CS is not set up.

JP1/IM - Manager is not set up.

S:

Suspends command processing.

O:

Re-install JP1/IM - Manager.

KAVB7714-W

The command execution will be stopped because the disk space is insufficient.

There is not enough disk space to execute the command.

S:

Suspends command processing.

O:

Check the amount of free space on the disk.

KAVB7715-E

The specified definition file file-name is not a file.

The definition file for jcs_hosts that was specified as an argument is not a file.

S:

Suspends command processing.

O:

The definition file that was specified for jcs_hosts is not a file. Check the specification, and then re-execute the command.

KAVB7722-E

The logical host (logical-host-name) is not specified.

The logical host has not been specified, or the specified logical host information does not exist.

S:

Suspends command processing.

O:

Make sure that the specified logical host name is correct and that it has been specified correctly.

KAVB7723-E

The command option is invalid. The option (option-name) cannot be recognized.

The specified option is invalid.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7724-E

The command option is invalid. The option (option-name) is specified redundantly.

An option has been specified more than once.

S:

Terminates command processing.

O:

Check the specified option, and then re-execute the command.

KAVB7725-E

The command option is invalid. The value of the option (option-name) is invalid.

A value required by the specified option has not been specified.

S:

Suspends command processing.

O:

Check the specified option, and then re-execute the command.

KAVB7726-E

A syntax error exists in the definition file. An IP address should be specified within 1-63 characters. (Line number: line-number, file name: file-name).

An IP address specified in the definition file is too long.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7727-E

The command execution will be stopped because the memory is insufficient.

There is not enough memory to execute the command.

S:

Suspends command processing.

O:

Check the amount of free space in system memory, increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7730-I

The JP1/IM - Central Scope setup will now start.

The Central Scope setup command will start.

S:

Continues processing.

KAVB7731-I

The file file-name was relocated.

The file-name file was relocated.

S:

Continues processing.

KAVB7732-E

'/opt/jp1base/bin/jbssetcnf' could not be executed.

The /opt/jp1base/bin/jbssetcnf command could not be executed.

S:

Suspends command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed correctly.

KAVB7733-I

file-name was registered to the common definition.

Common definition information was registered successfully.

S:

Continues processing.

KAVB7734-E

file-name could not be registered to the common definition.

An attempt to register common definition information failed.

S:

Suspends command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed correctly.

KAVB7735-I

The registration of the common definition data has completed.

Registration of common definition information is complete.

S:

Continues processing.

KAVB7736-E

The system environment could not be set.

The system environment could not be set up.

S:

Suspends command processing.

O:

Make sure that JP1/IM - Manager is installed correctly.

KAVB7737-I

JP1/IM - Central Scope setup has completed.

The Central Scope setup command has ended.

S:

Terminates command processing.

KAVB7750-I

Upgrading of the database version has finished.

Upgrading of the database version is complete.

S:

Terminates command processing.

KAVB7751-I

The database version has already been upgraded.

The database version has already been upgraded.

S:

Suspends command processing.

KAVB7753-E

The specified work path (specified-path) does not exist.

The specified work path does not exist.

S:

Suspends command processing.

O:

Make sure that the specified work path exists.

KAVB7754-W

The database will now be recovered from the backup because the database is corrupted.

The database was recovered from the backup because it was corrupted when the jp1csverup and jp1cshaverup commands were executed.

S:

Continues command processing.

O:

The most recent changes may not have been saved. Check the monitoring tree configuration in JP1/IM - View, and make sure that the monitoring tree is correct.

KAVB7755-E

Command execution will now stop because the attempt to recover the database failed.

An attempt to recover the database failed because the database was corrupted when the jp1csverup and jp1cshaverup commands were executed.

S:

Suspends command processing.

O:

Monitoring tree information was lost when the database was corrupted. Execute the jcsdbsetup command to set up the database, and then rebuild the monitoring tree.

KAVB7765-E

An attempt to copy the definition file file-name has failed.

An attempt to copy a definition file (file-name) failed.

S:

Suspends command processing.

O:

Check the following items. If the issue cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Determine whether the file-name file exists in the scope-path\conf\ directory.

If it does not, re-install JP1/IM - Manager.

Determine whether the \JP1Scope\conf\ folder exists in the shared folder of the specified logical host.

If it does not, execute the jp1cshasetup command to set up the Central Scope logical host again.

Make sure that there is sufficient memory.

Make sure that there is sufficient disk space.

KAVB7766-E

An attempt to add the common definition key has failed.

An attempt to add a key to the common definitions failed.

S:

Suspends command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7767-E

An attempt to delete the database has failed.

An attempt to delete the database failed.

S:

Suspends command processing.

O:

Determine whether the service is running. If it is running, stop the service, and then retry the operation. If the service is already stopped, use the data collection tool to collect data, and then contact a system administrator.

KAVB7770-I

The data was backed up successfully.

Reports that data was acquired successfully.

S:

Terminates the command.

KAVB7771-W

The logical host logical-host-name does not exist.

The specified logical host does not exist.

S:

Continues processing without acquiring the data of the specified logical host.

O:

Carefully review the specified logical host name to make sure that it is correct, and then re-execute the command.

KAVB7772-E

Command execution will stop because disk capacity is insufficient.

There is not enough disk space to execute the command.

S:

Suspends command processing.

O:

Check the amount of available disk space, increase available disk space by deleting unnecessary files, and then re-execute the command.

KAVB7773-E

The command option is invalid.

An incorrect command option was specified.

S:

Suspends command processing.

O:

Specify the correct command option, and then re-execute the command.

KAVB7774-E

Command execution will stop because memory is insufficient.

There is not enough memory to execute the command.

S:

Suspends command processing.

O:

Check the amount of free space in system memory, increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7775-W

The shared directory used by the specified logical host (logical-host-name) was not found.

(Shared directory = shared-directory-path)

The shared directory of the specified logical host does not exist.

S:

Acquires only the data of the physical host and continues processing.

O:

Install the shared directory, and then re-execute the command.

KAVB7776-W

A part of the data was not correctly acquired.

Part of the data could not be acquired. This message is output following messages that are output during execution.

S:

Terminates command processing.

O:

Take the corrective action given for the message that was output during execution.

KAVB7777-W

An attempt to acquire data for collection-directory-or-file did not finish successfully.

collection-directory-or-file data was not acquired normally.

S:

Continues command processing.

O:

Refer to jcs_log_failure.log to see if data exists at the collection source, and then manually acquire the data that could not be acquired.

KAVB7778-W

An attempt to acquire information from the registry for product-name-or-logical-host-name has failed.

product-name-or-logical-host-name data could not be acquired.

S:

Continues command processing.

O:

Refer to jcs_log_failure.log to see if data exists at the collection source, and then manually acquire the data that could not be acquired.

KAVB7779-E

An attempt to create the directory (specified-path) has failed.

The specified-path directory could not be created.

S:

Terminates command processing.

O:

Carefully review the executing user's read and write permissions for the directory above the specified directory, and then run the data collection tool again.

KAVB7780-W

The directory used by the physical host was not found. (directory-path)

The directory being used by the physical host does not exist.

S:

Continues processing without acquiring data in directory-path.

O:

Determine whether directory-path is temporarily unavailable.

KAVB7782-W

An attempt to acquire the Windows event log (event-log-type) has failed.

An attempt to acquire the Windows event log failed.

Event log type: System or Application

S:

Continues command processing.

O:

Use the event viewer to acquire the Windows event log manually.

KAVB7790-I

The pre-installation processing of JP1/IM-Central Scope will now start.

Pre-installation processing of JP1/IM - Manager will start.

S:

Starts pre-installation processing of JP1/IM - Manager.

KAVB7791-E

A prerequisite product has not been installed.

A prerequisite product has not been installed.

S:

Suspends installation.

O:

Install the prerequisite product(s), and then re-install Central Scope Service.

KAVB7792-I

The pre-installation processing of JP1/IM - Central Scope will now end.

Pre-installation processing of JP1/IM - Manager will end.

S:

Terminates pre-installation processing of JP1/IM - Manager.

KAVB7793-I

The post-installation processing of JP1/IM - Central Scope will now start.

Post-installation processing of JP1/IM - Manager will start.

S:

Starts post-installation processing of JP1/IM - Manager.

KAVB7794-I

The JP1/IM - the Central Scope service will now be registered.

The JP1/IM - Manager service will be registered.

S:

Adds a port number to the /etc/services file.

KAVB7795-I

The JP1/IM - the Central Scope service was registered.

JP1/IM - Manager service was registered.

S:

Adds a port number to the /etc/services file.

KAVB7796-E

The JP1/IM - the Central Scope service could not be registered.

The JP1/IM - Manager service could not be registered.

S:

Continues installation.

O:

Wait until installation finishes, and then add a port number to /etc/services.

KAVB7797-I

The post-processing of JP1/IM - Central Scope installation will now end.

Post-installation processing of JP1/IM - Manager will end.

S:

Terminates post-installation processing of JP1/IM - Manager.

KAVB7798-I

The uninstallation of JP1/IM - Central Scope will now start.

JP1/IM - Manager uninstallation will start.

S:

Starts uninstalling JP1/IM - Manager.

KAVB7799-E

An attempt to set the system environment has failed.

An attempt to set up the system environment failed because the /opt/jp1cons/bin/jcoimdef command could not be executed normally.

S:

Continues processing.

O:

After uninstallation is finished, execute the /opt/jp1cons/bin/jcoimdef command manually, specifying -s and OFF as arguments.

KAVB7800-E

'/opt/jp1scope/bin/jcsdbsetup' could be executed.

An attempt to create a Central Scope database failed because the jcsdbsetup command could not be executed normally.

S:

Continues processing.

O:

After installation is finished, execute the jcsdbsetup command manually.

KAVB7801-E

'/opt/jp1scope/bin/jp1cs_setup' could be executed.

Central Scope setup processing failed because the jp1cs_setup command could not be executed normally.

S:

Continues processing.

O:

After installation is finished, execute the jp1cs_setup command manually.

KAVB7802-E

The stop of services failed.

An attempt to stop services failed.

S:

Suspends installation or uninstallation.

O:

Stop JP1/IM - Manager manually, and then install or uninstall.

KAVB7810-E

An error occurred during the initialization of the communication encryption function for the command "command-name". (cause = cause)

An error occurred during the initialization of the communication encryption function for a command.

S:

Does not execute the command.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB7812-E

Failed to encrypt communications by using the communication encryption function for the command "command-name". (host name of connection destination = connection-destination-host-name, cause = cause)

An attempt to encrypt communication with a communication destination failed.

S:

Does not execute the command.

O:

The setting of the communication encryption function might have changed since JP1/IM - Manager started. Restart JP1/Base and JP1/IM - Manager, apply the settings of the communication encryption function, and then re-execute the command. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB7813-E

A parameter of the communication encryption function for the command "command-name" is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function for a command is invalid.

S:

Does not execute the command.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A valid value is not specified for a parameter. is displayed for cause, set a valid value for the parameter in the common definitions of JP1/Base.

If The value of a parameter exceeds the maximum. is displayed for cause, set a value no longer than the maximum length for the parameter in the common definitions of JP1/Base.

KAVB7814-E

Parameters for the communication encryption function for the command "command-name" could not be collected. (parameter = parameter-name, cause = cause)

Parameters for the communication encryption function for a command could not be acquired.

S:

Does not execute the command.

O:

Re-execute the command. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB7818-E

A library required for the command "command-name" was not found.

A library required for a command was not found.

S:

Does not execute the command.

O:

If JP1/IM - Manager encrypts its communication, install JP1/Base appropriate for the version of JP1/IM - Manager, restart JP1/IM - Manager, and then re-execute the command.

If JP1/IM - Manager does not encrypt its communication, reinstall and set up JP1/Base and JP1/IM - Manager, restart JP1/IM - Manager, and then re-execute the command.

KAVB7900-I

Status of monitoring-node-name is changed status from status.

Reports that the status of a monitoring node has changed.

S:

The status of monitoring node monitoring-node-name has changed.

KAVB7901-W

The number of status change event for the monitored node monitoring-node-ID has reached the threshold.

The number of status change events for the monitoring node (monitoring-node-ID) exceeded the upper limit.

S:

Disables the linked functionality for which corrective action has already been taken for the monitoring node (monitoring-node-ID) and continues processing.

O:

Execute a status change event search, and then check the contents of the status change event. If it is not problematic to do so, manually change the status of the monitoring node, and then clear the history of the status change event.

2.9 JP1/IM-related common messages (KAVB8000 to KAVB8999)

KAVB8000-W

Option (specified-option) appears twice or more.

An option was specified more than once.

S:

Ignores the specified option and continues processing.

O:

Reset the option value, and then retry the operation.

KAVB8001-W

Specify an argument (argument-value) after the option (option).

The command could not be executed because no argument value was specified after the displayed option.

S:

Terminates processing.

O:

Specify an argument value after the displayed option.

KAVB8002-W

No Logical Host Name is specified.

No logical host name was specified for environment variable JP1_HOSTNAME.

S:

Uses the default logical host name and continues processing.

O:

If a logical host name must be specified, specify the environment variable, and then retry the operation.

KAVB8003-W

An invalid logical host name (logical-host-name) is specified.

The logical host name specified as the argument is invalid.

S:

Terminates processing.

O:

Specify a valid logical host name, and then retry the operation.

KAVB8051-I

The health check will now start. (host name = host-name)

The health check will start.

S:

Starts the health check.

KAVB8052-I

The health check will now stop. (host name = host-name)

The health check will end.

S:

Stops the health check.

KAVB8053-E

The health check will now stop because an error occurred. (host name = host-name) : maintenance-information

The health check stopped due to an error.

S:

Terminates the health check.

O:

Collect data, and then contact a system administrator.

KAVB8054-E

The definition file of the health check (file-name) cannot be opened. : maintenance-information

Cannot open the health check definition file.

S:

If JP1/IM - Manager is running, ignores the health check. If the jco_spmd_reload command is being executed, re-uses the current definitions and continues processing.

O:

Make sure that the health check definition file exists and that access permission is assigned correctly, and then execute the jco_spmd_reload command.

KAVB8055-E

There is an error in the definition file of the health check (file-name). The default value will be used. (line line-number) : detailed-information

The health check will be performed using the default values because an invalid value was specified in the health check definition file.

The character string that contained the error is shown in the detailed information.

S:

If JP1/IM - Manager is running, operates using default values only for those definition items with errors. If the jco_spmd_reload command is being executed, re-uses the current definitions only for those definition items with errors and continues processing.

O:

Make sure that the definition file is specified correctly, and then execute the jco_spmd_reload command.

KAVB8060-E

An abnormality was detected in function-name. (host name = host-name, process name = process-name, process ID = process-ID) : maintenance-information

A function abnormality was detected. The possible causes are as follows.

A process ended abnormally.

A process stopped responding.

The server or network is in high load status.

S:

Continues processing.

O:

Determine whether the server or network is in high load status.

If the load is high, take the following corrective actions.

In Windows:

For the evflow, evgen, evtcon, and jcfmain processes, execute the jcogencore command to output a dump for any function for which an abnormality was detected.

After a dump is output, use the data collection tool to collect data, and then contact a system administrator.

For the jcamain processes, no dump can be output. Use the data collection tool to collect data, and then restart JP1/IM - Manager.

In UNIX:

Execute the jcogencore command to output a dump for any function for which an abnormality was detected. Functions (processes) for which a dump was output will stop.

After a dump is output, use the data collection tool to collect data, and then contact a system administrator.

After executing the jcogencore command, restart JP1/IM - Manager.

KAVB8061-I

function-name has been recovered. (host name = host-name, process name = process-name, process ID = process-ID) : maintenance-information

The function was recovered.

S:

Continues processing.

KAVB8062-E

An abnormality was detected in function-name. (host name = host-name, process name = process-name) : maintenance-information

A function abnormality was detected. The possible causes are as follows.

A process ended abnormally.

A process stopped responding.

The server or network is in high load status.

S:

Continues processing.

O:

Determine whether the server or network is in high load status.

If the load is high, collect JP1/Base data, and then restart JP1/Base Event Service and JP1/IM - Manager.

KAVB8063-I

function-name has been recovered. (host name = host-name, process name = process-name) : maintenance-information

The function was recovered.

S:

Continues processing.

KAVB8064-W

The function function-name was detected not to be responding. (host name = host-name, process name = process-name)

The function indicated in the message is not responding.

S:

Continues the health check. If the function still does not respond, the system reports a health check function abnormality.

O:

The host may be in high load status. Check the load status. If it is high, reduce the load.

KAVB8070-E

The JP1 event event-ID could not be issued. : maintenance-information

A JP1 event could not be issued.

S:

Continues processing.

O:

Determine whether Event Service is running. If it is not running, start it.

KAVB8071-I

The JP1 event event-ID was issued.

A JP1 event was issued.

S:

Continues processing.

KAVB8072-E

The notification command command could not be executed. : maintenance-information

A notification command could not be executed.

S:

Continues processing.

O:

Make sure that the definition file is specified correctly, and then execute the jco_spmd_reload command.

KAVB8073-I

The notification command command was executed.

A notification command was executed.

S:

Continues processing.

KAVB8074-W

No notification command is specified. (file name = file-name)

No notification command was specified in the definition file.

S:

Suspends processing.

O:

If a notification command must be specified in the definition file, specify the notification command, and then retry the operation.

KAVB8080-W

An attempt to obtain the IPv4 address has failed.

An attempt to obtain the IPv4 address required for JP1/IM - Manager has failed.

S:

Continues processing.

O:

The JP1/Base settings on the manager host might have problems. Check whether the IPv4 address for the manager host is set in jp1hosts2 in JP1/Base.

If there is no problem with the JP1/Base settings, check for a network problem.

KAVB8101-E

An attempt to open the system file (file-name) has failed. : system-error-code

An attempt to open a system file managed by the system failed.

S:

If file-name is ecsseq.inf

If the attempt to open a file fails while reading a system file, events are stored in the event buffer starting from the JP1 event registered in the event database after Event Console Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

If the attempt to open a file fails while writing to a system file, the system deletes the system file and continues processing. After the system recovers from the error, the system file is created again. If the system does not recover from the error and the system file is not created again, events are stored in the event buffer starting from the JP1 event registered in the event database after Event Console Service starts when JP1/IM - Manager starts again.

If file-name is fcsseq.inf

If the attempt to open a file fails while reading a system file, action matching processing is performed starting from the JP1 event registered in the event database after Event Base Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

If the attempt to open a file fails while writing to a system file, the system deletes the system file and continues processing. After the system recovers from the error, the system file is created again. If the system does not recover from the error and the system file is not created again, action matching processing is performed starting from the JP1 event registered in the event database after Event Base Service starts when JP1/IM - Manager starts again.

If file-name is fcssendseq.inf

If an attempt to open the system file to be read fails, whether the events are response-waiting events is determined, starting from the JP1 event registered in the event database after Event Base Service started. This processing is performed even if the response-waiting event management is enabled in the system settings by using the jcoimdef command.

If an attempt to open the system file used for writing data fails, the system deletes the system file and continues processing. After the system recovers from the error, the system file is created again. If the system does not recover from the error, the system file is not created again. In this case, when JP1/IM - Manager restarts, the system determines whether the events are response-waiting events, starting from the JP1 event registered in the event database after Event Base Service started.

This message is not output again until the system file indicated by file-name is successfully opened.

O:

Check the OS log to determine whether a resource shortage occurred.

If no resource shortage occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB8102-E

The system file (file-name) will be created again because the file was corrupted. : data-content-of-corrupted-system-file

An attempt to read data failed because the contents of a system file managed by the system was were invalid.

S:

Deletes the existing system file and creates a new system file.

If file-name is ecsseq.inf

Events are stored in the event buffer starting from the JP1 event registered in the event database after Event Console Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

If file-name is fcsseq.inf

Action matching processing is performed starting from the JP1 event registered in the event database after Event Base Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

If file-name is fcssendseq.inf

Whether the events are response-waiting events is determined, starting from the JP1 event registered in the event database after Event Base Service started. This occurs even if the response-waiting event management is enabled in the system settings by using the jcoimdef command.

O:

If file-name is ecsseq.inf

Check the integrated trace log to see if an error message from Event Console Service (error messages KAVB0001 to KAVB2000) was output.

If a message was output, take the corrective action given for that message.

If file-name is fcsseq.inf or fcssendseq.inf

Check the integrated trace log to see if an error message from Event Base Service (error messages KAVB4001 to KAVB6000) was output.

If a message was output, take the corrective action given for that message.

Also check the OS log to determine whether a resource shortage occurred.

If no resource shortage occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB8103-E

An attempt to read data from the system file (file-name) has failed. : system-error-code

An attempt to read data from a system file being managed by the system failed.

S:

If file-name is ecsseq.inf

Events are stored in the event buffer starting from the JP1 event registered in the event database after Event Console Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

If file-name is fcsseq.inf

Action matching processing is performed starting from the JP1 event registered in the event database after Event Base Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

If file-name is fcssendseq.inf

Whether the events are response-waiting events is determined, starting from the JP1 event registered in the event database after Event Base Service started. This occurs even if the response-waiting event management is enabled in the system settings by using the jcoimdef command.

O:

Check the OS log to determine whether a resource shortage occurred.

If no resource shortage occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB8104-E

An attempt to write data to the system file (file-name) has failed. : system-error-code

An attempt to write data to a system file being managed by the system failed.

S:

Deletes the system file to which data could not be written and continues processing.

O:

Check the OS log to determine whether a resource shortage occurred.

If no resource shortage occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB8105-E

An attempt to delete the system file (file-name) has failed. : system-error-code

An attempt to delete a system file being managed by the system failed.

S:

Stops file deletion processing and continues processing.

O:

Check the OS log to determine whether a resource shortage occurred.

If no resource shortage occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB8106-E

function-name could not be started because the environment is invalid. (cause = cause, details = detailed-information)

The function indicated in function-name could not start due to an incorrect environment.

S:

Suspends processing.

O:

Check whether a system error occurred. Uninstall JP1/IM - Manager, re-install it, and then retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB8107-E

JP1/IM - View could not be started because the environment is invalid. (cause = cause, details = detailed-information)

JP1/IM - View could not start due to an incorrect environment.

S:

Suspends processing.

O:

Check whether a system error occurred. Uninstall JP1/IM - Manager, re-install it, and then retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB8108-E

The command (command-name) could not be executed because the environment is invalid. (cause = cause, details = detailed-information)

The command (command-name) could not start due to an incorrect environment.

S:

Suspends processing.

O:

Check whether a system error occurred. Uninstall JP1/IM - Manager, re-install it, and then retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB8109-E

The command (command-name) could not be executed because the environment is invalid. (cause = cause, details = detailed-information)

The command (command-name) could not start due to an incorrect environment.

S:

Suspends processing.

O:

Check whether a system error occurred. Uninstall JP1/IM - Manager, re-install it, and then retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB8201-E

The configuration definition information could not be acquired. (manager host name = manager-host-name)

The configuration definition information could not be acquired.

S:

Aborts counting of managed nodes for the manager host for which the configuration definition information could not be acquired, and then continues processing.

O:

Check the items below, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If this message appears during counting of managed nodes for a logical host, make sure that the shared disk can be accessed.

Check the following OS logs to make sure that there are sufficient OS resources such as file descriptors:

• In Windows: Windows event log

• In UNIX: System log (syslog)

KAVB8202-E

Information about the remote monitoring configuration could not be acquired. (manager host name = manager-host-name)

Information about the remote monitoring configuration could not be acquired.

S:

Aborts counting of managed nodes for the manager host for which information about the remote monitoring configuration could not be acquired, and then continues processing.

O:

Check the items below, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If this message appears during counting of managed nodes for a logical host, make sure that the shared disk can be accessed.

Check the following OS logs to make sure that there are sufficient OS resources such as file descriptors:

• In Windows: Windows event log

• In UNIX: System log (syslog)

If an application that locks files (such as virus check software) is running, this message might appear due to a contention with that application. Stop the application that locks files, and then retry the operation.

KAVB8203-E

The destination path could not be accessed. (path = path)

The output destination path cannot be accessed

S:

Terminates processing.

O:

Check the following items, and then re-execute the command:

Make sure there is no file with the same name as the output-destination folder or directory.

Make sure the output-destination folder or directory exists.

Make sure the output-destination folder or directory does not contain a folder or directory of the same name as the output file.

Make sure you have the necessary permissions to read from and write to the output-destination folder or directory. If you do not have the necessary permissions, set up read and write permissions for the output-destination folder or directory.

Make sure you have the necessary permissions to write to the output file. If you do not have the necessary permissions, set up write permissions for the output file.

KAVB8204-E

An attempt to output the file containing the list of managed nodes failed. (file = file-name)

An attempt to output the file containing the list of managed nodes failed.

S:

Terminates processing.

O:

Check the items below, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator

Check the following OS logs to make sure that there are sufficient OS resources such as file descriptors:

• In Windows: Windows event log

• In UNIX: System log (syslog)

If an application that locks files (such as virus check software) is running, this messages might appear due to a contention with that application. Stop the application that locks files, and then retry the operation.

Make sure you have the necessary permissions to read from and write to the output-destination folder or directory.

If you do not have the necessary permissions, set up read and write permissions for the output-destination folder or directory.

Make sure you have the necessary permissions to write to the output file. If you do not have the necessary permissions, set up write permissions for the output file.

KAVB8205-E

The file cannot be saved because the file name is too long. (file = file-name)

The length of the file name in the absolute path exceeds 250 characters.

S:

Terminates processing.

O:

Specify the file name using a maximum of 250 characters in the absolute path, and then re-execute the command.

KAVB8206-E

A memory shortage occurred.

A memory shortage occurred.

S:

Terminates processing.

O:

Check the memory usage, and then re-execute the command.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB8207-E

A system error occurred.

A system error occurred.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB8208-E

An attempt to output the file containing the list of managed nodes failed. (file = file-name)

An attempt to output the file containing the list of managed nodes failed.

S:

Terminates processing.

O:

Make sure that the file can be accessed by using the file name in absolute path format. If the file cannot be accessed, specify a file that can be accessed, and then re-execute the command.

KAVB8301-W

Parameters for the operation log output function for JP1/IM - Manager could not be collected. The default settings will be used, and processing will continue. (parameter = parameter-name, default value = default-value)

Parameters for the operation log output function for JP1/IM - Manager cannot be acquired.

S:

Continues startup processing of JP1/IM - Manager by using the default value of the parameter.

O:

Execute the jbsgetcnf command to make sure that the parameter value is correct.

If an error occurs again after you have confirmed that there is no problem, use the data collection tool to collect data, and then contact a system administrator.

KAVB8302-W

Parameters for the operation log output function for JP1/IM - Manager contained an error. The default settings will be used, and processing will continue. (parameter = parameter-name, default value = default-value)

Parameters for the operation log output function for JP1/IM - Manager contains an error.

S:

Continues startup processing of JP1/IM - Manager by using the default value of the parameter.

O:

Specify a valid value for the parameter.

Restart JP1/IM - Manager to apply the specified value to JP1/IM - Manager.

KAVB8303-W

Parameters for the operation log output function for JP1/IM - Manager contained an error. (parameter = parameter-name, cause = cause)

Parameters for the operation log output function for JP1/IM - Manager contains an error.

S:

Starts JP1/IM - Manager with the operation log output function disabled.

O:

Take the corrective action that is appropriate to the cause displayed, as described below.

If the problem cannot be resolved or if a message other than the following is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

If The specified file path exceeds the maximum length. is displayed for cause:

Make sure that the length of the path specified for the parameter is 217 bytes of less.

If The specified file path was not found. is displayed for cause:

Check whether the path specified for the parameter exists.

In addition, check whether the output destination of operation log files contains a folder or directory with the same name as an operation log file.

If such a folder or directory exists, delete it.

If The file path is not specified. is displayed for cause:

Specify a valid path for the parameter.

If The format of the specified file path is invalid. is displayed for cause:

Specify an absolute path for the parameter.

Restart JP1/IM - Manager to apply the value specified for the parameter to JP1/IM - Manager.

KAVB8304-E

An I/O error occurred while the operation log output function was starting.

The operation log output function was disabled, and data will no longer be output to the operation log.

An I/O error occurred during initialization of the operation log output function.

S:

Disables the operation log output function. Data is no longer output to the operation log.

O:

Check the items below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Make sure that the operation log file and the output destination directory for the operation log file exist.

If the operation log file and its output destination directory exist, check whether you have write permission.

If you do not have write permission, set appropriate write permission.

Make sure that there is sufficient free space at the output destination of the operation log file.

Check whether the output destination of operation log files contains a folder or directory with the same name as an operation log file.

If such a folder or directory exists, delete it.

Make sure that there is sufficient memory.

Check the following OS logs to make sure that there are sufficient OS resources such as file descriptors:

• In Windows: Windows event log

• In UNIX: System log (syslog)

KAVB8305-W

An attempt to output data to the operation log failed.

Processing will now continue without data being output to the operation log.

An attempt to output data to the operation log failed.

S:

Continues processing without outputting data to the operation log.

O:

Check the items below.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Make sure that the operation log file and the output destination directory for the operation log file exist.

If the operation log file and its output destination directory exist, check whether you have write permission.

If you do not have write permission, set appropriate write permission.

Make sure that there is sufficient free space at the output destination of the operation log file.

Check whether the output destination of operation log files contains a folder or directory with the same name as an operation log file.

If such a folder or directory exists, delete it.

Make sure that there is sufficient memory.

Check the following OS logs to make sure that there are sufficient OS resources such as file descriptors:

• In Windows: Windows event log

• In UNIX: System log (syslog)

KAVB8306-E

A system error occurred while the operation log output function was starting.

The operation log output function was disabled, and data will no longer be output to the operation log.

A system error occurred during initialization of the operation log output function.

S:

Disables the operation log output function. Data is no longer output to the operation log.

O:

Check the following, and then restart JP1/IM - Manager:

If an error message or a warning message was displayed immediately before this message, take the corrective action given for that message.

If an error message or a warning message was not displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB8307-W

A system error occurred while outputting the operation log. Processing will now continue without data being output to the operation log.

A system error occurred while data was being output to the operation log.

S:

Continues processing without outputting data to the operation log.

O:

Check the following:

If an error message or a warning message was displayed immediately before this message, take the corrective action given for that message.

If an error message or a warning message was not displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB8400-E

The option is invalid

An option was invalid.

S:

Terminates processing.

O:

Check the option, and then re-execute the command.

KAVB8402-E

Specify the process ID.

No process ID was specified.

S:

Terminates processing.

O:

Specify a process ID, and then re-execute the command.

KAVB8403-E

The process ID is specified more than once.

Multiple process IDs were specified.

S:

Terminates processing.

O:

Specify only one process ID, and then re-execute the command.

KAVB8404-E

Specify the process ID of control-name process.

The process ID of a JP1/IM - Manager or JP1/IM - View process was not specified.

S:

Terminates processing.

O:

Specify a process ID for the JP1/IM - Manager or JP1/IM - View process, and then re-execute the command.

KAVB8405-E

The process ID is invalid.

A process ID value is invalid.

S:

Terminates processing.

O:

Make sure that a process ID is specified, and then re-execute the command.

KAVB8406-I

The core dump file will be output.

A core dump file will be output.

S:

Continues processing.

KAVB8407-I

When the core dump is output, process-name will stop. Is this OK? (y/n)

Confirms that it is OK to execute a core dump output.

S:

Waits for a user response. If y is entered, continues processing. If n is entered, terminates the command.

O:

To continue command execution, enter y. To suspend command execution, enter n.

KAVB8408-E

The specified process is not running.

The specified process is not running.

S:

Terminates processing.

O:

Determine whether the process is running.

KAVB8409-E

An error occurred during command execution. (cause : reason)

An error occurred during command execution.

S:

Terminates processing.

O:

Eliminate the cause of the error, and then re-execute the command. If the command cannot be executed, use the data collection tool to collect data, and then contact a system administrator.

KAVB8410-E

The process management process of JP1/IM -View is not running.

The process management process of JP1/IM -View is not running.

S:

Terminates processing.

O:

Make sure that JP1/IM - View is running. Alternatively, make sure that the process management process (jcoview.exe) of JP1/IM - View is running.

KAVB8411-E

The user lacks execution permission.

The user does not have permission to execute the command.

S:

Terminates processing.

O:

Log in as a user with Administrator or similar permissions, and then re-execute the command.

KAVB8412-E

JP1/IM - Manager is not running.

JP1/IM - Manager is not running.

S:

Terminates processing.

O:

Make sure that JP1/IM - Manager is running.

KAVB8413-E

An attempt to send the thread dump output request has failed.

An attempt to send a thread dump output request failed.

S:

Terminates processing.

O:

Check the following items:

In JP1/IM - View, make sure that JP1/IM - View process management (jcoview.exe) is running.

In JP1/IM - Manager, make sure that the process management process (jco_spmd.exe) is running.

KAVB8414-I

The thread dump output request has been sent.

A thread dump output request transmission was completed.

S:

Continues processing.

KAVB8415-E

An attempt to open the message file has failed.

An attempt to open a message file failed.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB8416-I

The core dump file has been output.

The core dump file was output.

S:

Continues processing.

KAVB8417-I

Please enter a number for the process to output the core dump file [1-7]:

Enter the number for the process to output the core dump file.

S:

Waits for entry of information.

O:

Enter the number for the process to output the core dump file.

KAVB8418-E

The specified logical host name does not exist.

The specified logical host does not exist.

S:

Terminates processing.

O:

Check the specified logical host name, and then re-execute the command.

KAVB8419-E

An attempt to read a shared configuration definition has failed.

An attempt to read common definition information failed.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB8420-E

Specify the process name of JP1/IM - Manager.

The JP1/IM - Manager process name was not specified.

S:

Terminates processing.

O:

Specify the JP1/IM - Manager process name, and then re-execute the command.

KAVB8421-E

The process management daemon is busy.

A command is being processed.

S:

Terminates processing.

O:

Wait until processing is finished, and then re-execute the command.

KAVB8422-E

The lock file in the conf directory cannot be opened.

An attempt to open a lock file failed.

S:

Terminates processing.

O:

Make sure that the conf directory exists and that the user has write permission. If operating in a cluster environment, make sure that the defined conf directory exists and that the user has write permission.

KAVB8423-I

The core dump file (file-name) will be overwritten. Is this OK? (y/n):

Confirms that it is OK to overwrite the core dump file.

O:

Enter y to overwrite the core dump file. Enter n to cancel overwriting of the core dump file.

KAVB8424-I

Please enter a number for the process to output the dump file [1-6]:

Enter a number for the process to output the dump file.

KAVB8425-E

The process information could not be obtained by the process management daemon. (cause: reason)

An attempt to acquire information for the process to output the core dump file failed.

S:

Terminates command execution.

O:

Execute the jco_spmd_status command to determine whether process management is operating normally.

If the jco_spmd_status command ends abnormally, check the integrated trace log to see if a process management error message was output.

If a message was output, take the corrective action given for that message.

If the problem cannot be resolved by the above method, use the data collection tool to collect data, and then contact a system administrator.

KAVB8426-I

The process to output the dump is not running.

A dump could not be output because JP1/IM - Manager processes that are able to output a dump were stopped.

S:

Terminates command execution.

KAVB8427-I

When outputting dumps for the three processes evflow, jcamain, and evtcon at the same time, output the dumps in order of evtcon, jcamain, and evflow.

When outputting dumps for the evflow, jcamain, and evtcon processes at the same time, output the dumps in the order evtcon, jcamain, evflow.

S:

Continues command processing.

KAVB8428-W

The core dump file was not found.

No core dump file was found due to one of the following reasons:

No core dump file was output.

The output directory for the core dump file or the file name was changed.

S:

Continues command processing.

O:

Check the following items:

Is there sufficient disk space?

Core dump files are output to the default output directories shown below. If there is insufficient free space, no core dump file is output.

- For a physical host: /var/opt/jp1cons/log/

- For a logical host: shared-directory/jp1cons/log/

Is the size of the core dump file set to 0?

Check the root user's file size setting for core dump files. If the size of the core dump file is set to 0, no core dump file is output.

Was the kernel parameter related to core dump files changed from the default setting? (For Linux only)

If the Linux kernel parameter specifying the core dump file's output directory and file name was changed from the default, the output core dump file will not be found.

Check the setting of the kernel.core_pattern kernel parameter, which changes the core dump file's output directory or file name.

If the core dump file's output directory or file name was changed from the default settings, the data collection tool may not be able to collect the core dump file when the tool is executed. The data collection tool collects the files whose names begin with core in the default output directories shown below.

For a physical host: /var/opt/jp1cons/log/

For a logical host: shared-directory/jp1cons/log/

To collect previously output core dump files using the data collection tool, you must take the following actions before executing the data collection tool.

If the core dump file's output directory was changed:

Copy the core dump file that was output to the default output directory.

If the core dump file's name was changed:

Rename the core dump file that was output to a file name that begins with core.

KAVB8430-E

The file cannot be saved because of an invalid file name. (file=file-name)

The file cannot be saved because the file name is invalid. Invalid file names as are follows.

Names that include any of the following characters: :, ?, ", <, >, |

Exact matches of any of the following characters strings (including lower case): CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

Any of the file names in 1 or 2 with a suffix of .xxx (xxx can be any characters).

(Example)CON.txt, PRN.txt.conf

S:

Suspends processing.

O:

Correct the file and directory names, and then retry the operation.

KAVB8450-I

The reference/operation permission function of the business group has been enabled.

The reference/operation permission function of the business group was enabled.

S:

Continues processing.

KAVB8451-W

A prerequisite function of the reference/operation permission function of the business group is not enabled.(cause = cause)

To use the reference/operation permission function of the business group, you must enable the event storage function, IM Configuration Management Service, and the event-source host mapping function.

S:

Continues processing.

O:

Take one of the following actions depending on the cause of the error indicated in the message.

The integrated monitoring database is currently disabled.

Use the jcoimdef command to enable the event storage function, and then restart JP1/IM - Manager.

The IM Configuration Management service is not running.

Use the jcoimdef command to specify the settings that start IM Configuration Management Service, and then restart JP1/IM - Manager.

The event-source-host mapping function is currently disabled.

Use the jcoimdef command to enable the event-source host mapping function, and then restart JP1/IM - Manager.

KAVB8452-E

The operation cannot be executed because the reference/operation permission function of the business group changed from active to inactive while logged in.

The operation cannot be performed because the reference/operation permission function of the business group was disabled during login.

S:

Aborts processing.

O:

Log in to the system again, and then retry the operation.

KAVB8453-I

The business group was updated. Processing will be performed from the next-received event. (last received event: reception time = reception-time, event database serial number = event-database-serial-number)

The business group was updated. Processing will be performed from the next received event.

S:

Continues processing.

KAVB8454-W

The business group could not be updated. (cause = cause)

The business group could not be updated.

S:

Continues processing without updating the business group, but using the business group before change.

O:

If using the communication encryption function, check whether the settings of the function are incorrect.

If not using the communication encryption function, take the corrective action as appropriate for the cause.

The IM database service is not running.

Make sure that the IM database service is running, and then restart JP1/IM - Manager.

A connection error has occurred.

The system might be temporarily unable to acquire or use a connection.

If the error cannot be resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.

A communication error has occurred.

A memory shortage has occurred.

Check whether a shortage has occurred in other OS resources such as memory and file descriptors, and then restart JP1/IM - Manager.

If the error cannot be resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.

The integrated monitoring database has not been set up.

Use the jcodbsetup command to set up the integrated monitoring database, and then restart JP1/IM - Manager.

The integrated monitoring database is currently inactive.

Enable the integrated monitoring database, and then restart JP1/IM - Manager.

An error occurred while applying the business group.

Check whether JP1/IM - Manager is in high load status. If the same message appears when you retry the operation, collect JP1/IM data, and then contact a system administrator.

An unexpected error has occurred.

Collect JP1/IM data, and then contact a system administrator.

KAVB8456-E

The business group could not be updated. (cause = cause)

The business group could not be updated during startup of JP1/IM - Manager.

S:

Continues processing without updating the business group.

O:

Take corrective action depending on the cause of the error.

The IM database service is not running.

Make sure that the IM database service is running, and then restart JP1/IM - Manager.

A connection error has occurred.

The system might be temporarily unable to acquire or use a connection.

If the error cannot be resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.

A communication error has occurred.

A memory shortage has occurred.

Check whether a shortage has occurred in other OS resources such as memory and file descriptors, and then restart JP1/IM - Manager.

If the error cannot be resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.

The IM Configuration Management database has not been set up.

Use the jcfdbsetup command to set up the IM configuration monitoring database, and then restart JP1/IM - Manager. If you do not use IM Configuration Management Service, use the jcoimdef command with the -cf option specified to disable startup of IM Configuration Management Service, and then restart JP1/IM - Manager

An unexpected error has occurred.

Collect JP1/IM data, and then contact a system administrator.

KAVB8457-E

The business group or monitoring group can now be specified or cannot now be specified because a manager setting was changed during login. Please log in again.

The business group or monitoring group can now be specified or can no longer be specified because the manager setting was changed during login. Log in to the system again.

S:

Suspends processing.

O:

Log in to the system again.

KAVB8500-E

Execute the command from the administrator console.

This command must be executed from the administrator console.

S:

Terminates command processing.

O:

Execute the command from the administrator console.

KAVB8550-E

The manual has not been moved.

The product directory does not include the manual.

S:

Suspends processing.

O:

Copy the electronic manual from the media that comes with the product.

KAVB8551-E

Help for this screen cannot be found.

The manual in the product directory might be old or incorrect.

S:

Suspends processing.

O:

Copy the electronic manual from the media that comes with the product.

KAVB8552-E

The manual is corrupted. Reinstall JP1/IM.

The manual cannot be displayed because it is in invalid state.

S:

Suspends processing.

O:

If you are using JP1/IM - View, re-install it.

If you are using the Web version of the Event Console window, re-install JP1/IM - Manager.

KAVB8600-I

The service control-name confirmed that the IM database service started.

The control-name process confirmed that the IM database service is running.

S:

Continues processing.

KAVB8601-I

The service control-name is waiting for the IM database service to start.

The control-name process is waiting for completion of IM database service startup.

S:

Waits for the IM database service to start.

KAVB8602-E

The service control-name could not be started because the status of the IM database service could not be confirmed. (details = reason)

The control-name process could not start because completion of IM database service startup could not be confirmed.

S:

The control-name process stops.

O:

Take corrective action based on the reason:

Reason: Processing to start or stop the IM database service is being performed.

Reason: The IM database service stopped.

Execute the jimdbstatus command, confirm that the IM database service is running, and then perform the next operation.

In Windows:

- Start the IM database service, and then restart JP1/IM - Manager.

In UNIX:

- Stop JP1/IM - Manager, and then re-execute the jco_start command.

If this error occurs when the OS is starting, specify the following common definition information, and then increase the number of retries so that it does not time out.

- [logical-host-name\JP1CONSOLEMANAGER\IMDB]

- DB_START_RETRY_COUNT

Reason: The restart of the IM database service was interrupted.

Execute jimdbstop -f, forcibly stop the IM database service, and then perform the next operation.

In Windows:

- Start the IM database service, and then restart JP1/IM - Manager.

In UNIX:

- Re-execute the jco_start command.

Reason: The IM database service has not been set up.

Set up the IM database service, and then start JP1/IM - Manager.

Reason: The status of the IM database service could not be confirmed.

Reason: A system error occurred.

Collect JP1/IM data, and then contact a system administrator.

KAVB8603-E

A request cannot be executed because the service control-name is waiting for the IM database service to start.

Processing could not be performed because the control-name process is waiting for completion of IM database service startup.

S:

Terminates processing.

O:

Execute the jimdbstatus command, and then check the status of the IM database service on the manager host.

Make sure that the IM database service is running, and then retry the operation.

If a KAVB8602-E message was output to the integrated trace log on the manager host, take the corrective action given for the KAVB8602-E message.

KAVB8604-I

A connection to the Integrated Monitoring database has been established.

A connection to the integrated monitoring database was established.

S:

Connects to the integrated monitoring database.

KAVB8605-E

Initialization of the Integrated Monitoring database API has failed. (reason = reason)

An attempt to initialize the integrated monitoring database API failed.

S:

Suspends processing.

O:

Determine whether the port number assigned to the IM database service is being used by another product.

If another product is using the same port, specify a unique port number for the IM database service.

If another product is not using the same port, or the error cannot be resolved by reassigning the port number, collect JP1/IM data, and then contact a system administrator.

KAVB8606-E

An attempt to establish a connection when initializing the Integrated Monitoring database has failed. (reason = reason)

An attempt to establish a connection when initializing the integrated monitoring database failed.

S:

Suspends processing.

O:

Take corrective action based on the reason.

Reason: An error occurred because a service is not running.

Make sure that the IM database service is running, and then restart JP1/IM - Manager.

Reason: A connection error occurred.

The system may be temporarily unable to acquire a connection or to use a connection. If the error is not resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.

Reason: A system error occurred.

Determine whether the port number assigned to the IM database service is being used by another product.

If another product is using the same port, specify a unique port number for the IM database service. If another product is not using the same port, or the error cannot be resolved by reassigning the port number, collect JP1/IM data, and then contact a system administrator.

KAVB8607-E

Initialization of an Integrated Monitoring database table has failed. (reason = reason)

An error occurred during initialization of the integrated monitoring database table.

S:

Suspends processing.

O:

Take corrective action based on the reason.

Reason: An error occurred because a service is not running.

Make sure that the IM database service is running, and then restart JP1/IM - Manager.

Reason: A communication error occurred. or A resource shortage occurred.

Make sure that there are sufficient OS resources such as memory and file descriptors, and then restart JP1/IM - Manager. If the error is not resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.

Reason: A connection error occurred.

The system may be temporarily unable to acquire a connection or to use a connection. If the error is not resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.

Reason: A system error occurred.

Determine whether the port number assigned to the IM database service is being used by another product.

If another product is using the same port, specify a unique port number for the IM database service. If another product is not using the same port, or the error cannot be resolved by reassigning the port number, collect JP1/IM data, and then contact a system administrator.

KAVB8608-W

The function "function-name" cannot be used because an attempt to check the table schema of an IM database service failed.

A function cannot be used because an attempt to check the table schema of an IM database service failed.

S:

Continues Event Base Service startup processing.

O:

Check to see if a shortage has occurred in an OS resource such as available memory or file descriptors, and then restart JP1/IM - Manager.

If restarting JP1/IM - Manager does not resolve the problem, collect JP1/IM data, and then contact a system administrator.

KAVB8609-W

The function "function-name" cannot be used because an IM database service has not been updated.

A function cannot be used because an IM database service has not been updated.

S:

Continues Event Base Service startup processing.

O:

Stop JP1/IM - Manager, update the integrated monitoring database with the jimdbupdate command, and then restart JP1/IM - Manager.

KAVB8610-W

Please update the IM database service.

A previous version of the IM database service is being used. Please update to the most recent version.

S:

Continues Event Base Service startup processing.

O:

Stop JP1/IM - Manager, update the integrated monitoring database with the jimdbupdate command, and then restart JP1/IM - Manager.

KAVB8701-E

The option (option) is invalid.

An invalid option is specified.

S:

Terminates processing.

O:

Specify the option correctly.

KAVB8702-E

An essential option (option) is not specified.

A required option is not specified.

S:

Terminates processing.

O:

Specify the option correctly.

KAVB8703-E

The option (option) is duplicated.

The option is specified more than once.

S:

Terminates processing.

O:

Specify the option correctly.

KAVB8704-E

Specify an argument (argument-value) after the option (option).

The command could not be executed because no argument value was specified after the indicated option.

S:

Terminates processing.

O:

Specify an argument value after the displayed option.

KAVB8705-E

The option option and the option option cannot be specified at the same time.

Processing cannot be executed because options that cannot be specified at the same time are specified.

S:

Terminates processing.

O:

Specify the options correctly.

KAVB8706-E

The specified email address exceeds the maximum length. (maximum length = maximum-length bytes)

The specified email address exceeds the maximum length.

S:

Terminates processing.

O:

Revise the specified email address, and then retry the operation.

KAVB8707-E

The specified email address is invalid.

The specified email address includes characters that cannot be used.

S:

Terminates processing.

O:

Revise the specified email address, and then retry the operation.

KAVB8708-E

The subject of the specified email exceeds the maximum length. (maximum length = maximum-length bytes)

The subject of the specified email exceeds the maximum length.

S:

Terminates processing.

O:

Revise the subject of the specified email, and then retry the operation.

KAVB8709-E

The body of the specified email exceeds the maximum length. (maximum length = maximum-length bytes)

The body of the specified email exceeds the maximum length.

S:

Terminates processing.

O:

Revise the body of the specified email, and then retry the operation.

KAVB8710-E

The specified password exceeds the maximum length. (maximum length = maximum-length bytes)

The specified password exceeds the maximum length.

S:

Terminates processing.

O:

Revise the specified password, and then retry the operation.

KAVB8711-E

An invalid logical host name (logical-host-name) is specified.

The specified logical host name is invalid.

S:

Terminates processing.

O:

Specify the correct logical host name, and then retry the operation.

KAVB8712-E

The address of the recipient is not specified.

The destination email address is not specified.

S:

Terminates processing.

O:

Use either of the following to specify the destination email address, and then retry the operation:

-to option of the jimmail command

DefaultTo parameter in the email environment definition file

KAVB8713-E

Failed to read the email environment definition file. (reason = reason)

An attempt to read the email environment definition file has failed.

S:

Terminates processing.

O:

Take corrective action based on the reason.

Reason: The file could not be locked.

An attempt to acquire exclusive permission for the file failed. Re-execute the command.

Reason: The file was not found.

Check whether the email environment definition file exists at the storage location.

If the file does not exist, create the file by copying the model file of the email environment definition file, and then specify the definition again.

Reason: An I/O error occurred.

Check whether you have permission to access the email environment definition file.

Also check whether the file system is normal.

If the system does not recover from the error after re-executing the command, collect data for JP1/IM, and then contact a system administrator.

KAVB8714-E

The definition contents of the email environment definition file are invalid. (parameter name = parameter-name, reason = reason)

The definition contents of the email environment definition file are invalid.

S:

Terminates processing.

O:

Take corrective action based on the reason, and then re-execute the command.

Reason: No parameter is specified.

Define the parameter in the email environment definition file.

Reason: The parameter value is not specified.

Define the value of the parameter.

Reason: The parameter is specified more than once.

The parameter is specified more than once. Revise the definition.

Reason: At least one unusable character is specified.

The setting specified for the parameter contains unusable characters. Revise the setting.

Reason: The set value is invalid.

Revise the setting of the parameter.

Reason: The set value exceeds the maximum length.

Revise the maximum length for the setting of the parameter.

Reason: The number of parameters exceeds the maximum number that can be specified.

Revise the number of values specified for the parameter.

Reason: An invalid parameter is specified.

Specify the correct parameter.

KAVB8715-W

The email environment definition file is invalid. The command will continue processing by using the default value. (parameter name = parameter-name, default value = default-value, reason = reason)

The definition of the email environment definition file contains an error.

S:

Assumes the default value to continue processing.

O:

Take corrective action based on the reason.

Reason: No parameter is specified.

Define the parameter in the email environment definition file.

Reason: The parameter value is not specified.

Define the value of the parameter.

Reason: At least one unusable character is specified.

The setting specified for the parameter contains a character that cannot be used. Revise the setting.

Reason: An unusable character encoding is specified.

Check the character encoding specified for the Charset parameter in the email environment definition file.

Reason: The port number is not a numerical value. The port number is outside the range of specifiable values.

Revise the port number specified for the parameter. You can specify port numbers in the range from 1 to 65535.

Reason: The set value is invalid.

Revise the setting of the parameter.

Reason: The set value exceeds the maximum length.

Revise the maximum length for the setting of the parameter.

KAVB8716-E

The connection to an SMTP server timed out. (SMTP-server-name:port-number)

A timeout occurred during connection to the SMTP server.

S:

Terminates processing.

O:

A timeout occurred because the server or network was in high load status. Wait a while and then retry the operation. If this message is output frequently, change the timeout values specified for ConnectTimeout and SoTimeout in the email environment definition file according to your operation.

KAVB8717-E

The connection to an SMTP server was refused. (SMTP-server-name:port-number, reason = reason)

An error occurred during connection to the SMTP server.

S:

Terminates processing.

O:

Take corrective action based on the reason.

Reason: The connection-destination host is not found.

Check the following items, and then re-execute the command:

- Is the host name of the SMTP server correct?

- Can the host name for the SMTP server be resolved?

- Is the SMTP port number correct?

Reason: The command cannot connect to the host.

Check the following items, and then re-execute the command:

- Is the SMTP server running?

- Are the SMTP server and manager host connected correctly?

- Has a communication error occurred?

Reason: A mail server error = message

Check the message, and then re-execute the command. If the system does not recover from the error, collect data for JP1/IM, and then contact a system administrator.

KAVB8718-E

An error occurred while an SMTP server was being connected to. (details = detailed-information)

An error occurred during connection to the SMTP server.

S:

Terminates processing.

O:

Collect data, and then contact a system administrator.

KAVB8719-E

An SMTP server refused the login attempt. (SMTP-server-name:port-number)

Authentication with the SMTP server has failed.

S:

Terminates processing.

O:

Revise the authentication account defined in the email environment definition file and the authentication password set by using the jimmailpasswd command.

KAVB8720-E

The connection to a POP3 server timed out. (POP3-server-name:port-number)

A timeout occurred during connection to the POP3 server.

S:

Terminates processing.

O:

A timeout occurred because the server or network was in high load status. Wait a while and then retry the operation. If this message is output frequently, change the timeout values specified for ConnectTimeout and SoTimeout in the email environment definition file according to your operation.

KAVB8721-E

The connection to a POP3 server was refused. (POP3-server-name:port-number, reason = reason)

An error occurred during connection to the POP3 server.

S:

Terminates processing.

O:

Take corrective action based on the reason.

Reason: The connection-destination host is not found.

Check the following items, and then re-execute the command:

- Is the host name of the POP3 server correct?

- Can the host name for the POP3 server be resolved?

- Is the POP3 port number correct?

Reason: The command cannot connect to the host.

Check the following items, and then re-execute the command:

- Is the POP3 server running?

- Are the POP3 server and manager host connected correctly?

- Has a communication error occurred?

Reason: A mail server error = message

Check the message, and then re-execute the command. If the system does not recover from the error, collect data for JP1/IM, and then contact a system administrator.

KAVB8722-E

An error occurred while a POP3 server was being connected to. (details = detailed-information)

An error occurred during connection to the POP3 server.

S:

Terminates processing.

O:

Collect data, and then contact a system administrator.

KAVB8723-E

A POP3 server refused the login attempt. (POP3-server-name:port-number)

Authentication with the POP3 server has failed.

S:

Terminates processing.

O:

Revise the authentication account defined in the email environment definition file and the authentication password set by using the jimmailpasswd command.

KAVB8724-W

Part of the subject of the email was truncated.

Part of the subject of the email was truncated because the subject exceeds the maximum length.

S:

Continues processing.

O:

Revise the subject of the email so that it does not exceed the maximum size.

KAVB8725-E

The number of specified email addresses exceeds the maximum. (maximum number = maximum-number-of-addresses)

The number of specified email addresses exceeds the maximum.

S:

Terminates processing.

O:

Revise the specified email addresses, and then retry the operation.

KAVB8726-E

An error occurred while the email was being sent. (reason = reason)

An error occurred while the email was being sent.

S:

Terminates processing.

O:

Take corrective action based on the reason.

Reason: The connection-destination host is not found.

Check the following items, and then re-execute the command:

- Is the host name of the SMTP server correct?

- Can the host name for the SMTP server be resolved?

- Is the SMTP port number correct?

Reason: The command cannot connect to the host.

Check the following items, and then re-execute the command:

- Is the SMTP server running?

- Are the SMTP server and manager host connected correctly?

- Has a communication error occurred?

Reason: A timeout occurred in the send processing.

A timeout occurred because the server or network was in high load status. Wait a while and then retry the operation

If this message is output frequently, change the timeout values specified for ConnectTimeout and SoTimeout in the email environment definition file according to your operation.

Reason: A mail server error = message

Check the message, and then re-execute the command.

If the system does not recover from the error, collect data for JP1/IM, and then contact a system administrator.

KAVB8727-E

No executing permission.

You do not have permission to execute the command.

S:

Aborts processing.

O:

Log in as a user with execution permission, such as an administrator, and then retry the operation.

KAVB8728-E

Failed to set the password. (reason = reason)

An attempt to write the password failed.

S:

Terminates processing.

O:

Take corrective action based on the reason, and then re-execute the jimmailpasswd command.

Reason: The file was not found.

Check whether the email environment definition file exists at the storage location.

If the file does not exist, create the file by copying the model file of the email environment definition file, and then specify the definition again.

If the email environment definition file exists, check whether you have access permissions to read and write the file.

Reason: An I/O error occurred.

Check whether you have access permissions to read and write the email environment definition file.

Also check whether the file system is normal.

If the system does not recover from the error after re-executing the command, collect data for JP1/IM, and then contact a system administrator.

KAVB8729-I

The email was successfully sent.

The email was successfully sent.

KAVB8730-I

The password was successfully set.

The password was successfully set.

KAVB8731-I

The command (command-name) has started.

The command has started.

KAVB8732-I

The command (command-name) terminates normally.

The command terminated normally.

KAVB8733-I

The command (command-name) terminates abnormally.

The command terminated abnormally.

KAVB8734-I

The password was successfully deleted.

The password was successfully deleted.

KAVB8735-I

A password is not set.

A password is not set.

KAVB8736-E

The authentication method is not configured correctly.

The authentication method is not configured correctly.

S:

Terminates processing.

O:

Specify POP or SMTP as the value of the AuthMethod parameter in the email environment definition file.

KAVB8737-E

The specified password is invalid. Multi-byte characters cannot be used.

The specified password is invalid. Multi-byte characters cannot be used in the password.

S:

Terminates processing.

O:

Multi-byte characters cannot be used in the password.

Only one-byte characters can be used in the password.

Revise the specified password, and then re-execute the command.

KAVB8738-E

A memory shortage occurred during execution of the command. (command-name)

A memory shortage occurred during execution of the command.

S:

Terminates processing.

O:

Allocate sufficient memory to execute the command, and then re-execute the command.

KAVB8739-E

A system error occurred while executing the command (command-name).Details:(detailed-information)

A system error occurred during execution of the command.

S:

Terminates processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB8740-E

An exception occurred while the log output was being prepared.

A system error occurred during startup of the command.

S:

Terminates processing.

O:

Collect the trace information output to the standard error output, use the data collection tool to collect data, and then contact a system administrator.

KAVB8741-E

The argument value (argument) of the option (option) is invalid.

The argument value of the option is not correct.

S:

Terminates processing.

O:

Specify the value of the option correctly.

KAVB8800-E

An attempt to stop the JP1/IM - Manager has failed.

JP1/IM - Manager did not stop after a retry was performed.

S:

Terminates the command.

O:

Execute the jco_spmd_status command, and then check the status of JP1/IM - Manager. If JP1/IM - Manager has not stopped, re-execute the jco_stop command.

If using the IM database service, execute the jimdbstatus command, and then check the status of the IM database service. If the IM database service has not stopped, re-execute the jco_stop command.

KAVB8801-E

An attempt to stop the IM Database service has failed.

The IM database did not stop after a retry was performed.

S:

Terminates the command.

O:

Execute the jimdbstatus command, and then check the status of the IM database service. If the IM database service has not stopped, re-execute the jco_stop command.

KAVB8810-I

JP1/IM - Manager is running with the communication encryption function enabled.

The communication encryption function is enabled in the common definitions of JP1/Base, so JP1/IM - Manager is running with the communication encryption function enabled.

S:

JP1/IM - Manager runs with the communication encryption function enabled.

KAVB8811-I

JP1/IM - Manager is running with the communication encryption function disabled.

The communication encryption function is disabled in the common definitions of JP1/Base, so JP1/IM - Manager is running with the communication encryption function disabled.

S:

JP1/IM - Manager runs with the communication encryption function disabled.

KAVB8812-W

Failed to delete the keystore used by the communication encryption function for JP1/IM - Manager. (file = file-name)

An attempt to delete the keystore used by the communication encryption function of JP1/IM - Manager failed.

S:

Continues startup or stop processing of JP1/IM - Manager.

O:

Determine whether you have write permission for the directories listed below. If not, set the permissions for these directories.

In Windows

Physical host: manager-path\conf\ssl

Logical host: shared-directory\JP1IMM\conf\ssl

In UNIX

Physical host: /etc/opt/jp1imm/conf/ssl

Logical host: shared-directory/jp1imm/conf/ssl

Determine whether a keystore exists. If it does, delete the keystore.

KAVB8813-E

Failed to create the keystore to be used by the communication encryption function for JP1/IM - Manager. (file = file-name)

An attempt to create a keystore to be used by the communication encryption function of JP1/IM - Manager failed.

S:

Stops startup processing of JP1/IM - Manager.

O:

Check the following, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Determine whether you have write permission for the directories listed below. If not, set permissions for these directories.

In Windows

Physical host: manager-path\conf\ssl

Logical host: shared-directory\JP1IMM\conf\ssl

In UNIX

Physical host: /etc/opt/jp1imm/conf/ssl

Logical host: shared-directory/jp1imm/conf/ssl

Determine whether a keystore exists. If it does, delete the keystore.

KAVB8814-E

A parameter of the communication encryption function for JP1/IM - Manager is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function of JP1/IM - Manager is invalid.

S:

Stops startup processing of JP1/IM - Manager.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A valid value is not specified for a parameter. is displayed for cause, set a valid value for the parameter in the common definitions.

If The value of a parameter is null. is displayed for cause, set a value for the parameter in the common definitions.

If The value of a parameter exceeds the maximum. is displayed for cause, set a value no longer than the maximum length for the parameter in the common definitions.

If The value of a parameter is not a full path. is displayed for cause, set a full path as the value for the parameter in the common definitions.

KAVB8815-E

Parameters for the communication encryption function for JP1/IM - Manager could not be collected. (parameter = parameter-name, cause = cause)

A parameter of the communication encryption function of JP1/IM - Manager could not be acquired.

S:

Stops startup processing of JP1/IM - Manager.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If A parameter is not defined. is displayed for cause, set the parameter in the common definitions.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact a system administrator.

KAVB8816-E

A file or directory specified for a parameter of the communication encryption function for JP1/IM - Manager was not found. (parameter = parameter-name, parameter value = parameter-value)

A file or directory was not found at the path specified by a parameter of the communication encryption function of JP1/IM - Manager.

S:

Stops startup processing of JP1/IM - Manager.

O:

Check the following, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Determine whether the file or directory corresponding to the parameter exists at the path specified by the parameter. If the file or directory corresponding to the parameter does not exist, create it.

If the path specified by a parameter is for a private key or server certificate, check whether you have read permission for the file. If not, set read permission for the file.

KAVB8817-E

A file specified for a parameter of the communication encryption function for JP1/IM - Manager could not be read. (parameter = parameter-name, parameter value = parameter-value)

A file specified by a parameter of the communication encryption function of JP1/IM - Manager cannot be read.

S:

Stops startup processing of JP1/IM - Manager.

O:

Check the following, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Check for problems with the format of the file at the path specified by the parameter.

Check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as file descriptors.

• In Windows: Windows event log

• In UNIX: System log (syslog)

KAVB8818-E

A private key specified for a parameter of the communication encryption function for JP1/IM - Manager could not be read. (parameter for the private key = parameter-name, parameter value for the private key = parameter-value, parameter for the server authentication certificate = parameter-name, parameter value for the server authentication certificate = parameter-value)

A private key specified by a parameter of the communication encryption function of JP1/IM - Manager cannot be read or is not paired with a server certificate.

S:

Stops startup processing of JP1/IM - Manager.

O:

Check the following, and then restart JP1/IM - Manager.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Check whether the server certificate and private key are paired. If they are not, put a paired server certificate and private key in place.

Check for problems with the format of the private key file.

If a pass phrase has been set for the private key, cancel the pass phrase.

Check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as file descriptors.

• In Windows: Windows event log

• In UNIX: System log (syslog)

KAVB8819-E

A library required for JP1/IM - Manager was not found.

A library required for JP1/IM - Manager was not found.

S:

Stops startup processing of JP1/IM - Manager.

O:

If JP1/IM - Manager encrypts its communication, install JP1/Base appropriate for the version of JP1/IM - Manager and then restart JP1/IM - Manager.

If JP1/IM - Manager does not encrypt its communication, reinstall and set up JP1/Base and JP1/IM - Manager, and then restart JP1/IM - Manager.

KAVB8820-W

The directory of the keystore used by the communication encryption function for JP1/IM - Manager was not found. Therefore, the directory will be created, and processing will continue. (directory = directory-name)

The directory where the keystore used by the communication encryption function for JP1/IM - Manager is to be stored was not found, so it will be created and processing will continue.

S:

Continues startup processing of JP1/IM - Manager.

KAVB8900-E

The command option is invalid.

The specified command option is invalid.

S:

Suspends command processing.

O:

Specify a valid command option, and then run the data collection tool again.

KAVB8901-E

The command option (option) is duplicated.

The specified command option (option) was duplicated.

S:

Suspends command processing.

O:

Specify a valid command option, and then run the data collection tool again.

KAVB8902-E

The logical host (logical-host-name) does not exist.

The specified logical-host-name does not exist.

S:

Suspends command processing.

O:

Carefully review the specified logical host name to make sure that it is correct, and then run the data collection tool again.

KAVB8903-E

The host name is not specified in the -h option.

No host name is specified by the -h option.

S:

Suspends command processing.

O:

Specify a valid command option, and then run the data collection tool again.

KAVB8904-E

The shared directory (shared-directory-path) used by the specified logical host (logical-host-name) was not found.

The shared directory (shared-directory-path) used by the specified logical host (logical-host-name) was not found.

S:

Continues command processing.

O:

For active server hosts, install the shared directory, and then run the data collection tool again.

For standby server hosts, no shared directory is installed, so no corrective action is necessary.

KAVB8905-E

The specified directory (data-storage-directory-name) is invalid.

The specified directory (data-storage-directory-name) is invalid.

S:

Suspends command processing.

O:

Specify a valid data storage directory, and then execute the data collection command again.

In Windows, check the following items:

Was a reserved device name (AUX, CON, NUL, PRN, COM1 to COM9, or LPT1 to LPT9) or any of the symbols ,, ;, %, &, ^, or ! used?

Was the specified directory name longer than 128 bytes?

KAVB8906-E

The directory has the same name as an existing file (file-name).

A file (file-name) with the same name as the directory already exists.

S:

Suspends command processing.

O:

Delete the file with the same name, and then run the data collection tool again.

KAVB8907-E

The directory (directory-name) could not be written to.

There is insufficient write permission for the directory (directory-name).

S:

Suspends command processing.

O:

Carefully review the executing user's write permission for the directory, and then run the data collection tool again.

KAVB8908-W

The directory (directory-path) used by the physical host does not exist.

The directory being used by the physical host does not exist.

S:

Continues processing without acquiring data in the directory path.

O:

Determine whether the directory path was temporarily disconnected.

KAVB8909-E

command-name does not exist.

command-name does not exist.

S:

Suspends command processing.

O:

Determine whether the command was deleted. If it does not exist, re-install JP1/IM - Manager.

KAVB8910-E

There is not enough free disk space to execute the command.

There is not enough disk space to execute the command.

S:

Suspends command processing.

O:

Check the amount of available disk space, increase available disk space by deleting unnecessary files, and then run the data collection tool again.

Also delete the data that was acquired before processing was suspended.

KAVB8911-E

There is not enough memory to execute the command.

There is not enough memory to execute the command.

S:

Suspends command processing.

O:

Check the amount of free space in system memory, increase available memory by stopping unnecessary processes, and then run the data collection tool again.

KAVB8912-W

An attempt to acquire the Windows event log (event-log-type) has failed.

An attempt to acquire the Windows event log failed.

Event log type: System or Application

S:

Continues command processing.

O:

Use the event viewer to acquire the Windows event log manually.

KAVB8913-E

The specified file cannot be read (file-name).

The specified file name cannot be read.

S:

Suspends command processing.

O:

Check the read permission for the specified file, and then run the data collection tool again.

KAVB8914-E

The specified file does not exist (file-name).

The specified file does not exist.

S:

Suspends command processing.

O:

Specify an existing file, and then run the data collection tool again.

KAVB8915-E

The specified directory has the same name as an existing file (file-name).

A file (file-name) with the same name as the specified data storage directory already exists.

S:

Suspends command processing.

O:

Either specify a different directory or delete the file with the same name, and then run the data collection tool again.

KAVB8916-E

A write operation cannot be performed for the specified directory (directory-name).

A write operation cannot be performed in the specified data storage directory.

S:

Suspends command processing.

O:

Either specify a different directory or make sure that the executing user has write permission for the directory above the specified directory, and then run the data collection tool again.

KAVB8917-E

An attempt to create the directory (directory-name) has failed.

An attempt to create a directory failed.

S:

Suspends command processing.

O:

Either specify a different directory or make sure that the executing user has write permission for the directory above the specified directory, and then run the data collection tool again.

KAVB8918-I

The data was successfully acquired.

Reports that data was successfully acquired.

S:

Terminates the command.

KAVB8919-E

Some of the data could not be acquired.

Some of the data could not be acquired. This message is output following messages that are output during execution.

S:

Terminates command processing.

O:

Take the corrective action given for the message that was output during execution.

KAVB8920-I

Deletion of the core dump file (dump-file-name) has finished.

Deletion of the core dump file (dump-file-name) is complete.

S:

Continues command processing.

KAVB8921-I

information will be acquired.

Reports that the data of information will be acquired.

S:

Continues command processing.

KAVB8922-I

information has been acquired.

Reports that the data of information was acquired.

S:

Continues command processing.

KAVB8923-W

information could not be acquired.

Reports that the data of information could not be acquired.

S:

Continues command processing.

O:

Refer to jim_log_result.log to see if data exists at the collection source, and then manually acquire the data that could not be acquired.

KAVB8924-I

The directory already exists. (directory-name)

The directory will be re-created.

directory-name already exists. Re-creates the directory.

S:

In Windows: Waits for a user response, then deletes the directory and continues processing.

In UNIX: Continues processing.

O:

In Windows: To continue processing, press any key. To suspend processing, press Ctrl + C.

In UNIX: No corrective action is necessary.

KAVB8925-I

The directory does not exist. (directory-name) The directory will be created.

directory-name does not exist. Creates the directory.

S:

In Windows: Waits for a user response, then creates the directory and continues processing.

In UNIX: Continues processing.

O:

In Windows: To continue processing, press any key. To suspend processing, press Ctrl + C.

In UNIX: No corrective action is necessary.

KAVB8926-I

Data acquisition processing will start.

Starts data acquisition.

S:

Continues command processing.

KAVB8927-I

Execution of the command-name command will start.

Starts executing command-name.

S:

Continues command processing.

KAVB8928-I

command-name execution is ended. (ERRORLEVEL=error-level)

command execution ended.

ERRORLEVEL: Return code of the command

S:

Continues command processing.

KAVB8929-I

information will be acquired. Please wait.

Wait until information is acquired.

S:

Continues command processing.

KAVB8930-E

An attempt to delete the directory (directory-name) has failed.

An attempt to delete the directory failed.

S:

Suspends command processing.

O:

Determine whether the directory is being used by another process. Make sure that it is not being used by another process, or specify another directory, and then run the data collection tool again.

KAVB8931-W

command-name does not exist.

command-name does not exist.

S:

Continues command processing.

O:

Determine whether the command was deleted. If the command does not exist, re-install JP1/IM - Manager.

KAVB8932-E

command-name does not exist.

command-name does not exist.

S:

Suspends command processing.

O:

Determine whether the command was deleted. If the command does not exist, re-install JP1/Base and JP1/IM - Manager.

KAVB8933-E

An attempt to access the registry for (information) has failed. (detailed-information)

An attempt to access the registry for information failed.

detailed-information: The argument passed to the function RegOpenKeyEx/RegEnumKeyEx and the return code.

S:

Suspends command processing.

O:

Contact a system administrator.

KAVB8934-I

The following logical host(s) exist on this machine:

logical-host-name

To acquire information about a logical host, execute "command-name -f output-directory-name -h logical-hostname".

The following logical-host exists on this computer.

Execute command-name -h logical-host-name to collect the logical host information.

S:

Continues command processing.

O:

Execute command-name -h logical-host-name to collect the logical host information.

KAVB8935-I

The following logical host(s) exist on this machine:

logical-host-name

To acquire information about a logical host, execute "command-name -f output-directory-name -h logical-hostname".

The following logical-host exists on this computer.

Execute command-name -h logical-host-name to collect the logical host information.

S:

Continues command processing.

O:

Execute command-name -h logical-host-name to collect the logical host information.

KAVB8936-W

An attempt to create the directory (directory-name) has failed.

An attempt to create directory failed.

S:

Continues command processing.

O:

Make sure that the executing user has write permission for the directory above the specified directory, and then run the data collection tool again.

KAVB8937-W

An attempt to execute command has failed. (arc=detailed-information)

An attempt to execute command failed.

detailed-information: Return code of the command

S:

Continues command processing.

O:

Take the corrective action given for the message that was output preceding this message.

KAVB8938-I

Execution of command was successful.

command was successfully executed.

S:

Continues command processing.

KAVB8939-E

The user does not have execution permission for the command (command-name).

The user does not have permission to execute command.

S:

Suspends command processing.

O:

Check the access permission for the command.

KAVB8940-I

Deletion of the thread dump file has finished.

Deletion of the thread dump file is complete.

S:

Continues command processing.

KAVB8941-I

Do you want to delete all the core dump files below the directory directory-name? [yes/no]

Confirms that you want to delete the core dump files located in the directory indicated by directory-name.

S:

If yes or y is entered, deletes the core dump files and terminates command processing.

If no or n is entered, terminates command processing without deleting the core dump files.

O:

To delete the core dump files, enter yes or y.

To cancel deleting of the core dump files, enter no or n.

KAVB8942-I

Do you want to delete all the thread dump files below the directory directory-name? [yes/no]

Confirms that you want to delete the thread dump files located in the directory indicated by directory-name.

S:

If yes or y is entered, deletes the thread dump files and terminates command processing.

If no or n is entered, terminates command processing without deleting the thread dump files.

O:

To delete the thread dump files, enter yes or y.

To cancel deleting of the thread dump files, enter no or n.

KAVB8943-E

A write operation cannot be performed because a file with the same name (file-name) already exists.

A write operation cannot be performed because a file with the same name already exists.

S:

Continues processing without creating a file.

O:

Check the write permission for the file. If the file is not needed, delete it, and then run the data collection tool again.

KAVB8944-I

file-name already exists. Do you want to overwrite it? [yes/no]

The file already exists. Do you want to overwrite it?

S:

If yes or y is entered, overwrites the file and continues command processing.

If no or n is entered, continues command processing without overwriting the file.

O:

To overwrite the file, enter yes or y.

To cancel overwriting of the file, enter no or n.

KAVB8945-I

Is the device (device-name) ready? [yes/no]

Is the device ready?

S:

If yes or y is entered, acquires data for the device and continues command processing.

If no or n is entered, continues command processing without acquiring data for the device.

O:

To acquire data for the device, enter yes or y.

To cancel acquisition of data for the device, enter no or n.

KAVB8946-I

Do you want to delete all the thread dump files below the directory directory-name? [y/n]

Confirms that you want to delete thread dump files located in the directory indicated by directory-name.

S:

If y is entered, deletes the thread dump files and terminates command processing.

If n is entered, terminates command processing without deleting the thread dump files.

O:

To delete the thread dump files, enter y.

To cancel deleting of the thread dump files, enter n.

KAVB8947-W

An attempt to get the IM Database backup file failed.

An attempt to acquire the IM database backup file failed.

S:

Continues command processing.

O:

Check the following items:

Is the IM database running?

Is sufficient system memory allocated?

Is there sufficient disk space in the destination folder for the IM database backup?

2.10 Messages related to installation and setup (KAVB9001 to KAVB9999)

KAVB9032-E

An attempt to switch the action information file has failed. (code = maintenance-code)

An attempt to move the action information file failed.

S:

Continues installation.

O:

Take corrective action according to the maintenance code.

Maintenance code: 2

Error type: A failure occurred during move processing

Corrective action: Use the data collection tool to collect data, and then contact a system administrator. Inform the administrator of the maintenance code.

Maintenance code: 3

Error type: I/O error

Corrective action: Use the data collection tool to collect data, and then contact a system administrator. Inform the administrator of the maintenance code.

Maintenance code: 4

Error type: Memory error

Corrective action: Stop all applications not in use after installation finishes or after cluster version upgrade finishes. Then re-execute the installation or cluster version upgrade.

KAVB9033-I

The switch of the action information file has finished.

The move of the action information file is complete.

S:

Continues installation.

KAVB9034-E

An attempt to change the permission for the file [file-name] has failed.

An attempt to change permission for a file [file-name] failed.

S:

Suspends setup and installation.

O:

Check the following items:

Is JP1/IM - Manager running?

Is there sufficient disk space and available memory?

After taking corrective action for the above causes, set up and install JP1/IM - Manager again.

KAVB9035-E

An attempt to copy the file [file-name] has failed.

An attempt to copy the file [file-name] failed.

S:

Suspends setup and installation.

O:

Check the following items:

Is JP1/IM - Manager running?

Is there sufficient disk space and available memory?

After taking corrective action for the above causes, set up and install JP1/IM - Manager again.

KAVB9036-E

The file [file-name] does not exist.

The file [file-name] does not exist.

S:

Suspends setup and installation.

O:

Check the following items:

Does the file [file-name] exist?

Is there sufficient disk space and available memory?

After taking corrective action for the above causes, install JP1/IM - Manager again.

KAVB9051-I

The Central Console Service setup will now start.

JP1/IM - Manager setup will start.

S:

Starts JP1/IM - Manager setup.

KAVB9053-I

The file [file-name] was relocated.

The definition file [file-name] was moved.

S:

Moves the definition file [file-name].

KAVB9054-E

'/opt/jp1base/bin/jbssetcnf' could not be executed.

The /opt/jp1base/bin/jbssetcnf command could not be executed.

S:

Suspends setup.

O:

Determine whether you can execute the /opt/jp1base/bin/jbssetcnf command.

If the file does not exist, re-install JP1/Base, and then set it up again.

Make sure that you can execute the /opt/jp1base/bin/jbssetcnf command, and then set up JP1/IM - Manager again.

KAVB9056-I

[file-name] was registered to the common definition.

[file-name] was registered as a common definition.

S:

Registers [file-name] as a common definition.

KAVB9057-E

[file-name] could not be registered to the common definition.

[file-name] could not be registered as a common definition.

S:

Suspends setup.

O:

Check the contents of [file-name], and then set up JP1/IM - Manager again.

If there are no errors in [file-name], re-install JP1/Base, and then set it up again.

KAVB9059-I

The registration of the common definition data has completed.

Registration of the common definition information is complete.

KAVB9064-I

The Central Console Service setup has completed.

Setup of JP1/IM - Manager is complete.

S:

Completes setup of JP1/IM - Manager.

KAVB9072-I

The Central Console Service Cluster environment setup will now start.

Setup of the JP1/IM - Manager cluster environment will start.

S:

Starts setup of the JP1/IM - Manager cluster environment.

KAVB9073-I

The logical host setup processing will now start.

Setup processing for the logical host will start.

S:

Starts setup processing for the logical host.

KAVB9074-E

An attempt to get the configuration data of the physical host failed.

An attempt to acquire the common definition information of the physical host failed.

S:

Suspends cluster setup.

O:

Make sure that the shared disk can be accessed.

Make sure that the jbsgetcnf command can be executed.

If the file does not exist, re-install JP1/Base, and then set it up again.

Make sure that you can execute the jbsgetcnf command, and then perform cluster setup of JP1/IM - Manager again.

KAVB9075-E

The configuration data could not be registered.

The configuration data could not be registered.

S:

Suspends setup.

O:

Make sure that the jbssetcnf command can be executed.

If the file does not exist, re-install JP1/Base, and then set it up again.

Make sure that you can execute the jbssetcnf command, and then perform cluster setup of JP1/IM - Manager again.

KAVB9076-I

The configuration files of the physical host will now be copied to the shared disk.

Copies the definition files of the physical host to the shared disk.

KAVB9077-E

The folder [shared-disk]/jp1cons/conf could not be created on the shared disk.

A folder could not be created on the shared disk.

S:

Suspends cluster setup.

O:

Make sure that the shared disk can be accessed.

Confirm that the shared disk can be accessed, and then perform cluster setup of JP1/IM - Manager again.

KAVB9078-I

The IP address will now be bound to the TCP/IP socket.

Binds the IP address to the TCP/IP socket.

S:

Binds the IP address to the TCP/IP socket.

KAVB9079-I

The acquisition of the shared disk name will now start.

Processing to acquire the shared disk name will start.

S:

Starts processing to acquire the shared disk name.

KAVB9080-E

An attempt to get the [logical-host] configuration data failed.

An attempt to acquire common definition information failed.

S:

Suspends cluster setup.

O:

Make sure that the shared disk can be accessed.

Make sure that the jbsgetcnf command can be executed.

If the file does not exist, re-install JP1/Base, and then set it up again.

Make sure that you can execute the jbsgetcnf command, and then perform cluster setup of JP1/IM - Manager again.

KAVB9101-I

The upgrading of the logical host environment will now start.

Upgrading of the logical host environment version will start.

S:

Starts upgrading the logical host environment version.

KAVB9102-I

The upgrading of the logical host environment has finished.

Upgrading of the logical host environment version is complete.

S:

Terminates processing.

KAVB9103-E

A specified argument is invalid.

A specified argument is invalid.

S:

Aborts processing.

O:

Specify a valid argument, and then retry the operation.

KAVB9104-E

A specified logical host name is invalid.

The specified logical host name is invalid.

S:

Aborts processing.

O:

Specify a valid logical host name, and then retry the operation.

KAVB9105-E

An attempt to upgrade the logical host environment has failed.

An attempt to upgrade the logical host environment version failed.

S:

Aborts processing.

O:

Take the corrective action given for the message that was output preceding this message.

KAVB9106-E

The file "file-name" could not be copied.

An attempt to copy a file (including folders and directories) failed.

S:

Aborts processing.

O:

Check the following items, and then retry the operation.

Is JP1/IM - Manager running?

Can the shared disk be accessed?

Does the user have write permission for the shared disk?

Is another application using JP1/IM - Manager files?

Is there sufficient disk space and available memory?

Was the operation executed with Administrator permissions (in Windows) or superuser permission (in UNIX)?

KAVB9107-E

The file "file-name" could not be created.

An attempt to create a file (including folders and directories) failed.

S:

Aborts processing.

O:

Check the following items, and then retry the operation.

Is JP1/IM - Manager running?

Can the shared disk be accessed?

Does the user have write permission for the shared disk?

Is another application using JP1/IM - Manager files?

Is there sufficient disk space and available memory?

Was the operation executed with Administrator permissions (in Windows) or superuser permission (in UNIX)?

KAVB9108-E

The configuration definition "common-definition-file-name" could not be registered. (detail-code)

An attempt to save common definitions failed for the following reason.

If detail-code is 900012000, the common definition file could not be read.

If detail-code is 900012002, the jbssetcnf command could not be executed.

S:

Aborts processing.

O:

Check the following items, and then retry the operation.

Is JP1/IM - Manager running?

Can the shared disk be accessed?

Does the user have write permission for the shared disk?

Is another application using JP1/IM - Manager files?

Is there sufficient disk space and available memory?

Was the operation executed with Administrator permissions (in Windows) or superuser permission (in UNIX)?

KAVB9109-E

The system environment could not be set. (detail-code)

An attempt to set up the system environment failed for the following reason.

If detail-code is 900011000, the configuration file (Windows: console-path\conf\jp1co_spmd.conf; UNIX: /etc/opt/jp1cons/conf/jp1co_spmd.conf) could not be read.

If detail-code is 900011001, there was an error in the options specified for the configuration file (Windows: console-path\conf\jp1co_spmd.conf; UNIX: /etc/opt/jp1cons/conf/jp1co_spmd.conf).

If detail-code is 900011002, the jcoimdef command could not be executed.

S:

Aborts processing.

O:

If detail-code is 900011000 or 900011002, check the following items, and then retry the operation.

Is JP1/IM - Manager running?

Can the shared disk be accessed?

Does the user have write permission for the shared disk?

Is another application using JP1/IM - Manager files?

Is there sufficient disk space and available memory?

Was the operation executed with Administrator permissions (in Windows) or superuser permission (in UNIX)?

If detail-code is 900011001, check the options of the configuration file (Windows: console-path\conf\jp1co_spmd.conf; UNIX: /etc/opt/jp1cons/conf/jp1co_spmd.conf), and then retry the operation.

KAVB9110-E

Insufficient memory has occurred.

There is insufficient memory.

S:

Aborts processing.

O:

Increase available memory by stopping other applications, and then retry the operation.

KAVB9111-E

An attempt to restore the logical host environment has failed.

An attempt to restore the original logical host environment after processing was suspended due to an error failed.

S:

Aborts processing.

O:

In Windows:

Confirm that the backup file is in the shared-folder\jp1cons\tmp\conf\ folder, and then perform the following operations.

1. Delete shared-folder\jp1cons\conf\ from each folder.

2. Move shared-folder\jp1cons\tmp\conf\ to shared-folder\jp1cons\conf\.

3. Remove the causes of other errors that occurred at the same time, and then retry the operation.

In UNIX:

Confirm that shared-directory/jp1cons/tmp/conf/ is in the backup file, and then perform the following operations.

1. Delete shared-directory/jp1cons/conf/ from each directory.

2. Move shared-directory/jp1cons/tmp/conf/ to shared-directory/jp1cons/conf/.

3. Remove the causes of other errors that occurred at the same time, and then retry the operation.

KAVB9112-E

Only one jp1cohaverup command can be executed at one time. Alternatively, a backup file remains from the last execution time.

A cluster environment move command is being executed. Another possibility is that the previous execution of a cluster environment move command was suspended, so a backup file still exists.

S:

Aborts processing.

O:

Multiple cluster environment move commands cannot be executed simultaneously. If a cluster environment move command is being executed, wait for processing to finish, and then retry the operation.

If the previous backup file still exists, perform the following operations, and then retry the operation.

In Windows:

1. Delete shared-folder\jp1cons\conf\ from each folder.

2. Move shared-folder\jp1cons\tmp\conf\ to shared-folder\jp1cons\conf\.

In UNIX:

1. Delete shared-directory/jp1cons/conf/ from each directory.

2. Move shared-directory/jp1cons/tmp/conf/ to shared-directory/jp1cons/conf/.

KAVB9113-E

Failed to acquire information about the host that was specified by the common definition information [key-value].

An attempt to acquire information about the host specified by the common definition information (key-value) failed.

The following items are displayed as key-value.

\\JP1DEFAULT\CONSOLE_MANAGER\CONF_DIR

\\host-name\CONSOLE_MANAGER\CONF_DIR

\\host-name\CONSOLE_MANAGER\JP1CONS_WORK PATH

\\host-name\CONSOLE_MANAGER\JP1CONS_LOGDIR

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB9114-E

Failed to acquire the installation path from the registry [product-name].

An attempt to acquire an installation path from the registry failed.

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAVB9115-E

No permission for execution.

The user does not have permission to execute the command.

S:

Aborts processing.

O:

Log in again as a user with Administrator or similar execution permissions, and then retry the operation.

KAVB9116-W

Failed to delete the temporary file created during processing. (file-name)

A temporary file created for move processing could not be deleted.

S:

Continues processing.

O:

Delete the indicated file.

KAVB9117-I

An attempt to restore the logical host environment will now start.

Environment recovery processing will start.

S:

Starts environment recovery processing.

KAVB9118-I

An attempt to restore the logical host environment has finished.

Environment recovery processing is complete.

S:

Terminates environment recovery processing.

KAVB9119-E

An attempt to switch the extended startup process definition file has failed. (code = code)

An attempt to move the extended startup process definition file failed.

S:

Continues processing.

O:

Check the maintenance code, and then retry the overwrite installation.

KAVB9120-E

An attempt to switch the extended startup process definition file has failed. Installation will continue using the pre-installation settings file. Please re-install product-name, using an overwrite installation. (code = maintenance-code)

An attempt to create an extended startup process definition file failed. Restore the original file, and then continue processing.

S:

An attempt to create a file failed. Restores the existing file and continues processing.

O:

Make sure that the attribute of the extended startup process definition file is not a read attribute, and then re-install the product.

KAVB9121-I

The switch of the extended startup process definition file has finished.

The move of the extended startup process definition file is complete.

S:

Terminates processing.

KAVB9201-I

The service dependencies were successfully changed.

The service dependencies were successfully changed.

S:

Terminates command processing.

KAVB9202-E

An attempt to change the service dependencies has failed. (details = detailed-information)

An attempt to change the service dependencies failed.

S:

Terminates command processing.

O:

Check the following items according to the detailed information that is displayed:

detailed-information: You do not have the required execution permissions.

Corrective action: Execute the command again as a user with Administrator permissions.

detailed-information: The service does not exist.

Corrective action: The JP1/IM - Manager service is not registered. Make sure that the JP1/IM - Manager service is registered, and then retry the operation.

If the JP1/IM - Manager service is not registered, re-install JP1/IM - Manager.

detailed-information: Other

Corrective action: Use the data collection tool to collect data, and then provide the detailed information to a system administrator.

KAVB9251-E

The evaluation version can be used only as a new installation, or as an overwrite installation of the evaluation version of the same software version.

Installation of the evaluation version failed. The evaluation version can be installed only as a new installation, or as an overwrite installation of the evaluation version of the same software version.

S:

Suspends processing.

O:

Uninstall the previously installed product, and then try installing the evaluation version again.

KAVB9252-E

The release version cannot be installed because either the trial version or a different software version of the evaluation version is installed.

Installation of the release version failed. The release version can be installed only as a new installation, an overwrite installation of the release version, or as an overwrite installation of the evaluation version of the same software version.

S:

Suspends processing.

O:

Uninstall the previously installed product, and then try installing the release version again.

KAVB9255-E

The product cannot be installed because an instance of product-name for which the software model name is different is already installed.

The product cannot be installed because an instance of product-name that has a different model name is already installed.

S:

Suspends processing.

O:

Determine the model names of the installed product and the product for which an overwrite installation is to be performed.

If the installed product is supported for the OS environment you are using, choose to perform an overwrite installation of the product, and re-install it. If the installed product is not supported for the OS environment you are using, uninstall the installed product, and then try installing the product again.

KAVB9256-E

The product cannot be installed because the currently installed version of the product does not support downgrade installations.

Installation failed, because an attempt was made to install an earlier version of the product.

S:

Suspends processing.

O:

Uninstall the already installed product, and then try installing the earlier version again.

KAVB9301-E

The product information could not be acquired because there was not enough memory. (Detailed information: function-name, return-value)

An attempt to acquire product information failed due to insufficient resources.

S:

Suspends processing.

O:

Make sure that there are sufficient system resources.

Resolve the resource insufficiency, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB9302-E

The product information could not be acquired because the environment is invalid. (Detailed information: function-name, return-value)

An attempt to acquire product information failed because the environment is invalid.

S:

Suspends processing.

O:

Determine whether a system error has occurred.

Uninstall the product, re-install it, and then retry the operation.

If the error cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB9901-W

This platform is unsupported. Do you want to cancel installation?

Confirms that you want to suspend processing.

S:

When Yes is clicked, the system suspends processing. When No is clicked, the system continues processing.

O:

Install the item in a supported OS.

KAVB9902-E

This platform is unsupported. Installation will now be cancelled.

This platform is not supported.

S:

Suspends processing.

O:

Install the item in a supported OS.

KAVB9903-E

The login account does not have the permissions necessary for installation. Please log in as a user with administrator permissions.

The account that is logged in does not have necessary permission for installation.

S:

Suspends processing.

O:

Log in as a user with Administrator permissions, and then re-install the item.

KAVB9906-W

The specified installation path is invalid. Please specify a fixed disk.

The specified installation destination is invalid.

S:

Continues processing.

O:

A fixed disk must be specified as the installation destination drive. Check the specified path, and specify a valid installation path.

KAVB9907-E

An attempt to uninstall product-name version has failed.

An attempt to uninstall product-name version failed.

S:

Suspends processing.

O:

Take the corrective action given in the recovery procedures for move operations.

KAVB9908-E

An attempt to stop the service has failed.

An attempt to stop the service failed.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9910-E

An attempt to copy a file has failed.

An attempt to copy a file failed.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9912-E

An attempt to open a file has failed.

Unopened file: file-name

An attempt to open a file failed.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9913-E

An attempt to access a file has failed.

Inaccessible file: file-name

A file could not be accessed.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9914-E

Installation will now be cancelled because information necessary for the installation is insufficient.

There is not enough information for installation.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9915-E

Information could not be written to the registry.

Information could not be specified in the registry.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9916-W

An attempt to register a service into the Services file has failed.

Unregistered service: service-name port-number/protocol

An attempt to register a service in the services file failed.

S:

Continues processing.

O:

After installation is complete, register the service indicated in the message in the services file.

KAVB9917-W

An attempt to register the PATH environment variable has failed.

Unregistered path: path-name

An attempt to configure the Path environment variable failed.

S:

Continues processing.

O:

After installation is complete, specify the value indicated in the message in the Path environment variable.

KAVB9918-W

An attempt to acquire a logical host name has failed. Please make sure the (JP1Console_'logical host name') service of the logical host has stopped, and then continue the installation. Do you want to continue?

An attempt to acquire the configured logical host name failed.

S:

When Yes is clicked, the system continues processing.

When No is clicked, the system suspends processing.

O:

If the logical host service (JP1Console_logical-host-name) is running, stop the service, and then continue processing.

KAVB9919-E

The installation will stop because the (service-name) service is running.

Processing was suspended because the (service-name) service is running.

S:

Suspends processing.

O:

Stop the service indicated by service-name, and the perform the installation again.

KAVB9920-E

An attempt to move to product-name version failed because the common definition could not be registered.

An attempt to move product-name version failed because an attempt to register common definition information failed.

S:

Suspends processing.

O:

Take the corrective action given in the recovery procedures for move operations.

KAVB9925-E

A file necessary for installation was not found.

A file required for installation was not found.

S:

Suspends processing.

O:

Collect data, and then contact a system administrator.

KAVB9926-E

JP1/Integrated Manager - Central Console has been uninstalled.

Uninstall JP1/Integrated Manager - Central Scope, and then re-install JP1/Integrated Management - Central Console.

JP1/Integrated Manager - Central Console has been uninstalled.

S:

Suspends processing.

O:

Uninstall JP1/Integrated Manager - Central Scope, and then install it again.

KAVB9927-E

An attempt to register a service has failed.

An attempt to register a service failed.

S:

Suspends processing.

O:

Restart the computer, and then install again.

KAVB9928-E

An attempt to create a file has failed.

An attempt to create a file failed.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9929-E

An attempt to acquire common definition information has failed.

An attempt to acquire common definition information failed.

S:

Suspends processing.

O:

Stop unnecessary services, and then install again.

KAVB9933-W

An attempt to delete a port has failed.

Service for the undeleted port: service-name

An attempt to delete a port failed.

S:

Continues processing.

O:

After installation is complete, delete the service indicated in the message from the SERVICES file.

KAVB9934-W

An attempt to delete a path in the PATH environment variable has failed. Undeleted path: path-name

An attempt to delete the Path environment variable failed.

S:

Continues processing.

O:

After installation is complete, delete the value indicated in the message from the Path environment variable.

KAVB9935-E

The installation path specified for product-name version cannot be used because it is not on a fixed disk.

The installation destination for product-name version is not a fixed disk.

S:

Suspends processing.

O:

Make sure that the product indicated by product-name is installed correctly.

KAVB9936-E

An attempt to register the common definition information has failed.

An attempt to register common definition information failed.

S:

Suspends processing.

O:

Make sure that JP1/Base is installed correctly.

KAVB9937-W

There is not enough free space on the disk specified as the installation destination. Specify another disk.

There is not enough free space on the disk specified as the installation destination.

S:

Continues processing.

O:

Specify a drive that has sufficient free space.

KAVB9938-E

A prerequisite version of JP1/Base is not installed. The installation will now stop.

A prerequisite version of JP1/Base is not installed.

S:

Suspends processing.

O:

Install the prerequisite version of JP1/Base.

KAVB9939-E

An attempt to change the display name of a service has failed. (Service that failed to be changed: service-name)

An attempt to change the service display name failed.

S:

Suspends processing.

O:

Stop the service indicated by service-name, and then install again.

KAVB9940-E

Unsetup has not been performed for the IM database service on the physical host.

The IM database service has not been unset up.

S:

Suspends processing.

O:

Execute the jcodbunsetup and jcfdbunsetup commands to unset up the IM database service, and then uninstall it again.

KAVB9941-E

Unsetup has not been performed for the IM database service on the logical host. (Logical host name: logical-host-name)

The IM database service of the logical host has not been unset up.

S:

Suspends processing.

O:

Execute the jcodbunsetup and jcfdbunsetup commands to unset up the IM database service of the logical host, and then uninstall it again.

KAVB9942-Q

To enable the communications encryption function, use the same version of JP1/IM - Manager and JP1/Base. If you want to use the communications encryption function in disabled state, continue the installation. Do you want to continue the installation?

Confirm whether you want to do so because communication encryption is not available with the system configuration of the installation destination.

S:

Waits for a response.

O:

InWindows :

To continue the installation, click the Yes button.

To suspend the installation, click the No button.

In UNIX :

To continue the installation, enter y.

To suspend the installation, enter n.

KAVB9943-E

Failed to obtain information about the JP1/Base. The installation will now stop.

Failed to obtain information about the JP1/Base.The installation will now stop.

S:

Suspends installation.

O:

In a new installation:

Make sure that a prerequisite version of JP1/Base is installed correctly. If JP1/Base is installed correctly, contact a system administrator.

In an overwrite installation or upgrade installation:

Make sure that a prerequisite version of JP1/Base is installed correctly. If JP1/Base is installed correctly, use the data collection tool to collect data, and then contact a system administrator.

KAVB9950-E

An attempt to install the Hitachi trace library has failed.

After the JP1/IM-View installer finishes, please re-install JP1/IM-View.

An attempt to install the Hitachi trace library failed.

S:

Suspends processing.

O:

Wait until installation processing finishes, and then re-install JP1/IM - View.

KAVB9951-E

An attempt to save the definition file storage folder has failed.

An attempt to save the definition file storage folder failed.

S:

Suspends processing.

O:

Stop any unnecessary services, and then perform the installation again.

KAVB9952-E

An attempt to save the image file of the integrated function menu has failed.

An attempt to save the image file of the integrated function menu failed.

S:

Suspends processing.

O:

Stop any unnecessary services, and then perform the installation again.

KAVB9953-E

An attempt to restore the definition file storage folder has failed.

An attempt to restore the definition file storage folder failed.

S:

Suspends processing.

O:

Take the corrective action given in the recovery procedures for move operations.

KAVB9954-E

An attempt to restore the image file of the integrated function menu has failed.

An attempt to restore the image file of the integrated function menu failed.

S:

Suspends processing.

O:

Take the corrective action given in the recovery procedures for move operations.

KAVB9955-E

Information could not be acquired from the registry.

Information could not be acquired from the registry.

S:

Suspends processing.

O:

Stop any unnecessary applications, and then perform the installation again.

KAVB9956-E

An attempt to add an access permission has failed.

An attempt to add an access permission failed.

S:

Suspends processing.

O:

Stop any unnecessary applications, and then perform the installation again.

KAVB9957-E

An attempt to delete JRE has failed. (directory = Console-path or View-path\bin\jre)

An attempt to delete a file or directory of JRE failed because a program of JP1/IM - Central Console or JP1/IM - View is running and the JRE files and directories could not be accessed.

S:

Cancels processing.

O:

Perform the following procedures:

(1) Stop any program products that are running.

(a) If the message is output to the directory View-path\bin\jre:

Stop JP1/IM - View.

(b) If the message is output to the directory Console-path\bin\jre:

Stop all instances of JP1/IM - View that are connected to JP1/IM - Central Console, and then stop any instances of JP1/IM - Central Console running on the physical host or a logical host.

(2) Reinstall the product you have been attempting to install.

KAVB9958-W

An attempt to register common definition information has failed. (file name = file-name)

An attempt to register common definition information failed.

S:

Continues processing.

O:

After installation is complete, execute the following command:

jbssetcnf.exe file-name

KAVB9959-E

The login account does not have the permissions necessary for installation or uninstallation. Please log in as a user with administrator permissions.

The account that is logged in does not have permissions required to install or uninstall.

S:

Suspends processing.

O:

Log in as an administrator to install or uninstall.

KAVB9990-E

Memory is insufficient. Please stop any unnecessary applications, and then execute installation again.

There is insufficient memory.

S:

Suspends processing.

O:

Stop any unnecessary applications, and then perform the installation again.

KAVB9991-E

An internal error has occurred. Acquire the relevant data, and then contact the system administrator.

An internal error occurred.

S:

Suspends processing.

O:

Collect data, and then contact a system administrator.

KAVB9998-E

An error might exist in the operation. Please install by using HCD_INST.EXE.

An error might have occurred during the operation.

S:

Suspends processing.

O:

Execute HCD_INST.EXE to install.

KAVB9999-E

Code 9999

The media might be defective. Please contact the seller.

The media might be defective.

S:

Suspends processing.

O:

Contact the vendor.

2.11 Messages related to event generation function (KAJV2001 to KAJV3999)

KAJV2002-E

A value set for common definition information (common-definition) is outside the valid range. The default value (default-value) will be used. (valid range = minimum-value to maximum-value)

A value outside the valid range was specified in the common definition information indicated in the message.

S:

Continues processing using the default value indicated in the message.

O:

Specify a common definition information value within the indicated range.

KAJV2003-E

A value (setting) set for common definition information (common-definition) is invalid. The default value (default-value) will be used.

The value of the common definition information indicated in the message is invalid.

S:

Continues processing using the default value indicated in the message.

O:

Correct the common definition information value.

KAJV2004-E

An attempt to read common definition information (common-definition) failed. The default value (default-value) will be used. (reason = reason)

An attempt to read the common definition information indicated in the message failed.

S:

Continues processing using the default value indicated in the message.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2006-E

A value set for common definition information (common-definition) is outside the valid range. The value (value-before-reload) from before the reload will be used. (valid range = minimum-value to maximum-value)

A value outside the valid range was specified in the common definition information indicated in the message.

S:

Continues processing using the value specified prior to the reload, which is indicated in the message.

O:

Specify a value for common definition information within the indicated range.

KAJV2007-E

A value (setting) set for common definition information (common-definition) is invalid. The value (value-before-reload) from before the reload will be used.

The value specified in the common definition information indicated in the message is invalid.

S:

Continues processing using the value specified prior to the reload, which is indicated in the message.

O:

Correct the common definition information value.

KAJV2008-E

An attempt to read common definition information (common-definition) failed. The value (value-before-reload) from before the reload will be used. (reason = reason)

An attempt to read the common definition information indicated in the message failed.

S:

Continues processing using the value specified prior to the reload, which is indicated in the message.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2010-E

Common definition information (common-definition) required for the correlation event generation service has not been set.

Common definition information required to start event generation function was not specified.

S:

Stops event generation function.

O:

Perform an overwrite installation of JP1/IM - Manager.

KAJV2011-E

Common definition information (common-definition) required for the correlation event generation function has not been set.

Common definition information required to start the correlation event generation function of Event Base Service was not specified.

S:

Stops the correlation event generation function of Event Base Service.

O:

Perform an overwrite installation of JP1/IM - Manager.

KAJV2016-W

The number of common exclusion condition groups (extended) exceeds the limit. (maximum number of condition groups = maximum-number)

The number of common exclusion-condition groups defined in JP1/IM - Manager exceeds the maximum.

S:

Continues processing with the predefined number of condition groups.

O:

Increase the maximum number of common exclusion-condition groups in extended mode, or delete unnecessary condition groups.

KAJV2017-W

The size of a common exclusion condition group (extended) filter exceeds the limit. (condition group maximum size = maximum-size)

The filter size for the common exclusion-condition group defined in JP1/IM - Manager exceeds the maximum size.

S:

Continue processing using the predefined filter size.

O:

Define the condition group so that the filter size does not exceed the maximum size.

KAJV2020-E

The setting for the language code is invalid. English will be assumed, and processing will continue. (set language code = language-code)

A language code not supported by JP1/IM - Manager was specified as LANG in the environment variable file (jp1co_env.conf).

S:

Assumes that the language code is English and continues processing.

O:

Carefully review the LANG setting in the environment variable file (jp1co_env.conf).

KAJV2021-I

A JP1 event (event-ID) could not be issued. (reason = reason)

The JP1 event with the indicated event ID could not be generated.

S:

Cancels event generation.

O:

Determine whether Event Service is running. If it is not running, start it.

If Event Service is running, use the data collection tool to collect data, and then contact a system administrator.

KAJV2101-I

The correlation event generation service has started.

Event generation function started.

S:

Continues processing.

KAJV2102-I

The correlation event generation service has stopped.

Event generation function stopped.

S:

Continues processing.

KAJV2103-E

The correlation event generation service has terminated abnormally.

Event generation function stopped abnormally.

S:

Terminates event generation function abnormally.

O:

Check the integrated trace log or common message log, and take the corrective action given for the message that was output preceding this message.

KAJV2104-I

A termination request was received from process management.

A stop request was received from process management.

S:

Performs stop processing for event generation function.

KAJV2105-I

A reload request was received from process management.

A reload request was received from process management.

S:

Performs reload processing for event generation function.

KAJV2106-E

An invalid request was received from process management. (request code = request-code)

An invalid request was received from process management.

S:

Ignores the invalid request and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2107-E

An attempt to communicate with process management has failed. (reason = reason)

An attempt to communicate with process management of JP1/IM - Manager failed.

S:

Stops event generation function.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2108-I

Reload processing has finished.

Reload processing is complete.

S:

Continues processing.

KAJV2109-E

The log output function could not be initialized. Data cannot be output to the integrated trace log and by-process trace log. (reason = reason)

If not using the integrated monitoring database:

The log output function could not be initialized when event generation function started.

If using the integrated monitoring database:

The log output function of the correlation event generation function could not be initialized when the correlation event generation function of Event Base Service started.

S:

Outputs only the common message log and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2110-I

The correlation event generation function has started.

The correlation event generation function of Event Base Service started.

S:

Continues processing.

KAJV2111-I

The correlation event generation function has stopped.

The correlation event generation function of Event Base Service stopped.

S:

Continues processing.

KAJV2112-E

The correlation event generation function has terminated abnormally.

The correlation event generation function of Event Base Service stopped abnormally.

S:

Stops the correlation event generation function of Event Base Service abnormally.

O:

Check the integrated trace log or common message log, and take the corrective action given for the message that was output preceding this message.

KAJV2151-E

An attempt to obtain the port number has failed. The default port number (20383) will be used. (reason = reason)

The port number used by event generation function could not be acquired.

S:

Continues processing using the default port number.

O:

Determine whether service name jp1imegs is defined in the services file. If service name jp1imegs is not defined, define it. The default port number is 20383. If jp1imegs is defined, make sure that the services file can be read. If it can be read, use the data collection tool to collect data, and then contact a system administrator.

KAJV2152-E

An attempt to initialize communication processing has failed. (reason = reason)

An attempt to initialize communication processing with event generation function failed.

S:

Stops event generation function.

O:

Network settings may be incorrect.

Check the integrated trace log or common message log, and take the corrective action given for the message that was output preceding this message.

If network settings are correct, use the data collection tool to collect data, and then contact a system administrator.

KAJV2153-E

An error occurred while communicating with a command. (reason = reason)

An error occurred while communicating with a command.

S:

Continues processing.

O:

If the error was a communication error, determine whether the command was forcibly terminated while being executed.

If the command was not forcibly terminated, use the data collection tool to collect data, and then contact a system administrator.

KAJV2154-E

Communication processing timed out because the command (command) did not respond. (timeout time = timeout-time)

Communication processing timed out because there was no response from the command displayed in the message to a request for processing by event generation function.

S:

Event generation function ends the connection to the command, and the system continues processing.

O:

Determine whether the manager host is in high load status.

If it is not in high load status, use the data collection tool to collect data, and then contact a system administrator.

KAJV2155-E

The data sent from the command (command) is invalid. The sent data will be ignored.

The data sent from the indicated command is invalid.

S:

Event generation function ignores data sent from the command, and the system continues processing.

O:

Determine whether the indicated command was suspended during execution.

If it was not suspended, use the data collection tool to collect data, and then contact a system administrator.

KAJV2156-E

An attempt to initialize communication processing for the correlation event generation service has failed. (IP address = IP-address, port number = port-number, reason = reason)

An attempt to initialize communication processing for event generation function failed.

S:

When multiple LANs are set up, the system ignores the IP address that generated the error and continues processing.

When there is a single LAN, the system terminates event generation function.

O:

Make sure that the port number of the service name jp1imegs defined in the services file is not being used by another service.

If the port number is duplicated, specify a unique port number.

Also check the OS settings and log to make sure that the network is available.

If the cause is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAJV2157-E

The port number of the service-name service could not be acquired. The default port number port-number will be used now.

The port number could not be acquired.

S:

Continues processing using the default port number.

O:

Make sure that the port number of the service name that could not be acquired is not being used by another service.

If the port number is duplicated, specify a unique port number.

Also check the OS settings and log to make sure that the network is available.

If the cause is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAJV2161-I

A connection with the event service has been established.

A connection with Event Service was established.

S:

Continues processing.

KAJV2162-I

The connection with the event service has been canceled.

The connection with Event Service was canceled.

S:

Continues processing.

KAJV2163-E

An attempt to establish a connection with the event service has failed. Another attempt to connect will now be performed. (reason = reason)

An attempt to connect to Event Service failed.

S:

Retries to establish a connection with Event Service.

O:

Make sure that Event Service is running.

If it is running, make sure that Event Service settings are valid.

If the settings are valid, use the data collection tool to collect data, and then contact a system administrator.

KAJV2164-E

An error occurred while connected with the event service. Processing cannot continue. (reason = reason)

Processing could not continue because an error occurred while connected to Event Service.

S:

Stops event generation function.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2165-E

An error occurred while communicating with the event service. The system will try to communicate again. (reason = reason)

An error occurred during communication with Event Service.

S:

Retries to communicate with Event Service.

O:

Make sure that Event Service is running.

If it is running, make sure that Event Service settings are valid.

If the settings are valid, use the data collection tool to collect data, and then contact a system administrator.

KAJV2166-E

An error occurred while connected with the event service. Processing cannot continue. (reason = reason)

Processing could not continue because an error occurred during communication with Event Service.

S:

Stops event generation function.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2167-E

An attempt to update the event acquisition filter has failed. (reason = reason)

An attempt to update the event acquisition filter failed.

S:

Continues processing using the filter in use prior to the update.

O:

If the failure was caused by a temporary error that occurred during communication with Event Service, the error occurred in communications with JP1/Base Event Service. Check the integrated trace log to see if there is a problem in Event Service.

If the failure was caused by insufficient memory, allocate sufficient memory.

KAJV2168-E

An attempt to update the event acquisition filter failed because a system error occurred. (reason = reason)

An attempt to update the event acquisition filter failed due to a system error.

S:

Continues processing using the filter in use prior to the update.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2169-E

The received JP1 event could not be stored in memory. (serial number in the event database for the received JP1 event = serial-number-in-event-database)

The received JP1 event could not be stored in memory.

S:

Skips the JP1 event that could not be stored and continues processing.

O:

Determine whether there is sufficient memory. If memory is insufficient, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2170-E

The definition file for the event acquisition filter was not found.

The definition file for the event acquisition conditions was not found.

S:

If the error occurs during switching of the event acquisition filter, the system continues processing using the event acquisition filter prior to switching.

If event generation function is running, the system continues processing with no definition specified for the event acquisition filter.

O:

Specify the event acquisition conditions again in the System Environment Settings window of JP1/IM - View.

KAJV2171-E

An attempt to read the definition file for the event acquisition filter has failed. (reason = reason)

An attempt to read the definition file for the event acquisition conditions failed.

S:

If the error occurs during switching of the event acquisition filter, the system continues processing using the event acquisition filter prior to switching.

If event generation function is running, the system continues processing with no definition specified for the event acquisition filter.

O:

When A file I/O error occurred. is displayed, check the OS log and make sure that resources have not become insufficient.

If resources are sufficient, use the data collection tool to collect data, and then contact a system administrator.

KAJV2172-E

The correlation event generation service will continue processing, using the setting to acquire all JP1 events.

An attempt to specify a definition for the event acquisition filter failed.

S:

Continues processing with no definition specified for the event acquisition filter.

O:

Take the corrective action given for the message that was output preceding this message.

KAJV2173-E

The correlation event generation service will continue processing using the event acquisition filter from before the change.

An attempt to switch the event acquisition filter failed.

S:

Continues processing using the event acquisition filter prior to switching.

O:

Take the corrective action given for the message that was output preceding this message.

KAJV2174-E

A system error occurred while reading the definition file for the event acquisition filter. (reason = reason)

An attempt to specify or switch the event acquisition filter failed because the definition file for the event acquisition conditions is invalid.

S:

If the error occurs during switching of the event acquisition filter, the system continues processing using the event acquisition filter prior to switching.

If event generation function is running, the system continues processing with no definition specified for the event acquisition filter.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2175-I

The correlation event generation service will acquire all JP1 events, because the event acquisition filter (for compatibility) is set.

Event generation function will acquire all JP1 events because the event acquisition filter (for compatibility) was specified.

S:

Continues processing.

KAJV2176-E

A system error occurred while reading to the definition file for the event acquisition filter. (reason = reason)

An attempt to read the definition file for the event acquisition conditions failed due to a system error.

S:

Continues processing with no definition specified for the event acquisition filter.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2177-E

Connection to the event service is not possible because the permission was not set.

A connection could not be established to Event Service because the required permissions were not specified.

S:

If the error occurs when event generation function is running, the system stops event generation function because no event can be acquired.

O:

Specify * or SYSTEM (in Windows) or root (in UNIX) as the users parameter in the JP1/Base event server setting file, and then restart JP1/Base and JP1/IM - Manager.

KAJV2178-E

Connection to the event service is not possible because the permission was not set.

A connection could not be established to Event Service because the required permissions were not specified. An attempt to switch the event acquisition filter failed.

S:

If the error occurs during switching of the event acquisition filter, the system continues processing using the event acquisition filter prior to switching.

O:

Specify * or SYSTEM (in Windows) or root (in UNIX) as the users parameter in the JP1/Base event server setting file, and then restart JP1/Base and JP1/IM - Manager.

KAJV2179-I

The event acquisition filter definition file was read. The read definitions will be used for processing from the next received event. (filter name = filter-name, last received event = arrival-time, serial number in event DB = serial-number-in-event-database)

The event acquisition condition definition file was read using the jcochfilter command or an operation from JP1/IM - View. Event acquisition processing is performed using the definitions that were read, starting with the event after the one indicated by the serial number in the event database that is displayed. If event generation function has not received an event, two hyphens (--) are displayed for the arrival time and serial number.

S:

Continues processing.

KAJV2180-W

The event acquired from the event service will be ignored because the event contains invalid information. (event database serial number = serial-number-in-event-database, reason code = reason-code)

An event acquired from Event Service will be ignored because it includes invalid information.

S:

Ignores events that include invalid information and continues processing.

O:

Check the following items:

If the reason code is 3:

The event arrival time is invalid. Use the manager to check the system time, and confirm that the time is set correctly.

If the reason code is 4:

The event registration time is invalid. Check the system time at the host that registered the event, and confirm that the time is set correctly.

If the problem is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAJV2188-I

An additional common exclusion conditions group was registered. (common exclusion conditions group ID = common-exclusion-conditions-group-ID, common exclude conditions group name = common-exclude-conditions-group-name, registering user = user-name)

An additional common exclusion-condition group was registered.

KAJV2190-I

A connection with the event base service has been established.

A connection with Event Base Service was established.

KAJV2191-I

The connection with the event base service has been canceled.

The connection with Event Base Service was ended.

KAJV2192-E

An attempt to establish a connection with the event base service has failed. Another attempt to connect will now be performed. (reason = reason)

An attempt to connect to Event Base Service failed.

S:

Retries to connect to Event Base Service.

O:

Make sure that Event Base Service is running. If it is running, make sure that the Event Base Service settings are valid. If the settings are valid, use the data collection tool to collect data, and then contact a system administrator.

KAJV2194-E

An error occurred while communicating with the event base service. The system will try to communicate again. (reason = reason)

An error occurred during communication with Event Base Service.

S:

Retries to communicate with Event Base Service.

O:

Make sure that Event Base Service is running. If it is running, make sure that the Event Base Service settings are valid. If the settings are valid, use the data collection tool to collect data, and then contact a system administrator.

KAJV2201-E

The system profile of the correlation event generation service was not found. The default value will be used.

The system profile of event generation function was not found.

S:

Continues processing using the default values.

O:

Create a correlation event generation system profile.

KAJV2202-E

A setting (setting-item-name) for the system profile of the correlation event generation service has not been set. The default value (default-value) will be used.

A setting in the correlation event generation system profile was not specified.

S:

Continues processing using the default values.

O:

Specify the setting in the correlation event generation system profile.

KAJV2203-E

The value (setting) set for a setting (setting-item) in the system profile of the correlation event generation service is invalid. The default value (default-value) will be used.

The value specified for the displayed correlation event generation system profile setting is invalid.

S:

Continues processing using the default values.

O:

Specify a correct value for the indicated correlation event generation system profile setting.

KAJV2204-E

An attempt to read the system profile of the correlation event generation service has failed. The default value will be used. (reason = reason)

An attempt to read the correlation event generation system profile failed.

S:

Continues processing using the default values.

O:

Make sure that the correlation event generation system profile can be read.

If it can be read, use the data collection tool to collect data, and then contact a system administrator.

KAJV2205-E

The system profile of the correlation event generation function was not found. The default value will be used.

The system profile of the correlation event generation function was not found.

S:

Continues processing using the default values.

O:

Create a correlation event generation system profile.

KAJV2206-E

A setting (setting-item-name) for the system profile of the correlation event generation function has not been set. The default value (default-value) will be used.

A setting item is not specified in the correlation event generation system profile.

S:

Continues processing using the default values.

O:

Specify the indicated setting item in the correlation event generation system profile.

KAJV2207-E

The value (setting) set for a setting (setting-item) in the system profile of the correlation event generation function is invalid. The default value (default-value) will be used.

The value of the indicated setting item in the correlation event generation system profile is invalid.

S:

Continues processing using the default values.

O:

Correctly set the value of the indicated setting item in the correlation event generation system profile.

KAJV2208-E

An attempt to read the system profile of the correlation event generation function has failed. The default value will be used. (reason = reason)

An attempt to read the system profile of the correlation event generation function failed.

S:

Continues processing using the default values.

O:

Check whether the correlation event generation system profile can be read.

If it can be read, use the data collection tool to collect data, and then contact a system administrator.

KAJV2210-E

An attempt to switch the event acquisition filter failed because the event database contains an invalid event.

An attempt to switch the event acquisition filter failed because the event database contained an invalid event.

S:

Continues processing using the event acquisition filter prior to switching.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2231-I

The correlation event generation definition file will now be read. (file name = file-name)

The correlation event generation definition file will be read.

S:

Continues processing.

KAJV2232-I

The read definitions will be used for processing from the next received JP1 event. (number of definitions = number-of-valid-definitions/total-number-of-definitions-in-file, time of last received event = arrival-time, serial number in the event database = serial-number-in-event-database)

The correlation event generation definition file was read using the jcoegschange command. Correlation event generation processing is performed using the correlation event generation definitions that were read, starting with the event after the one indicated by the serial number in the event database that is displayed.

S:

Continues processing.

KAJV2233-I

The correlation event generation definition has not been applied.

The correlation event generation definition was not applied.

S:

Continues processing.

O:

If using the correlation event generation function, create a correlation event generation definition file, and then apply it using the jcoegschange command.

KAJV2234-I

The correlation event generation function has stopped.

The correlation event generation function stopped.

S:

Stops processing.

KAJV2235-E

The correlation event generation definition file was not found. (file name = file-name)

The correlation event generation definition file was not found.

S:

Continues processing.

O:

Execute the jcoegschange command to redefine the correlation event generation definitions.

KAJV2236-E

There is an error in the contents of the correlation event generation definition file. (file name = file-name, line = line-number, incorrect contents = incorrect-contents)

The correlation event generation definition file contains an error.

S:

Continues processing without changing correlation event generation definitions.

O:

Determine the cause from the invalid contents, and carefully review the correlation event generation definitions.

Eliminate the cause of the error, and then execute the jcoegschange command to redefine the correlation event generation definitions.

If the error is not resolved after re-executing the command, use the JP1/IM - Manager data collection tool to collect data, and then contact a system administrator.

KAJV2238-E

An attempt to read the correlation event generation definition file failed because a file I/O error occurred. (file name = file-name)

An attempt to read the correlation event generation definition file failed due to a file I/O error.

S:

Continues processing.

O:

Determine whether the OS file I/O is in high load status.

If it is not in high load status, use the data collection tool to collect data, and then contact a system administrator.

KAJV2239-E

An attempt to read the correlation event generation definition file has failed. (file name = file-name, reason = reason)

An attempt to read the correlation event generation definition file failed.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2240-E

Event correlation processing will continue using the correlation event generation definitions from before the update, because an attempt to update the definitions failed.

An attempt to update the correlation event generation definition file failed.

S:

Continues correlation event generation processing using the correlation event generation definitions prior to the attempted update.

O:

Take the corrective action given for the message that was output preceding this message.

KAJV2242-I

The correlation event generation definition file has been read, and the definitions for the correlation event generation function have been updated. (file name = file-name)

The correlation event generation definition file was read and saved in the correlation event generation function.

KAJV2243-I

The correlation event generation function has been restarted.

The correlation event generation function was restarted.

S:

Continues processing.

KAJV2244-I

The correlation event generation definition storage file will now be read.

If not using the integrated monitoring database:

Event generation function reads the correlation event generation definition storage file.

If using the integrated monitoring database:

The correlation event generation function of Event Base Service reads the correlation event generation definition storage file.

S:

Continues processing.

KAJV2245-E

The correlation event generation definition storage file was not found.

The correlation event generation definition storage file was not found.

S:

Continues processing without correlation event generation definitions being specified.

O:

Execute the jcoegschange command to save the correlation event generation definitions again.

KAJV2246-E

An incorrect definition was detected because the correlation event generation definition storage file is corrupt. (line = line-number, incorrect contents = incorrect-contents)

An invalid definition was detected because the correlation event generation definition storage file is corrupted.

S:

Ignores the invalid definition at the relevant line and continues processing.

If correlation event generation conditions are invalid, the system ignores the invalid correlation event generation conditions and continues processing.

O:

Execute the jcoegschange command to save the correlation event generation definitions again.

KAJV2248-E

An attempt to read the correlation event generation definition storage file failed because a file I/O error occurred.

An attempt to read the correlation event generation definition storage file failed due to a file I/O error.

S:

Continues processing without correlation event generation definitions being specified.

O:

Determine whether OS file I/O is in high load status. If it is not in high load status, use the data collection tool to collect data, and then contact a system administrator.

KAJV2249-E

An attempt to read the correlation event generation definition storage file has failed. (reason = reason)

An attempt to read the correlation event generation definition storage file failed.

S:

Continues processing without correlation event generation definitions being specified.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2250-I

The correlation event generation definition storage file has been read, and the definitions for the correlation event generation function have been updated.

The correlation event generation definition storage file was read.

S:

Continues processing.

KAJV2251-E

The size of the correlation event generation definition file (file-name) exceeds the upper limit (maximum-value MB).

The size of the correlation event generation definition file exceeded the maximum.

S:

Continues processing without changing correlation event generation definitions.

O:

Carefully review the contents of the specified correlation event generation definition file, delete extra comments and redundant definitions, and then execute the jcoegschange command to save the correlation event generation definitions again.

KAJV2252-E

The size of the correlation event generation definition storage file exceeds the upper limit (maximum-value MB).

The size of the correlation event generation definition storage file exceeded the maximum.

S:

Continues processing without correlation event generation definitions being specified.

O:

Execute the jcoegschange command to define the correlation event generation definitions again.

KAJV2301-W

A JP1 event (event ID = event-ID, serial number in the event database = serial-number-in-event-database) could not be correlated because the correlation event generation condition (correlation-event-generation-condition-name) has already correlated maximum-number pairs of JP1 events.

A single correlation condition can correlate multiple pairs of JP1 events up to the number of simultaneous correlations specified (CORRELATION_NUM; if not specified, 10).

Generation processing could not be performed on the received JP1 event because the generating condition displayed in the message is already correlating maximum-number pairs of JP1 events.

S:

Continues processing.

O:

Carefully review the generating conditions.

Determine whether an unnecessarily long time-out time was specified.

Determine whether the combination of event conditions is valid.

KAJV2302-E

The event (serial number in the event database = serial-number-in-event-database) conforming to the correlation event generation condition (correlation event generation condition name = generation-condition-name) could not be correlated. (reason = reason)

A system error occurred during correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2303-E

The correlation event generation condition (condition name = correlation-event-generation-condition-name, correlation number = generation-processing-number) changed to the correlating state, but correlation processing was cancelled because a system error occurred. (reason = reason)

A system error occurred during correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of the Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2304-E

The correlation event generation condition (condition name = correlation-event-generation-condition-name, correlation number = generation-processing-number) exceeded the timeout time, but a system error occurred during timeout processing. (reason = reason)

A system error occurred during correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2305-E

The correlation event generation condition (condition name = correlation-event-generation-condition-name, correlation number = generation-processing-number) changed to the correlation-status state, but a system error occurred while registering an JP1 event. (reason = reason)

A system error occurred during correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2308-E

The correlation event generation condition (condition name = correlation-event-generation-condition-name, correlation number = generation-processing-number) changed to the correlation-status state, but a system error occurred while outputting to the correlation event generation history. (reason = reason)

A system error occurred during correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of the Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2309-W

The correlation event generation condition (condition name = correlation-event-generation-condition-name, correlation number = generation-processing-number) changed to the correlation-status state, but the correlation data being processed could not be deleted from memory. (reason = reason)

Generation processing could not be performed for the indicated generation condition and event because an error occurred during correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2310-E

A system error occurred while deleting a correlation event generation condition during correlation. Information on the trigger for deleting the correlation event generation condition cannot be correctly output to the history file. (reason = reason)

A system error occurred during correlation event generation processing.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2311-E

Information from when the correlation event generation service was stopped could not be saved. (unsaveable information = unsaveable-information, reason = reason)

When event generation function stopped, its stopped status could not be saved.

The displayed information could not be passed to the next startup.

S:

Continues stop processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2312-E

Information from the last termination could not be restored. (unrestorable information = unrestorable-information, reason = reason)

Correlation event generation function information from the previous termination could not be restored.

S:

Continues startup processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2313-E

A system error occurred while correlating an event using the correlation event generation condition. (serial number in the event database = serial-number-in-event-database, condition name = correlation-event-generation-condition-name, reason = reason)

A system error occurred during correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of Event Base Service because generation processing cannot continue.

O:

Determine whether there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2314-E

A system error occurred during timeout processing for the data being correlated. (reason = reason)

A system error occurred during time-out processing for data undergoing correlation event generation processing.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2315-E

A system error occurred during processing for a correlation that was not established. (reason = reason)

A system error occurred during processing for a correlation that was not established.

S:

If the cause is insufficient memory:

Continues processing.

If the cause is other than insufficient memory:

• If not using the integrated monitoring database:

Stops event generation function because generation processing cannot continue.

• If using the integrated monitoring database:

Stops the correlation event generation function of Event Base Service because generation processing cannot continue.

O:

Make sure that there is sufficient memory. If there is not enough memory, allocate sufficient memory.

If the cause is other than insufficient memory, use the data collection tool to collect data, and then contact a system administrator.

KAJV2316-W

The status of the correlation processing at the time the service stopped previously could not be inherited because the event acquisition starting position was set at 0-144 and the service was started.

Correlation processing resumed without inheriting the status of correlation processing that existed when the service stopped the last time because the central console was started with the event acquisition start location set from 0 through 144.

S:

Outputs the status of correlation processing that existed when the service stopped the last time to the correlation event generation history file, and resumes event correlation processing for JP1 events generated at a location subsequent to the event acquisition start location.

O:

Carefully review the setting of the event acquisition start location.

KAJV2317-E

Information from when the correlation event generation function was stopped could not be saved. (unsaveable information = unsaveable-information, reason = reason)

When the correlation event generation function of Event Base Service stopped, its stopped status could not be saved.

The displayed information could not be passed to the next startup.

S:

Continues stop processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2320-E

The correlation event could not be generated. (reason = reason, event ID = event-ID, condition name = correlation-event-generation-condition-name, correlation number = generation-processing-number)

The correlation event could not be generated.

S:

Cancels event generation.

O:

Make sure that Event Service is running. If it is not running, start it.

If Event Service is running, use the data collection tool to collect data, and then contact a system administrator.

KAJV2321-E

An attempt to create a correlation event has failed. (attribute name = attribute-name, reason = reason)

An attempt to create a correlation event failed.

S:

Cancels event generation.

O:

Make sure that the definition of the attribute value specified in the correlation event generation definition SUCCESS_EVENT or FAIL_EVENT does not exceed the maximum length of the attribute value.

KAJV2322-W

A JP1 event (event ID = event-ID, serial number in the event database = serial-number-in-event-database) could not be correlated because the number of correlated JP1 event pairs has reached the upper limit (20,000).

The number of correlating JP1 event pairs reached the upper limit (20,000 pairs).

S:

When a JP1 event that matches the event conditions is newly generated, the system continues processing without correlating the event.

JP1 event pairs that are already undergoing generation processing are correlated.

This message is output when the number of correlating JP1 event pairs reaches the upper limit and is not output again until the number of correlating JP1 event pairs decreases to 16,000.

O:

To clear all the JP1 events undergoing generation processing, take one of the following actions.

Execute the jcoegschange command, and then save the correlation event generation definitions again.

Specify cold as the startup option for the correlation event generation function, and then restart JP1/IM - Manager.

Execute the jcoegsstop command to stop correlation event generation processing, and then execute the jcoegsstart command to restart generation processing.

KAJV2324-E

There is no event correlation information for when the correlation event generation service stopped.

No event correlation information exists for when event generation function stopped because termination processing was performed incorrectly.

S:

Starts the same way as for a cold start regardless of the start option specified for event generation function startup.

O:

Check the integrated trace log to see if an event generation function error message (error messages KAJV2001 through KAJV3999) was output.

If a message was output, take the corrective action given for that message.

If no message was output, use the data collection tool to collect data, and then contact a system administrator.

KAJV2325-E

There is no event correlation information for when the correlation event generation function stopped.

No event correlation information exists for when the correlation event generation function of Event Base Service stopped because termination processing was performed incorrectly.

S:

Starts the same way as for a cold start regardless of how the start option was specified in the correlation event generation function of Event Base Service.

O:

Check the integrated trace log to see if an error message of the correlation event generation function of Event Base Service (error messages KAJV2001 through KAJV3999) was output.

If a message was output, take the corrective action given for that message.

If no message was output, use the data collection tool to collect data, and then contact a system administrator.

KAJV2401-E

The correlation event generation history file could not be created. The history cannot be output.

The correlation event generation history could not be output because the correlation event generation history file could not be created.

S:

Continues processing without outputting the correlation event generation history.

O:

Make sure that write permission is assigned for the directory that contains the correlation event generation history file.

If write permission is assigned, make sure that OS resources such as memory and file descriptors are sufficient.

KAJV2402-E

A system error occurred while outputting the correlation event generation history. (reason = reason)

The correlation event generation history could not be output due to a system error.

S:

Continues processing without outputting the correlation event generation history.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2403-E

An I/O error occurred while outputting the correlation event generation history.

The correlation event generation history could not be output due to an I/O error.

S:

Continues processing without outputting the correlation event generation history.

O:

Make sure that write permission is assigned for the correlation event generation history file.

If write permission is assigned, make sure that OS resources such as memory and file descriptors are sufficient.

KAJV2404-E

A memory shortage occurred while outputting the correlation event generation history.

The correlation event generation history could not be output because a memory shortage occurred.

S:

Continues processing without outputting the correlation event generation history.

O:

Check the OS log, and then make sure that memory is sufficient.

If memory is insufficient, allocate more memory.

KAJV2500-I

The correlation event issuing service will use the common-exclusion-condition-to-use. : logical-host-name

Event Generation Service will use the common-exclusion-condition-to-use.

S:

Continues processing.

KAJV2501-W

The correlation event issuing service cannot use common exclusion condition groups (extended) because an event acquisition filter (for compatibility) is set.

Event Generation Service cannot use common exclusion-condition groups in extended mode because an event acquisition filter (for compatibility) is set.

S:

Continues processing using the event acquisition filter (for compatibility).

O:

To extend common exclusion-condition groups, you need to change the location of the event acquisition filter from Event Console Service to Event Base Service.

Use the jcochafmode command to change the location of the filter, and then restart JP1/IM - Manager.

Note that you cannot undo the jcochafmode command that changes the location of the event acquisition filter.

If you do not want to extend the common exclusion-condition groups, execute the jcochcefmode command in JP1/IM - Manager as shown below to set the operation mode for the common exclusion-condition groups to basic mode.

jcochcefmode -m default [-h logical-host-name]

KAJV2502-W

The correlation event issuing service cannot use common exclusion condition groups (extended) because the regular expressions used by JP1/Base are not extended. The correlation event issuing service will start without any common exclusion condition groups (extended) being set.

Event Generation Service cannot use common exclusion-condition groups in extended mode because a regular expression used by JP1/Base is not extended.

S:

Assumes that common exclusion-condition groups are not defined, and continues processing.

O:

To extend common exclusion-condition groups, you need to extend the regular expressions used by JP1/Base. Extend the regular expressions for JP1/Base, and then restart JP1/IM - Manager.

Extending regular expressions will affect the JP1/Base and JP1/IM functions. For details about how to extend regular expressions, see the JP1/Base manual.

If you do not want to extend the common exclusion-condition groups, execute the jcochcefmode command in JP1/IM - Manager as shown below to clear the extended mode setting for the common exclusion-condition groups. Then restart JP1/IM - Manager.

jcochcefmode -m normal [-h logical-host-name]

KAJV2503-E

An error occurred during reading of the common exclusion conditions extended definition file. (cause = cause)

An error occurred during reading of the common-exclusion-conditions extended definition file.

S:

If the error occurred during switching of the event acquisition filter, the system continues processing using the event acquisition filter that was in use prior to switching.

If the error occurred during startup of Event Generation Service, the system continues processing with no definition specified in the event acquisition filter.

O:

If the message shown below is displayed for cause, the definition file might be corrupted. Stop JP1/IM - Manager, change the operation mode for the common exclusion-conditions to basic mode, and then change it back to extended mode to initialize the definition of the common exclusion-conditions (extended).

The common exclusion extended definition file is invalid.

If the following message is displayed for cause, allocate sufficient memory, and then retry the operation.

A memory shortage occurred while loading was being performed.

If the following message is displayed for cause, check whether a shortage has occurred in other OS resources such as file descriptors.

An I/O error occurred while loading was being performed.

If a message other than the above is displayed for cause or if the problem cannot be resolved, check the following OS log items.

In Windows: Windows event log

In UNIX: System log (syslog)

After checking the OS log items, check whether a shortage has occurred in other OS resources such as file descriptors. If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAJV2901-E

A system error occurred. (reason = reason)

A system error occurred.

S:

Aborts the processing that generated the error.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2902-E

An error occurred during an abnormal termination of the correlation event generation service. The service will now be forced to terminate. (reason = reason)

An error occurred when event generation function stopped abnormally.

S:

Forcibly terminates event generation function.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2903-E

Processing cannot continue because an error occurred while the correlation event generation service was starting. (reason = reason)

Processing could not continue because an error occurred while event generation function was starting.

S:

Stops event generation function.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2904-E

An error occurred while the correlation event generation service was stopping. The correlation event generation service cannot terminate normally. A forced termination will now be performed. (reason = reason)

An error occurred while event generation function was stopping.

S:

Forcibly terminates event generation function.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2905-E

A system error occurred while correlating an event using the correlation event generation condition. (serial number in the event database = serial-number-in-event-database, generation condition name = generation-condition-name, reason = reason)

A system error occurred during correlation event generation processing.

S:

Integrated monitoring database is not in use

Stops event generation function because generation processing could not continue.

Integrated monitoring database is in use

Stops Event Base Service because generation processing could not continue.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2906-E

Processing cannot continue because an error occurred while the correlation event generation function was starting. (reason = reason)

Processing cannot continue because an error occurred while the correlation event generation function of Event Base Service was starting.

S:

Stops the correlation event generation function of Event Base Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV2907-E

An error occurred while the correlation event generation function was stopping. The correlation event generation function cannot terminate normally. A forced termination will now be performed. (reason = reason)

An error occurred while the correlation event generation function of Event Base Service was stopping.

S:

Forcibly terminates the correlation event generation function of Event Base Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3002-E

A value set for common definition information (common-definition) is outside the valid range. The default value (default-value) will be used. (valid range = minimum-value to maximum-value)

A value specified for common definition information is outside the valid range.

S:

Continues processing using the default value displayed in the message.

O:

Specify a value within the valid range for the common definition information.

KAJV3003-E

A value set (set-value) for common definition information (common-definition) is invalid. The default value (default-value) will be used.

A value specified for common definition information is invalid.

S:

Continues processing using the default value displayed in the message.

O:

Change the value for the common definition information.

KAJV3004-E

An attempt to read common definition information (common-definition) has failed. The default value (default-value) will be used. (reason = reason)

An attempt to read the common definition information displayed in the message failed.

S:

Continues processing using the default value displayed in the message.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3010-E

Common definition information (common-definition) required for the command command has not been set.

Common definition information required for command startup was not specified.

S:

Uses the default value.

O:

Reinstall JP1/IM - Manager.

KAJV3021-E

An unsuitable parameter (parameter) has been specified.

A parameter that cannot be specified was specified.

S:

Terminates command processing.

O:

Correct the parameter, and then retry the operation.

KAJV3022-E

The parameter (parameter) value has not been specified.

A value required for the displayed parameter was not specified.

S:

Terminates command processing.

O:

Specify a value for the parameter, and then retry the operation.

KAJV3023-E

The parameter (parameter) value is invalid.

A value specified for the displayed parameter is invalid.

S:

Terminates command processing.

O:

Specify a valid value for the parameter, and then retry the operation.

KAJV3024-E

Duplicated parameters (parameter) cannot be specified.

The displayed parameter cannot be specified more than once.

S:

Terminates command processing.

O:

Correct the parameter, and then retry the operation.

KAJV3025-E

Parameters (parameter-1, parameter-2) cannot be simultaneously specified.

The displayed parameters cannot be specified simultaneously.

S:

Terminates command processing.

O:

Correct the parameter, and then retry the operation.

KAJV3026-E

Specify the parameter (parameter).

A required parameter was not specified.

S:

Terminates command processing.

O:

Specify the displayed parameter.

KAJV3027-E

An unsuitable logical host name has been specified.

A nonexistent host name was specified by JP1_DEFAULT.

S:

Terminates command processing.

O:

Correct the logical host name, and then retry the operation.

KAJV3040-E

You do not have execution permission.

There is insufficient permission to execute the command.

S:

Terminates command processing.

O:

Log in as a user with sufficient permission to execute this command, and then retry the operation.

KAJV3041-E

A processing timeout occurred because the correlation event generation service did not respond.

Command processing timed out because event generation function did not respond.

S:

Terminates command processing.

O:

There may have been an overload of event generation function or the OS. Wait awhile, and then re-execute the command.

KAJV3042-E

An attempt to establish a connection with the correlation event generation service has failed. Check whether the event correlation service is running.

Connection with event generation function failed.

S:

Terminates command processing.

O:

Make sure that event generation function has started.

KAJV3043-E

A processing timeout occurred because the event base service did not respond.

Command processing timed out because Event Base Service did not respond.

S:

Terminates command processing.

O:

There may have been an overload of Event Base Service or the OS. Wait awhile, and then re-execute the command.

KAJV3044-E

An attempt to establish a connection with the event base service has failed. Check whether the event base service is running.

Connection with Event Base Service failed.

S:

Terminates command processing.

O:

Make sure that Event Base Service has started.

KAJV3101-E

An I/O error occurred while communicating with the correlation event generation service.

Communication failed because an I/O error occurred during communication with event generation function.

S:

Terminates command processing.

O:

Check the integrated trace log to see if an error occurred in event generation function.

After checking, re-execute the command.

KAJV3102-E

Invalid data was received from the correlation event generation service.

Invalid data was received from event generation function.

S:

Terminates command processing.

O:

Check the integrated trace log to see if an error occurred in event generation function.

After checking, re-execute the command.

KAJV3103-E

An I/O error occurred while communicating with the event base service.

Communication failed because an I/O error occurred during communication with Event Base Service.

S:

Terminates command processing.

O:

Check the integrated trace log to see if an error occurred in Event Base Service.

After checking, re-execute the command.

KAJV3104-E

Invalid data was received from the event base service.

Invalid data was received from Event Base Service.

S:

Terminates command processing.

O:

Check the integrated trace log to see if an error occurred in Event Base Service.

After checking, re-execute the command.

KAJV3201-I

The correlation event generation definition file (file-name) has been read, and the definitions for the correlation event generation function on (host-name) have been updated.

The correlation event generation definition file for the host displayed in the message was read, and the correlation event generation functions have become operational.

KAJV3205-E

There is an invalid definition in the correlation event generation definition.

There is an invalid definition in the correlation event generation definition.

S:

Continues command processing.

O:

Refer to the messages in the integrated trace log to correct the invalid locations.

KAJV3206-E

An attempt to update the correlation event generation definition for host-name has failed. (reason = reason)

Integrated monitoring database is not in use.

Updating of the correlation event generation definition failed because an error occurred in event generation function.

Integrated monitoring database is in use.

Updating of the correlation event generation definition failed because an error occurred in the correlation event generation function of Event Base Service.

S:

Integrated monitoring database is not in use.

Event generation function continues processing as before the update.

Integrated monitoring database is in use.

The correlation event generation function of Event Base Service continues processing as before the update.

O:

Another command is now executing.

Because the jcoegschange command changed the correlation event generation definition file or the jcoegsstatus command referenced the correlation event generation definition file, processing was retried, but it could not be referenced. Retry the operation.

An I/O error occurred.

In Windows, check the event log, or in UNIX, check the syslog file, for an OS error such as insufficient disk space or a file I/O error.

If an OS error did not occur, use the data collection tool to collect data, and then contact a system administrator.

There is insufficient memory.

Make sure that there is sufficient memory. If there is insufficient memory, allocate more memory.

If there is sufficient memory, use the data collection tool to collect data, and then contact a system administrator.

Other than the above

Check the integrated trace log to see if an error was output by event generation function.

If an error was output, take the corrective action given for that message.

KAJV3209-E

The correlation event generation definition file for host-name was not found. (file name = file-name)

The correlation event generation definition file was not found.

S:

Terminates command processing.

O:

Execute the jcoegschange command, and then reset the correlation event generation definition file.

KAJV3211-E

The correlation event generation service is currently performing processing processing.

The command processing could not performed because event generation function is currently starting or stopping.

S:

Terminates command processing.

O:

If event generation function is starting, use the jco_spmd_status command to check the status of the startup, and then execute the command. If event generation function is stopping, the command processing cannot be performed. Execute the command after event generation function has started.

KAJV3212-E

Inappropriate characters were specified in the correlation event generation definition file name.

Unusable characters were used in the specified correlation event generation definition file name.

S:

Terminates command processing.

O:

Determine whether unusable characters (characters other than alphanumeric characters or the underscore) were used in the specified file name.

KAJV3214-E

The extension of the specified correlation event generation definition file is not conf.

The extension of the specified correlation event generation definition file is not conf.

S:

Terminates command processing.

O:

Set the extension of the correlation event generation definition file name to conf.

KAJV3215-E

The directory cannot be specified for a correlation event generation definition file.

A directory cannot be specified as a correlation event generation definition file.

S:

Terminates command processing.

O:

Specify the name of the file saved in the correlation event generation definition path.

KAJV3216-E

An invalid file name was specified for the correlation event generation definition file.

The file could not be read due to an invalid file name.

In Windows, the following file names cannot be used without the conf extension.

CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

Examples: CON.conf, PRN.conf

S:

Terminates command processing.

O:

Correct the name of the specified correlation event generation definition file, and then retry the operation.

KAJV3217-E

The size of the correlation event generation definition file (file-name) exceeds the upper limit (maximum-value MB).

The size of the correlation event generation definition file exceeds the maximum value.

S:

Terminates command processing.

O:

Check the contents of the specified correlation event generation definition file, delete surplus comments or excessive definitions, and then retry the operation.

KAJV3218-E

The correlation event generation function is currently performing processing processing.

The command processing could not performed because the correlation event generation function of Event Base Service is currently starting or stopping.

S:

Terminates command processing.

O:

If the correlation event generation function of Event Base Service is starting, use the jco_spmd_status command to check the status of the startup, and then retry the operation. If Event Base Service is stopping, the command processing cannot be performed. Execute the command after Event Base Service has started.

KAJV3261-I

The status of the correlation event generation service for host-name will now be displayed.

The status of event generation function is displayed.

KAJV3262-I

The correlation event generation service for host-name has stopped.

Event generation function stopped.

S:

Terminates command processing.

KAJV3263-E

An attempt to acquire the status of the correlation event generation service for host-name has failed. (reason = reason)

The status of event generation function cannot be displayed because the status could not be acquired.

S:

Terminates command processing.

O:

Take one of the following corrective actions according to the reason:

Another command is now executing

The correlation event generation definition file could not be referenced, even after processing was retried because the jcoegschange command was in the process of changing the file or the jcoegsstatus command was in the process of referencing the file. Retry the operation.

An I/O error occurred

In Windows, check the event log, or in UNIX, check the syslog file, for an OS error such as insufficient disk space or a file I/O error. If an OS error did not occur, use the data collection tool to collect data, and then contact a system administrator.

Other than the above

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3264-I

The status of the correlation event generation function for host-name will now be displayed.

The status of the correlation event generation function of Event Base Service is displayed.

KAJV3265-E

An attempt to acquire the status of the correlation event generation function for host-name has failed. (reason = reason)

The status of the correlation event generation function of Event Base Service cannot be displayed because the status could not be acquired.

S:

Terminates command processing.

O:

Take one of the following corrective actions according to the reason:

Another command is now executing

The correlation event generation definition file could not be referenced, even after processing was retried because the jcoegschange command was in the process of changing the file or the jcoegsstatus command was in the process of referencing the file. Retry the operation.

An I/O error occurred

In Windows, check the event log, or in UNIX, check the syslog file, for an OS error such as insufficient disk space or a file I/O error. If an OS error did not occur, use the data collection tool to collect data, and then contact a system administrator.

Other than the above

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3281-I

The correlation event generation definition for host-name will now be displayed.

The correlation event generation definition is displayed.

KAJV3282-E

An attempt to obtain the correlation event generation definition for host-name has failed. (reason = reason)

The status of the correlation event generation condition cannot be displayed because the status could not be acquired.

S:

Terminates command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3283-I

The correlation event generation definition for host-name has not been defined.

The correlation event generation definition was not defined.

S:

Continues processing.

O:

Define the correlation event generation definition.

KAJV3284-I

Operations will proceed without a set correlation event generation definition because an attempt to read the correlation event generation definition for host-name has failed.

Processing will proceed without a specified correlation event generation definition because an attempt to read the correlation event generation definition failed.

S:

Continues processing.

O:

Determine whether there is an overload in the file I/O on the OS.

If there is not an overload, use the data collection tool to collect data, and then contact a system administrator.

KAJV3285-I

Operations will continue while ignoring an invalid correlation event generation definition of host-name.

There is an invalid condition due to a corrupted correlation event generation definition applied in the correlation event generation function.

The correlation event generation function ignores the invalid correlation event generation definition and continues processing.

S:

Continues processing.

O:

Execute the jcoegschange command to re-apply the correlation event generation definition.

KAJV3286-E

The size of the correlation event generation definition storage file exceeds the upper limit (maximum-value MB).

The size of the correlation event generation definition storage file exceeds the upper limit.

S:

Terminates command processing.

O:

Use the jcoegschange command to redefine the correlation event generation definition.

KAJV3291-I

The correlation event generation function for host-name has restarted.

The correlation event generation function restarted.

S:

Continues processing.

KAJV3292-E

An attempt to restart the correlation event generation function for host-name has failed. (reason = reason)

An attempt to restart the correlation event generation function failed.

S:

Terminates command processing.

O:

Take one of the following corrective actions according to the reason:

If the reason is A memory shortage occurred, determine whether a memory insufficiency occurred. If a memory insufficiency occurred, allocate more memory. If a memory insufficiency did not occur, use the data collection tool to collect data, and then contact a system administrator.

If the reason is The correlation event generation function of the event base service is invalid, determine whether the correlation event generation function is invalid.

If the reason is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAJV3293-W

The correlation event generation function for host-name has already started.

The correlation event generation function has already started.

S:

Terminates command processing.

KAJV3301-I

The correlation event generation function for host-name has stopped.

The correlation event generation function stopped.

S:

Continues processing.

KAJV3302-E

An attempt to stop of the correlation event generation function for host-name has failed. (reason = reason)

An attempt to stop the correlation event generation function failed.

S:

Terminates command processing.

O:

Take one of the following corrective actions according to the reason:

If the reason is A memory shortage occurred, determine whether a memory insufficiency occurred. If a memory insufficiency occurred, allocate more memory. If a memory insufficiency did not occur, use the data collection tool to collect data, and then contact a system administrator.

If the reason is The correlation event generation function of the event base service is invalid, determine whether the correlation event generation function is invalid.

If the reason is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAJV3303-W

The correlation event generation function for host-name has already stopped.

The correlation event generation function has already stopped.

S:

Terminates command processing.

KAJV3311-I

The content of the correlation event generation definition file (file-name) will now be checked.

Checks the contents of the correlation event generation definition file.

S:

Continues processing.

KAJV3312-I

No mistakes were found in the content of the correlation event generation definition file (file-name).

No errors were found in the contents of the correlation event generation definition file.

S:

Terminates command processing.

KAJV3313-E

There is an invalid definition in the correlation event generation definition.

There is an invalid definition in the correlation event generation definition.

S:

Continues command processing.

O:

Correct the invalid location indicated in the message output to standard error.

KAJV3314-E

There is an error in the contents of the correlation event generation definition file. (file name = file-name, line = line-number, incorrect contents = incorrect-contents)

There is an error in the contents of the correlation event generation definition file.

S:

Continues processing.

O:

Correct the invalid location indicated in the message.

KAJV3315-W

The correlation event generation definition does not contain a valid definition.

The correlation event generation definition file does not contain any valid condition.

S:

Terminates command processing.

KAJV3316-E

The correlation event generation definition file (file-name) was not found.

The correlation event generation definition file was not found.

S:

Terminates command processing.

O:

Make sure that the specified path is correct.

KAJV3317-E

An attempt to read the correlation event generation definition file (file-name) failed because a file I/O error occurred.

An attempt to read the correlation event generation definition file failed because a file I/O error occurred.

S:

Terminates command processing.

O:

Determine whether there is an overload in the file I/O on the OS.

If there is not an overload, use the data collection tool to collect data, and then contact a system administrator.

KAJV3318-E

An attempt to check the correlation event generation definition file (file-name) has failed. (reason = reason)

An attempt to check the correlation event generation definition file failed.

S:

Terminates command processing.

O:

Take one of the following corrective actions according to the reason:

a memory shortage occurred

Make sure that there is sufficient memory. If there is insufficient memory, allocate more memory.

If there is sufficient memory, use the data collection tool to collect data, and then contact a system administrator.

Other than the above

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3801-E

A system error occurred when using the command command. (reason = reason)

Processing could not continue because a system error occurred while using the command.

S:

Continues command processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3901-E

An attempt to create the message (message ID = ID) has failed. (reason = reason)

An unexpected error occurred during creation of the message.

S:

Aborts output of the message and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3902-E

The message could not be output to output-destination. (reason = reason) (message = message)

An unexpected error occurred during output of the message to the displayed output destination.

S:

Aborts output of the message and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3903-E

An attempt to initialize the integrated trace log has failed. (reason = reason)

An attempt to initialize the integrated trace log failed.

S:

Cannot output messages to the integrated trace log.

Outputs messages that are output to the common message log.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3904-E

The output destination of the message cannot be acquired. (reason = reason)

The output destination of the message cannot be acquired from the resource.

S:

Outputs the message to the OS log and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJV3905-E

An attempt to acquire the output information for the message has failed. (reason = reason)

The output information for the message could not be acquired from the resource.

S:

Outputs the message to the OS log and continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

2.12 Messages related to IM Configuration Management - View (KNAN20000 to KNAN21999)

KNAN20000-E

A system error has occurred.

Detail code: detail-code

A system error occurred.

S:

Terminates IM Configuration Management - View.

O:

If the following is displayed for detail-code, take the indicated corrective action.

V000001

JP1/Base might have been uninstalled.

Because JP1/IM - View definition information is deleted, uninstall JP1/IM - View, and then install it again.

If any detail code other than the above is displayed, use the data collection tool to collect data, and then contact a system administrator.

KNAN20001-E

Memory was insufficient.

Detail code: detail-code

Memory is insufficient.

S:

Continues processing.

O:

Make sure that there is sufficient memory, and then restart IM Configuration Management - View.

KNAN20002-E

A system error occurred when processing.

A system error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN20003-I

The application terminated normally.

IM Configuration Management - View ended normally.

S:

Terminates IM Configuration Management - View.

KNAN20004-E

The application terminated abnormally.

IM Configuration Management - View ended abnormally.

S:

Terminates IM Configuration Management - View.

O:

Check the following items, and take correction action:

Determine whether IM Configuration Management Service started normally.

Take the corrective action indicated in the message prior to this message.

If this method cannot resolve the issue, use the data collection tool to collect data, and then contact a system administrator.

KNAN20005-E

An internal error occurred when processing.

An internal error occurred in IM Configuration Management - View.

S:

Continues IM Configuration Management - View processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN20006-E

Invalid data was received from the server when processing.

Invalid data was received from the server.

S:

Continues IM Configuration Management - View processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN20007-E

An error occurred for the command "processing".

A failure occurred during standby and stop processing.

S:

Continues IM Configuration Management - View processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN20008-E

An error occurred when processing.

An error occurred in IM Configuration Management - View.

S:

Continues IM Configuration Management - View processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN20009-I

The application forced termination.

IM Configuration Management - View was forcibly terminated.

S:

Terminates IM Configuration Management - View.

KNAN20010-E

Execution of the specified application failed.

Application: application-name

Detail code: detail-code

Execution of the application failed.

S:

Suspends execution of the application.

O:

Make sure that the application was correctly installed or set up, and then retry the operation.

KNAN20011-W

Since there is an error in the registry key, CF-View is started by using default value.

Registry key : registry-key-name

A registry value is incorrect.

S:

Starts IM Configuration Management - View.

O:

Make sure that an appropriate value is set in the registry, and then retry the operation.

KNAN20020-W

CF-View started by using the default values because a file could not be read.

File name: file-name

Detail code: detail-code

An error occurred while reading a file.

S:

Assumes the default value for the defined value and continues processing.

O:

Check the following items, and then retry the operation.

Is there sufficient memory?

Does the file exist?

Has the file access permission been set correctly?

Has the file been opened (locked) by another application?

KNAN20021-W

CF-View started by using the default values because there is an error in a file.

File name: file-name

Attribute name: attribute-name

Detail code: detail-code

An error occurred in the file contents.

S:

Assumes the default value for the defined value and continues processing.

O:

Make sure that the contents of the file are specified correctly, and then retry the operation.

KNAN20022-E

A file could not be created.

File name: file-name

Detail code: detail-code

A file could not be created.

S:

Suspends file creation.

O:

Check the following items, and then retry the operation:

Is there sufficient memory?

Has the directory access permission been set correctly?

Does the directory exist at the specified path?

Has the file been opened (locked) by another application?

Does the file name contain any of the following invalid characters?

/, :, ?, \", <, >, |, \\, *

KNAN20023-E

An error occurred when writing to a file.

File name: file-name

Detail code: detail-code

An error occurred while writing to a file.

S:

Suspends writing to the file.

O:

Check the following items, and then retry the operation:

Is there sufficient memory?

Has the file access permission been set correctly?

Has the file been opened (locked) by another application?

KNAN20024-E

An error occurred when deleting a file.

File name: file-name

An error occurred while deleting a file.

S:

Suspends file deletion.

O:

Check the following items, and then retry the operation:

Has the file access permission been set correctly?

Has the file been opened (locked) by another application?

KNAN20025-E

The content of the file is invalid.

File name: file-name

Attribute name: attribute-name

The contents of the help file contain an invalid value, or the file does not exist.

S:

Continues IM Configuration Management - View processing without displaying the online manual.

O:

Check the following items, and then retry the operation:

Are the attributes of the helpid.txt file valid?

Have the attributes of the helpid.txt file been specified correctly?

KNAN20026-E

An error occurred while reading a file.

File name: file-name

Detail code: detail-code

An error occurred while reading a help file.

S:

Continues IM Configuration Management - View processing without displaying the online manual.

O:

Check the following items, and then retry the operation:

Is there sufficient memory?

Does the help file exist?

Has the file access permission been set correctly?

KNAN20030-W

image-file was not found.

Path: path-name

An error occurred while displaying an image file.

S:

Continues processing without the image.

O:

Check the following items, and then retry the operation:

Does the file exist?

Has the file access permission been set correctly?

Has the file been opened (locked) by another application?

KNAN20040-E

An item was not input. Please input it, and then try again.

Item : input-item

A required input item was not input.

S:

Waits for re-entry of information.

O:

Input the required item, and then retry the operation.

KNAN20041-E

The format of an item is invalid. Please change the value of the item, and then try again.

Item: input-item

The format of an input item is invalid.

S:

Waits for re-entry of information.

O:

Change the value of the input item, and then retry the operation.

KNAN20042-E

The value of an item is outside the valid range. Please change the value of the item and then try again.

Item : input-item

Valid range: input-range

The value of an input item is outside the valid range.

S:

Waits for re-entry of information.

O:

Change the value of the input item, and then retry the operation.

KNAN20043-E

The number of values that can be set for an item has exceeded the upper limit. Please change the values of the item and then try again.

Item: input-item

Upper limit: upper-limit

The number of values that can be specified for an item exceeded the maximum.

S:

Waits for re-entry of information.

O:

Change the value of the input item, and then retry the operation.

KNAN20044-E

The invalid characters are input in the file name.

Please change the input value and re-execute.

File name: file-name

Invalid characters were used in the file name.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Does the file name contain control characters?

Does the file name contain a reserved device name?

Does the file name contain any of the following invalid characters?

/, :, ?, \", <, >, |, \\, *

KNAN20045-Q

Changes to the common system settings have not been saved.

Are you sure you want to close the common system setup window?

This message confirms that you want to close the System Common Settings window.

O:

Click the Yes button to close the System Common Settings window. Click the No button if you do not want to close the System Common Settings window.

KNAN20046-E

The passwords do not match.

Confirm the passwords, and then try again.

A wrong password was entered.

S:

Suspends processing.

O:

Check the password, and then retry the operation.

KNAN20048-W

The system common setting for remote monitoring is not set.

The system common settings for remote monitoring are not specified.

S:

Suspends processing.

O:

Check the system common settings for remote monitoring, specify the settings, and then retry the operation.

KNAN20050-W

The exclusive edit status of exclusive-data data was forcibly released by the user user-name:View-host-name.

Another user forcibly released exclusive edit status.

S:

Continues processing.

O:

Save the contents because the data being edited cannot be updated on the server. After saving the contents, close the editing window, and then re-open the window to acquire exclusive edit rights.

KNAN20051-E

Failed to acquire latest information since IM configuration management DB cannot be accessed.

Acquisition of data from the server failed.

S:

Suspends processing.

O:

Make sure that the IM database server started normally, and then retry the operation.

If this method cannot resolve the issue, use the data collection tool to collect data, and then contact a system administrator.

KNAN20052-W

An error occurred in the initialization processing of the integrated trace log output.

An error occurred in the initialization processing of the integrated trace log output. Messages cannot be output to the integrated trace log.

S:

Continues processing.

O:

Determine whether the following service has been started:

Hitachi Network Objectplaza Trace Monitor 2

If it has not been started, start the service, and then restart IM Configuration Management - View.

KNAN20054-E

The IP address for the local host could not be found.

The IP address for the agent host could not be acquired.

S:

Suspends processing.

O:

Make sure that the local host resolves the IP address, and then retry the operation.

KNAN20055-E

The specified encoding "character-code" is not supported.

An unsupported character code was specified.

S:

Continues processing.

O:

Specify a supported character code.

KNAN20056-I

The latest status will be acquired because the IM Configuration and host list information has changed. If any processes are being executed, close them after closing this message.

The latest status will be acquired because the IM configuration (system hierarchy) or host list information changed.

KNAN20057-I

The latest information from the server will be acquired. If any processes are being executed, close them after closing this message.

The latest information will be acquired because the IM configuration or host information was updated.

KNAN20100-E

Address resolution for the specified connection destination host name failed.

Connection destination host name: connection-destination-host-name

Due to an error in the input for the connection host name, a connection could not be established with the connection host.

S:

Suspends processing.

O:

Make sure that the entered connection host name is correct, and then retry the operation.

KNAN20101-E

Communication error occurred in establishing the connection.

Connection destination host name: connection-host-name

Port number: port-number

A connection could not be established with the connection host because the connection host is not started.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Was the connection host name input correctly?

Is the port number available for use?

Is the connection host started?

Is there a problem communicating with the connection host?

Is the IM Configuration Management database set up?

Is the use of IM Configuration Management specified?

Is the IM database running?

Is an IPv6 address entered for the connection host name?

Can the IPv4 address be resolved for the entered connection host name?

Use the jco_spmd_status command to confirm that the connection host has been started.

KNAN20102-E

Communication error occurred in establishing the connection.

Connection destination host name: connection-host-name

Port number: port-number

Detail code: detail-code

A communication error occurred during connection to the host.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Was the connection host name input correctly?

Is the port number available for use?

Is the connection host started?

Is there a problem communicating with the connection host?

Is an IPv6 address entered for the connection host name?

Can the IPv4 address be resolved for the entered connection host name?

If the communication encryption function is enabled on the host to be connected to, have the encrypted communication settings been specified in JP1/IM - View?

Use the jco_spmd_status command to confirm that the connection host has been started.

KNAN20103-E

A communication error occurred while sending data.

Host name: connection-host-name

Port number: port-number

Detail code: detail-code

A communication error occurred while sending data.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Was the connection host name input correctly?

Is the connection host started?

Is there a problem communicating with the connection host?

KNAN20104-E

A communication error occurred while receiving data.

Host name: connection-host-name

Port number: port-number

Detail code: detail-code

A communication error occurred while receiving data.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Was the connection host name input correctly?

Is the port number available for use?

Is the connection host started?

Is there a problem communicating with the connection host?

Use the jco_spmd_status command to confirm that the connection host has been started.

KNAN20105-E

A timeout occurred during the wait for a response of request-name.

Connection destination host name: connection-host-name

Port number: port-number

A time-out occurred while waiting for a response.

S:

Suspends processing.

O:

Check the following items, wait awhile, and then retry the operation.

Is the connection host started?

Is there a problem communicating with the connection host?

If this message is output frequently, adjust the setting for the time-out value. If the above methods cannot resolve the problem, contact a system administrator and check the load on the manager host.

KNAN20121-E

An error occurred during the initialization of the communication encryption function for CF - View. (cause = cause, directory = directory-name)

An error occurred during the initialization of the communication encryption function on the IM configuration management viewer.

S:

Terminates processing.

O:

Check the following items:

If No root authentication certificates were found. is displayed for cause, check if there is a root certificate, and then log in again:

• If there is a root certificate, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• If there is no root certificate, create a root certificate.

If None of the root authentication certificates could be read. is displayed for cause, check the following items, and then log in again:

• Check if there is a root certificate. If there is a root certificate, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• Verify that there is no problem in the root certificate file.

• Check the Windows event log to see if a shortage has occurred in an OS resource such as file descriptors.

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If The placement directory for root authentication certificates could not be found. is displayed for cause, create a directory for storing root certificates, and then place the root certificate there.

KNAN20122-E

Failed to encrypt communications by using the communication encryption function for CF - View. (host name of connection destination = connection-target-host-name, cause = cause)

An attempt to establish encrypted communication with the target host has failed.

S:

Terminates processing.

O:

Check the following items:

If The CN or SAN of the server authentication certificate does not match with the host name of the connection destination. is displayed for cause, verify that the CN or SAN in the server certificate of the connection-target manager host matches the connection-target host name in the IM configuration management viewer, and then log in again.

If A communication error occurred. is displayed for cause, check the items listed below, and then log in again. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

• Verify that the communication encryption function is enabled on the connection-target manager host. If the communication encryption function is enabled, verify that the non-encryption communication host configuration file does not contain the connection-target manager host name.

• Check if the message Failed to read some of the root authentication certificates was output to the integrated trace log. If this message has been output, take the corrective action given for that message.

• Check if the root certificate corresponding to the server certificate of the connection-target manager host has been placed in JP1/IM - View. If the root certificate has not been placed, place the root certificate.

• Check if the server certificate of the connection-target manager host has expired. If it has expired, renew the server certificate.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact the system administrator.

KNAN20123-W

Failed to read some of the root authentication certificates used by the communication encryption function for CF - View. (directory = directory-name, file = file-name, file-name, ...)

An attempt to read some of the root certificates that are used by the communication encryption function in the IM configuration management viewer has failed.

S:

Ignores the files that could not be imported and continues processing.

O:

Check the items listed below. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

Check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

Check the Windows event log to see if a shortage has occurred in an OS resource such as file descriptors.

Verify that there is no problem in the root certificate files.

KNAN20124-W

The root authentication certificate used by the communication encryption function for CF - View is no longer valid. (directory = directory-name, file = file-name, file-name, ...)

The root certificate used by the communication encryption function in the IM configuration management viewer has expired.

S:

Continues processing.

O:

Check whether operating with an expired root certificate will cause a problem. If it will, update the root certificate.

KNAN20131-E

A non-encryption communication host configuration file for CF - View was not found. (file = file-name)

There is no non-encryption communication host configuration file for the IM configuration management viewer.

S:

Terminates processing.

O:

Check the following items, and then log in again:

Check if there is a non-encryption communication host configuration file. If there is no non-encryption communication host configuration file, create one.

Check whether you have read permission for the non-encryption communication host configuration file. If not, set read permission for the file.

KNAN20132-E

The non-encryption communication host configuration file for CF - View failed to load. (file = file-name)

An attempt to load the non-encryption communication host configuration file for the IM configuration management viewer has failed.

S:

Terminates processing.

O:

Check Windows event log to see if a shortage has occurred in an OS resource such as file descriptors.

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KNAN20133-E

The first line of the non-encryption communication host configuration file for CF - View is not "[NO_SSL_HOST]". (file = file-name)

[NO_SSL_HOST] is not on the first line of a non-encryption communication host configuration file for the IM configuration management viewer.

S:

Terminates processing.

O:

Enter [NO_SSL_HOST] on the first line of the non-encryption communication host configuration file, and then log in again.

KNAN20134-E

The number of manager host names specified in the non-encryption communication host configuration file for CF - View exceeds the maximum (maximum-value). (file = file-name)

The number of manager hosts in the non-encryption communication host configuration file for the IM configuration management viewer exceeds the maximum value.

S:

Terminates processing.

O:

Check the number of manager hosts in the non-encryption communication host configuration file and correct it. After that, log in again.

KNAN20135-E

The length of a manager host name specified in the non-encryption communication host configuration file for CF - View exceeds the maximum (maximum-value). (line number = line-number, file = file-name)

The length of a manager host name specified in the non-encryption communication host configuration file for the IM configuration management viewer exceeds the maximum value.

S:

Terminates processing.

O:

Correct the manager host name on the specified line in the non-encryption communication host configuration file, and then log in again.

KNAN20136-E

The syntax for asterisks (*) in the manager host name for the non-encryption communication host configuration file for CF - View is invalid. (file = file-name)

An asterisk (*) was incorrectly entered for the manager host names in the non-encryption communication host configuration file for the IM configuration management viewer.

S:

Terminates processing.

O:

Correct the non-encryption communication host configuration file, and then log in again.

To set an asterisk (*) for the manager host names, enter a single asterisk on the line that follows [NO_SSL_HOST]. Note that if you enter an asterisk (*), communication with all manager hosts will be in the clear (will not be encrypted).

KNAN20137-E

A manager host name in the non-encryption communication host settings file is duplicated. (line number = line-number, file = file-name)

A manager host name is duplicated in the non-encryption communication host configuration file for the IM configuration management viewer.

S:

Terminates processing.

O:

Correct the manager host name on the specified line in the non-encryption communication host configuration file, and then log in again.

KNAN20141-E

An error occurred during the initialization of the communication encryption function for CF - View for the base manager. (cause = cause, directory = directory-name)

An error occurred during initialization of the communication encryption function for the IM configuration management viewer on the base manager.

S:

Terminates processing.

O:

Check the following items:

If No root authentication certificates were found. is displayed for cause, check if there is a root certificate, and then log in again:

• If there is a root certificate, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• If there is no root certificate, create a root certificate.

If None of the root authentication certificates could be read. is displayed for cause, check the following items, and then log in again:

• Check if there is a root certificate. If there is a root certificate, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• Verify that there is no problem in the root certificate file.

• Check the Windows event log to see if a shortage has occurred in an OS resource such as file descriptors.

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If The placement directory for root authentication certificates could not be found. is displayed for cause, create a directory for storing root certificates, and then place the root certificate.

KNAN20142-E

Failed to encrypt communications by using the communication encryption function for CF - View for the base manager. (host name of connection destination = connection-target-host-name, cause = cause)

An attempt to establish encrypted communication with the target host has failed.

S:

Terminates processing.

O:

Check the following items:

If The CN or SAN of the server authentication certificate does not match with the host name of the connection destination. is displayed for cause, verify that the CN or SAN in the server certificate of the connection-target manager host matches the connection-target host name in the IM configuration management viewer of the base manager, and then log in again.

If A communication error occurred. is displayed for cause, check the items listed below, and then log in again. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

• Verify that the communication encryption function is enabled on the connection-target manager host. If the communication encryption function is enabled, verify that the non-encryption communication host configuration file does not contain the connection-target manager host name.

• Check if the message Failed to read some of the root authentication certificates was output to the integrated trace log. If this message has been output, take the corrective action given for that message.

• Check if the root certificate corresponding to the server certificate of the connection-target manager host has been placed in JP1/IM - View. If the root certificate has not been placed, place the root certificate.

• Check if the server certificate of the connection-target manager host has expired. If it has expired, renew the server certificate.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact the system administrator.

KNAN20143-W

Failed to read some of the root authentication certificates used by the communication encryption function for CF - View for the base manager. (directory = directory-name, file = file-name, file-name, ...)

An attempt to read some of the root certificates that are used by the communication encryption function in the IM configuration management viewer on the base manager has failed.

S:

Ignores the files that could not be imported and continues processing.

O:

Check the items listed below, and then log in again. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

Check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

Check the Windows event log to see if a shortage has occurred in an OS resource such as file descriptors.

Verify that there is no problem in the root certificate files.

KNAN20144-W

The root authentication certificate used by the communication encryption function for CF - View for the base manager is no longer valid. (directory = directory-name, file = file-name, file-name, ...)

The root certificate used by the communication encryption function in the IM configuration management viewer on the base manager has expired.

S:

Continues processing.

O:

Check whether operating with an expired root certificate will cause a problem. If it will, update the root certificate.

KNAN20151-E

A non-encryption communication host configuration file for CF - View for the base manager was not found. (file = file-name)

There is no non-encryption communication host configuration file for the IM configuration management viewer on the base manager.

S:

Terminates processing.

O:

Check the following items, and then log in again:

Check if there is a non-encryption communication host configuration file. If there is no non-encryption communication host configuration file, create it.

Check whether you have read permission for the non-encryption communication host configuration file. If not, set read permission for the file.

KNAN20152-E

The non-encryption communication host configuration file for CF - View for the base manager failed to load. (file = file-name)

An attempt to load the non-encryption communication host configuration file for the IM configuration management viewer on the base manager has failed.

S:

Terminates processing.

O:

Check the Windows event log to see if there is any shortage of an OS resource such as file descriptors.

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KNAN20153-E

The first line of the non-encryption communication host configuration file for CF - View for the base manager is not "[NO_SSL_HOST]". (file = file-name)

[NO_SSL_HOST] is not on the first line of a non-encryption communication host configuration file for the IM configuration management viewer on the base manager.

S:

Terminates processing.

O:

Enter [NO_SSL_HOST] on the first line of the non-encryption communication host configuration file, and then log in again.

KNAN20154-E

The number of manager host names specified in the non-encryption communication host configuration file for CF - View for the base manager exceeds the maximum (maximum-value). (file = file-name)

The number of manager hosts in the non-encryption communication host configuration file for the IM configuration management viewer on the base manager exceeds the maximum value.

S:

Terminates processing.

O:

Check the number of manager hosts in the non-encryption communication host configuration file and correct it. Then, log in again.

KNAN20155-E

The length of a manager host name specified in the non-encryption communication host configuration file for CF - View for the base manager exceeds the maximum (maximum-value). (line number = line-number, file = file-name)

The length of a manager host name specified in the non-encryption communication host configuration file for the IM configuration management viewer on the base manager exceeds the maximum value.

S:

Terminates processing.

O:

Correct the manager host name on the corresponding line in the non-encryption communication host configuration file, and then log in again.

KNAN20156-E

The syntax for asterisks (*) in the manager host name for the non-encryption communication host configuration file for CF - View for the base manager is invalid. (file = file-name)

An asterisk (*) was incorrectly entered for the manager host names in the non-encryption communication host configuration file for the IM configuration management viewer on the base manager.

S:

Terminates processing.

O:

Correct the non-encryption communication host configuration file, and then log in again.

To set an asterisk (*) for the manager host names, enter a single asterisk on the line that follows [NO_SSL_HOST].

Note that if you enter an asterisk (*), communication with all manager hosts will be in the clear (will not be encrypted).

KNAN20157-E

A manager host name in the non-encryption communication host settings file is duplicated. (line number = line-number, file = file-name)

A manager host name is duplicated in the non-encryption communication host configuration file for the IM configuration management viewer on the base manager.

S:

Terminates processing.

O:

Correct the manager host name on the specified line in the non-encryption communication host configuration file, and then log in again.

KNAN20200-E

The option "option" is invalid.

An invalid option was specified.

S:

Suspends processing.

O:

Specify the option correctly.

KNAN20201-E

The option "option" is duplicated.

Specification of the option was duplicated.

S:

Suspends processing.

O:

Specify the option correctly.

KNAN20202-E

Specify the value argument after the option "option".

The command cannot be executed because no argument value was specified after the displayed option.

S:

Suspends processing.

O:

Specify an argument value after the displayed option.

KNAN20203-E

The argument value of the option "option" includes an unusable character.

The argument value of the option includes an unusable character.

S:

Suspends processing.

O:

Specify the argument value correctly.

KNAN20204-E

The value specified in the argument of the option "option" exceeds the maximum value of maximum-value bytes.

The value specified in the argument value of the option exceeds the maximum length that can be specified.

S:

Suspends processing.

O:

Specify the argument value correctly.

KNAN20205-E

If you specify a password, also specify a host name and user name.

If you specify a password, you must also specify a host name and user name.

S:

Suspends processing.

O:

If a password is specified, also specify a host name and user name.

KNAN20206-E

The product information could not be acquired because there was not enough memory.

Detailed information: function-name, return-value

The product information could not be acquired because there were insufficient resources.

S:

Suspends processing.

O:

Make sure that there are sufficient system resources.

Eliminate any resource insufficiency, and then retry the operation.

If this method cannot resolve the issue, use the data collection tool to collect data, and then contact a system administrator.

KNAN20207-E

The product information could not be acquired because the environment is invalid.

Detailed information: function-name, return-value

The product information could not be acquired because the environment is invalid.

S:

Suspends processing.

O:

Determine whether a failure occurred in the system.

If a failure did not occur in the system, uninstall and then re-install IM Configuration Management - View, and then retry the operation.

If this method cannot resolve the issue, use the data collection tool to collect data, and then contact a system administrator.

KNAN20220-Q

Are you sure you want to log out?

Confirms that you want to log out.

O:

Click the Yes button to log out. Click the No button if you do not want to log out.

KNAN20221-Q

Do you want to delete the selected host?

Confirms that you want to delete the selected host.

O:

Click the Yes button to delete the selected host. Click the No button if you do not want to delete the selected host.

KNAN20222-Q

Do you want to collect the host information of the selected host?

When the host is included in the agent configuration, the profile list on the server is deleted.

Confirms that you want to collect the host information of the selected host.

If the host is included in the agent configuration, the profile list in the agent configuration will be deleted because the product information is updated by collecting host information. Retry collecting the profile information in batch, or open the Display/Edit Profiles window and then acquire the profile list.

O:

Click the Yes button to collect the host information of the selected host. Click the No button if you do not want to collect the host information of the selected host.

KNAN20223-Q

Do you want to acquire the IM configuration applied in the current system?

Acquiring the IM configuration will update the IM configuration on the server to the latest information.

Confirms that you want to apply the IM configuration (system hierarchy).

O:

Click the Yes button to acquire the IM configuration (system hierarchy). Click the No button if you do not want to acquire the IM configuration (system hierarchy).

KNAN20224-Q

Do you want to synchronize the IM configuration?

Synchronizing the IM configuration integrates separately created IM configurations.

Confirms that you want to synchronize the IM configuration (system hierarchy).

O:

Click the Yes button to synchronize the IM configuration (system hierarchy). Click the No button if you do not want to synchronize the IM configuration (system hierarchy).

KNAN20225-Q

Do you want to verify the IM configuration?

Verification of the IM configuration checks whether the IM configuration information set for each host in the IM configuration matches the IM configuration information on the server.

Confirms that you want to verify the IM configuration (system hierarchy).

O:

Click the Yes button to verify the IM configuration (system hierarchy). Click the No button if you do not want to verify the IM configuration (system hierarchy).

KNAN20226-Q

Do you want to perform a batch collection of the profile information?

This function collects the profile information of all hosts in the agent configuration.

Confirms that you want to perform a batch collection of the profile information.

O:

Click the Yes button to perform a batch collection of the profile information. Click the No button if you do not want to perform a batch collection of the profile information.

KNAN20227-Q

The configuration file will be applied to all hosts in the agent configuration. The date of the configuration files on the hosts will not be confirmed.

Do you want to continue?

Confirms that you want all of the profile information to be applied.

O:

Click the Yes button to have all of the profile information applied. Click the No button if you do not want to have all of the profile information applied.

KNAN20228-E

Startup of View of the base manager (host-name) failed.

Please confirm the following and then try again:

- IM-CF is set up in the base manager host.

- The service of the IM-CF server (jcfmain) has started on the base manager host.

- Login to the base manager host is possible with the currently logged in user name and password.

Startup of the site manager's IM Configuration Management - View failed.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Is IM Configuration Management set up on the site manager host?

Has IM Configuration Management Service (jcfmain) started on the site manager host?

Is login allowed with the user name and password currently logged in to the site manager host?

If the communication encryption function is enabled on the base manager, have encrypted communication settings been specified in JP1/IM - View?

KNAN20230-Q

Agent configuration does not exist. Do you want to delete the agent configuration maintained in the Server?

The agent configuration does not exist.

S:

Continues processing.

O:

Click the Yes button to delete the agent configuration on the server.

Click the No button if you do not want to delete the agent configuration on the server.

KNAN20231-Q

Do you want to collect the virtual machine configuration of Related system type from the selected host? Processing takes a long time when information for many guest OSs is collected.

This message confirms that you want to collect the virtualization configuration.

S:

Continues processing.

O:

Click the Yes button to collect the virtualization configuration. Click the No button if you do not want to collect the virtualization configuration.

KNAN20232-Q

Do you want to batch collect all virtualization configurations?

This message confirms that you want to collect virtualization configurations in batch.

S:

Continues processing.

O:

Click the Yes button to collect virtualization configurations in batch. Click the No button if you do not want to collect virtualization configurations in batch.

KNAN20233-Q

Do you want to apply the virtualization configuration to the Central Scope monitoring tree?

This message confirms that you want to apply the virtualization configuration to the central scope monitoring tree.

S:

Continues processing.

O:

Click the Yes button to apply the virtualization configuration to the central scope monitoring tree. Click the No button if you do not want to apply the virtualization configuration to the central scope monitoring tree.

KNAN20234-I

The virtualization configuration was applied successfully to the Central Scope monitoring tree.

The virtualization configuration was applied to the central scope monitoring tree.

KNAN20238-Q

Do you want to collect the host information from the host during selection?

If the host information is collected, all the remote monitoring operated by the host during selected is stopped.

This message confirms that you want to collect host information from the selected host.

O:

Click the Yes button to collect host information.

Click the No button if you do not want to collect host information.

KNAN20240-Q

Are you sure you want to forced terminate the application?

This message confirms that you want to forcibly terminate IM Configuration Management - View.

O:

Click the Yes button to forcibly terminate IM Configuration Management - View. The operation being processed is not canceled.

Click the No button if you do not want to terminate IM Configuration Management - View.

KNAN20241-Q

Do you want to collect host information from the selected host?

If the host is included in the agent configuration, the profile list on the server will be deleted.

If the host is included in the remote monitoring configuration, all remote monitoring on the selected host will stop.

This message confirms that you want to collect host information from the selected host.

O:

Click the Yes button to collect the host information of the selected host.

Click the No button if you do not want to collect the host information of the selected host.

KNAN20242-Q

Do you want to collect host information from the selected host?

If the host is included in the agent configuration, the profile list on the server will be deleted.

If the host is included in the remote monitoring configuration, all remote monitoring on the selected host might stop depending on the results of host information collection.

This message confirms that you want to collect host information from the selected host.

O:

Click the Yes button to collect the host information of the selected host.

Click the No button if you do not want to collect the host information of the selected host.

KNAN20300-E

primary-host and standby-host are the same. Specify different hosts, and then try again.

The primary host and the standby host are the same.

S:

Returns to the input window.

O:

Set the primary host and the standby host to different hosts, and then retry the operation.

KNAN20301-Q

If you change the host type, the virtualization configuration information will be deleted.

Do you want to change the host type?

This message confirms that you want to change the host type.

O:

Click the Yes button to delete the virtualization configuration information. Click the No button if you do not want to delete the virtualization configuration information.

KNAN20302-Q

The host name contains invalid characters. Some functions might be unusable.

Do you want to continue?

This message confirms that you want to register a host name containing invalid characters.

S:

Continues processing.

O:

Click the Yes button to register the host.

Click the No button if you do not want to register the host.

KNAN20303-E

The JP1 event that occurred during distribution of the agent configuration might not have been transferred.

Do you want to reflect the IM configuration?

You cannot change the remote communication type because remote monitoring is running on the selected host.

S:

Returns to the input window.

O:

Stop remote log monitoring and remove event log monitoring, and then retry the operation.

KNAN20320-Q

A configuration file is being edited.

Are you sure you want to close the profile window?

Confirms that you want to close the Display/Edit Profiles window.

O:

Click the Yes button to close the Display/Edit Profiles window. Click the No button if you do not want to close the Display/Edit Profiles window.

KNAN20321-Q

Do you want to save the contents of the configuration file being edited to the server?

Even if the configuration file is saved, it will not be applied to product-name of the host "host-name".

Confirms that you want to save the configuration file to the server.

O:

Click the Yes button to save the configuration file to the server. Click the No button if you do not want to save the configuration file to the server.

KNAN20322-Q

Do you want to apply the configuration file to product-name of the host "host-name"?

Confirms that you want to apply the configuration file.

O:

Click the Yes button to apply the configuration file. Click the No button if you do not want to apply the configuration file.

KNAN20323-Q

Do you want to collect the profile profile-name for product-name of the host "host-name"?

Collecting the profile information updates the contents of the configuration file in the server to the latest information.

Confirms that you want to collect the profile information.

O:

Click the Yes button to collect the profile information. Click the No button if you do not want to collect the profile information.

KNAN20324-I

The configuration file of the profile profile-name for product-name of the host "host-name" was successfully saved in the server.

The configuration file was saved in the server.

KNAN20325-I

The configuration file of the profile profile-name for product-name was successfully applied to the host "host-name".

The configuration file was applied in the host.

KNAN20326-Q

Do you want to rebuild the profile tree of product-name of the host "host-name"?

When the profile tree is updated, the profiles on the server are deleted, and then the profile tree is collected from the hosts.

The profiles of services that are not operated in the current agent host cannot be managed.

Confirms that you want to rebuild the profile tree.

O:

Click the Yes button to rebuild the profile tree. Click the No button if you do not want to rebuild the profile tree.

KNAN20329-Q

The configuration file of the profile profile-name has not been saved.

All changes will be lost. Do you want to continue?

Confirms that you want processing to continue.

O:

Click the Yes button to continue processing. Click the No button if you do not want to continue processing.

KNAN20330-E

The host (host-name) does not support individual collection of profile information.

Please execute the profile batch collection item from the main window.

The host does not support individual collection of profile information.

S:

Suspends processing.

O:

Collect the profile information in batch from the IM Configuration Management window.

KNAN20331-E

The selected configuration file does not exist on the server. Please execute the profile batch collection item from the main window.

The configuration file does not exist on the server.

S:

Suspends processing.

O:

Collect the profile information in batch from the IM Configuration Management window.

KNAN20333-I

Setup file does not exist in agent host.

The configuration file does not exist in the agent host.

S:

Suspends processing.

O:

Make sure that the configuration file exists in the host.

KNAN20352-Q

Do you want to delete the selected log file trap from the profile list?

This message confirms that you want to delete the log file trap settings file from the profile list.

O:

Click the Yes button to delete the log file trap settings file.

Click the No button if you do not want to delete the log file trap settings file.

KNAN20353-I

The log file trap of monitoring-target-name for product-name was successfully deleted from IM Configuration Management.

The log file trap settings file was deleted from the server.

KNAN20354-Q

Do you want to stop the selected log file trap?

This message confirms that you want to stop the log file trap.

O:

Click the Yes button to stop the log file trap.

Click the No button if you do not want to stop the log file trap.

KNAN20355-Q

The configuration file "file-path" on the agent host "host-name" already exists.

Do you want to overwrite the file on the agent host?

This message confirms that you want to overwrite the configuration file on the agent host.

O:

Click the Yes button to overwrite the configuration file on the agent host.

Click the No button to cancel applying the configuration file.

KNAN20356-I

The log file trap of monitoring-target-name for product-name on the host "host-name" was successfully stopped.

The configuration file process on the agent stopped.

KNAN20357-E

An attempt to add the log file trap for monitoring-target-name failed. (Details = Details)

An attempt to add the log file trap failed due to one the following causes:

An attempt to add the configuration file failed.

A log file trap with the same monitoring target name already exists.

A log file trap with the same file name already exists.

The number of profiles for the log file trap exceeds the maximum.

S:

Cancel adding of the log file trap.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

An attempt to add the configuration file file-name from IM Configuration Management failed.

Check the following items, and then retry the operation.

• Have the access permissions for the path indicated in the message been changed?

• Is there sufficient disk space?

A log file trap with the same monitoring target name "monitoring-target-name" already exists.

Change the monitoring target name, and then retry adding the log file trap.

A log file trap with the same file name "file-name" already exists.

The number of log file trap profiles has reached the maximum limit.

Delete log file traps that are no longer required.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator

KNAN20358-Q

The path of the configuration file on the agent host "configuration-file-path" is different from the path saved in IM Configuration Management "configuration-file-path".

The processes will be stopped, and then the file on the agent host "configuration-file-path" will be deleted.

Do you want to continue?

This message appears if the path of the configuration file used on the agent host is different from the path saved in IM Configuration Management.

O:

The path of the configuration file on the agent host is different from the path that was saved when IM Configuration Management agent collected the profile.

Make sure that the profile managed by IM Configuration Management is not changed on the agent host.

Click the Yes button to stop the process and delete the configuration file that has the path saved in IM Configuration Management from the agent host.

Click the No button to cancel processing.

KNAN20359-Q

The path of the configuration file on the agent host "configuration-file-path" is different from the path saved in IM Configuration Management "configuration-file-path".

A new file "configuration-file-path" will be used.

Do you want to continue?

This message appears if the path of the configuration file used on the agent host is different from the path saved in IM Configuration Management.

O:

The path of the configuration file on the agent host is different from the path that was saved when IM Configuration Management agent collected the profile.

Make sure that the profile managed by IM Configuration Management is not changed on the agent host.

Click the Yes button to apply the configuration file to the path saved in IM Configuration Management, and then restart the log file trap.

Click the No button to cancel processing.

KNAN20360-E

The path of the agent host configuration file "file-path" differs from the path saved in IM Configuration Management "file-path".

This message appears if the path of the configuration file used on the agent host is different from the path saved in IM Configuration Management.

S:

Cancels reloading the log file trap.

O:

The path of the configuration file on the agent host is different from the path that was saved when IM Configuration Management agent collected the profile.

If this message is output, take the following actions.

Restart the log file trap to apply the setting. When the log file trap restarts, the KNAN20359-Q message appears.

Rebuild the profile tree and acquire the latest profile. Note, however, that the contents of any profiles that have not been applied are aborted.

KNAN20362-Q

Do you want to start the selected log file trap?

This message confirms that you want to start the log file trap.

O:

Click the Yes button to start the log file trap.

Click the No button if you do not want to start the log file trap.

KNAN20363-I

The log file trap of monitoring-target-name for product-name on the host "host-name" was started successfully.

The log file trap on the agent has started.

KNAN20364-I

The event-log trap for event-log trap on the host host-name was successfully started.

The event log trap on the host has started.

KNAN20365-I

The event-log trap for event-log trap on the host host-name was successfully stopped.

The event log trap on the host has stopped.

KNAN20400-Q

Do you want to replace the IM configuration information being edited?

Confirms that you want the existing IM configuration information (system hierarchy information) to be overwritten by the contents being edited.

O:

Click the Yes button to overwrite with the IM configuration information (system hierarchy information) being edited. Click the No button if you do not want to overwrite with the IM configuration information (system hierarchy information) being edited.

KNAN20401-Q

The read IM configuration information includes one or more hosts that are not registered in the host list. In order to continue, unregistered hosts must be registered in the host list.

Do you want to add the unregistered hosts to the host list?

Confirms that you want to add the unregistered hosts to the host list.

O:

Click the Yes button to add the unregistered hosts to the host list. Click the No button if you do not want to add the unregistered hosts to the host list and instead want to suspend reading of the file.

KNAN20402-E

The syntax of the IM configuration information in the specified file is invalid.

File name = file-name

Line number = line-number

Details = detailed-information

There is a syntax error in the file being read.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action, and then retry the operation.

Parentheses are not supported.

Remove the parentheses.

Unusable characters are being used.

Make sure that the following characters are not being used:

/, :, ?, \", <, >, |, \\, *

The host name is too long.

Specify the host name so that it does not exceed the maximum length.

An upper host has not been specified.

Define a host above the agent.

A manager host does not exist.

Make sure that the manager host is correctly defined.

The same host has been specified multiple times.

Specify a host only once.

The file is empty.

Define the IM configuration information (system hierarchy information).

The IM configuration of Base Manager is invalid.

Make sure that the IM configuration (system hierarchy information) of the site manager is correctly defined.

KNAN20403-Q

The IM configuration being edited has not been applied to the system.

Do you want to close the window for editing the IM configuration?

Confirms that you want to close the IM Configuration Management window.

O:

Click the Yes button to close the IM Configuration Management window. Click the No button if you do not want to close the IM Configuration Management window.

KNAN20404-Q

When the IM configuration is applied to the system, the existing configuration is deleted, and then the new configuration is distributed.

All of the hosts defined in the IM configuration must be running.

Do you want to apply the IM configuration?

This message confirms that you want to apply the IM configuration information (system hierarchy information) to the system.

O:

Click the Yes button to apply the IM configuration information (system hierarchy information) to the system. Click the No button if you do not want to apply the IM configuration information (system hierarchy information) to the system.

KNAN20405-Q

In order to change the base manager, lower level hosts must be deleted.

Do you want to delete the lower level hosts?

Confirms that you want to delete lower level hosts to change to the site manager.

O:

Click the Yes button to delete the lower level hosts and change to the site manager. Click the No button if you do not want to delete the lower level hosts and change to the site manager.

KNAN20407-I

The latest configuration will be acquired because the IM configuration has been changed.

The update operation ended normally.

KNAN20408-I

The IM configuration was successfully saved.

The IM configuration (system hierarchy information) was saved.

KNAN20409-E

The selected node cannot be moved to its own child node.

The selected host cannot be moved to a lower level to the specified host.

S:

Suspends processing.

O:

Specify a host other than a lower level host as the move destination.

KNAN20410-Q

Do you want to delete the selected node?

Confirms that you want to delete the specified host.

O:

Click the Yes button to delete the host. Click the No button if you do not want to delete the host.

KNAN20411-E

The selected node cannot be moved to itself.

The host cannot be moved to itself.

S:

Suspends processing.

O:

Specify a host other than the move source as the move destination.

KNAN20412-E

Host exchange for the host (host-name) failed.

Please confirm the following and then try again:

- The host is registered.

- The host does not exist in the IM configuration.

Host exchange failed.

Check the following items, and then retry the operation:

Has a host name that is not registered in Host after the exchange been entered?

Has a host name that is not included in the system hierarchy been entered in Host after the exchange?

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Has the host been registered?

Is the host included in the IM configuration (system hierarchy)?

KNAN20413-I

The IM configuration tree has unregistered host (host-name). Please register and perform [Update to latest host information] to continue.

One of the hosts in the host list was renamed or deleted while the IM Configuration Management window was being displayed.

KNAN20414-I

The host (host-name) is unregistered. Please register and perform [Update to latest host information] to continue.

After the IM Configuration Management window was updated to the most recent information, a renamed or deleted host was added.

KNAN20415-I

The host (host-name) in the IM configuration tree does not exist in the host list information. Please perform [Update to latest host information] to continue.

A host was newly registered and IM configuration acquisition was executed without updating the IM Configuration Management window to the most recent information.

KNAN20416-Q

The host name contains invalid characters. Some functions might be unusable.

Host name:host-name

Do you want to continue?

This message confirms that you want to register a host name containing invalid characters.

S:

Continues processing.

O:

Click the Yes button to register the host. Click the No button if you do not want to use the file that was read.

KNAN20418-Q

Do you want to replace the agent configuration being edited?

This message confirms that you want to discard the agent configuration that is being edited.

O:

Click the Yes button to replace the agent configuration that is being edited.

Click the No button if you do not want to replace the agent configuration that is being edited.

KNAN20419-Q

Do you want to replace the remote monitoring configuration being edited?

This message confirms that you want to discard the remote monitoring configuration that is being edited.

O:

Click the Yes button to replace the remote monitoring configuration that is being edited.

Click the No button if you do not want to replace the remote monitoring configuration that is being edited.

KNAN20420-Q

The agent configuration includes one or more hosts that are not registered in the host list.

To continue, unregistered hosts must be registered in the host list.

Do you want to add the unregistered hosts to the host list?

This message confirms that you want to register unregistered hosts in the host list.

O:

Click the Yes button to register unregistered hosts in the host list.

Click the No button to cancel reading of the file without registering unregistered hosts in the host list.

KNAN20421-Q

The remote monitoring configuration includes one or more hosts that are not registered in the host list.

To continue, unregistered hosts must be registered in the host list.

Do you want to add the unregistered hosts to the host list?

This message confirms that you want to register unregistered hosts in the host list.

O:

Click the Yes button to register unregistered hosts in the host list.

Click the No button to cancel reading of the file without registering unregistered hosts in the host list.

KNAN20422-E

The syntax of the agent configuration in the specified file is invalid.

File name: file-name

Line number: line-number

Details: details

A syntax error occurred in the file that was read.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action, and then retry the operation.

Parentheses are not supported.

Delete the parentheses.

An included character is invalid.

Check whether any of the following invalid characters were entered:

/ : ? \" < > | \\ *

The host name is too long.

Specify a host name that is not greater than the maximum length.

An upper host has not been specified.

Define the host at a higher level than the agent.

A manager host does not exist.

Make sure that the manager host is defined correctly.

The same host has been specified multiple times.

Specify only one host.

The file is empty.

Define configuration information (agent configuration or remote monitoring configuration).

The IM configuration of Base Manager is invalid.

Make sure that the agent configuration (system hierarchy information) for the site manager is defined correctly.

KNAN20423-E

The syntax of the remote monitoring configuration in the specified file is invalid.

File name: file-name

Line number: line-number

Details: details

This message confirms that you want to close the Edit Agent Configuration window.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action, and then retry the operation.

Parentheses are not supported.

Delete the parentheses.

An included character is invalid.

Check whether any of the following invalid characters were entered:

/ : ? \" < > | \\ *

The host name is too long.

Specify a host name that is not greater than the maximum length.

An upper host has not been specified.

Define the host at a higher level of the agent.

A manager host does not exist.

Make sure that the manager host is defined correctly.

The same host has been specified multiple times.

Specify only one host.

The file is empty.

Define configuration information (agent configuration or remote monitoring configuration).

KNAN20424-Q

The agent configuration has not been applied.

Are you sure you want to close the window for editing the agent configuration?

This message confirms that you want to close the Edit Agent Configuration window.

O:

Click the Yes button to close the Edit Agent Configuration window. Click the No button if you do not want to close the Edit Agent Configuration window.

KNAN20425-Q

The remote monitoring configuration has not been applied.

Are you sure you want to close the window for editing the remote monitoring configuration?

This message confirms that you want to close the Edit Remote Monitoring Configuration window.

O:

Click the Yes button to close the Edit Remote Monitoring Configuration window. Click the No button if you do not want to close the Edit Remote Monitoring Configuration window.

KNAN20426-I

The agent configuration was saved.

The agent configuration was saved.

KNAN20427-I

The remote monitoring configuration was saved.

The remote monitoring configuration was saved.

KNAN20428-I

An unregistered host "host-name" exists in the agent configuration.

Register the host, and then update the information in the window for editing the agent configuration.

A host in the host list was renamed or deleted while the Edit Agent Configuration window was open.

O:

Register the host, and then refresh the Edit Agent Configuration window.

KNAN20429-I

An unregistered host "host-name" exists in the remote monitoring configuration.

Register the host, and then update the information in the window for editing the remote monitoring configuration.

A host in the host list was renamed or deleted while the Edit Remote Monitoring Configuration window was open.

O:

Register the host, and then refresh the Edit Remote Monitoring Configuration window.

KNAN20430-I

A host "host-name" in the agent configuration does not exist in the host list.

Update the information in the window for editing the agent configuration.

A new host was registered, and IM configuration acquisition was performed without refreshing the Edit Agent Configuration window.

O:

Register the host, and then refresh the Edit Agent Configuration window.

KNAN20431-I

A host "host-name" in the remote monitoring configuration does not exist in the host list.

Update the information in the window for editing the remote monitoring configuration.

A new host was registered, and IM configuration acquisition was performed without refreshing the Edit Remote Monitoring Configuration window.

O:

Register the host, and then refresh the Edit Remote Monitoring Configuration window.

KNAN20432-E

Reflection of the agent configuration has failed.

Details: details

An attempt to apply the agent configuration failed.

S:

Suspends processing.

O:

Perform either of the following.

A host that is not a connection-destination host has been specified for the top-level host

Change the highest-level host to the connected host.

Unregistered hosts exist in the agent configuration.

Make sure that the host is registered.

KNAN20433-E

Reflection of the remote monitoring configuration has failed.

Details: details

An attempt to apply the remote monitoring configuration failed.

S:

Suspends processing.

O:

Perform either of the following.

A host that is not a connection-destination host has been specified for the top-level host

Change the highest-level host to the connected host.

Unregistered hosts exist in the remote monitoring configuration.

Make sure that the host is registered.

KNAN20437-Q

When an agent configuration is reflected in the system, the existing agent configuration is deleted, and the new configuration is distributed.

All hosts that are defined in the existing agent configuration must be running.

All hosts that are defined in the new agent configuration must be running.

The JP1 event that occurred during distribution of the agent configuration might not have been transferred.

When a host is removed from an agent configuration, the profile list on the server is deleted.

Do you want to reflect the agent configuration in the IM configuration?

This message confirms that you want to apply the agent configuration.

O:

Click the Yes button to apply the agent configuration.

Click the No button if you do not want to apply the agent configuration.

KNAN20438-Q

When a host is deleted from a remote monitoring configuration, all remote monitoring for that host is stopped, and the profile is deleted.

Do you want to reflect the agent configuration into the IM configuration?

This message confirms that you want to apply the remote monitoring configuration.

O:

Click the Yes button to apply the remote monitoring configuration.

Click the No button if you do not want to apply the remote monitoring configuration.

KNAN20440-Q

When an agent configuration is reflected in the system, all hosts that are defined in the agent configuration must be running.

When a host is removed from an agent configuration, the profile list on the server is deleted.

Do you want to reflect the agent configuration in the IM configuration?

O:

Click the Yes button to apply the agent configuration to the IM configuration.

Click the No button if you do not want to apply the agent configuration to the IM configuration.

KNAN20441-Q

When an agent configuration is reflected in the system, all target hosts to be changed, and their higher-level manager hosts, must be running.

When a host is removed from an agent configuration, the profile list on the server is deleted.

Do you want to reflect the agent configuration in the IM configuration?

This message confirms that you want to apply the agent configuration.

A host for which the agent configuration is to be changed is a host that was added to or removed from the agent configuration definition.

O:

Click the Yes button to apply the agent configuration to the IM configuration.

Click the No button if you do not want to apply the agent configuration to the IM configuration.

KNAN20480-Q

Do you want to read the file "file-name"?

Confirms that you want to read the file.

O:

Click the Yes button to read the file. Click the No button if you do not want to read the file.

KNAN20481-Q

Do you want to save the file "file-name"?

Confirms that you want to save the file.

O:

Click the Yes button to save the file. Click the No button if you do not want to save the file.

KNAN20482-Q

Do you want to overwrite the file "file-name"?

Confirms that you want to overwrite the file.

O:

Click the Yes button to overwrite the file. Click the No button if you do not want to overwrite the file.

KNAN20483-E

An attempt to read data-name failed.

File name: file-name

An attempt to read the file failed.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Does the file exist?

Has the file access permission been set correctly?

Has the file been opened (locked) by another application?

KNAN20484-E

An attempt to save data-name failed.

File name: file-name

An attempt to save the file failed.

S:

Suspends processing.

O:

Check the following items, and then retry the operation:

Is the disk space sufficient?

Is there sufficient memory?

Are the resources sufficient?

Does the file exist?

Has the file access permission been set correctly?

Has the file been opened (locked) by another application?

If this method cannot resolve the issue, use the data collection tool to collect data, and then contact a system administrator.

KNAN20500-Q

Do you want to forcibly release the exclusive edit status of the selected user?

If the exclusive edit status is forcibly released, data being edited might be lost.

Confirms that you want to forcibly release exclusive edit status.

O:

Click the Yes button to forcibly release exclusive edit status. Click the No button if you do not want to forcibly release exclusive edit status.

KNAN20510-I

process completed.

The process finished.

KNAN20513-Q

Do you want to interrupt process?

Confirms that you want to interrupt the process.

O:

Click the Yes button to interrupt the process. Click the No button if you do not want to interrupt the process.

KNAN20514-I

Processing to interrupt process completed.

Processing to interrupt the process finished.

KNAN20515-Q

The window for displaying execution results will close. Is this OK?

Confirms that you want to close the window.

O:

Click the Yes button to close the Execution Results window. Click the No button if you do not want to close the Action Log window.

KNAN20516-I

process cannot be interrupted because it has already completed.

The process cannot be interrupted because it has already finished.

KNAN20520-I

process. Please wait...

The process is currently communicating with the server.

O:

Wait until the server processing finishes.

KNAN20530-W

The topmost host is not a connection destination host.

If the topmost host is not a connection destination host, an error will occur when the IM configuration is applied.

Do you want to exchange hosts as specified?

The specified host is not the host connected to the highest-level host.

S:

Continues processing.

O:

Click the Yes button to continue host exchange. Click the No button to stop host exchange.

KNAN20800-E

Command execution failed.

Detailed information : API-name, error-code

Command execution failed.

S:

Suspends command execution.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN20801-E

Command execution failed. (detail code = detail-code)

Command execution failed.

S:

Suspends command execution.

O:

Check the following items, and then retry the operation:

Is the disk space sufficient?

Is there sufficient memory?

KNAN20802-E

Please execute the command from an administrator console.

This command must be executed from an administrator console.

S:

Suspends command execution.

O:

Re-execute the command from an administrator console.

KNAN20803-E

Command execution failed because the user does not have execution permission.

Command execution failed because the user does not have execution permission.

S:

Suspends command execution.

O:

Log in as a user with Administrator permissions, and then execute the command.

KNAN20810-I

A thread dump output request was sent.

A thread dump output request communication was completed.

S:

Terminates the command normally.

KNAN20811-E

Please specify the process ID and then try again.

The process ID was not specified.

S:

Suspends command execution.

O:

Specify the process ID, and then re-execute the command.

KNAN20812-E

Multiple process IDs were specified. Please correct the argument and then try again.

Multiple process IDs were specified.

S:

Suspends command execution.

O:

Specify a single process ID, and then re-execute the command.

KNAN20813-E

The specified process ID was invalid. Please correct the argument and then try again.

The process ID value is invalid.

S:

Suspends command execution.

O:

Make sure that the process ID is specified correctly, and then re-execute the command.

KNAN20814-E

Please specify the process ID of the IM configuration management/viewer and then try again.

The process ID of IM Configuration Management - View was not specified.

S:

Suspends command execution.

O:

Specify the process ID of IM Configuration Management - View.

KNAN20815-E

The jcfview process of the IM configuration management viewer is not running.

The jcfview process of IM Configuration Management - View is not running.

S:

Suspends command execution.

O:

Make sure that IM Configuration Management - View is running. Also make sure that the jcfview process (jcfview.exe) of IM Configuration Management - View is running.

KNAN20816-E

Transmission of a thread dump output request failed.

Transmission of a thread dump output request failed.

S:

Suspends command execution.

O:

Make sure that the jcfview_evt process (jcfview_evt.exe) of IM Configuration Management - View is running.

KNAN20820-I

Setup terminated normally.

Setup finished normally.

S:

Terminates the command normally.

KNAN20821-I

Unsetup terminated normally.

Unsetup finished normally.

S:

Terminates the command normally.

KNAN20822-E

An invalid parameter was specified.

An invalid option was specified in a parameter of the jcovcfsetup setup command.

S:

Suspends command execution.

O:

Specify a valid option in the parameter of the jcovcfsetup setup command. The valid options are the following:

For setup processing, specify jcovcfsetup -i or jcovcfsetup.

For unsetup processing, specify jcovcfsetup -u.

KNAN20823-E

Command execution failed because acquisition of JP1/IM - View installation information failed.

Command execution failed because collection of IM Configuration Management - View installation information failed.

S:

Suspends command execution.

O:

Make sure that IM Configuration Management - View was installed correctly, and then retry the operation.

KNAN20824-E

Setup cannot be performed because the shortcut destination does not exist.

The jcovcfsetup setup command cannot add a shortcut because the IM Configuration Management - View program folder does not exist.

S:

Suspends command execution.

O:

Install IM Configuration Management - View, make sure that the position and name of the IM Configuration Management - View menu displayed when you click Start and then Programs have not been changed, and then retry the operation.

KNAN20825-E

Unsetup failed. (Detailed information : API-name, error-code).

Unsetup failed.

S:

Suspends command execution.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN20826-E

Setup failed. (Detailed information : API-name, error-code)

Setup failed.

S:

Suspends command execution.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN21000-E

The number of connections to the server exceeds the maximum value of maximum-number-of-connections.

The number of connections to the server exceeded the maximum.

S:

Suspends processing.

O:

Reduce the number of connections to the server so that there are no more than the maximum.

KNAN21001-E

User authentication failed.

Confirm the specified user name and password, and then try again.

User authentication failed.

S:

Suspends processing.

O:

Check the user name and password, and then retry the operation.

KNAN21002-E

A communication error occurred between the specified connection destination host and authentication server.

Login failed because a connection with the authentication server could not be made.

S:

Suspends processing.

O:

Make sure that there is no error in the setting for the authentication server on the connection destination host.

If the communication encryption function is used, check whether the communication encryption function settings are correct.

KNAN21003-E

A login operation failed.

Login failed.

S:

Suspends processing.

O:

Check the following items, and then log in again.

Was the connected host name input correctly?

Is the port number a usable port?

Has the connected host been started?

Is there a problem communicating with the connected host?

Use the jco_spmd_status command to confirm that the connected host was started.

KNAN21004-E

A communication error occurred between the connected host and the authentication server during logout.

Login failed due to an authentication server access error.

S:

Suspends processing.

O:

Make sure that there is no error in the setting for the authentication server on the connection destination host.

KNAN21005-E

A logout operation failed.

Logout failed.

S:

Suspends processing.

O:

Make sure that there is no error in the setting for the authentication server on the connected host.

KNAN21055-E

Application of the IM configuration failed.

Details: A host that is not a connection-destination host has been specified for the top-level host.

An attempt to apply the IM configuration (system hierarchy) failed because a host other than the host connected to the highest-level host was specified.

S:

Suspends processing.

O:

Specify the host connected to the highest-level host, and then retry the operation.

KNAN21151-E

The collection of profile list is failed.

Get the latest information and confirm whether the host exists.

The host was not found in the IM Configuration Management database.

S:

Suspends processing.

O:

Make sure that the host has been registered, and then retry the operation.

KNAN21154-E

The collection of operation definition information is failed.

Get the latest information and confirm whether the host exists.

The specified host was not found in the host list.

S:

Suspends processing.

O:

Make sure that the host has been registered, and then retry the operation.

KNAN21157-E

The collection of Configuration file content is failed.

Get the latest information and confirm whether the host exists.

The specified host was not found in the host list.

S:

Suspends processing.

O:

Make sure that the host has been registered, and then retry the operation.

KNAN21162-E

Batch collection for the host failed.

Get the latest information and confirm whether the host exists.

Batch collection for the host failed because the specified host does not exist.

S:

Suspends processing.

O:

Make sure that the host has been registered, and then retry the operation.

KNAN21165-E

Application of the configuration files failed.

Update the information, and then confirm whether the host exists.

The specified host was not found in the host list.

S:

Suspends processing.

O:

Make sure that the host has been registered, and then retry the operation.

KNAN21168-E

Batch application of the profiles failed.

Update the information, and then confirm whether the host exists.

The specified host was not found in the host list.

S:

Suspends processing.

O:

Make sure that the host has been registered, and then retry the operation.

KNAN21169-E

Acquisition of exclusive edit rights failed.

Get the latest information and confirm whether the host exists.

Acquisition of exclusive edit rights failed.

S:

Suspends processing.

O:

Make sure that the host has been registered, and then retry the operation.

KNAN21170-W

The configuration file "file name" for profile type on the agent host might have been changed.

Do you want to apply the changes?

The configuration file on the server might be different from the latest configuration file used on the agent host.

The possible causes are as follows:

The configuration file on the agent host was rewritten by another user.

Profile collection was not performed after host information was collected and the collection time of the configuration file was cleared.

An imported configuration file was applied.

S:

When you select Yes

Applies the profile information for the agent.

When you select No

Suspends processing.

O:

Check the contents of the definition file from the agent side, and then continue the update.

KNAN21171-E

Request name cannot be executed.

Details: detailed information

Close all of the Profile Display/Edit windows, apply the IM configuration, and then try again.

The request request-name cannot be executed.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

The specified product is not supported.

Make sure that the JP1/Base version is 09-00 or later.

The IM configuration has not been applied.

Apply the IM configuration (system hierarchy) from the IM Configuration Management window, and then retry the operation.

KNAN21172-E

The request-name cannot be executed because the database was updated.

Please close all the opened profile windows and invoke again after refreshing the main window.

The request request-name cannot be executed.

S:

Suspends processing.

O:

Close all Display/Edit Profiles windows, update the IM Configuration Management window to the most recent information, and then retry the operation.

KNAN21173-E

Saving the configuration file in server is failed.

Get the latest information and confirm whether the host exists.

The configuration file could not be saved on the server.

S:

Suspends processing.

O:

Update the IM Configuration Management window to the most recent information, and then confirm that the host has been registered.

KNAN21174-E

Application of changes failed because an error occurred when moving the configuration file (file-name) for profile-type.

Detail Information: detailed-information

Edited contents might be stored in host (host-name) because rollback of configuration file is also failed.

Changes could not be applied because an attempt to move the configuration file failed.

Another possibility is that an attempt to roll back the configuration file failed because the host version is 08-50 or earlier.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.

Check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent host.

Another session has exclusive rights.

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

The directory does not exist.

Make sure that the directory exists and that it is accessible.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A communication error occurred.

Determine whether the relevant host exists.

If the host exists, make sure that the network is available.

The processing is busy. Please try again.

Wait awhile, and then retry the operation.

A service or process failed to reload.

Make sure that the relevant service or process is running and that the configuration file is correctly formatted.

If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21175-E

The log file trap failed to be applied because an error occurred when the reload command was executed.

Error code: error code. For details, see the description of the jevlogreload command in the JP1/Base manual.

The configuration file "file name" on the host "host name" will be returned to the state it was in after the changes had been made because the configuration file failed to be rolled back.

Application of settings to the log file trap failed because an error occurred during execution of the reload/startup command.

For details, check the JP1/Base manuals (jevlogstart command, jevlogreload command) and refer to the error message for the displayed error code.

Another possibility is that an attempt to roll back the configuration file failed because the host version is 08-50 or earlier.

S:

Suspends processing.

O:

Take the following actions:

Check the details of the error code displayed in the message in the JP1/Base manuals (jevlogstart command, jevlogreload command), and take corrective action.

Confirm that the configuration information is valid, edit the configuration file, and then reload.

KNAN21176-E

Application of changes to the configuration file (file-name) for profile-type failed.

Cause: detailed-information

Edited contents might be stored in host (host-name) because rollback of configuration file also failed.

Changes to the configuration file could not be applied.

Another possibility is that an attempt to roll back the configuration file failed because the host version is 08-50 or earlier.

S:

Suspends processing.

O:

Confirm that the configuration information is valid, edit the configuration file, and then reload.

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

The file name is too long.

Shorten the file name or the path, and then retry the operation.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The configuration file for rollback failed to be created.

Make sure that there is sufficient disk space, memory, or other OS resources.

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status with the acquired host.

There might be a mistake in a configuration file definition, or JP1/Base might not be running properly.

Make sure that the relevant service or process is running and that the configuration file is configured correctly.

If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21177-E

Application of changes to the configuration file (setup-file-name) for of profile-type failed.

Cause: detailed-information

The rollback function of the configuration file is not supported for JP1/Base version of host (host-name).

Edited contents might be stored in host (host-name).

Changes to the configuration file could not be applied.

Another possibility is that an attempt to roll back the configuration file failed because the host version is 08-50 or earlier.

S:

Suspends processing.

O:

Confirm that the configuration information is valid, edit the configuration file, and then reload.

If the following detailed information is displayed, take the indicated corrective action.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The configuration file for rollback failed to be created.

Make sure that there is sufficient disk space, memory, or other OS resources.

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

There might be a mistake in a configuration file definition, or JP1/Base might not be running properly.

Make sure that the relevant service or process is running and that the configuration file is configured correctly.

If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

The file name is too long.

Shorten the file name or the path, and then retry the operation.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21178-E

Application of changes failed for the configuration file (file-name) for profile-type.

Detail Information: detailed-information

Reload with old configuration file is also failed.

An attempt to apply changes to the configuration file failed.

S:

Suspends processing.

O:

Confirm that the configuration information is valid, edit the configuration file, and then reload.

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

The file name is too long.

Shorten the file name or the path, and then retry the operation.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The configuration file for rollback failed to be created.

Make sure that there is sufficient disk space, memory, or other OS resources.

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status with the acquired host.

There might be a mistake in a configuration file definition, or JP1/Base might not be running properly.

Make sure that the relevant service or process is running and that the configuration file is configured correctly.

If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

A service or process failed to reload.

Make sure that the relevant service or process is running and that the configuration file is configured correctly.

If the service or process is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21179-E

The log file trap failed to be applied because an error occurred when the reload command was executed.

Error code: error code

The configuration file, which was rolled back, failed to be reloaded.

Application of settings to the log file trap failed because an error occurred during execution of the reload command.

S:

Suspends processing.

O:

Take one of the following actions:

Refer to the jevlogreload command in the JP1/Base manuals, and check the error code details.

Edit the configuration file with valid configuration information, and then retry the operation.

KNAN21180-E

Application of the log file trap for monitoring-target-name failed.

Details: details

The startup definition file of the host "host-name" has been overwritten by IM Configuration Management because rollback of the startup definition file failed.

An attempt to apply the log file trap failed.

The startup definition file was overwritten by IM Configuration Management because an attempt to roll back the startup definition file failed.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action:

There is no access permission.

Check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent host.

Another session has exclusive rights.

In the Login User List window, check whether the user has acquired exclusive access permission.

If there is no problem, select the check box for the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

The directory does not exist.

Make sure that the specified directory exists and is accessible.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation:

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

A communication error occurred.

Check the condition and status of the network connected to the target host.

Also make sure that JP1/Base is running.

If JP1/Base is not running, take the following actions:

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

The processing is busy. Please try again.

Wait a while, and then retry the operation.

A memory shortage occurred on the manager host.

Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.

Make sure that there is enough free memory on the agent host, and then retry the operation.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

The configuration file for rollbacks failed to be created.

Make sure that there are sufficient OS resources such as disk space and memory.

The data that was acquired while connected to the host is invalid.

Invalid data might have been sent from JP1/Base on the target host.

Make sure that JP1/Base is running properly on the target host.

There might be a mistake in a configuration file definition, or JP1/Base might not be running properly.

Make sure that the relevant service or process is running and that the configuration file is configured correctly.

If the service or process is not running, take the following actions, and then retry the operation:

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

A request was executed in an invalid operating environment.

The IM configuration (system hierarchy information) might have been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21181-E

The log file trap for monitoring-target-name failed to start.

Details: details

The configuration file of the host "host-name" has been overwritten with the edited configuration file because rollback of the configuration file failed.

An attempt to start the log file trap failed.

The configuration file was overwritten by the edited contents because an attempt to roll back the configuration file failed.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action:

IM Configuration Management database access error.

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

The log file trap service is not running.

Check whether the log file trap service is running. If the log file trap service is not running, start it, and then retry the operation.

The specified command option is invalid.

Check the following items:

• Is the startup option specified correctly?

• Is the -f or -a option specified as an additional option?

A trap with the same name is already running.

Check the log file trap running on the agent host.

The syntax of the configuration file is invalid, or the specified log file does not exist.

Check the following items:

• Are the contents of the configuration file correct?

• Does the specified log file exist?

• If the specified log file path contains space characters, is it enclosed in double quotation marks (")?

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

Failed to relocate the configuration file. (path = path)

Check the following on the agent host, and then retry the operation:

• Has access permission for the path indicated in the message been set correctly?

• Is it possible to overwrite a file, if any, reached by the path indicated in the message?

• Is there sufficient disk space?

An attempt to update the startup definition file "startup-definition-file-path" failed.

Check the following on the agent host, and then retry the operation:

• Has the format of the startup definition file been set correctly?

• Has the access permission for the startup definition file been set correctly?

• Is there sufficient disk space?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21183-E

The log file trap for monitoring-target-name failed to start.

Details: details

The startup definition file of the host "host-name" has been overwritten by IM Configuration Management because rollback of the startup definition file failed.

An attempt to start the log file trap failed.

The startup definition file was overwritten by IM Configuration Management because an attempt to roll back the startup definition file failed.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action:

IM Configuration Management database access error.

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

The log file trap service is not running.

Check whether the log file trap service is running. If the log file trap service is not running, start it, and then retry the operation.

The start options were invalid.

Check the following items:

• Is the startup option specified correctly?

• Is the -f or -a option specified as an additional option?

The log file trap of the monitoring target name "monitoring-target-name" has already been started.

Check the log file trap running on the agent host.

The syntax of the configuration file is invalid, or the specified log file does not exist.

Check the following items:

• Are the contents of the configuration file correct?

• Does the specified log file exist?

• If the specified log file path contains space characters, is it enclosed in double quotation marks (")?

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

Failed to relocate the configuration file. (path = path)

Check the following on the agent host, and then retry the operation:

• Has access permission for the path indicated in the message been set correctly?

• Is it possible to overwrite a file, if any, reached by the path indicated in the message?

• Is there sufficient disk space?

An attempt to update the startup definition file "startup-definition-file-path" failed.

Check the following on the agent host, and then retry the operation:

• Has the format of the startup definition file been set correctly?

• Has the access permission for the startup definition file been set correctly?

• Is there sufficient disk space?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21184-E

The log file trap for monitoring-target-name failed to stop.

Details: details

The startup definition file of the host "host-name" has been overwritten by IM Configuration Management because rollback of the startup definition file failed.

An attempt to stop the log file trap failed.

The startup definition file was overwritten by IM Configuration Management because an attempt to roll back the startup definition file failed.

S:

Suspends processing.

O:

If the following detailed information is displayed, take the indicated corrective action:

IM Configuration Management database access error.

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

The log file trap service is not running.

Check whether the log file trap service is running. If the log file trap service is not running, start it, and then retry the operation.

Execution of the command to stop the log file trap failed.

Check whether the command that stops the log file trap can be executed on the agent host.

Deletion of the configuration file "file-name" on the agent host failed.

Manually delete the configuration file having the indicated file name on the agent host.

An attempt to update the startup definition file "startup-definition-file-path" failed.

Check the following on the agent host, and then retry the operation:

• Has the format of the startup definition file been set correctly?

• Has the access permission for the startup definition file been set correctly?

• Is there sufficient disk space?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21185-E

Batch collection cannot be performed because the agent configuration does not exist.

An attempt is made to perform batch collection processing in an environment in which the agent configuration does not exist.

Batch collection of profiles is impossible in the remote monitoring configuration.

S:

Stops batch collection of profiles.

O:

If you are using only a remote monitoring configuration, ignore this message. Alternatively, define the agent configuration and then retry the operation.

KNAN21186-E

Batch application processing was not performed because the agent configuration does not exist.

An attempt is made to perform batch application processing in an environment in which the agent configuration does not exist.

Batch application of profiles is impossible in the remote monitoring configuration.

S:

Stops batch application of profiles.

O:

If you are using only the remote monitoring configuration, ignore this message. Alternatively, define the agent configuration and then retry the operation.

KNAN21187-W

The configuration file "file-name" for profile-type on the agent host might have been changed.

Do you want to collect the profile-type?

The configuration file on the server might be different from the latest configuration file used on the agent host.

The possible causes are as follows:

The configuration file on the agent host was rewritten by another user.

Profile collection was not performed after host information was collected and the collection time of the configuration file was cleared.

An imported configuration file was applied.

S:

When you select Yes

Collects the profile information for the agent.

When you select No

Suspends processing.

O:

Check the contents of the configuration file from the agent side, and then continue the collection.

KNAN21300-E

An attempt to paste a business group or a monitoring group failed because the path length exceeds the limit "upper limit byte".

Pasting data will cause the length of the path of a monitoring group to exceed the limit.

S:

Suspends processing.

O:

Shorten the business group name or monitoring group name, and then retry the operation.

KNAN21301-Q

Do you want to apply the business group changes to the system?

If you apply when bizmonmode is ON, the restriction of controlling event monitoring is performed according to the changed business group configuration.

This message confirms that you want to apply the edited information for the business group.

O:

Click the Yes button to apply the edited information for the business group.

If restrictions on operation and reference of business groups are enabled, applying the information changes the range of restrictions on operation and reference of event monitoring for the edited business group configuration.

Click the No button if you do not want to apply the edited information for the business group.

KNAN21302-Q

Do you want to apply the business groups to the central scope monitoring tree?

This message confirms that you want to apply the business groups to the central scope monitoring tree.

O:

Click the Yes button to apply the business groups to the central scope monitoring tree.

Click the No button if you do not want to apply the business groups to the central scope monitoring tree.

KNAN21303-Q

Do you want to delete the selected business group?

This message confirms that you want to delete the business group.

O:

Click the Yes button to delete the selected business group.

Click the No button if you do not want to delete the selected business group.

KNAN21304-Q

Do you want to delete the selected monitoring group?

This message confirms that you want to delete the monitoring group.

O:

Click the Yes button to delete the selected monitoring group.

Click the No button if you do not want to delete the selected monitoring group.

KNAN21305-E

Names are duplicated in the same layer of the business group.

Duplicated names: Duplicated name

Hosts or monitoring groups having the same name exist at the same layer of the business group.

S:

Suspends processing.

O:

Change the business group name or monitoring group name, and then retry the operation.

KNAN21306-E

The host "Host name" cannot be deleted because it is registered in a business group "business-group-name".

A host that belongs to a business group cannot be deleted. If you want to delete the host, unregister the host from the business group.

S:

Suspends processing.

O:

Unregister the host from the business group, and then retry the operation.

KNAN21307-E

The business group or monitoring group could not be created or edited because the length of the path exceeds the limit "upper limit bytes".

Creating or changing a business group or monitoring group will cause the length of the path of a monitoring group to exceed the limit.

S:

Suspends processing.

O:

Shorten the business group name or monitoring group name, and then retry the operation.

KNAN21308-Q

If the hosts "Host name" are unregistered from the business group, they will also be unregistered from all corresponding monitoring groups.

Do you want to continue?

This message confirms that you want to unregister the hosts from all monitoring groups to which the hosts belong.

O:

Click the Yes button to unregister the selected hosts.

Click the No button if you do not want to unregister the selected hosts.

KNAN21309-Q

Executing the Request name request will cause all edited information in the business group to be lost.

Do you want to continue?

This message confirms that you want to discard the contents of the business group that is being edited.

O:

Click the Yes button to perform the operation indicated by request-name.

Click the No button if you do not want to perform the operation indicated by request-name.

KNAN21310-E

Host Name of the host "Old Host Name" cannot be changed since the monitoring group of the same name "New Host Name" already exists in the same heirarchy.

A monitoring group that has the same name as the host exists at the layer of the business group to which the host belongs.

S:

Suspends processing.

O:

Specify a unique name for the monitoring group at that layer, and then retry the operation.

KNAN21311-E

The operation to upper limit cannot be performed because the number of levels for business groups and monitoring groups exceeds the limit (operation levels).

Performing the operation on a monitoring group will cause the number of levels for business groups and monitoring groups to exceed the limit.

S:

Suspends processing.

O:

Create the business group so that the number of levels for business groups and monitoring groups is within the limit.

KNAN21400-W

Collection of host information from host "host-name" partially succeeded.

Collection of host information from JP1/Base succeeded while collection of host information from the remote host failed.

Details: details

Collection of host information from the specified host partially succeeded.

S:

Does not collect host information from the remote host.

O:

If an error occurred during collection of host information from a remote host and the following detailed information is displayed, take the indicated corrective action.

Remote communication settings have not been configured.

Configure the remote communication settings for the host, and then retry the operation.

An attempt to connect monitored host failed.

If the OS for the monitored host is UNIX, check the following items:

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items:

• Is communication with the monitored host possible?

• Has the password for the user who logs in to the monitored host expired?

• Has the remote communication type for the monitored host name been set correctly?

• Is the WMI service running?

If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection have been configured correctly.

Authentication failed.

If the OS for the monitored host is UNIX, check the following items:

• Has SSH authentication been configured correctly?

If no error is found by checking the above item, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

Acquisition of an SSH private key failed.

On the SSH page in the system common settings, set a private key file path.

Creation of the jcfallogtrap process failed.

Check the IM host account specified in the system common settings.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21401-W

Collection of host information from host (host-name) partially succeeded.

Collection of host information from the remote host succeeded while collection of host information from JP1/Base failed.

Details: details

Collection of host information from the specified host partially succeeded.

S:

Does not collect host information from JP1/Base.

O:

If an error occurred during collection of host information from JP1/Base and the following detailed information is displayed, take the indicated corrective action. Note, however, that no action is required if you do not want to monitor an agent configuration. Even if an agent configuration is not monitored, this message will be output until the host is included in an IM configuration.

Collection of host information failed because a connection could not be established with the host host-name.

• Make sure that the connecting host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

• Make sure that name resolution can be performed.

Collection of host information failed because the version of JP1/Base on the host host-name is not supported.

• Upgrade the JP1/Base version to 09-00 or later.

An attempt to collect host information for the host host-name failed because the actual host type is different from the registered host type. (registered host type = registered-host-type, collected host type = actual-host-type)

• Edit the host attribute to correct the host type. Then, retry the operation.

Collection of host information from the host "host-name" failed. (A connection could not be established with the host.)

• Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

Collection of host information from the host host-name failed. (A request was executed in an invalid operating environment.)

• Make sure that the connecting host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

Collection of host information from the host host-name failed. (Details:IM Configuration Management database access error.)

• Invalid data might have been sent from JP1/Base on the target host. Make sure that JP1/Base is running on the target host.

Collection of host information from the host host-name failed. (Details:There are not enough resources.)

• Make sure that there are sufficient OS resources such as disk space and memory.

Collection of host information from the host host-name failed. (The connection destination host is busy.)

• Wait a while, and then retry the operation.

Collection of host information from the host host-name failed. (Failed to send the data to the connection destination host.)

Collection of host information from the host host-name failed. (Failed to receive the data from the connection destination host.)

• Check the OS resources, memory status, and the condition and status of the network connection with the destination host.

• Make sure that IM Configuration Management Service is running on the connection destination host.

Collection of host information from the host host-name failed. (A request was executed in an invalid operating environment.)

• The IM configuration (system hierarchy information) might have been deleted.

• Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21402-E

The collection of host information for a host "host-name" failed.

The collection of host information failed from JP1/Base.

Detailed information: detailed-information

The collection of remote host information failed.

Detailed information: detailed-information

An attempt to collect host information failed.

S:

Does not collect host information.

O:

If an error occurred during collection of host information from JP1/Base and the following detailed information is displayed, take the indicated corrective action. Note, however, that no action is required if you do not want to monitor an agent configuration. If you do not want to monitor a remote monitoring configuration, no action is required if an attempt to collect host information from a remote host failed. Even if an agent configuration or remote monitoring configuration is not monitored, this message will be output until the host is included in an IM configuration.

Collection of host information failed because a connection could not be established with the host host-name.

• Make sure that the connecting host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

• Make sure that name resolution can be performed.

Collection of host information failed because the version of JP1/Base on the host host-name is not supported.

• Upgrade the JP1/Base version to 09-00 or later.

An attempt to collect host information for the host host-name failed because the actual host type is different from the registered host type. (registered host type = registered-host-type, collected host type = actual-host-type)

• Edit the host attribute to correct the host type. Then, retry the operation.

Collection of host information from the host "host-name" failed. (A connection could not be established with the host.)

• Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

Collection of host information from the host host-name failed. (A request was executed in an invalid operating environment.)

• Make sure that the connecting host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

Collection of host information from the host host-name failed. (Details:IM Configuration Management database access error.)

• Invalid data might have been sent from JP1/Base on the target host. Make sure that JP1/Base is running on the target host.

Collection of host information from the host host-name failed. (Details:There are not enough resources.)

• Make sure that there are sufficient OS resources such as disk space and memory.

Collection of host information from the host host-name failed. (The connection destination host is busy.)

• Wait a while, and then retry the operation.

Collection of host information from the host host-name failed. (Failed to send the data to the connection destination host.)

Collection of host information from the host host-name failed. (Failed to receive the data from the connection destination host.)

• Check the OS resources, memory status, and the condition and status of the network connection with the destination host.

• Make sure that IM Configuration Management Service is running on the connection destination host.

Collection of host information from the host host-name failed. (A request was executed in an invalid operating environment.)

• The IM configuration (system hierarchy information) might have been deleted.

• Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If an error occurred during collection of host information from a remote host and the following detailed information is displayed, take the indicated corrective action.

Remote communication settings have not been configured.

Configure the remote communication settings for the host, and then retry the operation.

An attempt to connect monitored host failed.

If the OS for the monitored host is UNIX, check the following items:

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the above item, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items:

• Is communication with the monitored host possible?

• Has the password for the user who logs in to the monitored host expired?

• Has the remote communication type for the monitored host name been set correctly?

• Is the WMI service running?

If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection have been configured correctly.

Authentication failed.

If the OS for the monitored host is UNIX, check the following items:

• Has SSH authentication been configured correctly?

If no error is found by checking the above item, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

Acquisition of an SSH private key failed.

On the SSH page in the system common settings, set a private key file path.

Creation of the jcfallogtrap process failed.

Check the IM host account specified in the system common settings.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21403-E

Host "host-name" failed to collect host information from the remote host.

Details: details

An attempt to collect host information failed.

S:

Does not collect host information.

O:

If an error occurred during collection of host information from a remote host and the following detailed information is displayed, take the indicated corrective action.

Remote communication settings have not been configured.

Configure the remote communication settings for the host, and then retry the operation.

An attempt to connect monitored host failed.

If the OS for the monitored host is UNIX, check the following items:

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the above item, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items:

• Is communication with the monitored host possible?

• Has the password for the user who logs in to the monitored host expired?

• Has the remote communication type for the monitored host name been set correctly?

• Is the WMI service running?

If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection have been configured correctly.

Authentication failed.

If the OS for the monitored host is UNIX, check the following items:

• Has SSH authentication been configured correctly?

If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

Acquisition of an SSH private key failed.

On the SSH page in the system common settings, set a private key file path.

Creation of the jcfallogtrap process failed.

Check the IM host account specified in the system common settings.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21404-E

There is a host for which IM configuration synchronization failed.

Take action according to the manual, and then retry IM configuration synchronization.

Host where acquisition of the agent configuration failed. (Host: host-name)

Host where acquisition of the remote configuration failed. (Host: host-name)

Synchronization failed.

S:

Stops synchronization.

O:

Check whether JP1/Base is running on the host (site manager) for which an attempt to acquire an agent configuration failed. If it is running, perform the following.

Execute the jbsrt_get command.

Check whether any of the following occurred:

Was a KAVB3162-E message output?

Did the jbsrt_get command end abnormally?

Is the local host name displayed as a higher-level host or a lower-level host?

Is a host name other than the local host name displayed as the local host?

Is the host name misspelled?

If any of the above occurred, use the following method to recover from the error:

Execute the jbsrt_del command to delete the IM configuration on the host (site manager) for which the agent configuration could not be acquired.

Apply the IM configuration again from the manager host by using batch distribution.

Check the following items for the host (site manager) for which an attempt to acquire a remote monitoring configuration failed.

Make sure that IM Configuration Management is running on the site manager. If a remote monitoring configuration does not exist on the site manager, ignore this message.

Connect IM Configuration Management - View and make sure that the remote monitoring configuration can be displayed.

If the communication encryption function is enabled on the base manager, check if the root certificate of the base manager has been set on the connection-target manager. For details about troubleshooting, see If acquisition of remote monitoring configuration fails during IM configuration synchronization in 11.5.1(59) Actions to take when an error is displayed in JP1/IM - View when the communication encryption function is enabled in the JP1/Integrated Management 2 - Manager Administration Guide.

KNAN21405-W

Collection of host information from host "host-name" partially succeeded.

Collection of host information from JP1/Base succeeded while collection of host information from the remote host failed.

Detailed information: detailed-information

All remote monitoring on the host "host-name" stopped, because collection of remote host information failed.

Collection of host information from the specified host was partially successful. Because host information could not be collected from the remote host, all remote monitoring operations on the host stopped.

S:

Does not collect host information from the remote host and stops all remote monitoring operations on the host.

O:

Perform the corrective action that is described in the detailed information, and then re-execute the collection of host information from the remote host.

After the collection of host information from the remote host finishes normally, restart the remote monitoring operations that were stopped.

If an error occurs during the collection of host information from the remote host and the following detailed information is displayed, perform the indicated corrective action:

Remote communication settings have not been configured.

Configure the remote communication settings of the host, and then retry the operation.

An attempt to connect to the monitored host failed.

If the OS of the monitored host displayed for host-name is UNIX, check the following items:

• Is communication with the monitored host possible?

• Is the remote communication type of the monitored host set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the preceding items, make sure that the SSH connection is configured correctly.

If the OS of the monitored host displayed for host-name is Windows, check the following items:

• Is communication with the monitored host possible?

• Has the password for the user who is trying to log in to the monitored host expired?

• Is the remote communication type of the monitored host set correctly?

• Is the WMI service running?

If no error is found by checking the preceding items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection are configured correctly.

Authentication failed.

If the OS of the monitored host displayed for host-name is UNIX, check the following item:

• Is SSH authentication configured correctly?

If no error is found by checking the above item, make sure that the SSH connection is configured correctly.

If the OS of the monitored host displayed for host-name is Windows, check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings window or the Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the preceding items, make sure that the WMI connection is configured correctly.

Acquisition of an SSH private key failed.

On the SSH page in the system common settings, set a private key file path.

Creation of the remote monitoring process failed.

Check the IM host account specified in the system common settings.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21406-W

Collection of host information from host (host-name) partially succeeded.

Collection of host information from the remote host succeeded while collection of host information from JP1/Base failed.

Detailed information: detailed-information

All remote monitoring on the host "host-name" stopped, because the OS of the host changed around the time that the host information was collected. (OS before collection = OS-before-collection, OS after collection = OS-after-collection)

Collection of host information from the specified host was partially successful. Because the OS of the host changed after the host information was collected, all remote monitoring operations on the host stopped.

S:

Does not collect host information from JP1/Base and stops all remote monitoring operations on the host.

O:

The OS of the monitored host has changed. Make sure that the correct monitored host is specified.

If the monitored host is correct, make sure that the remote monitoring profile settings are appropriate for the OS displayed for OS-after-collection, and then restart the remote monitoring operations that were stopped. In addition, perform the corrective action that is described in the detailed information, and then re-execute the collection of host information.

If an error occurred during the collection of host information from JP1/Base and the following detailed information is displayed, perform the indicated corrective action.

Collection of host information failed because a connection could not be established with the host "host-name".

• Make sure that the connection-destination host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

• Make sure that name resolution can be performed.

Collection of host information failed because the version of JP1/Base on the host "host-name" is not supported.

• Upgrade JP1/Base to version 09-00 or later.

An attempt to collect host information for the host "host-name" failed because the actual host type is different from the registered host type. (registered host type = registered-host-type, actual host type = host-type)

• Change the host attribute to correct the host type, and then retry the operation.

Collection of host information from the host "host-name" failed. (Details: IM Configuration Management database access error)

• Execute the jimdbstatus command to check whether the IM database service is running. If the service is not running, start it.

Collection of host information from the host "host-name" failed. (Details: A connection could not be established with the host.)

• Make sure that the connection-destination host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

Collection of host information from the host "host-name" failed. (Details: The data acquired during the connection to the host is invalid.)

• Invalid data might have been sent from JP1/Base on the target host. Make sure that JP1/Base is running on the target host.

Collection of host information from the host "host-name" failed. (Details: There are not enough resources.)

• Make sure OS resources such as disk space and memory are sufficient.

Collection of host information from the host "host-name" failed. (Details: The connection-destination host is busy.)

• Wait a while, and then retry the operation.

Collection of host information from the host "host-name" failed. (Details: Failed to send data to the connection-destination host.)

Collection of host information from the host "host-name" failed. (Details: Failed to receive data from the connection-destination host.)

• Check the OS resources, memory status, and the condition and status of the network connection with the connection-destination host.

• Make sure that the IM Configuration Management service is running on the connection-destination host.

Collection of host information from the host "host-name" failed. (Details: A request was executed in an invalid operating environment.)

• The IM configuration (system hierarchy) might have been deleted.

• Click Operation and then Verify IM Configuration to check whether the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

If the monitored host is incorrect, revise the system configuration.

KNAN21407-E

The collection of host information for a host "host-name" failed.

The collection of host information failed from JP1/Base.

Detailed information: detailed-information

The collection of remote host information failed.

Detailed information: detailed-information

All remote monitoring on the host ""host-name" stopped, because collection of remote host information failed.

Host information could not be collected. Because host information could not be collected from a remote host, all remote monitoring operations on the host were stopped.

S:

Does not collect host information and stops all remote monitoring operations on the host.

O:

Perform the corrective action that is described in the detailed information, and then re-execute the collection of host information.

After the collection of remote host information from the remote host finishes normally, restart the remote monitoring operations that were stopped.

If an error occurred during the collection of host information from a remote host and the following detailed information is displayed, perform the indicated corrective action.

Remote communication settings have not been configured.

Configure the remote communication settings of the host, and then retry the operation.

An attempt to connect to the monitored host failed.

If the OS of the monitored host displayed for host-name is UNIX, check the following items:

• Is communication with the monitored host possible?

• Is the remote communication type of the monitored host set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the preceding items, make sure that the SSH connection is configured correctly.

If the OS of the monitored host displayed for host-name is Windows, check the following items:

• Is communication with the monitored host possible?

• Has the password for the user who is trying to log in to the monitored host expired?

• Is the remote communication type of the monitored host set correctly?

• Is the WMI service running?

If no error is found by checking the preceding items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection are configured correctly.

Authentication failed.

If the OS of the monitored host displayed for host-name is UNIX, check the following item:

zueng030.tif Is SSH authentication configured correctly?

If no error is found by checking the preceding item, make sure that the SSH connection is configured correctly.

If the OS of the monitored host displayed for host-name is Windows, check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings window or the Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the preceding items, make sure that the WMI connection is configured correctly.

Acquisition of an SSH private key failed.

On the SSH page in the system common settings, set a private key file path.

Creation of the remote monitoring process failed.

Check the IM host account specified in the system common settings.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

If an error occurs during the collection of host information from JP1/Base and the following detailed information is displayed, perform the indicated corrective action.

Collection of host information failed because a connection could not be established with the host "host-name".

• Make sure that the connection-destination host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

• Make sure that name resolution can be performed.

Collection of host information failed because the version of JP1/Base on the host "host-name" is not supported.

• Upgrade JP1/Base to version 09-00 or later.

An attempt to collect host information for the host "host-name" failed because the actual host type is different from the registered host type. (registered host type = registered-host-type, actual host type = host-type)

• Change the host attribute to correct the host type, and then retry the operation.

Collection of host information from the host "host-name" failed. (Details: IM Configuration Management database access error)

• Execute the jimdbstatus command to check whether the IM database service is running. If the service is not running, start it.

Collection of host information from the host "host-name" failed. (Details: A connection could not be established with the host.)

• Make sure that the connection-destination host is running.

• Make sure that a connection can be established with the host.

• Make sure that JP1/Base is running.

Collection of host information from the host "host-name" failed. (Details: The data acquired during the connection to the host is invalid.)

• Invalid data might have been sent from JP1/Base on the target host. Make sure that JP1/Base is running on the target host.

Collection of host information from the host "host-name" failed. (Details: There are not enough resources.)

• Make sure that OS resources such as disk space and memory are sufficient.

Collection of host information from the host "host-name" failed. (Details: The connection-destination host is busy.)

• Wait a while, and then retry the operation.

Collection of host information from the host "host-name" failed. (Details: Failed to send data to the connection-destination host.)

Collection of host information from the host "host-name" failed. (Details: Failed to receive data from the connection-destination host.)

• Check the OS resources, memory status, and the condition and status of the network connection with the connection-destination host.

• Make sure that the IM Configuration Management service is running on the connection-destination host.

Collection of host information from the host "host-name" failed. (Details: A request was executed in an invalid operating environment.)

• The IM configuration (system hierarchy) might have been deleted.

• Click Operation and then Verify IM Configuration to check whether the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21408-E

Host "host-name" failed to collect host information from the remote host.

Detailed information: detailed-information

All remote monitoring on the host "host-name" stopped, because collection of remote host information failed.

Host information could not be collected. Because host information could not be collected from the remote host, all remote monitoring operations on the host were stopped.

S:

Does not collect host information and stops all remote monitoring operations on the host.

O:

Perform the corrective action that is described in the detailed information, and then re-execute the collection of host information.

After the collection of remote host information from the remote host finishes normally, restart the remote monitoring operations that were stopped.

If an error occurs during the collection of host information from a remote host and the following detailed information is displayed, perform the indicated corrective action.

Remote communication settings have not been configured.

Configure the remote communication settings of the host, and then retry the operation.

An attempt to connect monitored host failed.

If the OS of the monitored host displayed for host-name is UNIX, check the following items:

• Is communication with the monitored host possible?

• Is remote communication type of the monitored host name set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the preceding items, make sure that the SSH connection is configured correctly.

If the OS of the monitored host displayed for host-name is Windows, check the following items:

• Is communication with the monitored host possible?

• Has the password for the user who is trying to log in to the monitored host expired?

• Is the remote communication type of the monitored host name set correctly?

• Is the WMI service running?

If no error is found by checking the preceding items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection are configured correctly.

Authentication failed.

If the OS of the monitored host displayed for host-name is UNIX, check the following item:

• Is SSH authentication configured correctly?

If no error is found by checking the preceding item, make sure that the SSH connection is configured correctly.

If the OS of the monitored host displayed for host-name is Windows, check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings window or the Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the preceding items, make sure that the WMI connection is configured correctly.

Acquisition of an SSH private key failed.

On the SSH page in the system common settings, set a private key file path.

Creation of the remote monitoring process failed.

Check the IM host account specified in the system common settings.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN21409-W

Host information from the host "host-name" was successfully collected.

All remote monitoring on the host "host-name" stopped, because the OS of the host changed around the time that the host information was collected. (OS before collection = OS-before-collection, OS after collection = OS-after-collection)

Host information was collected successfully. Because the OS of the host changed after the host information was collected, all remote monitoring operations on the host were stopped.

S:

Stops all remote monitoring operations on the host.

O:

The OS of the monitored host has changed. Make sure the correct monitored host is specified.

If the monitored host is correct, make sure the remote monitoring profile settings are appropriate for the OS displayed for OS-after-collection, and then restart the remote monitoring operations that were stopped.

If the monitored host is incorrect, revise the system configuration.

KNAN21410-E

An attempt to copy to the clipboard failed because the clipboard is being used.

An attempt to copy to the clipboard failed because the clipboard is being used by another application.

S:

Suspends the attempt to copy to the clipboard.

O:

Make sure that no other application is using the clipboard, and then retry the operation.

KNAN21411-E

A memory shortage occurred during processing to copy to the clipboard.

A memory shortage occurred during copying to the clipboard.

S:

Suspends the attempt to copy to the clipboard.

O:

Check the following, and then retry the operation:

Make sure that there is sufficient memory.

Check the Windows event log to make sure that OS resources are sufficient.

KNAN21412-E

An attempt to copy to the clipboard has failed.

An attempt to copy to the clipboard failed.

S:

Suspends the attempt to copy to the clipboard.

O:

Retry the operation.

If this message frequently appears, use the data collection tool to collect data, and then contact a system administrator.

2.13 Messages related to IM Configuration Management (KNAN22000 to KNAN26999)

KNAN22000-I

The host "host-name" was successfully registered.

The host was successfully registered.

S:

Registers the host.

KNAN22001-I

An attribute for the host "host-name" was successfully changed.

An attribute for the specified host was changed.

S:

Changes the host attribute.

KNAN22002-I

Host information from the host "host-name" was successfully collected.

Host information from the agent host was collected successfully.

S:

Collects the host information.

KNAN22003-I

The host "host-name" was successfully deleted.

The specified host was successfully deleted.

S:

Deletes the host.

KNAN22004-E

Collection of host information from all hosts failed. (Cause: error-code)

A search of all hosts failed.

S:

Does not collect host information.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22005-E

Host "host-name" cannot be registered because a host with the same name is already registered.

The host is already registered in the IM Configuration Management database.

S:

Does not register the host.

O:

Register a host name that is not already registered.

KNAN22006-E

Registration of the host "host-name" failed because the number of registered hosts exceeded the maximum limit maximum-number-of-registered-hosts.

Registration of the host failed because the number of registered hosts exceeds the maximum.

S:

Does not register the host.

O:

Take one of the following measures:

Delete unnecessary hosts registered in the IM Configuration Management.

If the maximum-number-of-registered-hosts is 1,024, expand the size of the IM Database Service to the L size.

KNAN22007-E

The host "host-name-1" cannot be registered because the host "host-name-2" specified in related-host is not registered.

The host specified as the active host, the standby host, or the VMM host was not registered.

S:

Does not register the host.

O:

Specify a host that is not registered in the host list as the host name for the active host, the standby host, or the VMM host.

KNAN22008-E

Registration of the host "host-name" failed. (Cause: error-code)

Registration of the host failed.

S:

Does not register the host.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22009-E

Registration of the host "host-name" failed because the host type of the host "related-host-name" specified in related-host is incorrect.

Registration of the host failed because the specified host type is incorrect.

S:

Does not register the host.

O:

Revise the condition based on the host type:

For a VMM host, specify the physical host.

For an active host, specify the physical host or the virtual host.

For a standby host, specify the physical host or the virtual host.

KNAN22010-E

An attribute of the host "host-name" cannot be changed because the host "host-name" specified in related-host is not registered.

An attribute of the host cannot be changed because the specified host is not registered.

S:

Does not register the changed host attribute.

O:

Specify a host that is not registered in the host list as the host name for the VMM host, the active host, or the standby host.

KNAN22011-E

An attribute of the host "host-name" cannot be changed because the host type of the host "related-host-name" specified in related-host is incorrect.

An attribute of the host cannot be changed because the specified host type is incorrect.

S:

Does not register the changed host attribute.

O:

Revise the condition based on the host type:

For a VMM host, specify the physical host.

For an active host, specify the physical host or the virtual host.

For a standby host, specify the physical host or the virtual host.

KNAN22012-E

An attempt to change a host attribute for the host "host-name" failed. (Details: error-code)

A host attribute of the specified host could not be changed.

S:

Does not register the changed host attribute.

O:

If the following detailed information is displayed, take the indicated corrective action.

Trap is running for the host.

Stop the remote log-file trap and remote event-log trap running on the target host. Then retry the operation.

Operations cannot be performed on the file.

• Check the appropriate OS log listed in the following to determine if there is any shortage of an OS resource such as file descriptors, and then perform the processing again:

• Windows: Windows event log

• UNIX: syslog

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If detailed information other than the above is displayed, execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

KNAN22013-E

The host attribute cannot be changed to host-type because host host-name is referenced as related-host from host-name-2.

The host attribute cannot be changed because the specified host is referenced from another host.

S:

Does not register the changed host attribute.

O:

Edit the host attribute of the referencing host so that it is not referenced, and then retry the operation.

KNAN22014-E

The host attribute cannot be changed because the host "host-name" is the local host.

A host attribute of the local host cannot be changed.

S:

Does not register the changed host attribute.

O:

Do not change the host type of the local host.

KNAN22015-E

Collection of host information from the host "host-name" failed. (Details: error-code)

Collection of host information from the specified host failed.

S:

Does not collect host information.

O:

If the following detailed information is displayed, take the indicated corrective action.

The data that was acquired while connected to the host is invalid.

It is possible that invalid data was sent from JP1/Base of the connected host.

Make sure that JP1/Base of the connected host is operating normally.

Check the connection status of the manager host and the host to which it is connected.

If you are using the communication encryption function, review the settings to see if any of the following conditions apply:

- Is there a configuration of the communication encryption feature between the manager and the host that match the destination host?

- Does the settings in the non-SSL communication host configuration file on the manager's JP1/Base match the destination host?

- Does the root certificate correspond to the server certificate of the manager's destination host?

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

The connection destination host is busy.

Wait awhile, and then retry the operation.

Failed to receive the data from the connection destination host.

Failed to send the data to the connection destination host.

Check the OS resources and memory status, and then check the network configuration and status with the connection destination.

Also make sure that IM Configuration Management Service of the connection destination is running.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22016-E

Collection of host information failed because the version of JP1/Base on the host host-name is not supported.

Collection of host information failed because the version of JP1/Base on the specified host is not supported.

S:

Does not collect host information.

O:

Upgrade JP1/Base to version 09-00 or later.

KNAN22017-E

Collection of host information failed because a connection could not be established with the host "host-name".

Collection of host information failed because a connection could not be established with the specified host.

S:

Does not collect host information.

O:

Check the following items, and then retry the operation.

Has the connection destination been started?

Can a connection destination be made to the host?

Is JP1/Base on the connection destination running?

Can name resolution of host-name be performed on the manager host?

Are the JP1/Base settings on the manager host and the connection destination correct?

Is the connection destination in high load status?

Is the network to the connection destination in high load status?

KNAN22019-E

An attempt to collect host information for the host "host-name" failed because the actual host type is different from the registered host type. (registered host type = registered-host-type, collected host type = actual-host-type)

An attempt to collect host information for the specified host failed because the actual host type is different from the registered host type.

S:

Does not collect host information.

O:

Edit the host attribute so that it is the proper type, and then retry the operation.

KNAN22020-E

The host "host-name" cannot be deleted because a local host cannot be deleted.

A local host cannot be deleted.

S:

Does not delete the host.

O:

Do not delete a local host.

KNAN22021-E

The host "host-name" cannot be deleted because hosts in an IM configuration cannot be deleted.

The specified host cannot be deleted because it is contained in an IM configuration (system hierarchy).

S:

Does not delete the host.

O:

Separate the host from the IM configuration (system hierarchy), and then retry the operation.

KNAN22022-E

The host "host-name-1" cannot be deleted because it is referenced as related-host host for the host "host-name-2".

The specified host cannot be deleted because it is referenced from another host.

S:

Does not delete the host.

O:

Edit the host attribute of the referencing host so that it is not referenced, and then retry the operation.

KNAN22023-E

Deletion of the host "host-name" failed. (Cause: error-code)

Deletion of the specified host failed.

S:

Does not delete the host.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22024-E

Acquisition of product information for the host "host-name" failed. (Cause: error-code)

Acquisition of product information for the specified host failed.

S:

Does not collect host information.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22025-E

Acquisition of host information for the host "host-name" failed. (Cause: error-code)

Acquisition of host information for the specified host failed.

S:

Does not acquire host information.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22026-E

An attribute of the host "host-name" could not be changed because the host name "new-host-name" is already registered.

An attribute of the host could not be changed because the entered host name is already registered.

S:

Does not register the changed host attribute.

O:

Enter a different host name, and then retry the operation.

KNAN22027-W

Host information cannot be collected because the user user-name:View-host-name is collecting information for the host "host-name".

Host information cannot be collected because another user is collecting information.

S:

Does not collect host information.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Wait awhile, and then retry the operation.

KNAN22028-E

Host Registration failed because the number of registered hosts exceeded the maximum limit maximum-number-of-registered-hosts.

Registration of the host failed because the number of registered hosts exceeds the maximum.

S:

Does not register the host.

O:

The total of the hosts registered in the IM Configuration Management and the hosts in the selected configuration information file exceeded the maximum-number-of-registered-hosts. Take one of the following measures.

Delete unnecessary hosts registered in the selected configuration information file.

Delete unnecessary hosts registered in the IM Configuration Management.

If the maximum-number-of-registered-hosts is 1,024, and the total of the remotely monitored hosts registered in IM Configuration Management and remotely monitored hosts in the configuration information file is 1,024 or less, expand the size of the IM Database Service to the L size.

KNAN22029-E

Host registration failed because the host "Related hostname", whose virtualization management type is "Related system type", cannot be specified as the VMM host of the host "host-name".

Host registration is impossible because a host that cannot be used as a VMM host is specified as the VMM host.

S:

Cancels registration of the host.

O:

Change the virtualization management type of the host specified as the VMM host.

KNAN22030-E

Host attributes could not be changed because the host "Related hostname", whose virtualization management type is "Related system type", cannot be specified as the VMM host of the host "host-name".

Host attributes cannot be changed because the host for which the virtualization management type is set cannot be specified as the VMM host.

S:

Cancels update of the host.

O:

Change the virtualization management type of the host specified as the VMM host.

KNAN22031-E

The request "request name" cannot be executed for the host "host-name" because the host contains data of a higher version.

Operations cannot be performed on a host that retains data of a higher version.

S:

Cancels operation on the host.

O:

Check the version of JP1/IM - Manager, and then perform the operation from the corresponding version of JP1/IM Configuration Management - View.

KNAN22032-E

The host "host-name" cannot be deleted because hosts in a business group cannot be deleted.

The host you are trying to delete belongs to a business group.

S:

Does not delete the host.

O:

Remove the host from the business group, and then retry the operation.

KNAN22033-E

The host host name cannot be deleted because hosts in a remote monitoring configuration cannot be deleted.

The host you are trying to delete is included in a remote monitoring configuration.

S:

Does not delete the host.

O:

Remove the host from the remote monitoring configuration, and then retry the operation.

KNAN22050-I

The virtualization configuration for the host "host-name" was collected successfully.

The virtualization configuration for the host was collected.

S:

Collected the virtualization configuration for the host.

KNAN22051-I

The host virtualization configuration was changed because the host "host-name" did not exist in the collected virtualization configuration.

The virtualization configuration for the host was changed because the host registered as a virtual server did not exist in the collected virtualization configuration.

KNAN22052-E

The virtualization configuration for the host "host-name" cannot be collected because the host is locked by the user "user name:Client host name".

An attempt to collect the virtualization configuration failed because another user has locked the host.

S:

Does not collect the virtualization configuration.

O:

Perform either of the following.

In the Login User List window, check the user who has locked the host. Check the status of the operator who has locked the host, select the check box for the user who has locked the host, and then click the Release Exclusive Editing button to release the lock.

Wait a while, and then retry the operation.

KNAN22053-E

The virtualization configuration for the host "host-name" cannot be collected because host information is being updated.

The virtualization configuration for the host cannot be collected because the host information has been updated.

S:

Stops collection of the virtualization configuration.

O:

Update the host information, and then retry the operation.

KNAN22054-E

The virtualization configuration for the host "host-name" cannot be collected because the profile information is locked by the user "user name:Client host name".

The virtualization configuration for the host cannot be collected because another user has locked the profile.

S:

Stops collection of the virtualization configuration.

O:

Perform either of the following.

In the Login User List window, check the user who has locked the profile. Check the operation status of the operator who has locked the host, select the check box for the user who has locked the host, and then click the Release Exclusive Editing button to release the lock.

Wait a while, and then retry the operation.

KNAN22055-E

The virtualization configuration for the host "host-name" cannot be collected because profile information is being updated.

The virtualization configuration for the host cannot be collected because the profile information has been updated.

S:

Stops collection of the virtualization configuration.

O:

Obtain the profile information, and then retry the operation.

KNAN22056-E

The host "host-name" cannot be updated because it is locked by the user "user name:Client host name".

Host information cannot be updated because another user has locked the host.

S:

Does not update the host information.

O:

Perform either of the following.

In the Login User List window, check the user who has locked the host. Check the operation status of the operator who has locked the host, select the check box for the user who has locked the host, and then click the Release Exclusive Editing button to release the lock.

Wait a while, and then retry the operation.

KNAN22057-I

The host "host-name", whose type is "VMM Host or VM Host", was registered successfully.

An unregistered host was detected and registered when the virtualization configuration was collected.

KNAN22058-E

Collection of the virtualization configuration for the host "host-name" has failed. (cause = Detailed information)

An attempt to collect the virtualization configuration failed.

S:

Stops collection of the virtualization configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

Host host-name is not found.

Check whether the host indicated in the detailed information exists in the host list.

Invalid Username/Password/Domain name.

Enter the correct user name, password, or domain name.

If this message appears again after the correct user name, password, or domain name is entered, check whether a host name that can be resolved to an IP address is set.

The specified user has insufficient privilege to acquire virtual configuration.

Make sure that the user who has permissions to acquire a virtualization configuration performed the operation.

A request was executed in an invalid operating environment.

Make sure that the virtualization environment management software can manage the virtual computers.

SCVMM Admin Console Version is incompatible.

Match the version of the SCVMM management console on the JP1/IM - Manager host and the version of the connection destination SCVMM so that they can be connected.

VMM database error.

Make sure that VMM database is operating correctly.

A prerequisite component might not be available, or Username/Password/Domain name might be invalid.

If a prerequisite product is not installed, install it, and then retry the operation.

Check and, if necessary, correct the entered user name, password, and domain name.

If this message appears again after the correct user name, password, and domain name are entered, check whether a host name that can be resolved to an IP address is set.

An error occurred in the KVM host.

Make sure that the KVM host is operating correctly and the libvirt service is running, and then retry the operation.

HCSM server is busy.

Make sure that HCSM at the connection destination is operating correctly. Wait a while, and then retry the operation.

Failed to login to HCSM sever.

Make sure that you can log in to HCSM by using the specified user name and password.

One of the following messages is indicated in Detailed information with an HCSM error code:

- Failed to connect to HCSM: HCSM-error-code

- Failed to get information from HCSM server: HCSM-error-code

- HCSM server internal error: HCSM-error-code

- HCSM server error: HCSM-error-code

Make sure that you can log in to HCSM by using the specified user name and password. Also make sure that HCSM at the connection destination is operating correctly.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22060-E

An attempt to update details for the host "host-name" failed because the registered host (Registered Host Type) is different from the actual type (Actual Host Type).

Host information cannot be updated because the host attributes are inconsistent in the collected virtualization configuration.

S:

Does not update information for the host and lower-level host whose attributes are inconsistent.

O:

Check the items listed below. Then delete the host, or edit the host information to match the actual system. After deleting the host or editing the host information, collect the virtualization configuration again.

Is there another host having the same name?

Is the host type correct?

Is the virtualization management type correct?

KNAN22061-E

Collection of the virtualization configuration failed because the user "user name:Client host name" is now batch collecting the virtualization configurations.

The virtualization configuration cannot be collected because another user is collecting it.

S:

Stops collection of the virtualization configuration.

O:

Wait a while, and then retry the operation.

KNAN22062-E

Collection of the virtualization configuration failed for the host "host-name" because the communication type is not supported.

An attempt to collect the virtualization configuration failed because the communication type of the host was not supported.

S:

Stops collection of the virtualization configuration.

O:

Respecify the communication type of the host, and then retry the operation.

KNAN22063-E

Collection of the virtualization configuration failed for the host "host-name" because a prerequisite component is not available.

An attempt to collect the virtualization configuration failed because a prerequisite product was not available on the host.

S:

Stops collection of the virtualization configuration.

O:

Install the prerequisite product, and then retry the operation.

KNAN22064-E

Collection of the virtualization configuration failed because the export command is executing.

A virtualization configuration cannot be collected during export.

S:

Stops collection of the virtualization configuration.

O:

Wait a while, and then retry the operation.

KNAN22065-E

Collection of the virtualization configuration failed for host "host-name" because the user name is not registered.

The virtualization configuration cannot be collected because the user name is not registered on the host.

S:

Stops collection of the virtualization configuration.

O:

Edit the host to register the user name and password. Then, retry the operation.

KNAN22066-E

Collection of the virtualization configuration failed because communication with host "host-name" was not possible.

An attempt to collect the virtualization configuration failed because communication with the host was not possible.

S:

Stops collection of the virtualization configuration.

O:

Check the following items, and then retry the operation.

Is the target host running?

Has the target virtualization environment management software been started and set up?

Has communication failure with the host occurred?

If the target virtualization environment management software is SCVMM, make sure that the SCVMM management console on the JP1/IM - Manager host can connect to SCVMM on the target host. Also make sure that their versions are the same.

If you attempted to collect the virtualization configuration from HCSM, make sure that the user name and password are specified correctly. Also make sure that you can log in to HCSM from the manager host by using the specified user name and password.

KNAN22067-E

Collection of the virtualization configuration is not supported for the host "host-name".

An attempt to collect the virtualization configuration from the host failed because collection of a SCVMM virtualization configuration from IM Configuration Management running on a UNIX OS is not supported.

S:

Stops collection of the virtualization configuration.

O:

Because collection of a SCVMM virtualization configuration from IM Configuration Management running on a UNIX OS is not supported, use IM Configuration Management running on a Windows OS to collect the virtualization configuration.

KNAN22068-E

Collection of the virtualization configuration failed for the host "host-name" because the environment is invalid.

An attempt to collect the virtualization configuration failed due to an incorrect environment.

S:

Stops collection of the virtualization configuration.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22069-E

The host name (host-name) contains invalid characters (Special Characters).

Host information cannot be collected.

Host information cannot be collected because the host name contains invalid characters.

S:

Does not collect host information.

O:

Perform either of the following:

Change the host name to remove the invalid characters, and then retry the operation.

Avoid collecting host information from a host whose name contains invalid characters.

KNAN22070-W

The virtual machine configuration collected from the host (host-name) contains at least one node that cannot acquire the host name.

The virtualization configuration collected from the host contains a node whose host name cannot be acquired.

S:

Continues processing.

O:

Check the following items:

Are the virtual hosts and VMM hosts managed by the virtualization environment management software in an environment supported by this software?

Are prerequisite products installed on the virtual hosts?

Can the actual host names of the virtual hosts be viewed in the window of the virtualization environment management software?

KNAN22071-W

The virtual machine configuration collected from the host (host-name) is partial as the configuration is not supported.

The virtualization configuration collected from the host is not supported.

S:

Continues processing.

O:

Because the virtualization configuration cannot be collected from the specified host, register the virtual host manually.

KNAN22072-E

The virtualization configuration cannot be collected for host "Host Name" because the password is not registered.

The virtualization configuration could not be collected because a password was not specified.

S:

Stops collection of the virtualization configuration.

O:

Set the password for the host, and then retry the operation.

KNAN22073-E

The virtualization configuration cannot be collected for host "Host Name" because the private key file name is not registered.

An attempt to collect the virtualization configuration has failed because a private key file path was not specified.

S:

Stops collection of the virtualization configuration.

O:

Set the private key file path for the host, and then retry the operation.

KNAN22100-E

An argument is incorrect.

An argument is incorrect.

S:

Does not collect host information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22101-E

Common definition initialization failed.

Common definition initialization failed.

S:

Does not collect host information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22102-E

The command jp1agentinfo will now stop because the logical host "host-name" does not exist.

The specified logical host does not exist.

S:

Does not collect host information.

O:

Specify a logical host that has already been configured.

KNAN22103-E

An internal error occurred. (Command name: jp1agentinfo, error code: error-code)

An internal error occurred.

S:

Does not collect host information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22104-E

The command command-name terminated abnormally. (error code = error-code)

The command terminated abnormally.

S:

Does not collect host information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22200-I

An agent configuration does not exist.

An agent configuration could not be acquired because it does not exist.

S:

Stops acquiring the IM configuration (system hierarchy).

KNAN22201-E

Acquisition of the agent configuration failed because the acquired configuration is invalid.

The acquired agent configuration is invalid.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Use the jbsrt_get command to check the agent configuration.

KNAN22202-E

Registration of the agent configuration failed because the maximum number of hosts (maximum-number-of-registered-hosts) was exceeded.

An agent configuration could not be registered because the maximum number of hosts that can be registered was exceeded.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Take one of the following measures:

Delete unnecessary hosts registered in the IM Configuration Management.

If the maximum-number-of-registered-hosts is 1,024, expand the size of the IM Database Service to the L size.

KNAN22203-E

Registration of the agent configuration failed because registration of the host "host-name" failed. (Cause: error-code)

The acquired agent configuration cannot be registered because an attempt to register the host information failed.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host has already been registered.

Enter a different host name, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22204-E

Registration of the agent configuration failed because writing to the database failed.

The agent configuration cannot be registered because an attempt to write to the IM Configuration Management database failed.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Make sure that there is sufficient disk space, memory, or other OS resources. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22205-E

Collection of the agent configuration failed because the local host name "host-name-1" is different from the registered host name "host-name-2".

The local host name in the agent configuration is different from the local host name registered in the host list.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Change the local host name to a host name used in the agent configuration, and then retry the operation.

KNAN22206-E

Acquisition of the agent configuration failed. (Cause: detailed-information)

The agent configuration cannot be acquired because an internal error occurred.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

If the following detailed information is displayed, take the indicated corrective action.

The execution environment of JP1/Base is invalid.

The JP1/Base configuration file could not be accessed.

Check the following items:

• Is the JP1/Base conf directory defined in the common definition?

• Did the JP1/Base configuration end normally?

An internal error occurred in JP1/Base during processing.

Check the following items:

• Is there sufficient memory?

• Has Configuration Management been started?

• Was JP1/Base restarted after JP1/IM was installed?

• Is there sufficient write and read permission for the conf/route/ directory?

An I/O error occurred.

Failed to read the configuration file.

Make sure that there is sufficient disk space, memory, or other OS resources. Also make sure that you have read permission for the configuration file.

A common definition could not be acquired.

The JP1/Base common definition information is not configured. Make sure that it is configured correctly.

If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22207-I

The collection of the IM compositions ended.

Acquisition of the IM configuration (system hierarchy) ended.

S:

Stops acquiring the IM configuration (system hierarchy).

KNAN22208-E

agent Configuration collection is failed. (Cause: Configuration includes incorrect host name (host-name).)

The agent configuration cannot be acquired because it contains an invalid host.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Execute the jbsrt_get command, and then make sure that the output host name satisfies the following conditions:

Does the host name begin and end with alphabetic or numeric characters?

Does the host name begin and end with a hyphen (-) or a period (.)?

If a host does not satisfy the above conditions, delete the host from the primary system configuration.

KNAN22209-I

The agent configuration does not exist. Do you want to apply the agent configuration stored on the server?

The agent configuration does not exist. This message asks you whether you want to apply the agent configuration stored on the server.

S:

Continues acquiring the IM configuration (system hierarchy).

KNAN22220-E

The IM configuration for the host "host-name" is invalid.

The IM structure (or the hierarchical structure of the system) on the manager host does not match the IM structure in the displayed host.

S:

Stops verification.

O:

Execute the jbsrt_get command on the indicated host to check the IM configuration.

If the IM configuration cannot be found by executing the jbsrt_get command, apply the IM configuration by using batch distribution, and then try to check the IM configuration again.

If the IM configuration is included in another IM configuration, revise the IM configurations, and then delete the former (the IM configuration to be checked) from the latter (the IM configuration that includes the IM configuration to be checked). Apply the information, and then try to check the IM configuration again.

If the host is a site manager and a higher-level host name is not displayed, use an integrated manager to synchronize the IM configurations.

If the host is an integrated manager and you want to use the configuration stored in IM Configuration Management, apply the IM configuration and then retry verification. To use the configuration stored in JP1/Base, acquire the IM configuration and then retry verification.

KNAN22221-E

IM configuration verification for the host "host-name" is not supported.

IM configuration (system hierarchy) verification is not supported for the version of JP1/Base on the host.

S:

Stops verification of the host and continues verification of the remaining hosts.

O:

Upgrade to JP1/Base version 09-00 or later. If you want to use a JP1/Base version earlier than 09-00, directly log in to the host, and then execute the jbsrt_get command to check the IM configuration.

KNAN22223-E

IM configuration information could not be acquired from the host "host-name". (Cause: detailed-information)

IM configuration information (system hierarchy) could not be acquired from the host.

S:

Stops verification of the host and continues verification of the remaining hosts.

O:

If the following detailed information is displayed, take the indicated corrective action.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

The connection destination host is busy.

Wait awhile, and then retry the operation.

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status with the acquired target.

A connection could not be established with the host.

Connection with the acquired host failed.

Check the network configuration and status with the acquired host.

Also make sure that JP1/Base is running on the acquired host.

The version of JP1/Base on the connection destination is not supported.

Make sure that the JP1/Base version is 09-00 or later.

Failed to receive the data from the connection destination host.

Failed to send the data to the connection destination host.

Check the OS resources and memory status, and then check the network configuration and status with the connection destination.

Also make sure that IM Configuration Management Service of the connection destination is running.

Connection with the host has ended.

A host connection timeout occurred.

Check the network configuration and status with the acquired host.

Also make sure that JP1/Base is running on the acquired host.

The configuration did not exist.

There is an invalid definition in the configuration file.

Execute the jbsrt_get command, and then make sure that the IM configuration (system hierarchy) exists on the host.

If no IM configuration (system hierarchy) exists, in the IM Configuration Management window, apply the IM configuration by using batch distribution.

Operations cannot be performed on the file.

Check the following items, and then retry the operation:

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

A common definition could not be acquired.

The JP1/Base common definition information is not configured. Make sure that it is configured correctly.

If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

KNAN22224-I

The IM configuration of the host "host-name" is normal.

The IM configuration (system hierarchy) on the host is normal.

S:

Continues verification of the remaining hosts.

KNAN22225-E

IM Configuration verification for the host (host-name) is failed. (Cause: DB Updation is failed.)

IM configuration verification failed because updating of the IM Configuration Management database failed.

S:

Continues verification of the remaining hosts.

O:

Confirm that the IM Configuration Management database is running, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22240-E

An attempt to apply the IM configuration failed because database registration failed. (details = error-code)

An attempt to register with the IM Configuration Management database failed.

S:

Stops applying the IM configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.

Check the following items, and then retry the operation:

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host does not exist.

Make sure that the host is registered in the host list of the IM Configuration Management window.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22241-E

An attempt to apply changes to the JP1/Base definition file (jbsrt_route.conf) failed.

An attempt to apply changes to the JP1/Base definition file (jbsrt_route.conf) failed.

S:

Stops applying the changes.

O:

Make sure that the user has write permission to the JP1/Base definition file (jbsrt_route.conf), and then retry the operation.

KNAN22243-E

An attempt to apply the IM configuration failed. (Cause: error-code)

An attempt to apply the IM configuration (system hierarchy) failed because an internal error occurred.

S:

Stops applying the IM configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.

Check the following items, and then retry the operation:

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22244-E

Cannot delete configuration for the host and its lower-level hosts. Try again after deleting configuration of the host "host-name" each definition separately.

An attempt to delete the IM configuration (system hierarchy) of the host and lower-level hosts failed.

S:

Stops deleting the IM configuration.

O:

Execute the jbsrt_del command from the displayed host and lower-level hosts, delete the IM configuration (system hierarchy), and then retry the operation.

KNAN22245-E

Cannot set configuration for the host. Please execute the action according to the manual and apply the IM configuration again. (host: host-name)

An attempt to apply the IM configuration (system hierarchy) failed for some hosts.

S:

Stops applying the IM configuration.

O:

Check the following items on the host where the error occurred:

Is JP1/Base running?

Is the JP1/Base Configuration Management port number the same as the port for an higher-level host of the host that had the error?

Are lower-level hosts defined for JP1/Base?

Is the higher-level host of JP1/IM - Manager JP1/IM - Satellite Console?

On the site manager or the relay manager, are 6 or more hosts defined directly below the JP1/IM - Central Console 5 Node?

On the site manager or the relay manager, are 11 or more hosts defined directly below the JP1/IM - Central Console 10 Node?

Can the host name of the host that had the error be resolved from the higher-level hosts?

Was the host that had the error defined as the previous topmost host? If the IM configuration (system hierarchy) defined as the topmost host remains, use the jbsrt_distrib command from the host that had the error to delete the IM configuration (system hierarchy).

Was JP1/Base restarted after JP1/IM was installed?

Is there sufficient memory?

Is there read and write permission for the JP1/Base installation directory and for the logical host shared disk conf/route/ directory?

If the problem is other than the above, take the following actions on the host with the error:

Execute the jbsrt_get command.

Determine whether any of the following occurred:

• Message KAVB3162-E was output.

• The jbsrt_get command finished abnormally.

• The local host name is displayed in Higher-level hosts or Lower-level hosts.

• A host name other than a local host is displayed in Local hosts.

• The host name is unintelligible.

If any of the above occurred, recover using the following method:

On the host for which the error occurred, execute the jbsrt_del command to delete the IM configuration (system hierarchy).

From the manager host, re-apply the IM configuration (system hierarchy) by using batch distribution.

KNAN22247-E

Application of the IM configuration failed because host host-name is not registered.

Application of the IM configuration failed because the host (host-name) is not registered.

S:

Stops applying the IM configuration.

O:

Make sure that the host is registered, and then retry the operation.

KNAN22248-I

Application of the IM configuration was successful.

The IM configuration (system hierarchy) was applied successfully.

S:

Stops applying the IM configuration.

KNAN22249-E

Application of the IM configuration failed. (Cause: "Detailed information")

Application of the IM configuration (system hierarchy) failed.

S:

Stops applying the IM configuration.

O:

Take one of the following actions depending on the detailed information.

A communication with JP1/Base failed.

Make sure that JP1/Base is running.

JP1/Base is busy.

Wait awhile, and then retry the operation.

A timeout occurred.

Check the following items:

• Has an error occurred on a lower-level host?

• If allocation of the definition takes too much time, the jbsrt_distrib command will time out. Revise the system configuration.

Failed to read the IM configuration definition file.

Check the following items:

• Is the configuration definition file in the correct location?

• Do you have write permission for the conf/route/ directory?

A communication error occurred with JP1/Base.

Check the following items:

• Revise the common definition jp1hosts.

• Make sure that the JP1/Base configuration ended normally.

If these actions do not resolve the problem, collect data, and then contact a system administrator.

The execution environment of JP1/Base is invalid.

Check the following items:

• Is the JP1/Base conf directory defined in the common definition?

• Did the JP1/Base configuration end normally?

An internal error occurred in JP1/Base during processing.

Check the following items:

• Is there sufficient memory?

• Has Configuration Management been started?

• Was JP1/Base restarted after JP1/IM was installed?

• Do you have write and read permission for the conf/route/ directory?

There is not the local host name in the IM configuration.

Define a local host in the configuration definition file.

Trap running for the removed Agentless host in the IM configuration.

Check whether the remote monitoring host for which a log file trap was started has been deleted from the IM configuration.

The IM configuration might have been changed.

Update the information to the latest host information, and then retry the operation.

KNAN22250-E

Synchronization of the IM configuration failed. Please execute the action according to the manual and execute the IM synchronization again. (host: host-name))

Synchronization failed because an error occurred on the displayed host.

S:

Stops synchronization.

O:

Determine whether JP1/Base is running on the host with the error. If it is running, take the following actions:

Execute the jbsrt_get command.

Determine whether any of the following occurred:

• Message KAVB3162-E was output.

• The jbsrt_get command ended abnormally.

• The local host name is displayed in Higher-level hosts or Lower-level hosts.

• A host name other than a local host is displayed in Local hosts.

• The host name is unintelligible.

If any of the above occurred, recover using the following methods:

On the host for which the error occurred, execute the jbsrt_del command to delete the IM configuration (system hierarchy).

From the manager host, re-apply the IM configuration (system hierarchy) by using batch distribution.

KNAN22251-E

Synchronization failed because the Base Manager is not defined.

Synchronization failed because the site manager is not defined.

S:

Stops synchronization.

O:

Define the site manager, and then retry the operation.

KNAN22252-I

Synchronization of the IM configuration ended successfully.

Synchronization ended successfully.

S:

Stops synchronization.

KNAN22253-E

Synchronization of the IM configuration failed because an error occurred during acquisition of the IM configuration. (error code = error-code)

An error occurred in the synchronized IM configuration (system hierarchy) during application to the IM Configuration Management database.

S:

Stops synchronization.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host does not exist.

Make sure that the host is registered in the host list of the IM Configuration Management window.

The Host host-name with the same name is defined

Execute the jbsrt_get command on the integrated manager, and make sure that the same host name is not defined for the integrated manager and site manager. If the same host name is defined, edit the IM configuration so that the host names are unique. Then apply and synchronize the IM configuration.

The local host name host-name is different from the registered host name host-name.

The local host in the agent configuration applied to JP1/Base might have an alias host name. Apply the agent configuration, and then retry the operation.

The maximum number of hosts (maximum limit) was exceeded.

The number of hosts in the agent configuration applied to JP1/Base exceeded the maximum. Delete unnecessary hosts and then apply the agent configuration. Alternatively, consider expanding the size of the IM Configuration Management database.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22254-E

Synchronization of the IM configuration failed. (Cause: error-code)

Synchronization failed.

S:

Stops synchronization.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22255-E

IM Configuration synchronization is failed. (Cause: detailed-message)

Synchronization failed.

S:

Stops synchronization.

O:

If the following detailed information is displayed, take the indicated corrective action.

An internal error occurred in JP1/Base during processing.

Check the following items:

• Is there sufficient memory?

• Has Configuration Management been started?

• Was JP1/Base restarted after JP1/IM was installed?

• Do you have write and read permission for the conf/route/ directory?

A communication with JP1/Base failed.

Make sure that JP1/Base is running.

JP1/Base is busy.

Wait awhile, and then retry the operation.

The IM configuration does not exist.

Execute the jbsrt_get command, and then make sure that the IM configuration (system hierarchy) exists on the host.

If there is no IM configuration (system hierarchy), use the IM Configuration Management window to refresh it.

A timeout occurred.

Check the network configuration and status with the acquired host.

Also make sure that JP1/Base is running on the acquired host.

The execution environment of JP1/Base is invalid.

Check the following items:

• Is the JP1/Base conf directory defined in the common definition?

• Did the JP1/Base configuration end normally?

The JP1/Base configuration file could not be accessed.

Make sure that the access permission to the file has been set correctly. Also determine whether the file has been opened (locked) by another application.

A communication error occurred with JP1/Base.

Check the following items:

• Revise the common definition jp1hosts value.

• Make sure that the JP1/Base configuration ended normally.

If these actions do not resolve the problem, collect data, and then contact a system administrator.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22263-E

Acquisition of the agent configuration information failed because a database access error occurred. (Cause: error-code)

The agent configuration could not be acquired because an access error occurred.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host does not exist.

Make sure that the host is registered in the host list of the IM Configuration Management window.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22264-E

The host name (host-name) contains invalid characters (Special Characters).

The IM configuration cannot be changed because the host name contains invalid characters.

S:

Cancels processing.

O:

Perform either of the following:

Change the host name to remove the invalid characters.

Remove the host with the name containing invalid characters from the IM configuration.

KNAN22265-E

Remote connection was not possible. (Host name: host-name, Detail information: Detail information)

Verification of the IM configuration failed because a remote connection was not possible.

S:

Cancels processing.

O:

An attempt to connect monitored host failed.

The collection of log files did time-out.

If this message appears at startup of a remote log-file trap and the OS of the monitored host is UNIX, check the following items, and then restart the remote log-file trap.

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

If this message appears at startup of a remote log-file trap and the OS of the monitored host is Windows, check the following items, and then restart the remote log-file trap.

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Has the number of connections exceeded the maximum for Windows?

If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

If this message appears at startup of a remote event-log trap, check the following items, and then restart the remote event-log trap.

• Is communication with the monitored host possible?

• Has the password for the user who logs in to the monitored host expired?

• Has the remote communication type for the monitored host name been set correctly?

• Is the WMI service running?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

• Check the load on the system.

• Make sure that the host is running.

• Check whether the number of connections exceeds the maximum.

• Make sure that the IM host account has been specified correctly in the system common settings.

Remote communication settings have not been configured.

Configure the remote communication settings.

Authentication failed.

If this message appears at startup of a remote log-file trap and the OS for the monitored host is UNIX, check the following item:

• Has SSH authentication been configured correctly?

If no error is found by checking the above item, make sure that the SSH connection has been configured correctly.

If this message appears at startup of a remote log-file trap and the OS for the monitored host is Windows, check the following item:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

If no error is found by checking the above item, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

Acquisition of an SSH private key failed.

Make sure that a private key exists on the manager host.

Creation of the jcfallogtrap process failed.

Check the IM host account specified in the system common settings.

KNAN22266-E

Acquisition of the remote monitoring configuration information failed because a database access error occurred. (Details: Error code)

The remote monitoring configuration could not be acquired.

S:

Does not acquire the remote monitoring configuration.

O:

IM Configuration Management database access error.

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start the IM data service.

The host does not exist.

Make sure that the host is registered in the host list of the IM Configuration Management Window.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22267-E

Synchronization of the remote monitoring configuration failed. (Details: details)

An attempt to synchronize remote monitoring connections has failed.

S:

Stops synchronization.

O:

Check the following items:

Can the monitored host name be resolved?

Is the monitored host running?

Is IM Configuration Management running on the site manager?

Are the firewall settings on the monitored host correct?

Is there any problem with the network connection for the monitored host?

If the communication encryption function is enabled on the base manager host, have root certificates been set on the higher manager host?

KNAN22270-E

Invalid response received from the base manager host. (Host name: host-name)

A response from the site manager is invalid.

S:

Stops synchronization.

O:

Check the version of the site manager. Make sure that the IM database service on the site manager is running.

KNAN22271-I

The agent configuration is deleted.

The agent configuration will be deleted.

S:

Deletes the agent configuration.

KNAN22272-I

The agent configuration is updated.

The agent configuration will be updated.

S:

Updates the agent configuration.

KNAN22273-I

The agent configuration was reflected.

This message indicates that execution of the jbsrt_distrib command has terminated by application of the agent configuration.

KNAN22274-I

Changes made to the agent configuration will be reflected.

Changes to the agent configuration will be applied.

S:

Applies the changes to the agent configuration.

KNAN22300-I

The virtualization configuration was applied successfully to the Central Scope monitoring tree.

The virtualization configuration was applied to the central scope monitoring tree.

S:

Finishes applying the virtualization configuration to the central scope monitoring tree.

KNAN22301-E

The virtualization configuration could not be applied to the Central Scope monitoring tree because an attempt to output the virtualization configuration failed. (cause = Detailed Information)

The virtualization configuration could not be applied to the central scope monitoring tree.

S:

Stops application of the virtualization configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

Make sure that there are sufficient OS resources such as disk space and memory.

If detailed information other than the above is displayed, check the following items:

Has the central scope been set up correctly? Has the service started normally?

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22302-E

The virtualization configuration could not be applied to the Central Scope monitoring tree because the user "user name:Client host name" is currently performing the same operation.

The virtualization configuration cannot be applied to the central scope monitoring tree because another user is performing the same operation.

S:

Stops application of the virtualization configuration.

O:

Wait a while, and then retry the operation.

KNAN22303-E

The virtualization configuration could not be applied to the Central Scope monitoring tree because an attempt to export the Central Scope monitoring tree failed. (cause = Detailed Information)

The virtualization configuration could not be applied to the central scope monitoring tree.

S:

Stops application of the virtualization configuration.

O:

Make sure that the jcsdbexport command can be executed. If the jcsdbexport command can be executed normally, use the data collection tool to collect data, and then contact a system administrator.

KNAN22304-E

The virtualization configuration could not be applied to the Central Scope monitoring tree because an attempt to create the monitoring tree failed. (cause = Detailed Information)

The virtualization configuration could not be applied to the central scope monitoring tree.

S:

Stops application of the virtualization configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

There is not enough disk space.

Make sure that there are sufficient OS resources such as disk space and memory.

If detailed information other than the above is displayed, check the following items:

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22305-E

The virtualization configuration could not be applied to the Central Scope monitoring tree because an attempt to import the virtualization configuration into the Central Scope monitoring tree failed. (cause = Detailed Information)

The virtualization configuration could not be applied to the central scope monitoring tree.

S:

Stops application of the virtualization configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

There is not enough disk space.

Make sure that there are sufficient OS resources such as disk space and memory.

Central Scope is busy.

Wait a while, and then retry the operation.

If detailed information other than the above is displayed, check the following items:

Has the central scope been set up correctly? Has the service started normally?

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22306-E

An attempt to apply the virtualization configuration to the Central Scope monitoring tree has failed. (cause =Detailed Information)

The virtualization configuration could not be applied to the central scope monitoring tree.

S:

Stops application of the virtualization configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

Make sure that there are sufficient OS resources such as disk space and memory.

Central Scope is busy.

Wait a while, and then retry the operation.

If detailed information other than the above is displayed, check the following items:

Has the central scope been set up correctly? Has the service started normally?

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22307-I

Business groups were applied successfully to the Central Scope monitoring tree.

The business groups were applied to the central scope monitoring tree.

S:

Finishes applying the business groups to the central scope monitoring tree.

KNAN22308-E

Business groups could not be applied to the central scope monitoring tree because an attempt to output business groups failed. (Details: Detailed Information)

The business groups could not be applied to the central scope monitoring tree.

S:

Stops application of the business groups.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

Make sure that there are sufficient OS resources such as disk space and memory.

If detailed information other than the above is displayed, check the following items:

Has the central scope been set up correctly? Has the service started normally?

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22309-E

Business groups could not be applied to the central scope monitoring tree because the user "user name:Client host name" is currently performing the same operation.

The business groups cannot be applied to the central scope monitoring tree because another user is performing the same operation.

S:

Stops application of the business groups.

O:

Wait a while, and then retry the operation.

KNAN22310-E

Business groups could not be applied to the central scope monitoring tree because an attempt to export the central scope monitoring tree failed. (Details: Detailed Information)

The business groups could not be applied to the central scope monitoring tree.

S:

Stops application of the business groups.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

There is not enough disk space.

Make sure that there are sufficient OS resources such as disk space and memory.

Central Scope is busy.

Wait a while, and then retry the operation.

If detailed information other than the above is displayed, check the following items:

Has the central scope been set up correctly? Has the service started normally?

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22311-E

Business groups could not be applied to the central scope monitoring tree because an attempt to create the monitoring tree failed. (Details: Detailed Information)

The business groups could not be applied to the central scope monitoring tree.

S:

Stops application of the business groups.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

There is not enough disk space.

Make sure that there are sufficient OS resources such as disk space and memory.

Generation of the Central Scope import files failed because the version of the Central Scope export file data was old.

Execute the jp1csverup command to upgrade the central scope data to the latest version.

If detailed information other than the above is displayed, check the following item:

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22312-E

Business groups could not be applied to the central scope monitoring tree because an attempt to import business groups into the central scope monitoring tree failed. (Details: Detailed Information)

The business groups could not be applied to the central scope monitoring tree.

S:

Stops application of the business groups.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

There is not enough disk space.

Make sure that there are sufficient OS resources such as disk space and memory.

Central Scope is busy.

Wait a while, and then retry the operation.

If detailed information other than the above is displayed, check the following items:

Has the central scope been set up correctly? Has the service started normally?

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22313-E

An attempt to apply business groups to the central scope monitoring tree has failed. (Details: Detailed Information)

The business groups could not be applied to the central scope monitoring tree.

S:

Stops application of the business groups.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is not enough memory.

Make sure that there are sufficient OS resources such as disk space and memory.

Central Scope is busy.

Wait a while, and then retry the operation.

If detailed information other than the above is displayed, check the following items:

Has the central scope been set up correctly? Has the service started normally?

Was an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22314-E

An attempt to apply the changes of business groups to the system failed because database registration failed.

An attempt to apply the business groups failed because an attempt to register information to the IM Configuration Management database failed.

S:

Stops application of the business groups.

O:

Check the following items:

Execute the jimdbstatus command to make sure that the IM database service is running. If the IM database service is not running, start it.

Check whether an error message was output to the integrated trace log of the manager.

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22315-E

An attempt to apply the changes of business groups to the central console failed.

An attempt to apply the edited information for business groups failed because an attempt to apply information to the central console failed.

S:

Stops application of the business groups.

O:

Check the following items:

Execute the jimdbstatus command to make sure that the IM database service is running. If the IM database service is not running, start it.

Check whether an error message output to the integrated trace log of the manager?

If an error message was output, take the corrective action given for that message.

If the problem cannot be solved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN22316-I

Edited business groups were applied to the system.

The business groups were applied.

S:

Finishes applying the business groups.

KNAN22317-I

A business group "business-group-name" was added.

A business group was added.

S:

Finishes adding a business group.

KNAN22318-I

A business group "business-group-name" was deleted.

The business group was deleted.

S:

Finishes deleting the business group.

KNAN22319-I

A host "host-name" was registered to the business group "business-group-name".

The host was added to the business group.

S:

Finishes adding the host to the business group.

KNAN22320-I

A host "host-name" was unregistered from the business group "business-group-name".

The host was unregistered from the business group.

S:

Finishes unregistering the host from the business group.

KNAN22321-E

An attempt to apply the changes of business groups to the system failed because the sum total of business groups and monitoring groups reached the limit (Upper limit).

The total number of business groups and monitoring groups has reached the limit.

S:

Suspends processing.

O:

Delete unnecessary business groups and monitoring groups, and then retry the operation.

KNAN22400-I

The profile list was acquired successfully.

Acquisition of the manageable profile list ended successfully.

KNAN22401-E

Acquisition of the profile list failed because the host type is not selected.

Acquisition of the manageable profile list failed because the host type is not selected.

S:

Stops acquisition of the profile list.

O:

In the Edit Host Properties window, select the host type, and then retry the operation.

KNAN22402-E

Collection of the profile list failed because host information has not been acquired.

Acquisition of the manageable profile list failed because the host information is not valid.

S:

Stops acquisition of the profile list.

O:

Correct the host information acquisition in the Edit Host Properties window.

KNAN22403-E

Acquisition of the profile list failed. (Detail Information: detailed-information)

Acquisition of the manageable profile list failed because a connection could not be established with the host.

S:

Stops acquisition of the profile list.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.

The agent configuration on the manager might be different from the agent configuration enabled in the system, or the agent configuration on the manager might have been deleted.

In the IM Configuration Management window, click Operation, and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If the agent configurations do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to use batch distribution to make the agent configurations match. Also, check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

Another session has exclusive rights.

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Make sure that JP1/Base is running on agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A communication error occurred.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running, a correct communication method is set, and JP1/Base is configured correctly.

If JP1/Base is not running, take the following actions:

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The processing is busy. Please try again.

Wait awhile, and then retry the operation.

A memory shortage occurred on the manager host.

Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.

Make sure that there is enough free memory on the agent host, and then retry the operation.

The configuration file for rollback failed to be created.

Make sure that the target configuration file and/or the log-file trap startup definition file which are in the following path have read permission, or are not locked by other application.

In Windows: Base-path\conf

In UNIX: /etc/opt/jp1base/conf

Check the network condition and status with the agent host.

Also make sure that JP1/Base is running on the agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22404-E

Acquisition of the profile list failed because the specified host is not registered.

Acquisition of the manageable profile list failed because the host is not registered in the host list.

S:

Stops acquisition of the profile list.

O:

Make sure that the host is correctly registered in the host list of the IM Configuration Management window.

KNAN22405-E

Acquisition of the profile list failed because a database access error occurred. (Cause: detailed-information)

Acquisition of the manageable profile list failed.

S:

Stops acquisition of the profile list.

O:

If the following detailed information is displayed, take the indicated corrective action.

The OS information does not exist.

In the IM Configuration Management window, make sure that the OS type is displayed in the host information.

If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The profile has already been registered.

The profile name is already in use by a process or service. Use a different profile name.

It is possible that multiple log file traps have been started from the same configuration file.

Log in to the agent machine, and then start only one log file trap for each configuration file.

If you want to start multiple log file traps in the same definition, copy the contents to a file with a different name, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22406-E

Acquisition of the profile list failed. (Cause: error-code)

Acquisition of the manageable profile list failed because of an internal error.

S:

Stops acquisition of the profile list.

O:

If the following detailed information is displayed, take the indicated corrective action.

The product does not exist.

In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.

If JP1/Base is not displayed, click Operation, and then Collect Host Information, and then retry the operation.

If the target host is the local host, the agent configuration was not applied. Apply the agent configuration, and then retry the operation.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status with the acquired host.

A required service or process is not running.

Make sure that all of the JP1/Base processes started normally.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

The configuration file name is already in use by a log file trap.

Make sure that the configuration file name for the running log file trap is not specified for the log file trap in the startup definition file.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22407-E

Collection of the profile list failed because the specified host is not in the agent configuration.

The profiles cannot be collected because the host is not included in the agent configuration.

S:

Stops acquisition of the profile list.

O:

Include the host in the agent configuration, and then retry the operation.

KNAN22408-E

Collection of the profile list failed because the product "product-name" does not exist on the specified host.

Acquisition of the profile list failed because the product could not be found on the host.

S:

Stops acquisition of the profile list.

O:

Make sure that JP1/Base is installed and running on the host, and then retry the operation.

KNAN22409-E

Collection of the profile list failed because the specified host is not a managed host.

Acquisition of the profile list cannot be performed because the specified host is not a managed host.

S:

Stops acquisition of the profile list.

O:

Add the specified host to the IM configuration (system hierarchy), and then retry the operation.

KNAN22410-E

Acquisition of the profile list failed because the profile "profile-type" is not usable.

Acquisition of the profile list failed because the profile is not usable.

S:

Stops acquisition of the profile list.

O:

Check the following items:

Is the network activated?

Is JP1/Base running?

KNAN22411-W

Collection of the profile list was interrupted because the maximum number profile-type that can be managed for product-name was exceeded.

Acquisition of the profile list was suspended because the maximum number of profiles that can be managed was exceeded.

S:

Stops acquisition of the profile list.

O:

Start a number of processes that does not exceed the maximum number of manageable configuration files that are defined on the server. Alternatively, change the maximum number of manageable configuration files, and then retry the operation.

KNAN22412-E

Profile management failed because the host name of host host-name is defined with IP address. Please define real host name.

Profile management failed because the name of the specified host is defined by an IP address.

S:

Stops display of the Display/Edit Profiles window for the host.

Also skips batch collection and batch application processing for that host only (other hosts can undergo normal collection and application).

O:

Use the following procedure to change the IP address to the host name:

In the host list, select the host for which the host name is given as an IP address.

On the menu bar, click Edit, and then Edit Host Properties.

In the Edit Host Properties window, change the host name.

Open the Edit Agent Configuration window or Edit Remote Monitoring Configuration window, and then apply the setting.

KNAN22413-E

Collection of the profile list failed because host information (host information type) has not been acquired.

An attempt to acquire the list of manageable profiles failed because host information for the target host was not collected.

S:

Stops acquisition of the profile list.

O:

In the IM Configuration Management window, collect the host information again.

KNAN22414-W

A part of profile is displayed because host information (host information type) has not been acquired.

Only the profiles that can be displayed are displayed because part of the host information for the target host was not collected.

S:

Continues acquisition of the profile list.

O:

To display all profiles, in the IM Configuration Management window, collect the host information again.

KNAN22415-E

Batch application processing of host-name was not performed because host information (agent) has not been collected.

Batch application processing for the host cannot be performed because host information was not collected.

S:

Stops application of the configuration file.

O:

Collect the host information again, and then retry the operation.

KNAN22421-I

Operation definition information for profile-type was collected successfully.

Acquisition of operation definition information ended successfully.

S:

Acquires operation definition information.

KNAN22422-E

Collection of operation definition information for profile-type failed. (Detail Information: detailed-information)

Acquisition of operation definition information failed because a connection could not be established with the managed host.

S:

Stops acquisition of operation definition information.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.

The agent configuration on the manager might be different from the agent configuration enabled in the system, or the agent configuration on the manager might have been deleted.

In the IM Configuration Management window, click Operation, and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If the agent configurations do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to use batch distribution to make the agent configurations match. Also, check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

Another session has exclusive rights.

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A communication error occurred.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If JP1/Base is not running, take the following actions:

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The processing is busy. Please try again.

Wait awhile, and then retry the operation.

A memory shortage occurred on the manager host.

Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.

Make sure that there is enough free memory on the agent host, and then retry the operation.

A memory shortage occurred on the manager host.

Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.

Make sure that there is enough free memory on the agent host, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22423-E

Collection of operation definition information failed because the host is not registered.

Acquisition of operation definition information failed.

S:

Stops acquisition of operation definition information.

O:

In the host list of the IM Configuration Management window, make sure that the managed host is registered correctly.

KNAN22424-E

Collection of operation definition information for profile-type failed. (Cause: detailed-information)

Acquisition of operation definition information failed because of an error.

S:

Stops acquisition of operation definition information.

O:

If the following detailed information is displayed, take the indicated corrective action.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The product is not supported.

In the IM Configuration Management window, make sure that the version of JP1/Base displayed in the product information is 09-00 or later. If the JP1/Base version is 09-00 or later, click Edit IM Configuration, and then confirm again that the version of JP1/Base is 09-00 or later.

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status with the acquired host.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

No authentication servers have been set up.

Register an authentication server using the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX), and then re-execute the command.

User mapping has not been registered.

The user mapping information was not registered, or the mapping information file may be corrupted. Re-execute the user mapping configuration command.

The execution environment of JP1/Base is invalid.

Re-register an authentication server using the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX), and then re-execute the command.

If the error cannot be resolved, check the following items:

• Is the JP1/Base conf directory defined in the common definition?

• Did the JP1/Base configuration end normally?

• In Windows: Is there a problem with access permission to the blockade file in the installation destination folder \jp1base\conf\user_acl\blockade?

• In UNIX: Is there a problem with access permission to the blockade file in the /etc/opt/jp1base/conf/user_acl/blockade directory?

The specified event log trap is not running.

The event log trap might have been stopped by another user or might have terminated abnormally. Check the log data for the event log trap in the integrated trace log.

The specified log file trap is not running.

The log file trap might have been stopped by another user or might have terminated abnormally. Check the log data for the log file trap in the integrated trace log.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22425-I

The contents of the configuration file "file-name" for profile-type was collected successfully.

Acquisition of the contents of the configuration file ended successfully.

S:

Acquires the contents of the configuration file.

KNAN22426-E

Collection of the contents of the configuration file "file-name" for profile-type failed. (Detail Information: detailed-information)

Acquisition of the contents of the configuration file failed because a connection could not be established with the managed host.

S:

Stops acquisition of the contents of the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.

The agent configuration on the manager might be different from the agent configuration enabled in the system, or might have been deleted.

In the IM Configuration Management window, click Operation, and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If the agent configurations do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to use batch distribution to make the agent configurations match. Also, check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

Failed to read the configuration file.

Make sure that you have read permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have read permission for the JP1/Base conf directory on the target host.

Another session has exclusive rights.

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Make sure that JP1/Base is running on agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

The file does not exist.

• For Log File Trapping:

Stop log file traps and starting log file traps.

• For Event Forwarding, Event Log Trapping, or Local Action:

Make sure that the displayed configuration file or directory exists and that it is accessible.

If it does not exist, create a configuration file on the agent host and then retry the operation.

The directory does not exist.

Make sure that specified file or directory by the log-file trap startup definition file exists and that it is accessible.

Make sure that the specified file or directory exists and that it is accessible.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A communication error occurred.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If JP1/Base is not running, take the following actions:

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The processing is busy. Please try again.

Wait awhile, and then retry the operation.

A memory shortage occurred on the manager host.

Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.

Make sure that there is enough free memory on the agent host, and then retry the operation.

A system error occurred.

Make sure the output destination of the displayed configuration file and the log-file trap startup definition file does not contain a directory of the same name as the that file.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

The configuration file for rollback failed to be created.

Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22427-E

Collection of operation definition information failed because a database access error occurred. (Cause: error-code)

Acquisition of operation definition information failed because an IM Configuration Management database access error occurred.

S:

Stops acquisition of operation definition information.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

The OS information does not exist.

In the IM Configuration Management window, make sure that the OS type is displayed in the host information.

If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22428-E

Collection of the configuration file "file-name" for profile-type failed because an attempt to save the profile file failed.

Acquisition of the contents of the configuration file failed.

S:

Stops acquisition of the contents of the configuration file.

O:

Check the following items:

Do the file and directory exist, and are they accessible?

Has sufficient disk space been allocated?

KNAN22429-E

Collection of the configuration file "file-name" for profile-type failed. (Cause: error-code)

Acquisition of the contents of the configuration file failed because of an internal error.

S:

Stops acquisition of the contents of the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status with the acquired host.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) has been deleted.

Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22430-E

Batch collection of profiles failed because the user user-name:View-host-name is executing the batch operation "batch-collection/reflection".

Batch collection of profiles failed because another user is executing batch collection or application of profiles.

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after the other user's batch collection or application finishes.

KNAN22432-E

Collection of product-name of the host "host-name" failed because the system is now performing batch collection of profiles. (Cause: error-code)

Profile collection on the host failed because the system is now performing batch collection of profiles.

S:

Stops batch collection of profiles.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22433-E

Collection of the configuration file "file-name" for profile-type failed because another user is currently accessing the file.

Acquisition of the configuration file failed because another user is currently accessing the file.

S:

Stops acquisition of the contents of the configuration file.

O:

Wait awhile, and then retry the operation.

KNAN22435-E

Batch collection of profiles failed because a database access error occurred. (Cause: error-code)

Batch collection of profiles failed because an IM Configuration Management database access error occurred.

S:

Stops batch collection of profiles.

O:

If the following detailed information is displayed, take the indicated corrective action.

The product does not exist.

In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.

If JP1/Base is not displayed, click Operation, and then Collect Host Information, and then retry the operation.

The profile does not exist.

Check the profile collection status in the IM Configuration Management window, and then determine whether profile collection is completed or partially completed.

The OS information does not exist.

In the IM Configuration Management window, make sure that the OS type is displayed in the host information.

If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22437-E

Batch collection of profiles failed because the host does not exist in the database.

Processing failed because the host could not be found in the IM Configuration Management database.

S:

Stops batch collection of profiles.

O:

In the host list in the IM Configuration Management window, make sure that the managed host is registered correctly.

KNAN22438-E

Collection of the configuration file failed because the host is not registered.

Acquisition of the configuration file failed because the host is not registered.

S:

Stops acquisition of the contents of the configuration file.

O:

In the host list in the IM Configuration Management window, make sure that the managed host is registered correctly.

KNAN22439-E

Collection of the configuration file failed because a database access error occurred. (Cause: error-code)

Acquisition of the configuration file failed because of an error in the IM Configuration Management database access.

S:

Stops acquisition of the contents of the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

The product does not exist.

In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.

If JP1/Base is not displayed, click Operation, and then Collect Host Information, and then retry the operation.

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The profile does not exist.

Check the profile collection status in the IM Configuration Management window, and then determine whether profile collection is completed or partially completed.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

The OS information does not exist.

In the IM Configuration Management window, make sure that the OS type is displayed in the host information.

If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22440-E

Collection of the configuration file "file-name" for profile-name failed because the specified profile type is not supported for logical hosts.

Acquisition of the configuration file failed because the specified profile type is not supported for logical hosts.

S:

Stops acquisition of profiles.

O:

The environment is invalid.

Re-install JP1/IM - Manager.

KNAN22441-E

Profile information for the host "host-name" cannot be collected using batch acquisition because the host information is locked by the user "user-name:View-host-name ".

Batch collection processing failed because another user has acquired exclusive permission to the host information.

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after exclusive access is released.

KNAN22442-E

Profile information for the host "host-name" cannot be collected using batch acquisition because the host information is being updated.

Batch collection processing failed because the host information is being updated.

S:

Stops batch collection of profiles.

O:

Collect the most recent information, and then retry the operation.

KNAN22443-E

product-name of "host-name" cannot be collected using batch collection because the profile information is locked by the user "user-name:View-host-name".

Batch collection processing failed because another user has acquired exclusive permission to the profile information.

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after exclusive access is released.

KNAN22444-E

product-name of "host-name" cannot be collected using batch collection because profile information is being updated.

Batch collection processing failed because the profile information is being updated.

S:

Stops batch collection of profiles.

O:

Acquire the most recent information, and then retry the operation.

KNAN22445-E

Batch collection cannot be performed because the IM configuration tree is being updated.

Batch collection cannot be performed because the IM configuration information (system hierarchy information) is being updated.

S:

Stops batch collection of profiles.

O:

Acquire the most recent information, and then retry the operation.

KNAN22446-E

Batch collection cannot be performed because the IM configuration is being locked by the user "user-name:View-host-name".

Batch collection cannot be performed because update permission is being acquired for the IM configuration information (system hierarchy information).

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after update permission is released.

KNAN22447-E

Batch collection cannot be performed because IM configuration verification is being performed by the user user-name:View-host-name.

Batch collection cannot be performed because the user is performing verification of the IM configuration information (system hierarchy information).

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Wait awhile, and then retry the operation.

KNAN22448-E

Batch collection terminated abnormally.

Batch collection ended abnormally.

S:

Stops batch collection of profiles.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22449-I

Setup file "file-name" for profile-type does not exist in Agent host.

The configuration file could not be found in the agent host.

S:

Stops acquisition of the contents of the configuration file.

O:

Make sure that the configuration file exists on the agent host and that it is accessible, and then retry the operation.

KNAN22451-E

The profile "monitoring-target-name" cannot be deleted because the it is running.

The profile cannot be deleted because it is running.

S:

Suspends processing.

O:

Stop the profile, and then retry the operation.

KNAN22452-E

Creation of the configuration file "file-name" for Profile type failed because the maximum number of files for Profile type has been exceeded.

An attempt to create the configuration file failed because the maximum number of configuration files that can be defined on the agent host was exceeded.

S:

Suspends processing.

O:

Click Operation, and then Rebuild Profile Tree. Then make sure that the maximum number of manageable configuration files that are defined on the agent host is not exceeded.

KNAN22454-E

Creation of the configuration file "file-name" for Profile type failed because a file with the same name already exists.

An attempt to create the configuration file failed because another configuration file with the same name exists on the agent host.

S:

Suspends processing.

O:

Check for a log file trap that has the same name as the configuration file.

If such a log file trap exists, change the monitoring target name, and then add the log file trap.

KNAN22455-I

Changes to the configuration file "file-name" of profile-type were successfully saved on the server.

Changes to the profile were successfully saved on the server.

S:

Saves the configuration file on the server.

KNAN22456-E

Application of the configuration file failed because a database access error occurred. (Cause: error-code)

Changes could not be made to the profile on the server.

S:

Stops saving the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

OS information does not exist.

In the IM Configuration Management window, make sure that the OS type is displayed in the host information.

If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22457-E

The configuration file "file-name" for profile-type could not be saved. (Cause: error-code)

Changes could not be made to the profile on the server because of an internal error.

S:

Stops saving changes to the profile on the server.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Has the file access permission been set correctly?

• Has the file been opened (locked) by another application?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22458-I

Exclusive edit rights for product-name of the host "host-name" were successfully acquired.

Exclusive edit permission was successfully acquired.

S:

Acquires exclusive edit permission.

KNAN22459-E

An attempt to save the configuration file "file-name" for profile-type failed because another user is currently accessing the file.

An attempt to acquire exclusive access permission failed because another user has acquired exclusive access permission for the host or product.

S:

Stops saving the configuration file.

O:

Wait awhile, and then retry the operation.

KNAN22460-I

Editing changes were successfully applied to the configuration file "file-name" for profile-type.

Changes made to the profile on the server were applied to the agent host profile.

S:

Applies changes to the configuration file.

KNAN22461-E

Batch application of profiles failed because the user user-name:View-host-name is executing a batch "collection/reflection" operation.

Batch application of profiles failed because another user is performing batch profile collection or application.

S:

Stops batch application of profiles.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive access permission, and click the Release Exclusive Editing button to release exclusive access permission.

Wait until batch collection or application by the other user has finished, and then retry the operation.

KNAN22462-E

Creation of the configuration file "file-name" for Profile type failed. (Cause: Error code)

An attempt to create the configuration file failed due to an incorrect environment.

S:

Suspends processing.

O:

Re-install JP1/IM - Manager, and then retry the operation.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect data, and then contact a system administrator.

KNAN22463-E

During batch application of profiles, an attempt to apply the changes of product-name of the host "host-name" failed, because the profile list for the product does not exist in the database.

An attempt to apply the profile of a host failed during batch application of profiles.

S:

Stops batch application of profiles.

O:

Check the following items, and then retry the operation.

Is profile collection complete?

Can the contents of the profile be referenced from the Display/Edit Profiles window?

KNAN22464-I

Editing changes were successfully applied to the profile for log file trapping "monitoring-target-name".

Profile changes made on the server were applied to the agent host profile.

S:

Applies changes to the configuration file.

KNAN22465-E

Creation of the configuration file "file-name" for profile-type failed because a new profile cannot be created in this version of JP1/Base.

Creation of the configuration file is not supported for the version in use.

S:

Terminates processing.

O:

Use a version for which creation of the configuration file is supported.

KNAN22466-E

Application of changes failed because an error occurred when moving the configuration file "file-name" for profile-type. (Detail Information: detailed-information)

An attempt to apply changes failed because a connection could not be established with the agent host.

S:

Stops application of changes to the agent host.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.

The agent configuration on the manager might be different from the agent configuration enabled in the system, or the agent configuration on the manager might have been deleted.

In the IM Configuration Management window, click Operation, and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If the agent configurations do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to use batch distribution to make the agent configurations match. Also, check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

Failed to write the configuration file.

Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have write permission for the JP1/Base conf directory on the target host.

Failed to read the configuration file.

Make sure that you have read permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have read permission for the JP1/Base conf directory on the target host.

Another session has exclusive rights.

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Make sure that JP1/Base is running on agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

The directory does not exist.

Make sure that the specified directory exists and is accessible.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following corrective actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

A communication error occurred.

Check the condition and status of the network with the acquired managed host.

Also make sure that JP1/Base is running.

If JP1/Base is not running, take the following corrective actions:

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

The processing is busy. Please try again.

Wait awhile, and then retry the operation.

A service or process failed to reload.

Make sure that the relevant service or process is running and that the configuration file is correctly formatted.

If it is not running, take the following corrective actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

A memory shortage occurred on the manager host.

Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.

Make sure that there is enough free memory on the agent host, and then retry the operation.

IM Configuration Management database-access error

Execute the jimdbstatus command to check whether the IM database service is running, start it, and then retry the operation.

The log file trap service is not running.

Check whether the log file trap service is running. If the log file trap service is not running, start it, and then retry the operation.

The start options were invalid.

Check the following items:

• Is the startup option specified correctly?

• Is the -f or -a option specified as an additional option?

The log file trap of the monitoring target name "monitoring-target-name" has already been started.

Check the log file trap running on the agent host.

The syntax of the configuration file is invalid, or the specified log file does not exist.

Check the following items:

• Are the contents of the configuration file correct? Does the specified log file exist?

• If the specified log file path contains space characters, is it enclosed in double quotation marks (")?

• Does the specified startup locale exist on the agent host?

• If a multi-process trace file is monitored, is HTRACE specified for the FILETYPE parameter in the configuration file?

• Is the log file trap service running?

• Are there sufficient OS resources, such as disk space and memory, on the agent host?

If the problem cannot be solved by taking the above actions, execute the JP1/Base jevlogstart command, which starts a log file trap, on the agent host by specifying the same settings as those specified for IM Configuration Management. Then make sure that the log file trap starts normally. If the jevlogstart command does not start the log file trap normally, take the corrective action for the displayed error message. If the jevlogstart command starts the log file trap normally, use the JP1/IM - Manager data collection tool to collect data, and then contact a system administrator.

The event service is not running.

Make sure that the event service on the agent is running.

The configuration file for rollback failed to be created.

Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22467-E

Application of the configuration file failed because the host is not registered.

Application of changes to the agent host failed.

S:

Stops application of changes to the agent host.

O:

In the IM Configuration Management window, open the host list and make sure that the managed host is registered correctly.

KNAN22468-E

Application of changes to the configuration file "file-name" for profile-type failed. (Cause: error-code)

Application of changes to the agent host failed due to an internal error.

S:

Stops application of changes to the agent host.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Is the file access permission configured correctly?

• Has the file been opened (locked) by another application?

The file name is too long.

Specify the file name using a maximum of 259 characters in the absolute path.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, take the following corrective actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

The configuration file for rollback failed to be created.

Make sure that there is sufficient disk space, memory, or other OS resources.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) was deleted.

Click Verify IM Configuration, and make sure that the current configuration is correct.

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status of the target host.

An error occurred during execution of the re-load command: The configuration file might contain a mistake.

Revise the contents of the configuration file definition.

Make sure that the relevant service or process is running. If it is not running, take the following corrective actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

There might be a mistake in a configuration file definition, or JP1/Base might not be running properly.

Make sure that the relevant service or process is running and that the configuration file is formatted correctly.

If it is not running, take the following corrective actions, and then retry the operation.

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

An attempt to update the startup definition file "startup-definition-file-path" failed.

Check the following on the agent host:

• Has the format of the startup definition file been set correctly?

• Has the access permission for the startup definition file been set correctly?

• Is there sufficient disk space?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22469-W

The configuration file "file-name" for profile-type in the agent host might have been changed.

The configuration file in the agent host may have been overwritten.

S:

Continues processing.

O:

Check the contents of the configuration file in the agent host.

Note:

When acquiring information from the agent host, changes are overwritten.

KNAN22471-E

Batch application of a configuration failed because a database access error occurred. (Cause: error-code)

Batch application of a configuration failed because an IM Configuration Management database access error occurred.

S:

Stops application of the configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Execute the jimdbstatus command, and determine whether the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

The product does not exist.

In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.

If no host information is displayed in the window, click Collect Host Information, and then retry the operation.

The OS information does not exist.

In the IM Configuration Management window, make sure that the OS type is displayed in the host information.

If it is not displayed, click Collect Host Information, and confirm that the OS type is displayed.

The profile does not exist.

Check the profile collection status in the IM Configuration Management window, and then determine whether profile collection is complete or partially complete.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22472-E

Batch application for a host failed because the host is not registered.

Batch collection of a configuration file failed because the host is not registered.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22473-I

Exclusive edit rights for the product-name of the host "host-name" was released successfully.

Reports that exclusive permission was released successfully.

S:

Terminates processing.

KNAN22474-E

Batch application was not performed because product-name does not exist on the host "host-name".

Application was not performed because the relevant product does not exist in the host.

S:

Stops application of the configuration file.

O:

Make sure that JP1/Base is installed on the host, and then retry the operation.

KNAN22475-E

Application of the configuration file "file-name" for profile-type failed because another user is currently accessing the file.

Application of the configuration file failed because another user is currently accessing the file.

S:

Stops application of the configuration file.

O:

Wait awhile, and then retry the operation.

KNAN22476-E

During batch application, application of the host "host-name" failed. (Cause: error-code)

Application of the profile information failed during batch application processing.

S:

Stops application of the configuration file.

O:

Check the contents of the detailed information. Take the indicated action, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22477-E

An attempt to save the configuration file to the server failed because a database access error occurred. (Cause: error-code)

An attempt to save the configuration file on the server failed because an IM Configuration Management database access error occurred.

S:

Stops saving the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Execute the jimdbstatus command, and make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

The OS information does not exist.

In the IM Configuration Management window, make sure that the OS type is displayed in the host information.

If it is not displayed, click Collect Host Information, and confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22478-E

An attempt to save the configuration file to the server failed because the host is not registered.

An attempt to save the configuration file on the server failed because the host is not registered.

S:

Stops saving the configuration file.

O:

In the IM Configuration Management window, open the host list and make sure that the managed host is registered correctly.

KNAN22479-E

Application of the configuration file "file-name" for profile-name failed because application of the specified profile type is not supported for logical hosts.

Application of the configuration file failed because application of the specified configuration file is not supported for logical hosts.

S:

Stops application of the configuration file.

O:

The environment is invalid.

Re-install JP1/IM - Manager.

KNAN22480-E

Batch application of the host "host-name" was not performed because the host is locked by the user user-name:View-host-name.

Batch application processing of the profile information cannot be performed because another user has acquired exclusive access permission for the host information.

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN22481-E

Batch application of the host "host-name" was not performed because another user is currently updating the host information.

Batch application processing of the profile information cannot be performed because the host information is being updated.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22482-E

Batch application of product-name of the host "host-name" was not performed because the profile information is locked by the user user-name:View-host-name.

Batch application processing of the profile information cannot be performed because a user has acquired exclusive access permission for the host information.

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN22483-E

Batch application of product-name of the host "host-name" was not performed because the profile information is being updated.

Batch application processing of the profile information cannot be performed because the profile information is being updated.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22484-E

Batch application processing was not performed because another user is currently updating the IM configuration tree.

Batch application processing cannot be performed because the IM configuration (system hierarchy) is being updated.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22485-E

Batch application processing was not performed because the IM configuration is locked by the user user-name:View-host-name.

Batch application processing cannot be performed because a user has acquired update permission for the IM configuration (system hierarchy).

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN22486-E

Batch application processing was not performed because IM configuration verification was being performed by the user user-name:View-host-name.

Batch application processing cannot be performed because a user is performing verification of the IM configuration (system hierarchy).

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Wait awhile, and then retry the operation.

KNAN22487-E

Batch application processing of host-name was not performed because host information has not been collected.

Batch application processing cannot be performed on the host because the host information has not been collected.

S:

Stops application of the configuration file.

O:

Wait until the host information has been collected, and then retry the operation.

KNAN22488-E

Application of the configuration file "file-name" for profile-type failed because the configuration file does not exist in the server.

Application of the configuration file failed because the configuration file has not been saved on the server.

S:

Stops application of the configuration file.

O:

Check the following items, and then retry the operation.

Has the profile been acquired?

Can the contents of the profile be referenced from the Display/Edit Profiles window?

KNAN22491-E

Batch application terminated abnormally.

Batch application ended abnormally.

S:

Stops application of the configuration file.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22492-E

The configuration file "file-name" for monitoring-target-name cannot be reloaded because a startup option was changed.

The configuration file cannot be reloaded because the startup option was changed.

S:

Stops application of the configuration file.

O:

Perform either of the following:

If you want to reload the configuration file:

Undo the change of the startup option, and then retry the operation.

If you want to change the startup option:

Click Apply by Restarting from the menu to restart the log file trap.

KNAN22493-E

Application of log file trap contents failed because an error occurred when the reload command was executed. (Error code: error code. For details, see the description of the jevlogreload command in the JP1/Base manual.)

Application of the log file trap failed because an error occurred during execution of the reload/start command.

S:

Stops application of the configuration file.

O:

Refer to the JP1/Base manuals (jevlogstart and jevlogreload commands), and take the corrective action indicated by the command execution time error.

KNAN22494-E

Acquisition of exclusive edit rights failed. (Cause: Host is not registered.)

Acquisition of exclusive editing permission failed because the specified host could not be found in the host list.

S:

Stops acquisition of exclusive editing permission.

O:

Acquire the most recent information, and make sure that the host exists.

KNAN22495-E

Rollback of configuration file "file-name" for profile-type failed.

Note: The configuration file "file-name" stored the host "host-name" is changed to the contents of after-editing.

Rollback of the configuration file failed.

S:

Stops rollback processing.

O:

Make sure that the configuration information is correct, edit the configuration file, and then retry the operation.

KNAN22496-W

Rollback of configuration file "file-name" for profile-type is not executed because the rollback is not supported for JP1/Base's version of host "host-name".

Note: The configuration file "file-name" stored the host "host-name" is changed to the contents of after-editing.

Rollback of the configuration file failed because rollback is not supported for the version of JP1/Base on the host.

S:

Stops rollback processing.

O:

Edit the configuration file, and then retry the operation.

KNAN22497-I

The profile type configuration file "file name" could not be applied because the configuration file does not exist on the server.

Application of profile-type failed because the configuration file does not exist on the server.

S:

Applies profiles other than profile-type.

KNAN22498-E

Application of the configuration file file-name for profile-type was not performed because the configuration file contains control characters.

Application failed because the configuration file includes control characters.

S:

Applies profiles other than profile-type and terminates processing,

O:

Delete the control characters from the configuration file, and then retry the operation.

KNAN22499-E

Error occured during reload command execution for profile-type with the old configuration file.

Reloading of the rolled-back configuration file of profile-type failed.

S:

Stops application.

O:

Make sure that the configuration information is correct, edit the configuration file, and then retry the operation.

KNAN22500-E

An attempt to start the log file trap for monitoring-target-name failed. (Details = details)

An attempt to start the log file trap failed due to one of the following causes:

A database access error occurred.

The log file trap service is not running.

A startup option is invalid.

The syntax of a configuration file is invalid.

The maximum number of monitored files is exceeded.

The specified log file does not exist.

The specified log file trap is already running.

An attempt to execute the command that starts the log file trap failed.

Allocation of an action definition file failed.

The event service is not running.

An attempt to update the startup definition file failed.

S:

Stops starting the log file trap.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.

The agent configuration on the manager might be different from the agent configuration enabled in the system, or the agent configuration on the manager might have been deleted.

In the IM Configuration Management window, click Operation, and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If the agent configurations do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to use batch distribution to make the agent configurations match. Also, check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

The host information might have been changed. Please collect the host information again.

The host information might be different from the actual environment. Collect the host information again. If this message appears again after the host information is collected, the operating environment for JP1/Base running on the host might not be correct. Check whether a JP1/Base error message or warning message was output to the integrated trace log. Also make sure that there are write and read permissions for the JP1/Base conf directory.

Failed to write the configuration file.

Make sure that you have write permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have write permission for the JP1/Base conf directory on the target host.

Failed to read the configuration file.

Make sure that you have read permission for the configuration file and for the log-file trap startup definition file and that another application has not locked these files. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log and that you have read permission for the JP1/Base conf directory.

IM Configuration Management database-access error

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

The log file trap service is not running.

Make sure that the log file trap service is running. If the log file trap service is not running, start it and then retry the operation.

The start options were invalid.

Check the following items:

• Has the startup option been specified correctly?

• Is the -f or -a option specified as an additional option?

The log file trap of the monitoring target name "monitoring-target-name" has already been started.

Check the log file trap running on the agent host.

The syntax of the configuration file is invalid, or the specified log file does not exist.

Check the following items:

• Are the contents of the configuration file correct?

• Does the specified log file exist?

• If the specified log file path contains space characters, is it enclosed in double quotation marks (")?

• Can the specified startup locale be configured for the OS of the agent host?

• If a multi-process trace file is monitored, is HTRACE specified for the FILETYPE parameter in the configuration file?

• Is the log file trap service running?

• Are there sufficient OS resources such as disk space and memory, on the agent host?

• Is the maximum number of monitored files exceeded? (Check whether a JP1 event was issued.)

Failed to relocate the configuration file. (path = path)

Check the following on the agent host, and then retry the operation.

• Has access permission for the path indicated in the message been set correctly?

• Is it possible to overwrite a file, if any, reached by the path indicated in the message?

• Is there sufficient disk space?

The event service is not running.

Make sure that the event service on the agent host is running.

An attempt to update the startup definition file "startup-definition-file-path" failed.

Check the following on the agent host, and then retry the operation.

• Has the format of the startup definition file been set correctly?

• Has the access permission for the startup definition file been set correctly?

• Is there sufficient disk space?

The directory does not exist.

Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

A system error occurred.

Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

The configuration file for rollback failed to be created.

Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

Another session has exclusive rights.

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Make sure that JP1/Base is running on agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

A communication error occurred.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running on the target host.

If JP1/Base is not running on the target host, take the following actions:

Start the service or process.

In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If the problem cannot be solved by taking the above actions, execute the JP1/Base jevlogstart command on the agent host by specifying the same settings as those specified for IM Configuration Management. Then make sure that the log file trap starts normally.

If the jevlogstart command starts the log file trap normally, use the JP1/IM - Manager data collection tool to collect data, and then contact a system administrator.

If the jevlogstart command does not start the log file trap normally, take the corrective action for the displayed error message.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22501-E

An attempt to stop the log file trap for monitoring-target-name failed. (Details = details)

An attempt to stop the log file trap failed due to one of the following causes:

A database access error occurred.

The log file trap service is not running.

An attempt to execute the command that stops the log file trap failed.

An attempt to delete the configuration file on the agent host failed.

An attempt to update the startup definition file (startup-definition-file-path) failed.

S:

Ceases attempting to stop the log file trap.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database-access error

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

The log file trap service is not running.

Check whether the log file trap service is running. If the log file trap service is not running, start it, and then retry the operation.

Execution of the command to stop the log file trap failed.

Check whether the command that stops the log file trap can be executed on the agent host.

Deletion of the configuration file "file-name" on the agent host failed.

Manually delete the configuration file having the indicated file name on the agent host.

An attempt to update the startup definition file "startup-definition-file-path" failed.

Check the following on the agent host, and then retry the operation.

• Has the format of the startup definition file been set correctly?

• Has the access permission for the startup definition file been set correctly?

• Is there sufficient disk space?

The file does not exist.

Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

The directory does not exist.

Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

Failed to write the configuration file.

Make sure that you have write permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have write permission for the JP1/Base conf directory on the target host.

Failed to read the configuration file.

Make sure that you have read permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have read permission for the JP1/Base conf directory on the target host.

There is no access permission.

Check the settings of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent, confirm that the access from a manager host is admitted.

The configuration file for rollback failed to be created.

Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

Another session has exclusive rights.

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Make sure that JP1/Base is running on agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

A communication error occurred.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running on the target host.

If JP1/Base is not running on the target host, take the following actions:

Start the service or process.

In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22502-I

A profile for log file trapping was sent, but the process for the log file trap was stopped. (Monitoring-target-name = monitoring-target-name)

Log file trap information was sent, but the log file trap process was stopped. The log file trap information that was sent will take effect when the log file trap process is started.

S:

Applies changes to the configuration file.

O:

To apply the file that was sent, start the log file trap process.

KNAN22503-E

Deletion of the log file trap for monitoring-target-name failed. (Details = details)

An attempt to delete the log file trap failed due to one of the following causes:

An attempt to delete the configuration file failed.

An attempt to update the startup definition file (startup-definition-file-path) failed.

S:

Stops attempting to delete the log file trap.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database-access error

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

Deletion of the configuration file "file-name" from IM Configuration Management failed.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file indicated in the message exist?

• Has access permission for the file indicated in the message been set correctly?

• Has the file indicated in the message been opened (locked) by another application?

An attempt to update the startup definition file "startup-definition-file-path" failed.

Check the following on the agent host, and then retry the operation.

• Has the format of the startup definition file been set correctly?

• Has the access permission for the startup definition file been set correctly?

• Is there sufficient disk space?

A system call error occurred

Check the following, and then retry the operation.

• Make sure that you have access permission for the log-file trap startup definition file on the agent host.

• Check the OS log of the agent host to see if a shortage has occurred in other OS resources such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

• If an application on the agent host that locks files (such as virus check software) is running, this message might appear due to a contention with that application. Stop the application that locks files, and then retry the operation.

The directory does not exist.

Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

The configuration file for rollback failed to be created.

Make sure that you have read permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

Failed to read the configuration file.

Make sure that you have read permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have read permission for the JP1/Base conf directory on the target host.

There is no access permission.

Check the settings of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent, confirm that the access from a manager host is admitted.

Another session has exclusive rights.

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Make sure that JP1/Base is running on agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

A communication error occurred.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running on the target host.

If JP1/Base is not running on the target host, take the following actions:

Start the service or process.

In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22505-I

The log file trap of the monitoring target name "monitoring-target-name" has already been stopped.

The log file trap has already stopped.

KNAN22506-W

The log file trap "monitoring-target-name" was stopped successfully, but deletion of the configuration file "configuration-file-path" on the agent host failed.

An attempt to delete the configuration file on the agent host failed.

S:

Stops log file trap without deleting the configuration file on the agent host.

O:

Manually delete the configuration file with the indicated path on the agent host.

KNAN22507-W

There are one or more invalid definitions in the start-definition-file. These definitions will be skipped. line-numbers-of-all-invalid-definitions-separated-by-commas

Reading of part of the indicated startup definition file is skipped because the file contained invalid definitions.

S:

Continues processing without reading the invalid definitions in the indicated startup definition file.

O:

Check the following items for the lines with invalid definitions in the indicated startup definition file:

Is the definition specified in the correct format?

Is the action definition file name (-f option) specified?

Does a value specified in the definition exceed the maximum string length?

If the specified monitoring-target log file trap name exceeds the maximum string length, split the definition into multiple log file traps.

Is a monitoring target name or action definition file name specified more than once in the definition?

KNAN22510-I

The log file trap for monitoring-target-name was deleted successfully.

Deletion of the log file trap has ended.

KNAN22511-I

The log file trap for monitoring-target-name was stopped successfully.

The log file trap was stopped.

KNAN22514-W

The configuration file "file-path" on the agent host "host-name" already exists.

This message is output when the Yes button is clicked in response to the KNAN20355-Q message.

S:

Overwrites the configuration file on the agent host.

O:

If the KNAN20355-Q message appears, click the Yes button to overwrite the configuration file on the agent host.

Make sure that the profile managed by IM Configuration Management is not changed on the agent host.

KNAN22515-W

The path of the configuration file on the agent host "configuration-file-path" is different from the path saved in IM Configuration Management "configuration-file-path" during process stop of log file trap operation.

This message is output when the Yes button is clicked in response to the KNAN20358-Q message.

S:

Deletes the configuration file that has the path saved in IM Configuration Management from the agent host.

O:

This message is output if the path of the configuration file on the agent host is different from the path that was saved when IM Configuration Management agent collected the profile.

When the KNAN20358-Q message appears, click the Yes button to stop the process and delete the configuration file that has the path saved in IM Configuration Management from the agent host.

Make sure that the profile managed by IM Configuration Management is not changed on the agent host.

KNAN22517-W

The path of the configuration file on the agent host "configuration-file-path" is different from the path saved in IM Configuration Management "configuration-file-path" during process restart of log file trap operation.

This message is output when the Yes button is clicked in response to the KNAN20359-Q message.

S:

Applies the configuration file with the path saved in IM Configuration Management, and then restarts the log file trap.

O:

This message is output if the path of the configuration file on the agent host is different from the path that was saved when IM Configuration Management agent collected the profile.

When the KNAN20359-Q message appears, click the Yes button to apply the configuration file to the path saved in IM Configuration Management, and then restart the log file trap.

Make sure that the profile managed by IM Configuration Management is not changed on the agent host.

KNAN22518-E

The log file trap failed to be reloaded because the path of the configuration file on the agent host "configuration-file-path" is different from the path saved in IM Configuration Management "configuration-file-path".

This message is output if the path of the configuration file used on the agent host is different from the path saved in IM Configuration Management.

S:

Cancels reloading of the log file trap.

O:

This message is output if the path of the configuration file used on the agent host is different from the configuration file path saved in IM Configuration Management agent when the profile is collected.

Take the following actions:

Restart the log file trap to apply the setting. When the log file trap restarts, the KNAN20359-Q message appears.

Rebuild the profile tree and acquire the latest profile. Note, however, that the contents of any profiles that have not been applied are aborted.

KNAN22520-E

Rollback of the startup definition file "startup-definition-file-path" failed. The startup definition file stored on the host "host-name" was changed by IM Configuration Management.

An attempt to roll back the startup definition file failed.

S:

Cancels rollback processing.

O:

Retry the operation. If the same message appears again, use the data collection tool to collect data, and then contact a system administrator.

KNAN22521-I

The log file trap for monitoring-target-name was started successfully.

The log file trap started.

KNAN22523-I

The configuration file "file-name" for monitoring-target-name was successfully sent.

The configuration file was sent to the agent.

KNAN22524-E

An attempt to send the configuration file "file-name" for monitoring-target-name failed.

An attempt to send the configuration file failed.

S:

Stops sending the configuration file.

O:

Check the following on the agent host, and then retry the operation.

Has access permission for the following path been set correctly and Is there sufficient disk space for following path?

In Windows: Base-path\conf

In UNIX: /etc/opt/jp1base/conf

Check the condition and status of the network connected to the target host.

Make sure that JP1/Base is running.

Make sure that you have access permission for the configuration file

Another application has not locked the configuration file.

Make sure the output destination of the configuration file does not contain a directory of the same name as the that file.

In the Login User List window, determine whether the user has acquired exclusive permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Make sure that you have access permission for the log-file trap startup definition file.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect data, and then contact a system administrator.

KNAN22526-W

The start-definition-file failed to be read. The startup definition file will be skipped.

Reading of the indicated startup definition file is skipped because its contents are invalid.

S:

Continues processing without reading the indicated startup definition file.

O:

Check access permissions for the displayed log-file trap startup definition file.

Make sure that the monitoring target name and action definition file name for the running log file trap are not used in any other definitions.

Make sure that the log-file trap startup definition file or directory by the log-file trap startup definition file exists and that it is accessible. If the file exists, Manually delete the file.

Make sure the output destination of the log-file trap startup definition file does not contain a directory of the same name as the file. In addition, make sure that JP1/Base on the target host is running.

If JP1/Base on the target host is not running, perform the following corrective actions:

Start the service or process.

In the Display/Edit Profiles window, click Rebuild Profile Tree.

KNAN22527-W

The start-definition-file failed to be read. The startup definition file will be skipped. And There are one or more invalid definitions in the start-definition-file. These definitions will be skipped. line-numbers-of-all-invalid-definitions-separated-by-commas

Reading of the indicated startup definition file is skipped because its contents are invalid. In addition, reading of the invalid definitions found in the indicated startup definition file will be skipped.

S:

Continues processing without reading the indicated startup definition file and invalid definitions in the startup definition file.

O:

Check the access permission for the indicated startup definition file.

In addition, check the following items for the lines with invalid definitions in the indicated startup definition file:

Is the definition specified in the correct format?

Does a value specified in the definition exceed the maximum string length?

If the specified monitoring-target log file trap name exceeds the maximum string length, split the definition into multiple log file traps.

Is the same monitoring target name or action definition file name specified more than once in the definition?

KNAN22528-W

The log file trap "monitoring-target-name" was deleted successfully, but deletion of the configuration file "configuration-file-path" on the agent host failed.

An attempt to delete the configuration file on the agent host failed.

S:

Deletes the log file trap without deleting the configuration file on the agent host.

O:

Manually delete the file having the indicated file name on the agent host.

Make sure that you have read permission for the displayed file and that another application has not locked the file.

KNAN22529-E

The remote monitoring configuration file Configuration file name does not exist on the server.

An attempt to read the action definition file for the remote-monitoring log file trap failed.

S:

Stops display of the remote-monitoring log file trap.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22530-E

The configuration file "monitoring-target-name" cannot be reloaded because the specified startup option ("startup-option") does not match the startup option of the log file trap that is currently running.

The configuration file cannot be reloaded because the specified startup option does not match the startup option of the log file trap that is currently running.

S:

Stops the application of the configuration file.

O:

Perform one of the following corrective actions:

To reload the configuration file:

Change the startup option of the configuration file to the startup option of the log file trap that is currently running (which you can check on the Valid Configuration Information page), and then try the operation again.

To change the startup option:

Select Apply by Restarting, and then restart the log file trap.

KNAN22531-E

Application of log file trap contents failed because an error occurred when the reload command was executed. (Cause: detailed-information. error code: error-code. For details, see the description of the jevlogreload command in the JP1/Base manual.)

A log file trap could not be applied because an error occurred during execution of the reload/start command.

S:

Stops the application of the configuration file.

O:

If the following detailed information is displayed, perform the indicated corrective action.

There is a mistake in the settings.

Correct the mistake, and then re-execute the command.

A parameter other than MARKSTR and ACTDEF was changed.

If you want to reload the configuration file, make sure the values of parameters other than MARKSTR or ACTDEF match the values on the Valid Configuration Information page, and then re-execute the command.

If you want to change a parameter other than MARKSTR or ACTDEF, select Apply by Restarting, and then restart the log file trap.

For details about error codes, see the description of the jevlogreload command in the JP1/Base User's Guide.

KNAN22532-E

Changes could not be applied to the profile for log file trapping ("monitoring-target-name"). (Details = detailed-information)

Changes to the log file trap information could not be applied to the agent host.

S:

Stops the application of changes to the agent host.

O:

If the following detailed information is displayed, perform the indicated corrective action.

You do not have the necessary access permissions.

The agent configuration on the manager might be different from the agent configuration enabled in the system, or the agent configuration on the manager might have been deleted.

In the IM Configuration Management window, click Operation and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If they do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to make the agent configurations match. In addition, check the settings of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

Failed to write the configuration file.

Make sure that you have write permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have write permission for the JP1/Base conf directory on the target host.

Failed to read the configuration file.

Make sure that you have read permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have read permission for the JP1/Base conf directory on the target host.

Another session has exclusive rights.

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Make sure that JP1/Base is running on agent host.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager, JP1/Base

• In manager host: JP1/Base

The directory does not exist.

Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

A required service or process is not running.

Make sure that the relevant service or process is running. If it is not running, perform the following corrective actions, and then retry the operation:

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

A communication error occurred.

Check the condition and status of the network connection with the acquired managed host.

In addition, make sure that JP1/Base is running.

If JP1/Base is not running, perform the following corrective actions:

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

The system is busy. Try again later.

Wait a while, and then retry the operation.

Failed to reload a service or process.

Make sure that the relevant services or processes are running and that the configuration file is correctly formatted.

If a relevant service or process is not running, perform the following corrective actions, and then retry the operation:

• Start the service or process.

• In the Display/Edit Profiles window, click Rebuild Profile Tree.

A memory shortage occurred on the manager host.

Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.

Make sure that there is enough free memory on the agent host, and then retry the operation.

An error occurred in the attempt to access the IM Configuration Management database.

Execute the jimdbstatus command to check whether the IM database service is running. If it is not running, start it, and then retry the operation.

The log file trap service is not running.

Check whether the log file trap service is running. If it is not running, perform the following action, and then retry the operation:

• Start the log file trap service.

The startup option is invalid.

Check the following items:

• Is the startup option specified correctly?

• Is the -f or -a option specified as an additional option?

The log file trap of the monitoring target "monitoring-target-name" is already running.

Check the log file trap that is running on the agent host.

The content in the configuration file is specified incorrectly, or the specified log file does not exist.

Check the following items:

• Are the contents of the log-file trap action definition file and the log-file trap startup definition file correct? Does the specified log file exist?

• If the specified log file path contains space characters, is it enclosed in double quotation marks (")?

• Does the specified startup locale exist on the agent host?

• If a multi-process trace file is monitored, is HTRACE specified for the FILETYPE parameter in the configuration file?

• Is the log file trap service running?

• Are there sufficient OS resources, such as disk space and memory, on the agent host?

• Has the log-file trap action definition file and the log-file trap startup definition file access permission been set correctly?

• Has the log-file trap action definition file and the log-file trap startup definition file been opened (locked) by another application?

If the problem cannot be solved by taking the above actions, execute the JP1/Base jevlogstart command, which starts a log file trap, on the agent host by specifying the same settings as those specified for IM Configuration Management. Then make sure that the log file trap starts normally. If the jevlogstart command does not start the log file trap normally, take the corrective action for the displayed error message. If the jevlogstart command starts the log file trap normally, use the JP1/IM - Manager data collection tool to collect data, and then contact a system administrator.

The event service is not running.

Make sure that the event service is running on the agent.

There is a mistake in the settings.

Correct the mistake, and then re-execute the command.

A parameter other than MARKSTR and ACTDEF was changed.

If you want to reload the configuration file, make sure the values of parameters other than MARKSTR or ACTDEF match the values on the Valid Configuration Information page, and then re-execute the command.

If you want to change a parameter other than MARKSTR or ACTDEF, select Apply by Restarting, and then restart the log file trap.

The configuration file for rollback failed to be created.

Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

• In agent host: JP1/IM-Manager. JP1/Base

• In manager host: JP1/Base

Error code: 3. For details, see the description of the jevlogreload command in the JP1/Base manual.

Check the network condition and status with the acquired target.

Also make sure that JP1/Base is running on the target host.

If JP1/Base is not running on the target host, take the following actions:

Start the service or process.

In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22533-E

Application of the IM configuration failed. (Host name: host name, Cause: detailed-information)

The application of the IM configuration (system hierarchy) failed.

S:

Cancels the application.

O:

Take one of the following actions depending on the detailed information:

A timeout occurred.

Check the following points, and then retry the operation:

- Check whether an error occurred on a lower-level host. When host-name includes a submanager, a host under the submanager might take time for the processing. Check the integrated trace log of the submanager.

- Wait until processing by the submanager and lower-level hosts is completed, and then try to apply the IM configuration again. To know whether the processing is completed, check whether the message KAVB3185-I is issued on the submanager host after the timeout.

- When there is no error on lower-level hosts but this message is issued, the duration of processing by the submanager and lower-level hosts might exceed the communication timeout period. Adjust the jbsrt_distrib command to ensure that the communication timeout period is greater than the processing duration in the message KAVB3185-I issued on the submanager host. Alternatively, use the differing-components distribution facility of JP1/Base to apply the configuration for each group composed of a few hundred to about 500 hosts.

KNAN22534-E

IM Configuration synchronization is failed.(Host name: host name, Cause: detailed-information)

The synchronization failed.

S:

Cancels the synchronization

O:

Take one of the following actions depending on the detailed information:

A timeout occurred.

Check the following points, and then retry the operation:

- Check whether an error occurred on a lower-level host. When host-name includes a submanager, a host under the submanager might take time for the processing. Check the integrated trace log of the submanager.

- Check the configuration and status of the network with the host indicated in host-name. Additionally, check that JP1/Base is running on the acquired host.

- Wait until processing by the submanager and lower-level hosts is completed, and then try to synchronize the IM configuration again. To know whether the processing is completed, check whether the message KAVB3185-I was issued on the submanager host after the timeout.

- When there is no error on lower-level hosts but this message is issued, the duration of processing by the submanager and lower-level hosts might exceed the communication timeout period. Adjust the jbsrt_sync command to ensure that the communication timeout period is greater than the processing duration in the message KAVB3185-I issued on the submanager host.

KNAN22600-I

Collection of service information from the host "host-name" ended successfully.

Collection of service activity information ended.

S:

Stops collection of service activity information.

KNAN22601-E

Collection of service information failed because the JP1/Base service of host "host-name" is not running.

Collection of service activity information failed because JP1/Base is not running.

S:

Stops collection of service activity information.

O:

Make sure that JP1/Base is running, and then retry the operation.

KNAN22602-E

Collection of service information failed because the connection with the host "host-name" was lost.

A connection cannot be established with the host.

S:

Stops collection of service activity information.

O:

Make sure that JP1/Base is running, and then retry the operation.

KNAN22603-E

Collection of service information failed because the connection with the host "host-name" timed out.

The connection timed out.

S:

Stops collection of service activity information.

O:

Check the status of JP1/Base, and then retry the operation.

KNAN22604-W

The JP1/Base version on the host "host-name" is not supported.

The JP1/Base version on the host is not supported.

S:

Stops collection of service activity information.

O:

Make sure that the JP1/Base version is 09-00 or later.

KNAN22605-E

Collection of service information failed because the version of JP1/Base of the host "host-name" and the database are not the same.

The version of JP1/Base on the host does not match the IM Configuration Management database.

S:

Stops collection of service activity information.

O:

Collect the host information again, and then retry the operation.

KNAN22606-E

Service operation information collection for the host "host-name" failed because a database access error occurred. (Cause: detailed-information)

Collection of service activity information on the host failed because an IM Configuration Management database access error occurred.

S:

Stops collection of service activity information.

O:

If the following detailed information is displayed, take the indicated corrective action.

The host does not exist.

In the IM Configuration Management window, open the host list and make sure that the managed host has been registered.

IM Configuration Management database access error.

Execute the jimdbstatus command, and make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22607-E

Collection of service information failed. (Cause: error-code)

Collection of service activity information failed.

S:

Stops collection of service activity information.

O:

If the following detailed information is displayed, take the indicated corrective action.

There are not enough resources.

Make sure that there is sufficient disk space, memory, or other OS resources.

The connection destination host is busy.

Wait awhile, and then retry the operation.

Failed to send the data to the connection destination host.

Failed to receive the data from the connection destination host.

Check the OS resources and memory status, and then check the network configuration and status with the connection destination.

Also make sure that the IM Configuration Management Service instance of the connection destination is running.

The data that was acquired while connected to the host is invalid.

Invalid data may have been received temporarily. Retry the operation.

Also check the network configuration and status of the acquired host.

A request was executed in an invalid operating environment.

It is possible that the IM configuration (system hierarchy) was deleted.

Click Verify IM Configuration, and make sure that the current configuration is correct.

A common definition could not be acquired.

The JP1/Base common definition information is not configured. Make sure that it is configured correctly.

If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22608-E

The service operation information collection for host-name host is failed. (Cause: The execution of collection command command-name is failed.)

Collection of service activity information failed because command execution failed.

S:

Stops collection of service activity information.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22700-E

The update permission for the business group could not be acquired because another user has locked the group. (User User Name: View Host Name)

Update permission for the business group could not be acquired because another user had acquired the update permission.

S:

Stops acquisition of the update permission.

O:

Do the following:

In the Login User List window, check the user who has acquired the update permission.

If there is no problem, select the check box for the user who has acquired the update permission, and then click the Release Exclusive Editing button to release the update permission.

After the update permission is released, retry the operation.

KNAN22701-E

Login is not possible because the operation is restricted by business group.

Login is not possible because the JP1 user does not have the necessary operation permission for the JP1_Console resource group and restrictions on operation and reference of business groups are enabled.

S:

Stops login.

O:

Make sure that the JP1 user has one of the following JP1 permission levels for the JP1_Console resource group:

JP1_CF_Admin, JP1_CF_Manager, JP1_CF_User, JP1_Console_Admin, JP1_Console_Operator, and JP1_Console_User

KNAN22702-E

Cannot acquire a lock of business group because host lock is acquired.

The update permission for the business group could not be acquired because the update permission for the host had already been acquired.

S:

Stops acquisition of the update permission.

O:

Make sure that the JP1 user has one of the following JP1 permission levels for the JP1_Console resource group:

JP1_CF_Admin, JP1_CF_Manager, JP1_CF_User, JP1_Console_Admin, JP1_Console_Operator, and JP1_Console_User

Release the update permission for the host, and then retry the operation.

KNAN22800-E

The logical host "logical-host-name" does not exist.

The specified logical host does not exist.

S:

Stops processing the command.

O:

Check the logical host name, and then retry the operation.

KNAN22801-E

The user does not have execution permission.

The user executing the command does not have execution permission.

S:

Stops processing the command.

O:

Log in as a user with the following execution permission, and then retry the operation.

In Windows: Administrator permissions

In UNIX: superuser permission

KNAN22802-E

Command execution will now stop because memory is insufficient.

Command execution is suspended because memory is insufficient.

S:

Stops processing the command.

O:

Allocate sufficient memory, and then re-execute the command.

KNAN22803-E

Command execution will now stop because disk capacity is insufficient.

Free disk space is insufficient. Processing is suspended.

S:

Stops processing the command.

O:

Allocate sufficient disk space, and then re-execute the command.

KNAN22804-E

Command execution failed because a database access error occurred. (Cause: error-code)

An error occurred in the IM Configuration Management database during command execution.

S:

Stops processing the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

The host has already been registered.

Enter a different host name, and then retry the operation.

The number of registered hosts has reached the maximum value.

Reduce the number of registered hosts.

IM Configuration Management database access error.

Execute the jimdbstatus command, and make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22805-E

A connection could not be established with the server.

The command could not establish a connection with the server.

S:

Stops processing the command.

O:

Execute the jco_spmd_status command, and make sure that jcfmain is running. After confirming that jcfmain is running, retry the operation.

Verify that the communication encryption function settings have not changed since JP1/IM - Manager started.

KNAN22806-E

The connection with the server was lost.

The command's connection with the server was lost.

S:

Stops processing the command.

O:

Make sure that the IM Configuration Management Service is running. If the IM Configuration Management Service is not running, start it and then retry the operation. If the IM Configuration Management Service is running, check the processing results on the server to see if the problems listed below occurred. Correct the cause of the problem, and then retry the operation.

The network cannot be used.

OS resources such as memory and ports are temporarily insufficient.

The communication encryption function settings have changed since JP1/IM - Manager started.

This message might also be displayed if output is temporarily suppressed because, for example, the window for executing commands is selected. In this case, cancel the selection to enable the output, and then retry the operation.

KNAN22807-E

The connection with the server timed out.

The command's connection has timed out.

S:

Stops processing the command.

O:

Make sure that IM Configuration Management Service is running, and then retry the operation.

KNAN22808-E

The command was interrupted.

When you press the Ctrl + C keys, a message is displayed notifying you that the command was suspended.

S:

Suspends command processing.

KNAN22809-E

The command option "option" is invalid.

The option is invalid.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22810-E

The command option "option" is specified more than once.

The option is specified more than once.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22811-E

The option "option-value" is mandatory.

A required option is not specified.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22812-E

The maximum length of the value for the option "option-value" is maximum-length.

The option is too long.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22814-E

The value of the option "option-value" is invalid.

The value of the option is invalid.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22816-E

No value is specified for the option "option-value".

No value is specified for a required option.

S:

Stops processing the command.

O:

Make sure that a value is specified for the option, and then retry the operation.

KNAN22817-E

Please execute the command from an administrator console.

The command must be executed from the administrator console.

S:

Stops processing the command.

O:

Execute the command from the administrator console.

KNAN22819-E

The following command options are mutually exclusive: option-value.

The specified command options cannot be specified together.

S:

Stops processing the command.

O:

Check the options, and then retry the operation.

KNAN22820-I

The command command-name will now start.

Reports that the command will now start.

S:

Starts the command.

KNAN22821-I

A connection with the JP1/IM-CF server was established.

The command successfully established a connection with the server.

S:

Continues executing the command.

KNAN22822-I

The command command-name ended successfully.

The command ended normally.

S:

Terminates command processing.

KNAN22823-E

A command failed because the file format is invalid. (file name: file-name, line number: line-number, details: detailed-information)

The command cannot be executed because the file definition is invalid.

S:

Stops processing the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

There are control characters in "file-name".

Delete the control characters in the file displayed in the message.

The host name "host" contains at least one invalid character.

Specify the host name using alphanumeric characters.

"host-name" exceeds the maximum length "maximum-length".

Specify a host name whose length does not exceed the maximum length specified in the message.

There is not a VMM host, an active host, or a standby host "host-name" in the file.

Make sure that the VMM host, primary host, or standby host displayed in the message is listed in the file.

If it is not listed in the file, add it.

Do not specify an active host name, a standby host name, or a VMM host name for the physical host "host-name".

Specify a host other than a primary host, standby host, or VMM host as the physical host.

Do not specify an active host name, a standby host name, or a VMM host name for an unknown host "host-name".

Specify a host other than a primary host, standby host, or VMM host as an unidentified host.

Do not specify an active host name, a standby host name, or a VMM host name for the virtual host "host-name".

Specify a host other than a primary host, standby host, or VMM host as a virtual host.

The active host "host-name" is not a physical or virtual host.

Specify a physical host or a virtual host as the primary host or standby host.

Specify a VMM host name for the virtual host "host-name".

Specify a VMM host name as a virtual host.

Specify a physical host for the VMM host "host-name".

Specify a physical host as a VMM host.

Do not specify a VMM host name for the logical host "host-name".

Specify a host other than a VMM host as a physical host.

The active host name and the standby host name are the same.

The same host cannot be specified as both the primary host and the standby host. Specify a different host for each.

The header information was not found./The header information is invalid./There is an error in the CSV format.

Make sure that the file header information or the CSV format is correct.

The product name is invalid.

Make sure that the product name is formatted correctly.

The number of "value" has exceeded the maximum./The column name "column-name" exceeds the maximum length./The length of "value" exceeds the maximum limit.

Specify the number of values and their lengths so that they do not exceed the maximum values listed in the manual.

There is an invalid character in the value "value".

Make sure that the value displayed in the message does not contain the following characters:

/, :, ?, \", <, >, |, \\, *

The number of hosts has reached the maximum value (1024).

Increase the size of the IM database to L.

The number of hosts has reached the maximum value (10000).

The number of hosts in the export file is invalid. Specify hosts to ensure that the maximum value is not exceeded.

There is a blank line.

Make sure that there are no empty lines in the file.

The host name "host-name" has been duplicated.

Do not specify a host more than once.

The Host type value is invalid.

Specify physical, logical, virtual, or unknown for the host type.

Group Configuration Business Group does not exist in monitorting_system_data.csv.

Make sure that the contents of the monitoring_system_data.csv file are correct.

The column name column name exceeds the maximum length maximum length.

Specify a column that does not exceed the maximum length.

There are control characters in "file-name".

Make sure that there are no control characters in the file.

The number of file-name has exceeded the maximum.

Check the number of files.

Group Configuration Business Group does not exist in monitorting_system_data.csv.

Make sure that the monitoring_system_data.csv file contains the business group name.

Host name host name does not exist under configuration Business Group.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22824-E

A command failed because the file format is invalid. (file name: file-name, details: detailed-information)

The command cannot be executed because the file definition is invalid.

S:

Stops processing the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

The format of the header information is invalid./There is an error in the CSV format.

Make sure that the file header information or the CSV format is correct.

The physical host for the host "host-name" is not present.

There is no definition for the physical host specified in the VMM host, primary host, or standby host. Specify the definition for the host displayed in the message.

There are control characters in "file-name".

Make sure that the file does not contain the following characters:

/, :, ?, \", <, >, |, \\, *

The host name "host" contains at least one invalid character.

Specify the host name using alphanumeric characters.

"host-name" exceeds the maximum length "maximum-length".

Specify a host name whose length does not exceed the maximum length specified in the message.

The number of hosts has reached the maximum value (1024).

Review the file contents shown in the file-name so that the number of hosts including the local host does not exceed the maximum value, or expand the size of the IM Database to the L size.

The number of hosts has exceeded the maximum value (10000). / The number of hosts including the local host has exceeded the maximum value.

Review the file contents shown in the file-name so that the number of hosts including the local host does not exceed the limit.

The protocol_ver tag is invalid.

The format of the import file below the directory specified with the -o option is invalid. Check the protocol_ver of the import information.

The topmost host "host-name" is different.

Specify the local host as the highest-level host.

The Base Manager configuration for the host "host-name" is invalid.

Make sure that the IM configuration (system hierarchy) of the host specified as the site manager is correctly defined.

The host "host-name" has been specified multiple times.

Specify a host only once.

The host "host-name" is looping.

The IM configuration (system hierarchy) is looped. Revise the definition of the IM configuration (system hierarchy) so that it is not looped.

The file content is invalid.

The contents of the system_tree_information are invalid. Revise the contents of the system_tree_information.

The manager host host-name does not exist.

The host specified in the manager host does not exist. Make sure that the host information has been defined.

Host "host-name" is not a base manager in IM configuration.

Make sure that the host is a site manager.

Agent host not available

Use a host that is not an agent host.

Relay manager configuration is not possible.

Specify other than a relay manager.

The format of the management file is invalid.

Make sure that the format of the manager file is correct.

The local host name Host name in a managed host exists.

An IM configuration (system hierarchy information) in which the local host is defined as a managed host cannot be imported. Use an IM configuration (system hierarchy information) in which the local host is not defined as a managed host.

KNAN22825-E

The import operation failed because the profile information of the host "host-name" is locked by user-name:View-host-name.

The import operation failed because the profile is locked by another user.

S:

Stops processing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22826-E

The import operation failed because the IM configuration information is locked by user-name:View-host-name.

The import operation failed because the IM configuration (system configuration) is locked by another user.

S:

Stops processing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22827-E

The import operation failed because the host "host-name" is locked by user-name:View-host-name.

The import operation failed because the profile is locked by another user.

S:

Stops the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22828-E

The import operation failed because the version of the file is not supported. (file = file-name)

The import operation failed because the version of the file is not supported.

S:

Stops processing the command.

O:

Specify an export file whose version is supported by the manager, and then retry the operation.

KNAN22829-W

The host will be automatically registered because the specified host name does not exist in host list file. (host = host-name)

A host that does not exist in the export file (host_input_data.csv) will be registered.

S:

Continues executing the command.

O:

This message is output if a host that does not exist in the export file (host_input_data.csv) is written in the export file (system_tree_information.txt) or if a file exported by another host will be imported. Ignore this message.

KNAN22830-E

The specified path does not exist. (path = path)

The command cannot be executed because the specified path does not exist.

S:

Stops processing the command.

O:

Make sure that the specified file exists and that it is accessible, and then retry the operation.

KNAN22831-E

The file cannot be accessed. (file = path)

The command cannot be executed because the specified file cannot be accessed.

S:

Stops processing the command.

O:

Make sure that the specified directory path and file exist and that they are accessible, and then retry the operation.

KNAN22832-E

The file reading operation failed. (Cause: detailed-information)

Reading of the specified file failed.

S:

Stops processing the command.

O:

Check the following items, and then retry the operation.

Is there sufficient memory?

Does the file exist?

Is the file access permission configured correctly?

Has the file been opened (locked) by another application?

KNAN22833-W

An attempt to acquire a message from the resource file failed.

The relevant message could not be found in the message file.

S:

Continues executing the command.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22834-E

The command "command-name" cannot be executed because the command "command-name" is executing.

The specified command cannot be executed because another command is now executing.

S:

Stops processing the command.

O:

Wait until execution of the other command is complete, and then retry the operation.

KNAN22835-E

A file with the same name already exists.

A file with the same name as the specified file already exists.

S:

Stops processing the command.

O:

Check the specified file, and then retry the operation.

KNAN22836-E

Command operation failed because an I/O error occurred. (details = detailed-information)

An I/O error occurred during output.

S:

Stops processing the command.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN22837-W

The profile information of the host "host-name" is locked by user-name:View-host-name.

The profile is locked by another user.

Another user might change the profile.

S:

Continues executing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22838-W

The IM configuration information is locked by user-name:View-host-name.

The IM configuration (system hierarchy) is locked by another user.

Another user might change the IM configuration (system hierarchy).

S:

Continues executing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22839-W

The host "host-name" is locked by user-name:View-host-name.

The host is locked by another user.

Another user might change the host information.

S:

Continues executing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22840-E

The number of command arguments is invalid.

The number of command arguments is invalid.

S:

Stops processing the command.

O:

Check the command arguments, and then retry the operation.

KNAN22841-I

The profile information does not exists.The import operation is carried out without the profile information.

The profile could not be found at the specified location. Information other than the profile is imported.

S:

Continues executing the command.

KNAN22842-E

Creation of a CSV file failed. (file name = file-name, details = detailed-information, error code = error-code)

Creation of a CSV file failed.

S:

Stops the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

The file or directory path does not exist.

Make sure that the specified path is correct, and that the file exists and it is accessible.

There is insufficient disk space.

Make sure that there is sufficient disk space, memory, or other OS resources.

There is no access permission.

Check the access permission for the specified path.

Too many files are open.

The file could not be opened due to insufficient resources.

Close any unnecessary files, and then retry the operation.

In addition, if the detailed information above is displayed, use the data collection tool to collect data, and then contact a system administrator.

KNAN22843-E

The file format is invalid. (file name = file-name, details = detailed-information, line number = line-number)

The file format is invalid.

S:

Stops the command.

O:

Check the contents of the detailed information. Take the indicated actions, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22844-E

Creation of a temporary CSV file failed. (details = detailed-information)

Creation of a temporary CSV file failed.

S:

Stops the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.

Check the access permission for the specified path.

JP1CONFIG_TMPDIR cannot be obtained from the registry.

The common definition information is not configured. Make sure that the configuration is correct.

If operating in a cluster environment, and if the command is executed with the -h option, make sure that the logical host name is correct.

Also make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

The path specified in JP1CONFIG_TMPDIR does not exist.

Make sure that the tmp directory exists. Also make sure that there is read and write permission for the specified path.

If operating in a cluster environment, check the following items:

• Does the defined log directory exist?

• Is the common disk mounted?

• Is there read and write permission for the specified path?

• If the command is executed with the -h option, was the command issued from the primary host?

The length of the Temp directory path exceeded the maximum value.

The file name specified by jcfmkcsdata exceeds the range allowed by the OS.

Shorten the file name, and then re-execute the command.

In addition, if the detailed information above is displayed, use the data collection tool to collect data, and then contact a system administrator.

KNAN22845-E

Log initialization failed.

Log initialization failed.

S:

Stops the command.

O:

Check the following items:

Make sure that the log directory exists, and that there is read and write permission for the log directory.

If operating in a cluster environment, check the following items:

• Does the defined log directory exist?

• Is the common disk mounted?

• Is there read and write permission for the defined log directory?

If the command is executed with the -h option, make sure that the command was issued from the primary host.

KNAN22846-E

A command terminated abnormally. (Cause: detailed-information)

A command ended abnormally.

S:

Stops the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

An error occurred while writing to a CSV file.

An error occurred while opening a CSV file.

Operations cannot be performed on the file.

Check the following items, and then retry the operation.

• Is there sufficient memory?

• Does the file exist?

• Is the file access permission configured correctly?

• Has the file been opened (locked) by another application?

An attempt to read the common definition parameter has failed.

The common definition information is not configured. Make sure that the configuration is correct.

If operating in a cluster environment, and if the command is executed with the -h option, make sure that the logical host name is correct.

Also make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

An error occurred while opening a temporary CSV file.

In Windows, make sure that the tmp directory exists.

In UNIX, make sure that the tmp directory exists in /var/opt/jp1imm/, and that the user has read and write permissions for the tmp directory.

If operating in a cluster environment, check the following items:

• Does the defined log directory exist below the JP1IMM directory on the shared disk?

• Is the common disk mounted?

• Is there read and write permission?

If the command is executed with the -h option, make sure that the command was issued by the primary host.

An invalid node ID has been specified for a new node.

The file specified for IMCS_ExportFile is invalid. Specify a file that was output by the jcsdbexport command.

Creation of the jcfallogtrap process failed.

If the OS of the manager host is Windows, check the IM host account specified in the system common settings. If the OS is UNIX, check the OS settings related to startup of processes.

The specified command option is invalid.

An incorrect startup option is specified. From IM Configuration Management - View, check the following items for the startup option:

• Is the maximum number of monitored log files exceeded?

• Can the option and its value be specified with additional options?

The specified command option is invalid.

The JP1/Base command arguments are invalid.

An incorrect startup option is specified. From IM Configuration Management - View, check the following items for the startup option:

• Can the option and its value be specified with additional options?

JP1/Base command execution error

Check the JP1/Base environment.

Check whether the JP1/Base LogTrap service or daemon has stopped or restarted. If the JP1/Base LogTrap service or daemon has stopped, start it and then start or restart all the remote monitoring profiles. If the JP1/Base LogTrap service or daemon has restarted, stop all the remote monitoring profiles, and then start or restart them.

An internal error occurred.

Communication with the remote monitoring process failed.

The format of the management file is invalid.

Use the data collection tool to collect data, and then contact a system administrator.

If the problem cannot be resolved using the above methods, use the data collection tool to collect data, and then contact a system administrator.

KNAN22847-I

Conversion of an input file will now start.

Conversion of an input file will now start.

S:

Continues executing the command.

KNAN22848-I

Conversion of an input file was successful.

Conversion of an input file was successful.

S:

Continues executing the command.

KNAN22849-I

Conversion of an input file ended normally.

Conversion of an input file ended normally.

S:

Terminates command processing.

KNAN22850-E

The specified path "path" includes a reserved device name.

The specified path includes a reserved device name.

S:

Stops the command.

O:

Specify the path without a reserved device name, and then retry the operation.

KNAN22854-E

The command "command-name," cannot be executed because the virtualization configuration is being collected.

The command cannot be executed because the virtualization configuration is being collected.

S:

Stops the command.

O:

Wait a while, and then retry the operation.

KNAN22857-E

The host name "host-name" contains at least one invalid character.

The host name contains invalid characters.

S:

Stops the command.

O:

Remove the invalid characters from the host name, and then retry the operation.

KNAN22858-E

The host name "host-name" exceeds the maximum length (Max Limit).

The length of the host name exceeds the maximum.

S:

Stops the command.

O:

Specify a host name that is not greater than the maximum length.

KNAN22859-E

A command failed because the file format is invalid. (file name = file-name, line number = line-number, details = details)

The file format is invalid.

S:

Stops the command.

O:

Check and correct the item indicated by the detailed information, and then retry the operation.

KNAN22860-W

The host name (host-name) contains invalid characters. Some functions might be unusable.

Some functions might be disabled because the host name contains invalid characters.

S:

Continues processing.

O:

Consider changing the host name.

Use the following procedure to change the host name:

In the host list, select the host whose name you want to change.

On the menu bar, click Edit, and then Edit Host Properties.

In the Edit Host Properties window, change the host name.

Open the Edit Agent Configuration window or Edit Remote Monitoring Configuration window, and then apply the setting.

KNAN22861-W

The group configuration information is locked by the user "user name: View Hostname".

A user has acquired the update permission for the business group.

Another user might change the business group.

S:

Continues processing.

O:

Do the following:

In the Login User List window, check the user who has acquired the update permission.

If there is no problem, select the check box for the user who has acquired the update permission, and then click the Release Exclusive Editing button to release the update permission.

After the update permission is released, retry the operation.

KNAN22862-E

The command was not executed because execution of the command would cause the number of commands being concurrently executed to exceed the limit (5).

Execution of the command will be terminated because the maximum number of commands that can be executed concurrently has been exceeded.

S:

Terminates command processing.

O:

Make sure that the number of commands being executed concurrently does not exceed the maximum. If it does, wait until the concurrently executed commands terminate, and then re-execute the command.

KNAN22863-E

Generation of the Central Scope import files failed because the version of the Central Scope export file data was old. (file name = File Name, data version = Data Version)

Command processing could not continue because the version of the central scope export file specified for input was old.

S:

Stops the command.

O:

Specify a central scope export file whose version is 08-10-00 or later. Perform the following to upgrade the central scope export file to the latest version.

Stop the JP1/IM - Manager service, and then execute the jp1csverup command.

After the command has finished, execute the jcsdbexport command to create an export file.

KNAN22875-E

The monitoring group configuration is not the same between IM Configuration Management and the configuration information files.

The monitoring group configurations do not match.

S:

Stops the command.

O:

Match the monitoring group configurations, and then retry the operation.

KNAN22876-E

The business group does not exist in IM Configuration Management. (Business group: Business Group)

The business group does not exist in IM Configuration Management.

S:

Stops the command.

O:

Match the business group configurations, and then retry the operation.

KNAN22890-E

Importing cannot be performed because remote monitoring is running.

Import will be stopped because remote monitoring is running.

S:

Stops the command.

O:

Use the Display/Edit Profiles window, the jcfallogstat command with the ALL option, or the jcfaleltstat command with the ALL option to check whether remote monitoring is running. Stop the remote monitoring, and then retry the operation.

KNAN23000-I

Login was successful. (user name = user-name, host = host-name)

Login was successful.

S:

Logs in successfully.

KNAN23001-E

Login cannot be performed because the number of users connected to the server exceeds the maximum limit of maximum-value.

Login cannot be performed because the number of users that are logged in exceeds the maximum.

S:

Stops login processing.

O:

Wait until another user logs out, and then log in again.

KNAN23002-E

User authentication failed. (user name = user-name, host = host-name)

User authentication failed.

S:

Stops login processing.

O:

Check the user ID and password, and then log in again.

KNAN23003-E

A connection to the authentication server could not be established.

Login failed because a connection to the authentication server could not be established.

S:

Stops login processing.

O:

Make sure that the authentication server is running and accessible, and then log in again.

If you are using the communication encryption function, verify that the communication encryption function settings are correct, and then log in again.

KNAN23004-E

Login failed. (user name = user-name, host = host-name, details = detailed-information)

Login failed.

S:

Stops login processing.

O:

If the detailed information indicates that the common definition could not be acquired, take the following action:

A common definition could not be acquired.

If operating in a cluster system, make sure that the logical host name specified in the JP1_HOSTNAME environment variable is correct.

Use the data collection tool to collect data, and then contact a system administrator.

KNAN23005-E

Logout failed because a communication error occurred between the connecting host and the authentication server. (user name = user-name, host = host-name)

Logout failed because a communication error occurred with the authentication server.

S:

Stops logout processing.

O:

Make sure that the authentication server is running and accessible, and then log out again.

KNAN23006-E

Logout failed. (user name = user-name, host = host-name, details = detailed-information)

Logout failed.

S:

Stops logout processing.

O:

If the detailed information indicates that the common definition could not be acquired, take the following actions:

A common definition could not be acquired.

If operating in a cluster environment, make sure that the logical host name specified in the JP1_HOSTNAME environment variable is correct.

Use the data collection tool to collect data, and then contact a system administrator.

KNAN23008-E

Acquisition of the list of users failed. (details = detailed-information)

Acquisition of the user list failed.

S:

Stops processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN23009-E

The session timed out. (timeout = timeout-value)

The session timed out.

S:

Stops processing.

O:

Log in again.

KNAN23010-I

Logout was successful. (user name = user-name, host = host-name)

Logout was successful.

S:

Logs out successfully.

KNAN23011-I

The received request was aborted because it was sent from an IPv6 address. (source IP address = source IP address)

The received request was aborted because IPv6 addresses are not supported.

S:

Stops login processing.

KNAN24000-E

A command option is invalid.

A command argument is invalid.

S:

Suspends command processing.

O:

Specify a valid argument, and then retry the operation.

KNAN24001-E

The specified file "file-name" is invalid.

The specified file is invalid.

S:

Suspends command processing.

O:

Specify a valid file, and then retry the operation.

KNAN24002-E

The file "file-name" does not exist.

The specified input file does not exist.

S:

Suspends command processing.

O:

Make sure that the specified input file exists and that it is accessible.

KNAN24003-E

The output file "file-name" already exists.

The output file already exists.

S:

Suspends command processing.

O:

Specify the name of an output file that has not already been specified, and then re-execute the command.

KNAN24004-E

The user does not have access permission for the specified file "file-name".

There is no access permission for the specified file.

S:

Suspends command processing.

O:

Check the access permission for the specified file.

KNAN24005-E

No executing permission.

There is insufficient permission to execute the command.

S:

Suspends command processing.

O:

Check the access permission for the specified file.

KNAN24006-E

The memory was insufficient to execute the command.

A memory shortage occurred.

S:

Suspends command processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory.

KNAN24007-E

An IO error occurred. (information = maintenance-information)

An I/O error occurred.

S:

Suspends command processing.

O:

Make sure that there is sufficient disk space, memory, or other OS resources.

KNAN24008-E

An attempt to start the Java VM failed.

An attempt to start Java VM failed.

S:

Suspends command processing.

O:

Make sure that there is sufficient disk space, memory, or other OS resources.

KNAN24009-E

Command execution failed. (information = maintenance-information)

Command execution failed.

S:

Suspends command processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

An error occurred in the KVM host.

Make sure that the KVM host is operating correctly and the libvirt service is running, and then retry the operation.

HCSM server is busy.

Make sure that HCSM at the connection destination is operating correctly. Wait a while, and then retry the operation.

Failed to login to HCSM server.

Make sure that you can log in to HCSM by using the user name and password specified for the command.

One of the following messages is indicated in Detailed information with an HCSM error code:

- Failed to connect to HCSM: HCSM-error-code

- Failed to get information from HCSM server: HCSM-error-code

- HCSM server internal error: HCSM-error-code

- HCSM server error: HCSM-error-code

Make sure that you can log in to HCSM by using the user name and password specified for the command. Also make sure that HCSM at the connection destination is operating correctly.

If detailed information other than the above is output, make sure that there is sufficient disk space, memory, or other OS resources.

If the problem cannot be resolved by checking the above items, use the data collection tool to collect data, and then contact a system administrator.

KNAN24010-E

Execute this command from the manager console.

The command was not executed from the administrator console.

S:

Suspends command processing.

O:

Execute the command from the administrator console.

KNAN24011-W

Acquisition of information from common definitions failed. (information = maintenance-information)

Acquisition of information from the common definition information failed. The default is to continue processing.

S:

Continues processing the command.

O:

Make sure that there is sufficient disk space, memory, or other OS resources.

KNAN24012-E

The "option" option is mandatory.

A required option is missing.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24013-E

The command option "option" is invalid.

An option is invalid.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24014-E

The command option "option" is specified more than once.

An option is specified more than once.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24015-E

No value is specified for the option "option".

No value is specified for an option.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24016-E

The value of the option "option" is invalid.

The value of an option is invalid.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24017-W

An attempt to open the catalog file has failed. (information = maintenance-information)

An attempt to open the catalog file failed.

S:

Assumes that the value of the LANG environment variable is C and continues processing.

O:

Specify a valid value for the LANG environment variable.

KNAN24018-E

The host host-name is duplicated

The same host is specified more than once.

S:

Stops the command.

O:

Check the specified host name, and then retry the operation.

KNAN24030-I

Acquisition of virtual machine configuration information will now start.

Acquisition of virtual machine configuration information will now start.

S:

Starts acquisition of virtual machine configuration information.

KNAN24031-I

Virtual machine configuration information was successfully output.

Virtual machine configuration information was output successfully.

S:

Outputs virtual machine configuration information.

KNAN24032-W

There is the Virtual OS of the host-name host that could not be taken the vm hostname. (VM name: VM-name)

The host-name virtual host name could not be acquired.

S:

Continues processing the command.

O:

Make sure that the virtual host can be acquired in the virtual OS of the specified host.

KNAN24033-W

Username or password for "host-name" host is wrong.

Authentication of the host (host-name) failed.

S:

Continues processing the command.

O:

Specify a valid user name and password.

KNAN24034-E

Acquisition of the virtual machine configuration information failed.

Acquisition of the virtual machine configuration information failed.

S:

Terminates command execution.

O:

Take the corrective action given for the message that was output preceding this message.

KNAN24035-W

A communication error for the host "host-name" occurred.

A communication error for the host (host-name) occurred.

S:

Continues command execution.

O:

Check the following items:

Is the virtual machine software running on the specified host?

Is communication blocked by a firewall?

Is communication enabled for the communication type specified in the -m option?

If you attempted to collect the virtualization configuration from HCSM, make sure that the user name and password are specified correctly. Also make sure that you can log in to HCSM from the manager host by using the specified user name and password.

KNAN24036-W

The host "host-name" is not VMware ESX Server or is not a supported version of VMware ESX Server.

The host (host-name) is not VMware ESX Server, or is not a supported version of VMware ESX Server.

S:

Continues command execution.

O:

Make sure that the connection destination is a supported version of VMware ESX Server.

KNAN24037-W

The host name of the host "host" is different from the SSL certification host name.

The host name of the host (host-name) is different from the SSL certification host name.

S:

Continues command execution.

O:

Specify an SSL certification host name as the host name.

KNAN24038-W

An SSL certification for the host "host-name" was not found.

An SSL certification for the host (host-name) was not found.

S:

Continues command execution.

O:

Use the keytool command to assign SSL certification to the host (host-name).

KNAN24039-E

The file vmware.keystore, which stores the certification information, is invalid.

The certification information stored in the file vmware.keystore is invalid.

S:

Terminates command execution.

O:

Delete the vmware.keystore file, and then use the keytool command to re-create the vmware.keystore file.

KNAN24040-I

A connection to the VMM host could be established. (host name = Host name, VMM name = VMM name, version = Version)

A connection to the VMM host could be established.

S:

Acquires the virtual machine configuration information.

KNAN24041-I

Updating of the virtualization configuration will now start.

Updating of the virtualization configuration will start.

S:

Starts updating the virtualization configuration.

KNAN24042-I

The virtualization configuration was updated successfully.

The virtualization configuration was updated successfully.

S:

Finishes updating the virtualization configuration.

KNAN24050-I

Conversion of the input file will now start.

Conversion of the input file will now start.

S:

Continues command processing.

KNAN24051-I

The input file was successfully converted.

The input file was successfully converted.

S:

Terminates command execution.

KNAN24052-I

Conversion of the input file ended normally.

Conversion of the input file ended normally.

S:

Terminates command execution.

KNAN24053-E

The maximum number of managable hosts was exceeded.

The maximum number of manageable hosts was exceeded.

S:

Terminates command execution.

O:

Revise the number of managed hosts.

KNAN24060-W

Analysis of the virtualization information collected from the host "host-name" has failed.

An error occurred during analysis of the virtualization information acquired from the specified host.

S:

Continues command processing.

O:

Make sure that JP1/SC/CM is running normally on the specified host, and then retry the operation.

If the problem cannot be solved, use the data collection tool to collect data, and then contact a system administrator.

KNAN24061-W

Collection of the virtualization information from the host "host-name" has failed. (cause = cause)

An error occurred during analysis of the virtualization information acquired from the specified host.

S:

Continues command processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

The data that was acquired while connected to the host is invalid.

Invalid data might have been sent from JP1/Base on the target host. Make sure that JP1/Base is normally running on the target host.

The connection destination host is busy.

Wait a while, and then retry the operation.

Failed to send the data to the connection destination host.

Check the OS resources, memory status, and the condition and status of the network connection with the destination host. Also make sure that IM Configuration Management Service is running on the connection destination host.

Failed to receive the data from the connection destination host.

Check the OS resources, memory status, and the condition and status of the network connection with the destination host. Also make sure that IM Configuration Management Service is running on the connection destination host.

An error occurred on the JP1/SC/CM

Make sure that JP1/SC/CM is running normally on the specified host, and then retry the operation.

There are not enough resources.

Make sure that there are sufficient OS resources such as disk space and memory.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN24062-W

JP1/SC/CM is not running on the host "host-name".

JP1/SC/CM is not running on the specified host, or linkage with IM Configuration Management is not configured.

S:

Continues command processing.

O:

Check the following items, and then retry the operation.

Is JP1/SC/CM installed on the specified host?

Does the version of JP1/SC/CM on the specified host support the linkage with IM Configuration Management?

Has JP1/SC/CM started normally on the specified host?

Has the linkage between JP1/SC/CM on the specified host and IM Configuration Management been configured correctly?

To confirm that the linkage between JP1/SC/CM on the specified host and IM Configuration Management has been configured correctly, confirm that the following file exists in Base-path\plugin\conf for the host on which JP1/SC/CM is installed:

Adapter_HITACHI_SERVERCONDUCTOR_SERVERMANAGER.conf

If the file does not exist, see the manual for JP1/ServerConductor/Control Manager to find the location of the file, and then specify the necessary settings.

KNAN24063-W

There is the Virtual OS of the host-name host that could not be taken the vm hostname.(VMM name : VMM name)

The virtual host name could not be acquired by using the data obtained from the host name and VMM name.

S:

Continues command processing.

O:

Make sure that the virtual host name can be acquired in the virtual OS of the specified host.

KNAN24070-W

SSH connection with host "hostname" failed.(cause = cause)

The SSH connection with the host has failed.

S:

Continues command processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

Acquisition of an SSH private key failed.

Check the path to the SSH private key and make sure that the file exists and that it is accessible.

Authentication failed.

Check the following items:

• Is communication with the virtualization host possible?

• Is the SSH server running on the monitored host?

• Is the correct private key specified for the private key file?

If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN24150-E

A parameter of the communication encryption function for the command "command-name" is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function is invalid in the command.

S:

Terminates command execution.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then re-execute the command:

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If A valid value is not specified for a parameter. is displayed for cause, specify a valid value for the parameter in the JP1/Base common definition.

If The value of a parameter exceeds the maximum. is displayed for cause, specify a parameter value that does not exceed the maximum value in the JP1/Base common definition.

KNAN24151-E

Parameters for the communication encryption function for the command "command-name" could not be collected. (parameter = parameter-name, cause = parameter-value)

An attempt to acquire parameters for the communication encryption function has failed.

S:

Terminates command execution.

O:

Re-execute the command. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KNAN24153-E

An error occurred during the initialization of the communication encryption function for the command "command-name". (cause = cause)

An error occurred during initialization of the communication encryption function for the command.

S:

Terminates command execution.

O:

Re-execute the command. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KNAN24155-E

Failed to encrypt communications by using the communication encryption function for the command "command-name". (host name of connection destination = connection-target-host-name, cause = cause)

An attempt to establish encrypted communication with the connection target has failed.

S:

Terminates command execution.

O:

Check to see if the communication encryption function settings have been changed since JP1/IM - Manager started. If they have, restart JP1/Base and JP1/IM - Manager, apply the communication encryption function settings, and then re-execute the command. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

KNAN26000-I

The remote event-log trap will now start. (Host name: host name)

The remote-monitoring event log trap will start.

S:

Starts the remote-monitoring event log trap.

KNAN26001-I

The remote event-log trap has stopped. (Host name: host name)

The remote-monitoring event log trap has stopped.

S:

Stops the remote-monitoring event log trap.

KNAN26002-E

The remote event-log trap will now stop due to error. (Code: code, Host name: host name)

The remote-monitoring event log trap cannot continue because an error occurred.

S:

Stops the remote-monitoring event log trap.

O:

If an error message was output immediately before this message, take the corrective action given for that error message. If an error message was not output, restart the remote-monitoring event log trap. If the problem cannot be resolved by restarting the remote-monitoring event log trap, restart JP1/IM - Manager, and then restart the remote-monitoring log file trap. If the problem cannot be resolved, contact a system administrator.

KNAN26003-E

A connection to the event server cannot be established.

The remote-monitoring event log trap could not start because the event service was not running.

S:

Stops the remote-monitoring log file trap or remote-monitoring event log trap.

O:

Make sure that the event service is running. If it has stopped, start the event service, and then restart the remote-monitoring log file trap or remote-monitoring event log trap.

KNAN26006-I

Reloading of the remote event-log trap has finished. (Host name: Host name)

Reloading of the remote-monitoring event log trap has finished.

KNAN26025-E

Acquisition of event log data failed. (Host name: hostname, Code: code)

An error indicated by the code occurred in the Windows API function during monitoring of the event log. After this message, the system might no longer be able to monitor the event log correctly. In the case of code 1500, the event log might have been corrupted.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN26026-I

An event log can now be monitored. (Host name: host name)

The system is recovered from the error that occurred during monitoring of the event log, and can now monitor the event log.

S:

Continues monitoring of the event log.

KNAN26027-I

The system will now retry reading the event log. (Code: code, Host name: host name)

The system will retry reading the event log because reading failed during monitoring.

S:

Continues processing.

O:

If an error message indicating the cause of retry was output immediately before this message, take the corrective action given for that error message. If an error message was not output, use the data collection tool to collect data, and then contact a system administrator.

If the retry is due to an unsuccessful WMI connection, DCOM outputs multiple error events to the Windows event log. In this case, a DCOM error event is output to the Windows event log each time the system retries.

KNAN26028-E

Monitoring will now stop because the event log could not be read after the specified number of retries. (Code: code, Host name: host name)

Reading failed during event log monitoring. Monitoring of the event log will stop because the system could not read the log after specfied number of retries.

S:

Stops monitoring of the event log.

O:

If an error message indicating the cause of retry was output immediately before this message, take the corrective action given for that error message. If an error message was not output, use the data collection tool to collect data, and then contact a system administrator.

KNAN26039-E

The specified remote log-file trap failed to start. (Host name: Host name, Monitoring-target-name: monitoring-target-name, Details: message)

An error occurred at startup of the remote-monitoring log file trap.

S:

Terminates processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

The operation definition file is invalid.

The action definition file contains an invalid specification. Check the contents of the action definition file.

Authentication failed.

If the OS for the monitored host is UNIX, check the following item:

• Has SSH authentication been configured correctly?

If no error is found by checking the above item, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following item:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

If no error is found by checking the above item, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

Acquisition of an SSH private key failed.

Check the path for the SSH private key.

An attempt to connect monitored host failed.

Confirm that the monitored host exists.

The collection of log files did time-out.

If the OS for the monitored host is UNIX, check the following items, and then restart the remote log-file trap.

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items, and then restart the remote log-file trap.

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Has the number of connections exceeded the maximum for Windows?

If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

• Is the system in high load status?

• Is the host running?

• Has the number of connections exceeded the maximum?

• Has the IM host account been specified correctly in the system common settings?

• Is DCOM configured correctly on the manager host and monitored host?

An attempt to access the monitored file failed.

Check the following items:

• Does the log file exist?

• Has the path for the log file been specified correctly for remote monitoring?

• Has the log file access permission been set correctly?

• If the monitored host is a Windows host, has the maximum number of users permitted to connect to the file share been exceeded? Is communication with the monitored host possible?

If no error is found by checking the above items, check the following items:

• If the monitored host is a Windows host, have the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection been configured correctly?

• If the monitored host is a UNIX host, has the SSH connection been configured correctly? In addition, does the path of a monitoring target file contain any characters other than alphanumeric characters and hyphens (-), underscores (_), periods (.), and slashes (/)?

If you want to perform monitoring even if no log files exist, specify the -r option for either the jcfallogstart or jcfallogdef commands.

The size of the monitored log file has exceeded the limit that can be monitored.

Make sure that the size of the monitored log file does not exceed the maximum size that can be monitored. If it has exceeded the maximum size, revise the log file output settings so that the size of the monitored log file is not greater than the maximum.

The number of monitored files has exceeded the limit.

Check whether the total number of files monitored by remote monitoring has exceeded the maximum number of monitored files that can be managed. Stop remote monitoring, and then reduce the number of files to be monitored.

Log file trap service does not start.

Check the following items:

• Make sure that the log file trap service is running. If the log file trap service has stopped, start it, and then restart the remote-monitoring log file trap or remote-monitoring event log trap.

• Check the integrated trace log to see if the JP1/Base KAVA3663-E or KAVA3917-E message was output. If either message was output, take the corrective action given for that message.

Event service is not started.

Make sure that the event service is running. If the event service has stopped, start it, and then restart the remote log-file trap or remote event-log trap.

The specified command option is invalid.

An incorrect startup option is specified. Check the startup options.

• Can the option and its value be specified with additional options?

Communication with JP1/Base failed.

If possible, restart JP1/Base.

JP1/Base command execution error

Check the JP1/Base environment.

The maximum number of collection processes has been reached.

The number of collection processes has reached the maximum. Stop unnecessary log file traps, and then restart.

Creation of the jcfallogtrap process failed.

If the OS of the manager host is Windows, check the IM host account specified in the system common settings.

If the OS is UNIX, check the OS settings related to startup of processes.

The specified command option is invalid.

An incorrect startup option is specified. Check the startup option.

• Is the maximum number of monitoring log files exceeded?

• Can the option and its value be specified with additional options?

An attempt to connect to the JP1 Event service failed.

If possible, start the event service.

The JP1/Base command arguments are invalid.

Check the startup options.

In any other case, use the data collection tool to collect data, and then contact a system administrator.

KNAN26050-I

The targeted remote log-file traps have started. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The target remote log-file traps have started.

KNAN26055-I

The remote log-file trap will now start. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file trap will start.

S:

Starts the remote-monitoring log file trap.

KNAN26056-I

The remote log-file trap has stopped. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file trap will stop.

S:

Stops the remote-monitoring log file trap.

KNAN26057-E

The remote log-file trap will stop due to error. (Code: code, Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file trap cannot continue because an error occurred.

S:

Stops the remote-monitoring log file trap.

O:

If an error message was output immediately before this message, take the corrective action given for that error message. If an error message was not output, restart the remote-monitoring event log trap. If the problem cannot be resolved by restarting the remote-monitoring event log trap, restart JP1/IM - Manager, and then restart the remote-monitoring log file trap. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26058-E

An error occurred during the opening of the log-file trap action definition file.

An error occurred when the action definition file opened.

S:

Terminates command processing.

O:

Make sure that the action definition file is specified correctly. In Windows, make sure that a reserved device name is not specified. Then, re-execute the command.

In Windows, this message might appear when too many log files are being monitored at the same time. In such a case, stop the monitoring of log files that do not require it, and then re-execute the command.

KNAN26063-E

The action definition file contains an invalid definition. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The action definition file for a remote-monitoring log file trap or remote-monitoring event log trap contains an invalid specification.

S:

Terminates command processing.

O:

Check the following items, and then re-execute the commmand.

Check the contents of the action definition file.

If you want to use the parameters listed below in the action definition file for a remote-monitoring event log trap, upgrade JP1/Base and JP1/IM - Manager to version 11-10 or later. If you do not want to use these parameters, delete them.

• open-retry-times

• open-retry-interval

For the remote-monitoring event log trap, a hyphen (-) is output for the monitoring-target-name.

KNAN26069-E

An attempt to stop the specified remote log-file trap failed. (Host name: host name, Monitoring-target-name: monitoring-target-name, Details: message)

An error occurred when the target remote-monitoring log file trap stopped.

S:

Terminates processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Make sure that the IM database is running. If it has stopped, start the event service, and then stop the remote log-file trap or remote event-log trap again.

The collection of log files did time-out.

The remote log-file trap and remote event-log trap were forced to stop because no response was sent from the monitored host.

In any other case, use the data collection tool to collect data, and then contact a system administrator.

KNAN26072-W

There is no response from the specified remote log-file trap. (Host name: host-name, Monitoring-target-name: monitoring-target-name)

No response has been sent from the specified remote-monitoring log file trap.

S:

Terminates processing.

O:

If no response was sent when the jcfallogstop command was executed, wait a while, and then execute the jcfallogstat command. If you can confirm that the jcfallogstop command stopped the target remote-monitoring log file trap, no action is required.

If the jcfallogstat command indicates that the remote-monitoring log file trap has not stopped or if no response is sent when any other command is executed, use the data collection tool to collect data, and then contact a system administrator.

KNAN26073-W

There is no response from the specified remote event-log trap. (Host name: host-name)

No response has been sent from the remote-monitoring event log trap.

S:

Terminates processing.

O:

If no response was sent when the jcfaleltstop command was executed, wait a while and then execute the jcfaleltstat command. If you can confirm that the jcfaleltstop command stopped the target remote-monitoring event log trap, no action is required.

If the jcfallogstat command indicates that the remote-monitoring event log trap has not stopped or if no response is sent when any other command is executed, use the data collection tool to collect data, and then contact a system administrator.

KNAN26078-I

Reloading of the remote log-file trap has finished. (Host name: host-name, Monitoring-target-name: monitoring-target-name)

Reloading of the remote-monitoring log file trap has finished.

KNAN26081-E

An attempt to reload the remote log-file trap has failed. (Host name: host-name, Monitoring-target-name: monitoring-target-name, Details: message)

An attempt to reload the remote-monitoring log file trap failed.

S:

Suspends reload processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

The operation definition file is invalid.

The action definition file contains an invalid specification.

From the integrated trace log of the manager host, refer to the JP1/Base KAVA3633-E message that is output immediately before this message. Correct the error in the action definition file, and then retry the operation.

A parameter other than MARKSTR and ACTDEF was changed.

A parameter whose profile cannot be applied by reloading was changed before attempting the reload.

From the integrated trace log of the manager host, refer to the JP1/Base KAVA3634-E message that is output immediately before this message, and check the parameter whose profile could not be applied. If you want to reload the remote log-file trap, check the Valid Configuration Information page, make sure the listed values for all parameters other than MARKSTR or ACTDEF match the current values, and then re-execute the reload command.

If you want to change a parameter whose profile cannot be applied by reloading, apply the profile by starting the remote-monitoring log file trap again.

The JP1/Base command arguments are invalid.

Check the startup option.

Log file trap service does not start.

Check the following items:

• Make sure that the log file trap service is running. If the log file trap service has stopped, start it, and then restart the remote-monitoring log file trap or remote-monitoring event log trap.

• Check the integrated trace log to see if the JP1/Base KAVA3663-E or KAVA3917-E message was output. If the message was output, take the corrective action given for that message.

Event service is not started.

Make sure that the event service is running. If the event service has stopped, start it, and then restart the remote log-file trap or remote event-log trap.

JP1/Base command execution error

Check the JP1/Base environment.

Check whether the JP1/Base LogTrap service or daemon has stopped or restarted. If the JP1/Base LogTrap service or daemon has stopped, start it and then start or restart all the remote monitoring profiles. If the JP1/Base LogTrap service or daemon has restarted, stop all the remote monitoring profiles, and then start or restart them.

The specified log file trap is not running.

Check the operation status of the specified log file trap.

The collection of log files did time-out.

If the OS for the monitored host is UNIX, check the following items, and then reload the remote log-file trap.

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Is the SSH server running on the monitored host?

If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

If the OS for the monitored host is Windows, check the following items, and then reload the remote log-file trap.

• Is communication with the monitored host possible?

• Has the remote communication type for the monitored host name been set correctly?

• Has the number of connections exceeded the maximum for Windows?

If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

If the above methods cannot resolve the problem, check the following items:

• Check the load on the system.

• Make sure that the host is running.

• Check whether the number of connections exceeds the maximum.

• Make sure that the IM host account has been specified correctly in the system common settings.

The number of monitored files has exceeded the limit.

Check whether the total number of files monitored by remote monitoring has exceeded the maximum number of monitored files that can be managed. Stop remote monitoring, and then reduce the number of files to be monitored.

In any other case, use the data collection tool to collect data, and then contact a system administrator.

KNAN26091-I

The relevant log file was successfully re-read. (Host name: host-name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name)

The system recovered from the error that occurred during remote monitoring of the log file, and is now available for remote monitoring of log files.

KNAN26092-E

An error occurred while connecting to the manager host's JP1/Base. (Code: code)

An error occurred while JP1/Base on the manager host was being connected.

S:

Stops the remote log-file trap or remote event-log trap.

O:

Make sure that the log file trap service for JP1/Base on the manager host is running normally.

KNAN26093-I

The system will now retry reading the relevant log file. (Code: code, Host name: host-name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name)

The system will retry reading the relevant log file.

S:

Continues processing.

O:

If an error message indicating the cause of retry was output immediately before this message, take the corrective action given for that error message. If an error message was not output, use the data collection tool to collect data, and then contact a system administrator.

KNAN26094-E

The relevant log file could not be read after the specified number of retires, so monitoring will stop. (Code: code, Host name: host-name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name)

Reading failed during log file monitoring. Monitoring of the log file will stop because the system could not read the file after specfied number of retries.

S:

Stops the remote-monitoring log file trap.

O:

If an error message indicating the cause of retry was output immediately before this message, take the corrective action given for that error message. If an error message was not output, use the data collection tool to collect data, and then contact a system administrator.

KNAN26095-E

The relevant log file can no longer be monitored. (Code: code, Host name: host-name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name)

The relevant log file cannot be monitored correctly because its status is abnormal. For the cause of the error, see the value for code.

code = AL000026: The log file being monitored was deleted.

code = AL000027: The log file being monitored was re-created.

code = AL000028: The log file being monitored became smaller.

code = AL000045: The header size of the log file being monitored exceeded the maximum header size that can be monitored.

code = AL000046: The log file being monitored exceeded the maximum file size that can be monitored.

code = AL000052: An attempt to execute the OS command on the monitored host has failed.

The state of the remote log file trap when it was last stopped will not be inherited the next time the remote log file trap starts.

S:

Stops monitoring of the relevant log file.

O:

When code is AL000026 or AL000027:

Check whether the log file being monitored was deleted or re-created.

Make sure that you have access permission for the remote-monitoring target file.

If no problem was found, review and correct the format of the log file (FILETYPE) specified in the action definition file, and then restart the remote log-file trap.

When code is AL000028:

Make sure that the contents of the log file being monitored are not deleted.

This code might be output when the size of the monitored file exceeds 2 gigabytes. Check and, if necessary, revise the size of the monitored file so that it does not exceed 2 gigabytes.

Review and correct the format of the log file (FILETYPE) specified in the action definition file, and then restart the remote log-file trap.

When code is AL000045:

Make sure that the header size specified for HEADLINE in the remote-monitoring log file trap action definition file does not exceed the maximum header size that can be monitored. Then, restart the remote log-file trap.

When code is AL000046:

Make sure that the size of the log file being monitored does not exceed the maximum file size that can be monitored. If the maximum size is exceeded, review the log file output settings of the monitored log file so that the size of the monitored log file is not greater than the maximum. Then, restart the remote-monitoring log file trap.

When code is AL000052:

Check the integrated trace log and take the corrective action given for the message that was output immediately before this message.

KNAN26097-E

Command execution failed because a remote log-file trap corresponding to the Monitoring-target-name is already running. (Host name: host name, Monitoring-target-name: monitoring-target-name)

A remote log-file trap for the same monitoring target name is already running.

S:

Terminates command processing.

O:

Use the jcfallogstat command to check whether a remote-monitoring log file trap for the same monitoring target name is already running. If it is, stop it, and then retry the operation.

KNAN26098-E

A remote log-file trap corresponding to the Monitoring-target-name does not exist. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote log-file trap for the specified monitorng target name does not exist.

S:

Terminates command processing.

O:

Check the monitoring target name.

KNAN26099-E

An attempt to connect monitored host failed. (Host name: host name)

The specified monitored host does not exist.

S:

Terminates processing.

O:

If this message appears at startup of a remote log-file trap and the OS for the monitored host is UNIX, check the following items:

Is communication with the monitored host possible?

Is the SSH server running on the monitored host?

If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

If this message appears at startup of a remote log-file trap and the OS for the monitored host is Windows, check the following items:

Is communication with the monitored host possible?

Has the number of connections exceeded the maximum for Windows?

If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

If the above methods cannot resolve the problem, make sure that DCOM configured correctly on the manager host and monitored host.

If this message appears at startup of a remote event-log trap, check the following items:

Is communication with the monitored host possible?

Has the password for the user who logs in to the monitored host expired?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

KNAN26101-I

Remote log-file trap information is displayed.(Host name: host name): Monitoring-target-name: monitoring-target-name, Options: Options, Watch-file: Watch-file

This message indicates information when a remote-monitoring log file trap starts.

S:

Continues processing.

KNAN26102-E

The remote log-file trap cannot start. (Code: code, Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file trap cannot start.

S:

Terminates processing.

O:

Take the corrective action given for the error message that was output for the relevant remote-monitoring log file trap before this message. Then restart the remote-monitoring log file trap.

KNAN26103-I

The remote log-file trap will automatically start. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file trap will start automatically.

S:

Continues processing.

KNAN26104-I

The remote log-file trap has automatically stopped. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file trap will stop automatically.

S:

Continues processing.

KNAN26106-I

Remote event-log trap information is displayed. (Monitoring-target-name: host name): Options: Options

This message indicates information when a remote event-log trap starts.

S:

Continues processing.

KNAN26107-E

The remote event-log trap cannot start. (Code: code, Host name: host name)

The remote-monitoring event log trap cannot start.

S:

Terminates processing.

O:

Take the corrective action given for the error message that was output for the relevant remote-monitoring event log trap before this message. Then restart the remote-monitoring event log trap.

KNAN26108-I

The remote event-log file trap will now automatically start. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring event log trap will start automatically.

S:

Continues processing.

KNAN26109-I

The remote event-log trap has automatically stopped. (Host name: host name)

The remote-monitoring event log trap will stop automatically.

S:

Continues processing.

KNAN26119-E

The specified monitored host is invalid. (Host name: host name)

The specified monitored host is invalid.

S:

Terminates command processing.

O:

Check the following items for the monitored host:

Has host information been registered?

Has a remote configuration been set correctly?

Has host information been acquired?

KNAN26140-W

The amount of data that a remote log file trap collected from the log file exceeded the limit. The log entries output from the last collection time to this collection time will not be output as JP1 events. (host name: host name, monitoring-target name: monitoring-target-name, log file name: Log file name, previous collection time: Last collection time (yyyy/MM/dd hh:mm:ss), this collection time: This collection time (yyyy/MM/dd hh:mm:ss))

Because the amount of data collected from the monitored log file exceeded the limit that can be collected, the log entries output from around the previous collection time to around this collection time will not be output as JP1 events.

S:

Continues the log file trap.

O:

On the monitored host, check the log data output from around the previous collection time to around this collection time.

If this message frequently appears for the same target log file, consider taking the following corrective actions:

Shorten the monitoring interval.

Specify a filter (-filter option of the jcfallogstart command) as an startup option.

Change the value for log acquisition capacity for the remote-monitoring log file trap.

Use an agent configuration for monitoring.

KNAN26142-W

The amount of data that a remote event-log trap collected from the host exceeded the limit. The event-log entries output from the last collection time to this collection time will not be output as JP1 events. (host name: host name,previous collection time: Last collection time (yyyy/MM/dd hh:mm:ss), this collection time: This collection time (yyyy/MM/dd hh:mm:ss))

Because the amount of data collected from the monitored host exceeded the limit that can be collected, the event-log entries output from the previous collection time to this collection time will not be output as JP1 events. The next monitoring will collect the event-log entries output from this collection time by the monitored host.

The last date and time when the remote event-log trap output event-logs as JP1 events is displayed as the previous collection time.

Even when the remote event-log trap is working, the date and time is not shown as the previous collection time if no event log is output as a JP1 event.

S:

Continues the event log trap.

O:

On the monitored host, check the event log data output from the previous collection time to the present collection time. If the present collection time is earlier than the previous collection time, the date and time on the manager host is different from the date and time on the monitored host. In such a case, this message might also be output for the next monitoring. Synchronize the time on the manager host and monitored host.

If this message frequently appears for the same monitored host, consider taking the following corrective actions:

Make sure that the date and time on the manager host is the same as the date and time on the monitored host.

Make sure that no event log entry exists on the monitored host for a time later than the current time of the monitored host. If any such events exist, delete them.

Specify a filter (-filter option of the jcfaleltstart command) as a startup option.

Configure a filter ahead of time on the Configuration File page of the Display/Edit Profiles window, or by using the -filter option of the jcfaleltdef command.

Shorten the monitoring interval.

Change the value for log acquisition capacity for the remote-monitoring event log trap.

Use an agent configuration for monitoring.

KNAN26143-W

The total value of the upper limits on obtained logs exceeds Maximum. Estimate the total capacity of the logs again. If you continue monitoring in the current state, remote log file traps and remote event log traps might not work properly.

Maximum value: 10 MB

The value for log acquisition capacity exceeds the maximum value. Log acquisition capacity is the maximum number of logs that can be collected from a single instance of JP1/IM - Manager by using remote-monitoring log file traps and remote-monitoring event log traps.

When log acquisition capacity exceeds the maximum value, any of the following might occur:

Remote-monitoring log file traps or remote-monitoring event log traps are not executed.

The processing to convert, into JP1 events, the logs that were output to the log files and event logs takes a long time.

S:

Continues executing the remote-monitoring log file traps and remote-monitoring event log traps.

O:

Re-estimate the total log acquisition capacity.

KNAN26153-E

The WMI connection to the monitored host cannot be established. (Host name: host name, Code: detailed-information)

The WMI connecttion with the monitored host failed.

S:

Terminates command processing.

O:

Check the following items:

Is DCOM configured correctly on the monitored host?

Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

KNAN26155-E

Account authentication failed. (Host name: host name)

Account authentication failed.

S:

Terminates processing.

O:

If this message appears at startup of a remote log-file trap and the OS for the monitored host is Windows, check the following item:

Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

If no error is found by checking the above item, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

If this message appears at startup of a remote event-log trap, check the following items:

Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

Is DCOM configured correctly on the monitored host?

Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

KNAN26163-E

An attempt to start the specified remote event-log trap has failed. (Host name: host name, Details: message)

An error occurred during startup of a remote-monitoring event log trap.

S:

Stops the remote-monitoring event log trap.

O:

If the following detailed information is displayed, take the indicated corrective action.

The operation definition file is invalid.

The action definition file contains an invalid specification. Check the contents of the action definition file.

If you want to use the parameters listed below in the action definition file for a remote-monitoring event log trap, upgrade JP1/Base and JP1/IM - Manager to version 11-10 or later. If you do not want to use these parameters, delete them.

• open-retry-times

• open-retry-interval

Authentication failed.

Check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

An attempt to connect monitored host failed.

The collection of log files did time-out.

If this message appears at startup of a remote event-log trap, check the following items, and then restart the remote event-log trap.

• Is communication with the monitored host possible?

• Has the password for the user who logs in to the monitored host expired?

• Has the remote communication type for the monitored host name been set correctly?

• Is the WMI service running?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

• Check the load on the system.

• Make sure that the host is running.

• Check whether the number of connections exceeded the maximum.

• Make sure that the IM host account has been specified correctly in the system common settings.

Creation of the jcfallogtrap process failed.

Check the IM host account specified in the system common settings.

The specified command option is invalid.

An incorrect startup option is specified. Check the startup option.

• Is the maximum number of monitored log files exceeded?

• Can the option and its value be specified with additional options?

The event service is not running.

Make sure that the event service is running. If the event service has stopped, start it, and then restart the remote log-file trap or remote event-log trap.

The log file trap service is not running.

Check the following items:

• Make sure that the log file trap service is running. If the log file trap service has stopped, start it, and then restart the remote-monitoring log file trap or remote-monitoring event log trap.

• Check the integrated trace log to see if the JP1/Base KAVA3663-E or KAVA3917-E message was output. If the message was output, take the corrective action given for that message.

JP1/Base command execution error

Check the JP1/Base environment.

Check whether the JP1/Base LogTrap service or daemon has stopped or restarted. If the JP1/Base LogTrap service or daemon has stopped, start it and then start or restart all the remote monitoring profiles. If the JP1/Base LogTrap service or daemon has restarted, stop all the remote monitoring profiles, and then start or restart them.

Communication with JP1/Base failed.

If possible, restart JP1/Base.

An attempt to connect to the JP1 Event service failed.

If possible, restart the event service.

The JP1/Base command arguments are invalid.

Check the startup option.

The maximum number of collection processes has been reached.

The number of collection processes has reached the maximum. Stop unnecessary log file traps, and then restart.

An attempt to connect monitored host failed.

Check the following items, and then restore the remote log-file trap or remote event-log trap.

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

The remote event-log trap has already been started.

Check whether the remote-monitoring event log trap is already running on the monitored host.

In any other case, use the data collection tool to collect data, and then contact a system administrator.

KNAN26181-E

The SSH private key was not created.

The SSH private key does not exist.

S:

Terminates processing.

O:

Check the path for the SSH private key.

KNAN26182-E

SSH authentication failed. (Host name: host-name)

Authentication of the SSH connection failed.

S:

Terminates processing.

O:

Check the following items, and then retry the operation.

Is the correct private key specified for the private key file name in the system common settings?

Is the combination of the specified private key and public key correct?

Has SSH been set correctly?

For details about how to set SSH, see 1.17.3 Configuring SSH (for Windows) or 2.16.1 Configuring SSH (for UNIX) in the JP1/Integrated Management 2 - Manager Configuration Guide.

Is the SSH connection with the monitored host that uses the specified private key possible?

KNAN26187-E

The monitored log file cannot be accessed, or collection of the log file failed. (host name: host name, monitoring-target name: monitoring-target-name, log file name: Log file name)

The log files on the monitored host cannot be accessed. Alternatively, an attempt to collect the log files failed.

S:

Retries the processing that collects the log files on the monitored host.

O:

Check the following items:

Does the log file exist?

Has the path for the log file been specified correctly for remote monitoring?

Has the log file access permission been set correctly?

If the monitored host is a Windows host, also check the following items:

Has the maximum number of users permitted to connect to the file share been exceeded?

Is communication with the monitored host possible?

Is the correct regular expression string specified for Filter on the Configuration File page of the Display/Edit Profiles window or specified by the -filter option for the jcfaleltdef command?

Can the operator using the SSH connection with the monitored host execute the following command?

In Linux:

/bin/grep -E 'regular-expression-string-specified-for-the-filter' monitoring-target-log-file-path

In Solaris:

/usr/xpg4/bin/grep -E 'regular-expression-string-specified-for-the-filter' monitoring-target-log-file-path

In OSs other than Solaris and Linux:

/usr/bin/grep -E 'regular-expression-string-specified-for-the-filter' monitoring-target-log-file-path

If no error is found by checking the above items, check the following items:

If the monitored host is a Windows host, have the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection been configured correctly?

If the monitored host is a UNIX host, has the SSH connection been configured correctly?

If you want to perform monitoring even if no log files exist, specify the -r option.

KNAN26189-E

The size of the monitored log file has exceeded the limit that can be monitored. (host name: host name, monitoring-target name: monitoring-target-name, log file name: Log file name, file size: File size (bytes))

The size of the monitored log file has exceeded the maximum size that can be monitored.

S:

Stops the relevant remote-monitoring log file trap.

O:

Make sure that the size of the monitored log file does not exceed the maximum size that can be monitored. If it has exceeded the maximum size, revise the log file output settings so that the size of the monitored log file is not greater than the maximum.

KNAN26196-E

The network connection timed out while the log file was being read. (Host name: host name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name)

A connection timeout occurred while log data was being read.

S:

Cancels processing.

O:

Check the network settings. If the problem cannot be solved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26206-E

The specified remote event-log trap failed to stop. (Host name: host name, Details: message)

An error occurred when the target remote-monitoring event log trap stopped.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.

Make sure that the IM database is running. If it has stopped, start the event service, and then stop the remote log-file trap or remote event-log trap again.

The collection of log files did time-out.

The remote log-file trap and remote event-log trap were forced to stop because no response was sent from the monitored host.

In any other case, use the data collection tool to collect data, and then contact a system administrator.

KNAN26208-E

An attempt to reload the remote event-log trap has failed. (Host name: host name, Details: message)

An attempt to reload the remote-monitoring event log trap failed.

S:

Suspends reload processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

The operation definition file is invalid.

The action definition file contains an invalid specification. Check the contents of the action definition file.

If you want to use the parameters listed below in the action definition file for a remote-monitoring event log trap, upgrade JP1/Base and JP1/IM - Manager to version 11-10 or later. If you do not want to use these parameters, delete them.

• open-retry-times

• open-retry-interval

The specified event log trap is not running.

Check the operation status of the specified event log trap.

Authentication failed.

Check the following items:

• Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

An attempt to connect monitored host failed.

The collection of log files did time-out.

If this message appears at startup of a remote event-log trap, check the following items, and then restart the remote event-log trap.

• Is communication with the monitored host possible?

• Has the password for the user who logs in to the monitored host expired?

• Has the remote communication type for the monitored host name been set correctly?

• Is the WMI service running?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

• Is the system in high load status?

• Is the host running?

• Has the number of connections exceeded the maximum?

• Has the IM host account been specified correctly in the system common settings?

Creation of the jcfallogtrap process failed.

Check the IM host account specified in the system common settings.

The specified command option is invalid.

An incorrect startup option is specified. Check the startup option.

• Is the maximum number of monitoring log files exceeded?

• Can the option and its value be specified with additional options?

Event service is not started.

Make sure that the event service is running. If the event service has stopped, start it, and then restart the remote log-file trap or remote event-log trap.

Log file trap service does not start.

Check the following items:

• Make sure that the log file trap service is running. If the log file trap service has stopped, start it, and then restart the remote-monitoring log file trap or remote-monitoring event log trap.

• Check the integrated trace log to see if the JP1/Base KAVA3663-E or KAVA3917-E message was output. If the message was output, take the corrective action given for that message.

JP1/Base command execution error

If possible, restart JP1/Base.

Communication with JP1/Base failed.

If possible, restart JP1/Base.

An attempt to connect to the JP1 Event service failed.

If possible, restart the event service.

The JP1/Base command arguments are invalid.

Check the startup option.

The maximum number of collection processes has been reached.

The number of collection processes has reached the maximum. Stop unnecessary log file traps, and then restart.

An attempt to connect monitored host failed.

Check the following items, and then restart the remote log-file trap or remote event-log trap:

• Is DCOM configured correctly on the monitored host?

• Is DCOM configured correctly on the JP1/IM - Manager host?

If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

In any other case, use the data collection tool to collect data, and then contact a system administrator.

KNAN26209-E

The database is not running.

An attempt to connect the database failed.

S:

Terminates processing.

O:

Make sure that the IM database is running, and then retry the operation.

KNAN26210-E

Collection of the profile list failed because the specified host is not in the remote monitoring configuration.

The profiles cannot be collected because the host is not included in the remote monitoring configuration.

S:

Stops collection of the profile list.

O:

Include the host in the remote monitoring configuration, and then retry the operation.

KNAN26211-E

The number of remote log-file trap action definition files and the number of remote event-log trap action definition files has reached the limit of manageable action definition files.

The number of remote-monitoring log file trap action definition files and remote-monitoring event log trap action definition files has reached the maximum number of action definition files that can be managed.

S:

Stops collection of the profile list.

O:

Delete unnecessary remote log-file trap action definition files and remote event-log trap action definition files, and then retry the definition.

KNAN26212-E

The number of remote log-file trap action definition files and the number of remote event-log trap action definition files running at the same time has reached the limit.

The number of action definition files has reached the maximum number of files that can be executed concurrently.

S:

Stops collection of the profile list.

O:

Delete unnecessary remote log-file traps and remote event-log traps, and then retry the operation.

KNAN26214-I

The operation status of the specified remote log-file traps will now be displayed.

The operation status of the remote-monitoring log file traps will be displayed.

KNAN26216-I

The operation status of the remote log-file traps for the specified monitored host will now be displayed. (Host name: monitored-host-name)

The operation status of the remote-monitoring log file traps on the monitored host will be displayed.

KNAN26217-I

The operation status of all the remote log-file traps will now be displayed.

The operation statuses of all the remote-monitoring log file traps will be displayed.

KNAN26223-Q

This operation will delete the remote log-file trap corresponding to the Monitoring-target-name from the specified monitored host from the profiles tree. Do you want to continue? (Y/N)

KNAN26224-Q

This operation will delete all the remote log-file traps running for the specified monitored host from the profiles tree. Do you want to continue? (Y/N)

KNAN26225-Q

This operation will delete all the remote log-file traps from the profiles tree. Do you want to continue? (Y/N)

KNAN26226-I

The specified remote log-file traps have stopped. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file traps stopped.

KNAN26230-I

The specified remote log-file traps have been deleted. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The remote-monitoring log file traps were deleted.

KNAN26239-I

The specified remote log-file traps have been reloaded. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The specified remote log-file traps were reloaded.

KNAN26243-E

The specified remote log-file traps are not running. (Host name: host name, Monitoring-target-name: monitoring-target-name)

The specified remote log-file traps are not running.

S:

Terminates command processing.

KNAN26247-E

Remote event-log traps are already running on the specified monitored host. (Host name: host name)

Remote event-log trap are already running on the specified monitored host.

S:

Terminates command processing.

KNAN26249-I

The remote event-log traps started. (Host name: host name)

The remote-monitoring event log traps started.

KNAN26251-I

The operation status of the remote event-log traps on the specified monitored host will now be displayed. (Host name: host name)

The operation status of the remote-monitoring event log traps on the monitored host will be displayed.

KNAN26252-I

The operation status of all remote event-log traps will now be displayed.

The operation status of all remote-monitoring event log traps will be displayed.

KNAN26256-I

The remote event-log traps on the monitored host have been stopped. (Host name: host name)

The remote-monitoring event log traps on the monitored host stopped.

KNAN26258-E

No remote event-log traps are running on the specified monitored host. (Host name: host name)

No remote event-log traps are running on the specified monitored host.

S:

Terminates command processing.

KNAN26261-I

The remote event-log traps on the monitored host have been reloaded. (Host name: host name)

The remote-monitoring event log traps on the monitored host were reloaded.

KNAN26266-E

The specified parameter value is outside the valid range. (option: option, parameter: parameter)

The specified parameter is outside the valid range.

S:

Terminates command processing.

O:

Check the value specified for the option, and then retry the operation.

KNAN26267-E

Command execution failed because another user is currently using the command. (Host name: host name)

An attempt to execute the command failed because another user was using the command.

S:

Terminates command processing.

O:

Wait a while, and then re-execute the command.

KNAN26269-I

Remote log-file traps have been reloaded. (number successful: success, number failed: failure)

The remote-monitoring log file traps have been reloaded.

KNAN26271-I

Remote log-file traps have stopped. (number successful: success, number failed: failure)

The remote-monitoring log file traps have stopped.

KNAN26274-I

The remote log-file trap profile was successfully added. (monitored host: host name, Monitoring-target-name: monitoring-target-name)

The profile for the remote-monitoring log file trap was added successfully.

KNAN26278-I

Event file traps have stopped. (number successful: success, number failed: failure)

The remote-monitoring event log traps have stopped.

KNAN26279-I

Event file traps were reloaded. (number successful: success, number failed: failure)

The remote-monitoring event log traps have been reloaded.

KNAN26281-I

The remote event-log trap profile was successfully Saved. (monitored host: host name)

The profile for the remote-monitoring event log trap was saved successfully.

KNAN26285-I

The remote log-file trap profile was successfully deleted. (monitored host: host name, Monitoring-target-name: monitoring-target-name)

The profile for the remote-monitoring log file trap was deleted successfully.

KNAN26287-I

Remote log-file trap profiles were deleted. (number successful: success, number failed: failure)

The profiles for the remote-monitoring log file trap have been deleted.

KNAN26293-E

The command, command was canceled due to a forced release of exclusive editing rights. (command name: command, Host name: host name)

The command was canceled because exclusive editing rights were forcibly released.

S:

Terminates command processing.

O:

Acquire the exclusive rights again, and then retry the operation.

KNAN26294-E

An I/O error occurred.

An I/O error occurred.

S:

Terminates command processing.

O:

Check the following items:

Are there sufficient system resources and memory?

Is the event log intact (can be viewed by the event viewer)?

If the system resources or memory are insufficient or the event log has been corrupted, correct the cause of the problem, and then retry the operation.

If the problem cannot be corrected, use the data collection tool to collect data, and then contact a system administrator.

KNAN26296-E

The specified host does not exist in the remote configuration. (Host name: host name)

The specified host does not exist in the remote monitoring configuration.

S:

Terminates command processing.

O:

Register the monitored host specified by the command in the remote monitoring configuration.

KNAN26297-E

The monitored host OS is not Windows. (monitored host: host name)

The OS for the monitored host is not Windows.

S:

Terminates command processing.

O:

Check the OS for the monitored host, and then retry the operation.

KNAN26317-I

No hosts exist in the remote configuration.

No hosts exist in the remote monitoring configuration.

KNAN26318-I

No Windows hosts exist in the remote configuration.

No Windows hosts exist in the remote monitoring configuration.

KNAN26319-E

The specified log file name "Log file name" is invalid.

The specified log file name is invalid.

S:

Terminates command processing.

O:

Correct the log file name, and then retry the operation.

KNAN26320-E

The number of specifiable log files has been exceeded.

Processing failed because the maximum number of files that can be monitored has been reached.

S:

Terminates command processing.

O:

Check the monitored files and stop monitoring of unnecessary files. Then retry the operation.

KNAN26322-E

The remote log-file trap service of the manager host's JP1/Base is not running.

Command processing terminated because the log file trap service for JP1/Base on the manager host is not running.

S:

Terminates command processing.

O:

Start the log file trap service for JP1/Base on the manager host, and then retry the operation.

KNAN26326-I

The log file trap of the monitoring target name "monitoring-target-name" has already been stopped.

The remote-monitoring log file trap has already stopped.

KNAN26327-I

Specified Event Log file trap has already been stopped.

The specified remote-monitoring event log trap has already stopped.

KNAN26328-E

An attempt to access the monitored file failed. (monitored host: host name, monitoring-target-name: monitoring-target-name)

The monitored log file cannot be accessed.

S:

Terminates command processing.

O:

Check the following items:

Does the log file exist?

Has the path for the log file been specified correctly for remote monitoring?

Has the log file access permission been set correctly?

If the monitored host is a Windows host, has the maximum number of users permitted to connect to the file share been exceeded? Is communication with the monitored host possible?

If no error is found by checking the above items, check the following items:

If the monitored host is a Windows host, have the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection been configured correctly?

If the monitored host is a UNIX host, has the SSH connection been configured correctly?

If you want to perform monitoring even if no log files exist, specify the -r option for either the jcfallogstart or jcfallogdef command.

KNAN26329-E

The monitored log file could not be read. (monitored host: host name, monitoring-target name: monitoring-target-name)

An attempt to read the log file failed.

S:

Terminates command processing.

O:

Make sure that the log file to be monitored exists and that it is accessible, and then retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26330-E

The Windows event log could not be read. (monitored host: host name)

An attempt to read the event log failed.

S:

Terminates command processing.

O:

Check the log to be monitored, and then retry the operation.

KNAN26331-E

The version of the manager host's JP1/Base doesn't support the remote configuration.

The version of JP1/Base on the manager host does not support remote monitoring.

S:

Terminates command processing.

O:

Upgrade the JP1/Base to version 09-50 or later.

KNAN26332-E

The network connection timed out while the log file was being read. (Host name: host name, Monitoring-target-name: monitoring-target-name)

Log collection did not finish when the timeout period expired.

S:

Cancels processing.

O:

Check the network settings. If the problem cannot be solved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26334-E

The size of the monitored log file has exceeded the limit that can be monitored. (host name: host name, monitoring-target-name: monitoring-target-name)

The size of the monitored log file has exceeded the maximum size that can be monitored.

S:

Terminates command processing.

O:

Confirm that the size of the monitored log file has exceeded the maximum size that can be monitored, and then re-execute the command. If it has exceeded the maximum size, revise the log file output settings so that the size of the monitored log file is not greater than the maximum.

KNAN26336-E

The number of monitored files has exceeded the limit.

The total number of monitored files has exceeded the maximum number of monitored files that can be managed.

S:

Terminates command processing.

O:

Check whether the total number of files monitored by remote monitoring has exceeded the maximum number of monitored files that can be managed. Stop remote monitoring, and then reduce the number of files to be monitored.

KNAN26337-E

The result of the command using SSH connection was invalid. (Host name: host name, Monitoring-target name: monitoring-target-name)

The result of the command executed on the monitored host is invalid.

S:

Terminates processing.

O:

Make sure that the SSH connection has been configured correctly. If the problem cannot be solved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26338-E

The OS command execution failed in the remote monitored host. (Host name: Host name, Monitoring-target name: Monitoring-target-name, User: User, Command line: Command line)

An attempt to execute the OS command on the remotely monitored host has failed.

S:

Terminates processing.

O:

Log in to the monitored host by using the indicated user name, run the indicated OS command, and make sure that the return value is 0. If the return value is not 0, revise the environment of the monitored host so that the return value is 0.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26339-W

Failed to save the state of the remote log file trap when the log was collected. (host name = monitored-host-name, monitoring target = monitoring-target-name)

The state of the remote-monitoring log file trap when the log was collected could not be saved.

If recovery notification event 00003FDB was not issued, when remote monitoring is stopped and started, the logs that were output while monitoring was stopped might not have been trapped, or the logs might be trapped twice, causing JP1 events to be duplicated.

If recovery notification event 00003FDB was issued, normal operation will resume when remote monitoring is stopped and started.

S:

Continues remote monitoring.

O:

Check whether recovery notification event 00003FDB was issued.

If recovery notification event 00003FDB was not issued, check the following items:

Check whether there is enough free disk space.

Check whether a memory shortage occurred.

Check the following OS logs to see whether a shortage occurred with OS resources such as file descriptors:

In Windows: Windows event log

In UNIX: syslog

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26340-W

Failed to save the state of the remote event log trap when the log was collected. (host name = monitored-host-name)

The state of the remote-monitoring event log trap when the log was collected could not be saved.

If recovery notification event 00003FDC was not issued, when remote monitoring is stopped and started, the logs that were output while monitoring was stopped might not have been trapped, or the logs might have been trapped twice, causing JP1 events to be duplicated.

If recovery notification event 00003FDC was issued, normal operation will resume when remote monitoring is stopped and started.

S:

Continues remote monitoring.

O:

Check whether recovery notification event 00003FDC was issued.

If recovery notification event 00003FDC was not issued, check the following items:

Check whether there is enough free disk space.

Check whether a memory shortage occurred.

Check the Windows event log to see whether a shortage of OS resources, such as file descriptors, occurred.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN26341-W

Failed to restore the remote log file trap to its state when it was last terminated. (host name = monitored-host-name, monitoring target = monitoring-target-name)

The remote-monitoring log file trap could not be restored to its state when it was last stopped.

S:

Starts remote monitoring of the relevant remote-monitoring log file without inheriting the state of the remote-monitoring log file trap when it was last stopped.

O:

Check the log data that was output to the monitored log from the time remote monitoring last stopped to the time this message was output. The time remote monitoring last stopped can be determined by checking the time the KNAN26056-I, KNAN26092-E, KNAN26094-E, or KNAN26095-E message was output to the integrated trace log of the manager host, or the time JP1/IM - Manager last stopped.

If this message appears frequently, check the following:

Check whether there is enough free disk space.

Check whether a memory shortage occurred.

Check the following OS logs to see whether a shortage occurred with OS resources such as file descriptors:

In Windows: Windows event log

In UNIX: syslog

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KNAN26342-W

Failed to restore the remote log file trap to its state when it was last terminated. (host name = monitored-host-name)

The remote-monitoring event log trap could not be restored to its state when it was last stopped.

S:

Starts remote monitoring on the relevant monitored host without inheriting the state of the remote-monitoring event log trap when it was last stopped.

O:

Check the event log data that was output to the monitored log from the time remote monitoring last stopped to the time this message was output. The time remote monitoring last stopped can be determined by checking the time the KNAN26001-I, KNAN26028-E, or KNAN26092-E message was output to the integrated trace log of the manager host, or the time JP1/IM - Manager last stopped.

If this message appears frequently, check the following:

Check whether there is enough free disk space.

Check whether a memory shortage occurred.

Check the Windows event log to see whether a shortage of OS resources, such as file descriptors, occurred.

If the problem persists, use the data collection tool to collect data, and then contact a system administrator.

KNAN26343-W

The remote log file trap was not restored to its state when it was last terminated, because the trap was in a state where it could not be monitored. (details = detailed-information, host name = monitored-host-name, monitoring target = monitoring-target-name, log file name = log-file-name)

The remote-monitoring log file trap was not restored to its state when it was last stopped, because the trap was in a state in which it could not be monitored.

S:

Starts remote monitoring without inheriting the state of the remote-monitoring log file trap when it was last stopped.

O:

If the detailed information indicates that the log file being monitored was deleted or re-created

Check whether the log file being monitored was deleted or re-created.

Make sure that you have access permission for the remote-monitoring target file.

If no problem was found, review and correct the format of the log file (FILETYPE) specified in the action definition file, and then restart the remote-monitoring log file trap.

If the detailed information indicates that the size of the log file being monitored has decreased

Check whether the content of the log file being monitored was deleted.

If no problem was found, review and correct the format of the log file (FILETYPE) specified in the action definition file, and then restart the remote-monitoring log file trap.

KNAN26344-W

Failed to delete the state maintenance file for remote monitoring. (file name = file-name)

The state maintenance file for remote monitoring could not be deleted.

S:

Continues processing.

O:

Delete the file indicated in the message.

KNAN26345-I

An error related to saving the state of the remote log file trap that occurred during log collection was resolved. (host name = monitored-host-name, monitoring target = monitoring-target-name)

An error in the processing to save the state of the remote-monitoring log file trap that occurred during log collection was resolved.

S:

Continues remote monitoring.

KNAN26346-I

An error related to saving the state of the remote event log trap that occurred during log collection was resolved. (host name = monitored-host-name, monitoring target = monitoring-target-name)

An error in the processing to save the state of the remote-monitoring event log trap that occurred during log collection was resolved.

S:

Continues remote monitoring.

KNAN26350-W

The backup files for the monitored log files were not found. The log entries output to the backup files between the last collection time and the current collection time will not be output as JP1 events. (host name = monitored-host-name, monitoring target = monitoring-target-name, log file name = monitored-log-file-name, last collection time = yyyy/MM/dd hh:mm:ss, current collection time = yyyy/MM/dd hh:mm:ss, user = user, command line executed = command-line-executed)

The backup files for the monitored host for which remote monitoring was performed could not be found.

The log entries that were output to backup files between the previous collection time and the current collection time are not output as JP1 events.

The executed command line displayed in the message includes the OS command below, which was executed to search for the backup files. The OS command was executed by the user indicated in the message.

find monitored-directory-path -xdev -inum inode-of-backup-files-of- monitored-log-files

S:

Continues remote monitoring.

O:

Log in to the monitored host, and then check whether there is a backup file in the inode displayed in command-line-executed in the message.

If there is a backup file, check the log data that was output between the previous collection time and the current collection time.

The user specified in the Remote Monitoring Settings window or the System Common Settings window might not have the required permissions. Check whether the specified user has permission to read the backup file. In addition, check whether the user has read and write permissions for the directory that holds the backup file and for all the directories above it, and set the permissions as necessary.

After setting the permissions, execute executed-command-line as indicated in the message, and make sure that the backup file appears in the standard output.

If there are no backup files, check the following:

The backup files might have been removed during monitoring.

After a backup file is created, do not delete it untile the next time the log file is trapped.

The format of the monitoring-target log file might not be SEQ2, which is the format specified for FILETYPE in the action definition file for the remote-monitoring log file trap.

Using the SEQ2 format, you cannot monitor files that are in a format in which a backup file is created by copying the monitoring target file. Make sure that the format of the monitoring-target log file is SEQ2.

If the format of the monitoring-target log file is not SEQ2, change the specification for FILETYPE in the action definition file for the remote-monitoring log file trap, and then start remote monitoring again.

For details about log file formats that can be monitored by the remote-monitoring log file traps, see the chapter that describes log information that can be monitored in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.

KNAN26351-E

All trapping of remote log files on monitored host "monitored-host-name" will now stop. (cause = cause)

Remote-monitoring log file traps will now stop due to one of the following causes:

- Collection of remote host information failed.

- The OS of the monitored host changed.

S:

Stops all remote-monitoring log file traps on the monitored host.

O:

Perform the corrective action that corresponds to whichever of the following causes of error is applicable.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If Collection of remote host information failed is displayed for cause, re-execute the collection of host information from the remote host, wait for the processing to terminate normally, and then restart the remote-monitoring log file traps that were stopped.

If The OS of the monitored host changed is displayed for cause, make sure that the monitored host is correct.

If the monitored host is correct, make sure that the remote monitoring profile settings are appropriate for the new OS, and then restart the remote-monitoring log file traps that were stopped. Note that the next time remote monitoring starts, the remote-monitoring log file traps cannot be carried over from when they were last stopped.

If the monitored host is incorrect, revise the system configuration.

KNAN26352-W

The backup files for the monitored log files were not found. The log entries output to the backup files between the last collection time and the current collection time will not be output as JP1 events. (host name = monitored-host-name, monitoring target = monitoring-target-name, log file name = monitored-log-file-name, last collection time = yyyy/MM/dd hh:mm:ss, current collection time = yyyy/MM/dd hh:mm:ss, user = user)

The backup files for the monitored host for which remote monitoring was performed could not be found.

The log entries that were output to backup files between the previous collection time and the current collection time will not be output as JP1 events.

S:

Continues remote monitoring.

O:

Log in to the monitored host and check whether there is a backup file for the monitored log indicated in the message.

If there is a backup file, check the log data that was output between the previous collection time and the current collection time.

In addition, check the following:

The user specified in the Remote Monitoring Settings window or the System Common Settings window might not have the required permissions.

Check whether the monitored host's log file can be read by the specified user from the JP1/IM - Manager host. If the file cannot be read, make the necessary changes to make it readable.

The format of the monitoring-target log file might not be SEQ2, which is the format specified for FILETYPE in the action definition file for the remote-monitoring log file trap.

Using the SEQ2 format, you cannot monitor files that are in a format in which a backup file is created by copying the monitoring target file. Make sure that the format of the monitoring-target log file is SEQ2.

If the format of the monitoring-target log file is not SEQ2, change the specification for FILETYPE in the action definition file for the remote-monitoring log file trap, and then start remote monitoring again.

For details about log file formats that can be monitored by the remote-monitoring log file traps, see the chapter that describes log information that can be monitored in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.

If there are no backup files, they might have been removed during monitoring.

After a backup file is created, do not delete it until the next time the log file is trapped.

KNAN26353-E

Trapping of remote event log files on monitored host "monitored-host-name" will now stop. (cause = cause)

Remote-monitoring event log traps will now stop due to the following cause:

Collection of remote host information failed.

S:

Stops remote-monitoring event log traps on the monitored host.

O:

Take the appropriate corrective action, as described below. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If Collection of remote host information failed is displayed for cause, re-execute the collection of host information from the remote host, wait for the processing to terminate normally, and then restart the remote-monitoring event log traps that were stopped.

KNAN26354-E

A parameter of the action definition file other than MARKSTR and ACTDEF was changed. (Host name: monitored-host-name, Monitoring-target-name: monitoring-target-name)

An attempt to reload the remote-monitoring log file trap failed because a parameter in the action definition file for which changes cannot be applied by reloading was changed before you attempted to reload the remote-monitoring log file trap.

S:

Cancels reloading for the monitored host and the monitoring target whose names appear in the message.

O:

From the integrated trace log of the manager host, refer to the JP1/Base KAVA3634-E message that is output immediately before this message to check which parameter cannot be applied by reloading.

If you want to reload the remote-monitoring log file trap, check the Valid Configuration Information page, make sure the values of all parameters other than MARKSTR or ACTDEF match the current configuration, and then re-execute the reload command.

If you want to change a parameter whose profile cannot be applied by reloading, apply the profile by starting the remote-monitoring log file trap again.

2.14 IM Configuration Management messages common to all components (KNAN29000 to KNAN29999)

KNAN29000-I

The JP1/IM - Configuration daemon has started. (host = host-name)

IM Configuration Management Service started.

S:

Starts IM Configuration Management Service.

KNAN29001-I

The JP1/IM - Configuration daemon ended normally. (host = host-name)

IM Configuration Management Service stopped.

S:

Stops IM Configuration Management Service.

KNAN29002-E

The JP1/IM - Configuration daemon terminated abnormally. (host = host-name)

IM Configuration Management Service stopped abnormally.

S:

Stops IM Configuration Management Service.

O:

Take the following actions:

Make sure that the IM Configuration Management database is operating normally, and then restart IM Configuration Management Service.

Check to see if the communication encryption function settings have been changed to an invalid value after JP1/Base started. Stop JP1/IM - Manager and JP1/Base, carefully review the communication encryption function settings, and then restart JP1/Base and JP1/IM - Manager.

Refer to the message that was output preceding this message, and take the corrective action given for that message.

If the problem cannot be resolved using the above methods, use the data collection tool to collect data, and then contact a system administrator.

KNAN29003-E

The JP1/IM - Configuration daemon cannot start because the host name is invalid. (host = host-name)

IM Configuration Management Service cannot start because the specified logical host name is invalid.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29004-E

The JP1/IM - Configuration daemon cannot start because initialization of JP1 common definitions failed.

IM Configuration Management Service could not be started because initialization of JP1 common definition access failed.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29005-E

The JP1/IM - Configuration daemon cannot start because initialization of the integrated trace log failed.

IM Configuration Management Service could not be started because initialization of the integrated trace log failed.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29006-E

The JP1/IM - Configuration daemon cannot start because initialization of the log of each process failed.

IM Configuration Management Service could not be started because initialization of the process-specific trace log failed.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29007-E

The JP1/IM - Configuration daemon cannot start because an initialization of the database failed.

An attempt to start the IM Configuration Management service has failed, because it could not establish a connection with the IM Configuration Management database.

S:

Terminates IM Configuration Management Service.

O:

If you will not be using the IM Configuration Management service, disable the IM Configuration Management service function by specifying the -cf option in the jcoimdef command.

If you will be using the IM Configuration Management service, check if the IM Configuration Management database has been set up.

If the IM Configuration Management database has not been set up, use the jcfdbsetup command to set up the IM Configuration Management database, and then start JP1/IM - Manager.

If the IM Configuration Management database has already been set up, use the data collection tool to collect the required data, and then contact the system administrator.

KNAN29008-I

Initialization of the JP1/Base communication finished successfully.

Initialization of the JP1/Base communication base finished successfully.

S:

Finishes initializing the JP1/Base communication base.

KNAN29009-E

Initialization of JP1/BASE communication is failed. (error code = error-code)

IM Configuration Management Service could not be started because initialization of the JP1/Base communication base failed.

S:

Terminates IM Configuration Management Service.

O:

The common definition information is not configured. Make sure that the configuration is correct.

If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN29010-W

A common definition value is invalid. The default value will be assigned. (key = key-name, default value = default-value)

A common definition value is invalid. The default value will be used.

S:

Continues processing.

KNAN29011-E

Acquisition of the common directory path name failed.

IM Configuration Management Service could not be started because acquisition of the conf directory from the common definition information failed.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29012-E

Acquisition of the log directory path name failed.

IM Configuration Management Service could not be started because acquisition of the log directory from the common definition information failed.

S:

Terminates IM Configuration Management Service.

O:

If the error occurred in a logical host environment, make sure that the jp1cfhasetup command has already been executed.

If the problem cannot be resolved by taking the above action, use the data collection tool to collect data, and then contact a system administrator.

KNAN29013-W

The JP1/IM - CF daemon will be started using the default port number port-number because acquisition of the port number failed.

The default port will be used because IM Configuration Management Service could not acquire the port number.

S:

Continues processing.

KNAN29014-E

The JP1/IM - CF daemon cannot start because initialization of the service failed.

Initialization of the service failed.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29015-I

The JP1/IM - CF daemon will be reloaded.

Reloading of IM Configuration Management Service will start.

S:

Starts reloading of IM Configuration Management Service.

KNAN29016-I

The JP1/IM - CF daemon was reloaded successfully.

Reloading of IM Configuration Management Service has finished.

S:

Finishes reloading of IM Configuration Management Service.

KNAN29017-W

An attempt to reload the JP1/IM - CF daemon failed.

Reloading of IM Configuration Management Service failed.

S:

Continues operating using the data registered prior to reloading.

KNAN29018-I

The JP1/IM - CF daemon will stop because a stop request was received from the process management daemon.

IM Configuration Management Service will stop normally.

S:

IM Configuration Management Service stops normally.

KNAN29019-E

The JP1/IM - CF will stop because an invalid request was received from the process management daemon. (error code = error-code)

IM Configuration Management Service will stop abnormally.

S:

Terminates IM Configuration Management Service.

O:

Take the following actions:

Make sure that the IM Configuration Management database is running normally, and then restart IM Configuration Management Service.

Refer to the message that was output preceding this message, and take the corrective action given for that message.

If the problem cannot be resolved using the above methods, use the data collection tool to collect data, and then contact a system administrator.

KNAN29020-E

Startup completion could not be reported to the process management daemon.

Completion of startup could not be reported to SPMD.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29021-I

Creation of all the threads waiting for TCP/IP communication completed successfully.

Creation of all threads waiting for a TCP/IP connection finished successfully.

S:

Finishes creating all threads waiting for a TCP/IP connection.

KNAN29022-W

Creation of some threads waiting for TCP/IP communication failed, but processing will continue.

Creation of some threads waiting for a TCP/IP connection failed, but processing will continue.

S:

Continues processing.

KNAN29023-E

The JP1/IM - CF daemon will stop because the creation of all the threads waiting for TCP/IP communication did not succeed.

IM Configuration Management Service stops because creation of all threads waiting for a TCP/IP connection failed.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29024-I

Creation of threads waiting for the TCP/IP communication completed successfully. (IP address = IP-address)

Creation of threads waiting for a TCP/IP connection finished.

S:

Finishes creating threads waiting for a TCP/IP connection.

KNAN29025-E

An attempt to create a thread waiting for the TCP/IP communication failed. (IP address = IP-address)

Creation of threads waiting for a TCP/IP connection failed.

S:

Terminates IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29026-I

The IM configuration management service will now start. (language = environment-variable and character encoding =character-code)

Reports that IM Configuration Management Service will now start.

S:

Starts IM Configuration Management Service.

KNAN29027-E

Initialization of the plugin service failed. (error code = error-code)

Startup of IM Configuration Management Service failed because initialization of the JP1 plug-in manager failed.

S:

Terminates IM Configuration Management Service.

O:

If the detailed information indicates that there are not enough resources, take the following corrective actions:

Make sure that there is sufficient disk space, memory, or other OS resources.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN29028-I

The TCP/IP communication waiting thread started.

Reports that a thread waiting for a TCP/IP connection has started.

S:

Starts a thread waiting for a TCP/IP connection.

KNAN29029-I

The TCP/IP communication waiting thread terminated normally.

Reports that a thread waiting for a TCP/IP connection stopped normally.

S:

Stops a thread waiting for a TCP/IP connection.

KNAN29030-E

The TCP/IP communication waiting thread terminated abnormally.

A thread waiting for a TCP/IP connection stopped abnormally.

S:

Stops a thread waiting for a TCP/IP connection.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29031-E

The connection with the client will be closed because an invalid protocol was received from the client.

The connection will be ended because an invalid protocol was received.

S:

Ends the connection with the IM Configuration Management - View.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29032-E

The connection with the client will be closed because reception of a request failed.

The connection will be ended because reception of a request failed.

S:

Ends the connection with the IM Configuration Management - View.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29033-E

The connection with the client will be closed because an error occurred during request processing.

The connection will be ended because an error occurred during request processing.

S:

Ends the connection with the IM Configuration Management - View.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29034-E

Communication processing will now end because the connection with the client was closed.

Terminates connection processing because the connection was ended.

S:

Ends the connection with the IM Configuration Management - View.

O:

Log in again from the IM Configuration Management - View.

KNAN29036-E

The request "request-name" cannot be executed because of insufficient disk space to update the database.

Stops execution of the request due to insufficient disk space.

S:

Stops execution of the request.

O:

Make sure that sufficient free disk space has been allocated, and then retry the operation.

KNAN29037-E

request-name failed because the database could not be accessed.

Stops execution of the request because IM Configuration Management database access failed.

S:

Stops execution of the request.

O:

Make sure that the IM database service is running, and then retry the operation.

If the problem cannot be resolved using the above method, use the data collection tool to collect data, and then contact a system administrator.

KNAN29038-E

The request "request-name" cannot be executed because the logged-in user "user-name" does not have update permission.

Stops execution of the request due to insufficient user permission.

S:

Stops execution of the request.

O:

Assign the required permission, and then retry the operation.

KNAN29041-E

A request could not be executed. (request = request-name, error code = detailed-information)

Execution of a request failed.

S:

Stops processing the request.

O:

If There are not enough resources. is displayed for detailed-information, take the following action:

Make sure that there are sufficient OS resources such as disk space and memory.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN29045-E

The format of a received request was was invalid. (request = request-name)

The format of a received request was invalid.

S:

Stops execution of the request.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29046-E

A received request could not be executed. (request = request-name, error code = error-code)

A received request could not be executed.

S:

Stops execution of the request.

O:

If the following detailed information is displayed, take the indicated corrective action.

The specified product is not supported

Make sure that the version of the installed product is 09-00 or later.

The IM configuration has not been applied

In the IM Configuration Management window, apply the IM configuration (system hierarchy), and then retry the operation.

KNAN29047-W

A request could not be executed because the database is busy. (request = request-name)

A request could not be executed because the IM Configuration Management database is busy.

S:

Stops execution of the request.

O:

Wait until another user finishes updating the database, and then acquire the most recent information.

KNAN29048-E

The JP1/IM - Configuration daemon will now stop because registration of an IM host failed.

IM Configuration Management Service will stop because registration of the local host failed.

S:

Stops IM Configuration Management Service.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29049-W

The request "request-name" cannot be executed because another user is updating the IM configuration tree.

The request cannot be executed because the IM configuration (system hierarchy) is being updated.

S:

Stops execution of the request.

O:

Acquire the most recent information, and then retry the operation.

KNAN29050-E

The request "request-name" cannot be executed because the profile is locked by another user.

The request cannot be executed because another user has acquired exclusive access permission for the profile information.

S:

Stops execution of the request.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN29051-E

The request "request-name" cannot be executed because the host is locked by another user.

The request cannot be executed because another user has acquired exclusive access permission for the host information.

S:

Stops execution of the request.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN29052-E

The request "request-name" cannot be executed because the IM configuration is locked by the user user-name:View-host-name.

The request cannot be executed because another user has acquired update permission for the IM configuration (system hierarchy).

S:

Stops execution of the request.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN29053-E

The request "request-name" cannot be executed because IM configuration verification is being performed by the user user-name:View-host-name.

The request could not be processed because IM configuration (system hierarchy) verification is being performed by another user.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Wait until processing is completed, and then retry the operation.

KNAN29054-E

The request "request-name" cannot be executed because the host "host-name" is locked by the user user-name:View-host-name.

The request could not be processed because another user has acquired exclusive access permission for the host information.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

After exclusive access has been released, retry the operation.

KNAN29055-W

The request "request-name" cannot be executed because another user is updating the host.

The request could not be processed because the host information is being updated.

S:

Stops execution of the request.

O:

Acquire the most recent information, and then retry the operation.

KNAN29056-E

The request "request-name" cannot be executed because the profile for the host "host-name" is locked by another user.

The request could not be processed because another user has acquired exclusive access permission for the profile information.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

After exclusive access has been released, retry the operation.

KNAN29057-E

"request-name" was forcibly canceled by the user user-name:host-name

The current processing was canceled because exclusive access was forcibly released by the user.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29058-E

The request "request-name" cannot be executed because the lock was forcibly cancelled by the user user-name:host-name.

Scheduled processing could not be executed because exclusive access was forcibly released by the user.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29059-E

The request "request-name" cannot be executed because the lock was forcibly released.

The request could not be processed because exclusive access was forcibly released.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29060-E

The request "request-name" cannot be executed because processing is in progress.

The request could not be processed because processing is in progress.

S:

Stops execution of the request.

O:

Wait until processing is completed, and then retry the operation.

KNAN29061-E

The request "request-name" cannot be executed because the IM Configuration is already locked. Release the lock and then try again.

IM Configuration (system hierarchy) update permission was already acquired. Release the update permission, and then retry the operation.

S:

Stops execution of the request.

O:

Wait until update permission has been released, and then retry the operation.

KNAN29062-E

The request "request-name" cannot be executed because the product "product-name" of the host "host-name" has been locked by the user user-name:View-host-name.

The request could not be processed because another user acquired exclusive access permission for the profile.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that has acquired exclusive access permission.

If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

After exclusive access has been released, retry the operation.

KNAN29063-E

The request "request-name" cannot be executed because the product "product-name" of host "host-name" is being updated by another user.

The request could not be processed because the profile information is being updated.

S:

Stops execution of the request.

O:

Acquire the most recent information, and then retry the operation.

KNAN29064-E

The request "request-name" cannot be executed because an error occurred while trying to acquire the lock.

The request could not be processed because an attempt to acquire exclusive access failed.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29065-W

Initialization of a profile failed.

An attempt to initialize a profile failed.

S:

Stops execution of the request.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29066-E

The request "request-name" cannot be executed because the database was updated.

The request could not be processed because the IM Configuration Management database was updated.

S:

Stops execution of the request.

O:

Acquire the most recent information.

KNAN29067-E

The connection from a client for which login authentication was not performed will now be closed.

The connection will be ended because the client has not logged in.

S:

Continues processing.

O:

Log in, and then retry the operation.

KNAN29069-E

The request cannot be processed because the database was updated.

The request could not be processed because the IM Configuration Management database was updated.

S:

Stops execution of the request.

O:

Acquire the most recent information.

KNAN29070-E

Since startup status of IM database service could not be confirmed, IM configuration management service cannot be started.(Status : status)

IM Configuration Management Service could not be started because the startup status of the IM Configuration Management database could not be confirmed.

S:

Stops execution of the request.

O:

Make sure that the IM Configuration Management database is running, and then retry the operation.

KNAN29071-E

The JP1/IM - Configuration daemon is not started because the resource initialization is failed.

The IM Configuration Management daemon could not be started because an attempt to initialize resources failed.

S:

Stops execution of the request.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN29080-I

The IM Configuration Management service confirmed that the IM database service has started.

IM Configuration Management Service reports that IM database service startup is complete.

S:

Continues processing.

KNAN29081-I

The IM Configuration Management service is waiting for the IM database service to start.

IM Configuration Management Service is waiting for completion of IM database service startup.

S:

Waits for completion of IM database service startup.

KNAN29082-E

The IM Configuration Management service cannot start because it cannot confirm whether the IM database service has started. Cause: cause

IM Configuration Management Service could not be started because completion of IM database service startup could not be confirmed.

S:

Stops IM Configuration Management Service.

O:

Take corrective action based on the reason:

Reason: The IM database service is now performing start or stop processing.

Reason: The IM database service is stopping.

Execute the jimdbstatus command to determine whether the IM database service is running, and then perform the following operation.

In Windows:

Start the IM database service, and then restart JP1/IM - Manager.

In UNIX:

Stop JP1/IM - Manager, and then re-execute the jco_start command.

Reason: The IM database service was interrupted during a restart.

Execute the jimdbstop -f command to forcibly stop the IM database service, and the perform the following operation.

In Windows:

Start the IM database service, and then restart JP1/IM - Manager.

In UNIX:

Execute the jco_start command.

Reason: The IM database service is not set up.

Use the jcfdbsetup command to set up the IM Configuration Management database, and then start JP1/IM - Manager. If you will not be using the IM Configuration Management service, disable the IM Configuration Management service function by specifying the -cf option in the jcoimdef command.

Reason: Status confirmation error

Reason: System error

Collect JP1/IM data, and then contact a system administrator.

KNAN29083-E

Processing cannot be executed because the IM Configuration Management service is still starting up.

Processing could not be performed because IM Configuration Management Service is starting.

S:

Suspends processing.

O:

Execute the jco_spmd_status command to determine whether jcfmain is running. Make sure that jcfmain is running, and then retry the operation.

KNAN29084-E

Processing cannot be executed because the IM database service is waiting to start.

Processing could not be performed because IM Configuration Management Service is waiting for completion of IM database service startup.

S:

Suspends processing.

O:

Execute the jimdbstatus command to check the status of the IM database service on the manager host. Make sure that the IM database service is running, and then retry the operation. If a KNAN29082-E message was output to the integrated trace log of the manager, take the corrective action given for the KNAN29082-E message.

KNAN29085-W

Acquisition of the contents of the configuration file "file-name" failed.

An attempt to read the configuration file failed.

S:

Continues processing.

O:

Make sure that the configuration file exists.

KNAN29086-W

A configuration parameter is invalid. The default value will be assigned. (parameter name = item, default value = default-value)

Because the set value is invalid, the default value will be used.

S:

Continues processing.

O:

Make sure that the parameter is specified correctly.

KNAN29087-E

The request "request name" cannot be executed because the business group configuration is locked by the user "user name: client host name".

The operation could not be performed because another user acquired the update permission.

S:

Suspends processing.

O:

Do the following:

In the Login User List window, check the user who has acquired the update permission.

If there is no problem, select the check box for the user who has acquired the update permission, and then click the Release Exclusive Editing button to release the update permission.

After the update permission is released, retry the operation.

KNAN29088-E

The request "request name" cannot be executed because another user is updating the Group configuration tree.

The operation could not be performed because another user was using the business group configuration tree.

S:

Suspends processing.

O:

Wait until another user has finished using the business group configuration tree, and then retry the operation.

KNAN29090-E

A parameter of the communication encryption function for the IM Configuration Management Service is invalid. (parameter = parameter-name, parameter value = parameter-value, cause = cause)

A parameter of the communication encryption function is invalid for the IM Configuration Management service.

S:

Stops the IM Configuration Management service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If A valid value is not specified for a parameter. is displayed for cause, specify a valid value for the parameter in the JP1/Base common definition.

If The value of a parameter is null. is displayed for cause, specify the parameter value in the JP1/Base common definition.

If The value of a parameter exceeds the maximum. is displayed for cause, specify a parameter value that does not exceed the maximum value in the JP1/Base common definition.

If The value of a parameter is not a full path. is displayed for cause, specify a full path in the parameter in the JP1/Base common definition.

KNAN29091-E

Parameters for the communication encryption function for the IM Configuration Management Service could not be collected. (parameter = parameter-name, cause = cause)

An attempt to acquire parameters of the communication encryption function has failed in the IM Configuration Management service.

S:

Stops the IM Configuration Management service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager.

If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If A parameter is not defined. is displayed for cause, specify the parameter in the JP1/Base common definition.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact the system administrator.

KNAN29093-E

The keystore used by the communication encryption function for the IM Configuration Management Service could not be read. (file = file-name)

The keystore that is used by the communication encryption function of the IM Configuration Management service cannot be read.

S:

Stops the IM Configuration Management service.

O:

Check the items listed below, and then restart JP1/IM - Manager. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If there is a keystore, check whether you have read permission for the keystore. If not, set read permission for the keystore.

If there is no keystore, check if the message An attempt to create a keystore failed has been output to the integrated trace log. If the message has been output, take the corrective action given for that message.

KNAN29094-E

An error occurred during the initialization of the communication encryption function for the IM Configuration Management Service. (cause = cause)

An error occurred during initialization of the communication encryption function for the IM Configuration Management service.

S:

Stops the IM Configuration Management service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If A private key or server authentication certificate for the keystore could not be read. is displayed for cause, verify the following, and then restart JP1/IM - Manager:

• Verify that the server certificate and the private key for the server certificate have been placed.

If A system error occurred. is displayed for cause, restart JP1/IM - Manager.

KNAN29095-E

An error occurred during the initialization of the communication encryption function for the IM Configuration Management Service. (cause = cause, file= file-name)

An error occurred during initialization of the communication encryption function for the IM Configuration Management service.

S:

Stops the IM Configuration Management service.

O:

Take the corrective action that is appropriate to the cause displayed, as described below, and then restart JP1/IM - Manager. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

If The root authentication certificate was not found. is displayed for cause, check if there is a root certificate:

• If there is a root certificate, check whether you have read permission for the root certificate. If not, set read permission for the root certificate.

• If there is no root certificate, create a root certificate.

If The root authentication certificate could not be read. is displayed for cause, check the following:

• Verify that there is no problem in the root certificate file.

• Check the appropriate OS log listed in the following to determine if a shortage has occurred in an OS resource such as file descriptors:

- Windows: Windows event log

- UNIX: syslog

KNAN29097-W

The root authentication certificate used by the communication encryption function for the IM Configuration Management Service is no longer valid. (file = file-name)

The root certificate used by the communication encryption function of the IM Configuration Management service has expired.

S:

Continues processing.

O:

Check whether operating with an expired root certificate will cause a problem. If it will, update the root certificate.

KNAN29098-E

Failed to encrypt communications by using the communication encryption function for the IM Configuration Management Service. (host name of connection destination = connection-target-host-name, cause = cause)

An attempt to establish encrypted communication with the connection target has failed.

S:

Stops execution of the request.

O:

If The CN or SAN of the server authentication certificate does not match with the host name of the connection destination. is displayed for cause, verify that the CN or SAN in the server certificate of the connection-target manager host matches the connection-target host name, and then perform the processing again.

If A communication error occurred. is displayed for cause, check the items listed below, and then perform the processing again. If the problem is not resolved, use the data collection tool to collect data, and then contact the system administrator.

• Check if the message Failed to read some of the root authentication certificates was output to the integrated trace log. If this message has been output, take the corrective action given for that message.

• Check if the root certificate corresponding to the server certificate of the connection-target host has been placed on the manager host. If the root certificate has not been placed on the manager host, place the root certificate.

• Check if the server certificate of the connection-target host has expired. If it has expired, renew the server certificate.

If A system error occurred. is displayed for cause, use the data collection tool to collect data, and then contact the system administrator.

KNAN29099-W

"A value set for common definition information (common-definition-name) is outside the valid range. The defaultvalue(default-value) will be used."

An invalid value is specified for the common definition setting.

S:

Ignores the setting and continues processing using the default value.

O:

Revise the specified value.

KNAN29900-I

JP1/IM Configuration Management Cluster environment setup will start now.

Processing to set up the logical host for the IM configuration management will start.

S:

Starts processing to set up the logical host for the IM configuration management.

KNAN29901-I

Copying of the configuration files of logical host to the shared disk will start now.

Processing to copy the logical host settings file to the shared disk will start.

S:

Starts processing to copy the logical host settings file to the shared disk.

KNAN29902-I

JP1/IM Configuration Management cluster environment setup completed successfully.

The logical host environment was set up successfully.

S:

Terminates command processing.

KNAN29903-E

Logical host of JP1/IM-CC is not setup.

The logical host environment for the integrated console has not been set up.

S:

Terminates command processing.

O:

Set up the logical host for the integrated console, and then re-execute the command.

KNAN29904-E

Specified shared directory does not exist.

The specified shared directory does not exist.

S:

Terminates command processing.

O:

Check the specified shared directory, and then re-execute the command.

KNAN29905-E

Failed to get default configuration data.

An attempt to acquire the configuration information has failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager on the physical host have been installed and set up correctly.

KNAN29906-E

Failed to register configuration data.

An attempt to register the configuration information has failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager on the physical host have been installed and set up correctly.

KNAN29907-E

cannot create directory-name

An attempt to create a directory has failed.

S:

Terminates command processing.

O:

Check the name of the specified shared directory and its access permissions, and then re-execute the command.

KNAN29909-E

Logical host of JP1/IM-CF is not setup.

The logical host environment for the IM configuration management has not been set up.

S:

Terminates command processing.

O:

Set up the logical host for the IM configuration management, and then re-execute the command.

KNAN29910-E

Failed to setup socket bind configuration.

An attempt to set up the common definition for the physical host has failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager on the physical host have been installed and set up correctly.

KNAN29911-I

Updating of JP1/IM-CC configuration files will start now.

Updating of the integrated console definition file will start.

S:

Starts updating of the integrated console definition file.

KNAN29912-I

Setting up of socket bind configuration for default environment will start now.

Setup of the physical host communication will start.

S:

Starts setup of the physical host communication.

KNAN29913-I

The logical host setup processing of JP1/IM-CF will start now.

Setup of the logical host for the IM configuration management will start.

S:

Starts setup of the logical host for the IM configuration management.

KNAN29914-E

Failed to update JP1/IM-CC conf files.

An attempt to set up the integrated console has failed.

S:

Terminates command processing.

O:

Make sure that the shared disk for the integrated console has been mounted, and then retry the setup.

KNAN29920-I

The JP1/IM - Configuration setup will now start.

The IM configuration management setup command has started.

S:

Continues processing.

KNAN29921-I

The definition file file-name was relocated.

The file indicated by file-name is relocated.

S:

Continues processing.

KNAN29922-E

'/opt/jp1base/bin/jbssetcnf' could not be executed.

The /opt/jp1base/bin/jbssetcnf command cannot be executed.

S:

Cancels command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager have been installed correctly.

KNAN29923-I

file-name was registered in the common definition.

The common definition information was registered successfully.

S:

Continues processing.

KNAN29924-E

file-name could not be registered in the common definition.

An attempt to register the common definition information has failed.

S:

Cancels command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager have been installed correctly.

KNAN29926-I

JP1/IM-Configuration setup has finished.

The IM configuration management setup command has terminated.

S:

Terminates command processing.

KNAN29927-I

JP1/IM-Configuration setup has finished.

The IM configuration management setup command has terminated.

S:

Terminates command processing.

2.15 Messages output to operation logs (KNAN30000 to KNAN30003)

KNAN30000-I

A login operation was successful.

This message appears if a login operation is successful.

KNAN30001-W

A login operation failed.

This message appears if a login operation failed.

KNAN30002-I

A logout operation was successful.

This message appears if a logout operation is successful.

KNAN30003-W

A logout operation failed.

This message appears if a logout operation failed.

2.16 Messages from the IM database (KNAN11005 to KNAN11213, KFPH00212 to KFPH00213, KFPS01850, and KFPS05210)

KNAN11005-I

The IM database service will now be set up.

Reports that setup of the IM database service will start.

S:

Continues processing.

KNAN11006-I

Size of the IM database service : size

Reports the size of the IM database service to be created.

The value specified in the IMDBSIZE parameter of the setup information file is output for size.

S:

Continues processing.

KNAN11007-I

The data storage directory of the IM database service : directory-name

Reports the data storage directory of the IM database service to be created.

The value specified in the IMDBDIR parameter of the setup information file is output for directory-name.

S:

Continues processing.

KNAN11008-I

Port number of the IM database service : port-number

Reports the port number of the IM database service to be created.

The value specified in the IMDBPORT parameter of the setup information file is output for port-number.

S:

Continues processing.

KNAN11009-Q

Do you want to continue processing? (Y/N):

Queries whether the user wants to continue processing.

S:

Continues processing.

O:

To continue processing, enter Y or y. To suspend processing, enter N or n.

KNAN11010-I

Setup will now start.

Reports that setup of the IM database service will start.

S:

Continues processing.

KNAN11011-I

Setup was canceled.

This message is output when N or n is entered in response to the KNAN11009-Q message output during execution of the setup command.

S:

Suspends processing.

KNAN11012-I

Setup ended normally.

Reports that setup of the IM database service ended normally.

S:

Finishes processing.

KNAN11013-I

The IM database service will now be installed.

Reports that installation of the IM database service will start.

S:

Continues processing.

KNAN11014-I

The IM database service was installed.

Reports that installation of the IM database service is complete.

S:

Continues processing.

KNAN11015-I

The IM database service has already been installed.

This message is output if the setup command is executed when the IM database service is already installed.

S:

Continues processing.

KNAN11016-I

The system database area of the IM database service will now be created.

Reports that creation of the system database area of the IM database service will start.

S:

Continues processing.

KNAN11017-I

The system database area of the IM database service was created.

Reports that creation of the system database area of the IM database service is complete.

S:

Continues processing.

KNAN11018-I

The system database area of the IM database service has already been created.

This message is output if the setup command is executed when the system database area has already been created.

S:

Continues processing.

KNAN11019-I

The integrated monitoring database area of the IM database service will now be created.

Reports that creation of the integrated monitoring database area of the IM database service will start.

S:

Continues processing.

KNAN11020-I

The integrated monitoring database area of the IM database service was created.

Reports that creation of the integrated monitoring database area of the IM database service is complete.

S:

Continues processing.

KNAN11021-E

A command option is invalid.

A command argument is invalid.

S:

Suspends processing.

O:

Referring to the argument that was output in Usage, specify a valid argument, and then re-execute the command.

KNAN11022-E

Superuser permissions are required to execute the command.

The user executing the command does not have Administrator permissions.

S:

Suspends processing.

O:

Execute the command as a user with Administrator or root permissions.

KNAN11023-E

An internal error occurred. (error code = reason-code)

An internal error occurred.

error-code contains the reason code for the cause of the error.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11024-E

Memory allocation has failed.

An attempt to allocate memory failed.

S:

Suspends processing.

O:

Close any unnecessary programs.

KNAN11025-E

A message resource could not be obtained.

A resource could not be obtained.

An attempt to obtain a message resource failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11026-E

A message resource could not be created.

A resource could not be created message.

An attempt to construct a message during message resource acquisition failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11027-E

A message resource could not be initialized.

A resource could not be initialized.

An attempt to acquire a message resource during message resource initialization failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11028-I

Please wait.

Reports that the command is being executed.

S:

Continues processing.

KNAN11029-E

Acquisition of the status of the IM database service has failed.

The status of the JP1/IM - Manager DB Cluster Service and JP1/IM - Manager DB Server services of the IM database service could not be acquired.

S:

Suspends processing.

O:

In Windows:

Determine whether the JP1/IM - Manager DB Cluster Service and JP1/IM - Manager DB Server of the IM database service are registered. If they are registered, stop the service, and then re-execute the command. If they are not registered, use the data collection tool to collect data, and then contact a system administrator.

In UNIX:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11030-E

A required key is not specified in the setup information file. (key = item-name)

An item in the setup information file specified with the setup command -f option is invalid.

item-name: Item to be specified

S:

Suspends processing.

O:

Specify the item in the setup information file indicated by the item name in the message, and then re-execute the command.

KNAN11031-E

The integrated monitoring database area has already been created.

This message is output if the setup command is executed when the integrated monitoring database has already been set up.

S:

Suspends processing.

O:

To set up the integrated monitoring database again, unset up the integrated monitoring database, and then re-execute the command.

KNAN11032-E

Acquisition of log directory information from common definitions failed.

Log directory information could not be acquired from the common definition information.

S:

Suspends processing.

O:

For a logical host:

Create the logical host name of JP1/IM - Manager on the host specified in the parameter. If it has already been created, create the logical host name of JP1/IM - Manager again. If the problem is not resolved, contact a system administrator.

For a physical host:

Perform an overwrite installation of JP1/IM - Manager. If the problem is not resolved, contact a system administrator.

KNAN11033-E

Log initialization has failed. (code = error-code, status = error-status)

Initialization of HNTRLIB2 failed.

error-code contains the HNTR2_Initialize() return value.

error-status contains the return value of HNTR2_GetLastError(), which acquired the reason why HNTR2_Initialize() failed.

S:

Suspends processing.

O:

Make sure that the Hitachi Network Objectplaza Trace Monitor 2 service is running, and then re-execute the command. If the same message is output, contact a system administrator.

KNAN11034-E

An attempt to stop the IM database service has failed.

An attempt to stop the IM database service failed.

HiRDB is placed in invalid status.

S:

Suspends processing.

O:

In Windows:

Stop the IM database service, and then re-execute the command. If the attempt to stop the IM database service fails, contact a system administrator. If the same message is output after the command is retried, use the data collection tool to collect data, and then contact a system administrator.

In UNIX:

Execute the jimdbstop command specifying the -f option to stop the IM database service, and then re-execute the command. If the attempt to stop the IM database service fails, contact a system administrator. If the same message is output after the command is retried, use the data collection tool to collect data, and then contact a system administrator.

KNAN11035-E

An attempt to start the IM database service has failed.

An attempt to start the IM database service failed.

HiRDB is placed in invalid status.

S:

Suspends processing.

O:

In Windows:

Start the IM database service, and then re-execute the command. If the attempt to start the IM database service fails, contact a system administrator. If the same message is output after the command is retried, use the data collection tool to collect data, and then contact a system administrator.

In UNIX:

Execute the jimdbstop command specifying the -f option to stop the IM database service, and then re-execute the command. If the attempt to stop the IM database service fails, contact a system administrator. If the same message is output after the command is retried, use the data collection tool to collect data, and then contact a system administrator.

KNAN11036-E

The installation directory of the IM database service cannot be created.

An attempt to create the installation directory of the IM database service from the setup information file specified using the setup command with the -f option failed.

S:

Suspends processing.

O:

Change the IM database service installation directory indicated in the IMDBENVDIR parameter of the setup information file to a path that can be created for the directory, and then re-execute the command.

KNAN11037-E

The data storage directory of the IM database service cannot be accessed.

The data storage directory of the IM database service could not be accessed.

S:

Suspends processing.

O:

If operating in a cluster environment, make sure that shared disk space was allocated on the host that executed the command, and then re-execute the command.

KNAN11038-E

A key specified in the setup information file is invalid. (key = item-name)

The value of an item in the setup information file specified by the setup command with the -f option is invalid.

item-name: Invalid item name

S:

Suspends processing.

O:

Correct the value of the item specified in the setup information file, and then re-execute the command.

KNAN11039-E

The logical host number is duplicated. (key = item-name)

The logical host number is duplicated.

S:

Suspends processing.

O:

Correct the logical host number, and then re-execute the command.

KNAN11040-E

The setup information file does not exist.

The setup information file specified by the setup command with the -f option does not exist.

S:

Suspends processing.

O:

Make sure that the setup information file exists, specify the correct path, and then re-execute the command.

KNAN11041-E

Installation of the IM database service has failed.

Installation of the IM database service failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message. If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11042-E

Creation of the system database area has failed. Please execute the setup again after the cause of the error is solved, and execute unsetup.

An attempt to create the system database area failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, perform unsetup, and then re-execute the command. If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11043-E

The data storage directory of the IM database service cannot be made.

The data storage directory of the IM database service specified by the IMDBDIR parameter in the setup information file using the setup command with the -f option could not be created.

S:

Suspends processing.

O:

Make sure that the directory specified in the setup information file can be created. Also determine whether the same directory was created in IM database setup for another host. If the directory already exists, specify another directory, and then re-execute the command.

KNAN11044-E

A port number is duplicated. (key = item-name)

The port number is duplicated in the IMDBPORT parameter in the setup information file specified by the setup command with the -f option.

S:

Suspends processing.

O:

Check the following items, specify a unique port number in the system, and then re-execute the command.

Is the specified port number duplicated in another logical host setup?

Is the port number indicated in the services file duplicated?

Is the port number used by the installed HiRDB of another product duplicated?

Does the port number duplicate a temporary port used by another product or OS?

KNAN11045-E

The content of the setup information file is different from the IM configuration database setup.(key = item-name, value = value)

The contents of the setup information file specified when the integrated monitoring database was set up differ from the contents of the setup information file specified when the IM Configuration Management database was set up.

S:

Suspends processing.

O:

If specifying the setup information file using the setup command, change the contents of the setup information file to match the values specified during IM Configuration Management database setup, and then re-execute the command. Alternatively, execute the setup command specifying the -s option, and then re-execute the command.

KNAN11046-E

The service JP1/IM2-Manager DB Server _logical-host-name is not running.

This message is output if the command is executed when the IM database service is not running.

S:

Suspends processing.

O:

Make sure that the service indicated in the message is running. If it is not running, start it, and then re-execute the command.

KNAN11047-E

A key name specified in the setup information file is invalid. (key = item-name)

An item name specified using the setup command -f option is invalid.

item-name: Invalid item name

S:

Suspends processing.

O:

Correct the item specified in the setup information file, and then re-execute the command.

KNAN11048-E

A key name specified in the setup information file is duplicated. (key = item-name)

An item specified using the setup command -f option is duplicated.

item-name: Duplicate item name

S:

Suspends processing.

O:

Delete the duplicate item specified in the setup information file, and then re-execute the command.

KNAN11049-E

The [option-name] option is invalid.

An invalid option is specified, or no option value is specified.

option: Option that cannot be specified

S:

Suspends processing.

O:

Correct the option, and then re-execute the command.

KNAN11050-E

The [option-name] option is defined more than once.

An option is specified more than once.

option: Option specified more than once

S:

Suspends processing.

O:

Correct the option, and then re-execute the command.

KNAN11051-E

An illegal value is specified for the [option-name] option.

An invalid value is specified for an option.

option: Option with an invalid value

S:

Suspends processing.

O:

Correct the value specified for the option, and then re-execute the command.

KNAN11052-E

Acquisition of the installation path from the registry has failed. (error code = error-code)

Acquisition of the JP1/IM - Manager installation path from the registry failed.

S:

Suspends processing.

O:

Perform an overwrite installation of JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN11053-E

An attempt to read a file has failed. (file name = file-name)

An attempt to read a file failed.

file-name: Name of the file that could not be read

S:

Suspends processing.

O:

Make sure that the indicated file can be read. If it can be read, perform an overwrite installation of JP1/IM - Manager.

KNAN11054-E

The format of a file is invalid. (file name = file-name)

The format of a file is invalid.

file-name: Name of the file with an invalid format

S:

Suspends processing.

O:

Perform an overwrite installation of JP1/IM - Manager.

KNAN11055-E

An attempt to set an environment variable has failed.

An attempt to specify an environment variable to connect to the IM database service failed.

S:

Suspends processing.

O:

Make sure that the value can be specified for the environment variable, and then re-execute the command. If the same message is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN11056-E

An attempt to write a file has failed. (file name = file-name)

An attempt to write to a file failed.

file-name: Name of the file that could not be written to

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11057-E

An attempt to copy a file has failed. (file name = file-name)

An attempt to copy a file failed.

file-name: Name of the file that could not be copied

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11058-E

Processing was interrupted because there is not enough free disk space.

Insufficient disk space was specified in the setup information file for the disk storage directory of the IM database service.

S:

Suspends processing.

O:

Allocate disk space from the IM database service data storage directory, or switch to a directory with sufficient disk space, and then re-execute the command.

KNAN11059-E

Acquisition of a host name has failed.

Acquisition of an OS host name failed.

S:

Suspends processing.

O:

Execute the hostname command to make sure that the host name is output normally, and then re-execute the command. If the same message is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN11060-E

There is not enough free space in the disk containing the installation directory of the IM database service.

There is insufficient disk space for the installation directory of the IM database service specified in the IMDBENVDIR parameter of the setup information file using the -f option.

S:

Suspends processing.

O:

Allocate sufficient disk space in the IM database configuration directory, or switch to a directory that has sufficient disk space, and then re-execute the command.

KNAN11061-E

Processing was interrupted because the IM database service is running.

An error occurred during unsetup execution because the IM database service is running.

S:

Suspends processing.

O:

Stop the IM database service, and then re-execute the command.

KNAN11062-E

Processing was interrupted because at least one file is being used.

An error occurred during setup because a file is being used.

S:

Suspends processing.

O:

Stop the IM database service, and then re-execute the command.

KNAN11063-E

A file necessary for installing the IM database service is missing.

A file required to install the IM database service was deleted.

S:

Suspends processing.

O:

Perform an overwrite installation of JP1/IM - Manager, and then re-execute the command.

KNAN11064-W

Unsetup ended. But file deletion has failed. It is necessary to reboot the OS.

A file could not be deleted during unsetup of the IM database service.

S:

Continues processing.

O:

Restart the OS to delete the file that could not be deleted.

KNAN11065-E

The file file-name does not exist.

A file required for command execution does not exist.

file-name: HiRDB setup file

S:

Suspends processing.

O:

Determine whether the indicated file exists. If it does not exist, re-install JP1/IM - Manager. If the file exists, use the data collection tool to collect data, and then contact a system administrator.

KNAN11066-I

Installation directory of the IM database service : directory-name

Reports the installation directory of the IM database service to be created.

S:

Continues processing.

KNAN11067-E

Creation of an RD area has failed.

An attempt to create an RD area failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11068-E

Creation of a table has failed.

An attempt to create a table failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11069-E

The data storage directory of the IM database service cannot be made on a shared disk.

The data storage directory of the IM database service specified in the SHAREDBDIR parameter of the setup information file using the -f option could not be created on a shared disk.

S:

Suspends processing.

O:

Make sure that the directory specified in the setup information file can be created. Also determine whether the same directory was created in IM database setup for another host. If the directory already exists, specify another directory, and then re-execute the command.

KNAN11070-E

Registration of a stored function has failed.

Registration of a stored function failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11071-E

Other commands of the IM database service are executing.

Another command is already being executed in the IM database server.

S:

Suspends processing.

O:

Wait for the other command in the IM database server to finish, and then re-execute the command.

KNAN11074-I

The IM configuration database area of the IM database service will now be created.

Reports that the integrated monitoring database area will be created.

S:

Continues processing.

KNAN11075-I

The IM configuration database area of the IM database service was created.

Reports that the integrated monitoring database area was created.

S:

Continues processing.

KNAN11076-E

The IM configuration database area has already been created.

The IM configuration database area has already been created.

S:

Suspends processing.

O:

To set up the IM Configuration Management database again, unset up the IM Configuration Management database, and then re-execute the command.

KNAN11077-E

The specified logical host host-name does not exist.

The specified logical host does not exist.

S:

Suspends processing.

O:

Make sure that the JP1/IM - Manager logical host was set up, and then re-execute the command.

KNAN11078-E

Creation of the integrated monitoring database area has failed. Please execute the setup again after the cause of the error is solved, and execute unsetup.

An attempt to create the integrated monitoring database failed during setup.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, perform unsetup, and then re-execute the command.

If this message was output to an integrated trace log, take the corrective action given in the message output to the console.

If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11079-E

Creation of the IM configuration database area has failed. Please execute the setup again after the cause of the error is solved, and execute unsetup.

An attempt to create the IM configuration database area failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, perform unsetup, and then re-execute the command.

If this message was output to an integrated trace log, take the corrective action given in the message output to the console.

If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11080-E

The specified set-up type is different from the currently set-up type.

The -c standby option was specified for the command on a host set up as a primary system, or the -c online option was specified for the command on a host set up as a standby system.

S:

Suspends processing.

O:

Correct the parameter, and then re-execute the command.

KNAN11081-E

The content of the setup information file is different from the integrated monitoring database setup. (key = item-name, value = value)

The contents of the setup information file specified during setup of the IM Configuration Management database do not match the contents of the setup information file specified during setup of the integrated monitoring database.

S:

Suspends processing.

O:

To specify the setup information file using the setup command, specify the same values as those specified when the integrated monitoring database was set up, and then re-execute the command. Alternatively, execute the setup command specifying the -s option, and then re-execute the command.

KNAN11082-E

A network drive cannot be specified.

The specified path was output for a network drive.

S:

Suspends processing.

O:

For the database setup command, make sure that the network drive path is not specified in IMDBDIR, IMDBENVDIR, or SHAREDBDIR.

For the database backup recovery command, make sure that the network drive path is not specified in the path specified in the parameter.

KNAN11083-E

A file name reserved by Windows cannot be specified.

The specified path contains a Windows reserved file name.

S:

Suspends processing.

O:

For the database setup command, make sure that a Windows reserved file name is not specified in IMDBDIR, IMDBENVDIR, or SHAREDBDIR.

For the database backup recovery command, make sure that a Windows reserved file name is not specified in the path specified in the parameter.

KNAN11084-E

Creation of a database file system area has failed.

An attempt to create a database file system area failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message.

If no error message was output before this message, check the following items, perform unsetup, and then re-execute the command.

Does the file system of the path specified in IMDBDIR correspond to a large file?

Is the kernel parameter set appropriately?

Is there an error in the host name specified in LOGICALHOSTNAME or ONLINEHOSTNAME? Is the specified host name set correctly in the hosts file?

KNAN11085-E

The service JP1/IM2-Manager database Cluster Service_logical-host-name is running.

This message is output if the command is executed when the server used for clustering the IM database service is running.

S:

Suspends processing.

O:

Stop the service indicated in the message, and then re-execute the command.

KNAN11086-E

Could not start setup.

An attempt to start setup failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command. If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11087-W

Deletion of the file file-name has failed.

An attempt to delete a file failed.

S:

Continues processing.

O:

Wait until the command has finished, and then delete the indicated file.

KNAN11088-E

Deletion of the file file-name has failed.

An attempt to delete a file failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11089-E

Creation of the directory directory-name has failed.

An attempt to create a directory failed.

S:

Suspends processing.

O:

Make sure that the directory indicated in the message can be created.

KNAN11090-I

The integrated monitoring database was created. (host name = host-name, database size = size, port number = port-number, database storage directory = DB-storage-directory, database installation directory = DB-installation-destination, database storage directory [SHARE] = shared-disk-DB-storage-directory)

This message outputs information about the integrated monitoring database that was created.

host-name: For a logical host, the logical host name is output; for a physical host, (JP1_DEFAULT) is output

size: Database size

port-number: Port number

DB-storage-directory: Database storage destination

DB-installation-destination: Database installation destination

shared-disk-DB-storage-directory: For a cluster environment, the storage destination of the database created on the shared disk is output. For a physical host, a space is output.

S:

Continues processing.

KNAN11091-I

The integrated monitoring database was deleted. (host name = host-name, database size = size, port number = port-number, database storage directory = DB-storage-directory, database installation directory = DB-installation-destination, database storage directory [SHARE] = shared-disk-DB-storage-directory)

This message outputs information about the integrated monitoring database that was deleted.

host-name: For a logical host, the logical host name is output; for a physical host, (JP1_DEFAULT) is output

size: Database size

port-number: Port number

DB-storage-directory: Database storage destination

DB-installation-destination: Database installation destination

shared-disk-DB-storage-directory: For a cluster environment, the storage destination of the database created on the shared disk is output. For a physical host, a space is output.

S:

Continues processing.

KNAN11092-I

The IM configuration database was created. (host name = host-name, database size = size, port number = port-number, database storage directory = DB-storage-directory, database installation directory = DB-installation-destination, database storage directory [SHARE] = shared-disk-DB-storage-directory)

This message outputs information about the IM Configuration Management database that was created.

host-name: For a logical host, the logical host name is output; for a physical host, (JP1_DEFAULT) is output

size: Database size

port-number: Port number

DB-storage-directory: Database storage destination

DB-installation-destination: Database installation destination

shared-disk-DB-storage-directory: For a cluster environment, the storage destination of the database created on the shared disk is output. For a physical host, a space is output.

S:

Continues processing.

KNAN11093-I

The IM configuration database was deleted. (host name = host-name, database size = size, port number = port-number, database storage directory = DB-storage-directory, database installation directory = DB-installation-destination, database storage directory [SHARE] = shared-disk-DB-storage-directory)

This message outputs information about the IM Configuration Management database that was deleted.

host-name: For a logical host, the logical host name is output; for a physical host, (JP1_DEFAULT) is output

size: Database size

port-number: Port number

DB-storage-directory: Database storage destination

DB-installation-destination: Database installation destination

shared-disk-DB-storage-directory: For a cluster environment, the storage destination of the database created on the shared disk is output. For a physical host, a space is output.

S:

Continues processing.

KNAN11094-E

Other processes are accessing the IM database service.

The command could not be executed because other processes are accessing the IM database service.

S:

Suspends processing.

O:

Stop the JP1/IM - Manager service, and then re-execute the command.

Alternatively, make sure that no other database operation is being executed, wait for the command to finish, and then retry the operation.

KNAN11095-I

Shared disk for data storage directory of the IM database service: shared-disk-storage-directory

Reports the data storage directory of the IM database service on the shared disk created during cluster setup.

S:

Continues processing.

KNAN11096-E

JP1_DEFAULT is specified for the hostname.

An unidentifiable character string was specified in a parameter.

S:

Suspends processing.

O:

Correct the parameter, and re-execute the command.

KNAN11097-E

There is not enough free space on the disk containing the data storage directory of the IM database service. (key = item-name, necessary size = required-size Mbyte)

The data storage directory and the shared data storage directory of the IM database service specified in the setup information file contain insufficient disk space to create the IM database service.

item-name: IMDBDIR or SHAREDBDIR

required-size: Space required to create the IM database service (in megabytes)

S:

Suspends processing.

O:

Do one of the following:

Specify a directory that has sufficient disk space.

Allocate the amount of disk space indicated in the message to the specified directory.

KNAN11098-W

An attempt to change the startup type of the service JP1/IM2-Manager database Server_logical-host-name has failed.

An attempt to change the startup type of the service indicated in the message from Automatic to Manual failed.

S:

Continues processing.

O:

Wait for the command to finish normally, and then, in the window that manages the service, change the startup type of the service indicated in the message from Automatic to Manual.

KNAN11099-E

Initialization of common definitions has failed.

An attempt to initialize common definition information failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11100-I

Unsetup of the IM database service will now be performed.

Reports that unsetup of the IM database service will be performed.

S:

Continues processing.

KNAN11101-I

Unsetup will now start.

Reports that unsetup processing of the IM database service will start.

S:

Continues processing.

KNAN11102-I

The integrated monitoring database area of the IM database service will now be deleted.

Reports that the integrated monitoring database area of the IM database service will be deleted.

S:

Continues processing.

KNAN11103-I

The integrated monitoring database area of the IM database service was deleted.

Reports that the integrated monitoring database area of the IM database service was deleted.

S:

Continues processing.

KNAN11104-I

The system database area of the IM database service will now be deleted.

Reports that the system database area will be deleted.

S:

Continues processing.

KNAN11105-I

The system database area of the IM database service was deleted.

Reports that the system database area of the IM database service was deleted.

S:

Continues processing.

KNAN11106-I

The IM database service will now be uninstalled.

Reports that the IM database service will be uninstalled.

S:

Continues processing.

KNAN11107-I

The IM database service was uninstalled.

Reports that the IM database service was uninstalled.

S:

Continues processing.

KNAN11108-I

Unsetup ended normally.

Reports that unsetup of the IM database service ended normally.

S:

Finishes processing.

KNAN11109-E

The IM database service is not set up.

The setup command cannot be executed.

S:

Suspends processing.

KNAN11110-I

Unsetup was canceled.

Reports that N or n was entered in response to the KNAN11009-Q message that was output when the unsetup command was executed.

S:

Suspends processing.

KNAN11111-I

The system database area of the IM database service will not be deleted.

Reports that the system database area will not be deleted. This message is output in the following cases:

The IM Configuration Management database was set up when the integrated monitoring database setup command is executed.

The integrated monitoring database was set up when the IM Configuration Management database setup command is executed.

S:

Continues processing.

KNAN11112-I

The IM database service will not be uninstalled.

Reports that the system database will not be uninstalled. This message is output in the following cases:

The IM Configuration Management database was set up when the integrated monitoring database setup command is executed.

The integrated monitoring database was set up when the IM Configuration Management database setup command is executed.

S:

Continues processing.

KNAN11113-E

The integrated monitoring database is not set up.

The integrated monitoring database area unsetup command was executed in an environment where only the IM Configuration Management database was set up.

S:

Suspends processing.

KNAN11114-E

Deletion of a system database area has failed.

An attempt to delete a system database area failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command. If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11115-E

Uninstallation of the IM database service has failed.

An attempt to uninstall the IM database service failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command.

If the problem is not resolved, restart the computer, and then re-execute the command.

If the same message is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN11116-E

An attempt to update the setup list has failed.

An attempt to update the setup list failed.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11117-E

The IM database service is running.

There was an attempt to uninstall the IM database service while the IM database service is running.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11118-E

The specified path is invalid.

The specified path is a relative path, and an invalid character is used as the path delimiter.

S:

Suspends processing.

O:

Check the following items, and then re-execute the command.

Is a relative path specified?

Is the path delimiter character duplicated?

In Windows, does the file name end with a period followed by a space?

KNAN11119-W

Deletion of at least one file has failed. (directory name = directory-name)

An attempt to delete a file in the directory indicated in the message failed.

S:

Continues processing.

O:

Wait until the command has finished, and then delete the directory indicated in the message.

KNAN11120-E

Acquisition of a file has failed. (file name: file-name)

An attempt to acquire a file failed.

S:

Suspends processing.

O:

Check the indicated file, and then contact a system administrator.

KNAN11121-E

The IM configuration database is not set up.

The IM Configuration Management database area unsetup command was executed in an environment where only the integrated monitoring database has been set up.

S:

Suspends processing.

KNAN11122-E

Deletion of the integrated monitoring database area has failed.

An attempt to delete the integrated monitoring database area failed.

S:

Continues processing.

O:

If you are using the IM Configuration Management database, unset up the IM Configuration Management database, and then restart the system to delete the IM database area.

If you are not using the IM Configuration Management database, restart the system to delete the IM database area.

KNAN11123-E

Deletion of the IM configuration database area has failed.

An attempt to delete the IM configuration database area failed.

S:

Continues processing.

O:

If you are using the integrated monitoring database, unset up the integrated monitoring database, and then restart the system to delete the IM database.

If you are not using the integrated monitoring database, restart the system to delete the IM database area.

KNAN11124-I

The IM configuration database area of the IM database service will now be deleted.

Reports that the IM Configuration Management database area will be deleted.

S:

Continues processing.

KNAN11125-I

The IM configuration database area of the IM database service was deleted.

Reports that the IM Configuration Management database area was deleted.

S:

Continues processing.

KNAN11140-E

An error occurred while the IM database service was being installed. (error code: error-code)

An error occurred while the IM database service was being installed.

S:

Suspends processing.

O:

If the following error code is displayed, take the indicated corrective action:

Error code: 02

A file of the IM database service cannot be updated because a process (for example, event viewer, virus scan, or backup software) is using that file. Restart the machine and make sure that the event viewer, virus scan, and backup software are not started, and then re-execute the command. If a setup information file is specified for a command option, do not change the contents of the setup information file before executing the command.

Error code: Other than 02

If another error message was output before this message, take the corrective action given for that message, restart the machine, and then re-execute the command.

If no error message was output before this message, check the following items, restart the machine, and then re-execute the command:

- Does the file system of the path specified in IMDBDIR correspond to a large file?

- Is the kernel parameter set appropriately?

- Is an existing host name specified in LOGICALHOSTNAME or ONLINEHOSTNAME?

- Is the logical IP associated with the host specified in LOGICALHOSTNAME valid?

If the message appears again after the above actions are taken, use the data collection tool to collect data, and then contact a system administrator.

KNAN11141-E

An error occurred while the system DB area was being created. (error code: error-code)

An error occurred while the system database area was being created.

S:

Suspends processing.

O:

Check the following items, perform unsetup, and then re-execute the command.

Does the file system of the path specified in IMDBDIR correspond to a large file?

Is the kernel parameter set appropriately?

Is an existing host name specified in LOGICALHOSTNAME or ONLINEHOSTNAME?

Is the logical IP associated with the host specified in LOGICALHOSTNAME valid?

Does the host name of the physical host or logical host where the IM database is set up meet the conditions listed below? If not, correct the host name so that the conditions can be met. Make sure that the host name persists even after the operating system restarts.

- Physical host name

A name consists of alphanumeric characters, hyphens (-), and periods (.), and the maximum length is 32 characters.

- Logical host name

A name consists of alphanumeric characters and hyphens (-), and the maximum length is 32 characters.

KNAN11142-E

An error occurred while the IM database service was being uninstalled. (error code: error-code)

An error occurred while the IM database service was being uninstalled.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command. If no error message was output before this message, restart the system, and then re-execute the command. If the same message is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN11143-E

Configuration of the IM database service is invalid.

The configuration of the IM database service is invalid.

S:

Suspends processing.

O:

Make sure that the IM database installation directory or data storage directory is accessible, and then re-execute the command. It the same message is output, unset up the IM database service, and then set it up again.

KNAN11144-W

Configuration of the IM database service is invalid.

This message is output when the IM database service file configuration is invalid during unsetup.

S:

Continues processing.

O:

Stop processing in response to the KNAN11009-Q message, check the following items, and then retry the unsetup.

Make sure that no files remain in the IM database installation directory or data storage directory. If any files remain, delete all of the files.

If unsetup was performed for the primary system in a cluster environment, make sure that the shared disk is mounted. If the shared disk is not mounted, mount it.

If you have chosen to continue processing in response to the KNAN11009-Q message, restart the system to complete unsetup of the IM database service.

KNAN11145-E

The file or directory cannot be accessed. (path name = path-name)

The file or directory could not be accessed.

path-name: Path of the file or directory that could not be accessed

S:

Suspends processing.

O:

Determine whether the path indicated in the message can be accessed. If the path indicated in the message refers to a shared disk, determine whether the shared disk can be accessed.

KNAN11146-I

Logical host name: logical-host-name

Reports the logical host name of the IM database service to be created.

logical-host-name outputs the value specified in the LOGICALHOSTNAME parameter of the setup information file.

S:

Continues processing.

KNAN11147-I

Online host name: primary-system-host-name

Reports the primary system host name of the IM database service to be created.

primary-system-host-name outputs the value specified in the ONLINEHOSTNAME parameter of the setup information file.

S:

Continues processing.

KNAN11148-I

Logical host number: logical-host-number

Reports the logical host number of the IM database service to be created.

logical-host-number outputs the value specified in the LOGICALHOSTNUMBER parameter of the setup information file.

S:

Continues processing.

KNAN11150-I

The IM database service will now be backed up.

Reports that the IM database service will be backed up.

S:

Continues processing.

KNAN11151-I

The IM database service was successfully backed up.

Reports that the IM database service was backed up.

S:

Terminates processing.

KNAN11152-E

An attempt to back up the IM database service has failed.

An attempt to back up the IM database service failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command.

If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11153-I

The IM database service will now be recovered.

Reports that the IM database service will be recovered.

S:

Continues processing.

KNAN11154-I

The IM database service was successfully recovered.

Reports that the IM database service was recovered.

S:

Terminates processing.

KNAN11155-E

Recovery of the IM database service has failed.

An attempt to recover the IM database service failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command.

If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11156-E

The backup file does not exist.

The backup file specified using the -i option could not be found when the recovery command was executed.

S:

Suspends processing.

O:

Correct the backup file name specified using the -i option, and then re-execute the command.

KNAN11157-E

The specified recovery format is different from the format of the backup data.

This message is output in the following cases:

When the data backed up for use in failure recovery is specified in a recovery command used for extension.

When the data backed up for use in extension is specified in a recovery command used for failure recovery.

S:

Suspends processing.

O:

Correct the command parameter or the backup file, and then re-execute the command.

KNAN11158-I

The IM database service will now be reorganized.

Reports that the IM database service will be re-organized.

S:

Continues processing.

KNAN11159-I

The IM database service was successfully reorganized.

Reports that the IM database service was re-organized.

S:

Terminates processing.

KNAN11160-E

Reorganization of the IM database service has failed.

An attempt to re-organize the IM database service failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command.

If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11161-I

The unused area of the IM database service will now be deallocated.

Reports that the unused area of the IM database service will be de-allocated.

S:

Continues processing.

KNAN11162-I

The unused area of the IM database service was successfully deallocated.

Reports that the unused area of the IM database service was de-allocated.

S:

Terminates processing.

KNAN11163-E

Deallocation of the unused area of the IM database service has failed.

An attempt to de-allocate the unused area of the IM database service failed.

S:

Suspends processing.

O:

If another error message was output before this message, take the corrective action given for that message, and then re-execute the command.

If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11164-E

The configuration of the IM database service is different than from when the backup was performed.

The database size and setup configuration for when a recovery command is used for failure recovery does not match the configuration of the backup acquired for use in failure recovery.

S:

Suspends processing.

O:

Set up the database configuration the same as for when the backup is acquired for use in failure recovery, and then re-execute the command.

KNAN11165-E

A directory with the same name already exists. (directory name = directory-name)

A directory with the same name as the backup file already exists.

S:

Suspends processing.

O:

Revise the name of the backup file, and then re-execute the command.

KNAN11166-E

A directory cannot be specified.

The specified path refers to a directory.

S:

Suspends processing.

O:

Correct the path, and then re-execute the command.

KNAN11167-E

A UNC path name cannot be specified.

The specified path is in UNC path format.

S:

Suspends processing.

O:

Correct the path, and then re-execute the command.

KNAN11168-E

A stream name cannot be specified.

The specified path is in stream format.

S:

Suspends processing.

O:

Correct the path, and then re-execute the command.

KNAN11169-W

A backup file with the same name already exists. The existing file will be overwritten.

A file with the same name as the backup file to be output during execution of the backup command already exists. The existing file will be overwritten. After this message is output, a KNAN11009-Q message is output to query whether processing is to continue.

S:

Continues processing.

O:

To continue processing, enter Y or y in response to the KNAN11009-Q message that is output after this message. To stop processing, enter N or n in response to the KNAN11009-Q message that is output after this message.

KNAN11170-E

The specified path is too long. (path size = maximum-path-size)

The length of the specified path exceeds the maximum.

S:

Suspends processing.

O:

Correct the specified path, and re-execute the command.

KNAN11171-E

Creation of the directory for storing backup files has failed.

An attempt to create a directory for storing backup files specified using the backup command -o option failed.

S:

Suspends processing.

O:

Specify a directory that is able to store backup files, and then re-execute the command.

KNAN11172-E

An internal error occurred while the IM database service was being backed up.

An unexpected error occurred during backup processing of the IM database service.

S:

Suspends processing.

O:

Check the following items, and then re-execute the command:

Is the correct path specified as the output destination of the backup file?

Can the directory specified as the output destination of the backup file be written to?

Does a directory with the same name as the output destination of the backup file exist?

KNAN11173-E

An internal error occurred while the IM database service was being recovered.

An unexpected error occurred during recovery of the IM database service.

S:

Suspends processing.

O:

For the MAINT parameter, check the following items, and then re-execute the command:

Is a backup file that was acquired from the same OS specified?

Are the backup acquisition time and database configuration the same?

Is the setup information file of the current IM database the same as when the backup was acquired?

For the EXPAND parameter, see 11.5.1(60) Actions to take if extended recovery fails in the JP1/Integrated Management 2 - Manager Administration Guide.

KNAN11174-E

An internal error occurred while the IM database service was being reorganized.

An unexpected error occurred while the IM database service was being re-organized.

S:

Suspends processing.

O:

Make sure that there is sufficient free space in the IM database installation directory, and then re-execute the command.

KNAN11175-E

An internal error occurred while unused area of the IM database service was being deallocated.

An unexpected error occurred while unused area of the IM database service was being de-allocated.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KNAN11176-I

The backup was canceled.

This message is output when N or n is entered in response to the KNAN11009-Q message output during execution of the backup command.

S:

Suspends processing.

KNAN11177-I

The reorganization was canceled.

This message is output when N or n is entered in response to the KNAN11009-Q message output during execution of the re-organization command.

S:

Suspends processing.

KNAN11178-I

Deallocation of the unused area of the IM database service was canceled.

This message is output when N or n is entered in response to the KNAN11009-Q message output during execution of the unused area de-allocation command.

S:

Suspends processing.

KNAN11179-I

Processing to start the IM database service will now start.

Reports that processing to start the IM database service will start.

S:

Continues processing.

KNAN11180-I

Processing to start the IM database service ended normally.

Reports that processing to start the IM database service ended.

S:

Terminates processing.

KNAN11181-I

Processing to start or stop the IM database service is in progress.

Reports that processing to start or stop the IM database service is in progress.

S:

Continues processing.

KNAN11182-I

The IM database service is running.

Reports that the IM database service is running.

S:

Continues processing.

KNAN11183-I

The IM database service is stopped.

Reports that the IM database service stopped.

S:

Continues processing.

KNAN11184-I

The IM database service started normally.

Reports that the IM database service started.

S:

Continues processing.

KNAN11185-I

Processing to stop the IM database service will now start.

Reports that processing to stop the IM database service will start.

S:

Continues processing.

KNAN11186-I

Processing to stop the IM database service ended normally.

Reports that processing to stop the IM database service ended.

S:

Terminates processing.

KNAN11187-I

The IM database service stopped normally.

Reports that the IM database service stopped.

S:

Continues processing.

KNAN11188-I

The status of the IM database service will now be confirmed.

Reports that the status of the IM database service will be confirmed.

S:

Continues processing.

KNAN11189-I

The status of the IM database service was successfully confirmed.

Reports that the status of the IM database service was confirmed.

S:

Terminates processing.

KNAN11190-W

The IM database service is stopped (restarting was interrupted).

The IM database service was suspended.

S:

Continues processing.

O:

Execute the jimdbstop -f command to forcibly stop the IM database service, and then restart the IM database.

KNAN11191-E

An internal error occurred during confirmation of the status of the IM database service.

An attempt to confirm the status of the IM database service failed.

S:

Suspends processing.

O:

Make sure that the IM database installation directory or the data storage directory can be accessed, and then re-execute the command. If the same message is output, perform unsetup on the IM database service, and then set it up again.

KNAN11192-E

Please execute this command from an administrator console.

The UAC user does not have Administrator permissions.

S:

Suspends processing.

KNAN11193-E

The IM database service is not set up. It is necessary to specify the option (option-name).

If the database is not set up, the -f option must be specified. The -s option cannot be specified.

S:

Suspends processing.

O:

Correct the parameter, and then re-execute the command.

KNAN11194-I

The recovery was canceled.

This message is output when N or n is entered in response to the KNAN11009-Q message output during execution of the recovery command.

S:

Suspends processing.

KNAN11195-E

The specified directory does not exist.

The specified directory does not exist.

S:

Suspends processing.

O:

Make sure that the directory indicated in the message exists.

KNAN11196-E

The directory for storing backup files does not exist.

The directory that stores the specified backup information file does not exist.

S:

Suspends processing.

O:

Make sure that the directory indicated in the message exists.

KNAN11197-I

The IM database service will now be updated.

The IM database service will now be updated.

S:

Continues processing.

KNAN11198-I

The IM database service was successfully updated.

The IM database service was successfully updated.

S:

Terminates processing.

KNAN11199-E

Failed to update the IM database service.

An attempt to update the IM database service has failed.

S:

Suspends processing.

O:

If an error message was output before this message, take the corrective action given for that message. Then re-execute the command.

If no error message was output before this message, use the data collection tool to collect data, and then contact a system administrator.

KNAN11200-I

The update was canceled.

The update processing has been terminated.

S:

Suspends processing.

KNAN11201-I

The IM database service is the latest.

The IM database service is in the latest status.

S:

Terminates processing.

KNAN11202-I

The overwrite is necessary for the IM database.

Overwrite installation of the IM database service is required.

S:

Continues processing if the jimdbupdate command was executed with the -i option specified.

Terminates processing if the jimdbupdate command with the -i option specified was not executed.

O:

If the jimdbupdate command with the -i option specified was not executed, specify the -i option, and then re-execute the jimdbupdate command.

KNAN11203-I

host name: host-name

This message reports the host name for the IM database service to be created.

For host-name, the value specified for IMDBHOSTNAME in the setup information file (jimdbsetupinfo.conf) is output.

S:

Continues processing.

KNAN11204-E

An attempt to update the index of the IM database service has failed.

An attempt to update the indexes used by the IM database service has failed.

S:

Stops processing the command.

O:

Make sure that there is sufficient disk space, memory, and other OS resources.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact the system administrator.

KNAN11205-E

Failed to establish a connection to an IM database service.

An attempt to establish connection with the IM database service has failed.

S:

Terminates processing.

O:

Stop the JP1/IM - Manager service, and then re-execute the command.

If the error cannot be corrected by re-executing the command, collect the required JP1/IM data, and then contact the system administrator.

KNAN11206-E

An error occurred while an operation was being performed for an IM database service.

An error occurred while the IM database service was running.

S:

Terminates processing.

O:

Make sure that there is sufficient disk space, memory, and other OS resources.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact the system administrator.

KNAN11207-I

An update of the table schema of an IM database service is required.

The table schema of the IM database service must be updated.

S:

Continues processing if the jimdbupdate command was executed with the -i option specified.

Terminates processing if the jimdbupdate command with the -i option specified was not executed.

O:

If the jimdbupdate command with the -i option specified was not executed, specify the -i option, and then re-execute the jimdbupdate command.

KNAN11208-I

The table schema of the IM database service will be updated.

The update operation on the table schema of the IM database service was started.

S:

Continues processing.

KNAN11209-I

The table schema of the IM database service was updated.

The update operation on the table schema of the IM database service has finished.

S:

Continues processing.

KNAN11210-W

The table schema could not be checked because a common disk could not be accessed.

The table schema could not be checked because the shared disk could not be accessed.

S:

Skips the table schema check process and continues processing.

O:

If this warning event occurred on the primary node, check if the shared disk has been mounted, and then re-execute the command.

If the error cannot be corrected by re-executing the command, collect the required JP1/IM data, and then contact the system administrator.

KNAN11211-I

An update of the configuration files of an IM database service is required.

The configuration files of the IM database service must be updated.

S:

Continues processing if the jimdbupdate command was executed with the -i option specified.

Terminates processing if the jimdbupdate command with the -i option specified was not executed.

O:

If the jimdbupdate command without the -i option specified was executed, specify the -i option, and then re-execute the jimdbupdate command.

KNAN11212-I

The configuration files of the IM database service will be updated.

The update operation on the configuration files of the IM database service was started.

S:

Continues processing.

KNAN11213-I

The configuration files of the IM database service were updated.

The update operation on the configuration files of the IM database service has finished.

S:

Continues processing.

KFPH00212-I

Table should be reorganized,RDAREA="RD-area-name",AUTHID=authorization-identifier,TABLE=table-name

This message is output when re-organization of the IM Configuration Management database is required.

RD-area-name: Name of the RDAREA of the database that requires re-organization

authorization-identifier: JP1IMDB

table-name: Name of the table that requires re-organization

S:

Continues processing.

O:

Execute the re-organization command to re-organize the IM database service.

KFPH00213-W

All segments in RDAREA "RD-area-name" allocated

The RDAREA in the IM Configuration Management database is insufficient.

RD-area-name: Name of the RDAREA that is of insufficient size

S:

Suspends processing.

O:

Execute the free page de-allocation command or the re-organization command to allocate the free space in the IM database service.

KFPS01850-I

HiRDB system terminated. mode=termination-mode

Reports that the IM database service stopped.

termination-mode: Normal termination, planned termination, forcible termination

S:

Stops the IM database service.

KFPS05210-I

HiRDB system initialization process complete

Reports that the IM database service started normally.

S:

Starts the IM database service normally.

2.17 Messages related to Intelligent Integrated Management Base (KAJY00001-E to KAJY52032)

KAJY00001-E

Cannot connect to the Server.

The Intelligent Integrated Management Base Service cannot be connected. The possible causes are as follows:

The Service is not running.

The Service is busy.

The network connection with the Service is interrupted.

S:

Suspends processing.

O:

If the Service is not running

Restart the Intelligent Integrated Management Base Service.

If the Service is busy

The connection can be established if you make a retry to connect.

If the network connection with the host at the connection destination is interrupted

Check the network environment where the host at the connection destination is in. If there is a firewall between the Service and the host at the connection destination, check the firewall settings. If the session is discarded, log in again.

KAJY00004-I

The Intelligent Integrated Management Base Service will now start. : logical-host-name

The Intelligent Integrated Management Base Service was started.

KAJY00005-I

The Intelligent Integrated Management Base Service will now terminate.: logical-host-name

The Intelligent Integrated Management Base Service was stopped.

KAJY00006-E

The Intelligent Integrated Management Base Service was ended abnormally. : logical-host-name

The Intelligent Integrated Management Base Service on the host (host-name) was stopped abnormally due to an error that prevents the service from continuing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJY00007-E

A system error occurred. : maintenance-information

System error occurred.

S:

Aborts processing where the error occurred.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJY00008-E

A memory shortage occurred. : maintenance-information

memory shortage occurred.

S:

Aborts processing where the error occurred.

O:

Retry the operation. If the problem cannot be resolved, use the data collection tool to collect data, and then contact the system administrator.

KAJY00009-E

The REST API request body size exceeds the limit. (jp1user-name: jp1user-name, URL path: URL-path, upper limit: upper-limit, size of the sent request body: size-of-the-sent-request-body)

A request cannot be accepted because the size of the REST API request body exceeded the upper limit.

S:

Suspends processing.

O:

Split one REST API request into a smaller request body size and try again.

KAJY00010-E

The specified REST API request header value is invalid. (jp1user-name : jp1user-name, URL path : URL-path, property name : property-name)

The REST API cannot be executed because an invalid REST API request header is specified.

S:

Aborts processing.

O:

If the property indicated by the message is not specified, then specify it. If it is already specified, check if the specified value is correct. Then, try again.

KAJY00011-E

Cannot read the keystore used by the communication encryption function in the Intelligent Integrated Management Base Service.(file : file-name)

The keystore used by the communication encryption function of the Intelligent Integrated Management Base Service cannot be read. (File name: file-name)

S:

Terminates the Intelligent Integrated Management Base Service.

O:

Check the items below, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

If the directory where the keystore is to be stored does not exist, create it.

If the keystore exists, check whether you have read permission for the keystore. If not, set read permission for the keystore.

If no keystore exists, check whether the message An attempt to create a keystore failed has been output to the integrated trace log. If so, take the corrective action given for that message.

KAJY00012-E

Cannot collect the parameters in the communication encryption function in Intelligent Integrated Management Base Service. (parameter : parameter-name)

Parameters for the communication encryption function for the Intelligent Integrated Management Base Service could not be acquired.

S:

Terminates the Intelligent Integrated Management Base Service.

O:

Check the item below, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Set the parameter in the common definitions.

KAJY00013-E

The parameter in the communication encryption function in Intelligent Integrated Management Base Service is invalid. (parameter : parameter-name, parameter value : parameter-value, cause : a-valid-value-is-not-specified-for-a-parameter.)

A parameter of the communication encryption function for the Intelligent Integrated Management Base Service is invalid.

S:

Terminates the Intelligent Integrated Management Base Service.

O:

Check the item below, and then restart JP1/IM - Manager. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Set a valid value for the parameter in the common definitions.

KAJY00014-E

Failed to initialize communication infrastructure. : maintenance-information

An attempt to initialize the communication infrastructure failed.

S:

Terminates the Intelligent Integrated Management Base Service.

O:

Check the settings file, and take the corrective action given.

KAJY00015-W

Failed to read the Intelligent Integrated Management Base definition file. The process will continue by using the default value.(property name : property-name, default value : default-value)

An attempt to read the Intelligent Integrated Management Base definition file failed.

S:

Continues processing.

O:

Check whether the Intelligent Integrated Management Base definition file exists. If the file exists check whether administrator (in Windows) or root (in UNIX) has read permission on the file.

KAJY00016-W

The Intelligent Integrated Management Base definition file is invalid. The process will continue by using the default value.(property name : property-name, default value : default-value)

There is an error in the Intelligent Integrated Management Base definition file.

S:

Continues processing.

O:

Check the content of the Intelligent Integrated Management Base definition file, and if needed, modify it.

KAJY00017-E

The Intelligent Integrated Management Base Service could not be started because the environment is invalid. (cause : cause)

An invalid environment prevented the Intelligent Integrated Management Base from being started.

S:

Suspends processing.

O:

Determine whether a system error has occurred.

Uninstall JP1/IM2 - Manager and reinstall it, and then try again.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact the system administrator.

KAJY00018-E

A connection to the authentication server could not be established.

The authentication server cannot be connected.

S:

Continues processing.

O:

Check the following items, and then take the appropriate corrective action:

Is the authentication server running?

Is communication with the authentication server possible?

Are the authentication server settings correct?

Whether the settings of the Communication encryption function are wrong, if you are using the Communication encryption function.

KAJY00019-W

The specified window could not be displayed because the URL is incomplete.

The specified window could not be displayed because the URL was incomplete.

S:

Continues processing.

O:

Check whether the obtained URL matches the one you specified in the WWW browser.

If the problem cannot be resolved, check that the length of the URL does not exceed the maximum length of the URL for the WWW browser, and then access it again in a different supported WWW browser.

KAJY00020-W

The specified window could not be displayed because the URL is invalid.

The specified window could not be displayed because an invalid URL was specified.

S:

Continues processing.

O:

Obtain the URL again.

KAJY00021-E

Failed to read the Intelligent Integrated Management Base definition file.

Failed to read the Intelligent Integrated Management Base definition file.

S:

Terminates the Intelligent Integrated Management Base Service.

O:

Check the following content, and then restart JP1/IM - Manager.

Check whether the Intelligent Integrated Management Base definition file exists.

If the Intelligent Integrated Management Base definition file exists, check whether you have permission (Administrators permissions in Windows, or root permissions in UNIX) to read the file.

KAJY00022-E

The Intelligent Integrated Management Base definition file is invalid.(property name : property-name)

The Intelligent Integrated Management Base definition file is invalid.

S:

Terminates the Intelligent Integrated Management Base Service.

O:

Fix the content in the Intelligent Integrated Management Base definition file (imdd.properties), and then restart JP1/IM - Manager.

KAJY00023-W

The specified window could not be displayed because the parameter is invalid. (Parameter Name : parameter-name)

The value specified for a query parameter is invalid.

S:

Continues processing.

O:

Check the following points, and then retry the access:

Obtain the URL again if you used the Operation menu button in the Integrated Operation Viewer window to obtain the URL.

Check whether the query parameter has a correct value and make corrections if necessary.

When seqno is indicated, check that an event with the event database serial number of seqno exists in the integrated monitoring database.

When sid is indicated, review the configuration to make sure that business group filtering does not exclude the target IM management node. If filtering is not performed, check that the IM management node for the tree SID specified for sid exists.

KAJY01000-E

The user does not have permission to execute REST API.(jp1user-name : jp1user-name, URL path : url-path)

Execution failed because the user does not have sufficient permissions to execute the REST API.

S:

Suspends processing.

O:

Review the JP1 permission level for the JP1 user.

KAJY01001-E

Your session is invalid.

Please log in again.

The session is invalid.

S:

Suspends processing and opens the Login window.

O:

Log in again from the Login window.

KAJY02000-E

The file does not exist.(file-name)

The file does not exist.

S:

Suspends processing.

O:

Check whether the file exists in the directory specifed by the command option. If the file exists check whether administrator (in Windows) or root (in UNIX) has read permission on the file.

If an error occurs when executing the jddcreatetree command and the above measures do not work, check the following content:

Check if the system node definition file exists. Also check if read permissions are given.

Execute the jcfexport command and check that it terminates normally.

If the command terminates abnormally, take the corrective action given for the displayed error message.

Check if the Administrators group (in Windows) or the root user (in UNIX) is granted the read permission or write permission for the directory specified by the -o option of the jddcreatetree command.

Make sure that there is sufficient disk space.

KAJY02001-E

The file can not read.(File Name : file-name, Cause : cause)

An attempt to read a file failed.

S:

Suspends processing.

O:

Check whether administrator (in Windows) or root (in UNIX) has read permission on the file.

KAJY02002-E

The file format is not correct.(File Name : file-name, Line : line-number, Column : column-number)

The file format is not correct.

S:

Suspends processing.

O:

Check if the file format is correct, and if not, change it.

The approximate position of the incorrect description is output by Line and Column. When the positions of Line and Column is correct, review the description before and after Line and Column.

KAJY02003-E

The specified value in the file is invalid.(File name : file-name, target location : target-location, Item : item, Factor : factor)

The setting value for the item contained in the file is incorrect.

The target-location indicates where the invalid item is located. If the invalid item is an element of an array, the location is indicated with the index, starting from 0.

Example: links/0/from

S:

Suspends processing.

O:

If an error occurs when the jddcreatetree command is executed:

Check the content of the file and if needed, modify it.

If duplicate IM management nodes are found:

Remove the output result of the jddcreatetree command that is specified in the jddupdatetree command, and start from the execution of the jddcreatetree command again.

If an error occurs when the jddupdatetree command is executed or the JP1/IM - Manager service starts:

Re-execute the jddcreatetree command and then execute the jddupdatetree command.

If an error occurs when the jddupdatesuggestion command is executed:

Check the contents of the suggestion definition file and make corrections.

KAJY02004-W

Since the System node definition file has not set, all hosts are set to the All Systems.(reason : reason)

All hosts were placed directly under All Systems because the system node definition file did not exist or the number of defined systems was zero.

S:

Continues processing.

O:

Check if the jddcreatetree command can be executed without specifying the system node definition file.

KAJY02005-W

Since there is no an applicable system, the host has set directly under the All Systems.(Host name : host-name)

The host that has no applicable system was placed directly under All Systems.

S:

Continues processing.

O:

Check if it is acceptable for the host placed directly under All Systems not to have an applicable system. Host names are displayed in the order of precedence for host names displayed in a window. For details about the host names displayed in a window, see Host name definition file (imdd_host_name.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

KAJY02006-W

Since there are multiple applicable systems, the host has set in to the first defined system.

(Host name : host-name, system set : system-set, system not set : system-not-set)

This host was placed under the system that defines it first because there were multiple applicable systems found.

S:

Continues processing.

O:

Check if the system under which this host is placed is appropriate because it is placed under a system that defines it first when there are multiple applicable systems. Host names are displayed in the order of precedence for host names displayed in a window. For details about the host names displayed in a window, see Host name definition file (imdd_host_name.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

KAJY02007-I

Since the IM configuration management function is enabled, JP1 resource group information set in to remote configuration and operation group is collected.

JP1 resource group information set for the remote configuration and the operation group is collected because the IM configuration management function is enabled.

S:

Continues processing.

KAJY02008-I

Since the IM configuration management function is disabled, JP1 resource group information set in to remote configuration and operation group is not collected.

JP1 resource group information set for the remote configuration and the operation group is not collected because the IM configuration management function is disabled.

S:

Continues processing.

KAJY02009-I

The command (command-name) started.

The command has started.

KAJY02010-I

The command (command-name) ended normally.

The command ended normally.

KAJY02011-E

The argument is invalid. Usage : Usage

An invalid argument was specified for the command.

S:

Aborts processing.

O:

Carefully review the specified argument.

KAJY02012-E

The value specified for the argument is invalid.(argument: argument)

An invalid value was specified for the argument.

S:

Aborts processing.

O:

Carefully review the value specified for the argument.

KAJY02013-E

Failed to set up authentication information.

An attempt to set up authentication information failed.

S:

Aborts processing.

O:

An attempt to set up authentication information failed due to insufficient disk space. Check the free disk space, free up disk space by deleting unnecessary files, for example, and then re-execute the jddsetaccessuser command.

If the disk space is sufficient, wait a while and then re-execute the jddsetaccessuser command. If the problem cannot be resolved, contact the system administrator.

KAJY02014-E

System error occurred by an operation in command execution (Command Name : command-name).(Cause : cause)

A system error occurred when using thecommand.

S:

Aborts processing.

O:

Use the data collection tool to collect data, and then contact the system administrator.

KAJY02015-E

The specified logic host name is invalid.

The specified logical host name is invalid.

S:

Aborts processing.

O:

Check if the logical host specified in the -h option of the command or in the JP1_HOSTNAME environment variable exists.

KAJY02016-E

The item specified in the file is invalid.(File Name : file-name, Item : item, Cause : cause)

The setting value for the item contained in the file is incorrect.

S:

Suspends processing.

O:

Check the contents of the file, and if needed, change it.

KAJY02017-E

An attempt to connect the Intelligent Integrated Management Base has failed.

An attempt to connect to the Intelligent Integrated Management Base failed.

S:

Suspends processing.

O:

Check if the Intelligent Integrated Management Base Service is running.

KAJY02018-E

The authentication to the Intelligent Integrated Management Base has failed.(Cause : cause)

An attempt to connect to the Intelligent Integrated Management Base failed.

S:

Suspends processing.

O:

If the user ID and the password are invalid

Use the jddsetaccsessuser command to set the correct user ID and password again.

If the connection to the authentication server failed

Check if the authentication server is running.

If permissions sufficient for authentication are not granted

Grant one of the following JP1 permission levels to the user ID specified by the jddsetaccsessuser command:

- JP1_Console_Admin

- JP1_Console_Operator

- JP1_Console_User

KAJY02019-E

Concurrent execution is being suppressed.

Execution stopped because a command the same as the one being executed or another command that has an exclusive relationship is being executed.

S:

Suspends processing.

O:

Wait awhile, and then re-execute the command.

KAJY02020-E

The IM Database service cannot be connected to.

The IM Database service (integrated monitoring database) cannot be connected to.

S:

Suspends processing.

O:

If the integrated monitoring database is not set up, please set up integrated monitoring database.

If the integrated monitoring database has already been set up, execute the jimdbstatus command and check whether the IM database service is running. If the IM database service is not running, start the IM database service.

If the IM database service is running, review the values of the following properties set in the intelligent integrated management infrastructure definition file (imdd.properties) and restart the JP1/IM - Manager service :

jp1.im.db.DEFAULT.portNo

jp1.im.db.DEFAULT.logicalHostNum#

#: For logical host only.

KAJY02021-E

An attempt to aquire the event information of JP1/IM - Manager has failed.(Details : details)

An attempt to aquire the event information of JP1/IM - Manager has failed.

S:

Suspends processing.

O:

Take the corrective action according to the message in details.

KAJY02022-W

The System configuration that manages JP1/IM - Manager and event information mapping failed. (Details : details)

The System configuration that manages JP1/IM - Manager and event information mapping failed.

S:

Continues processing.

O:

If a detailed message with message ID is output, take action in accordance with the message.

If a registered JP1 event is included while the host mapping function for the problem source in the integrated monitoring DB is disabled, this message might be output but action is not necesary. For details of mapping between JP1 events and IM management nodes, see 3.4.1 Evaluations using JP1 events in the manual, JP1/Integrated Management 2 - Manager Introduction and Design Guide.

If the above does not apply, collect materials using the data collection tools, and then contact the system administrator.

KAJY02023-E

Failed to create the file.(File Name : file-name, Cause : cause)

Failed to create the file.

S:

Suspends processing.

O:

Check whether the following directories exist, administrator (in Windows)

or root (in UNIX) has read permission and also enough disk space:

If the jddcreatetree command is executed

The directory path specified by jddcreatetree command with -o option

If the jddupdatetree command or jddupdatesuggestion command are executed

In Windows

- In a physical host: Manager-path\data\imdd\

- In a logical host: shared-folder\jp1imm\data\imdd\

In UNIX

- In a physical host: /etc/opt/jp1imm/data/imdd/

- In a logical host: shared-directory/jp1imm/data/imdd/

KAJY02024-E

Failed to replace the management node related master file.(File Name : file-name, Cause : cause)

Failed to replace the management node related master file.

S:

Suspends processing.

O:

Check the access permissions of the displayed file and then re-execute the jddupdatetree command.

KAJY02025-W

The information received from JP1/IM - Manager system configuration is invalid.(Host Name : host-name, Component Name : component-name)

The information received from JP1/IM - Manager system configuration is invalid.

S:

Continues processing.

O:

Use the data collection tool to collect data, and then contact the system administrator.

KAJY02026-W

Failed to create the file.(File Name : file-name, Cause : cause)

Failed to create the file.

S:

Continues processing.

O:

Check whether the following directory exists, administrator (in Windows) or root (in UNIX) has read permission and also enough disk space:

The directory path specified by jddcreatetree command with -o option

KAJY02028-W

An attempt to aquire the system configuration information that manages JP1/IM - Manager has failed.(Host Name : Host Name, Component Name : Component Name, Details : Details)

An attempt to aquire the system configuration information that manages JP1/IM - Manager has failed.

S:

Continues processing.

O:

Take the corrective action according to the message in details.

KAJY02029-E

The authentication information used by Intelligent Integrated Management Base is invalid.

The authentication information used by the Intelligent Integrated Management Base is invalid.

S:

Suspends processing.

O:

Re-execute the jddsetaccessuser command.

KAJY02030-E

The information required to execute jddupdatetree command is not sufficient.

There is not enough information for executing the jddupdatetree command.

S:

Suspends processing.

O:

Execute the jddupdatetree command, with the output destination of the file created by the jddcreatetree command specified for the -o option.

KAJY02032-E

Cannot access the directory specified in the argument.(directory-name)

Cannot access the directory specified in the argument.

S:

Aborts processing.

O:

Check if the directory specified in the argument exists and you have administrator (in Windows) or root (in UNIX) access permissions on the specified directory.

KAJY02033-E

The user does not have permission to execute.

There is no permission to execute the command.

S:

Terminates processing.

O:

Log in again as an administrator who has execution permission, and then retry the operation.

KAJY02034-I

The command (command-name) ended with warnings.

The command ended with warnings.

KAJY02035-I

The command (command-name) ended abnormally.

The command terminated abnormally.

KAJY02038-E

The specified directory path (directory-name) is too long.

The specified directory path is too long.

S:

Suspends processing.

O:

Specify the absolute path of the directory name within 200 characters.

KAJY02039-E

An internal error has occurred. Acquire the relevant data, and then contact the system administrator. : maintenance-information

An internal error occurred.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJY02040-E

An attempt to read the message file has failed.

An attempt to read a massage file failed.

S:

Suspends processing.

O:

Check whether the following files exist, and also administrator (in Windows) or root (in UNIX) has read permission. If the file does not exist, reinstall the JP1/IM - Manager.

InWindows

Manager-path\public\assets\json\KAJY_messages_en.json

Manager-path\public\assets\json\KAJY_messages_ja.json

In UNIX

/opt/jp1imm/public/assets/json/KAJY_messages_en.json

/opt/jp1imm/public/assets/json/KAJY_messages_ja.json

KAJY02041-E

The specified user is not authenticated due to insufficient permissions.(User ID : user-ID)

The user used for authentication has insufficient permissions.

S:

Suspends processing.

O:

Grant one of the following JP1 permission levels to the user ID specified by the jddsetaccsessuser command:

JP1_Console_Admin

JP1_Console_Operator

KAJY02043-E

Failed to generate link information between IM management nodes.(Details : Details)

Failed to generate link information between IM management nodes.

S:

Suspends processing.

O:

Perform the operation following the instructions in the message displayed in the details, and then execute the jddcreatetree command again.

KAJY02044-E

The Link information between IM management nodes is invalid.(Component : Component)

The Link information between IM management nodes is invalid.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJY02045-W

Failed to read the status information of the IM management node.(Filename : Filename, Cause : Cause)

Failed to read the status information of the IM management node.

The statuses of the IM management nodes are re-evaluated in the background from the beginning of the event DB.

S:

Continues processing.

KAJY02046-W

Failed to read the management node related master file.

Failed to read the management node related master file.

S:

Continues processing of without the management node.

O:

The possible causes are as follows:

A temporary file access error occurred.

Eliminate the cause of the error, and then restart JP1/IM - Manager service.

In cases other than the above:

Execute jddupdatetree command, and then re-create the IM management node related information.

KAJY02047-E

The parameter specified for the REST API for publishing events is invalid.

(parameter name: parameter-name, cause:cause)

The REST API for publishing events cannot be executed because an invalid parameter was specified for that REST API.

S:

Suspends event registration processing.

O:

Identify the problem based on the cause, and review the specified parameter.

KAJY02048-E

The JP1 event (event-ID) could not be published:maintenance-information

A JP1 event could not be issued.

S:

Suspends event registration processing.

O:

Determine whether Event Service is running. If it is not running, start it.

If Event Service is running, use the data collection tool to collect data, and then contact a system administrator.

KAJY02049-E

The REST API for acquiring URL information cannot be executed, because the specified parameter is invalid. (parameter name: parameter-name, specified value: specified-value)

The URL information acquisition REST API cannot be executed because an invalid parameter was specified for that REST API.

S:

Suspends URL information acquisition processing.

O:

Review the specified parameter for the URL information acquisition REST API, and then retry the operation.

KAJY02050-E

Failed to get URL information. : detailed-information

Failed to get URL information.

S:

Suspends URL information acquisition processing.

O:

Retry the operation. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAJY02051-E

Failed to generate tree information of IM management nodes.(Details : Details)

Failed to generate tree information of IM management nodes.

S:

Suspends processing.

O:

Perform the operation following the instructions in the message displayed in the details, and then execute the jddcreatetree command again.

KAJY02052-E

The tree information of IM management nodes is invalid.(Component : Component)

The tree information of IM management nodes is invalid.

S:

Suspends processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJY02053-W

Since there is no an applicable system, the node has set directly under the All Systems.(IM management node type : IM-management-node-type, Node name : node-name)

A node without any applicable system was placed directly under All Systems.

S:

Continues processing.

O:

Check if the node placed directly under All Systems actually had no applicable system.

KAJY02054-W

Since there are multiple applicable systems, the node has set in to the first defined system.(IM management node type : IM-management-node-type, Node name : node-name, system set : system-set, system not set : system-not-set)

This node was placed under the system that defines it first because there were multiple applicable systems found.

S:

Continues processing.

O:

Check if the system under which this node is placed is appropriate because it is placed under a system that defines it first when there are multiple applicable systems.

KAJY02055-I

IM Database service is connected.

The IM Database service is connected successfully.

KAJY04100-E

An attempt to connect to the JP1/PFM - Web Console (host:host-name) has failed.

An attempt to connect to the JP1/PFM - Web Console has failed.

S:

The plug-in aborts processing.

O:

Check the following and remove the cause of the problem, and then synchronize configuration information in JP1/IM:

The version of the JP1/PFM - Web Console is 12-00 or later.

Services of the JP1/PFM - Web Console are running.

The IM host can communicate with the JP1/PFM - Web Console host with the following settings:

- The host name that is specified for Monitoring Console Host# (if not specified, the host name output by the jpcconf host hostmode -display command)

- The port number that is specified for Monitoring Console Port# (if not specified, 20358)

- The communication protocol that is specified for Monitoring Console Https# (if not specified, http)

#: Can be set and checked in JP1 Event Configurations of the Master Manage service in the Services window in the JP1/PFM - Web Console.

KAJY04101-E

An error occurred in the JP1/PFM - Web Console. (host:host-name, message:message-ID message)

An error occurred in the JP1/PFM - Web Console.

S:

The plug-in aborts processing.

O:

The following table shows the actions should be taken for each output message ID.

Message ID

Action

KAVJR2000-E

Use the registered user name or the correct password to set the credentials, and then try again. If the problem still persists, contact the system administrator.

KAVJR2001-E

Set the credentials as a user with access permissions to JP1/PFM, and then try again.

KAVJR2002-E

Check and, if necessary, revise the settings of the authentication server, and then try again.

KAVJR2003-E

Change the authentication mode of JP1/PFM to the JP1 authentication mode, and then try again.

KAVJR2004-E

Check if the JP1 authentication server connects with the correct destination or if the server is up and running, and then try again.

KAVJR2005-E

Contact the system administrator.

KAVJR2006-E

Check that the agent corresponding to the specified IM management node has been set up with JP1/PFM - Manager. If so, use the user with access permissions to the hosts managed by the applicable agent to try the operation.

KAVJR2007-E

Wait a while, and then try again. If the problem still persists, check if the health check agent of JP1/PFM - Manager is up and running.

KAVJR2008-E

If the agent corresponding to the specified IM management node or the Store database for the applicable agent is not up and running, start the agent or the Store database, and then try again.

KAVJR2009-E

Wait a while, and then try again. If the problem still persists, check the status of the service for JP1/PFM - Manager.

KAVJR2010-E

Try again. If the problem still persists, restart the JP1/PFM - Web Console service. If the problem still persists after the service is restarted, contact the system administrator.

KAVJR2011-E

Check that JP1/PFM - Manager is running properly, and then try again. If the problem still persists, contact the system administrator.

KAVJR2013-E

Wait a while, and then try again.

KAVJR2014-E

Contact the system administrator.

KAVJR2015-E

Check and, if necessary, revise the value specified for the request message, and then try again.

KAVJR2016-E

Exit unnecessary applications on the JP1/PFM - Web Console host, and then try again.

KAVJR2017-E

Use the registered user name or the correct password to set the credentials, and then try again.

KAVJR2018-E

Connect to JP1/PFM - Manager that satisfies the prerequisites.

KAVJR2202-E

When the performance data retrieval REST API is executed:

Make sure that the values you set for the request message are correct, and then try again.

When the trend data display API or the time series data acquisition API is executed:

Make sure that the values you set in the metric definition file are correct, and then try again.

KAVJR2203-E

Check if the agent can output the specified record ID, or if the agent's manually is necessary to registered in both JP1/PFM - Manager and JP1/PFM - Web Console, and then try again.

For information on the necessity of manual agent registration, see JP1/PFM - Manager and JP1/PFM - Web Console Release Notes.

KAVJR2204-E

Make sure that the specified field ID can be output for the agent, and then try again.

KAVJR2205-E

Specify the start date/time that is earlier than the end date/time, and then try again.

KAVJR2206-E

Specify a valid start and end date/time range, and then try again.

KAVJR2207-E

Make sure that the specified field ID is appropriate for the records, and then try again.

KAVJR2208-E

Check if the value in the specified filter conditions is an acceptable value, and then try again.

KAVJR2209-E

Modify the length of the filter condition value within the range from 1 to 2,048 bytes, and then try again.

KAVJR2210-E

Specify acceptable characters for the filter condition value or use the wildcard (*) to specify a substituted string, and then try again.

KAVJR2211-E

Check and, if necessary, revise the duration or interval for or at which performance data is retrieved, and then try again. If you want to retrieve the performance data without modifying the said duration or interval above, then extend the timeout length for reporting in the initialization file of JP1/PFM - Web Console, and then try again.

If the problem still persists, the service for JP1/PFM - Manager or the agent might be busy. Use the command to show the configuration and status of a service for Performance Management programs to check the status of the service.

KAVJR2212-E

Check if JP1/PFM - Manager is up and running or if the JP1/PFM - Manager host can communicate with the JP1/PFM - Web Console host, and then try again.

KAVJR2213-E

Specify the required key and value, and then try again.

KAJY04102-E

An error occurred during communication with the JP1/PFM - Web Console. (host:host-name)

An error occurred during communication with the JP1/PFM - Web Console.

S:

The plug-in aborts processing.

O:

Make sure that the JP1/IM host can communicate with JP1/PFM - Web Console.

If communications cannot be performed, remove the cause of the problem, and then synchronize configuration information in JP1/IM.

If this error occurs even when communications can be performed, use the data collection tool to collect data, and then contact a system administrator.

KAJY04120-E

An unexpected exception has occurred.

An unexpected error has occurred.

S:

The plug-in aborts processing.

O:

Use the data collection tool to collect data, and then contact a system administrator.

KAJY04150-E

The JP1/PFM - Manager environment is invalid. (rc:maintenance-code)

The system environment for JP1/PFM - Manager is invalid.

S:

Cancels command execution.

O:

System files have been accidentally deleted or access permission settings have been changed. Reinstall JP1/PFM - Manager.

KAJY04151-E

Execution of the adapter command in the JP1/PFM - Manager has failed.

Execution of the adapter command in JP1/PFM - Manager has failed.

S:

Cancels command execution.

O:

If JP1/PFM - Manager is in a logical host environment, make sure that the logical host name of JP1/PFM - Manager and that of JP1/Base are the same.

If JP1/PFM - Manager is in a physical host environment, use the data collection tool to collect data, and then contact a system administrator.

KAJY04152-E

Memory is insufficient in the JP1/PFM - Manager host.

Memory is insufficient in the JP1/PFM - Manager host.

S:

Cancels command execution.

O:

Stop the applications running on the JP1/PFM - Manager host that are not currently in use or increase the amount of memory.

KAJY04153-E

An attempt to access the configuration file in the JP1/PFM - Manager host has failed. (file:file-name)

An attempt to access the file in the JP1/PFM - Manager host has failed.

S:

Cancels command execution.

O:

Check whether the file is accessible. If not, remove the cause.

KAJY04201-E

An internal error occurred.(plugin : plug-in-name, function : function-name, details : detailed-information))

An internal error (argument error) occurred in the plug-in function for JP1/AJS.

S:

The plug-in aborts processing.

O:

Collect data by using the data collection tool, and then contact the system administrator.

KAJY04203-E

There is a contradiction in the configuration information acquisition environment. (plugin : plug-in-name, hostname : target-host-name, details : detailed-information)

There is a contradiction in the configuration information acquisition environment. The JP1/AJS plug-in cannot process the configuration information collected from the target host.

S:

The plug-in aborts processing.

O:

Set up the adapter commands that support the JP1/AJS plug-in. The version information of the adapter for the target host is displayed in detailed-information.

KAJY04204-E

An internal error occurred.(plugin : plug-in-name, function : function-name, details : detailed-information)

An internal error (invalid data collection) occurred in the plug-in function for JP1/AJS.

S:

The plug-in aborts processing.

O:

Collect data by using the data collection tool, and then contact the system administrator. Adapter data information is displayed in detailed-information.

KAJY04205-E

An internal error occurred.(plugin : plug-in-name,, function : function-name, details : detailed-information)

An internal error (invalid data processing) occurred in the plug-in function for JP1/AJS.

S:

The plug-in aborts processing.

O:

Collect data by using the data collection tool, and then contact the system administrator. A JSON.parse error string is displayed in detailed-information.

KAJY04250-E

The collecting information is already running on the same host.

Commands were executed concurrently.

S:

Cancels command execution.

O:

Either wait for the completion of the command that is executed first or forcibly terminate the command, and then try again.

KAJY04251-E

Memory is insufficient.

Memory became insufficient.

S:

Cancels command execution.

O:

Allocate enough memory to execute the command, and then try again.

KAJY04252-E

The permission is insufficient.

The permission is insufficient.

S:

Cancels command execution.

O:

Make sure that you have execution permissions for files or paths in JP1/AJS3 by using the adapter command, and then try again.

KAJY04253-E

The collecting information arguments are invalid.

An invalid argument was specified.

S:

Cancels command execution.

O:

Make sure that the adapter command file was not changed, and then try again.

Confirm that the absolute path to the adapter command is correctly specified for the cmdpath attribute in the adapter command setting file used for linkage with JP1/IM - Manager (Intelligent Integrated Management Base).

KAJY04254-E

The collecting information process could not be generated.

The collecting information process could not be generated.

S:

Cancels command execution.

O:

Memory might be insufficient, or the maximum number of processes that can be generated in the system might be reached. Check the following, and then try again:

For UNIX, the settings of the kernel parameters related to memory and processes are correct.

Sufficient memory is allocated for command execution.

KAJY04255-E

An error occurred during command processing.

An error occurred during internal command execution.

S:

Cancels command execution.

O:

Check the following, and then try again:

The JP1/AJS3 service is running.

The target logical host exists on the host from which information is collected.

KAJY04256-E

The execution environment is invalid.

The execution environment is invalid.

S:

Cancels command execution.

O:

Check the following, and then try again:

For UNIX, the LANG environment variable is set.

JP1/AJS3 is installed.

JP1/AJS3 commands are not deleted or renamed accidentally.

JP1/AJS3 operates in a standard configuration.

KAJY04257-E

I/O error occurred.

An I/O error is detected.

S:

Cancels command execution.

O:

Check the following, and then try again:

The maximum number of processes or the files that can be opened by the system is not exceeded.

The disk has sufficient free space.

Sufficient memory is allocated for command execution.

No hardware problem has occurred on the disk.

KAJY04258-E

An error occurred in the API processing.

An error occurred during execution.

S:

Cancels command execution.

O:

Make sure that the host on which the command was executed has sufficient memory, and then try again.

KAJY04259-E

An unexpected error occurred in the collecting information.

An unexpected error occurred during information collection.

S:

Cancels command execution.

O:

Obtain the succeeding log file and the result of execution of the data collection tool of JP1/IM, and then contact the system administrator:

IMDDAdapter_HITACHI_JP1_AJS3_01.log

IMAC_00.log

IMAC_01.log

IMAC_logical-host-name_00.log

IMAC_logical-host-name_01.log

IMACE_00.log

IMACE_01.log

IMACE_logical-host-name_00.log

IMACE_logical-host-name_01.log

Data collected by the data collection tool of JP1/IM

KAJY04260-E

The number of units exceeds the limit.

The number of units exceeds the limit.

S:

Stops command execution.

O:

The maximum number of units that can be obtained is 400 thousand units. Reduce the total number of units, job groups, manager job groups, and planning groups that have been registered for execution to 400 thousand or less, and then try again.

KAJY22000-W

There is data that is not displayed because the upper limit is reached. (item = item)

Some data is not displayed due to the above limitation.

S:

Continues display processing.

O:

If the message is output to the display:

Remove the link information of the node that is not necessarily shown from the system configuration information and ask the system administrator for the removal to take effect in the system.

If the message is output by the REST API:

Increase the value specified for the parameter of the output item, and then try again.

KAJY22001-E

The link information acquisition REST API cannot be executed because the user does not have the access permissions for the specified node. (jp1user-name : jp1user-name, node : node)

The link information acquisition REST API cannot be executed because the user does not have the access permissions for the specified node.

S:

Aborts processing.

O:

Review the value specified for the node, and then try again.

KAJY22002-E

Specified parameters of the link information acquisition REST API is invalid. (jp1user-name : jp1user-name, parameter name : parameter-name, specified value : specified-value)

The link information acquisition REST API cannot be executed because the parameter specified for the link information acquisition REST API is invalid.

S:

Aborts processing.

O:

Review the parameter specified for the link information acquisition REST API, and then try again.

KAJY22003-E

The specified value for the parameter of the plug-in processing execution REST API is invalid. (jp1user-name : jp1user-name, parameter name : parameter-name, specified value : specified-value)

The plug-in processing execution REST API cannot be executed because the parameter specified for the plug-in processing execution REST API is invalid.

S:

Aborts processing.

O:

Review the parameter specified for the plug-in processing execution REST API, and then try again.

KAJY22004-E

The plug-in processing execution REST API cannot be executed because the user does not have JP1_Console_Admin, JP1_Console_Operator, or JP1_Console_User permission for the specified IM management node. (jp1user-name = jp1user-name, IM management node = im-management-node)

The plug-in processing execution REST API cannot be executed because there are no access permissions on the specified IM management node.

S:

Aborts processing.

O:

Review if the value specified for the sid parameter is correct. If the specified value is correct, contact the system administrator to make sure that the execution user is granted the JP1_Console_Admin, JP1_Console_Operator, or JP1_Console_User permission for the resource group with the configuration information SID. Then, retry the execution.

KAJY22005-E

An error occurred while plug-in processing was being executed. (jp1user-name = jp1user-name, method = method, error message of the plug-in = error-message-of-the-plug-in)

The plug-in processing execution REST API cannot be executed because an error occurred during plug-in processing.

S:

Aborts processing.

O:

Read the plug-in manual to check how to respond to the output error message of the plug-in, take the corrective action, and then try again.

KAJY22006-E

Failed to obtain the time-series data. (IM management node : configuration-information-SID, metric : metric-name, detail : detail)

An attempt to aquire the time series data.

S:

Aborts processing.

O:

Refer to the action indicated for that message found in detail, and take the corrective action.

KAJY22007-E

Failed to obtain the list of metrics. (IM management node : SID, detail : detail)

An attempt to aquire metrics.

S:

Aborts processing.

O:

Refer to the action indicated for that message found in detail, and take the corrective action.

KAJY22008-E

The obtained data is invalid. (IM management : SID, data tyep : data-tyep)

The data received is in valid.

S:

Aborts processing.

O:

Contact the system administrator.

KAJY22009-E

The parameter specified for the REST API for acquiring metrics information is invalid. (parameter name : parameter-name, specified value : specified-value)

The metrics information acquisition REST API cannot be executed because an invalid parameter was specified for that REST API.

S:

Aborts processing.

O:

Review the specified parameter for the metrics information acquisition REST API, and then retry the operation.

KAJY22010-E

The parameter specified for the REST API for acquiring time-series data is invalid. (parameter name : parameter-name,, specified value : specified-value)

The time series data acquisition REST API cannot be executed because an invalid parameter was specified for that REST API.

S:

Aborts processing.

O:

Review the specified parameter for the time series data acquisition REST API, and then retry the operation.

KAJY22011-E

Data cannot be obtained for the specified IM management node. (IM management : SID, data tyep : data-tyep)

The IM management node can't aquire the data is specified.

S:

Aborts processing.

O:

Review the IM management node you specify, and then retry the operation.

KAJY22012-W

Some data cannot be displayed, because the maximum number of instances has been reached. (maximum: upper-limit)

There is data that is not displayed because the upper limit of instance number is reached.

S:

Continues processing.

O:

If the message is displayed in the Trends tab: Contact a system administrator.

If the message is output by the REST API : Increase the specified parameter for the output item, and then retry the operation.

KAJY22015-E

The obtained data is invalid. (tyep : tyep)

The data received is in valid.

S:

Aborts processing.

O:

Collect data by using the data collection tool, and then contact the system administrator.

KAJY22018-E

Replacement of the suggestion-related master file failed. (file name : file-name, cause : cause)

The suggestion-related master file failed to be replaced.

S:

Suspends processing.

O:

Check the access permission for the indicated file and then re-execute the jddupdatesuggestion command.

KAJY22019-E

The parameter specified for the previous execution history acquisition REST API is invalid. (parameter name : parameter-name, specified value : specified-value)

The previous execution history acquisition REST API cannot be executed because a parameter of the API is specified incorrectly.

S:

Suspends processing.

O:

Check the parameter specified for the previous execution history acquisition REST API, and then try again.

KAJY22020-E

The parameter specified for the response action suggestion REST API is invalid. (parameter name : parameter-name, specified value : specified-value)

The response action suggestion REST API cannot be executed because a parameter of the API is specified incorrectly.

S:

Suspends processing.

O:

Check the parameter specified for the response action suggestion REST API, and then try again.

KAJY22021-E

The specified suggestion ID cannot be used to obtain data. (suggestion ID : suggestion-ID, IM management node : tree-SID)

No data can be obtained with the specified suggestion ID.

S:

Aborts processing.

O:

Check the suggestion ID to be specified, and then try again.

KAJY22022-E

The specified suggestion ID is duplicated. (suggestion ID :suggestion-ID)

The REST API cannot be executed because the suggestion ID specified for the REST API parameter is duplicated.

S:

Suspends processing.

O:

Check the parameter specified for the REST API, and then try again.

KAJY22023-I

The response action will now start. (suggestion ID : suggestion-ID, JP1 user name : JP1-user-name, IM management node : tree-SID, action information : action-information)

The execution of the response action will start.

KAJY22024-I

The response action has finished. (suggestion ID : suggestion-ID, JP1 user name : JP1-user-name, IM management node : tree-SID, action information : action-information)

The execution of the response action is completed.

KAJY22025-E

Execution of the response action failed. (suggestion ID : suggestion-ID, JP1 user name : JP1-user-name, cause : cause, IM management node : tree-SID, action information : action-information)

The response action failed to be executed.

S:

Aborts processing.

O:

Check the cause to identify why the failure occurred. If the failure is due to the suggestion definition, correct the suggestion definition file and then execute the jddupdatesuggestion command to apply your changes to the system. After the cause is removed, retry the judgment on the suggestion activation criteria.

KAJY22026-W

Conversion of the variables in the suggestion definition failed. (target area : target-area, variable name : variable-name, cause : cause)

The variables in the suggestion definition failed to be converted.

The target-area indicates where the invalid variable is located in the format described below. If the invalid item is an element of an array, the location is indicated with the index, starting from 0.

suggestion-ID/parameter-name/...

Example: id1/cases/0/0/description

S:

Continues processing.

O:

Check the cause to identify why the failure occurred. If the failure is due to the suggestion definition, correct the suggestion definition file and then execute the jddupdatesuggestion command to apply your changes to the system. After the cause is removed, retry the judgment on the suggestion activation criteria.

KAJY22027-W

The suggestion information after variable conversion is invalid. (target area : target-area, target item : target-item, cause : cause)

The suggestion information including converted variables is invalid.

If the invalid item is an element of an array, the location is indicated with the index, starting from 0.

suggestion-ID/parameter-name/...

Example: id1/cases/0/0/description

S:

Continues processing.

O:

Check the cause to identify what is invalid. If a suggestion definition is invalid, correct the suggestion definition file and then execute the jddupdatesuggestion command to apply your changes to the system. After making corrections, retry the judgment on the suggestion activation criteria.

KAJY22028-W

Judgement of the activation conditions failed. (suggestion ID : suggestion-ID, target area : target-area, cause : cause, IM management node : tree-SID)

The suggestion activation criteria failed to be judged.

The target-area indicates which criterion failed to be judged in the following format:

criterion-type[n]

n indicates the order in the same criterion type, as an integer starting from 1.

S:

Aborts processing.

O:

Check the cause to identify why the failure occurred. If the failure is due to the suggestion definition, correct the suggestion definition file and then execute the jddupdatesuggestion command to apply your changes to the system. After the cause is removed, retry the judgment on the suggestion activation criteria.

KAJY22029-W

The response action is running. (suggestion ID : suggestion-ID, IM management node : tree-SID)

The response action is running.

S:

This message indicates that the response action is running.

KAJY22030-E

The suggestion definition file does not exist. (directory name : directory-name)

The specified directory contains no suggestion definition file.

S:

Suspends processing.

O:

Make sure that the suggestion definition file exists in the specified directory and then retry. The suggestion definition file is named in the following format:

The format to name the suggestion definition file

imdd_suggestion_any-file-name.conf

If the suggestion definition file exists, make sure that the Administrators group (in Windows) or the root user (in UNIX) is granted the read permission for the file.

KAJY22031-E

The parameter specified for the response action execution REST API is invalid. (parameter name : parameter-name, specified value : specified-value)

The response action execution REST API cannot be executed because a parameter of the API is specified incorrectly.

S:

Suspends processing.

O:

Check the parameter specified for the response action execution REST API, and then try again.

KAJY22033-E

The specified response action cannot be executed because the number of concurrent response actions exceeds the maximum. (maximum number of concurrent executions : maximum-concurrent-executions)

The response action cannot be executed because the upper limit of concurrent executions for the response action is exceeded.

S:

Suspends processing.

O:

Make sure that the upper limit of concurrent executions for the response action is not exceeded and then retry the response action.

KAJY22034-W

A suggestion definition is not mapped to any IM managed node. (suggestion ID : suggestion-ID)

The suggestion definitions to be applied with the jddupdatesuggestion command include a suggestion definition that is not mapped to any IM management node.

S:

Continues processing.

O:

Check the value of the member node in the suggestion definition with the indicated suggestion ID. If an error is found, correct the definition and then re-execute the jddupdatesuggestion command.

KAJY22035-W

Duplicate pre-conversion characters have been specified in the configuration file for converting information during event succession. (line : line-number)

The configuration file for converting information during event succession specifies duplicate pre-conversion characters.

S:

Ignores the duplicate definition and continues processing.

O:

The message indicates the line number where an error is found. Correct the invalid definition.

KAJY22036-W

An invalid pre-conversion character has been specified in the configuration file for converting information during event succession. (line : line-number)

The configuration file for converting information during event succession specifies an invalid pre-conversion character.

S:

Ignores the invalid definition and continues processing.

O:

The message indicates the line number where an error is found. Correct the invalid definition.

KAJY22037-W

An invalid post-conversion character string has been specified in the configuration file for converting information during event succession. (line : line-number)

The configuration file for converting information during event succession specifies an invalid post-conversion character.

S:

Ignores the invalid definition and continues processing.

O:

The message indicates the line number where an error is found. Correct the invalid definition.

KAJY22038-W

The number of definitions specified in the configuration file for converting information during event succession has exceeded the maximum of upper-limit.

The configuration file for converting information during event succession has more definitions than the upper limit.

S:

Ignores extra definitions exceeding the upper limit and continues processing.

O:

Check the number of definitions and make corrections.

KAJY22039-W

The syntax of a definition, specified in the configuration file for converting event succession information, is invalid. (line : line-number)

The configuration file for converting information during event succession includes an invalid definition.

S:

Ignores the invalid definition and continues processing.

O:

The message indicates the line number where an error is found. Correct the invalid definition.

KAJY22040-I

The configuration file for converting event succession information was read.

The configuration file for converting information during event succession was read.

KAJY22041-W

An attempt to read the configuration file for converting event succession information has failed. (cause : cause)

The configuration file for converting information during event succession failed to be read.

S:

Stops reading the configuration file for converting information during event succession and continues processing.

O:

Make sure that the configuration file for converting information during event succession is allowed to be read. If the file is readable, check the OS logs listed below to see if a shortage has occurred in an OS resource such as file descriptors.

In Windows: Windows event log

In UNIX: System log (syslog)

If no shortage occurs, use the data collection tool to collect data and contact a system administrator.

KAJY22042-W

It will take a long time to perform matching by using the specified regular expression. This will affect the performance of the jddupdatesuggestion command and the judgment of activation conditions. (file name : file-name, target area : target-area, item : target-item, cause : cause)

The specified regular expression can cause the matching to take a long time. This will affect the performance of the jddupdatesuggestion command or the judgment on suggestion activation criteria.

The target-area indicates where the invalid item is located.

If the invalid item is an element of an array, the location is indicated with the index, starting from 0.

Example: suggestions/0/cases/0/1/key/REGEX_B.MESSAGE

S:

Continues processing.

O:

Modify the regular expression where matching can take a long time.

".*" is specified at the beginning or the end.

Delete .* specified at the beginning or the end.

".*" is specified repeatedly.

Use only one instance of .* at the location where it is repeated.

KAJY22043-E

The value specified for an argument of a common method is invalid. (method name : method-name, argument name : argument-name, specified value : specified-value)

The common method cannot be executed because an invalid argument is specified.

S:

Suspends processing.

O:

Check the arguments of the common method.

KAJY22044-W

Failed to read the suggestion-related master file.

The suggestion-related master file failed to be read.

S:

Continues processing without reading the suggestion-related information.

O:

The possible causes are as follows:

A temporary file access error occurred.

Remove the cause of the error, and then restart the JP1/IM2 - Manager service.

Other than the above

Execute the jddupdatesuggestion command to re-create the suggestion-related information.

KAJY22045-W

Failed to read the previous execution history information of the response action. (file name : file-name, cause : cause)

The previous execution history information of the response action failed to be read.

S:

Continues processing without reading the previous execution history information of the response action.

KAJY22046-E

Failed to replace the previous execution history file. (file name : file-name, cause : cause)

The previous execution history information of the response action could not be saved for the period from when the JP1/IM2 - Manager service started to when the JP1/IM2 - Manager service stopped.

S:

Suspends processing.

O:

Check access permissions for the indicated file.

For the previous execution history information that could not be saved, refer to the response action execution history file.

KAJY22047-W

Failed to obtain information from the Repeated event list window. (suggestion ID: suggestion-ID, cause: cause)

For target events in the Repeated event list window that are specified in the suggestion definition, the information failed to be obtained.

S:

Continues processing.

O:

Check the cause to identify why the failure occurred. If the failure is due to the suggestion definition, correct the suggestion definition file and then execute the jddupdatesuggestion command to apply your changes to the system. After the cause is removed, retry the judgment on the suggestion activation criteria.

KAJY24100-E

An attempt to connect to the JP1/PFM - Web Console (host:host-name) has failed.

An attempt to connect to the JP1/PFM - Web Console has failed.

S:

The plug-in aborts processing.

O:

Check the following and remove the cause of the problem, and then synchronize configuration information in JP1/IM:

The version of the JP1/PFM - Web Console is 12-00 or later.

Services of the JP1/PFM - Web Console are running.

The IM host can communicate with the JP1/PFM - Web Console host with the following settings:

- The host name that is specified for Monitoring Console Host# (if not specified, the host name output by the jpcconf host hostmode -display command)

- The port number that is specified for Monitoring Console Port# (if not specified, 20358)

- The communication protocol that is specified for Monitoring Console Https# (if not specified, http)

#: Can be set and checked in JP1 Event Configurations of the Master Manage service in the Service window in the JP1/PFM - Web Console.

KAJY24101-E

An error occurred in the JP1/PFM - Web Console. (host: host-name, message: message-ID message)

An error occurred in the JP1/PFM - Web Console.

S:

The plug-in aborts processing.

O:

The following table shows the actions should be taken for each output message ID.

Message ID

Action

KAVJR2000-E

Use the registered user name or the correct password to set the credentials, and then try again. If the problem still persists, contact the system administrator.

KAVJR2001-E

Set the credentials as a user with access permissions to JP1/PFM, and then try again.

KAVJR2002-E

Check and, if necessary, revise the settings of the authentication server, and then try again.

KAVJR2003-E

Change the authentication mode of JP1/PFM to the JP1 authentication mode, and then try again.

KAVJR2004-E

Check if the JP1 authentication server connects with the correct destination or if the server is up and running, and then try again.

KAVJR2005-E

Contact the system administrator.

KAVJR2006-E

Check that the agent corresponding to the specified IM management node has been set up with JP1/PFM - Manager. If so, use the user with access permissions to the hosts managed by the applicable agent to try the operation.

KAVJR2007-E

Wait a while, and then try again. If the problem still persists, check if the health check agent of JP1/PFM - Manager is up and running.

KAVJR2008-E

If the agent corresponding to the specified IM management node or the Store database for the applicable agent is not up and running, start the agent or the Store database, and then try again.

KAVJR2009-E

Wait a while, and then try again. If the problem still persists, check the status of the service for JP1/PFM - Manager.

KAVJR2010-E

Try again. If the problem still persists, restart the JP1/PFM - Web Console service. If the problem still persists after the service is restarted, contact the system administrator.

KAVJR2011-E

Check that JP1/PFM - Manager is running properly, and then try again. If the problem still persists, contact the system administrator.

KAVJR2013-E

Wait a while, and then try again.

KAVJR2014-E

Contact the system administrator.

KAVJR2015-E

Check and, if necessary, revise the value specified for the request message, and then try again.

KAVJR2016-E

Exit unnecessary applications on the JP1/PFM - Web Console host, and then try again.

KAVJR2017-E

Use the registered user name or the correct password to set the credentials, and then try again.

KAVJR2018-E

Connect to JP1/PFM - Manager that satisfies the prerequisites.

KAVJR2202-E

When the performance data retrieval REST API is executed:

Make sure that the values you set for the request message are correct, and then try again.

When the trend data display API or the time series data acquisition API is executed:

Make sure that the values you set in the metric definition file are correct, and then try again.

KAVJR2203-E

Check if the agent can output the specified record ID, or if the agent's manually is necessary to registered in both JP1/PFM - Manager and JP1/PFM - Web Console, and then try again.

For information on the necessity of manual agent registration, see JP1/PFM - Manager and JP1/PFM - Web Console Release Notes.

KAVJR2204-E

Make sure that the specified field ID can be output for the agent, and then try again.

KAVJR2205-E

Specify the start date/time that is earlier than the end date/time, and then try again.

KAVJR2206-E

Specify a valid start and end date/time range, and then try again.

KAVJR2207-E

Make sure that the specified field ID is appropriate for the records, and then try again.

KAVJR2208-E

Check if the value in the specified filter conditions is an acceptable value, and then try again.

KAVJR2209-E

Modify the length of the filter condition value within the range from 1 to 2,048 bytes, and then try again.

KAVJR2210-E

Specify acceptable characters for the filter condition value or use the wildcard (*) to specify a substituted string, and then try again.

KAVJR2211-E

Check and, if necessary, revise the duration or interval for or at which performance data is retrieved, and then try again. If you want to retrieve the performance data without modifying the said duration or interval above, then extend the timeout length for reporting in the initialization file of JP1/PFM - Web Console, and then try again.

If the problem still persists, the service for JP1/PFM - Manager or the agent might be busy. Use the command to show the configuration and status of a service for Performance Management programs to check the status of the service.

KAVJR2212-E

Check if JP1/PFM - Manager is up and running or if the JP1/PFM - Manager host can communicate with the JP1/PFM - Web Console host, and then try again.

KAVJR2213-E

Specify the required key and value, and then try again.

KAJY24102-E

An error occurred during communication with the JP1/PFM - Web Console. (host:host-name)

An error occurred during communication with the JP1/PFM - Web Console.

S:

The plug-in aborts processing.

O:

Make sure that the JP1/IM host can communicate with JP1/PFM - Web Console.

If communications cannot be performed, remove the cause of the problem, and then synchronize configuration information in JP1/IM.

If this error occurs even when communications can be performed, use the data collection tool to collect data, and then contact a system administrator.

KAJY24103-E

An invalid argument is specified. (argument-name:specified-value)

The value of the argument is invalid. Alternatively, the argument is not specified. If the argument is not specified, the specified-value is replaced with an empty value.

S:

The plug-in aborts processing.

O:

Specify the argument with a valid value, and then try again.

KAJY24104-E

The specified IM management node does not exist. (IM management node:IM-management-node)

The specified IM management node does not exist.

S:

The plug-in aborts processing.

O:

Make sure that the value of the IM management node is valid, and then try again.

KAJY24105-E

The configuration might have changed during processing.

The configuration information might have been changed during processing.

S:

The plug-in aborts processing.

O:

Take either of the following corrective actions depending on the previous operation:

An operation in the browser:

Refresh the window and then retry the operation in the browser.

An execution of a REST API:

Review the parameter of the REST API, and then retry the operation.

If the configuration information has not been changed,use the data collection tool of JP1/PFM - Manager, JP1/PFM - Web Console, and JP1/IM to collect data, and then contact a system administrator.

KAJY24106-E

An attempt to read the file failed. (file:file)

One of the following operations failed because an attempt to read the file failed or the operation was executed during update of the file:

Showing trend data

Executing the metrics information acquisition API

Executing the time series data acquisition API

For details about the location of the file, see the topic that describes the definition files in the manual JP1/Performance Management Reference.

S:

The plug-in aborts processing.

O:

Retry the operation. If the problem cannot be resolved after the retry, check that the file can be accessed, and then retry the operation.

If the file is the metric definition file, the metric definition file that corresponds to the target JP1/PFM agent might not have been created. In this case, create the metric definition file that corresponds to the target JP1/PFM agent, and then retry the operation.

KAJY24107-E

The format of the file is invalid. (file:file, details : details)

The format of the file is not valid, or the operation might have been executed during the update of the file.

For details about the location of the file, see the topic that describes the definition files in the manual JP1/Performance Management Reference.

S:

The plug-in aborts processing.

O:

Retry the operation. If the problem cannot be resolved after the retry, correct the file format, and then retry the operation.

KAJY24108-E

The value specified for a member is invalid. (file:file, member:member, specified value:specified-value)

The value specified for a member is invalid.

Examples:

A type of value that is not specifiable was specified.

With the number type, a value that is out of the specifiable range was specified.

With the string type, a value with its length not in the specifiable value, or an invalid character code was specified.

For details about the location of the file and the detailed specifiable values, see the topics that describe the definition files in the manual JP1/Performance Management Reference.

S:

The plug-in aborts processing.

O:

Specify a valid value for the member in the file, and then retry the operation.

KAJY24109-E

The specified metric is not defined in the metric definition file. (file: file, metric: specified-value)

The specified metric is not defined in the metric definition file.

The metric definition file might have been updated.

If a REST API is executed without any metric name, the file and specified-value have empty strings.

For details about the location of the file, see the topic that describes the definition files in the manual JP1/Performance Management Reference.

S:

The plug-in aborts processing.

O:

Take either of the following corrective actions depending on the previous operation:

An operation in the browser:

Refresh the window and then retry the operation in the browser.

An execution of a REST API:

Review the parameter of the REST API, and then retry the operation.

KAJY24110-E

The member is not specified. (file:file, member:member)

The member is not specified.

For details about the location of the file, see the topic that describes the definition files in the manual JP1/Performance Management Reference.

S:

The plug-in aborts processing.

O:

Specify a valid value for the member in the file, and then retry the operation.

KAJY24111-E

The value of a member is specified more than once. (file:file, member:member, specified value:specified-value)

The value of a member is specified more than once.

For details about the location of the file, see the topic that describes the definition files in the manual JP1/Performance Management Reference.

S:

The plug-in aborts processing.

O:

Specify the member value in file so that it has no duplicate value, and then retry the operation.

KAJY24112-E

The number of metrics is outside the allowable range. (file: file)

The number of metrics is outside the allowable range.

For details about the location of the file and the allowable range, see the topic that describes the definition files in the manual JP1/Performance Management Reference.

S:

The plug-in aborts processing.

O:

Correct the number of metrics defined in file to be within the allowable range, and then retry the operation.

KAJY24113-E

The suggestion definition file content is invalid. (plugin-function:plug-in-function, member:member)

The contents of the suggestion definition file are invalid.

S:

Suspends processing.

O:

Specify a correct value for the member of the plug-in function, and then try again.

If the value of the member should be a sid, make sure that you specify a sid that is allowed by the plug-in function.

If you have specified the value correctly, use the data collection tools of JP1/PFM - Manager, JP1/PFM - Web Console, and JP1/IM to collect data and contact a system administrator.

KAJY24114-E

JP1/PFM - Manager command could not be executed. (host:host, command:command, error code:error-code)

The command of JP1/PFM - Manager could not be executed.

S:

Suspends processing.

O:

Wait a while, and then retry the operation. If the retry fails, check the following points to remove the cause and then try again:

Is the JP1/Base service running on the host?

Is JP1/Base on the host configured so that the user mapping specifies the JP1/IM host as a server host?

Is the JP1 user that is specified for jp1User in the suggestion definition file mapped to an OS user on the host where the command will run?

Is the version of JP1/PFM - Manager on the host 12-50 or later?

KAJY24115-E

An error occurred in the JP1/PFM - Manager command. (host:host, command:command, error code:error-code, message:message-ID message)

An error occurred in the JP1/PFM - Manager command.

S:

Suspends processing.

O:

For details about how to address the indicated message-ID, see 7. Messages in the manual JP1/Performance Management Reference.

If a JP1/PFM message is not specified as the message ID, check if:

The command name is correct when the command is specified in the suggestion definition file.

The command is located in the tools directory of JP1/PFM - Manager.

KAJY24116-E

An error occurred in the API of the JP1/IM2. (API:API, message:message-ID message)

An error occurred in the API of JP1/IM2.

S:

Suspends processing.

O:

Refer to the action for the indicated message-ID.

KAJY24120-E

An unexpected exception has occurred.

An unexpected error has occurred.

S:

The plug-in aborts processing.

O:

Use the data collection tool of JP1/PFM - Manager, JP1/PFM - Web Console, and JP1/IM to collect data, and then contact a system administrator.

KAJY24201-E

An internal error occurred.(plugin : plug-in-name, function : function-name, details : detailed-information)

An internal error (argument error) occurred in the plug-in function for JP1/AJS.

S:

The plug-in aborts processing.

O:

Take corrective action as follows according to the cause of the error.

If a method to get the list of metrics for time-series data that can be collected was called:

JP1/AJS3 - Manager is version earlier than 12-10.

Check if JP1/AJS3 - Manager where the scheduler service is defined is version 12-10 or later.

For the name of the host where JP1/AJS3 - Manager you are going to check is installed, refer to the name with the class of _JP1AJS-M_ in the specified SID.

If a method to get time-series data is called:

JP1/AJS3 - Manager is version earlier than 12-10.

Check if JP1/AJS3 - Manager where the scheduler service is defined is version 12-10 or later.

For the name of the host where JP1/AJS3 - Manager you are going to check is installed, refer to the name with the class of _JP1AJS-M_ in the specified SID.

The specified metric name is an invalid string.

For details about possible metric names, see 2.4.1 Metrics that can be retrieved from JP1/AJS in the manual JP1/Integrated Management 2 - Manager GUI Reference.

If any of the above conditions apply, eliminate the cause of the error and then re-execute the method.

If the problem is other than the above, use the data collection tool to collect data, and then contact a system administrator.

KAJY24204-E

An internal error occurred. (plugin : plug-in-name, function : function-name, details : detailed-information)

An internal error (invalid data collection) occurred in the plug-in function for JP1/AJS.

S:

The plug-in aborts processing.

O:

Collect data by using the data collection tool, and then contact the system administrator.

KAJY24210-E

The metric definition file is invalid. (plugin : plug-in-name, function : function-name, details : detailed-information)

Information could not be acquired from the metric definition file for JP1/AJS3.

S:

The plug-in aborts processing.

O:

Take corrective action as follows according to the cause of the error.

The metric definition file is not put in place.

The data format of the metric definition file is invalid.

Take the corrective action, and then try again.

If the cause is unknown, use the data collection tool to collect data, and then contact a system administrator.

KAJY24211-E

The JP1/AJS3 plug-in settings file is invalid. (plugin : plug-in-name, function : function-name, details : detailed-information)

Information could not be acquired from the JP1/AJS3 plug-in settings file.

S:

The plug-in aborts processing.

O:

Take corrective action as follows according to the cause of the error.

The JP1/AJS3 plug-in settings file is not put in place.

The data format of the JP1/AJS3 plug-in settings file is invalid.

Take the corrective action, and then try again.

If the cause is unknown, use the data collection tool to collect data, and then contact a system administrator.

KAJY24212-E

An error occurred during the acquisition of information.(plugin : plug-in-name, function : function-name, details : detailed-information)

An error occurred during processing of acquiring information from JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

Take corrective action as follows according to the cause of the error.

The information source host is not running.

There is a problem with the network that connects between JP1/IM and the information source host.

JP1/AJS3 - Manager is not running.

The target logical host does not exist on the host from which information is collected.

The target scheduler service does not exist on the host from which information is collected.

Take the corrective action, and then try again.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24213-E

No metric information exists. (plugin : plug-in-name, function : function-name, details : detailed-information)

The information could not be acquired from JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

Take corrective action as follows according to the cause of the error.

An instance that does not exist in the metric definition file was specified.

An instance that cannot be acquired due to the version of JP1/AJS3 - Manager as an information source is specified for the metric.

Take the corrective action, and then try again.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24217-E

The specified unit name is invalid. (plugin : plug-in-name, function : function-name, details : detailed-information)

The unit name specified in the IM management node link definition file is invalid.

S:

The plug-in does not acquire information about the target unit. Processing continues.

O:

The probable causes are as follows.

There is an error in the specification of precedingJob

It is not the same name as the root jobnet specified in from

It is not a unit under the root jobnet specified in from

There is an error in the specification of succeedingJob

It is not the same name as the root jobnet specified in to

It is not a unit under the root jobnet specified in to

The character string specified for from, to, precedingJob, and succeedingJob is too long

Please specify correctly in the IM management node link definition file. If the information must take effect in the Intelligent Integrated Management server, execute the jddupdatetree command to apply the definitions to the Intelligent Integrated Management server, and then retry the operation. Take the corrective action, and then try again.

If the cause is unknown, use the data collection tool to collect data, and then contact a system administrator.

KAJY24218-W

The related information exceeds the limit.(plugin : plug-in-name, function : function-name, details : detailed-information)

The number of related information has exceeded the following values. Exceeding information will not be acquired.

The upper limit is the value of linkValueLimit specified in the JP1/AJS3 plug-in configuration file, or 64 by default if not specified.

To change the upper limit value, specify linkValueLimit in the JP1/AJS3 plug-in configuration file.

KAJY24219-E

The host name (host-name) IP address could not be acquired. (plugin : plug-in-name, function : function-name, details : detailed-information)

JP1/AJS3 - Manager failed to resolve the host name to its IP address. The processing cannot continue because the JP1/AJS plug-in might not generate a connection using the JP1 event linkage.

S:

The plug-in aborts this processing.

O:

The network must be configured properly so that JP1/AJS3 - Manager can resolve host names to IP addresses through the hosts, jp1hosts, and jp1hosts2 files, the DNS server, or others. Correct the network configuration, and then try again.

KAJY24250-E

Memory is insufficient. (plugin : plug-in-name, function : function-name, details : detailed-information)

Memory shortage occurred in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

Allocate memory necessary for JP1/AJS3 - Manager as an information source, and then retry the operation.

If the error cannot be resolved, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24252-E

The collecting information arguments are invalid. (plugin : plug-in-name, function : function-name, details : detailed-information)

An invalid argument was specified for the command to collect information in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

Take corrective action as follows according to the cause of the error.

A value specified for the start time or end time of the trend information is outside the range that can be obtained by JP1/AJS3-Manager.

Specify the value correctly, and then retry the operation.

Undo the edits properly, and then retry the operation.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager to collect data, and then contact a system administrator.

KAJY24253-E

The collecting information process could not be generated. (plugin : plug-in-name, function : function-name, details : detailed-information)

The collecting information process could not be generated in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

In JP1/AJS3 - Manager, memory might be insufficient, or the maximum number of processes that can be generated in the system might be reached. Check the following, and then try again:

For UNIX, the settings of the kernel parameters related to memory and processes are correct.

Sufficient memory is allocated for command execution.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24254-E

An error occurred during command processing. (plugin : plug-in-name, function : function-name, details : detailed-information)

An error occurred during execution of the command to collect information in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

In JP1/AJS3 - Manager, check the following, and then retry the operation:

Make sure that the host on which information is collected has sufficient memory.

The target logical host exists on the host from which information is collected.

The target scheduler service exists on the host from which information is collected.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24255-E

I/O error occurred. (plugin : plug-in-name, function : function-name, details : detailed-information)

An I/O error was detected in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

In JP1/AJS3 - Manager, check the following, and then retry the operation:

The maximum number of processes or the files that can be opened by the system is not exceeded.

The disk has sufficient free space.

Sufficient memory is allocated for command execution.

No hardware problem has occurred on the disk.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24257-E

An unexpected error occurred in the collecting information. (plugin : plug-in-name, function : function-name, details : detailed-information)

An unexpected error occurred in the command to collect information in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24259-W

Unit does not exist. (plugin : plug-in-name, function : function-name, details : detailed-information)

A unit does not exist in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

The probable causes are as follows. Take action according to the cause of the error.

Cause 1

Check if the information of JP1/AJS3 - Manager is inconsistent with that of JP1/IM.

Action

If it is inconsistent, take the following corrective actions if necessary:

Check if the definitions and statuses of root jobnets are correct in JP1/AJS3 - Manager, and define or register them for execution if necessary.

If the information must take effect in the Intelligent Integrated Management server, execute the jddcreatetree command to generate IM management node-related files, and execute the jddupdatetree command to apply the definitions to the Intelligent Integrated Management server.

Cause 1

The unit name length specified in the IM management node link definition file is long (exceeds 930 bytes) in the Display linked units.

Action

Please specify correctly in the IM management node link definition file.

If the information must take effect in the Intelligent Integrated Management server, execute the jddupdatetree command to apply the definitions to the Intelligent Integrated Management server, and then retry the operation.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24260-E

A timeout occurred during the acquisition of information. (plugin : plug-in-name, function : function-name, details : detailed-information)

A timeout occurred during processing of acquiring information in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

In JP1/AJS3 - Manager, check the following, and then retry the operation:

Does CPU workload not become heavy?

Was the correct the network environment?

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY24261-W

The unit is not registered for execution. (plugin : plug-in-name, function : function-name, details : detailed-information)

The unit is not registered for execution in JP1/AJS3 - Manager.

S:

The plug-in aborts processing.

O:

Check if the information of JP1/AJS3 - Manager is inconsistent with that of JP1/IM. If it is inconsistent, take the following corrective actions if necessary:

Check if the definitions and statuses of root jobnets are correct in JP1/AJS3 - Manager, and register them for execution if necessary.

If the information must take effect in the Intelligent Integrated Management server, execute the jddcreatetree command to generate IM management node-related files, and execute the jddupdatetree command to apply the definitions to the Intelligent Integrated Management server.

If the cause is unknown, use the data collection tools for JP1/AJS3 - Manager and JP1/IM to collect data, and then contact a system administrator.

KAJY32000-E

The event information could not be acquired because it can not connect to the event console server.

The event information could not be acquired because it can not connect to the event console server.

S:

Stops acquiring the event.

O:

Execute the jco_spmd_status command to check if the Event Console Service on the manager host is running, and then try again.

KAJY32001-E

The event information could not be acquired because an error occurred while communicating with the event console server.

The event information could not be acquired because an error occurred while communicating with the event console server.

The possible causes are as follows:

The manager is not running.

The Event Service is not running.

The processing request load is temporarily high.

The IM database service is not in operating status.

The settings of the communication encryption function are not correct.

S:

Stops acquiring the event.

O:

Take corrective action as follows according to the cause of the error.

Confirm that the manager is running.

Confirm that Event Service is running.

If you are using an integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service of the manager host. Confirm that the IM database service is operating, and then retry the operation.

If you are using the communication encryption function, check its settings for errors.

KAJY32002-E

The event information could not be acquired because it can not connect to the event base service.

The event information could not be acquired because it can not connect to the event base service.

S:

Stops acquiring the event.

O:

Execute the jco_spmd_status command to make sure that the Event Base Service is running on the manager host, and then retry the operation.

Execute the jimdbstatus command to check whether the IM database service is running. If not, start the IM database service and then retry the operation.

KAJY32003-E

The event information could not be acquired because it can not connect to the IM Database service.

The event information could not be acquired because it can not connect to the IM Database service.

S:

Stops acquiring the event.

O:

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start the service and then retry the operation. If the IM database service is running, the integrated monitoring database might be busy due to operations from other JP1/IM - View or from the viewer of the Intelligent Integrated Management Base Service. Wait a while and then retry the operation.

KAJY32004-E

An error occurred while acquiring event information from the Integrated Monitoring Database.

An error occurred while acquiring event information from the Integrated Monitoring Database.

S:

Stops acquiring the event.

O:

Make sure that the IM database service is running. If it is not running, start the IM database service, and then retry the operation.

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact the system administrator.

KAJY32005-W

An error occurred in acquiring an event from the integrated monitoring database. Cannot recover the error after attempting the number of retries specified in the system profile. Event search processing was interrupted due to this error.

An error occurred while an event was being acquired from the integrated monitoring database.

S:

Suspends the event search.

O:

Check whether the IM database is running. If not, restart the IM database and then try again.

KAJY32006-E

The settings for a regular expression is incorrect.

The specified regular expression is incorrect.

S:

Stops the event acquisition.

O:

Correct the conditions, and then try again.

KAJY32007-E

The information on the selected event could not be acquired because an error occurred in the Integrated Monitoring Database.

The information on the selected event could not be acquired because an error occurred in the Integrated Monitoring Database.

S:

Stops acquiring information about the event.

O:

Make sure that the IM database service is running. If it is not running, start the IM database service, and then retry the operation.

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact the system administrator.

KAJY32008-E

Failed to obtain detailed event information.

An unexpected error was detected while acquiring the detailed event information to be displayed from the Event Console Service.

S:

Stops acquiring information about the event.

O:

Use the data collection tool to collect data, and then contact the system administrator.

KAJY32010-W

The acquisition of events from the integrated monitoring database was interrupted because the set event search limit was reached. (serial number in the event database : serial-number-in-event-database)

The acquisition of events was interrupted because the specified event search limit was reached. The possible causes are as follows:

The events that are mapped with the specified IM management node contain an event that cannot be retrieved due to an event receiver filter.

Events that are mapped with the specified IM management node cannot be retrieved because setting changes to a business group have not taken effect in the Intelligent Integrated Management Base.

S:

Suspends acquisition of the events.

O:

Check if the setting changes to the business group have taken effect in the Intelligent Integrated Management Base. If not, execute the jddcreatetree command and then execute the jddupdatetree command.

If an event receiver filter is specified, take the following corrective actions:

If the message is output to the display:

If you want to resume event acquisition from the point where it was interrupted, click the Previous button or the Next button in the Events area.

In addition, see 5.4.2 Notes on using event receiver filters in the manual JP1/Integrated Management 2 - Manager Administration Guide to consider changing the event search limit if necessary.

If the message is output by the REST API:

If you want to resume event acquisition from the point where it was interrupted, specify endSid in the response body for the since parameter, and then try again.

KAJY32100-E

The operation-name operation could not be performed on the Integrated Monitoring Database because it can not connect to the Event Console Server.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because a connection could not be established to the Event Console Service.

S:

Suspends processing.

O:

Execute the jco_spmd_status command to make sure that the Event Console Service is running on the manager host, and then retry the operation.

KAJY32101-E

The operation-name operation could not be performed on the Integrated Monitoring Database because an error occurred while communicating with the Event Console Server.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because an error occurred during communication with the Event Console Service.

The possible causes are as follows:

The manager is not running.

The Event Service is not running.

The processing request load is temporarily high.

The IM database service is not in operating status.

The settings of the communication encryption function are not correct.

S:

Suspends processing.

O:

Take corrective action according to the cause of the error.

Make sure that the manager is running.

Make sure that the Event Service is running.

If you are using an integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service of the manager host. Make sure that the IM database service is operating, and then retry the operation.

If you are using the communication encryption function, check its settings for errors.

KAJY32102-E

The operation-name operation could not be performed on the Integrated Monitoring Database because it can not connect to the Event Base Service.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because a connection could not be established to the Event Base Service.

S:

Suspends processing.

O:

Execute the jco_spmd_status command to make sure that the Event Base Service is running on the manager host, and then retry the operation.

KAJY32103-E

The operation-name operation could not be performed on the Integrated Monitoring Database because it can not connect to the IM Database Service.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because a connection could not be established to the IM database service.

S:

Suspends processing.

O:

Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start the service and then retry the operation. If the IM database service is running, the integrated monitoring database might be busy due to operations from other JP1/IM - View or from the viewer of the Intelligent Integrated Management Base Service. Wait a while and then retry the operation.

KAJY32106-E

The operation-name operation could not be performed on the Integrated Monitoring Database because an error occurred while operating the Integrated Monitoring Database.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because an error occurred during operation of the integrated monitoring database.

S:

Suspends processing.

O:

Make sure that the IM database service is running. If it is not running, start the IM database service, and then retry the operation.

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact the system administrator.

KAJY32107-E

The operation-name operation could not be performed on the Integrated Monitoring Database because the Event Service can not connect to that database.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because a connection could not be established to the Event Service.

S:

Suspends processing.

O:

Make sure that the Event Service is running on the manager. If it is not running, start the Event Service, and then retry the operation.

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact the system administrator.

KAJY32109-E

The operation-name operation could not be performed on the Integrated Monitoring Database because an error occurred while operating the Event Database.

The effects of the operation indicated in the message could not be applied to the integrated monitoring database because an error occurred during operation of the event database.

S:

Suspends processing.

O:

Determine whether a memory shortage occurred. If so, restart JP1/IM - Manager, and then retry the operation.

Determine whether the manager host was in high load status. If so, wait awhile, and then retry the operation.

If the cause is other than the above or you cannot recover from the error after retrying the operation, contact the system administrator.

KAJY32110-W

An operation could not be performed for an event because the user does not have the permissions necessary to perform the operation.

An operation for an event could not be performed.

S:

An operation performs for an event only which the user has the permissions necessary to perform the operation.

O:

Check whether the user has JP1_Console_Admin or JP1_Console_Operator permission for the event handling.

KAJY32200-E

The specified parmeter for the event search RESP API is disabled. reason

The event search REST API cannot be executed because the parameter specified for the event search REST API is invalid.

S:

Suspends processing.

O:

Identify the problem based on the reason, review the specified parameter, and then retry the operation.

KAJY32201-E

The syntax of the event search condition is invalid. reason (where-the-error-occurred)

The event search REST API cannot be executed because the syntax of the filter parameter for the event search REST API is incorrect.

S:

Suspends processing of the event search REST API.

O:

Identify the problem based on the reason and then review the syntax of the filter parameter.

KAJY32202-E

The specified node was not be found. (node : node)

The specified node does not exist on the manager.

S:

Suspends processing.

O:

Review the node specified for the parameter of the REST API.

KAJY32210-E

The specified Event Detailed Information Acquisition REST API is invalid. reason

The Event Detailed Information Acquisition REST API cannot be executed because the parameter specified for the Event Detailed Information Acquisition REST API is invalid.

S:

Suspends processing.

O:

Identify the problem based on the reason, review the specified parameter, and then retry the operation.

KAJY32211-E

The specified event was not be found.

An attempt to find the specified event failed. The probable causes are as follows:

The specified event no longer exists in the integrated monitoring database.

Cannot refer the specified event because of settings of user filer or business group.

No event can be found that has the specified JP1 event SID.

S:

Suspends processing.

O:

Check if event receiver filters are applied or events are filtered by business group.

If this message was output from the REST API, check the JP1 event SID specified for a parameter of the REST API.

In the direct access URL function, if the seqno parameter is specified, review the configuration to make sure that event receiver filters or business group filtering does not exclude the event with the event database serial number of seqno.

KAJY32220-E

The specified parmeter for the Event Corresponding Condition Change REST API is invalid. reason

The Event Corresponding Condition Change REST API cannot be executed because the parameter specified for the Event Corresponding Condition Change REST API is invalid.

S:

Suspends processing.

O:

Identify the problem based on the reason, review the specified parameter, and then retry the operation.

KAJY32221-E

The operation cannot be performed, because the statuses are being changed at once. Wait a while, and then try again.

The operation cannot be performed, because the statuses are being changed at once.

S:

Suspends processing.

O:

The operation cannot be performed, because the statuses are being changed at once. Wait a while, and then try again.

KAJY52001-E

Login failed due to a bad username or password.

Login failed.

O:

Check the specified user name and password and then retry the operation.

KAJY52002-E

A communication error occurred while establishing connection with JP1/Base authentication server.

Login failed.

O:

Check if the JP1/Base authentication server can be connected.

KAJY52003-E

Login failed due to an error occurred in the communication with the Intelligent Integrated Management Base Service.

Login failed.

O:

Check if the Intelligent Integrated Management Base Service is running.

KAJY52004-E

Login failed because the user has not given permission to login to the Intelligent Integrated Management Base Service.

Login failed.

O:

Check whether if the specified user has JP1_Console_Admin, JP1_Console_Operator, or JP1_Console_User permission.

KAJY52005-E

Session timeout occurred in the Intelligent Integrated Management Base Service.

The session has timed out.

O:

Perform the login operation again.

KAJY52010-E

Authentication of the token failed.

Authentication of the token failed.

O:

Use the login API operation to get the token again, and then try again.

KAJY52012-E

Specified parameters of Proxy REST API is invalid. (parameter name : parameter-name, specified value : specified-value)

The REST API for specifying proxy authentication information cannot be executed because an invalid parameter was specified for that REST API.

S:

Aborts processing.

O:

Review the specified parameter for the REST API for specifying proxy authentication information, and then retry the operation.

KAJY52013-E

Failed to exclusive proxy credentials.

Failed to exclusive proxy credentials.

S:

Aborts processing.

O:

Wait a while, and then retry the operation.

KAJY52014-E

Failed to set proxy credentials.

Failed to set proxy credentials.

S:

Aborts processing.

O:

If you are deleting proxy authentication information, verify that the specified proxy authentication information are registered.

If the above does not resolve, check that the disk space is not running out.

Check if a disk space shortage occurs. If the disk space is sufficient, wait a while and then try again. If the retry still fails, contact a system administrator.

KAJY52015-W

Proxy credentials will take effect after manager restart.

The proxy authentication information takes effect after JP1/IM - Manager is restarted.

S:

Continues processing.

O:

If the JP1/IM - Manager service is running, try again because the connection with the Intelligent Integrated Management Base is not established successfully.

KAJY52016-W

Disable the setting value and continue because the IP address of the proxy server cannot be resolved. (property name : property, value : specified-value)

An attempt to resolve the IP address of the proxy server specified for jp1.imdd.proxy.server[n].host failed.

S:

Invalidates the setting of jp1.imdd.proxy.server[n] and continues processing.

O:

Specify the host name of which the IP address can be resolved.

KAJY52017-W

Disable the setting value and continue because the proxy server port number is invalid. (property name : property, value : specified-value)

The port number value of the proxy server specified for jp1.imdd.proxy.server[n].port is invalid.

S:

Invalidates the setting of jp1.imdd.proxy.server[n] and continues processing.

O:

Specify it within the range from 1 to 65535.

KAJY52018-W

Disable the setting value and continue because the proxy server corresponding to the REST API execution target host is not set. (property name : property, value : specified-value)

The proxy server specified for jp1.imdd.proxy.target[n].serverHost is not defined in jp1.imdd.proxy.server[n] or invalid.

S:

Invalidates the setting of jp1.imdd.proxy.target[n] and continues processing.

O:

Specify the host name of the proxy server defined in jp1.imdd.proxy.server[n] as jp1.imdd.proxy.target[n].serverHost.

If the KAJY52017-W message for the jp1.imdd.proxy.server[n] property on the applicable proxy server is output, define the proxy server correctly.

KAJY52019-W

The setting value will have no effect because the OpenID provider property is invalid. Processing continues. (OpenID provider : OpenID-provider-key-name, property name : property, value : specified-value)

The property specified for jp1.imdd.oidc.<key-name-of-the-OpenID-provide> or the client secret set through the jddsetopinfo command is invalid or nothing is specified.

S:

Invalidates the setting of the jp1.imdd.oidc.<key-name-of-the-OpenID-provide> property and continues processing.

O:

Check the settings for the jp1.imdd.oidc.<key-name-of-the-OpenID-provide> property.

Check the settings for the jddsetopinfo command.

KAJY52020-E

Failed to set client information for the OpenID provider.

The client information for the OpenID provider failed to be set.

S:

Aborts processing.

O:

Check if a disk space shortage occurs. If the disk space is sufficient, wait a while and then try again. If the retry still fails, contact a system administrator.

KAJY52021-E

The client information for the OpenID provider does not exist.

The client information for the OpenID provider that you attempted to delete does not exist.

S:

Aborts processing.

O:

Check whether the specified OpenID provider key name is correct.

KAJY52022-E

Failed to lock the Single Sign-on mapping definition information.

The exclusive processing failed for the single sign-on mapping definition information.

S:

Aborts processing.

O:

Wait a while, and then retry the operation.

KAJY52023-E

Failed to update the Single Sign-on mapping definition information.

The single sign-on mapping definition information failed to be applied.

S:

Aborts processing.

O:

Check if a disk space shortage occurs. If the disk space is sufficient, wait a while and then try again. If the retry still fails, contact a system administrator.

KAJY52024-W

The version of the JP1/Base authentication server is not a prerequisite version for the OpenID authentication feature.

The version of the authentication server does not meet the version requirement for the OpenID authentication feature.

S:

Invalidates the OpenID authentication feature and continues processing.

O:

When the OpenID authentication feature is enabled, the system administrator needs to make sure that the version of JP1/Base installed on the host where the authentication server resides is 11-50 or later and that the authentication server is not blocked.

KAJY52025-W

The Single Sign-on mapping definition information has not been applied.

The single sign-on mapping definition information is not applied to the Intelligent Integrated Management Base. Apply the single sign-on mapping definition information.

S:

Continues processing.

KAJY52026-E

The Single Sign-on mapping definition file could not be loaded correctly.

The single sign-on mapping definition file could not be loaded correctly.

S:

Suspends processing.

O:

Check whether the single sign-on mapping definition file (imdd_sso_mapping.properties) exists and whether the Administrators group (in Windows) or the root user (in UNIX) is granted the read permission for the file. If the file exists, check whether the file format is valid and make corrections.

For details about the single sign-on mapping definition file, see Single sign-on mapping definition file (imdd_sso_mapping.properties) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

KAJY52027-E

Single Sign-on mapping authentication failed. (OpenID user ID : OpenID-user-ID, JP1 user name : JP1-user-name)

The single sign-on mapping authentication failed.

S:

Suspends processing.

O:

Check the following points to resolve the problem:

Does the single sign-on mapping definition file (imdd_sso_mapping.properties) define information correctly?

Is the single sign-on mapping definition applied to the Intelligent Integrated Management Base?

Is the correct user information registered through the jddsetaccessuser command?

Is the JP1 user registered with the authentication server?

Does the JP1 user have a JP1 permission level (JP1_Console_Admin, JP1_Console_Operator, or JP1_Console_User) required to log in?

Is a DS user that cannot be used for single sign-on mapping authentication specified?

For details about the single sign-on mapping definition file and the jddsetaccessuser command, see Single sign-on mapping definition file (imdd_sso_mapping.properties) in Chapter 2. Definition Files and jddsetaccessuser in Chapter 1. Commands respectively in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

For details about the DS user, see the JP1/Base User's Guide.

KAJY52028-E

OpenID authentication failed.

The OpenID authentication failed.

S:

Suspends processing.

O:

Check the following points to resolve the problem:

Is the OpenID provider defined correctly in the Intelligent Integrated Management Base definition file (imdd.properties)?

Is it possible to communicate with the OpenID provider?

Is the information of the Intelligent Integrated Management Base correctly registered with the OpenID provider?

When the REST API is used, is the correct access token that was issued by the OpenID provider specified?

When the REST API is used, is the OpenID provider configured so that the preferred_username claim of the access token is set to the login user name for the OpenID provider?

Does the Intelligent Integrated Management server host name for the Intelligent Integrated Management Base login URI match the Intelligent Integrated Management server host name for URI of the redirection URL specified in the jp1.imdd.oidc.<OpenID-provider-key-name>.redirect-uri property in the Intelligent Integrated Management Base definition file?

An HTTP session can be invalidated if cookies stored in the WWW browser are deleted or if the interval between an authentication request and the completion of the authentication is too long. Therefore, an HTTP session that is created during authentication request processing can be invalidated even if there is no problem with your settings and communications, causing authentication to fail. If this happens, try authentication by the OpenID provider in the Login window again.

If the above measures do not work, the client secret registered with the jddsetopinfo command may be invalid. Check the client secret registered in the OpenID provider and re-execute the jddsetopinfo command to perform registration, and then restart JP1/IM - Manager.

If the above measures do not work, use the data collection tool to collect data, and then contact a system administrator.

For details about the Intelligent Integrated Management Base definition file (imdd.properties), see Intelligent Integrated Management Base definition file (imdd.properties) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

KAJY52029-E

Failed to lock the client information of the OpenID provider.

The exclusive processing failed for the client information of the OpenID provider.

S:

Aborts processing.

O:

Wait a while, and then retry the operation.

KAJY52030-E

The value specified for the REST API X-Token-Issuer request header is invalid. (value : specified-value)

The REST API cannot be executed because an invalid value is specified for the X-Token-Issuer request header of the REST API.

S:

Aborts processing.

O:

Specify the X-Token-Issuer request header if it is not specified. If it is specified, check whether the specified value is correct against the OpenID provider key name that is defined in the Intelligent Integrated Management Base definition file (imdd.properties).

For details about the Intelligent Integrated Management Base definition file (imdd.properties), see Intelligent Integrated Management Base definition file (imdd.properties) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

KAJY52031-W

The Single Sign-on mapping definition file does not contain a valid definition.

The single sign-on mapping definition information is cleared because the single sign-on mapping definition file does not have any valid definition.

S:

Continues processing.

O:

If you do not intend to clear the single sign-on mapping definition information, review the contents of the single sign-on mapping definition file and then try again.

KAJY52032-W

The OpenID authentication feature cannot be used because the authentication information used by Intelligent Integrated Management Base is invalid.

The authentication information used by the Intelligent Integrated Management Base is invalid, or is not configured.

S:

Continues processing.

O:

If another error message was output before this message, take the corrective action given for that message.

If no error message was output before this message, take either of the following corrective actions:

If the jddsetaccessuser command was not executed, execute the jddsetaccessuser command.

If the jddsetaccessuser command was executed, review the user ID and password you specified and then re-execute the jddsetaccessuser command.

Index

C

communications errors, detailed information about[1]

conventions

fonts and symbols[1]

version numbers[1]

F

font conventions[1]

K

KAJV2001 to KAJV3999[1]

KAJY00001 to KAJY52032[1]

KAVB0001 to KAVB2000[1]

KAVB2001 to KAVB2999[1]

KAVB3001 to KAVB3200[1]

KAVB3501 to KAVB3999[1]

KAVB4001 to KAVB6000[1]

KAVB6001 to KAVB6999[1]

KAVB7001 to KAVB7999[1]

KAVB8000 to KAVB8999[1]

KAVB9001 to KAVB9999[1]

KFPH00212 to KFPH00213[1]

KFPS01850[1]

KFPS05210[1]

KNAN11005 to KNAN11213[1]

KNAN20000 to KNAN21999[1]

KNAN22000 to KNAN26999[1]

KNAN29000 to KNAN29999[1]

KNAN30000 to KNAN30003[1]

M

message IDs[1]

list of[1]

messages

description format[1]

format of[1]

list of[1]

organization of[1]

output destinations of[1]

output format of[1]

overview of[1]

messages related to automated actions and event base service

output destinations of[1]

O

output destination of

messages related to the Intelligent Integrated Management Base[1]

output destinations of

IM Configuration Management messages common to all components[1]

JP1/IM-related common messages[1]

messages from IM database[1]

messages output to operation log[1]

messages related to automated actions and event base service[1]

messages related to Central Console - View[1]

messages related to Central Scope Service[1]

messages related to Central Scope - View[1]

messages related to command execution[1]

messages related to configuration management[1]

messages related to IM Configuration Management[1]

messages related to IM Configuration Management - View[1]

messages related to installation and setup[1]

messages related to process management[1]

messages related to the event generation function[1]

S

symbol conventions[1]

system administrator

actions to be taken for problems during operation[1]

system logs (syslogs), list of[1]

V

version number conventions[1]

W

Windows event logs, list of[1]